| Summary: | M8->M9 Plasma upgrade attempt in VirtualBox fails, because of conflict between fwupd & fwupdx64-efi | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Andrews <andrewsfarm> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.mageia.org/show_bug.cgi?id=30799 | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Thomas Andrews
2023-05-02 02:10:13 CEST
After I saw that an updated fwupd-efi had arrived at my mirror-of-choice, I revisited this vbox guest and tried getting the updates again. This time they were successful. After removing 15 orphans, I rebooted to a working desktop once again. To all appearances, it's OK. I don't know what this might mean for the php-pear script errors I saw after the first pass of the upgrade. I can restore the M8 guest and try the upgrade again, and see what happens. This particular mga8 guest had been used to test updates in the past, and while many packages had been removed after testing, I don't know what else might have been left behind. In addition, there were some tested packages that had not been removed. My thinking was that it's not a bad real-world simulation of a M8->M9 upgrade, as few users will be doing such upgrades on basic, unused systems. This is a worms' nest going back a year or two; these are all still open! This bug is not quite the same as the others, though. This looks the essential: "file /usr/libexec/fwupd/efi/fwupdx64.efi from install of fwupd-efi-1.3-1.mga9.x86_64 conflicts with file from package fwupd-1.5.5-1.mga8.x86_64" [TRACKER] Packages that need to be obsoleted... https://bugs.mageia.org/show_bug.cgi?id=30163#c13 fwupdate, https://bugs.mageia.org/show_bug.cgi?id=28878#c3 Bug 28878 - Conflict between fwupdate-efi and grub2-common https://bugs.mageia.org/show_bug.cgi?id=28878 Conflict between fwupdate-efi and grub2-common [Note that these refer to 'fwupdate', which is obsoleted] https://bugs.mageia.org/show_bug.cgi?id=29061 fwupd: (null)/fwupdx64.efi cannot be found https://bugs.mageia.org/show_bug.cgi?id=30799 Conflicts while updating fwupd (In reply to Thomas Andrews from comment #1) > After I saw that an updated fwupd-efi had arrived at my mirror-of-choice, I > revisited this vbox guest and tried getting the updates again. This time > they were successful. This suggests that the problem is fixed. Assigning to tv who has the other two fwupd bugs. He may close this one 'fixed'. Summary:
M8->M9 Plasma upgrade attempt in VirtualBox fails, probably because of fwupd =>
M8->M9 Plasma upgrade attempt in VirtualBox fails, because of conflict between fwupd & fwupdx64-efi I restored the Vbox M8 guest, and tried the upgrade from the CI again. This time I did not see any problems that concerned fwupd, so that part, at least, appears to be fixed. I still saw script errors regarding several "php-pear" packages, and the boomaga error that we had when doing M7->M8 upgrades is still in effect. I don't see the point in rehashing the discussion about boomaga from bug 28419, since nothing has really changed. As for the php-pear script, that probably calls for a new bug. But that's a job for tomorrow. I see from the qa-discuss ML that we may soon have a new round of beta2 isos to test. I will wait for them and check all this out again. I've done several M8>M9 upgrades in the last few months, and this particular situation has been resolved. Closing the bug. Status:
NEW =>
RESOLVED |