search

pop-os / upgrade

Utility for upgrading Pop!_OS and its recovery partition to new releases.
GNU General Public License v3.0
95 stars 29 forks source link

Prepare for 24.04 upgrades #330

Open mmstick opened 4 months ago

mmstick commented 4 months ago
mmstick commented 3 months ago

This will require that the updates currently in master_noble are released.

jacobgkau commented 3 months ago

Is this no build available error when forcing an upgrade normal? I don't remember that from testing previous releases pre-release.

screenshot-2024-05-16-17-04-00

The upgrade did continue, despite the message saying it was aborted.

mmstick commented 3 months ago

Yes. Have updates for noble been released yet?

jacobgkau commented 3 months ago

Ah, I see, the "no build available" thing is because there are no 24.04 published isos yet.

Updates for noble have been released now. After adding this branch in the 22.04 VM again, applying all updates, rebooting, and then running pop-upgrade release upgrade -f, this time it seemed to think it was ready to reboot way earlier than it should have (it didn't do this when I tried last week):

screenshot-2024-05-20-21-05-43

The log doesn't look like it contains anything super useful (this was collected after rebooting): out.txt

Any idea why this is happening? I replicated it a second time, making sure there weren't any updates available (including for update-manager-core and ubuntu-release-upgrader-core). pop-upgrade still just downgraded those to the released versions (presumably because they weren't pinned and it reset the system's repos) and then told me to reboot.

screenshot-2024-05-20-21-35-58

I think those packages not being pinned during upgrades (and thus showing up in the output when testing pop-upgrade branches) was existing behavior, but the failure's new.

XV-02 commented 3 months ago

At least once I've seen all package sources updated to Noble, but the distro itself remained 22.04. This was on an Oryp7.

XV-02 commented 2 months ago

I have found, and continue to find, that I need to run the upgrade command (pop-upgrade release upgrade -f) two to three times to actually kick an upgrade off. I added a few lines to the output for clarity but this shows a few reported errors.

On the first attempt, the release upgrade was aborted. On the second, the release upgrade kicked off, but the recovery upgrade was aborted.

mmstick commented 2 months ago

Do you have logs from the pop-upgrade daemon?

mmstick commented 2 months ago

May need to use env S76_TEST=1 to prevent it from upgrading to the version in the master repository.

XV-02 commented 1 month ago

What would the expected behaviour be on a system which does not have Cosmic installed/configured before the upgrade? It looks like the boot process after running upgrade hangs while attempted to start gdm?

mmstick commented 1 month ago

It transitions to what is defined in the pop-desktop packaging for 24.04. The pop-de-cosmic metapackage replaces pop-de-gnome, so most gnome packages will be automatically removed on upgrade. Since cosmic-session provides cosmic-greeter, cosmic-greeter should be set up instead of gdm.

jacobgkau commented 1 month ago

Here's what's in journalctl when the iso failed to install to the recovery partition, in case that helps determine the issue.

screenshot-2024-08-09-22-53-43