Packages don't get updated when there has been a binNMU (strech)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Raspbian |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When a package gets a '+b1' appended to its version (is that a binNMU) it apparently doesn't trigger a similar rebuild on raspbian which results in unsatisfiable dependencies.
I had set up a stretch chroot on my Pi 2 and chrooted into that and tried to install python-minimal:
root@rasppi-2b:/# aptitude install python-minimal -s
The following NEW packages will be installed:
file{a} libexpat1{a} libmagic1{a} libpython-stdlib{a} libpython2.
python2.7{ab} python2.
0 packages upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 4168 kB of archives. After unpacking 20.0 MB will be used.
The following packages have unmet dependencies:
python2.7 : Depends: libpython2.7-stdlib (= 2.7.10-5+b1) but 2.7.10-5 is to be installed.
libpython2.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libpython-stdlib [Not Installed]
2) libpython2.7-stdlib [Not Installed]
3) python [Not Installed]
4) python2.7 [Not Installed]
Leave the following dependencies unresolved:
5) libpython2.
6) python-minimal recommends python
7) python2.7-minimal recommends python2.7
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
root@rasppi-2b:/# apt-cache policy python2.7 libpython2.7-stdlib
python2.7:
Installed: (none)
Candidate: 2.7.10-5+b1
Version table:
2.7.10-5+b1 0
500 http://
libpython2.
Installed: (none)
Candidate: 2.7.10-5
Version table:
2.7.10-5 0
500 http://
Changed in raspbian: | |
status: | New → Fix Released |
We don't syncronise our binnmus with Debian (it would be kinda difficult given the way they build in unstable and migrate to testing while we build in a testing based environment) but that isn't the issue here.
The issue here is that our "mirgrator" which migrates stuff from stretch-staging to stretch doesn't handle binnmus very well. It seems that the python2.7 binary has moved from stretch-staging to stretch but the libpython2.7-stdlib binary has not (because it's stuck in the big openssl transition).