This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.18
---
ubuntu-release-upgrader (1:24.04.18) noble; urgency=medium
[ Nick Rosbrook ]
* tests: fix un-templated expected ubuntu.sources
* DistUpgradeQuirks: prevent upgrades of TPM FDE desktops (LP: #2065229)
*
This bug was fixed in the package ubuntu-release-upgrader - 1:24.10.3
---
ubuntu-release-upgrader (1:24.10.3) oracular; urgency=medium
[ Nick Rosbrook ]
* tests: fix un-templated expected ubuntu.sources
* DistUpgradeQuirks: prevent upgrades of TPM FDE desktops (LP: #2065229)
*
As the test plan mentions, there is no known reproducer for this at the
moment. The best I can do is confirm that the
PostUpgradeInstall=systemd-resolved setting is present for upgrades from
Jammy:
nr@six:/t/tmp.U3JgXkB0Vr$ wget
http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgr
It's not clear to me how to test this package in the context of a `do-
release-upgrade`. I tried both `-d` and `-p` to another minimal Jammy
server install, but it both denied an upgrade with this message:
```
$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
There is no development v
Hello Andreas, or anyone else affected,
Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.17
in a few hours, and then in the -proposed repository.
Please help us by testing this
Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.
(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should b
Fix committed in ubuntu/main
** Summary changed:
- Package wasn't installed on upgrade from Jammy to Noble
+ systemd-resolved wasn't installed on upgrade from Jammy to Noble
** No longer affects: systemd (Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Fix Committe
