Package: apt Version: 1.0.1 Severity: normal Tags: moreinfo User: helm...@debian.org Usertags: rebootstrap
Dear apt maintainers, In a particular circumstance I arrive at a situation where apt's cache appears to be subtly wrong. The immediate observation is: # apt-get check Reading package lists... Building dependency tree... Reading state information... You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: libatomic1:m68k : PreDepends: multiarch-support:m68k but it is not installable libgcc2:m68k : PreDepends: multiarch-support:m68k but it is not installable libgomp1:m68k : PreDepends: multiarch-support:m68k but it is not installable libstdc++6:m68k : PreDepends: multiarch-support:m68k but it is not installable E: Unmet dependencies. Try using -f. # If I then issue apt-get --no-download update and run apt-get check again, no error is reported. I would not have expected a run of apt-get update to be able to correct a dependency problem and therefore conclude a bug in apt. Now describing the circumstances in which this happens has proven to be hard. It is reproducible very reliably: Jenkins runs into it in every rebootstrap build. https://jenkins.debian.net/job/rebootstrap_arm64_gcc49/9/console Having to wait 5 hours for a reproducer is a bad thing though, which is why I tag this bug as moreinfo. The basic sequence of the rebootstrap job (from the point of view of apt) is: * debootstrap a sid chroot and run everything in there. * Run apt-get update once and never again (without --no-download). * dpkg --add-architecture $some_arch * Iteratively change packages using operations: * apt-get install -y ... # build-depends * apt-get remove -y ... # build-conflicts * dpkg -i *.deb # results from some dpkg-buildpackage Among other things this causes the foreign libc and foreign gcc libraries to replaced with differently staged packages of the same version. After installing gcc stage2 and eglibc stage2, apt-get check thinks that everything is fine. Once installing the gcc stage3, the above errors show up (and are "healed" by apt-get --no-download update). This is a summary of the current diagnosis of this issue and its main goal is to obtain a bug number to reference the issue from elsewhere. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
