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#35854 - [python2-pylint] dependency problem (python2-logilab-astng)
Attached to Project:
Arch Linux
Opened by Damien (_djm_) - Wednesday, 19 June 2013, 18:42 GMT
Last edited by Angel Velasquez (angvp) - Friday, 28 June 2013, 14:00 GMT
Opened by Damien (_djm_) - Wednesday, 19 June 2013, 18:42 GMT
Last edited by Angel Velasquez (angvp) - Friday, 28 June 2013, 14:00 GMT
|
DetailsDescription:
pylint2 won't run with version 0.28.0-1. I get the following: Traceback (most recent call last): File "/usr/bin/pylint2", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2854, in <module> parse_requirements(__requires__), Environment() File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 594, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: logilab-astng>=0.24.3 It looks like it is expecting python2-logilab-astng to be at least 0.24.3, while it is currently 0.24.1 in [extra]. pylint2 works fine after downgrading to python2-pylint 0.27.0-1. |
This task depends upon
Closed by Angel Velasquez (angvp)
Friday, 28 June 2013, 14:00 GMT
Reason for closing: Fixed
Additional comments about closing: Version of logilab-astng and logilab-common updated
Friday, 28 June 2013, 14:00 GMT
Reason for closing: Fixed
Additional comments about closing: Version of logilab-astng and logilab-common updated
Comment by Médéric Boquien (mboquien) -
Friday, 28 June 2013, 07:06 GMT
I can reproduce the problem with a completely up to date system. The guilty package has been flagged as outdated for over 3 months now. Maybe the packager is not active anymore?
Comment by Angel Velasquez (angvp) -
Friday, 28 June 2013, 13:39 GMT
pylint shouldn't had to be upgraded to the last release but it was, dependencies of pylint are very broken and I had to research and make some patches, i will push something more stable soon, but I can't guarantee that it won't open different bug reports on the future, in case that happens, I simply will ask for a new maintainer or drop it into AUR.