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!
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!
FS#26372 - [django][anjuta] django-admin vs. django-admin.py
Attached to Project:
Arch Linux
Opened by Shanto (Shanto) - Monday, 10 October 2011, 09:18 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 19 October 2011, 14:12 GMT
Opened by Shanto (Shanto) - Monday, 10 October 2011, 09:18 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 19 October 2011, 14:12 GMT
|
DetailsThere's a minor conflict in the naming of "django-admin.py" binary between the packages for django and anjuta. The Python>Django project wizard in Anjuta refers to "django-admin" binary (as in Debian) as a required program. However, in the django package, this binary is django-admin.py.
This can be solved either by renaming /usr/bin/django-admin.py to /usr/bin/django-admin (which seems slightly more logical to me), or by patching /usr/share/anjuta/project/django.wiz to refer to django-admin.py instead (patch attached). Note: In case django-admin.py is renamed to django-admin, the wiki article "Django" should be corrected with the new binary name. 
anjuta-django-wiz.patch
(0.5 KiB)
|
This task depends upon
Closed by Ionut Biru (wonder)
Wednesday, 19 October 2011, 14:12 GMT
Reason for closing: Fixed
Additional comments about closing: anjuta 3.2.1
Wednesday, 19 October 2011, 14:12 GMT
Reason for closing: Fixed
Additional comments about closing: anjuta 3.2.1
Dan, can you add a symlink django-admin.py->django-admin ?
Then, we can put symlink(s) in /usr/bin pointing to /usr/lib/python2.7/site-packages/django/bin/django-admin.py:
/usr/bin/django-admin -> /usr/lib/python2.7/site-packages/django/bin/django-admin.py
/usr/bin/django-admin.py -> /usr/lib/python2.7/site-packages/django/bin/django-admin.py (only if it's needed/in use by other apps/people)
It sounds to me like anjuta is broken and hasn't been tested on non-Debian platforms and you need to address this upstream with them.
P.S. Good luck convincing Django to ship this way, their average bug turnaround time is probably close to 30 months...
@Dan I still think that you can consider adding symlinks (as discussed above) to workaround this problem temporarily. Packages from different authors will always have some rough edges to be polished by the distributions. And, as far as I understand, Arch is against extensive patching, but making things work by slight adjustments is not prohibited. Or, is it? :)
By the way, are there any policy for Arch in regard to executable scripts naming (such as xyz.py or abcd.php) inside binary directories? All I could find is an incomplete wiki entry from Allan[1] where he mentions about Debian and Fedora. And, from my quick research, both Debian and Fedora seem to prefer stripping the extension in such cases. For the majority, it just makes more sense, it's prettier, it's convenient, and is more likely preferred.
I think, this bug in Anjuta and/or Django is only one example from many possible applications/use-cases having unnecessary bugs/complexities[2] due to a missing policy/standard shared by the distributions in this regard. So, if either of you are in a position to address this, please do.
[1] https://wiki.archlinux.org/index.php/User:Allan/Python_Packaging_Policy
[2] See the hack at line 25: http://git.gnome.org/browse/anjuta/tree/plugins/project-wizard/templates/django.wiz.in#n25.