Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 616626 - python-pip pkg conflict with perl-pip
python-pip pkg conflict with perl-pip
Product: Fedora
Classification: Fedora
Component: perl-pip (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
Fedora Extras Quality Assurance
Depends On: 616399
  Show dependency treegraph
Reported: 2010-07-20 21:44 EDT by Adam Stokes
Modified: 2010-08-04 04:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 616399
Last Closed: 2010-08-04 04:21:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
CPAN 59589 None None None Never

  None (edit)
Description Adam Stokes 2010-07-20 21:44:54 EDT
+++ This bug was initially created as a clone of Bug #616399 +++

Description of problem:
Attempting to do a wildcard install of both python and perl packages results a file conflict for both python-pip and perl-pip

Version-Release number of selected component (if applicable):
python-pip 0.6.3-1 & perl-pip 1.16-1

How reproducible:

Steps to Reproduce:
1. yum install python* perl*
Actual results:
Running Transaction Test

Transaction Check Error:
  file /usr/bin/pip conflicts between attempted installs of python-pip-0.6.3-1.fc13.noarch and perl-pip-1.16-1.fc13.noarch

Expected results:
No conflicts

Additional info:

--- Additional comment from phalliday@excelsiorsystems.net on 2010-07-20 14:26:35 EDT ---

Well, I think the Debian approach (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551926) should be done here.  Both packages should have to rename their /usr/bin/pip.  Something like /usr/bin/pip-perl and /usr/bin/pip-python.  That way completion will work at least.
Comment 1 Marcela Mašláňová 2010-07-21 03:11:09 EDT
Thanks for your bug report. I've created bug report in upstream as stated in our guidelines [1]. Let's wait for a while for their opinion.

[1] https://fedoraproject.org/wiki/Packaging:Conflicts#Binary_Name_Conflicts
Comment 2 Bug Zapper 2010-07-30 08:43:08 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
Comment 3 Marcela Mašláňová 2010-08-03 08:20:46 EDT
No reply from upstream yet and also python pip wasn't still fixed.
Comment 4 Peter Halliday 2010-08-03 09:32:38 EDT
I haven't fixed this yet, because I'm waiting to hear what was going to happen with the perl-pip.  I doubt they will change, because both parties upstream had this "battle" debian.  And the packages had to rename them to pip-perl and pip-python, because neither would change their name.  I certainly am willing to make the changes, but I want to make sure both were planned to be changed.
Comment 5 Marcela Mašláňová 2010-08-04 04:21:27 EDT
Ok, I read the whole fight about who was here first with pip... It's ridiculous. 

Let's both change it to python-pip and perl-pip for rawhide. In my case only perl-Padre is using pip and it looks to be working even after rename.

Build with fix:

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