-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh 20.04 to 22.04 upgrade fails #319
Comments
I attempted to replicate this again today, running This feels like something is wrong with the |
pop-os/default-settings#163 touched the conffiles configuration of |
Perhaps it'll be fixed by renaming it back to |
I see in the
I think the breaking change in pop-os/default-settings@7fcad35 might have been that we used to override So maybe the naming doesn't matter so much as that override. (The new naming is correct if we want to have it use that and then add its auto-generated ones; doesn't matter so much if we use the "correct" name or not if we're overriding?) |
I'm working on this in a branch: https://github.com/pop-os/default-settings/tree/conffiles_jammy |
|
Steps to reproduce:
The system has the upgrade complete/rebooting message much quicker than expected, and the system reboots back into version 20.04, but with all sources pointing to Jammy.
Full offline upgrader log: upgrade.log
The following output is near the top of the log file:
Output:
The
E: Internal error, InstallPackages was called with broken packages!
error then repeats after later steps in the log file.On my test VM, after I booted back into 20.04, the Jammy sources were valid. Performing a regular
apt upgrade
(as many users are unaware offull-upgrade
), I noticed that I was asked whether or not to upgrade various files in/etc
, including our/etc/os-release
and/etc/lsb-release
files, with the default choice being "no":This explains why some users have appeared on Mattermost with mostly-upgraded systems but with those files still reporting that they're on the prior release.
After finishing the
apt upgrade
, there were still a number of packages that needed to be upgraded usingapt full-upgrade
. Doing that and then rebooting, I dropped into a busybox prompt. Not sure of the actual end state of the system, but we should probably focus on the earlier pop-upgrade failure first (as everything after that is dependent on how the user tries to proceed.)The text was updated successfully, but these errors were encountered: