Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1024809 - createrepo_c: Use Python 3 instead of Python 2
Summary: createrepo_c: Use Python 3 instead of Python 2
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: createrepo_c
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mlcoch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: PY3DNF
Blocks: PY3PACKAGER PYTHON3
TreeView+ depends on / blocked
 
Reported: 2013-10-30 13:21 UTC by Miro Hrončok
Modified: 2016-01-05 15:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-05 15:47:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2013-10-30 13:21:04 UTC
Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22.

https://fedoraproject.org/wiki/Changes/Python_3_as_Default

While this package is not in minimal buildroot, it belongs to fedora-packager stack. We would like to switch to Python 3 there as well.

The goal here is, that for F22 you should use Python 3 instead of Python 2 in this package.

Please, help us update to Python 3 flawlessly.

Check if upstream already support Python 3, if yes, use it and add the support to the package.

If upstream doesn't support Python 3 yet, encourage it to do so by sending patches and offering your help.

When upstream is dead or unwilling to support Python 3, say so and we can solve the problem together.

Chances are, that you ARE the upstream. In that case, everything is easier, just do it yourself.

There is a table on wiki, that should list your package. Chances are, that you can see an upstream link that covers the problem. Anyway, please update the table with information you know.

https://fedoraproject.org/wiki/User:Churchyard/python3#fedora-packager

I offer my help with this task, so if you have no idea, how to work on this, or it is just not your priority, don't hesitate to ask for help.

(As you've already realized, this is a bulk text, so if something is not quite exact about your package, sorry for that, just ask)

Comment 1 Jan Zeleny 2013-10-30 13:30:52 UTC
Note that createrepo_c will be the default in F22 (or at least we are working towards that goal). Createrepo shares some parts of code with yum itself, not sure how easy would be to migrate that codebase.

Comment 2 Miro Hrončok 2013-10-30 13:45:00 UTC
So should we close this?

Comment 3 Jan Zeleny 2013-10-30 13:51:50 UTC
Let's keep this open for tracking purposes, there are still some uncertainties with createrepo_c. Once we are 100% sure it will make it to F22, we can close this one.

Comment 4 Jaroslav Reznik 2015-03-03 15:10:23 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 5 Robert Kuska 2015-06-02 08:09:31 UTC
What is the status with createrepo_c please?

Comment 6 Jan Zeleny 2015-06-02 08:47:08 UTC
Forwarding to Tomas Mlcoch who is the main developer. I believe everything works in createrepo_c except for delta rpms ...

Comment 7 Tomas Mlcoch 2015-06-02 11:08:39 UTC
This is a first time I see this bug. Well, createrepo_c doesn't support python 3 now, but it shouldn't be a big deal to implement this. I'll put this into my backlog.

Comment 8 Robert Kuska 2015-11-27 10:44:55 UTC
Shouldn't this be switched to createrepo_c?

Comment 9 Tomas Mlcoch 2016-01-05 15:47:59 UTC
Rawhide build of createrepo_c with Python 3 support is available:

http://koji.fedoraproject.org/koji/taskinfo?taskID=12419979


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