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 <bdr...@debian.org> Wed, 01 Feb 2023 12:45:15 +0100
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606
Title:
Invalid PEP440 package version breaking setuptools >= 60
Status in devscripts package in Ubuntu:
New
Status in distro-info package in Ubuntu:
Fix Released
Status in drslib package in Ubuntu:
New
Status in duecredit package in Ubuntu:
Fix Released
Status in python-debian package in Ubuntu:
Fix Released
Status in reportbug package in Ubuntu:
Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
Fix Released
Status in devscripts source package in Bionic:
New
Status in distro-info source package in Bionic:
New
Status in drslib source package in Bionic:
Invalid
Status in duecredit source package in Bionic:
New
Status in python-debian source package in Bionic:
Invalid
Status in reportbug source package in Bionic:
New
Status in ubuntu-dev-tools source package in Bionic:
New
Status in devscripts source package in Focal:
New
Status in distro-info source package in Focal:
New
Status in drslib source package in Focal:
New
Status in duecredit source package in Focal:
New
Status in python-debian source package in Focal:
New
Status in reportbug source package in Focal:
New
Status in ubuntu-dev-tools source package in Focal:
New
Status in devscripts source package in Jammy:
New
Status in distro-info source package in Jammy:
New
Status in drslib source package in Jammy:
New
Status in duecredit source package in Jammy:
New
Status in python-debian source package in Jammy:
New
Status in reportbug source package in Jammy:
New
Status in ubuntu-dev-tools source package in Jammy:
Invalid
Status in devscripts source package in Kinetic:
New
Status in distro-info source package in Kinetic:
New
Status in drslib source package in Kinetic:
New
Status in duecredit source package in Kinetic:
New
Status in python-debian source package in Kinetic:
Invalid
Status in reportbug source package in Kinetic:
New
Status in ubuntu-dev-tools source package in Kinetic:
Invalid
Bug description:
With setuptools 66, the versions of all packages visible in the Python
environment *must* obey PEP440 <https://peps.python.org/pep-0440/>.
Otherwise, attempts to use pip to install a package with a setup.py-
based build system, or other attempts to use the `pkg-resources`
module, can produce errors like this:
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 844, in _resolve_dist
env = Environment(self.entries)
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 1044, in __init__
self.scan(search_path)
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 1077, in scan
self.add(dist)
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 1096, in add
dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 2631, in hashcmp
self.parsed_version,
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
line 2678, in parsed_version
self._parsed_version = parse_version(self.version)
File
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
line 266, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'0.23ubuntu1'
The official opinion of the setuptools maintainers seems to be that
version strings of this form haven't *really* been allowed since about
2014, and distributions need to change their package version naming
scheme for Python packages they install, so that the resulting version
strings obey PEP440. See for example
<https://github.com/pypa/setuptools/issues/3772#issuecomment-1384342813>.
suffix 1build1 is invalid.
Some python building tools, that verifies if version strings are
compatible with PEP440, are failing.
Example: python poetry: Invalid PEP 440 version: '1.1build1'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
