Package: libc6 Version: 2.19-7 Followup-For: Bug #751169 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Greetings, I'm not really sure if this is really related to this bug, however: libc6 upgrades always fail (leaving the system in the unstable state mentioned earlier) when the upgrade is done by synaptic. I could observe this for at least the three last versions (but probably more). This happened on two distinct machines (the one I'm sending this report from and another being also i386/i686). Regards Sven - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libgcc1 1:4.9.0-7 Versions of packages libc6 recommends: ii libc6-i686 2.19-7 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.53 pn glibc-doc <none> ii locales 2.19-7 - -- debconf information: * glibc/upgrade: true * glibc/restart-services: exim4 cups cron atd glibc/disable-screensaver: * libraries/restart-without-asking: false glibc/restart-failed: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJTyPkDAAoJEPUFi27xeHupJh4H/25rvO8do1aOVcthd1pP9EOz n5Gpc2JTqVP3yvWfYmq0JB3t6W8KCCG3fn+C4IULVavbE2aV8E9BO10L2RFNO6Zx VfM413SlVDn9mNCG2PUFhG4gc8HW0/K9eL7FwhZ3atx6mxEbIRAn3ivJT3bdZ2LY 4mE/P7nS1HiaWdYaVY+htQLye/4aJdkS/X6F6FRJ28lcfJqJSKsVHkVV1NH7xe/0 uMa/KxEowWhygzZU0cVza2RD5QqsM8OyG9ddnPlEFKPAUb7hRfG2zJp/5CJTHwfV H9up5NlWVcJeeKfc2pnTbksSGR+zcECe7M5fk1FRdeQ/TRlj8xxcPf89XrfCM44= =6iIl -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
