Bug 1180935

Summary: Python3 module
Product: [Fedora] Fedora Reporter: secondary
Component: pylibaclAssignee: Marcin Zajaczkowski <mszpak>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: erinn.looneytriggs, mszpak, pviktori
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pylibacl-0.5.2-1.fc23 pylibacl-0.5.2-1.fc24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-07 01:25:28 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1285816    
Attachments:
Description Flags
updated source rpm
none
updated source rpm none

Description secondary 2015-01-11 23:30:40 UTC
Description of problem:
No python 3 package is built.


Version-Release number of selected component (if applicable):
See [http://pkgs.fedoraproject.org/cgit/pylibacl.git/tree/pylibacl.spec]


Additional info:
I took a look at the debian package: no additional work is required to support python3. Just call setup.py with the python3 interpreter.

Comment 1 secondary 2015-01-12 17:17:30 UTC
I'll upload an updated spec today.

Comment 2 secondary 2015-01-12 18:44:06 UTC
Created attachment 979269 [details]
updated source rpm

Comment 3 secondary 2015-01-12 18:46:13 UTC
Tested working for both python-2 and python-3.

Comment 4 secondary 2015-01-12 18:50:02 UTC
Created attachment 979270 [details]
updated source rpm

Changelog:
- updated to 0.5.2
- phase out python-libacl (it's been a while...)
- run checks
- python3 subpackage
- remove outdated macros

Comment 5 Jaroslav Reznik 2015-03-03 16:41:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 6 Petr Viktorin (pviktori) 2016-04-19 12:36:49 UTC
Marcin, did you get time to look at the update?

Comment 7 Fedora Update System 2016-05-02 20:22:16 UTC
pylibacl-0.5.2-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7ff5bf5e72

Comment 8 Fedora Update System 2016-05-02 20:22:22 UTC
pylibacl-0.5.2-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-40135143a3

Comment 9 Marcin Zajaczkowski 2016-05-02 20:26:46 UTC
Thanks Petr for the reminder. I applied the changes and issued updates for F23 and F24. Unfortunately I don't use anything what can be built against the new Python 3 module. Feel free to test it if you use one.

Thanks Yclept for the patch! :).

Comment 10 Fedora Update System 2016-05-03 11:23:13 UTC
pylibacl-0.5.2-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7ff5bf5e72

Comment 11 Fedora Update System 2016-05-13 05:32:46 UTC
pylibacl-0.5.2-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-40135143a3

Comment 12 Fedora Update System 2016-06-07 01:25:26 UTC
pylibacl-0.5.2-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2016-06-18 19:01:24 UTC
pylibacl-0.5.2-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.