Hi Mark,
thanks for the report.
To give everyone arriving here some background:
I was recently fixing a bunch of chrony issues in bug 1867036 which also let me
identify bug 1870144. After discussions the latter was supposed to be fixed in
a systemd upload for bug 1849156.
It seems that systemd upload now (at the start of the Easter weekend to be more
specific) has landed and is causing this :-/
For the root cause analysis I agree to Vincent (thanks for chiming in,
glad to see your LP account now works).
We already changed that line which potentially was an issue in Eoan:
$ git show pkg/ubuntu/eoan-devel:debian/postrm | grep -A 8 '^restore_timesyncd'
| grep "start "
deb-systemd-invoke start systemd-timesyncd || true
$ git show pkg/ubuntu/disco-devel:debian/postrm | grep -A 8
'^restore_timesyncd' | grep "start "
deb-systemd-invoke start systemd-timesyncd
$ git show pkg/ubuntu/bionic-devel:debian/postrm | grep -A 8
'^restore_timesyncd' | grep "start "
systemctl start systemd-timesyncd
So Focal and Eoan are already ok. Upgraders "through" Eoan won't see this issue.
But due to the latest systemd upload upgraders from Bionic will see it.
There is nothing to fix "in Focal" anymore as we already have it there (we
might silence the warning, but that is far less important than the broken
upgrade).
Instead what we will need to SRU the same fix to Bionic to be there
before people will upgrade to Focal.
** Also affects: chrony (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: chrony (Ubuntu Bionic)
Status: New => Triaged
** Changed in: chrony (Ubuntu)
Status: New => Fix Released
** Changed in: chrony (Ubuntu Bionic)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Tags added: server-next ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872183
Title:
package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed
chrony package post-removal script subprocess returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1872183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
