Bug#952572: procps: move binaries back to /bin
On Thu, 27 Feb. 2020, 4:51 pm Paul Wise, wrote: > > Another option would be a compat symlink. > I did think of that but then you have to conditionally put a symlink in when there isn't the /bin directory link or maybe usrmerge there doing it's thing or perhaps there is some third thing that does this linking I didn't know about. So it was just easier to put the binaries back to /bin. I don't personally run any unmerged systems so it is hard to test and keep resting. If someone comes up with a install time helper that does this conditional moving then I'll use that. - Craig
Bug#952572: procps: move binaries back to /bin
On Thu, 27 Feb 2020 07:17:39 +1100 Craig Small wrote: > I think they all should be using a path rather than hard coding where ps > is. But in any case that's what these other packages do. I'll revert the > change. Another option would be a compat symlink. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#952572: procps: move binaries back to /bin
I think they all should be using a path rather than hard coding where ps is. But in any case that's what these other packages do. I'll revert the change. - Craig On Wed, 26 Feb. 2020, 7:45 pm Thorsten Glaser, wrote: > Package: procps > Version: 2:3.3.16-2 > Severity: important > > I just upgraded procps from 2:3.3.16-1+b1 to 2:3.3.16-2 and noticed > the following regression — only the first, of many to probably come: > > tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/postgresql stop > Can't exec "/bin/ps": No such file or directory at > /usr/share/perl5/PgCommon.pm line 613. > Error: Could not exec /bin/ps > No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning). > tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/postgresql start > Can't exec "/bin/ps": No such file or directory at > /usr/share/perl5/PgCommon.pm line 613. > Error: Could not exec /bin/ps > No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning). > > There’s a TC decision to keep supporting not-usrmerged systems, so > please DON’T⚠ just randomly move binaries around. In particular, some > binaries like /bin/ed are required by POSIX to live in /bin if they > are at all installed and others are most likely expected there. > > I’d even consider this RC (breaks unrelated software)… > > -- System Information: > Debian Release: bullseye/sid > APT prefers buildd-unstable > APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, > 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/lksh > Init: sysvinit (via /sbin/init) > > Versions of packages procps depends on: > ii init-system-helpers 1.57 > ii libc62.29-10 > ii libncurses6 6.1+20191019-1 > ii libncursesw6 6.1+20191019-1 > ii libprocps8 2:3.3.16-1+b1 > ii libtinfo66.1+20191019-1 > ii lsb-base 11.1.0 > > Versions of packages procps recommends: > ii psmisc 23.3-1 > > procps suggests no packages. > > -- no debconf information >
Bug#952572: procps: move binaries back to /bin
Hi, Or do not hesitate to use Debian Code Search[1] for more occurrences! ;-) In my case it breaks at least the following script: environment-modules: /etc/profile.d/modules.sh Thanks, Patrice [1] https://codesearch.debian.net/
Bug#952572: procps: move binaries back to /bin
Another place where things must be called with absolute path:
/lib/systemd/system $ grep bin/kill *
gdm3.service:ExecReload=/bin/kill -SIGHUP $MAINPID
gdm.service:ExecReload=/bin/kill -SIGHUP $MAINPID
network-manager.service:#ExecReload=/bin/kill -HUP $MAINPID
NetworkManager.service:#ExecReload=/bin/kill -HUP $MAINPID
openvpn@.service:ExecReload=/bin/kill -HUP $MAINPID
prometheus-node-exporter.service:ExecReload=/bin/kill -HUP $MAINPID
smartmontools.service:ExecReload=/bin/kill -HUP $MAINPID
ssh.service:ExecReload=/bin/kill -HUP $MAINPID
thinkfan.service:ExecReload=/bin/kill -HUP $MAINPID
tor@default.service:ExecReload=/bin/kill -HUP ${MAINPID}
tor@.service:ExecReload=/bin/kill -HUP ${MAINPID}
unbound.service:ExecReload=+/bin/kill -HUP $MAINPID
Please revert this change, or at least put a compat symlink in /bin in
place.
Christoph
Bug#952572: procps: move binaries back to /bin
Package: procps Version: 2:3.3.16-2 Severity: important I just upgraded procps from 2:3.3.16-1+b1 to 2:3.3.16-2 and noticed the following regression — only the first, of many to probably come: tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/postgresql stop Can't exec "/bin/ps": No such file or directory at /usr/share/perl5/PgCommon.pm line 613. Error: Could not exec /bin/ps No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning). tglase@tglase-nb:~ $ sudo cleanenv / /etc/init.d/postgresql start Can't exec "/bin/ps": No such file or directory at /usr/share/perl5/PgCommon.pm line 613. Error: Could not exec /bin/ps No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning). There’s a TC decision to keep supporting not-usrmerged systems, so please DON’T⚠ just randomly move binaries around. In particular, some binaries like /bin/ed are required by POSIX to live in /bin if they are at all installed and others are most likely expected there. I’d even consider this RC (breaks unrelated software)… -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages procps depends on: ii init-system-helpers 1.57 ii libc62.29-10 ii libncurses6 6.1+20191019-1 ii libncursesw6 6.1+20191019-1 ii libprocps8 2:3.3.16-1+b1 ii libtinfo66.1+20191019-1 ii lsb-base 11.1.0 Versions of packages procps recommends: ii psmisc 23.3-1 procps suggests no packages. -- no debconf information
