Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#22059 - [cherokee] can't find python

Attached to Project: Community Packages
Opened by Filipp Andjelo (scorp) - Saturday, 11 December 2010, 21:21 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 15 December 2010, 22:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Can't configure cherokee WebServer since cherokee-admin is searching for python2 under the name python, which is python3 since the switch to python3.

Additional info:
* cherokee-1.0.13-1

Steps to reproduce:
run 'cherokee-admin-launcher' or 'cherokee-admin'
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 15 December 2010, 22:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1.0.14-2.
Comment by Evangelos Foutras (foutrelis) - Saturday, 11 December 2010, 23:13 GMT
cherokee-admin works, as it's been patched to use python2.

However, cherokee-admin-launcher does indeed need to be fixed to use python2. I'll fix that tomorrow. :)
Comment by Filipp Andjelo (scorp) - Tuesday, 14 December 2010, 18:44 GMT
  • Field changed: Percent Complete (100% → 0%)
problems remains:

$ cherokee-admin
env: python: No such file or directory
ERROR: Couldn't find python.
Comment by Evangelos Foutras (foutrelis) - Tuesday, 14 December 2010, 18:54 GMT
I'm unable to reproduce the issue you're describing. Please post the output of the following command:

$ pacman -Ql cherokee | xargs grep python 2>/dev/null | grep bin | grep usr
Comment by Filipp Andjelo (scorp) - Wednesday, 15 December 2010, 21:38 GMT
Sorry for late answer, I hadn't time to do check it out. Now here you are:

$ pacman -Ql cherokee | xargs grep python 2>/dev/null | grep usr | grep bin
/usr/bin/CTK-run:#!/usr/bin/env python2
/usr/bin/CTK-run:# -*- Mode: python; coding: utf-8 -*-
/usr/bin/CTK-run: 'source!1!interpreter = python %s' %(app_file_path))
/usr/bin/CTK-run:mime!application/x-python-code!extensions = pyc,pyo
/usr/bin/CTK-run:mime!text/x-python!extensions = py
/usr/bin/cherokee-admin-launcher:#!/usr/bin/env python2
/usr/bin/cherokee-admin-launcher:# -*- coding: utf-8; mode: python -*-
/usr/bin/cherokee-tweak:#!/usr/bin/env python2
/usr/bin/cherokee-tweak:# -*- coding: utf-8; mode: python -*-
Binary file /usr/sbin/cherokee-admin matches <---------- This fails, but it's binary! May be hardcoded line the sources?
/usr/share/cherokee/admin/server.py:#!/usr/bin/env python2
/usr/share/cherokee/admin/upgrade_config.py:#!/usr/bin/env python2
/usr/share/doc/cherokee/cookbook_dbslayer.html:<pre><tt>#!/usr/bin/env python
Comment by Filipp Andjelo (scorp) - Wednesday, 15 December 2010, 21:50 GMT
I checked the sources and my assumption was correct. Look into sourcecode

cherokee/main_admin.c:499:
char *const args[] = {"env", "python", "-c", "raise SystemExit", NULL};

I'll make a patch and give it a try.
Comment by Filipp Andjelo (scorp) - Wednesday, 15 December 2010, 22:13 GMT
Here is a new PKGBUILD with a patch. I'm asking if I could commit such bugfixes to repository by myself?
Comment by Evangelos Foutras (foutrelis) - Wednesday, 15 December 2010, 22:27 GMT
Nice find, it's starting to make sense now. I had Python 3 installed on the two machines I tested, and that made the check succeed.

Thanks for the patch and updated PKGBUILD. I chose to use a sed command in the PKGBUILD, which does the same thing. If you can confirm that the bug is resolved in cherokee-1.0.14-2, which I just pushed to [community], I'll go ahead and close this bug report.

Regarding your last question, only TUs have commit access to the repository and push access to [community].
Comment by Filipp Andjelo (scorp) - Wednesday, 15 December 2010, 22:44 GMT
In fact I don't understand why you would want using sed instead of patch in such cases, but it is not important, the point is, it should work :)
I think you can close this bug report now, thank you for your help.

Loading...