Bug 1320654 - cracklib: Provide a Python 3 subpackage
Summary: cracklib: Provide a Python 3 subpackage
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cracklib
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3
TreeView+ depends on / blocked
 
Reported: 2016-03-23 17:21 UTC by Tomas Orsava
Modified: 2019-11-12 08:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-04 09:30:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Scaffolding for Python 3 support. Not a complete patch. (3.51 KB, application/mbox)
2016-04-29 16:15 UTC, Tomas Orsava
no flags Details

Description Tomas Orsava 2016-03-23 17:21:38 UTC
Upstream, this software supports Python 3. Please provide a Python 3
package for Fedora.


According to the Python packaging guidelines [0], software must be
packaged for Python 3 if upstream supports it.
The guidelines give detailed information on how to do this, and even
provide an example spec file [1].

The current best practice is to provide subpackages for the two Python
versions (called "Common SRPM" in the guidelines). Alternatively, if
nothing depends on your Python2 package, you can just switch to Python 3
entirely.

It's ok to do this in Rawhide only, however, it would be greatly
appreciated if you could push it to Fedora 24 as well.


If anything is unclear, or if you need any kind of assistance with the
porting, you can ask on IRC (#fedora-python on Freenode), or reply here.
We'll be happy to help!


[0] https://fedoraproject.org/wiki/Packaging:Python
[1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file

Comment 1 Dominika Krejčí 2016-04-22 11:07:57 UTC
Hello Tomas,

Do you need any help adding Python 3 support to the RPM?

If you need more instructions, a [guide] for porting Python-based RPMs is available.

[guide] http://python-rpm-porting.readthedocs.org/en/latest/index.html

Comment 2 Tomas Mraz 2016-04-22 11:37:22 UTC
If you provided at least some preliminary patch to work on, it would be nice. I am currently very busy with other work.

Comment 3 Dominika Krejčí 2016-04-27 13:28:27 UTC
I will do the patch, but there are some obstacles:
There is a reference of Source10: missing-words.gz in the specfile, but the file is missing from dist-git. Could you please include it?

Comment 4 Dominika Krejčí 2016-04-27 13:33:06 UTC
Sorry, I've found it among the sources.

Comment 5 Tomas Orsava 2016-04-29 16:15:39 UTC
Created attachment 1152349 [details]
Scaffolding for Python 3 support. Not a complete patch.

Hi Tomas,
Dominika and I took a crack at it, but were unfortunately unable to fully port the spec file.

Therefore, I have at least attached a patch that creates the scaffolding necessary for a new python3 subpackage. What is missing is actually generating the files for the Python 3 package.

What might help you is looking at how Python 3 packages are generated for Debian, as you can see the Debian "spec file equivalent" in the unpacked tarball with the sources. You can find it at: cracklib-2.9.6/debian/rules.

Thank you for your time.

Comment 6 Dominika Krejčí 2016-10-07 08:28:09 UTC
Hello Tomas,
any progress with our partial patch?

Comment 7 Tomas Mraz 2016-10-07 08:49:57 UTC
Unfortunately I am very busy with other things. But I'll try to look at it soon.

Comment 8 Tomas Mraz 2018-03-22 08:18:17 UTC
I think the best way would be to drop the Python support from cracklib completely. There is only one package (revelation) that currently depends on it according to:
http://fedora.portingdb.xyz/pkg/cracklib/
And the revelation looks like a package with dead upstream.

Comment 9 nvwarr 2019-11-12 07:48:33 UTC
system-config-rootpassword also depends on python2-cracklib and is now broken.

Comment 10 Tomas Mraz 2019-11-12 08:25:44 UTC
It has to be fixed to use python3-pwquality instead.


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