What is the libc6 warning in smxi about? I'm fully dist-upgraded here, including 2.6.31-6 kernel, and haven't noticed any issues.
Back to top

it only affects some users, apparently kdm users, not gdm, though more details are needed.

Since any core lib breaking is a big deal, I just put up a red warning and let people wait, better safe than sorry is the idea. This one should be fixed soon though.
Back to top

H2, today I did some test with the new version of libc6 and I noticed this: the hold on libc6 not work in the kernel section.

For me smxi the first thing that do is:

"Do you want upgrade your kernel?" (if there is a new kernel)

If I answer YES (as I did), libc6 is installed, the hold not affect here.

So when I said YES, "I want upgrade my system" the hold was applied but libc6 was already installed.

On 64bit system and kdm the libc6 2.10.1-7 seems OK.
Back to top

Had the exact same thing happen to me with a d-u yesterday.
first thing smwi proposes is a kernel upgrade, did that and libc6 was upgraded in the process
Only after that I got to see the big warning that there was probably something wrong with libc6 and it was not safe to dist-upgrade :-)

Luckily for me everything went smooth (on a 64-bit system too).
Back to top

ah, right. kernel before warning, I forgot.

Not sure what to do with that.

Maybe I should just move the kernel install to after the du, but the same problem would happen so I guess that wouldn't solve anything.

<update>
bug is fixed now: bugs.debian.org/cgi-bin/bugreport.cgi?bug=555463
so it's not an issue.

If a libc6 type problem arises again I'll think of some mechanism to simply block install in sid of those packages.
Back to top