[Touch-packages] [Bug 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
Thank you for your bug report, the description fails to mention the Ubuntu serie you are using? assuming it's 22.04 but please either use ubuntu-bug or include details in the futur ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd- cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
how expensive (by time and effort) would it be to add this revert as a SRU ? I see this bug is a copy of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992649 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd- cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
* Revert move to /usr (no. 5). closes: #992481, #992615, #992639, #992649 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd- cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
** Summary changed: - hardcoded wrong path to run-parts in cron-*.service + Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd- cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
