Your message dated Fri, 2 Dec 2022 16:39:59 -0400 with message-id <20221202203959.utwhjv7yr6dko...@haydn.kardiogramm.net> and subject line dh-python dropped 2.x support has caused the Debian Bug report #732713, regarding test t201 fails: has wrong assumptions about symlink handling to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 732713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dh-python Version: 1.20131021-2 Severity: important The dh-python package in Debian has its test suite disabled via debian/rules, with a 'FIXME' comment. The reason for this, it appears, is that t201 is completely broken wrt the actual symlink handling in dh-python. tests/t201/Makefile includes the following check: [ "`readlink debian/python-foo/usr/lib/python$(DPY)/dist-packages/foo/absolute_link_to_tmp`" = "/tmp" ] [ "`readlink debian/python-foo/usr/lib/python$(DPY)/dist-packages/foo/link_to_parent_dir`" = ".." ] But dh_python2 unconditionally moves symlinks from /usr/lib/python* to /usr/share/pyshared, replacing them with relative symlinks in the original directory. for package, pdetails in dh.packages.items(): [...] if not private_dir: share(package, stats, options)d exists(pyshared_dir): I don't know which of these you consider "correct", but they're obviously inconsistent, which makes it impossible to use the test suite for the purpose of detecting regressions in the code. I'm happy to provide a patch if you can tell me which should be changed, the code or the test. Bypassing this check gives me a subsequent failure in tests t202, t204, and t206 because of hard-coded references to python2.6 that are easily fixed, and presumably would have been noticed if the testsuite hadn't been disabled in the package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Version: 5.20221202 Python 2.x (and PyPy 2.x) support was removed in 5.20221202: dh-python (5.20221202) unstable; urgency=medium * Deprecate the flit plugin in favour of pyproject. - Reduce the auto-detect score of the flit plugin. * dh_python3: Clean up more license files from dist-info directories. * Write to debhelper.log files, in overrides. * Add support for --remaining-packages to dh_python*. (closes: 1021875) * Add a test that demonstrates building multiple libraries in a single source package. (closes: 1018952) * Remove dh_python2, dh_pypy, and related debhelper sequences, supporting the removal of the Python 2.7 stack before bookworm release. (closes: 942959) SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
--- End Message ---