[Bug 1977645] Re: python3-gpg 1.16.0-unknown version is incomparable, dependencies always fail
Steve Langasek
1977645 at bugs.launchpad.net
Mon Jun 5 17:12:23 UTC 2023
Thank you for this report. Yes, this is the same issue as bug #1991606.
It is a valid bug report; however, as discussed in that bug it's not
clear that addressing this in Ubuntu 22.04 fits our stable release
update policy. The impact of downloading a second copy of python3-gpg
is pretty minimal - certainly less than the impact of setuptools failing
to work out of the box. This bug has been marked as Importance: Medium,
which seems accurate to me, and would therefore not fit our normal SRU
policy.
I am marking this bug as a duplicate of LP: #1991606.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1977645
Title:
python3-gpg 1.16.0-unknown version is incomparable, dependencies
always fail
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in gpgme1.0 source package in Jammy:
Triaged
Status in gpgme1.0 source package in Kinetic:
Fix Released
Status in gpgme1.0 source package in Lunar:
Fix Released
Status in gpgme1.0 package in Debian:
Fix Released
Bug description:
The python version of the gpgme version contains "unknown" and is
therefore not PEP440 order compatible.
See this example:
# pip3 freeze | grep gpg
gpg===1.16.0-unknown
# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0
# pip3 freeze | grep gpg
gpg==1.10.0
Key takeways from that example:
- pstore depends on gpg>=1.10
- 1.16 SHOULD be higher than 1.10
- pip installs 1.10 even though 1.16 exists
- the triple-= (gpg===1.16.0-unknown) means that the version exists,
but cannot be version compared:
https://peps.python.org/pep-0440/#arbitrary-equality
Suggested fix:
- replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
a '+'; that will compare as expected;
- fix so "-unknown" isn't appended.
Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch
I've attached a FIXED version, which should fix things.
Before:
$ autoreconf -ivf
$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.
After:
$ quilt push
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch
$ autoreconf -ivf
$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.
Versions:
$ lsb_release -a 2>/dev/null| grep Codename
Codename: jammy
$ apt-cache policy python3-gpg | grep Installed
Installed: 1.16.0-1.2ubuntu4
Cheers,
Walter Doekes
OSSO B.V.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions
More information about the foundations-bugs
mailing list