Bug 2187642 - Failure to upgrade libomp from F37 to F38 due to multilib
Summary: Failure to upgrade libomp from F37 to F38 due to multilib
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libomp
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tulio Magno Quites Machado Filho
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-18 09:44 UTC by Elliott Sales de Andrade
Modified: 2024-03-26 20:33 UTC (History)
6 users (show)

Fixed In Version: libomp-16.0.1-2.fc39 libomp-16.0.1-3.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-19 21:07:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Elliott Sales de Andrade 2023-04-18 09:44:07 UTC
Attempting a system upgrade from F37 to F38 results in a conflict from missing multilib for libomp.


Reproducible: Always

Steps to Reproduce:
1. Start with F37 with libomp (x86_64+i686) installed
2. Run upgrade from test email `sudo dnf --releasever=38 --setopt=module_platform_id=platform:f38 --enablerepo=updates-testing $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) --assumeno distro-sync`
Actual Results:  
The following error occurs:

 Problem 2: libomp-15.0.7-1.fc37.i686 has inferior architecture
  - libomp-15.0.7-1.fc37.x86_64 does not belong to a distupgrade repository
  - problem with installed package libomp-15.0.7-1.fc37.i686

Expected Results:  
No conflicts or transaction errors during upgrade.

Checking F37 [1] shows an x86_64 and i686 package for libomp and libomp-devel.
Checking F38 [2] shows both architectures for _only_ libomp-devel.

Perhaps it is related to this loss of a shared library [3]?

[1] https://dl.fedoraproject.org/pub/fedora/linux/releases/37/Everything/x86_64/os/Packages/l/
[2] https://dl.fedoraproject.org/pub/fedora/linux/development/38/Everything/x86_64/os/Packages/l/
[3] https://src.fedoraproject.org/rpms/libomp/c/7b0c6905ecfc2251e2dfd86e566042311c42aa45?branch=rawhide

Comment 1 Tulio Magno Quites Machado Filho 2023-04-18 11:54:08 UTC
This is related to this upstream change [1].

Elliott, are there any packages requiring libomp.i686 in your system?

[1] https://reviews.llvm.org/D142023

Comment 2 Tulio Magno Quites Machado Filho 2023-04-18 14:11:49 UTC
We've identified that libomp-devel.i686 stopped depending on libomp.i686 and we believe this could be causing i686 package to not be included in the x86_64 multilib repository.
I'm working on a fix.

Comment 3 Fedora Update System 2023-04-18 14:44:09 UTC
FEDORA-2023-bd0b7a43b6 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-bd0b7a43b6

Comment 4 Fedora Update System 2023-04-18 14:49:06 UTC
FEDORA-2023-bd0b7a43b6 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Elliott Sales de Andrade 2023-04-18 19:54:10 UTC
This needs fixing on F38 as well, to fix upgrades.

(In reply to Tulio Magno Quites Machado Filho from comment #1)
> Elliott, are there any packages requiring libomp.i686 in your system?

On F37, yes, libomp-devel does. On F38, I don't know as I haven't upgraded yet.

Comment 6 Tulio Magno Quites Machado Filho 2023-04-19 13:21:23 UTC
In the end, the changes to Rawhide didn't work.

I reported the following issue to releng: https://pagure.io/releng/issue/11395
There is a chance this could be related to how multilib packages are being chosen.

Comment 7 Fedora Update System 2023-04-19 21:00:22 UTC
FEDORA-2023-7d5643bcbb has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7d5643bcbb

Comment 8 Fedora Update System 2023-04-19 21:07:07 UTC
FEDORA-2023-7d5643bcbb has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-04-19 21:16:45 UTC
FEDORA-2023-36b95f852a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-36b95f852a

Comment 10 Tulio Magno Quites Machado Filho 2023-04-19 21:19:05 UTC
I we have on-going fixes in place for both Fedora 38 and Rawhide.
I will continue to monitor if libomp.i686 is pushed to both x86_64 repositories.

Comment 11 Fedora Update System 2023-04-20 04:29:26 UTC
FEDORA-2023-36b95f852a has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-36b95f852a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-36b95f852a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Tulio Magno Quites Machado Filho 2023-04-20 12:14:27 UTC
I've just confirmed that libomp-16.0.1-3.fc39.i686 did land in the rawhide repository.

While the F38 update is in testing, we can already confirm the following command is not failing anymore:

    dnf --releasever=38 --setopt=module_platform_id=platform:f38 --enablerepo=updates-testing $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) --assumeno distro-sync

But we'll only be sure of the fix after the package lands in the stable repository in 2 weeks.

Comment 13 Fedora Update System 2023-04-25 01:53:17 UTC
FEDORA-2023-36b95f852a has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2024-03-26 20:28:39 UTC
FEDORA-2024-71d5ea5db1 (libomp17-17.0.6-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-71d5ea5db1

Comment 15 Fedora Update System 2024-03-26 20:33:28 UTC
FEDORA-2024-71d5ea5db1 (libomp17-17.0.6-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.