Bug#992649: run-parts in /usr/bin breaks systemd-cron

2022-01-15 Thread Dominique Dumont
On Sun, 2 Jan 2022 19:03:28 +0100 Alexandre Detiste 
 wrote:
> ./configure --runparts="/usr/bin/env run-parts"

The changelog of debianutils 5.0-1 (Aug 2021) shows:
  * Move run-parts to /usr/bin

I guess there are 2 ways to fix this.

Either a compat link (or a script with a deprecation warning) should be 
provided by debianutils as /bin/run-parts or systemd-cron should be modified
to use /usr/bin/run-parts.

What's preventing such a fix ?

Note that locate is also impacted by this bug :

$ locate foobarbaz
locate: warning: database ‘/var/cache/locate/locatedb’ is more than 8 jours 
old (actual age is 135,0 jours)

All the best

Dod



Bug#992649: run-parts in /usr/bin breaks systemd-cron

2022-01-02 Thread Alexandre Detiste
Hi,

I found this bug by luck.
I miss the context (why ? UsrMerge ?)

I can build systemd-cron like this during the transition:

./configure --runparts="/usr/bin/env run-parts"

Greetings,

Alexandre Detiste



Bug#992649: run-parts in /usr/bin breaks systemd-cron

2021-08-21 Thread Clint Adams
On Sat, Aug 21, 2021 at 02:12:14PM -0400, Robert Edmonds wrote:
> Hi,
> 
> systemd-cron's cron targets fail without being able to invoke
> /bin/run-parts, e.g.:
> 
> ● cron-daily.service - systemd-cron daily script service
>  Loaded: loaded (/lib/systemd/system/cron-daily.service; static)
>  Active: failed (Result: exit-code) since Sat 2021-08-21 06:25:03 
> EDT; 41ms ago
>Docs: man:systemd.cron(7)
> Process: 833540 ExecStartPre=/lib/systemd-cron/boot_delay 5 
> (code=exited, status=0/SUCCESS)
> Process: 833541 ExecStart=/bin/run-parts --report /etc/cron.daily 
> (code=exited, status=203/EXEC)
>Main PID: 833541 (code=exited, status=203/EXEC)
> CPU: 27ms
> 
> Aug 21 06:25:03 chase systemd[1]: Starting systemd-cron daily script 
> service...
> Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed to 
> locate executable /bin/run-parts: No such file or directory
> Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed at step 
> EXEC spawning /bin/run-parts: No such file or directory
> Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Main process 
> exited, code=exited, status=203/EXEC
> Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Failed with result 
> 'exit-code'.
> Aug 21 06:25:03 chase systemd[1]: Failed to start systemd-cron daily 
> script service.
> Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Triggering 
> OnFailure= dependencies.

It looks like systemd-cron is hard-coding the path to run-parts in two places:

 * cron-boot.service
 * cron-schedule.service

If this gets fixed, debianutils can add a Breaks for the appropriate
version of systemd-cron.



Bug#992649: run-parts in /usr/bin breaks systemd-cron

2021-08-21 Thread Robert Edmonds
Package: debianutils
Version: 5.3-1
Severity: important

Hi,

systemd-cron's cron targets fail without being able to invoke
/bin/run-parts, e.g.:

● cron-daily.service - systemd-cron daily script service
 Loaded: loaded (/lib/systemd/system/cron-daily.service; static)
 Active: failed (Result: exit-code) since Sat 2021-08-21 06:25:03 EDT; 
41ms ago
   Docs: man:systemd.cron(7)
Process: 833540 ExecStartPre=/lib/systemd-cron/boot_delay 5 
(code=exited, status=0/SUCCESS)
Process: 833541 ExecStart=/bin/run-parts --report /etc/cron.daily 
(code=exited, status=203/EXEC)
   Main PID: 833541 (code=exited, status=203/EXEC)
CPU: 27ms

Aug 21 06:25:03 chase systemd[1]: Starting systemd-cron daily script 
service...
Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed to locate 
executable /bin/run-parts: No such file or directory
Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed at step 
EXEC spawning /bin/run-parts: No such file or directory
Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Main process exited, 
code=exited, status=203/EXEC
Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Failed with result 
'exit-code'.
Aug 21 06:25:03 chase systemd[1]: Failed to start systemd-cron daily script 
service.
Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Triggering OnFailure= 
dependencies.

-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debianutils depends on:
ii  libc6  2.31-16

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Robert Edmonds
edmo...@debian.org