[Bug 1506536] Re: FTBFS because of python3.5
Łukasz Zemczak
1506536 at bugs.launchpad.net
Thu Oct 15 20:16:23 UTC 2015
Ok, so I have a proposed fix for this failure here, but I would
appreciate someone to review as I don't know enough about the
conventions in python packages. The issue here is that in debian/rules
we use pyversions/py3versions -s - which basically means to print all
'supported' versions, regardless if those are installed currently or
not. Since right now both 3.4 and 3.5 are supported, it wants to install
it for both - even though only one is installed. My proposed fix is to
use -i instead - printing all supported and installed versions. This way
we define what to build the package against in the dependencies. I think
this is more correct.
We could also change the deps, but that would be ugly.
** Patch added: "Fix for the FTBFS"
https://bugs.launchpad.net/ubuntu/+source/pylint/+bug/1506536/+attachment/4496077/+files/pylint_1.3.1-3ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pylint in Ubuntu.
https://bugs.launchpad.net/bugs/1506536
Title:
FTBFS because of python3.5
Status in pylint package in Ubuntu:
In Progress
Bug description:
Don't worry about the summary, it's not a python3.5 regression but
more like an issue with the package handling 3.5. Happened during the
wily test-rebuild [1]. Log:
/bin/sh: 3: python3.5: not found
debian/rules:15: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:12: recipe for target 'build' failed
make: *** [build] Error 2
[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
rebuild-20151001-wily.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pylint/+bug/1506536/+subscriptions
More information about the foundations-bugs
mailing list