Invalid PEP440 package version breaking setuptools >= 66

Hi there, thanks for the report.

Debian and Ubuntu have a long-established package versioning scheme, so I'm not sure it's appropriate to expect those packages to change to conform to what PEP440 wants. But we may be able to do something within the building tools, such as your poetry example, in terms of how it reports distro package versions.

I'm not previously familiar with the python3-poetry package. Would you provide a set of steps to produce this problem using that? I see that one can do a "poetry new poetry-demo", which may assist in constructing a minimal test case.

Also, are there other affected python building tools?

The version 1.1ubuntu1 is clearly not compliant with https://peps.python.org/pep-0440/. For distribution versions the local version identifiers can be used. So the version 1.1ubuntu1 can be mapped to 1.1+ubuntu1.

python/setup.py reads debian/changelog for the version number.

Fixed upstream: https://salsa.debian.org/debian/distro-info/-/commit/e2877dc44659d034155495e91976874c209a3c02

Ah, thank you Benjamin, nice work.

wieczyk, if the above looks like it should resolve the issue then I think no further info is needed.

What's the actual consequence of this issue? Do we need to cherry-pick the fix in Kinetic?

Hard to say. Only consequence I was able to observe is that some python tools that enforce PEP440 reject package. In hard cases someone can install pyenv and install distro-info in another version.

What does mean if we would not port this fix to kinetic? Next ubuntu release will have invalid python package version again?

Uploaded distro-info 1.1ubuntu1 with the fix.

I've accepted it, but please make sure this is synced again as soon as you can.

Don't worry, I am DD as well. I did do an upload to unstable due to the newer pylint that breaks the build in unstable.

This bug was fixed in the package distro-info - 1.1ubuntu1

---------------
distro-info (1.1ubuntu1) kinetic; urgency=medium

  * python: Use PEP440 compliant version in setup.py (LP: #1991606)

 -- Benjamin Drung <email address hidden> Sat, 08 Oct 2022 02:50:34 +0200

Can this change be applied to other branches? The distro-info source package in Jammy also has this bug.

Yes, I can backport the fix. Are you willing to do the paperwork for SRU (see https://wiki.ubuntu.com/StableReleaseUpdates)? For which releases do you want to have? Only jammy?

Sorry I'm not familiar with the paperwork for SRU. Personally, I only need jammy to be fixed

The relevant point of the SRU documentation is to update the ticket description to describe the test plan etc (see https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template).

When can I get it fix on ubuntu 22.04?

Can you provide a test case (step by step instructions to show the issue) for the SRU for 22.04?

Hi guys, I would also like to get this fixed on the LTS distros - bionic, focal. Would that be possible?

bionic: 0.18ubuntu0.18.04.1
focal: 0.23ubuntu1

Finally https://github.com/pypa/setuptools/issues/3772 gives reasoning and a test case:

```
docker run -it --rm --entrypoint=bash ubuntu:focal
apt update && apt install python3 python3-pip python3-distro-info python-debian libfuzzy-dev -y
pip install -U setuptools pip
python3 -m pip install ssdeep
```

> Changed in python-debian (Ubuntu Bionic):
> status: New → Invalid

Can I ask about this change? How is it invalid for bionic? The name of the package is wrong there, too... (for both python-distro-info an python3-distro-info).

python-debian 0.1.32 in bionic is fine. Therefore I marked it invalid for *python-debian* in bionic. distro-info 0.18ubuntu0.18.04.1 in bionic needs to be fixed though.

Ah, now I get it, thanks.

Uploaded distro-info 1.4, python-debian 0.1.49ubuntu2, reportbug 11.6.0ubuntu2, duecredit 0.9.1-1ubuntu1, and ubuntu-dev-tools 0.192 to fix the bug in lunar. I am working on devscripts now. drslib is broken upsteam and should be fixed there first.

This bug was fixed in the package reportbug - 11.6.0ubuntu2

---------------
reportbug (11.6.0ubuntu2) lunar; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Wed, 01 Feb 2023 11:03:46 +0100

This bug was fixed in the package python-debian - 0.1.49ubuntu2

---------------
python-debian (0.1.49ubuntu2) lunar; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Wed, 01 Feb 2023 10:32:24 +0100

This bug was fixed in the package duecredit - 0.9.1-1ubuntu1

---------------
duecredit (0.9.1-1ubuntu1) lunar; urgency=medium

  * Make Debian Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Wed, 01 Feb 2023 11:45:02 +0100

This bug was fixed in the package ubuntu-dev-tools - 0.192

---------------
ubuntu-dev-tools (0.192) unstable; urgency=medium

  [ Benjamin Drung ]
  * sponsor-patch:
    + Ignore exit code 1 of debdiff call.
    + Use --skip-patches instead of --no-preparation with dpkg-source -x.
  * Demote bzr/brz from Recommends to Suggests, as nowadays git is the way.
    Closes: #940531
  * Use PEP440 compliant version in setup.py (LP: #1991606)
  * Fix issues found by flake8 on the Python scripts
  * Check Python scripts with flake8 again
  * Format Python code with black and run black during package build
  * Sort Python imports with isort and run isort during package build
  * Replace deprecated optparse with argparse
  * requestbackport: Remove useless loop from locate_package
  * reverse-depends: Restore field titles format
  * test: Fix deprecated return value for test case
  * Fix all errors and warnings found by pylint and implement most refactorings
    and conventions. Run pylint during package build again.
  * Bump Standards-Version to 4.6.2
  * Drop unneeded X-Python3-Version from d/control

  [ Masahiro Yamada ]
  * mk-sbuild:
    + Handle the new location of the Debian bullseye security archive.
      Closes: #1001832; LP: #1955116

  [ Mattia Rizzolo ]
  * requestbackport:
    + Apply patch from Krytarik Raido and Unit 193 to update the template and
      workflow after the new Ubuntu Backport process has been established.
      LP: #1959115

 -- Benjamin Drung <email address hidden> Wed, 01 Feb 2023 12:45:15 +0100

This bug was fixed in the package update-manager - 1:23.04.1

---------------
update-manager (1:23.04.1) lunar; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)
  * Switch to Debian source 3.0 (native)
  * Replace transitional policykit-1 by polkitd and pkexec
  * Fix pycodestyle complains by formatting Python code with black
  * Drop imports only needed for Python 2
  * Replace lsb_release call with reading /etc/os-release directly

 -- Benjamin Drung <email address hidden> Mon, 13 Feb 2023 14:17:03 +0100

Also possible duplicate: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645

Also a duplicate https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2008121

This bug was fixed in the package devscripts - 2.23.3ubuntu2

---------------
devscripts (2.23.3ubuntu2) lunar; urgency=medium

  * Drop debpkg to make devscripts architecture all. Instead of debpkg please
    use sudo for debi (or, highly dangerous, make dpkg setuid root).
  * Revert special handling for i386

 -- Benjamin Drung <email address hidden> Mon, 20 Mar 2023 13:05:08 +0100

Uploaded distro-info 1.1ubuntu0.1 for jammy (debdiff attached).

Uploaded distro-info 0.23ubuntu1.1 for focal (debdiff attached).

Uploaded distro-info 0.18ubuntu0.18.04.2 for bionic (debdiff attached).

Uploaded python-debian 0.1.43ubuntu1.1 for jammy (debdiff attached).

Uploaded python-debian 0.1.36ubuntu1.1 for focal (debdiff attached).

I do not think this is justified as an SRU. We ship setuptools in Ubuntu, and the version of setuptools shipped in these releases does not trigger the issue. If someone is installing a different local version of setuptools with pip, then they can just as well set up their environment to mask the dist-packages too.

> We ship setuptools in Ubuntu, and the version of setuptools shipped in these releases does not trigger the issue.

It does for me (on Bionic).

Setuptools is not in bionic. So you're using a local version and the previous comment about configuring the environment to not use system modules applies.

> Setuptools is not in bionic

I don't understand. I clearly see it there: https://webcache.googleusercontent.com/search?q=cache:fZGhFT_sSb8J:https://packages.ubuntu.com/bionic/python-setuptools . Or am I missing something?

You're right, python3-setuptools is in bionic, I was looking at the setuptools source package which is not in bionic. python3-setuptools in bionic comes from the 'python-setuptools' source package instead.

In any event, this issue should not affect the python3-setuptools 39.0.1 shipped as part of the bionic release; it is only reported to affect setuptools 66.

So far, we have these implementations:

(a) python-debian and dput other than the lunar one (seems the more robust implementation?):

1.2.3ubuntu4~ppa1 -> 1.2.3+ubuntu4.ppa1

(b) lunar's dput:

1.2.3ubuntu4~ppa1 -> 1.2.3.post4~ppa1

(c) distro-info:

1.2.3ubuntu4~ppa1 -> 1.2.3+ubuntu4~ppa1

How about we standardize on one? What do you think?

You are right, I should apply the fix for lunar as well, because a SRU or security update would produce a malformed version (1.2.3.post4~ppa1 and 1.2.3.post4.1 are both invalid). The improved conversion will bail out in case it would produce a malformed version.

Here is the debdiff for the lunar dput SRU.

This bug was fixed in the package dput - 1.1.3ubuntu3

---------------
dput (1.1.3ubuntu3) mantic; urgency=medium

  * Make PEP 440 version conversion more robust for SRUs (LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 16:09:30 +0200

Hello wieczyk, or anyone else affected,

Accepted dput into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dput/1.1.3ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello wieczyk, or anyone else affected,

Accepted dput into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dput/1.1.2ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello wieczyk, or anyone else affected,

Accepted dput into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dput/1.1.0ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted dput (1.1.0ubuntu2.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#dput

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted dput (1.1.3ubuntu2.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#dput

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted dput (1.1.2ubuntu2.1) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#dput

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello wieczyk, or anyone else affected,

Accepted dput into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dput/1.0.3ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello wieczyk, or anyone else affected,

Accepted gpgme1.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gpgme1.0/1.13.1-7ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello wieczyk, or anyone else affected,

Accepted gpgme1.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gpgme1.0/1.16.0-1.2ubuntu4.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted dput (1.0.3ubuntu1.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

dgit/9.10 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#dput

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted gpgme1.0 (1.16.0-1.2ubuntu4.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

flatpak/1.12.7-1 (arm64)
ros-ros-comm/blacklisted (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#gpgme1.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello wieczyk, or anyone else affected,

Accepted distro-info into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro-info/0.23ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted distro-info (0.23ubuntu1.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

autopkgtest/5.11ubuntu1.1 (amd64)
update-manager/1:20.04.10.11 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#distro-info

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Verified distro-info, dput, gpgme1.0, and python-debian with the test plan from vorlon on lunar, kinetic, jammy, and focal. Detailed logs:

Verification for dput on lunar:

```
$ schroot-wrapper -c lunar -p dput,python3-pip -e
[...]
(lunar)bdrung@host:~$ pip3 install -U setuptools --break-system-packages
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (66.1.1)
Collecting setuptools
  Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 804.0/804.0 kB 8.3 MB/s eta 0:00:00
Installing collected packages: setuptools
Successfully installed setuptools-68.0.0
(lunar)bdrung@host:~$ dput
No package or host has been provided, see dput -h
(lunar)bdrung@host:~$ dpkg -s dput | grep ^Version
Version: 1.1.3ubuntu2.1
```

Verification for dput and python-debian on kinetic:

```
$ schroot-wrapper -c kinetic -p dput,python3-pip,python3-debian -e
[...]
(kinetic)bdrung@host:~$ pip3 install -U setuptools
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (59.6.0)
Collecting setuptools
  Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 804.0/804.0 kB 3.9 MB/s eta 0:00:00
Installing collected packages: setuptools
Successfully installed setuptools-68.0.0
(kinetic)bdrung@host:~$ dput
No package or host has been provided, see dput -h
(kinetic)bdrung@host:~$ dpkg -s dput | grep ^Version
Version: 1.1.2ubuntu2.1
(kinetic)bdrung@host:~$ dpkg -s python3-debian | grep ^Version
Version: 0.1.46ubuntu1
```

Verification for distro-info, dput, gpgme1.0, and python-debian on jammy:

```
$ schroot-wrapper -c jammy -p dput,python3-pip,python3-debian,python3-distro-info -e
[...]
(jammy)bdrung@host:~$ pip3 install -U setuptools
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (59.6.0)
Collecting setuptools
  Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 804.0/804.0 KB 8.0 MB/s eta 0:00:00
Installing collected packages: setuptools
Successfully installed setuptools-68.0.0
(jammy)bdrung@host:~$ dput
No package or host has been provided, see dput -h
(jammy)bdrung@host:~$ dpkg -s python3-distro-info | grep ^Version
Version: 1.1ubuntu0.1
(jammy)bdrung@host:~$ dpkg -s dput | grep ^Version
Version: 1.1.0ubuntu2.1
(jammy)bdrung@host:~$ dpkg -s python3-gpg | grep ^Version
Version: 1.16.0-1.2ubuntu4.1
(jammy)bdrung@host:~$ dpkg -s python3-debian | grep ^Version
Version: 0.1.43ubuntu1.1
```

Verification for distro-info, dput, gpgme1.0, and python-debian on focal:

```
$ schroot-wrapper -c focal -p dput,python3-pip,python3-debian,python3-distro-info -e
[...]
(focal)bdrung@host:~$ pip3 install -U setuptools
Collecting setuptools
  Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
     |████████████████████████████████| 804 kB 2.1 MB/s
Installing collected packages: setuptools
Successfully installed setuptools-68.0.0
(focal)b...

All failing autopkgtest look unrelated to this SRU. So I triggered migration-reference/0 for some of them and retried others.

All autopkgtests for the newly accepted gpgme1.0 (1.13.1-7ubuntu2.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

ros-ros-comm/blacklisted (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#gpgme1.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Rechecked autopkgtest results for distro-info, dput, gpgme1.0, and python-debian:

* focal: distro-info, dput, gpgme1.0, and python-debian okay
* jammy: dput and python-debian okay
* kinetic: dput and python-debian okay

* jammy:
  - distro-info: livecd-rootfs/2.765.20 regression on amd64
  - gpgme1.0: ros-ros-comm/blacklisted regression on s390x
* lunar:
  - dput: dgit/blacklisted regression on s390x

The ros-ros-comm/blacklisted and dgit/blacklisted failures are no regressions. I retried livecd-rootfs/2.765.20.

The livecd-rootfs/2.765.20 regression is not caused by distro-info: gzip: stdout: No space left on device

This bug was fixed in the package dput - 1.1.3ubuntu2.1

---------------
dput (1.1.3ubuntu2.1) lunar; urgency=medium

  * Make PEP 440 version conversion more robust for SRUs (LP: #1991606)

 -- Benjamin Drung <email address hidden> Sat, 01 Jul 2023 01:49:41 +0200

The verification of the Stable Release Update for dput has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package dput - 1.1.2ubuntu2.1

---------------
dput (1.1.2ubuntu2.1) kinetic; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 14:54:30 +0200

This bug was fixed in the package dput - 1.1.0ubuntu2.1

---------------
dput (1.1.0ubuntu2.1) jammy; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 15:45:46 +0200

This bug was fixed in the package dput - 1.0.3ubuntu1.1

---------------
dput (1.0.3ubuntu1.1) focal; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 16:58:12 +0200

This bug was fixed in the package python-debian - 0.1.46ubuntu1

---------------
python-debian (0.1.46ubuntu1) kinetic; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Sat, 27 May 2023 01:51:02 +0200

This bug was fixed in the package python-debian - 0.1.43ubuntu1.1

---------------
python-debian (0.1.43ubuntu1.1) jammy; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Tue, 25 Apr 2023 18:25:44 +0200

This bug was fixed in the package python-debian - 0.1.36ubuntu1.1

---------------
python-debian (0.1.36ubuntu1.1) focal; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung <email address hidden> Tue, 25 Apr 2023 20:39:33 +0200

> The livecd-rootfs/2.765.20 regression is not caused by distro-info: gzip: stdout: No space left on device

I triggered a migation-reference/0 and it failed too, so the error should clear soon.

This bug was fixed in the package distro-info - 1.1ubuntu0.1

---------------
distro-info (1.1ubuntu0.1) jammy; urgency=medium

  * python: Use PEP440 compliant version in setup.py (LP: #1991606)

 -- Benjamin Drung <email address hidden> Tue, 25 Apr 2023 15:30:42 +0200

This bug was fixed in the package distro-info - 0.23ubuntu1.1

---------------
distro-info (0.23ubuntu1.1) focal; urgency=medium

  * python: Use PEP440 compliant version in setup.py (LP: #1991606)
  * Update tests to match old date adjustments in distro-info-data 0.46.

 -- Benjamin Drung <email address hidden> Tue, 25 Apr 2023 15:57:38 +0200

This bug was fixed in the package gpgme1.0 - 1.16.0-1.2ubuntu4.1

---------------
gpgme1.0 (1.16.0-1.2ubuntu4.1) jammy; urgency=medium

  * avoid -unknown suffix (Closes: #1004742, LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 18:37:08 +0200

This bug was fixed in the package gpgme1.0 - 1.13.1-7ubuntu2.1

---------------
gpgme1.0 (1.13.1-7ubuntu2.1) focal; urgency=medium

  * avoid -unknown suffix (Closes: #1004742, LP: #1991606)

 -- Benjamin Drung <email address hidden> Thu, 29 Jun 2023 18:55:04 +0200

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.