Package: dh-runit
Version: 2.8.14

The fix for bug #934500 has the side effect of introducing broken
symlinks[1] into packages using it, causing complaints by tools that
report such oddities, e.g. adequate(1) or symlinks(1):

| $ sudo symlinks -r /etc | grep dangling
| dangling: /etc/sv/ssh/log/supervise -> /run/runit/supervise/ssh.log
| dangling: /etc/sv/ssh/supervise -> /run/runit/supervise/ssh
| $ adequate openssh-server
| openssh-server: broken-symlink /etc/sv/ssh/log/supervise -> 
| openssh-server: broken-symlink /etc/sv/ssh/supervise -> 

I find that quite annoying.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.5-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

1. For people who actually use runit as init system the symlinks are
   probably not broken, but that is currently a small minority.

Reply via email to