[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.26 --- ubuntu-release-upgrader (1:24.04.26) noble; urgency=medium [ Erich Eickmeyer ] * DistUpgradeQuirks: install pipewire-audio on ubuntu studio upgrades, uninstalling pulseaudio and preventing install of pulseaudio:i386 (LP: #2078639) [ Nick Rosbrook ] * Run pre-build.sh: updating mirrors and translations. ubuntu-release-upgrader (1:24.04.25) noble; urgency=medium * DistUpgradeQuirks: skip sd-resolved quirk if it's not running (LP: #2078555) * Revert "DistUpgradeQuirks: install pipewire-audio on ubuntu studio upgrades" * Run pre-build.sh: updating mirrors and translations. ubuntu-release-upgrader (1:24.04.24) noble; urgency=medium [ Julian Andres Klode ] * Avoid breaking upgrade by treating cross-grades as replacements (LP: #2081864) [ Nick Rosbrook ] * DistUpgradeQuirks: install pipewire-audio on ubuntu studio upgrades (LP: #2078639) * Run pre-build.sh: updating mirrors and translations. -- Nick Rosbrook Fri, 31 Jan 2025 12:11:23 -0500 ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
I have re-verified using 1:24.04.26 in noble-proposed: root@j2:~# dpkg --add-architecture i386 root@j2:~# wget https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+attachment/5821544/+files/VarLogDistupgradeAptclonesystemstate.tar.gz --2025-02-04 15:00:34-- https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+attachment/5821544/+files/VarLogDistupgradeAptclonesystemstate.tar.gz Resolving bugs.launchpad.net (bugs.launchpad.net)... 185.125.189.222, 185.125.189.223, 2620:2d:4000:1009::f3, ... Connecting to bugs.launchpad.net (bugs.launchpad.net)|185.125.189.222|:443... connected. HTTP request sent, awaiting response... 303 See Other Location: https://launchpadlibrarian.net/751168817/VarLogDistupgradeAptclonesystemstate.tar.gz [following] --2025-02-04 15:00:35-- https://launchpadlibrarian.net/751168817/VarLogDistupgradeAptclonesystemstate.tar.gz Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 185.125.189.228, 185.125.189.229, 2620:2d:4000:1009::13e, ... Connecting to launchpadlibrarian.net (launchpadlibrarian.net)|185.125.189.228|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 870975 (851K) [application/x-gzip] Saving to: ‘VarLogDistupgradeAptclonesystemstate.tar.gz’ VarLogDistupgradeAptclonesystemstate.tar.gz 100%[==>] 850.56K 1.58MB/sin 0.5s 2025-02-04 15:00:36 (1.58 MB/s) - ‘VarLogDistupgradeAptclonesystemstate.tar.gz’ saved [870975/870975] root@j2:~# tar xf VarLogDistupgradeAptclonesystemstate.tar.gz root@j2:~# cp var/lib/apt-clone/dpkg-status /var/lib/dpkg/status root@j2:~# do-release-upgrade --proposed ...SNIP... Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://archive.ubuntu.com/ubuntu jammy InRelease Hit http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit http://archive.ubuntu.com/ubuntu jammy-backports InRelease Hit http://security.ubuntu.com/ubuntu jammy-security InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information Hit http://security.ubuntu.com/ubuntu noble-security InRelease Hit http://archive.ubuntu.com/ubuntu noble InRelease Hit http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit http://archive.ubuntu.com/ubuntu noble-backports InRelease Fetched 0 B in 0s (0 B/s) Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes No candidate ver: libisc-export95 No candidate ver: libssl1.0.0 No candidate ver: libisc-export95 No candidate ver: libssl1.0.0 Do you want to start the upgrade? 36 installed packages are no longer supported by Canonical. You can still get support from the community. 173 packages are going to be removed. 313 new packages are going to be installed. 2220 packages are going to be upgraded. You have to download a total of 4803 M. This download will take about 16 minutes with a 40Mbit connection and about 2 hours 8 minutes with a 5Mbit connection. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled. Continue [yN] Details [d] ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
Hello Marco, 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.26 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-noble ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
I verified the fix using 1:24.04.25 from noble-proposed. One missing step in the test plan is to enable multi-arch if necessary: root@j:~# dpkg --add-architecture i386 Then copy the apt-clone tarball from the bug, and copy it's dpkg status: root@j:~# wget https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+attachment/5821544/+files/VarLogDistupgradeAptclonesystemstate.tar.gz --2025-01-30 20:00:13-- https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+attachment/5821544/+files/VarLogDistupgradeAptclonesystemstate.tar.gz Resolving bugs.launchpad.net (bugs.launchpad.net)... 185.125.189.222, 185.125.189.223, 2620:2d:4000:1009::f3, ... Connecting to bugs.launchpad.net (bugs.launchpad.net)|185.125.189.222|:443... connected. HTTP request sent, awaiting response... 303 See Other Location: https://launchpadlibrarian.net/751168817/VarLogDistupgradeAptclonesystemstate.tar.gz [following] --2025-01-30 20:00:14-- https://launchpadlibrarian.net/751168817/VarLogDistupgradeAptclonesystemstate.tar.gz Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 185.125.189.228, 185.125.189.229, 2620:2d:4000:1009::3b8, ... Connecting to launchpadlibrarian.net (launchpadlibrarian.net)|185.125.189.228|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 870975 (851K) [application/x-gzip] Saving to: ‘VarLogDistupgradeAptclonesystemstate.tar.gz’ VarLogDistupgradeAptclonesyst 100%[>] 850.56K 1.80MB/sin 0.5s 2025-01-30 20:00:15 (1.80 MB/s) - ‘VarLogDistupgradeAptclonesystemstate.tar.gz’ saved [870975/870975] root@j:~# tar xf VarLogDistupgradeAptclonesystemstate.tar.gz root@j:~# cp var/lib/apt-clone/dpkg-status /var/lib/dpkg/status Run the upgrader without --proposed to verify it fails: root@j:~# do-release-upgrade ... SNIP ... Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree... Done Reading state information... Done Then verify that the version in -proposed is able to calculate the upgrade: root@j:~# do-release-upgrade --proposed Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes No candidate ver: libisc-export95 No candidate ver: libssl1.0.0 No candidate ver: libisc-export95 No candidate ver: libssl1.0.0 Do you want to start the upgrade? 36 installed packages are no longer supported by Canonical. You can still get support from the community. 173 packages are going to be removed. 313 new packages are going to be installed. 2220 packages are going to be upgraded. You have to download a total of 4815 M. This download will take about 16 minutes with a 40Mbit connection and about 2 hours 8 minutes with a 5Mbit connection. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled. Continue [yN] Details [d] ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
Dear Brain and the other folks, The upgrade was successful! My steps were: 1) Enable proposed updated in mantic 2) Download the latest release upgrader from here https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.24 3) launch from the unpacked folder ./do-release-upgrade -p to fetch the proposed noble installer 4) Upgrade went through until the end 5) I did not remove the obsolete packages The system booted correctly and it's working so far. If you have any other request for me, please let me know. Thank you a thousand for this effort! Marco PS: I also did: cat
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
Hello Marco, 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.24 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
** Description changed: [Impact] Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as libcap2-bin:amd64 => libcap2-bin:i386 ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) These are Multi-Arch: foreign, hence each architecture provides each other, in some way. The 2nd case is actually fine (the result is marking ghostscript-x for removal, but the correct replacement exists), but the first one, the one in this bug, breaks upgrades (there may be more instances). In most cases this does not cause an issue, as the package being replaced must not be downloadable anymore. In this case, libcap2-bin was installed in a higher version than available in noble (due to epoch). Other cases include held packages (the jammy/mantic version will not be downloadable either), pinning. [Test plan] Ensure the apt-clone tarballs in this bug can be properly upgraded/upgrade resolution completes. A quick validation is to 1. start a container 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status 3. check that do-release-upgrade fails 4. check that do-release-upgrade -p gets to the install prompt A more extensive E2E validation is to fully restore the tarball in a VM, and then actually execute the full upgrade and not just calculate it, but this seems superfluous. [Where problems could occur] We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are packages that really only have replacements on a different architecture. + + [Other information] + + This patch applies to the t64 library transition logic in u-r-u, which + is only present in noble. Hence, the patch is only for that release. [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some fundamental packages in broken state. For instance, python3 and I cannot remove it since it depends on grub-common. The error from /var/log/dist-upgrade is: # grep 'E:' main.log 2024-09-24 18:26:37,663 ERROR Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.' I tried many things, I checked with dpkg --get-selections if I had hold packages and I did not have. My last try was to mark as "hold" grub packages: # apt-mark showhold grub-efi-amd64-bin grub-efi-amd64-signed Could you please give a hand on this one? Thank you very much in advance! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:115:325160:2024-09-23 19:38:03.393134716 +0200:2024-09-23 19:37:57.853134596 +0200:/var/crash/_usr_sbin_thermald.0.crash 640:1000:115:933873:2024-09-22 13:47:22.006442070 +0200:2024-09-22 13:47:23.006442070 +0200:/var/crash/_usr_bin_light-locker.1000.crash CurrentDesktop: KDE Date: Tue Sep 24 18:33:04 2024 InstallationDate: Installed on 2016-03-16 (3114 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-09-24 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-24 18:25:07 Requested-By: beatpanic (1000) End-Date: 2024-09-24 18:25:07 VarLogDistupgradeApttermlog: Log started: 2024-09-24 18:25:07 Log ended: 2024-09-24 18:25:07 ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/479519 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
Deardevelopers, any updates on this bug? I am basically blocked with the upgrade. Thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
** Description changed: [Impact] Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as libcap2-bin:amd64 => libcap2-bin:i386 ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) [Test plan] - Ensure the apt-clone tarballs in this bug and bug 2081864 (ghostscript) - can be properly upgraded/upgrade resolution completes. + Ensure the apt-clone tarballs in this bug can be properly + upgraded/upgrade resolution completes. - A quick validation is to + A quick validation is to 1. start a container 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status 3. check that do-release-upgrade fails 4. check that do-release-upgrade -p gets to the install prompt A more extensive E2E validation is to fully restore the tarball in a VM, - and then actually execute the full upgrade and not just calculate it. - + and then actually execute the full upgrade and not just calculate it, + but this seems superfluous. [Where problems could occur] We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are packages that really only have replacements on a different architecture. - [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some fundamental packages in broken state. For instance, python3 and I cannot remove it since it depends on grub-common. The error from /var/log/dist-upgrade is: # grep 'E:' main.log 2024-09-24 18:26:37,663 ERROR Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.' I tried many things, I checked with dpkg --get-selections if I had hold packages and I did not have. My last try was to mark as "hold" grub packages: # apt-mark showhold grub-efi-amd64-bin grub-efi-amd64-signed Could you please give a hand on this one? Thank you very much in advance! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:115:325160:2024-09-23 19:38:03.393134716 +0200:2024-09-23 19:37:57.853134596 +0200:/var/crash/_usr_sbin_thermald.0.crash 640:1000:115:933873:2024-09-22 13:47:22.006442070 +0200:2024-09-22 13:47:23.006442070 +0200:/var/crash/_usr_bin_light-locker.1000.crash CurrentDesktop: KDE Date: Tue Sep 24 18:33:04 2024 InstallationDate: Installed on 2016-03-16 (3114 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-09-24 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-24 18:25:07 Requested-By: beatpanic (1000) End-Date: 2024-09-24 18:25:07 VarLogDistupgradeApttermlog: Log started: 2024-09-24 18:25:07 Log ended: 2024-09-24 18:25:07 ** Description changed: [Impact] Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as libcap2-bin:amd64 => libcap2-bin:i386 ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) + + The 2nd case is actually fine (the result is marking ghostscript-x for + removal, but the correct replacement exists), but the first one, the one + in this bug, breaks upgrades (there may be more instances) [Test plan] Ensure the apt-clone tarballs in this bug can be properly upgraded/upgrade resolution completes. A quick validation is to 1. start a container 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status 3. check that do-release-upgrade fails 4. check that do-release-upgrade -p gets to the install prompt A more extensive E2E validation is to fully restore the tarball in a VM, and then actually execute the full upgrade and not just calculate it, but this seems superfluous. [Where problems could occur] We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are packages that really only have replacements on a different architecture. [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some f
