Bug 1315025 - Packaging conflict between python-qt5 and python3-qt5
Summary: Packaging conflict between python-qt5 and python3-qt5
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-qt5
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-05 22:04 UTC by stan
Modified: 2016-03-07 19:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 14:09:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description stan 2016-03-05 22:04:45 UTC
Description of problem:
When upgrading python-qt5, I get a file conflict error from dnf.

Version-Release number of selected component (if applicable):
python-qt5-5.5.1-13.fc25.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.  Have python3-qt5 installed.
2.  Try to upgrade python-qt5
3.

Actual results:
file /usr/lib/rpm/macros.d/macros.pyqt5 from install of python-qt5-5.5.1-13.fc25.x86_64 conflicts with file from package python3-qt5-5.5.1-11.fc25.x86_64


Expected results:
Successful upgrade

Additional info:
---> Package python-qt5.x86_64 5.5.1-11.fc25 will be upgraded
---> Package python-qt5.x86_64 5.5.1-13.fc25 will be an upgrade

Comment 1 Rex Dieter 2016-03-07 14:09:06 UTC
you have to upgrade both python-qt5 and python3-qt5 at the same time.

Comment 2 stan 2016-03-07 19:01:15 UTC
Yeah, I was going to post information about that this morning after I noticed that the python3 packages aren't updating because of dependency errors.  Not sure what those errors are, though.

Here is the output from dnf.

Upgrading:                                                                                                                                                                                                                             python-qt5                                                     x86_64                                              5.5.1-14.fc25                                                  rawhide                                              3.9 M 

Skipping packages with broken dependencies:                                                                                                                                                                                                   
 python3-qt5                                                    x86_64                                              5.5.1-14.fc25                                                  rawhide                                              3.9 M
 python3-qt5-devel                                              x86_64                                              5.5.1-14.fc25                                                  rawhide                                              502 k


And if I accept this, then it gives me the error I reported.

Comment 3 Rex Dieter 2016-03-07 19:05:14 UTC
What does this say:

dnf update --best 

??

Comment 4 Rex Dieter 2016-03-07 19:08:31 UTC
and, if you happen to have an oddly named python3-webkit pkg installed, try removing it.

Comment 5 stan 2016-03-07 19:13:14 UTC
Thanks for that command.  That's really useful.

Here are the relevant entries from the output:

package python3-webengine-5.5.1-11.fc25.x86_64 requires python3-qt5(x86-64) = 5.5.1-11.fc25, but none of the providers can be installed.

package python3-webkit-5.5.1-11.fc25.x86_64 requires python3-qt5(x86-64) = 5.5.1-11.fc25, but none of the providers can be installed.

So, you're saying I should remove these?  They're obsolete?   Or do they just need their dependencies updated to the latest python3-qt5 version?

Comment 6 Rex Dieter 2016-03-07 19:24:41 UTC
Yes, remove those

Comment 7 Rex Dieter 2016-03-07 19:28:26 UTC
%changelog
* Mon Mar 07 2016 Rex Dieter <rdieter> 5.5.1-15
- add Obsoletes for misnamed -webengine/-webkit pkgs (#1315025)

Comment 8 stan 2016-03-07 19:30:02 UTC
That did the trick!

Thanks for your help.


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