This was fixed in ca-certificates version 20211016 which is what Jammy
released with. As of today, all Ubuntu releases from Bionic onward ship
20230311 so marking as fix released.
** Changed in: ca-certificates (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
** Changed in: ca-certificates (Ubuntu)
Importance: Undecided => High
** Changed in: ca-certificates (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Changed in: ca-certificates (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1914839
Title:
package upgrade should replace
** Changed in: ca-certificates (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1914839
Title:
package upgrade should replace
** Changed in: ca-certificates (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1914839
Title:
package upgrade should replace
Ah yes, /usr/sbin/update-ca-certificates is deleting the ca-
certificates.crt shortly before atomically moving the new version into
place.
It looks like a fic was committed in debian for this a couple of weeks ago:
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914839
Title:
package upgrade should replace /etc/ssl/certs/ca-certificates.crt
