Description of problem: I took the liberty of packaging python3-asn1 for Cauldron. If someone please could add it to the mirror, that'd be great. Version-Release number of selected component (if applicable): 2.6.0-6
Created attachment 14456 [details] Proposal spec file
CC: (none) => lovaren
Please give a project URL, and say a bit more about this.
Summary: {PACKAGE REQUEST} python3-asn1 is a simple ASN.1 encoder and decoder for Python => python3-asn1 :s a simple ASN.1 encoder and decoder for Python {PACKAGE REQUEST}CC: (none) => lewyssmith
URL: (none) => https://pypi.org/project/asn1/
This package should not be mistaken for python-pyasn1 even though the usage is about the same subject.
python3-asn1 Is an unmaintained fork from the also unmaintained python-asn1
(In reply to sturmvogel from comment #4) > python3-asn1 Is an unmaintained fork from the also unmaintained python-asn1 And Fedora still uses it nevertheless. Just saying.
Introducing a dead package into Mageia because Fedora uses it as the last rpm based distribution. That isn‘t a valid argument.
The URL is for Python-ASN1; I found nothing for 'python3-asn1'. My search for 'python3-asn1' came back 'Did you mean: python-asn1'! OTOH https://github.com/andrivet/python-asn1 implies that the same package covers Python 3: "100% python, compatible with version 2.7, 3.5 and higher" and a couple of references "Add Python 3.11 tests - last year". So it looks current; but puts into question comment 3 "This package should not be mistaken for python-pyasn1". So please clarify this. "Dependencies Python-ASN1 relies on Python-Future for Python 2 and 3 compatibility" Do we have that?
(In reply to Lewis Smith from comment #7) > The URL is for Python-ASN1; I found nothing for 'python3-asn1'. My search > for 'python3-asn1' came back 'Did you mean: python-asn1'! Python packages typically use python3 or python2 for the rpm name but use just python for the srpm name. For example $ rpm -q -i python3-pillow|grep ^Source Source RPM : python-pillow-9.2.0-3.1.mga9.src.rpm
CC: (none) => davidwhodgins
(In reply to Dave Hodgins from comment #8) > (In reply to Lewis Smith from comment #7) > > The URL is for Python-ASN1; I found nothing for 'python3-asn1'. My search > > for 'python3-asn1' came back 'Did you mean: python-asn1'! By 'search', I meant an Internet search! This still leaves us in the dark about exactly what package Kristoffer is proposing.
(In reply to Lewis Smith from comment #9) > (In reply to Dave Hodgins from comment #8) > > (In reply to Lewis Smith from comment #7) > > > The URL is for Python-ASN1; I found nothing for 'python3-asn1'. My search > > > for 'python3-asn1' came back 'Did you mean: python-asn1'! > By 'search', I meant an Internet search! > This still leaves us in the dark about exactly what package Kristoffer is > proposing. In his spec file, he linked to https://github.com/andrivet/python-asn1 and in the URL: field he linked to https://pypi.org/project/asn1/ Both say 2.7.0 is the last version (from Jan 17, 2023), while Kristoffer wrote version 2.6.0, both in his suggested spec file and in comment 0 The only weird thing is, that https://github.com/andrivet/python-asn1/activity is entirely empty. Anyway, assigning this package request to the Python maintainers, for them to decide what to do with it and with the claim in comment 3: > This package should not be mistaken for python-pyasn1 even though the usage > is about the same subject.
Severity: normal => enhancementCC: (none) => marja11Assignee: bugsquad => python
[dave@x3 ~]$ urpmq -i python3-pyasn1-modules|grep ^Source|sort -u Source RPM : python-pyasn1-modules-0.2.8-3.mga9.src.rpm [dave@x3 ~]$ urpmq -i python3-pyasn1|grep ^Source|sort -u Source RPM : python-pyasn1-0.4.8-6.mga9.src.rpm