On Sat, Aug 4, 2012 at 11:14:15 +0200, Andreas Beckmann wrote: > # apt-get --no-y dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following NEW packages will be installed: > gcc-4.7-base gcj-4.7-base libapt-pkg4.12 libdb5.1 libgcj13 libgmp10 > liblzma5 libmount1 libpam-modules-bin libsemanage-common libsemanage1 > libssl1.0.0 libtinfo5 libustr-1.0-1 > multiarch-support python2.7 python2.7-minimal ucf > The following packages have been kept back: > gcc-4.4-base > The following packages will be upgraded: [...] > 76 upgraded, 18 newly installed, 0 to remove and 1 not upgraded. > [...] > > OK, that's not what we want. There shouln't be packages "kept back". > FWIW that result doesn't seem all that bad to me. If that's the only problem I wouldn't consider this bug RC. I guess there might be more issues (or in any case a different result) with libc6-dev on top though, since libc6-dev Breaks squeeze's gcc-4.4. Any chance you could test that? Thanks, Julien
Attachment:
signature.asc
Description: Digital signature