Bug 679544

Summary:	pip install using @rev fails, defaults to master
Product:	[Fedora] Fedora	Reporter:	Brian LaMere <brianlamere>
Component:	python-pip	Assignee:	Tim Flink <tflink>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14	CC:	phalliday
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-pip-0.8.3-1.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-12 22:04:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Brian LaMere 2011-02-22 19:59:35 UTC

Description of problem:

According to the pip documentation, "You can also include @rev in the URL, e.g., @275 to check out revision 275."
http://pypi.python.org/pypi/pip

However, when using python-pip as installed with Fedora14, using @rev is ignored, which defaults to master.

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



How reproducible:

100%

Steps to Reproduce:
1. pip install -e blah@blah:thing@place@rev#egg=eggname
2. check log - pulled master, not the version requested
3.
  
Actual results:

Pulled from master (@rev ignored)

Expected results:

pulled @rev requested

Additional info:

in so much as it is just pip, it's actually a very important part of our installation process for sites.  It dramatically deviates from what it is supposed to do, and worse - instead of failing, it does something *different* than what was requested.  This is Very Bad imo.  @rev was working by 0.8, I'm pretty sure?

Comment 1 Brian LaMere 2011-02-22 20:01:16 UTC

I do have a real example of what I did and what I got back, I'll scrub stuff and send it back if desired.  In the end, it's just an attempt to use @rev, and that's easy enough for anyone to duplicate.

Comment 2 Fedora Admin XMLRPC Client 2011-06-22 18:09:03 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2011-06-22 18:10:10 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Tim Flink 2011-06-24 16:38:01 UTC

This appears to be the same as upstream bug #78 https://github.com/pypa/pip/issues/78 (#138 in their old system) which was fixed with 0.8.1

I was able to reproduce using 0.8 and verify that 0.8.3 fixes the issue in my tests.

I am submitting 0.8.3 as an update. Could you verify the fix on your system?

Comment 5 Fedora Update System 2011-06-24 16:38:34 UTC

python-pip-0.8.3-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/python-pip-0.8.3-1.fc14

Comment 6 Fedora Update System 2011-06-25 19:57:07 UTC

Package python-pip-0.8.3-1.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-pip-0.8.3-1.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/python-pip-0.8.3-1.fc14
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-07-12 22:04:34 UTC

python-pip-0.8.3-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.