python3-gpg 1.16.0-unknown version is incomparable, dependencies always fail

Bug #1977645 reported by Walter
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gpgme1.0 (Debian)
Fix Released
Unknown
gpgme1.0 (Ubuntu)
Fix Released
Medium
Unassigned
Jammy
Won't Fix
Undecided
Unassigned
Kinetic
Fix Released
Undecided
Unassigned
Lunar
Fix Released
Undecided
Unassigned

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.

Tags: patch
Revision history for this message
Walter (wdoekes) wrote :
Revision history for this message
Walter (wdoekes) wrote (last edit ):
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0001-avoid-identifying-as-beta-FIXED.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gpgme1.0 (Ubuntu):
status: New → Confirmed
Changed in gpgme1.0 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Sebastian Wagner (sebix) wrote :

Ubuntu 20.04 is also affected by this bug in the same way.

Jeremy Bícha (jbicha)
summary: - python3-gpg "1.16.0-unknown" version is incomparable -> dependencies
- always fail
+ python3-gpg 1.16.0-unknown version is incomparable, dependencies always
+ fail
Changed in gpgme1.0 (Debian):
status: Unknown → Fix Released
Revision history for this message
Henry Ward Hopeman Jr. (neahwhopeman) wrote :
Steve Langasek (vorlon)
Changed in gpgme1.0 (Ubuntu Kinetic):
status: New → Fix Released
Changed in gpgme1.0 (Ubuntu Lunar):
status: New → Fix Released
Changed in gpgme1.0 (Ubuntu Jammy):
status: New → Triaged
Changed in gpgme1.0 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

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.

Revision history for this message
Steve Langasek (vorlon) wrote :

Well, as it turns out I'm not marking it as a duplicate because bug #1731268 in Launchpad prevents it. Closing this bug instead as wontfix, then.

Changed in gpgme1.0 (Ubuntu Jammy):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.