Package: runit-init Version: 2.1.2-18 Severity: normal Hi,
sometime in the past year or so, you changed /etc/runit/2 so it sets a PATH that no longer contains /usr/local/sbin and /usr/local/bin. I think this is wrong; those are standard locations for locally installed binaries, and they should occur in the PATH *before* their distribution-managed counterparts, to allow locally installed software to override whatever the distribution ships. In my case, the change caused actual breakage when rebooting after the upgrade, because some of my run scripts called stuff from /usr/local, which was suddenly no longer in the PATH. Of course, it would be possible to explcitily set the PATH in all run scripts, but I'd prefer them to inherit a sane default. Best regards, AndrĂ¡s -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (350, 'unstable'), (350, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Versions of packages runit-init depends on: ii getty-run 2.1.2-18 ii initscripts 2.88dsf-59.9+devuan3 ii libc6 2.27-8 ii runit 2.1.2-18 ii runit-helper 2.7.3 ii sysv-rc 2.88dsf-59.9+devuan3 runit-init recommends no packages. runit-init suggests no packages. -- no debconf information -- Back to Nature - but not on foot.