Bug 1499615 - Please provide in EPEL also vobject based on python 3.4
Summary: Please provide in EPEL also vobject based on python 3.4
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-vobject
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Pierre-YvesChibon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-09 05:28 UTC by Peter Bieringer
Modified: 2020-01-05 13:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Bieringer 2017-10-09 05:28:48 UTC 
Description of problem:

currently, only python-vobject for python 2.x is provided, which cannot be used e.g. for "radicale", which is requiring to have python34 based vobject.

Please provide also a python34-vobject in parallel in EPEL7, thank you!
Comment 1 Pierre-YvesChibon 2017-10-09 06:38:00 UTC 
If someone wants to do it, I will review a pull-request for this but I won't have the time to work on this anytime soon.
Comment 2 Peter Bieringer 2017-10-09 19:31:37 UTC 
I can supply a diff to current FC27 spec, but I ran into backwards compatibility issues:

adjusted spec would create python2-vobject and python34-vobject, but at vobject version 0.9.4 requires dateutil >= 2.4.0, but for python2 on EL7, currently only 1.5 is available.

either it is possible to push only a python34-vobject 0.9.4 into EL7 repo while keeping 0.8.1 for python2

or

python(2)-dateutil must be updated first to >= 2.4.0
Note You need to log in before you can comment on or make changes to this bug.