Package: libpam0g Version: 1.1.3-2 Severity: normal I just upgraded from gdm to gdm3 a few weeks ago. Today in my daily dist-upgrade of testing I got a new libpam0g. I always upgrade while being logged in, and to my surprise, the upgrade killed gdm3 in the process... It never did that when I still ran gdm... Does the (postinst?) script not take gdm3 into account?
Please fix this. I lost some work due to this :( -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam0g depends on: ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii multiarch-support 2.13-7 Transitional package to ensure mul libpam0g recommends no packages. Versions of packages libpam0g suggests: pn libpam-doc <none> (no description available) -- debconf information: * libpam0g/restart-services: kdm exim4 cups cron atd libpam0g/xdm-needs-restart: libpam0g/restart-failed: -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
