Bug 1174283 - Current master of nectar requires a newer version of python-requests
Summary: Current master of nectar requires a newer version of python-requests
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: rel-eng
Version: Master
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.6.0
Assignee: amacdona@redhat.com
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 14:54 UTC by Barnaby Court
Modified: 2015-02-28 22:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:46:55 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 640 0 None None None Never

Description Barnaby Court 2014-12-15 14:54:29 UTC
Description: 
The current master branch of nectar will fail if run against python-requests 2.2.1.  The dependency in pulp & nectar should be updated or the threaded downloader should be updated to not use the new python-requests api.

Comment 1 amacdona@redhat.com 2014-12-19 20:16:17 UTC
Barnaby, Pulp 2.6 is bundled with python-requests-2.4.3, so this should not be an issue.

Please reopen if I am incorrect.

Comment 2 amacdona@redhat.com 2014-12-19 20:31:15 UTC
https://github.com/pulp/nectar/pull/26

I see that the problem was not the built dependencies, rather the requires statement in the spec. I think that we should require at least the version that we provide.

Comment 3 Chris Duryee 2014-12-23 20:52:27 UTC
fixed in pulp 2.6.0-0.2.beta

Comment 4 Irina Gulina 2015-01-05 13:29:35 UTC
Failed QA


>> rpm -q pulp-server
pulp-server-2.6.0-0.2.beta.fc20.noarch

>>rpm -qR python-nectar | grep python-requests
python-requests >= 2.2.1

Comment 5 amacdona@redhat.com 2015-01-06 15:27:52 UTC
This was fixed in the nectar spec file, but not in the pulp copy of the same spec file. Fixed here:

https://github.com/pulp/pulp/pull/1482

Comment 6 Randy Barlow 2015-01-06 21:22:30 UTC
I don't think it is necessary for the Pulp package to also require python-requests >= 2.4, unless Pulp is actually using those features. AIUI, only nectar is using the newer features, so it was correct for Pulp to continue to require >= 2.2. That is, unless someone is aware of something Pulp is doing with python-requests that really does need 2.4. I know of no such usage.

Comment 7 amacdona@redhat.com 2015-01-08 15:14:54 UTC
Randy and I talked about this, it is appropriate to change this spec file to match that of the nectar repo.

Comment 8 Randy Barlow 2015-01-08 18:11:40 UTC
My comment was due to a mistake in my interpretation of the details. Carry on!

Comment 9 Chris Duryee 2015-01-15 00:28:32 UTC
This was merged to 2.6-dev (2.6.1) , not 2.6-testing (2.6.0).

If you'd like it in 2.6.0, please open a new PR against 2.6-testing and set the bug's target release to 2.6.0.

Comment 10 Chris Duryee 2015-01-16 23:00:00 UTC
pulp 2.6.0 beta 5

Comment 11 Irina Gulina 2015-01-19 09:42:23 UTC
Do I miss something or it failed QA again?

>> rpm -qa pulp-server
pulp-server-2.6.0-0.5.beta.el6.noarch

>> rpm -qR python-nectar | grep python-requests
python-requests >= 2.2.1

Comment 12 amacdona@redhat.com 2015-01-19 15:02:30 UTC
The code appears to be correct, but the build date for the nectar dep does not. Cracking open the rpm:

Build Date  : Thu 21 Aug 2014 02:28:03 PM EDT

Chris, I think that the deps were not rebuilt in this build?

Comment 13 Chris Duryee 2015-01-19 17:14:34 UTC
Try now:)

python-nectar 1.3.1-2 should fix this. The fix was in the src tree before but the newer nectar was not tagged.

Comment 14 Irina Gulina 2015-01-22 13:28:24 UTC
>> rpm -qa pulp-server
pulp-server-2.6.0-0.5.beta.el6.noarch

>> rpm -qa python-nectar
python-nectar-1.3.1-2.el6.noarch

>> rpm -qR python-nectar | grep python-requests
python-requests >= 2.4.3

Comment 15 Brian Bouterse 2015-02-28 22:46:55 UTC
Moved to https://pulp.plan.io/issues/640


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