Bug 2017661 - Conflict when upgrading F34 -> F35
Summary: Conflict when upgrading F34 -> F35
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-qt5-qtbase
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-27 07:07 UTC by Joachim Backes
Modified: 2021-11-14 04:07 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-14 04:07:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2021-10-27 07:07:32 UTC
Description of problem:

'm trying to test an upgrade from F34 to F35, but the step

*sudo dnf system-upgrade download --releasever=35 --best
--skip-broken --allowerasing*

fails with the message

*file /usr/lib64/libQt5Bootstrap.prl conflicts between attempted 
installs of qt5-qtbase-static-5.15.2-22.fc35.x86_64 and 
mingw64-qt5-qtbase-devel-5.15.2-5.fc35.x86_64*

Version-Release number of selected component (if applicable):
F35

How reproducible:
Each time

Steps to Reproduce:
sudo dnf distro-sync
sudo dnf upgrade --refresh 
sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-35-primary1
sudo dnf system-upgrade download --releasever=35 --best --skip-broken --allowerasing


Actual results:

see above
Expected results:

download is achieved
Additional info:

Comment 1 Marek Blaha 2021-11-02 07:24:48 UTC
Hi, file conflicts are not something dnf can solve, they usually signalize some packaging problems. Let's reassign this to qt5-qtbase component for further investigation.

Comment 2 Than Ngo 2021-11-02 07:57:33 UTC
it looks like libQt5Bootstrap.prl was added in mingw-qt5-qtbase in f35. In f34 it's not included in mingw-qt5-qtbase

Comment 3 Sandro Mani 2021-11-02 08:15:55 UTC
Is there point in shipping

%{_libdir}/libQt5Bootstrap.a
%{_libdir}/libQt5Bootstrap.la
%{_libdir}/libQt5Bootstrap.prl

in qt5-qtbase-static? libQt5Bootstrap.so is used by the cross host tools under /usr/%{mingw32/64}_target}/bin/qt5, no use of libQt5Bootstrap for native packages AFAIK.

Comment 4 Rex Dieter 2021-11-02 15:44:16 UTC
If we're sure libQt5Bootstrap is only needed for mingw64-qt5-qtbase and not core qt5-qtbase, then I'm ok with omitting it from the latter to resolve this.

Comment 5 Sandro Mani 2021-11-02 15:57:03 UTC
Qt5Bootstrap is a selected minimal subset of Qt5 sufficient for just running host the toolchain tools (moc, qmake, ...). The tools of the native packages clearly just link to the full libraries instead. (In Qt6, it was actually removed, and cross-builds don't build any host tools anymore, relying on pre-existing ones from a native build instead.)

Comment 6 Sandro Mani 2021-11-11 10:54:51 UTC
I've opened this PR: https://src.fedoraproject.org/rpms/qt5-qtbase/pull-request/7

Comment 7 Fedora Update System 2021-11-11 15:52:50 UTC
FEDORA-2021-2d4da0c977 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2d4da0c977

Comment 8 Fedora Update System 2021-11-12 01:02:49 UTC
FEDORA-2021-2d4da0c977 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2d4da0c977`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2d4da0c977

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

Comment 9 Joachim Backes 2021-11-12 09:49:00 UTC
I'm running FC35 since about 2 weeks after having uninstalled qtbase-static. So far, so good.
But after upgrade, two packages are re-installed:

mingw64-qt5-qtbase-static-5.15.2-5.fc35.noarch
mingw32-qt5-qtbase-static-5.15.2-5.fc35.noarch

Comment 10 Fedora Update System 2021-11-14 04:07:31 UTC
FEDORA-2021-2d4da0c977 has been pushed to the Fedora 35 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.