is there any plan/estimate of making python-cryptsetup compatible with Python 3? I'm currently trying to figure out what it'd take to move Fedora to Python 3 and since python-cryptsetup is one of Anaconda's deps, it'd need to be converted as one of the first.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
If you need any extra hand with this, feel free to use me :)
Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22.
From that perspective, your package is considered as IMPORTANT - that means, is has to be updated to Python 3, for our intention come true.
The goal here is, that at least for F22 you should provide python3- prefixed subpackage.
Please, help use update to Python 3 flawlessly.
Check if upstream already support Python 3, if yes, use it and add te 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, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option.
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.
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)
Note: do not follow this piece of advice as it is against the Packaging Guidelines: "When upstream is dead or unwilling to support Python 3, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option."
If you are in this situation, you'll essentially be forking upstream in order to produce a python3 port. In that situation, the proper thing to do is to create a new package with the python3 port. It would be even better to create the proper upstream infrastructure as well (new upstream scm and issue tracker) but that isn't 100% required by the guidelines.
Package is dead (#999215). Reassigning to cryptsetup.
Ok, so someone finally found the proper package (just 7 months, it is getting better!)
But now without sarcasm...
For years, there is cryptsetup-python which is part of cryptsetup upstream, this package also provide python-cryptsetup "provide". Old separate packege is dead (I included it in upstream and polished it, so they provide the same functionality).
If anyone have patches for python3 issues, please send it to me or attach them here.
I see no problem (except lack of time) to add another python3 subpackage (if build system is ready). Will check it later.
Just note: cryptsetup python binging is not complete - it was designed only for Anaconda use. But I think it is not problem for now.
Required Python3 changes are upstream now, once 1.6.5 release is out, I'll add cryptsetup-python3 subpackage to build.
Added cryptsetup-python3 subpackage in cryptsetup-1.6.5-1.fc21, please test it.