Hi,
On Sat, 2023-08-19 at 11:17 +0200, Vincent Lefevre wrote:
> First, I initially wasn't aware that this was assuming usrmerge:
> there was no announce at all. Moreover, doing partial upgrades
> is not breaking the system. This is perfectly allowed. That's why
> there is a dependency system, and
On 2023-08-19 07:39:24 +0200, Ansgar wrote:
> On Fri, 2023-08-18 at 22:45 +0200, Vincent Lefevre wrote:
> > On 2023-08-18 07:35:33 +0200, Ansgar wrote:
> > > Please investigate why "usrmerge" is not installed (I assume this is an
> > > upgraded system). Or, if it is installed, why /bin, /sbin,
On Fri, 2023-08-18 at 22:45 +0200, Vincent Lefevre wrote:
> On 2023-08-18 07:35:33 +0200, Ansgar wrote:
> > Please investigate why "usrmerge" is not installed (I assume this is an
> > upgraded system). Or, if it is installed, why /bin, /sbin, /lib* are
> > not symlinks to their respective
On 2023-08-18 07:35:33 +0200, Ansgar wrote:
> This seems the be the real issue:
>
> +---
> | Debian Release: trixie/sid
> | [...]
> | merged-usr: no
> +---[ https://bugs.debian.org/1049969#5 ]
>
> /bin *must* be a symlink to /usr/bin, so /usr/bin/run-parts must exist
> and cron's PATH is
Control: retitle -1 trixie/sid system ended up with split-usr
Hi,
On Thu, 17 Aug 2023 18:42:14 +0200 Vincent Lefevre wrote:
> Control: retitle -1 cron-daemon-common: in /etc/crontab, run-parts is no
> longer in $PATH
>
> That's actually the real reason.
>
> /etc/crontab has
>
>
Control: retitle -1 cron-daemon-common: in /etc/crontab, run-parts is no longer
in $PATH
That's actually the real reason.
/etc/crontab has
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
but
zira:~> dlocate =run-parts
debianutils: /bin/run-parts
--
Vincent Lefèvre - Web:
Package: cron-daemon-common
Version: 3.0pl1-166
Severity: serious
(set to serious because this is a regression whose effect will
be to send a spurious mail every hour)
After upgrading to 3.0pl1-166, I got a mail with
Subject: Cron cd / && run-parts --report /etc/cron.hourly
/bin/sh: 1:
7 matches
Mail list logo
