Bug 1030944

Summary: package pulls python3 dependency even when installing python2 version
Product: [Fedora] Fedora Reporter: Xavier Queralt <xqueralt>
Component: python-keyringAssignee: Christopher Meng <i>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: dallan, i, rtnpro
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-keyring-3.3-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-04 06:59:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Xavier Queralt 2013-11-15 11:31:54 UTC
Description of problem:
python2 version of python-keyring package wrongly pulls python3 package because it is installing the python3 version of the keyring script instead of the python2 one.

Version-Release number of selected component (if applicable):
f19, f20, rawhide and probably f18

How reproducible:


Steps to Reproduce:
1. yum install python-keyring
2. rpm -q --requires python-keyring | grep python3
3. grep python3 /usr/bin/keyring

Actual results:


Expected results:


Additional info:
I think the problem comes from the installed keyring script, which is copied to python3-keyring instead of moving it in the %install section (I don't know the exact reason but it looks like the python2 version doesn't override it).

Comment 1 Christopher Meng 2013-11-15 11:39:57 UTC
I'm on CC because I want to take the package and maintain.

Nowdays with more and more python3 supports, we should also care about the binary generated by setup.py.

I just do such care in my package by:

1. First build py3 version

2. Move py3 version bin from xxx to xxx-py3version(now is xxx-3.3) 

3. Build py2 version

4. Handle them in %files.

This package just got rebirth so I hope Ratnadeep can maintain it well.

Comment 2 Fedora Update System 2013-12-03 06:09:42 UTC
python-keyring-3.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-keyring-3.3-1.fc19

Comment 3 Fedora Update System 2013-12-03 06:10:06 UTC
python-keyring-3.3-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/python-keyring-3.3-1.fc20

Comment 4 Fedora Update System 2013-12-03 18:21:39 UTC
Package python-keyring-3.3-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-keyring-3.3-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22644/python-keyring-3.3-1.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-12-04 06:59:38 UTC
python-keyring-3.3-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2013-12-14 03:35:19 UTC
python-keyring-3.3-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.