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
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
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
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/
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
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
6 matches
Mail list logo
