Package: systemd Version: 37-1.1 Followup-For: Bug #634472 Is there any plan on bringing closure to this bug report. I don't know why setserial was installed default on my box but looking at it, it is not really a package required to be installed.
If it is something that'll be installed on most boxes, this bug should be brought to closure soon. When trying systemd, because of this bug, it give a false impression that systemd is still broken. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-22 ii libacl1 2.2.51-5 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-27 ii libcap2 1:2.22-1 ii libcryptsetup4 2:1.4.1-2 ii libdbus-1-3 1.5.10-1 ii libpam0g 1.1.3-7 ii libselinux1 2.1.9-2 ii libsystemd-daemon0 37-1.1 ii libsystemd-login0 37-1.1 ii libudev0 175-3.1 ii libwrap0 7.6.q-23 ii udev 175-3.1 ii util-linux 2.20.1-4 Versions of packages systemd recommends: ii libpam-systemd 37-1.1 Versions of packages systemd suggests: ii python 2.7.2-10 ii systemd-gui 37-1.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
