Hi, Error: Transaction check error: file /boot/efi/EFI/fedora from install of grub2-common-1:2.02-22.fc28.noarch conflicts with file from package fwupdate-efi-10-1.fc28.x86_64 file /boot/efi/EFI/fedora from install of grub2-efi-x64-1:2.02-22.fc28.x86_64 conflicts with file from package fwupdate-efi-10-1.fc28.x86_64 file /boot/efi/EFI/fedora from install of grub2-efi-ia32-1:2.02-22.fc28.x86_64 conflicts with file from package fwupdate-efi-10-1.fc28.x86_64 file /boot/efi/EFI/fedora/fonts conflicts between attempted installs of grub2-efi-x64-cdboot-1:2.02-22.fc28.x86_64 and grub2-efi-ia32-1:2.02-22.fc28.x86_64 file /boot/efi/EFI/fedora/fonts/unicode.pf2 conflicts between attempted installs of grub2-efi-x64-cdboot-1:2.02-22.fc28.x86_64 and grub2-efi-ia32-1:2.02-22.fc28.x86_64
Seeing this (at least one case of it) in F26 Workstation -> F28 (rawhide) i686 upgrade test in openQA currently: https://openqa.fedoraproject.org/tests/190849#step/upgrade_run/13 file /boot/efi/EFI/fedora from install of grub2-common-1:2.02-24.fc28.noarch conflicts with file from package fwupdate-efi-8-4.fc26.i686
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
I experienced a similar failure when upgrading from F27 Workstation (32-bit) to F28 Workstation. Error: transaction check error file /boot/efi/EFI/fedora from install of grub2-common-1:2.02-34.fc28.noarch conflicts with file from package fwupdate-efi-8-4.fc26.i686 This happened on a 2003 (15-year old) Dell desktop PC that is 32-bit only and does not support an efi bios. (I use this PC for backups). Is there a workaround so that I can finish the upgrade?
Removing fwupdate-efi should be safe, I believe.
I have this error when going from 27 Workstation to 28 Workstation Error: Transaction check error: file /boot/efi/EFI/fedora from install of grub2-common-1:2.02-34.fc28.noarch conflicts with file from package fwupdate-efi-8-4.fc26.i686 root can not access it to delete the older one.
(In reply to Murray from comment #5) > I have this error when going from 27 Workstation to 28 Workstation > Error: Transaction check error: > file /boot/efi/EFI/fedora from install of > grub2-common-1:2.02-34.fc28.noarch conflicts with file from package > fwupdate-efi-8-4.fc26.i686 > > root can not access it to delete the older one. How there been any update to this bug because I received the same. I am using a 32 bit, 11-year-old Dell Inspiron E1505 laptop running Fedora 27. Did anyone try Adams' workaround? I had the same issue last year when upgrading to Fedora 27 however the solution from last year is not working this year. Please advise?
(In reply to Ed from comment #6) > (In reply to Murray from comment #5) > > I have this error when going from 27 Workstation to 28 Workstation > > Error: Transaction check error: > > file /boot/efi/EFI/fedora from install of > > grub2-common-1:2.02-34.fc28.noarch conflicts with file from package > > fwupdate-efi-8-4.fc26.i686 > > > > root can not access it to delete the older one. > > How there been any update to this bug because I received the same. I am > using a 32 bit, 11-year-old Dell Inspiron E1505 laptop running Fedora 27. > Did anyone try Adams' workaround? I had the same issue last year when > upgrading to Fedora 27 however the solution from last year is not working > this year. Please advise? I removed fwupdate-libs-8-4.fc26.i686 and fwupdate-efi-8-4.fc26.i686 and grub2-efi received the same error message.
(In reply to Ed from comment #7) > (In reply to Ed from comment #6) > > (In reply to Murray from comment #5) > > > I have this error when going from 27 Workstation to 28 Workstation > > > Error: Transaction check error: > > > file /boot/efi/EFI/fedora from install of > > > grub2-common-1:2.02-34.fc28.noarch conflicts with file from package > > > fwupdate-efi-8-4.fc26.i686 > > > > > > root can not access it to delete the older one. > > > > How there been any update to this bug because I received the same. I am > > using a 32 bit, 11-year-old Dell Inspiron E1505 laptop running Fedora 27. > > Did anyone try Adams' workaround? I had the same issue last year when > > upgrading to Fedora 27 however the solution from last year is not working > > this year. Please advise? > > I removed fwupdate-libs-8-4.fc26.i686 and fwupdate-efi-8-4.fc26.i686 > and grub2-efi received the same error message. I removed fwupdate-efi-8-4.fc26.i686 (using dnf remove) and the F27 -> F28 upgrade then completed successfully.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.