Bug 2266779 - Transaction test error due to conflicts between kuserfeedback-6.0.0-1.fc40.x86_64 and kf6-kuserfeedback-6.0.0-1.fc40.x86_64
Summary: Transaction test error due to conflicts between kuserfeedback-6.0.0-1.fc40.x8...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kuserfeedback
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Yaroslav Sidlovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-29 02:00 UTC by Matt Fagnani
Modified: 2024-03-03 10:19 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-03-03 10:19:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Fagnani 2024-02-29 02:00:10 UTC
I ran sudo dnf offline-upgrade download with updates-testing enabled in Plasma 6.0.0 in a Fedora 40 KDE Plasma installation. kuserfeedback-6.0.0-1.fc40.x86_64 was in the updates. A transaction test error was shown due to conflicts between kuserfeedback-6.0.0-1.fc40.x86_64 and kf6-kuserfeedback-6.0.0-1.fc40.x86_64

Error: Transaction test error:
  file /usr/lib64/libKF6UserFeedbackCore.so.6.0.0 from install of kuserfeedback-6.0.0-1.fc40.x86_64 conflicts with file from package kf6-kuserfeedback-6.0.0-1.fc40.x86_64
  file /usr/lib64/libKF6UserFeedbackWidgets.so.6.0.0 from install of kuserfeedback-6.0.0-1.fc40.x86_64 conflicts with file from package kf6-kuserfeedback-6.0.0-1.fc40.x86_64
  file /usr/lib64/qt6/qml/org/kde/userfeedback/libKF6UserFeedbackQml.so from install of kuserfeedback-6.0.0-1.fc40.x86_64 conflicts with file from package kf6-kuserfeedback-6.0.0-1.fc40.x86_64

Reproducible: Didn't try

Steps to Reproduce:
1. Boot a Fedora 40 KDE Plasma installation
2. Log in to Plasma 6.0.0 on Wayland
3. Start Konsole
4. sudo dnf offline-upgrade download with updates-testing enabled. kuserfeedback-6.0.0-1.fc40.x86_64 must be in the updates.

Actual Results:  
Transaction test error due to conflicts between kuserfeedback-6.0.0-1.fc40.x86_64 and kf6-kuserfeedback-6.0.0-1.fc40.x86_64

Expected Results:  
No errors should have been shown.

Comment 1 Matt Fagnani 2024-02-29 06:08:37 UTC
https://src.fedoraproject.org/rpms/kuserfeedback has the upstream link https://invent.kde.org/libraries/kuserfeedback which shows "Project 'libraries/kuserfeedback' was moved to 'frameworks/kuserfeedback'. Please update any links and bookmarks that may still have the old path." So kuserfeedback and kf6-kuserfeedback might be packaging the same thing. kf6-kuserfeedback could obsolete kuserfeedback to fix this problem.

Comment 2 Yaroslav Sidlovsky 2024-02-29 08:17:40 UTC
Just ridiculous.
No one from KDE SIG group tries to contact me about this situation.
And no one checks that they cloned package that I've been maintaining for a while.

It's event described in "Package Maintainers" guide:
https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/#check
(Check if the package already exists)

Comment 3 Yaroslav Sidlovsky 2024-02-29 08:26:45 UTC
I'll wait for instructions what I need to do now.

Comment 4 Yaroslav Sidlovsky 2024-02-29 08:33:30 UTC
Update unpushed. But there was warning about Fedora 40 freeze:
```
This update will not be pushed to stable until freeze is lifted from Fedora 40. 
```

Comment 5 Alessandro Astone 2024-02-29 13:24:59 UTC
It is not a clone. We as KDE-SIG packaged the KF6 version of kuserfeedback under the common `kf6-` prefix.
Your package should still be maintained as it is the KF5 version of kuserfeedback (back to when it was not a kde "framework").

`repoquery` tells me that `LabPlot` is still using KF5 kuserfeedback, so you should not have tried to upgrade it to KF6 anyways.

Comment 6 Alessandro Astone 2024-02-29 13:35:52 UTC
https://src.fedoraproject.org/rpms/kuserfeedback/c/7d3cf191dfd5ecd9353d7d911bf7579225e62c5a?branch=rawhide
I even contributed to your package by making sure that it can coexist with the kf6 variant, so obviously we were aware.
But I suppose I could have notified you directly.

Comment 7 Matt Fagnani 2024-03-01 10:14:27 UTC
Thanks. I noticed that the kuserfeedback 6.0.0 change was reverted in rawhide https://src.fedoraproject.org/rpms/kuserfeedback/c/2cf33b99f47b9552ad4b63643385d6726799838e?branch=rawhide Adding an epoch of 1 might be good since otherwise kuserfeedback-6.0.0-1.fc41 might remain in rawhide because it was in the rawhide 20240229.n.0 compose https://lists.fedoraproject.org/archives/list/test-reports@lists.fedoraproject.org/thread/GSAY6UTNSABL6QGRCM2ZQJQBMCHTJWZZ/ This problem was described by Adam Williamson at https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NU75E4KDJROIEYOT22N4Y7SBLUXSMXDI/#NU75E4KDJROIEYOT22N4Y7SBLUXSMXDI

Comment 8 Alessandro Astone 2024-03-01 10:30:34 UTC
It will not remain in rawhide, it would remain installed in people's PC's, but considering the update was not installable, it should not be an issue

Comment 9 Matt Fagnani 2024-03-01 12:05:28 UTC
I think that rawhide composes include the highest epoch-version-release for a package tagged as f41, so kuserfeedback won't be downgraded to 1.3.0 in future rawhide composes without adding an epoch of 1. Adam's message I mentioned describes the guidelines for this issue.

Comment 10 Alessandro Astone 2024-03-01 12:58:23 UTC
> I think that rawhide composes include the highest epoch-version-release for a package tagged as f41

We'll find out tomorrow, but i don't believe that is true.

Comment 11 Alessandro Astone 2024-03-03 10:19:13 UTC
You can see rawhide has `kuserfeedback-0:1.3.0-5.fc41`


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