Hello wieczyk, or anyone else affected, Accepted distro-info into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/distro- info/1.1ubuntu0.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. ** Changed in: distro-info (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1991606 Title: Invalid PEP440 package version breaking setuptools >= 66 Status in devscripts package in Ubuntu: Fix Released 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 gpgme1.0 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 update-manager 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 gpgme1.0 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 update-manager 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 gpgme1.0 source package in Focal: New Status in python-debian source package in Focal: Fix Committed Status in reportbug source package in Focal: New Status in ubuntu-dev-tools source package in Focal: Fix Released Status in update-manager source package in Focal: New Status in devscripts source package in Jammy: New Status in distro-info source package in Jammy: Fix Committed Status in drslib source package in Jammy: New Status in duecredit source package in Jammy: New Status in gpgme1.0 source package in Jammy: New Status in python-debian source package in Jammy: Fix Committed Status in reportbug source package in Jammy: New Status in ubuntu-dev-tools source package in Jammy: Invalid Status in update-manager source package in Jammy: New Status in devscripts source package in Kinetic: New Status in distro-info source package in Kinetic: Fix Released Status in drslib source package in Kinetic: New Status in duecredit source package in Kinetic: New Status in gpgme1.0 source package in Kinetic: Fix Released Status in python-debian source package in Kinetic: Fix Committed Status in reportbug source package in Kinetic: New Status in ubuntu-dev-tools source package in Kinetic: Invalid Status in update-manager source package in Kinetic: New Bug description: [ Impact ] 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' [ Test Plan ] 1. $ mkdir /tmp/lp.1991606 $ export HOME=/tmp/lp.1991606 $ sudo apt install dput python3-pip $ pip3 install -U setuptools $ sudo apt install <broken package> $ dput This will produce a backtrace. 2. Enable -proposed 3. Upgrade <broken package> from proposed 4. dput This will succeed. [ Where problems could occur ] The fix touches only setup.py which is only used for installing the package. So there should be no effect on the installed package (except for exposing a different version). But there could be indirect effects (hidden bugs that trigger on package upgrade, etc). [ Other Info ] The related upstream bug report is https://github.com/pypa/setuptools/issues/3772. As of 2023-04-25 it has 85 comments and 108 thumbs ups. 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
