| 2022-10-15 18:03:00 |
Wladimir Mutel |
bug |
|
|
added bug |
| 2022-10-15 18:04:19 |
Wladimir Mutel |
summary |
hardcoded wrong path to run-parts in cron-daily.service |
hardcoded wrong path to run-parts in cron-*.service |
|
| 2022-10-17 08:58:56 |
Wladimir Mutel |
bug task added |
|
debianutils (Ubuntu) |
|
| 2022-10-17 09:41:35 |
Wladimir Mutel |
summary |
hardcoded wrong path to run-parts in cron-*.service |
Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
|
| 2022-10-18 07:53:19 |
Sebastien Bacher |
tags |
|
rls-jj-incoming |
|
| 2022-10-18 07:54:01 |
Sebastien Bacher |
bug |
|
|
added subscriber Sebastien Bacher |
| 2022-10-18 18:15:52 |
Wladimir Mutel |
summary |
Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
|
| 2022-10-18 18:16:53 |
Wladimir Mutel |
description |
package debianutils keeps run-parts executable in /usr/bin/
while package systemd-cron tries to find it in /bin/
$ which run-parts
/usr/bin/run-parts
$ dpkg -S `which run-parts`
debianutils: /usr/bin/run-parts
$ grep =/bin/run /lib/systemd/system/cron*
/lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily
/lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly
/lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly
/lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly
Because of that, cron-daily.serice gets info "failed" state soon after system reboot.
Please resolve the problem to make systemd-cron more usable.
Thanks in advance for your help. |
(Found in Ubuntu 22.04 LTS, also in 22.10)
package debianutils keeps run-parts executable in /usr/bin/
while package systemd-cron tries to find it in /bin/
$ which run-parts
/usr/bin/run-parts
$ dpkg -S `which run-parts`
debianutils: /usr/bin/run-parts
$ grep =/bin/run /lib/systemd/system/cron*
/lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily
/lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly
/lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly
/lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly
Because of that, cron-daily.serice gets info "failed" state soon after system reboot.
Please resolve the problem to make systemd-cron more usable.
Thanks in advance for your help. |
|
| 2022-10-18 18:17:03 |
Wladimir Mutel |
summary |
Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
Ubuntu 22.04/22.10, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
|
| 2022-10-18 18:20:33 |
Wladimir Mutel |
summary |
Ubuntu 22.04/22.10, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course |
|
| 2022-10-18 18:20:52 |
Wladimir Mutel |
description |
(Found in Ubuntu 22.04 LTS, also in 22.10)
package debianutils keeps run-parts executable in /usr/bin/
while package systemd-cron tries to find it in /bin/
$ which run-parts
/usr/bin/run-parts
$ dpkg -S `which run-parts`
debianutils: /usr/bin/run-parts
$ grep =/bin/run /lib/systemd/system/cron*
/lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily
/lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly
/lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly
/lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly
Because of that, cron-daily.serice gets info "failed" state soon after system reboot.
Please resolve the problem to make systemd-cron more usable.
Thanks in advance for your help. |
(Found in Ubuntu 22.04 LTS)
package debianutils keeps run-parts executable in /usr/bin/
while package systemd-cron tries to find it in /bin/
$ which run-parts
/usr/bin/run-parts
$ dpkg -S `which run-parts`
debianutils: /usr/bin/run-parts
$ grep =/bin/run /lib/systemd/system/cron*
/lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily
/lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly
/lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly
/lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly
Because of that, cron-daily.serice gets info "failed" state soon after system reboot.
Please resolve the problem to make systemd-cron more usable.
Thanks in advance for your help. |
|
| 2022-11-10 16:16:52 |
Lukas Märdian |
debianutils (Ubuntu): status |
New |
Incomplete |
|
| 2022-11-17 23:37:57 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2022-11-19 19:07:47 |
Steve Langasek |
debianutils (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2022-11-19 19:07:49 |
Steve Langasek |
systemd-cron (Ubuntu): status |
New |
Won't Fix |
|
