Hi, this bug is reproduced by a Jenkins job nicely setup by Holger:
* general information: http://jenkins.debian.net/job/chroot-test_squeeze_install_gnome_upgrade_to_wheezy/ * last try: http://jenkins.debian.net/job/chroot-test_squeeze_install_gnome_upgrade_to_wheezy/74/consoleFull => \o/ QA! To debug this further, see details and requests bellow. Manuel Rego Casasnovas wrote (19 Dec 2011 08:05:25 GMT) : > I've had this problem several times past weekends trying to install > Wheezy from a fresh Squeeze installation. > The concrete steps to reproduce the problem are: > 1) Install Squeeze > 2) Change your /etc/apt/sources.list from squeeze to wheezy > 3) # apt-get update > 4) # apt-get upgrade > 5) # apt-get dist-upgrade > However, I've been able to avoid this problem skipping point 4). The solution > for me > was: > 1) Install Squeeze > 2) Change your /etc/apt/sources.list from squeeze to wheezy > 3) # apt-get update > 4) # apt-get dist-upgrade > And then everything works like a charm. Indeed, the Jenkins job is doing upgrade before dist-upgrade. Holger, a) Can you confirm Recommends are disabled during this test? (the output seems to indicate this, but I'm unsure) b) How about adding a job that does the dist-upgrade without doing the upgrade first? c) How about adding a job with Recommends set to the opposite of the current one? (Will all possible combinations, that would make 2*2 = 4 times more tests, but I gather the CPU cores are idle, so...) Andreas: you expressed some interest in this issue, so perhaps you might want to replicate these combinations in your piuparts tests too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org