Bug#763519: systemd cruft
Just came across this bug report and noticed I have the same broken symlink on my machine (weekly updated jessie). I use etckeeper and checked its history. The symlink was added when I first installed docker.io 0.9.0+dfsg1-1. Another machine which only had docker.io installed on it recently (1.2.0~dfsg1-1) does not have the broken symlink. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763519: systemd cruft
Tianon Gravi wrote: > Ah interesting. Do you happen to know if these symlinks created by > dh_systemd_* or are they created by systemd itself? I suspect that systemd might have created those links due to an Alias= setting in the service file, which perhaps got removed. But I have not verified this. -- see shy jo signature.asc Description: Digital signature
Bug#763519: systemd cruft
On 30 September 2014 10:53, Joey Hess wrote: > joey@darkstar:/etc/systemd>find -name \*docker\* -ls > 57690440 lrwxrwxrwx 1 root root 37 Jul 2 14:59 > ./system/multi-user.target.wants/docker.io.service -> > /lib/systemd/system/docker.io.service > > I have this broken symlink on several systems, and suspect it's cruft from > an older version of the docker package. > > (May or may not be related to my sometimes problem with systemd not keeping > docker running.) Ah interesting. Do you happen to know if these symlinks created by dh_systemd_* or are they created by systemd itself? If they're made as part of the package scripts, then it seems like one of the bits that's added to our prerm/postrm probably needs some tweaking so that removes, purges, and/or renames of service files purge these symlinks too (because we definitely don't create that symlink intentionally, and I know that upstream doesn't either, so it's either something that's happened at runtime as part of systemd or something that's happened as a result of one of the dh_* bits). ♥, - Tianon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763519: systemd cruft
Package: docker.io Version: 1.2.0~dfsg1-1 Severity: normal joey@darkstar:/etc/systemd>find -name \*docker\* -ls 57690440 lrwxrwxrwx 1 root root 37 Jul 2 14:59 ./system/multi-user.target.wants/docker.io.service -> /lib/systemd/system/docker.io.service I have this broken symlink on several systems, and suspect it's cruft from an older version of the docker package. (May or may not be related to my sometimes problem with systemd not keeping docker running.) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-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 docker.io depends on: ii adduser 3.113+nmu3 ii iptables1.4.21-2 ii libapparmor12.8.0-8 ii libc6 2.19-11 ii libdevmapper1.02.1 2:1.02.90-2 ii libsqlite3-03.8.6-1 ii perl5.20.1-1 Versions of packages docker.io recommends: ii aufs-tools 1:3.2+20130722-1.1 ii ca-certificates 20140325 ii cgroupfs-mount 1.0 ii git 1:2.1.1-1 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages docker.io suggests: pn btrfs-tools ii debootstrap 1.0.63 pn lxc pn rinse -- no debconf information -- see shy jo signature.asc Description: Digital signature
