Bug #8959
closed
python-gflags has to be pinned to 2.0
Description
build/run-build-packages.sh creates the backports of several packages including python-gflags.
some build failed because dependency mismatch, see:
https://ci.curoverse.com/job/build-packages-debian7/80/console
https://ci.curoverse.com/job/build-packages-debian8/72/console
The following packages have unmet dependencies:
python-arvados-python-client : Depends: python-gflags (< 3.0) but 3.0.3-1 is to be installed
Recommends: git but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
ERROR: python-arvados-python-client test on arvados/package-test:debian8 failed with exit status 100
we do have version 2.0 available in the repo: http://apt.arvados.org/pool/wheezy/main/p/python-gflags/
but I still don't understand it why is not being added.
Updated by Nico César almost 10 years ago
python-gflags_3.0.3-1_all.deb was created at some point and giving dependency issues:
ci:/var/lib/jenkins/workspace/build-packages-debian7/packages/debian7# rm python-gflags_3.0.3-1_all.deb rm: remove regular file `python-gflags_3.0.3-1_all.deb'? y
then https://ci.curoverse.com/job/build-packages-debian7/82/console was successful
can someone review 8959-python-gflags-dependencies so I can merge it?
Updated by Nico César almost 10 years ago
and cleaned the others too:
ci:/var/lib/jenkins/workspace# rm ./build-packages-debian8/packages/debian8/python-gflags_3.0.3-1_all.deb rm: remove regular file `./build-packages-debian8/packages/debian8/python-gflags_3.0.3-1_all.deb'? y ci:/var/lib/jenkins/workspace# rm ./build-packages-ubuntu1204/packages/ubuntu1204/python-gflags_3.0.3-1_all.deb rm: remove regular file `./build-packages-ubuntu1204/packages/ubuntu1204/python-gflags_3.0.3-1_all.deb'? y ci:/var/lib/jenkins/workspace# find -name python-gflags* | grep 3.0 1!ci:/var/lib/jenkins/workspace#
Updated by Tom Clegg almost 10 years ago
I think we can use 'python-gflags<3' in the backports list (see 'pycurl<7.21.5'), which might be better. But either way, LGTM. Thanks.
Updated by Nico César almost 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:e935e107a4ac6250ae64878262c3145d7a62b8e8.
Updated by Nico César almost 10 years ago
Tom Clegg wrote:
I think we can use
'python-gflags<3'in the backports list (see'pycurl<7.21.5'), which might be better. But either way, LGTM. Thanks.
for the PYTHON_BACKPORTS that's invalid syntax :D reverted and got a blue ball. closing this bug.