Bug#1058122: python-griddataformats: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
Hi,
I created a patch for fixing AttributeError: module 'configparser' has
no attribute 'SafeConfigParser'. I've attached the debdiff for you to
check out.
Cheers!
diff -Nru python-griddataformats-1.0.1/debian/changelog
python-griddataformats-1.0.1/debian/changelog
--- python-griddataformats-1.0.1/debian/changelog 2022-11-07
17:53:52.0 +
+++ python-griddataformats-1.0.1/debian/changelog 2024-01-13
01:30:00.0 +
@@ -1,3 +1,22 @@
+python-griddataformats (1.0.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch for AttributeError: module 'configparser' (Closes:#1058122).
+ * Revised autopkgtest d/tests/* for Python 3.12.
+ * Bumped Standards-Version to 4.6.2.
+
+ -- Yogeswaran Umasankar Sat, 13 Jan 2024 01:30:00 +
+
+python-griddataformats (1.0.1-2) UNRELEASED; urgency=medium
+
+ * Trim trailing whitespace.
+ * Use versioned copyright format URI.
+ * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
+ * Remove constraints unnecessary since buster (oldstable):
++ Build-Depends: Drop versioned constraint on python3-numpy.
+
+ -- Debian Janitor Fri, 18 Nov 2022 03:19:39 -
+
python-griddataformats (1.0.1-1) unstable; urgency=medium
* New upstream release.
@@ -66,18 +85,18 @@
python-griddataformats (0.2.2-3) unstable; urgency=low
- * added debian/watch
+ * added debian/watch
-- Sébastien Buchoux Thu, 17 Nov 2011 17:19:28
+0100
python-griddataformats (0.2.2-2) unstable; urgency=low
- * python-setuptools added as a build dependency in debian/control
+ * python-setuptools added as a build dependency in debian/control
-- Sébastien Buchoux Wed, 16 Nov 2011 17:17:56
+0100
python-griddataformats (0.2.2-1) unstable; urgency=low
* Initial release as Debian package
-
+
-- Sébastien Buchoux Wed, 16 Nov 2011 10:43:43
+0100
diff -Nru python-griddataformats-1.0.1/debian/control
python-griddataformats-1.0.1/debian/control
--- python-griddataformats-1.0.1/debian/control 2022-11-07 17:53:52.0
+
+++ python-griddataformats-1.0.1/debian/control 2024-01-13 01:30:00.0
+
@@ -7,12 +7,12 @@
dh-python,
python3-all:any,
python3-mrcfile,
- python3-numpy (>= 1.19~),
+ python3-numpy,
python3-pytest,
python3-scipy,
python3-setuptools,
python3-six
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
Homepage: https://www.mdanalysis.org/GridDataFormats/
Vcs-Git: https://salsa.debian.org/debichem-team/python-griddataformats.git
Vcs-Browser: https://salsa.debian.org/debichem-team/python-griddataformats
diff -Nru python-griddataformats-1.0.1/debian/copyright
python-griddataformats-1.0.1/debian/copyright
--- python-griddataformats-1.0.1/debian/copyright 2022-11-07
17:53:52.0 +
+++ python-griddataformats-1.0.1/debian/copyright 2024-01-13
01:30:00.0 +
@@ -1,4 +1,4 @@
-Format: http://dep.debian.net/deps/dep5
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: python-griddataformats
Source: https://github.com/MDAnalysis/GridDataFormats
diff -Nru
python-griddataformats-1.0.1/debian/patches/001_AttributeError-fix-py312.patch
python-griddataformats-1.0.1/debian/patches/001_AttributeError-fix-py312.patch
---
python-griddataformats-1.0.1/debian/patches/001_AttributeError-fix-py312.patch
1970-01-01 00:00:00.0 +
+++
python-griddataformats-1.0.1/debian/patches/001_AttributeError-fix-py312.patch
2024-01-13 01:30:00.0 +
@@ -0,0 +1,18 @@
+Description: Fix for AttributeError: module 'configparser' in Python 3.12.
+Author: Yogeswaran Umasankar
+Last-Update: 2024-01-13
+
+--- a/versioneer.py
b/versioneer.py
+@@ -339,9 +339,9 @@ def get_config_from_root(root):
+ # configparser.NoOptionError (if it lacks "VCS="). See the docstring at
+ # the top of versioneer.py for instructions on writing your setup.cfg .
+ setup_cfg = os.path.join(root, "setup.cfg")
+-parser = configparser.SafeConfigParser()
++parser = configparser.ConfigParser()
+ with open(setup_cfg, "r") as f:
+-parser.readfp(f)
++parser.read_file(f)
+ VCS = parser.get("versioneer", "VCS") # mandatory
+
+ def get(parser, name):
diff -Nru python-griddataformats-1.0.1/debian/patches/series
python-griddataformats-1.0.1/debian/patches/series
--- python-griddataformats-1.0.1/debian/patches/series 1970-01-01
00:00:00.0 +
+++ python-griddataformats-1.0.1/debian/patches/series 2024-01-13
01:30:00.0 +
@@ -0,0 +1 @@
+001_AttributeError-fix-py312.patch
diff -Nru python-griddataformats-1.0.1/debian/source/options
python-griddataformats-1.0.1/debian/source/options
--- python-griddataformats-1.0.1/debian/source/options 1970-01-01
00:00:00.0 +
+++ python-griddataformats-1.0.1/debian/source/options 2024-01-13
01:30:00.0 +
@@ -0,0 +1,2 @@
+extend-diff-ignore =
Bug#1058027: pybj: FTBFS with Python 3.12
Dear Maintainer, Python 3.12 changed recursion mechanism [1] sys.setrecursionlimit() and sys.getrecursionlimit(). The recursion limit now applies only to Python code. Builtin functions do not use the recursion limit, but are protected by a different mechanism that prevents recursion from causing a virtual machine crash. so increasing recursion limit as py-ubjson did [2] makes your package buildable. E.g. --- a/test/test.py +++ b/test/test.py @@ -477,10 +477,10 @@ def test_recursion(self): old_limit = getrecursionlimit() - setrecursionlimit(200) + setrecursionlimit(100) try: obj = current = [] - for _ in range(getrecursionlimit() * 2): + for _ in range(getrecursionlimit() * 30): new_list = [] current.append(new_list) current = new_list @@ -488,7 +488,7 @@ with self.assert_raises_regex(RuntimeError, 'recursion'): self.bjddumpb(obj) - raw = ARRAY_START * (getrecursionlimit() * 2) + raw = ARRAY_START * (getrecursionlimit() * 30) with self.assert_raises_regex(RuntimeError, 'recursion'): self.bjdloadb(raw) finally: Kind Regards [1] https://docs.python.org/3/whatsnew/3.12.html#sys [2] https://sources.debian.org/src/py-ubjson/0.16.1-3/debian/patches/py12_recursion_PR19.diff/
Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.
Package: yubioath-desktop Version: 5.1.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: freagar...@tuta.io Dear Maintainer, since yesterday the problem holding back python3-ykman (and related packages) was resolved, I upgraded my system today. When trying to use the GUI for yubikeys (this package), my yubikeys were not shown. I could use the terminal (yubikey-manager CLI) to do my tasks. It seems that this package relies on a lower version of its dependencies. I can't really test due to the dependency issues that introduces. I know there is #1034701, so this report might be considered an escalation of that, but I'm not too comfortable (yet) with Debian policies. Please let me know if more information is needed. And thanks in advance for any effort taken. :) Kind regards, Freagarach -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.9-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yubioath-desktop depends on: ii libc6 2.37-13 ii libgcc-s1 13.2.0-9 ii libqt5core5a 5.15.10+dfsg-5 ii libqt5gui5 5.15.10+dfsg-5 ii libqt5multimedia5 5.15.10-2 ii libqt5qml5 5.15.10+dfsg-2 ii libqt5quick5 5.15.10+dfsg-2 ii libqt5quickcontrols2-5 5.15.10+dfsg-2 ii libqt5widgets5 5.15.10+dfsg-5 ii libstdc++6 13.2.0-9 ii pcscd 2.0.1-1 ii python3-ykman 5.2.1-1 ii qml-module-io-thp-pyotherside 1.6.0-4 ii qml-module-qt-labs-platform5.15.10+dfsg-2 ii qml-module-qt-labs-settings5.15.10+dfsg-2 ii qml-module-qtquick-controls5.15.10-2 ii qml-module-qtquick-controls2 5.15.10+dfsg-2 ii qml-module-qtquick-dialogs 5.15.10-2 yubioath-desktop recommends no packages. yubioath-desktop suggests no packages. -- no debconf information
Bug#1056476: python-importlib-metadata's autopkg tests fail with Python 3.12
Dear Maintainer, > 450s File > "/tmp/autopkgtest.5EvlHX/autopkgtest_tmp/tests/test_main.py", line 8, in > > 450s import pyfakefs.fake_filesystem_unittest as ffs > 450s File > "/usr/lib/python3/dist-packages/pyfakefs/fake_filesystem_unittest.py", > line 72, in > 450s from pyfakefs import fake_pathlib > 450s File "/usr/lib/python3/dist-packages/pyfakefs/fake_pathlib.py", > line 164, in > 450s flavour = pathlib._Flavour # type: ignore [attr-defined] > 450s > 450s AttributeError: module 'pathlib' has no attribute '_Flavour' the failure was fixed in python-pyfakefs/5.3.2-1 [1] uploaded in unstable. Your package builds fine now and all tests pass as well. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056524
Bug#1060671: marked as done (libdbd-oracle-perl: requires rebuild for perl 5.38)
Your message dated Sat, 13 Jan 2024 01:04:19 + with message-id and subject line Bug#1060671: fixed in libdbd-oracle-perl 1.83-2 has caused the Debian Bug report #1060671, regarding libdbd-oracle-perl: requires rebuild for perl 5.38 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.) -- 1060671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdbd-oracle-perl Version: 1.83-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org The perl 5.38 has started. Since libdbd-oracle-perl is in contrib and not auto-buildable, it requires a manual rebuild on amd64 and i386. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libdbd-oracle-perl Source-Version: 1.83-2 Done: Alex Muntada We believe that the bug you reported is fixed in the latest version of libdbd-oracle-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alex Muntada (supplier of updated libdbd-oracle-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 23:27:24 + Binary: libdbd-oracle-perl libdbd-oracle-perl-dbgsym Source: libdbd-oracle-perl Architecture: amd64 i386 source Version: 1.83-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Alex Muntada Closes: 1060671 Description: libdbd-oracle-perl - Perl DBI driver for Oracle Changes: libdbd-oracle-perl (1.83-2) unstable; urgency=medium . * Rebuild for perl 5.38 (Closes: #1060671) Checksums-Sha1: 34db0476ec7416b4959ae54ee23cd062a51d6660 2170 libdbd-oracle-perl_1.83-2.dsc b759b87d872226bcfd6a86195c71ecd3fc20a7f8 7272 libdbd-oracle-perl_1.83-2.debian.tar.xz f36baf661ff77b19ee87c8bde2dd8f6f9ce3f621 224560 libdbd-oracle-perl-dbgsym_1.83-2_amd64.deb 280165a7da71e495403224454204b5346d0a2d8a 6581 libdbd-oracle-perl_1.83-2_amd64.buildinfo 2fbfd7c31b77cbbe866ce4d91b105218b3254278 360716 libdbd-oracle-perl_1.83-2_amd64.deb e97d4f657d18f7096c8aa6e2384e522be8ace434 226944 libdbd-oracle-perl-dbgsym_1.83-2_i386.deb 7a50dfe9ed740701d1d0c6b5bb4468e730f0ed69 6844 libdbd-oracle-perl_1.83-2_i386.buildinfo 45190bcae0f25c1c53dbff65f2258f3b1bee2e69 358944 libdbd-oracle-perl_1.83-2_i386.deb Checksums-Sha256: 5a22b0c6367db8e4ad5afa02dac731c8525a01f8ae1203777d40d1ee649ed309 2170 libdbd-oracle-perl_1.83-2.dsc 0a5bf723a48725d6429db0aaf0d5fa9864a11d6b2e8e619fe9721c26ce01d591 7272 libdbd-oracle-perl_1.83-2.debian.tar.xz d6c1849501f3ed7dc5d0363a10928cb67be2e82766069e819777c15b9493a172 224560 libdbd-oracle-perl-dbgsym_1.83-2_amd64.deb f5082d22bafb89cbff2ca6b2d2e9d64b34d9646e2939d4e7541788c17ffdf432 6581 libdbd-oracle-perl_1.83-2_amd64.buildinfo 0c16c86215d53a35d8de325c929e36d9dc7d08e85be1cf738702fd5aae5d655e 360716 libdbd-oracle-perl_1.83-2_amd64.deb 172a0ab27fc2e5e29d1243d76c4dc322c4abb86742bafecbf84325dab0305055 226944 libdbd-oracle-perl-dbgsym_1.83-2_i386.deb 16923a2ce518c8d9628b85a0e6d8e71445bc5836dfab16dac7b802385868f81f 6844 libdbd-oracle-perl_1.83-2_i386.buildinfo 7529a7687218a480bae595e1144695aa44dcff120555d0cacd5a95788b48f4df 358944 libdbd-oracle-perl_1.83-2_i386.deb Files: 1250a77cf4b26551f4b7628134e49a8a 2170 contrib/perl optional libdbd-oracle-perl_1.83-2.dsc 4ff949195ced792009d093351e6b4fd1 7272 contrib/perl optional libdbd-oracle-perl_1.83-2.debian.tar.xz 3e251d0a4aa6ec74ebbba44079941bba 224560 contrib/debug optional libdbd-oracle-perl-dbgsym_1.83-2_amd64.deb 5a524e1c1f7cd564b66fc305695d39a0 6581 contrib/perl optional libdbd-oracle-perl_1.83-2_amd64.buildinfo 7f684ce8ae1dc7a1aac6ed3dcd1e2386 360716 contrib/perl optional libdbd-oracle-perl_1.83-2_amd64.deb 118aa4ffdbe1767f9856a1302d4ff97f 226944 contrib/debug optional libdbd-oracle-perl-dbgsym_1.83-2_i386.deb 92fb36952d2fa8cc696b2dfbcc68 6844 contrib/perl optional libdbd-oracle-perl_1.83-2_i386.buildinfo c9e8bfa8506351ff74c06814f4a3804b 358944 contrib/perl optional libdbd-oracle-perl_1.83-2_i386.deb -BEGIN PGP SIGNATURE-
Bug#1056474: python-ibm-cloud-sdk-core's autopkg tests fail with Python 3.12
Hi, Uploaded a patch in salsa [0] to fix the autopkgtest issue with Py 3.12. Updated the package with new upstream version too. [0] https://salsa.debian.org/python-team/packages/python-ibm-cloud-sdk-core Cheers! signature.asc Description: PGP signature
Bug#1058310: python-ibm-cloud-sdk-core: FTBFS: failed tests
Hi, Uploaded a patch in salsa [0] to fix the autopkgtest issue with Py 3.12. Updated the package with new upstream version too. [0] https://salsa.debian.org/python-team/packages/python-ibm-cloud-sdk-core Cheers! signature.asc Description: PGP signature
Bug#1041089: thin-provisioning-tools FTBFS with googletest 1.13.0
Hello, Is there something else that needs to be done to get the package back into testing? My system prints a "missing binary: /usr/sbin/check_cache" at boot time when assembling my lvmcache(7). Thanks, Karsten
Processed: tagging 1058997
Processing commands for cont...@bugs.debian.org: > tags 1058997 + patch Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1052899
Processing commands for cont...@bugs.debian.org: > close 1052899 Bug #1052899 [src:python-fido2] python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1052899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052899: closing 1052899
close 1052899 thanks python-fido2 1.1.2-2 uploaded to unstable, closing.
Bug#1060455: marked as done (awscli: Please drop python-cryptography upper limit or increase it)
Your message dated Fri, 12 Jan 2024 21:50:11 + with message-id and subject line Bug#1060455: fixed in awscli 2.15.9-1 has caused the Debian Bug report #1060455, regarding awscli: Please drop python-cryptography upper limit or increase it 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.) -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: awscli Version: 2.14.6-1 Severity: serious Control: forwarded -1 https://github.com/aws/aws-cli/issues/5943 awscli is not installable in Debian Unstable because python-cryptography has been updated to a newer version than permitted in awscli's dependencies. I recommend dropping the upper limit. Alternatively you could increase the limit to a higher version. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: awscli Source-Version: 2.15.9-1 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of awscli, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated awscli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 10:51:10 -0800 Source: awscli Architecture: source Version: 2.15.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Cloud Team Changed-By: Noah Meyerhans Closes: 1060455 Changes: awscli (2.15.9-1) unstable; urgency=medium . * New upstream version 2.15.9 (Closess: #1060287) * Relax upstream python-cryptography version restrictions (Closes: #1060455) Checksums-Sha1: 5b919be2b6e3a5724ce8434be39e33234bcdf658 2278 awscli_2.15.9-1.dsc eadb9f1a88d793b279f09441cc1cfd4d27caffc1 14651183 awscli_2.15.9.orig.tar.gz 12281e322c8e3d2ec2b77c52306c9ae03f8a050c 6084 awscli_2.15.9-1.debian.tar.xz 28d97bb080bb7aa86014b1cbe874f3963baa3550 7188 awscli_2.15.9-1_source.buildinfo Checksums-Sha256: 261ee3dcf63a647a19b5a0231267f26de00bc94579c241b96ec86be47c409802 2278 awscli_2.15.9-1.dsc 1ce772ead3f53e4f93eb96d0b876ed065beb41fb58a9b4ee8aa2d91e4721d3ff 14651183 awscli_2.15.9.orig.tar.gz f045579be8b81bb5cb7b0589a0997ce993a17a5b619a02d080da1c537f9c7fb6 6084 awscli_2.15.9-1.debian.tar.xz bb8c88c059a547b482db3f3aca9e0ab6fd4a26d6205280155a9157b0ef4ab0fc 7188 awscli_2.15.9-1_source.buildinfo Files: 53915d203fee664f03cb2a5e81d12125 2278 admin optional awscli_2.15.9-1.dsc aecb67aea4e4f3c20e33397ba4f10944 14651183 admin optional awscli_2.15.9.orig.tar.gz 78cc84f469ebf54a7d92b2361d49ae9d 6084 admin optional awscli_2.15.9-1.debian.tar.xz 78cc7f32b22b8683ce320d84bb5d5e0b 7188 admin optional awscli_2.15.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmWhrqQRHG5vYWhtQGRl Ymlhbi5vcmcACgkQ4+c1IpshdTU86w/9F6lPLGTEMMewsl4QtjGmXx62c93NK9Zy 3sBEynYeBXCBYKSXsCxVrVmgegHKp5eLabwOZhNIY8X7D59jAduWpgbQ7BikVNzq Ndmm7B4AyKgUF8c+3LYYLZYCMz17ferw41lkBMxGQ7w6d6aWOcFOKEKL6fcA6i+V KfKoL4jlp2OZZ58VKbHKsudKH9bb1GSWM6/iHxg3pjGqJoZDvIlAS3i5eE3okE2/ I+sK5QJQ0ryOQHUwgryVb9oIllFHcPq3IVpItQ5aKVk/dASBuMb/pMqmK2Hsg/0I 9d9RHbn4itieoZiTXmiIIawwcow59RZ+2Tod4L7vsAramcahr5NFQ151OW8+EXxv eUUGf8d7IfiXzeoAUrNGSbMvrIX+ygxqrxtKxXJUYLdRFnFRntKY3A/ZUsU3V5MJ 94BC2TnyQNzutLQHN8TBPZCfOxsnzuLSCZ3Bb5k6J5J5i/Gejkh4URCSUFX3ds04 184vzo4hG+la7vKQYWG+7TzztQ2ZVyRsUj1zzhpzXY6946Z7I4L4xS1KD9yaPO0p bBglnXh+NaGMK63BGbBcB7Y28+i2Zzw6yOFEZkPz46M2BLfJcVz0ELo0bTFg+FFf /TmlidrK37I0GWkSXWd7M6toWHM4fYem0TOBQyNI/vVvYx0X9YL8rhJUdoLsg2qV /I3uq9XXctg= =qpcD -END PGP SIGNATURE End Message ---
Bug#1060266: marked as done (python3-ykman: Package uninstallable)
Your message dated Fri, 12 Jan 2024 21:35:21 + with message-id and subject line Bug#1060266: fixed in yubikey-manager 5.2.1-1 has caused the Debian Bug report #1060266, regarding python3-ykman: Package uninstallable 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.) -- 1060266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-ykman Version: 4.0.9-2 Severity: serious Dear Maintainer, I can't install this package. | $ LANG=C sudo apt-get install python3-ykman | [...] | The following information may help to resolve the situation: | | The following packages have unmet dependencies: | python3-ykman : Depends: python3-cryptography (< 39) but 41.0.7-1 is to be installed | E: Unable to correct problems, you have held broken packages. ` Christian -- System Information: Debian Release: trixie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.10-1-custom (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-ykman depends on: ii python3 3.11.6-1 ii python3-click 8.1.6-1 ii python3-cryptography 41.0.7-1 ii python3-fido2 0.9.1-1 ii python3-pyscard 2.0.7-2+b1 Versions of packages python3-ykman recommends: ii pcscd 2.0.1-1 python3-ykman suggests no packages. --- End Message --- --- Begin Message --- Source: yubikey-manager Source-Version: 5.2.1-1 Done: Florian Schlichting We believe that the bug you reported is fixed in the latest version of yubikey-manager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated yubikey-manager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jan 2024 21:56:21 +0100 Source: yubikey-manager Architecture: source Version: 5.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Florian Schlichting Closes: 1060266 Changes: yubikey-manager (5.2.1-1) unstable; urgency=medium . * Team upload . * Update d/watch (linux release name uses underscore instead of hyphen) * New upstream version 5.2.0 (closes: #1060266) * Build-Depend on pybuild-plugin-pyproject instead of python3-setuptools * Update d/*.install for renamed directories * Update (build-)dependencies (add keyring, update versions) * Update d/copyright (Apache files, years) * d/rules: drop obsolete inclusion of pkg-info.mk * Drop python3-yubikey-manager.maintscript, we no longer build that package * Declare compliance with Debian Policy 4.6.2 * New upstream version 5.2.1 Checksums-Sha1: 43458dbf8a07955fc47f0827524d5f63f02c115f 2667 yubikey-manager_5.2.1-1.dsc 3fc2cd5cc274932c44a8522b525be53b987213ac 185533 yubikey-manager_5.2.1.orig.tar.gz d33b03da838fe5acb7cbb3c4f8f30138a131908f 488 yubikey-manager_5.2.1.orig.tar.gz.asc 094952cda8ed60301f47ae0993cdaaa6a7f163d6 72912 yubikey-manager_5.2.1-1.debian.tar.xz 3477a922c3173f2a2c29c22f4dcda504d04ff948 8399 yubikey-manager_5.2.1-1_amd64.buildinfo Checksums-Sha256: c4ca598a3ed688b73a5b291ebc9fa63971562b76bd718a11a9bd44edae2a54e6 2667 yubikey-manager_5.2.1-1.dsc 35c5aa83ac474fd2434c33267dc0e33d312b3969b108f885e533463af3fbe4e1 185533 yubikey-manager_5.2.1.orig.tar.gz 523966e8c73503d23d0718d3d2ec11b0af43ae9f838ead8deed3ca4a61a10a32 488 yubikey-manager_5.2.1.orig.tar.gz.asc 5775c06fa71c04b093469f286ac187d7f038e3a91bb18823dd7ee75e9b53021d 72912 yubikey-manager_5.2.1-1.debian.tar.xz 6191383cb7e3503432409d694c92898000c85fd96d583bd42c3226a0983951d0 8399 yubikey-manager_5.2.1-1_amd64.buildinfo Files: b924714d5f9a822a85324879f5224fc6 2667 utils optional yubikey-manager_5.2.1-1.dsc ea3288f3cf155655d64ab4694decc41a
Bug#1060285: marked as done (mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols)
Your message dated Fri, 12 Jan 2024 21:34:24 +
with message-id
and subject line Bug#1060285: fixed in mptcpd 0.12-3
has caused the Debian Bug report #1060285,
regarding mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP
disabled and no /etc/protocols
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.)
--
1060285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mptcpd
Version: 0.12-2
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear maintainer,
On riscv64, mptcpd fails to build from source with a segmentation fault
in the test-mptcpwrap test:
| ===
|mptcpd 0.12: tests/test-suite.log
| ===
|
| # TOTAL: 19
| # PASS: 17
| # SKIP: 1
| # XFAIL: 0
| # FAIL: 1
| # XPASS: 0
| # ERROR: 0
|
| .. contents:: :depth: 2
|
| SKIP: test-start-stop
| =
|
| Running non-interactive sudo check...
| sudo: a password is required
| fail, skipping the test
| SKIP test-start-stop (exit status: 77)
|
| FAIL: test-mptcpwrap
|
|
| Test case 0: PASS
| Test case 1: Segmentation fault
| FAIL test-mptcpwrap (exit status: 139)
A full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=mptcpd=riscv64=0.12-2%2Bb1=1704714971=0
Investigation shows that 3 conditions are needed to trigger this issue:
- A recent kernel that supports mptcp, to be checked with
/proc/sys/net/mptcp/enabled
- Something that prevents SCTP to be used, for instance on the build
daemons /proc/sys/kernel/modules_disabled is set to 1, preventing the
sctp.ko module to be loaded
- A system without /etc/protocols, for instance without the netbase
package installed.
With this three conditions, this triggers the following code path from
the mptcpwrap-tester.c file:
| static void test_socket_data(struct socket_data const *data)
| {
| int const fd = socket(data->domain, data->type, data->protocol);
|
| if (fd == -1) {
| if (errno == EPROTONOSUPPORT) {
| struct protoent const *const p =
| getprotobynumber(data->protocol);
|
| fprintf(stderr,
| "WARNING: Ignoring unsupported "
| "protocol: %d - %s\n",
| data->protocol,
| p->p_name);
|
| return;
| }
The output of getprotobynumber() is used directly, without checking for
a NULL pointer in case of error, for instance because /etc/protocols
does not exist. This causes a segmentation fault when trying to
dereference it. A workaround is to build-depends on netbase, and a
proper fix to test for this error.
In the latest rebuild of mptpcd, the conditions where met only on the
riscv64 buildd, and riscv64 is not a release architecture. That said a
few mips64el buildds also met the 3 conditions and it will be the case
of more and more buildds once they are upgraded to bookworm. I am
therefore filling this issue as severity serious.
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: mptcpd
Source-Version: 0.12-3
Done: Matthieu Baerts (NGI0)
We believe that the bug you reported is fixed in the latest version of
mptcpd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthieu Baerts (NGI0) (supplier of updated mptcpd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 11 Jan 2024 14:55:36 +0100
Source: mptcpd
Architecture: source
Version: 0.12-3
Distribution: unstable
Urgency: medium
Maintainer: Matthieu Baerts
Changed-By: Matthieu Baerts (NGI0)
Closes: 1060285
Changes:
mptcpd (0.12-3) unstable; urgency=medium
.
* debian: build-dep: add netbase. (Closes:
Bug#1060285: mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols
Hi Matthieu, On 2024-01-12 11:06, Matthieu Baerts wrote: > Hi Aurélien, > > On 10/01/2024 19:13, Matthieu Baerts wrote: > > On 08/01/2024 21:18, Aurelien Jarno wrote: > > (...) > > >> In the latest rebuild of mptpcd, the conditions where met only on the > >> riscv64 buildd, and riscv64 is not a release architecture. That said a > >> few mips64el buildds also met the 3 conditions and it will be the case > >> of more and more buildds once they are upgraded to bookworm. I am > >> therefore filling this issue as severity serious. > > > > Many thanks for the explanation! > > > > I will wait for the different pipelines to be over, before sending a new > > version to mentors.debian.net! > > This new version has been sent to mentors.debian.net: > > https://mentors.debian.net/package/mptcpd/ > https://mentors.debian.net/debian/pool/main/m/mptcpd/mptcpd_0.12-3.dsc > Thanks for the quick fix, I have just uploaded it! Cheers Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1059040: libxml2: ABI change? (undefined references)
* Thorsten Glaser [2024-01-12 17:56]: On Fri, 12 Jan 2024, Rafael Laboissière wrote: experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. No, this will still break partial upgrades. Losing symbols needs a major shlib version change *including*, in Debian, changing the binary package name so that the old and new shlibs are coïnstallable. And this needs to be exercised in experimental first, not only when introducing this to unstable. Alternatively, bring the symbols back. Thanks for the clarification, this is exactly what I meant. I apologized for not being clear enough. Best, Rafael Laboissière
Bug#1060687: libwacom-dev: Needs Depends: libevdev-dev
Source: libwacom Version: 2.9.0-1 Severity: serious libwacom.pc now has this line: Requires.private: gudev-1.0, glib-2.0, libevdev Therefore, please add libevdev-dev to libwacom-dev's Depends. I noticed this issue when building another package that uses libwacom but it was also detected by autopkgtests. Thank you, Jeremy Bícha
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
Good day, does grub 2.12 (without rc1) help? There are a good pile of fixups between rc1 and release. E.g. https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=1f5b180742ff2706bc3a696d115ddbc677ec75b9 or https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=67ae3981dc5113e5af3a0539174bcd7eab8f7722 could help. Additionally, the ZFS fixes are needed to boot from volumes touched by ZFS 2.2 ( https://github.com/openzfs/zfs/issues/13873 ), so migrating to 2.12 is helpful in either case. Best regards, Michael Fritscher On Sat, 25 Nov 2023 17:36:41 -0500 Nicolas Haller wrote: > Package: grub-efi-amd64 > Version: 2.06-13 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > My old laptop (Lenovo 11e) runs Sid and all was right before I updated > it the other day (I don't do that very often). After that upgrade, GRUB > wasn't able to load any kernel with the pretty much generic error > "Error: can't load image". The version of GRUB was 2.12~rc1-12. > If I try to boot again, GRUB tells me that I need to load the image > first (I guess it somehow ignores the linux command and sends that when > trying to load the initrd). > > I tried to reinstall grub, grub-install /dev/sda, update-grub, reinstall > the kernel, update-initramfs from the rescue mode but nothing worked. > The "file" command was able to read the vmlinuz file and none seemed > truncated. The system has one partition with both / and /boot and isn't > running out of space. > I did not see any error message during those operation besides GRUB > saying it wasn't able to update EFI parameters. > > I don't know if there is a way to get more logs or error message during > the boot explaining why it wasn't able to load the image. > > I tried to get the last version of GRUB from Bookworm, that is > 2.06-13, and now I'm able to boot. The kernel version did not change, > the only change I did is to downgrade GRUB (and dependencies apt was > asking for). > > I'm not sure which GRUB package I should use for reporting so I took the > one that seems the most specific to my system. Apologies if it is not > correct. > > Let me know if you need more info. > > Thanks, > > -- > Nicolas Haller > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > -- Package-specific info: > > *** BEGIN /proc/mounts > /dev/sda2 / ext4 rw,relatime,errors=remount-ro 0 0 > /dev/sda1 /boot/efi vfat > rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro > 0 0 > *** END /proc/mounts >
Bug#1060455: marked as pending in awscli
Control: tag -1 pending Hello, Bug #1060455 in awscli reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/cloud-team/awscli/-/commit/3063cba4ec35ea43ce28eeac05abb969019e877b Relax upstream python-cryptography version restrictions Closes: #1060455 (this message was generated automatically) -- Greetings https://bugs.debian.org/1060455
Processed: Bug#1060455 marked as pending in awscli
Processing control commands: > tag -1 pending Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Ignoring request to alter tags of bug #1060455 to the same tags previously set -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it
On Thu, Jan 11, 2024 at 02:27:23PM -0500, Jeremy Bícha wrote: > There is a diff at > https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this > issue. You can ignore the build failure since that doesn't seem to > currently affect Debian Unstable. Thanks, I've applied that patch and will include it with the upcoming 2.15.9-1 package.
Processed: tagging 1060455
Processing commands for cont...@bugs.debian.org: > tags 1060455 + pending Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059525: linux-image-6.1.0-16-amd64: Secure Boot is active but mokutil and dmesg says "Secure boot disabled" but just with an NVME not with an HDD/SSD
In a Debian Testing System one of the packages solved my problem. Secure Boot is now displayed as active. Start-Date: 2024-01-12 18:59:31 Commandline: apt full-upgrade Requested-By: user (1000) Upgrade: orca:amd64 (45.1-2, 45.2-1), dmeventd:amd64 (2:1.02.185-2, 2:1.02.185-3), libldb2:amd64 (2:2.8.0+samba4.19.3+dfsg-2, 2:2.8.0+samba4.19.4+dfsg-2), libgs10-common:amd64 (10.02.1~dfsg-1, 10.02.1~dfsg-2), liblua5.4-0:amd64 (5.4.6-1, 5.4.6-2), liblvm2cmd2.03:amd64 (2.03.16-2, 2.03.16-3), libgs10:amd64 (10.02.1~dfsg-1, 10.02.1~dfsg-2), logrotate:amd64 (3.21.0-1, 3.21.0-2), libwbclient0:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2), libsmbclient:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2), lvm2:amd64 (2.03.16-2, 2.03.16-3), ghostscript:amd64 (10.02.1~dfsg-1, 10.02.1~dfsg-2), gir1.2-ibus-1.0:amd64 (1.5.29~rc2-1, 1.5.29-1), grep:amd64 (3.11-3, 3.11-4), libopenni2-0:amd64 (2.2.0.33+dfsg-17, 2.2.0.33+dfsg-18), dmsetup:amd64 (2:1.02.185-2, 2:1.02.185-3), libdevmapper-event1.02.1:amd64 (2:1.02.185-2, 2:1.02.185-3), samba-libs:amd64 (2:4.19.3+dfsg-2, 2:4.19.4+dfsg-2), libgs-common:amd64 (10.02.1~dfsg-1, 10.02.1~dfsg-2), libibus-1.0-5:amd64 (1.5.29~rc2-1, 1.5.29-1), libdevmapper1.02.1:amd64 (2:1.02.185-2, 2:1.02.185-3) End-Date: 2024-01-12 18:59:53
Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
Hi, On 12-01-2024 12:36, Chris Hofstaedtler wrote: can you confirm two additional things please: 1) this happens only on the large host? https://ci.debian.net/packages/p/pdns/testing/s390x/41650331/ Seems it happens on our s390x host too (which has 10 debci workers running in parallel). 2) this does not or does happen with other packages also requesting the same settings from systemd, e.g. dnsdist or pdns-recursor? https://ci.debian.net/packages/d/dnsdist/ -> Page not found. pdns-recursor seems to be flaky as well on amd64 and all passing tests were on one of the smaller hosts. pdns-recursor passes on s390x though. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf
> This is a quick word to let you know that I've disabled valgrind tests > on armhf in the Debian package. They were failing since the 1.8.5 upload > [...] Thank you, I agree with this approach. The evidence I have seen so far suggests that the failures are due to issues with the way valgrind itself behaves on that architecture. -- Andrew Wood
Bug#1059040: libxml2: ABI change? (undefined references)
On Fri, 12 Jan 2024, Rafael Laboissière wrote: > experimental, the configure script does detect the absence of the > xmlNanoFTPNewCtxt function in the libxml2 library (version > 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. > However, this rebuilt will not be automatically triggered without a > bump in the SONAME version of libxml2. > > In summary, the introduction of version 2.12 of libxml2 in unstable > will need a proper and coordinated transition. No, this will still break partial upgrades. Losing symbols needs a major shlib version change *including*, in Debian, changing the binary package name so that the old and new shlibs are coïnstallable. And this needs to be exercised in experimental first, not only when introducing this to unstable. Alternatively, bring the symbols back. bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Processed: [Pending] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Processing control commands: > tags -1 pending Bug #1042590 [src:django-session-security] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. -- 1042590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057607: marked as done (sphinx-design: FTBFS: failing tests)
Your message dated Fri, 12 Jan 2024 16:51:08 +
with message-id
and subject line Bug#1057607: fixed in sphinx-design 0.5.0-2
has caused the Debian Bug report #1057607,
regarding sphinx-design: FTBFS: failing tests
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.)
--
1057607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sphinx-design
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with python3 --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
module
I: pybuild base:310: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_sphinx-design
* Building wheel...
Successfully built sphinx_design-0.5.0-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with
"installer" module
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.11_sphinx-design
* Building wheel...
Successfully built sphinx_design-0.5.0-py3-none-any.whl
I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with
"installer" module
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:310: cd
/<>/.pybuild/cpython3_3.12_sphinx-design/build; python3.12 -m
pytest tests
= test session starts ==
platform linux -- Python 3.12.0, pytest-7.4.3, pluggy-1.3.0
rootdir: /<>/.pybuild/cpython3_3.12_sphinx-design/build
plugins: cov-4.1.0, datadir-1.4.1+ds, regressions-2.4.1+ds
collected 6 items
tests/test_snippets.py FF[100%]
=== FAILURES ===
test_sd_hide_title_rst
sphinx_builder = ._create_project at
0x7ff8dd512de0>
file_regression =
def test_sd_hide_title_rst(
sphinx_builder: Callable[..., SphinxBuilder], file_regression
):
"""Test that the root title is hidden."""
builder = sphinx_builder()
tests/test_snippets.py:122:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/conftest.py:78: in _create_project
app = make_app(
/usr/lib/python3/dist-packages/sphinx/testing/fixtures.py:183: in make
app_: Any = SphinxTestApp(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <[AttributeError("'SphinxTestApp' object has no attribute 'builder'")
raised in repr()] SphinxTestApp object at 0x7ff8dd527ef0>
buildername = 'html'
srcdir = path('/tmp/pytest-of-buildd/pytest-0/test_sd_hide_title_rst0/srcdir')
builddir =
path('/tmp/pytest-of-buildd/pytest-0/test_sd_hide_title_rst0/srcdir/_build')
freshenv = False, confoverrides = None
status = <_io.StringIO object at 0x7ff8dd51b7c0>
warning = <_io.StringIO object at 0x7ff8dd51aec0>, tags = None
docutilsconf = None, parallel = 0
def __init__(
self,
buildername: str = 'html',
srcdir: Path | None = None,
builddir: Path | None = None,
freshenv: bool = False,
confoverrides: dict | None = None,
status: IO | None = None,
warning: IO | None = None,
tags: list[str] | None = None,
docutilsconf: str | None = None,
parallel: int = 0,
) -> None:
assert srcdir is not None
self.docutils_conf_path = srcdir / 'docutils.conf'
if docutilsconf is not None:
self.docutils_conf_path.write_text(docutilsconf, encoding='utf8')
if builddir is None:
builddir = srcdir / '_build'
confdir = srcdir
outdir = builddir.joinpath(buildername)
outdir.mkdir(parents=True, exist_ok=True)
E AttributeError: 'path' object has no attribute 'mkdir'. Did you mean:
'isdir'?
/usr/lib/python3/dist-packages/sphinx/testing/util.py:105: AttributeError
___ test_sd_hide_title_myst
sphinx_builder =
Bug#1042590: [Pending] django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Control: tags -1 pending Hi, I've fixed this problem in Git[1] but did not uploaded since autopkgtest is failing in Salsa CI[2]. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/django-session-security/-/commit/af1ebc734a33cf1b629a2626bad508b833eb2706 [2] https://salsa.debian.org/python-team/packages/django-session-security/-/jobs/5150104 -- http://fam-tille.de
Processed: bug 1060251 is forwarded to https://bugs.kde.org/show_bug.cgi?id=479699
Processing commands for cont...@bugs.debian.org:
> forwarded 1060251 https://bugs.kde.org/show_bug.cgi?id=479699
Bug #1060251 {Done: Paul Gevers } [valgrind] valgrind: apt
autopkgtests on armhf fail with: Access not within mapped region
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=479699'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042674: marked as done (flufl.bounce: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Fri, 12 Jan 2024 16:34:34 + with message-id and subject line Bug#1042674: fixed in flufl.bounce 4.0-4 has caused the Debian Bug report #1042674, regarding flufl.bounce: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flufl.bounce Version: 4.0-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, flufl.bounce fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > /usr/lib/python3/dist-packages/setuptools/dist.py:945: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. > !! > > > > Please replace its usage with implicit namespaces (PEP 420). > > See > https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages > for details. > > > > !! > ep.load()(self, ep.name, value) > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl > copying flufl/__init__.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl > creating > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce > copying flufl/bounce/_scan.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce > copying flufl/bounce/conf.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce > copying flufl/bounce/__init__.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce > copying flufl/bounce/interfaces.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce > creating > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/smtp32.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/exim.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/simplewarning.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/caiwireless.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/groupwise.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/netscape.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/llnl.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/__init__.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/qmail.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/sina.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/exchange.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/microsoft.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/yahoo.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/yale.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/postfix.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/simplematch.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/dsn.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > copying flufl/bounce/_detectors/aol.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/_detectors > creating > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/testing > copying flufl/bounce/testing/__init__.py -> > /<>/.pybuild/cpython3_3.11_flufl.bounce/build/flufl/bounce/testing > copying flufl/bounce/testing/helpers.py -> >
Bug#1060067: marked as done (fuse3: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Fri, 12 Jan 2024 16:19:24 + with message-id and subject line Bug#1060067: fixed in fuse3 3.14.0-5 has caused the Debian Bug report #1060067, regarding fuse3: FTBFS: dh_missing: error: missing files, aborting 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.) -- 1060067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fuse3 Version: 3.14.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, fuse3 fails to build with error in dh_missing. From my build log on amd64: | dh_fixperms | chmod a-x debian/libfuse3-dev/usr/share/doc/libfuse3-dev/examples/cuse_client.c | make[1]: Leaving directory '/<>' |debian/rules override_dh_missing | make[1]: Entering directory '/<>' | dh_missing --fail-missing | dh_missing: warning: usr/lib/udev/rules.d/99-fuse3.rules exists in debian/tmp but is not installed to anywhere | dh_missing: error: missing files, aborting | The following debhelper tools have reported what they installed (with files per package) |* dh_install: fuse3 (3), fuse3-udeb (2), libfuse3-3 (2), libfuse3-3-udeb (2), libfuse3-dev (4) |* dh_installdocs: fuse3 (0), libfuse3-3 (3), libfuse3-dev (0) |* dh_installexamples: fuse3 (0), libfuse3-3 (0), libfuse3-dev (21) |* dh_installman: fuse3 (2), libfuse3-3 (0), libfuse3-dev (0) | If the missing files are installed by another tool, please file a bug against it. | When filing the report, if the tool is not part of debhelper itself, please reference the | "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). | (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz) | Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built | If the omission is intentional or no other helper can take care of this consider adding the | paths to debian/not-installed. | make[1]: *** [debian/rules:73: override_dh_missing] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:76: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 A full build log on riscv64 is available there: https://buildd.debian.org/status/fetch.php?pkg=fuse3=riscv64=3.14.0-4%2Bb1=1704460936=0 A full build log on arm64 is also available from reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/fuse3_3.14.0-4.rbuild.log.gz Regards Aurelien --- End Message --- --- Begin Message --- Source: fuse3 Source-Version: 3.14.0-5 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of fuse3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated fuse3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 16:46:21 +0100 Source: fuse3 Architecture: source Version: 3.14.0-5 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1060067 1060606 Changes: fuse3 (3.14.0-5) unstable; urgency=medium . * Fix 99-fuse3.rules path (closes: #1060067). * Switch udev build dependency to systemd-dev (closes: #1060606). Checksums-Sha1: 11816a4864a69bf9a83d0aa3d122eba38d18d137 2385 fuse3_3.14.0-5.dsc eee768aed1312c2ba34055e45bcfaa5e2226abff 17860 fuse3_3.14.0-5.debian.tar.xz Checksums-Sha256: 0fcf4cc70745c2b4225c7fd26944fbe8d6a5d4d0505e97524162d61e4f1eeb93 2385 fuse3_3.14.0-5.dsc e57fa675b7231dcecab0601c464dfda6c6e6983daa04bae98ec7548f6580def7 17860 fuse3_3.14.0-5.debian.tar.xz Files: 8ffa43008bf8e93e3a47da5455e64118 2385 utils optional fuse3_3.14.0-5.dsc 62f1e1d4ed18e760a6f7c04f14cbf535 17860 utils optional fuse3_3.14.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmWhYSMACgkQ3OMQ54ZM
Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
Hi Julian! On 2024-01-12 01:47, Julian Andres Klode wrote: > Either way, these are harmless I'm not saying they're harmful, what I'm saying is: 1) the errors you see on armhf when building apt without stack-clash-protection are the same valgrind reports on amd64 as well. Hence, you could consider rebuilding apt without stack-clash-protection on armhf and dropping the armhf conditional in test/integration/test-apt-update-simple 2) if you run valgrind in CI, I think you should probably use --error-exitcode. Otherwise, what's the point of using valgrind at all, if you don't fail when it reports errors? :-) This is not directly relevant to #1060251 of course, I'm happy to file a separate bug against apt if you find that useful.
Bug#1058192: marked as done (debiancontributors: FTBFS: AttributeError: 'TestTypes' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)
Your message dated Fri, 12 Jan 2024 15:49:10 +
with message-id
and subject line Bug#1058192: fixed in debiancontributors 0.7.9-1
has caused the Debian Bug report #1058192,
regarding debiancontributors: FTBFS: AttributeError: 'TestTypes' object has no
attribute 'assertEquals'. Did you mean: 'assertEqual'?
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.)
--
1058192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debiancontributors
Version: 0.7.8-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> I: pybuild base:310: /usr/bin/python3 setup.py build
> COLUMNS=200 help2man --name='Manage contributions to contributors.debian.org'
> --section=1 --version-string="0.7.8" --no-info ./dc-tool > dc-tool.1
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_debiancontributors/build; python3.12
> -m unittest discover -v
> /<>/.pybuild/cpython3_3.12_debiancontributors/build/test/test_submission.py:75:
> SyntaxWarning: invalid escape sequence '\('
> self.assertRegexpMatches(s.auth_token, "setup\(")
> /<>/.pybuild/cpython3_3.12_debiancontributors/build/test/test_submission.py:81:
> SyntaxWarning: invalid escape sequence '\('
> self.assertRegexpMatches(s.auth_token, "setup\(")
> test_gitdirs (test.test_mine_bts.TestMineBts.test_gitdirs)
> Test gitdirs scanner ...
> /<>/.pybuild/cpython3_3.12_debiancontributors/build/debiancontributors/scanners/bts.py:58:
> ResourceWarning: unclosed file <_io.BufferedReader name=5>
> scan.scan_dir(d)
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /<>/.pybuild/cpython3_3.12_debiancontributors/build/debiancontributors/scanners/bts.py:58:
> ResourceWarning: unclosed file <_io.BufferedReader name=7>
> scan.scan_dir(d)
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> ok
> test_email_scanner (test.test_mine_email.TestMineEmail.test_email_scanner)
> Test email scanner ... ok
> test_gitdirs (test.test_mine_git.TestMineGit.test_gitdirs)
> Test gitdirs scanner ... ok
> test_gitlogs (test.test_mine_git.TestMineGit.test_gitlogs)
> Test gitlogs scanner ... skipped 'no idea where to find my git repo when not
> run from the git checkout'
> test_gitlogs_authormap (test.test_mine_git.TestMineGit.test_gitlogs_authormap)
> Test gitlogs scanner ... skipped 'no idea where to find my git repo when not
> run from the git checkout'
> testGetKey (test.test_parser.TestParser.testGetKey) ... ERROR
> testGetKeyDateOrNone (test.test_parser.TestParser.testGetKeyDateOrNone) ...
> ERROR
> testGetKeyInt (test.test_parser.TestParser.testGetKeyInt) ... ERROR
> testGetKeySequence (test.test_parser.TestParser.testGetKeySequence) ... ERROR
> testGetKeySequenceOrObject
> (test.test_parser.TestParser.testGetKeySequenceOrObject) ... ERROR
> testGetKeyString (test.test_parser.TestParser.testGetKeyString) ... ERROR
> testGetKeyUnicode (test.test_parser.TestParser.testGetKeyUnicode) ... ERROR
> testFullData (test.test_submission.TestSubmission.testFullData) ... ERROR
> testIdentifier (test.test_submission.TestSubmission.testIdentifier) ... ERROR
> testMinimalData (test.test_submission.TestSubmission.testMinimalData) ...
> ERROR
> test_auth_token (test.test_submission.TestSubmission.test_auth_token) ...
> skipped 'no idea where to find my setup.py when not run from the git checkout'
> test_auto (test.test_types.TestTypes.test_auto) ... ERROR
> test_bad_contribution (test.test_types.TestTypes.test_bad_contribution) ... ok
> test_bad_identifier (test.test_types.TestTypes.test_bad_identifier) ... ok
> test_identifier (test.test_types.TestTypes.test_identifier)
> Test Identifier operations ... ERROR
>
> ==
> ERROR: testGetKey (test.test_parser.TestParser.testGetKey)
> --
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.12_debiancontributors/build/test/test_parser.py",
> line 26, in testGetKey
> self.assertEquals(parser.get_key({"foo": "bar"}, "foo"), "bar")
> ^
> AttributeError: 'TestParser' object has no
Bug#1037883: marked as done (vimix: ftbfs with GCC-13)
Your message dated Fri, 12 Jan 2024 15:36:02 + with message-id and subject line Bug#1037883: fixed in vimix 0.7.2+git20221123+ds-2 has caused the Debian Bug report #1037883, regarding vimix: ftbfs with GCC-13 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.) -- 1037883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vimix Version: 0.7.2+git20221123+ds-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/vimix_0.7.2+git20221123+ds-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] from /<>/src/main.cpp:27: /<>/src/Scene.h:135:27: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 135 | struct hasId: public std::unary_function | ^~ In file included from /usr/include/c++/13/string:49, from /<>/src/Settings.h:5, from /<>/src/main.cpp:26: /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ In file included from /<>/src/Primitives.h:6, from /<>/src/Scene.cpp:31: /<>/src/Scene.h:135:27: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 135 | struct hasId: public std::unary_function | ^~ In file included from /usr/include/c++/13/bits/refwrap.h:39, from /usr/include/c++/13/bits/shared_ptr_base.h:57, from /usr/include/c++/13/bits/shared_ptr.h:53, from /usr/include/c++/13/condition_variable:45, from /usr/include/c++/13/future:41, from /<>/src/Shader.h:4, from /<>/src/Scene.cpp:30: /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ In file included from /<>/src/GarbageVisitor.h:6, from /<>/src/Scene.cpp:33: /<>/src/Source.h:203:33: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 203 | struct hasNode: public std::unary_function | ^~ /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ /<>/src/Source.h:211:33: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 211 | struct hasName: public std::unary_function | ^~ /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ /<>/src/Source.h:221:31: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 221 | struct hasId: public std::unary_function | ^~ /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ /<>/src/Source.h:231:34: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 231 | struct hasDepth: public std::unary_function | ^~ /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |
Bug#1056423: [Help] Started to replace future but failed
Am Fri, Jan 12, 2024 at 11:45:02AM +0100 schrieb Alexandre Detiste: > > -class ExtensionNode(with_metaclass(ExtensionNodeMetaclass, object)): > +class ExtensionNode(metaclass=ExtensionNodeMetaclass, object_=True): > > Just simply > +class ExtensionNode(metaclass=ExtensionNodeMetaclass): > , but I can't test here: This helped a bit further. Unfortunately we have *lots* of instances of from past.utils import old_div with several instances of old_div inside the code. Do you know some automated tool to fix this? Replacing all these seems pretty error prone. Kind regards Andreas. -- http://fam-tille.de
Bug#1060432: [Python-modules-team] Bug#1060432: rpds-py ftbfs in unstable
Le 11/01/2024 à 10:27, Matthias Klose a écrit : Package: src:rpds-py Version: 0.12.0-2 Severity: serious Tags: sid trixie ftbfs rpds-py ftbfs in unstable, because of missing build dependencies: Issues preventing migration: ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-archery-dev ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-rpds-dev I just uploaded these two packages to NEW, along with a third one on the dependency chain. Roland.
Bug#1058344: marked as done (python-ocspbuilder: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 12 Jan 2024 14:34:42 +
with message-id
and subject line Bug#1056489: fixed in python-ocspbuilder 0.10.2-3
has caused the Debian Bug report #1056489,
regarding python-ocspbuilder: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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.)
--
1056489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ocspbuilder
Version: 0.10.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_ocspbuilder
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/ocspbuilder
> copying ocspbuilder/__init__.py -> build/lib/ocspbuilder
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/ocspbuilder
> copying build/lib/ocspbuilder/__init__.py ->
> build/bdist.linux-x86_64/wheel/ocspbuilder
> running install_egg_info
> running egg_info
> creating ocspbuilder.egg-info
> writing ocspbuilder.egg-info/PKG-INFO
> writing dependency_links to ocspbuilder.egg-info/dependency_links.txt
> writing requirements to ocspbuilder.egg-info/requires.txt
> writing top-level names to ocspbuilder.egg-info/top_level.txt
> writing manifest file 'ocspbuilder.egg-info/SOURCES.txt'
> reading manifest file 'ocspbuilder.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'ocspbuilder.egg-info/SOURCES.txt'
> Copying ocspbuilder.egg-info to
> build/bdist.linux-x86_64/wheel/ocspbuilder-0.10.2.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/ocspbuilder-0.10.2.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.12_ocspbuilder/.tmp-cgzi2y50/ocspbuilder-0.10.2-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'ocspbuilder/__init__.py'
> adding 'ocspbuilder-0.10.2.dist-info/LICENSE'
> adding 'ocspbuilder-0.10.2.dist-info/METADATA'
> adding 'ocspbuilder-0.10.2.dist-info/WHEEL'
> adding 'ocspbuilder-0.10.2.dist-info/top_level.txt'
> adding 'ocspbuilder-0.10.2.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built ocspbuilder-0.10.2-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_ocspbuilder
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/ocspbuilder
> copying build/lib/ocspbuilder/__init__.py ->
> build/bdist.linux-x86_64/wheel/ocspbuilder
> running install_egg_info
> running egg_info
> writing ocspbuilder.egg-info/PKG-INFO
> writing dependency_links to ocspbuilder.egg-info/dependency_links.txt
> writing requirements to ocspbuilder.egg-info/requires.txt
> writing top-level names to ocspbuilder.egg-info/top_level.txt
> reading manifest file 'ocspbuilder.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'ocspbuilder.egg-info/SOURCES.txt'
> Copying ocspbuilder.egg-info to
> build/bdist.linux-x86_64/wheel/ocspbuilder-0.10.2.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/ocspbuilder-0.10.2.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.11_ocspbuilder/.tmp-n6uimoh9/ocspbuilder-0.10.2-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'ocspbuilder/__init__.py'
> adding
Bug#1060266: [Pkg-auth-maintainers] Some help for coordinated uploads needed
Hi Florian, On 12.01.24 at 12:08, Florian Schlichting: I would like to do an upload of yubikey-manager very soon in order to fix #1060266 (serious) in python3-ykman. Can we perhaps do an upload of python-fido2 to unstable in the course of this weekend? Do you want to do that yourself, so you can update solo1-cli at the same time, or are you ok with me going ahead and you follow with solo1-cli whenever convenient? sure, please go ahead. Just ping me, once you uploaded phython-fido2 to unstable so I can upload solo1-cli afterwards. Thanks for all the preparation! Philip OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056489: marked as done (python-ocspbuilder's autopkg tests fail with Python 3.12)
Your message dated Fri, 12 Jan 2024 14:34:42 + with message-id and subject line Bug#1056489: fixed in python-ocspbuilder 0.10.2-3 has caused the Debian Bug report #1056489, regarding python-ocspbuilder's autopkg tests fail with Python 3.12 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.) -- 1056489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-ocspbuilder Version: 0.10.2-2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 python-ocspbuilder's autopkg tests fail with Python 3.12: [...] 337s = test session starts == 337s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0 337s rootdir: /tmp/autopkgtest.OWWyB9/autopkgtest_tmp 337s collected 9 items 337s 337s tests/test_ocsp_request_builder.py .. [ 22%] 337s tests/test_ocsp_response_builder.py ...F... [100%] 337s 337s === FAILURES === 337s __ OCSPResponseBuilderTests.test_build_no_certificate __ 337s 337s self = testMethod=test_build_no_certificate> 337s 337s def test_build_no_certificate(self): 337s issuer_key = asymmetric.load_private_key(os.path.join(fixtures_dir, 'test.key')) 337s issuer_cert = asymmetric.load_certificate(os.path.join(fixtures_dir, 'test.crt')) 337s subject_cert = asymmetric.load_certificate(os.path.join(fixtures_dir, 'test-inter.crt')) 337s 337s > with self.assertRaisesRegexp(ValueError, 'must be set if the response_status is "successful"'): 337s E AttributeError: 'OCSPResponseBuilderTests' object has no attribute 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'? 337s 337s tests/test_ocsp_response_builder.py:65: AttributeError 337s === short test summary info 337s FAILED tests/test_ocsp_response_builder.py::OCSPResponseBuilderTests::test_build_no_certificate 337s = 1 failed, 8 passed in 0.12s == --- End Message --- --- Begin Message --- Source: python-ocspbuilder Source-Version: 0.10.2-3 Done: Michael Fladischer We believe that the bug you reported is fixed in the latest version of python-ocspbuilder, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated python-ocspbuilder package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 13:31:04 + Source: python-ocspbuilder Architecture: source Version: 0.10.2-3 Distribution: unstable Urgency: low Maintainer: Debian Python Team Changed-By: Michael Fladischer Closes: 1056489 Changes: python-ocspbuilder (0.10.2-3) unstable; urgency=low . * Add patch to replace assertRaisesRegexp with assertRaisesRegex (Closes: #1056489). * Update year in d/copyright. Checksums-Sha1: 094e78367b2721b20879abe3a7968c0b76775fad 1885 python-ocspbuilder_0.10.2-3.dsc 7ad04d4c8e611fe4a7c8975220e76c0728e67114 2972 python-ocspbuilder_0.10.2-3.debian.tar.xz 7b55cede2c5a572500b62c5a76de9c35d76e26d6 7008 python-ocspbuilder_0.10.2-3_arm64.buildinfo Checksums-Sha256: 7eb707eaba2667350f9ca0e3f8eb9122ad0ba8db0c283389fd7753575b75c41d 1885 python-ocspbuilder_0.10.2-3.dsc bacca0965ef870a5e35c66224eb114b78a590e95ce3ed402c3842548201a103f 2972 python-ocspbuilder_0.10.2-3.debian.tar.xz 8a2bf23e51d952cd74013d2beaaaef6ecf17184e407474117f7ca487992e58d2 7008 python-ocspbuilder_0.10.2-3_arm64.buildinfo Files: 69c6b2151e3fc1b1c1c50f682a68d91b 1885 python optional python-ocspbuilder_0.10.2-3.dsc 43bc22be7bb9e0d3ecf9de3cf2bddd68 2972 python optional python-ocspbuilder_0.10.2-3.debian.tar.xz 9e5d15b9135f400a9bae01dcce3a0080 7008 python optional python-ocspbuilder_0.10.2-3_arm64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmWhP/EACgkQ/9PIi5l9 0WrvwQgAhCIWli8uwcExrFw+SB+ANyciVnoBYLkhYn082uuRCpn0ONElwIXXW1ut
Bug#1058997: flask-autoindex is incompatible with Py3.12
control: -1 tag +patch Please apply this patch and remove "python3-future ," from debian/control. Greetings remove-future Description: Binary data
Bug#1060671: libdbd-oracle-perl: requires rebuild for perl 5.38
Source: libdbd-oracle-perl Version: 1.83-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org The perl 5.38 has started. Since libdbd-oracle-perl is in contrib and not auto-buildable, it requires a manual rebuild on amd64 and i386. Cheers -- Sebastian Ramacher
Processed: merging 1056489 1058344
Processing commands for cont...@bugs.debian.org:
> merge 1056489 1058344
Bug #1056489 [src:python-ocspbuilder] python-ocspbuilder's autopkg tests fail
with Python 3.12
Bug #1056489 [src:python-ocspbuilder] python-ocspbuilder's autopkg tests fail
with Python 3.12
Added tag(s) ftbfs.
Bug #1058344 [src:python-ocspbuilder] python-ocspbuilder: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Merged 1056489 1058344
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056489
1058344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1058125
Processing commands for cont...@bugs.debian.org: > # Fixed by src:hypercorn-0.16.0-1. > close 1058125 Bug #1058125 [src:hypercorn] hypercorn: FTBFS: make[1]: *** [debian/rules:17: execute_before_dh_sphinxdoc] Error 2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060429: marked as done (solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py)
Your message dated Fri, 12 Jan 2024 13:05:46 + with message-id and subject line Bug#1060429: fixed in python-django-solo 2.1.0-2 has caused the Debian Bug report #1060429, regarding solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py 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.) -- 1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solo1-cli Version: 0.1.1-5 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-django-solo solo1-cli has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/solo/__init__.py is contained in the packages * python3-django-solo/2.1.0-1 as present in unstable * solo1-cli/0.1.1-5 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: python-django-solo Source-Version: 2.1.0-2 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of python-django-solo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated python-django-solo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jan 2024 12:03:59 +0100 Source: python-django-solo Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jérémy Lal Closes: 1060429 Changes: python-django-solo (2.1.0-2) unstable; urgency=medium . * Rename solo to django_solo. Closes: #1060429. * Comment about copyright owner Checksums-Sha1: 0367651cb2bcd352d95da1a2da7280d927cc46a2 2171 python-django-solo_2.1.0-2.dsc a300f0b92e20e0670b01bfbbd1facd48dd8c6b2d 9248 python-django-solo_2.1.0-2.debian.tar.xz d35ac9e921b407f57c8d6c6fcb24584278f8b376 8718 python-django-solo_2.1.0-2_source.buildinfo Checksums-Sha256: 25655861d4d09761a8dfc393e15292bbfec67a22739556cfa547892466616d2b 2171 python-django-solo_2.1.0-2.dsc 14ced36615b369423fe6134da64a2845fcf2f6dba150a21dcb9f39e558354b39 9248 python-django-solo_2.1.0-2.debian.tar.xz 2c2e28f2e6399905f3f8d98c3982e94915c1b96600fc0dd6f13b89f873a133df 8718 python-django-solo_2.1.0-2_source.buildinfo Files: ab9ddb645b097b4f84f17cbfabaf2aa4 2171 python optional python-django-solo_2.1.0-2.dsc eabf8089103708d809eec8405488d1a4 9248 python optional python-django-solo_2.1.0-2.debian.tar.xz b41e8f743ab2d056fed1e9061b95098e 8718 python optional python-django-solo_2.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmWhNpMSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0RJcP/jqlpru2vP+VxsVf1qoJxezQCD++BD29 +8Fct+U92F/cqZcIQRNf9JlIzZP2ZMdaoG/oINeM0JzbYRtoUNr7Ovhrn4IBg9jw YAAWZesV5GskIUqBLIe92OPKqkIYYJklN5g9ANSSc4wqYnBucLywhu/w5MSb678k FdkLaJeA1VWjKosR1ZGT2Vxu8+i44IPGLLYrb11eY8ahFc5Hi7g1RHILwsvGoTuW SvAoKQVIT0zV6O9uSObIqtfxXy9KeAJjcifOvsQBty5TWWFcqasGHSXC6K+YtrVX aEnb+LrBGip26PlQkgE6FSh1QfPj/99vxE1CTLQ9KZrEft8k/fmjdi19gXsGPHaO 4xwymTCCI4uIYZGvEoXy6viezVtSn9IZRrUAMqAlCIshBtpN5OGS+orQKSRNkRBg 5ge57ZGPoS78JCi6ScZllg+LOntWTc6zpdhTOlVxWTRpbvgD8gqeckiqf4Kz+2Hg blKhvPCn1izu4TiiiQDv7XPU4f9DZ4aYxU3DB1Gwnt4vUyav8WAL16p5vx1C7B0s 5sZtfA1BULZrfPesfd3nkgPB0t0aybIoi8jJ5PQsKogh6ojDk9wGsdeOav3ewMY6 FPnFxEzkIBDspqQDONpBzIaOaOITjigUZT5/Gxv1+D2AlONQMGC68uFLJwjdGe66 fWhpb/3FmGN2 =ClPn -END PGP SIGNATURE End Message ---
Processed: merging 1056469 1058333
Processing commands for cont...@bugs.debian.org:
> merge 1056469 1058333
Bug #1056469 [src:python-docformatter] python-docformatter's autopkg tests fail
with Python 3.12
Bug #1056469 [src:python-docformatter] python-docformatter's autopkg tests fail
with Python 3.12
Added tag(s) ftbfs.
Bug #1058333 [src:python-docformatter] python-docformatter: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12
3.11" returned exit code 13
Merged 1056469 1058333
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056469
1058333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
On Thu, Jan 11, 2024 at 10:18:58PM +0100, Emanuele Rocca wrote:
> Hi Julian,
>
> On 2024-01-11 05:46, Julian Andres Klode wrote:
> > And there aren't any hard errors. We could zero initialize
> > those or add supressions to make things look nicer I suppose.
>
> Mmmh no, they are all actual errors as far as valgrind is concerned.
>
> The thing is, you're running valgrind without --error-exitcode. By doing
> so, the exit code of your tests is the exit code of apt-get, not of
> valgrind.
>
> Try this instead:
>
> (sid-amd64)root@ariel:~# valgrind --error-exitcode=1 apt-get update
> [...]
> ==308534== ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0)
> (sid-amd64)root@ariel:~# echo $?
> 1
That's all just strawman arguments.
As said before, these aren't the issue. These all occur in locations
where we read the entire memory arena of our allocator, either for
hashing or writing it to a file.
While they _should_ be zero-initialized if you look at the code, we
actually initialize things with a header object. The problem is the
header object looks like:
uint32_t magic;
uint16_t major;
uint16_t minor;
bool dirty;
uint16_t boo;
And the padding bytes are never initialized but will inevitably
be read by the hashing and write back of the entire arena.
We can fix these errors by either zero initializing the padding in
the object constructor:
diff --git a/apt-pkg/pkgcache.cc b/apt-pkg/pkgcache.cc
index 76336b9b3..b845cb13c 100644
--- a/apt-pkg/pkgcache.cc
+++ b/apt-pkg/pkgcache.cc
@@ -52,6 +52,7 @@ using APT::StringView;
/* Simply initialize the header */
pkgCache::Header::Header()
{
+ memset(this, 0, sizeof(*this));
#define APT_HEADER_SET(X,Y) X = Y;
static_assert(std::numeric_limits::max() > Y, "Size violation
detected in pkgCache::Header")
APT_HEADER_SET(Signature, 0x98FE76DC);
or by not creating a header on the stack (with uninitialized padding) and then
copying
it in, by using placement new operator:
diff --git a/apt-pkg/pkgcachegen.cc b/apt-pkg/pkgcachegen.cc
index 9e47ef369..3a85a9585 100644
--- a/apt-pkg/pkgcachegen.cc
+++ b/apt-pkg/pkgcachegen.cc
@@ -89,7 +89,7 @@ bool pkgCacheGenerator::Start()
Map.UsePools(*Cache.HeaderP->Pools,sizeof(Cache.HeaderP->Pools)/sizeof(Cache.HeaderP->Pools[0]));
// Starting header
- *Cache.HeaderP = pkgCache::Header();
+ new (Cache.HeaderP) pkgCache::Header();
// make room for the hashtables for packages and groups
if (Map.RawAllocate(2 * (Cache.HeaderP->GetHashTableSize() *
sizeof(map_pointer))) == 0)
Either way, these are harmless
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Bug#1060323: libosp-dev: missing dependency on libosp5
On Fri, 12 Jan 2024 07:21:14 -0500, Neil Roeth wrote: > I took the second approach suggested by Gregor, of changing the install > order. Massive rewrite of d/rules to happen at a later date. :-) Thanks for the quick upload! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1060323: libosp-dev: missing dependency on libosp5
I took the second approach suggested by Gregor, of changing the install order. Massive rewrite of d/rules to happen at a later date. :-) -- Neil Roeth
Bug#1055713: marked as done (python-http-parser ftbfs with Python 3.12)
Your message dated Fri, 12 Jan 2024 12:05:09 +
with message-id
and subject line Bug#1055713: fixed in python-http-parser 0.9.0+ds-1
has caused the Debian Bug report #1055713,
regarding python-http-parser ftbfs with Python 3.12
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.)
--
1055713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-http-parser
Version: 0.9.0-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
[...]
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 8, in
from imp import load_source
ModuleNotFoundError: No module named 'imp'
E: pybuild pybuild:395: clean: plugin distutils failed with: exit
code=1: python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
returned exit code 13
--- End Message ---
--- Begin Message ---
Source: python-http-parser
Source-Version: 0.9.0+ds-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
python-http-parser, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated python-http-parser
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 12 Jan 2024 12:50:48 +0100
Source: python-http-parser
Architecture: source
Version: 0.9.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1048725 1055713
Changes:
python-http-parser (0.9.0+ds-1) unstable; urgency=medium
.
* Team upload.
* Replace imp which is deprecated in Python3.12 by importlib
Closes: #1055713
* d/copyright: Remove binary cruft from upstream tarball and
while doing so also auto-generated *.c source
Closes: #1048725
* Testsuite: autopkgtest-pkg-python (routine-update)
* Remove trailing whitespace in debian/copyright (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
* Rules-Requires-Root: no (routine-update)
* watch file standard 4 (routine-update)
Checksums-Sha1:
b61540f5339b0152ed798da5e5d67d9f77605c97 2178 python-http-parser_0.9.0+ds-1.dsc
afc1ca485afcbc22d1a1b134fd6b3582fa344029 30420
python-http-parser_0.9.0+ds.orig.tar.xz
074b2a83aadc5f08598da03c2b15553cd0f8d82a 4228
python-http-parser_0.9.0+ds-1.debian.tar.xz
2623c5f6a3dcd6776563b7a9200fde7fc2040533 7884
python-http-parser_0.9.0+ds-1_amd64.buildinfo
Checksums-Sha256:
5397607da092b143e09b76d9c1287f76108b91e3316ebb4028bc74db7ac5a75d 2178
python-http-parser_0.9.0+ds-1.dsc
2094e89ed00deefcd33574adca0e518fd504520b3ee4c17afe6598b9d3152ae8 30420
python-http-parser_0.9.0+ds.orig.tar.xz
d3c707988d9f33109cc4547531bb2394b38bb1fcc1bf2a71f9a777521e47820f 4228
python-http-parser_0.9.0+ds-1.debian.tar.xz
313a0d41c7ea989dc15397115d4b0265c058e986d66f8f1f86096eaee1afaebb 7884
python-http-parser_0.9.0+ds-1_amd64.buildinfo
Files:
8b83ea3b0f43870fa6f7c0cffae33933 2178 python optional
python-http-parser_0.9.0+ds-1.dsc
0a2fb9f859565c0878bc09e3f1cffd38 30420 python optional
python-http-parser_0.9.0+ds.orig.tar.xz
5cff0494555cc7be7ac2c416c823bdf9 4228 python optional
python-http-parser_0.9.0+ds-1.debian.tar.xz
2bc208259c8714d155ae4cc6d50ac650 7884 python optional
python-http-parser_0.9.0+ds-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWhKCURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF8Vg/9HDrZBLq5x203t5/UKzyON/qy/9DdGgmB
KbiNgpyzCVGlIr8UmIkNf8vKgUZqnGwNSLYr4/7qjOZyknd4qI9yF8kzss/HqWt9
oAj1fcA6SPDwRalC4QwHaAJeGk1+P3TkH/TOJK9ZMgkwjBKFVIF7e/pNcttcRVHz
G5tdq9L85V67M38YKp53ft3tnoaYZ984e+iPZe3DAtQLf8TMkWxgZjA5Mo6NV4RO
KinJcVi1pnPM4gmpO4RHp6j9m+J0Md9/ruMmqEc9PyD+DOEx5OVuUCIbcYLlmjh0
WlaCmh1CnxRkFiFmqNjYOSJgQ0TXaZlNOUAJ3cWamVPQ/JCOH1GZ4wddj+iqW5/D
1LPRTsQ3rDwBR4UW+B2V6Zh6k6Rb2xaRfXPkNox7EXjnWQhuDQBknZBTL35bytO3
Processed: closing 1056467
Processing commands for cont...@bugs.debian.org: > # Fixed by src:python-xmlschema-1.10.0-7. > close 1056467 Bug #1056467 [src:python-djangosaml2] python-djangosaml2's autopkg tests fail with Python 3.12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1058194
Processing commands for cont...@bugs.debian.org: > # Fixed by src:python-xmlschema-1.10.0-7. > close 1058194 Bug #1058194 [src:python-djangosaml2] python-djangosaml2: FTBFS: AttributeError: type object '_PurePosixPath' has no attribute '_from_parts'. Did you mean: '_load_parts'? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
Hi, can you confirm two additional things please: 1) this happens only on the large host? 2) this does not or does happen with other packages also requesting the same settings from systemd, e.g. dnsdist or pdns-recursor? Chris
Bug#1060266: [Pkg-auth-maintainers] Some help for coordinated uploads needed
Hi Philip, On Sun, Dec 24, 2023 at 10:25:21PM +0100, Philip Rinn wrote: > things changed a bit - Arch Linux picked up my patch and I think with > testing in two distributions, we will have enough momentum to get possible > bugs ironed out. > > I'll prepare an upload of solo1-cli with my patch targeting experimental > during the next days. I hope this makes it possible to push the transition > forward during January. I would like to do an upload of yubikey-manager very soon in order to fix #1060266 (serious) in python3-ykman. Can we perhaps do an upload of python-fido2 to unstable in the course of this weekend? Do you want to do that yourself, so you can update solo1-cli at the same time, or are you ok with me going ahead and you follow with solo1-cli whenever convenient? Best, Florian
Bug#1056423: [Help] Started to replace future but failed
Ok I'll pick it up this evening ! -class ExtensionNode(with_metaclass(ExtensionNodeMetaclass, object)): +class ExtensionNode(metaclass=ExtensionNodeMetaclass, object_=True): Just simply +class ExtensionNode(metaclass=ExtensionNodeMetaclass): , but I can't test here: Greetings Le ven. 12 janv. 2024 à 11:36, Andreas Tille a écrit : > > Control: tags -1 help > > Hi Alexandre, > > I started to follow your hint to replace future inside the > code but I'm obviously struck as you can see in Salsa-CI[1]. > > Any help would be welcome (please also review my patch since > I'm not sure about all changes). > > Kind regards >Andreas. > > [1] https://salsa.debian.org/python-team/packages/mdp/-/jobs/5148982 > > -- > http://fam-tille.de
Bug#1060665: orphan-sysvinit-scripts: needs to ship /etc/init.d/
Package: orphan-sysvinit-scripts Version: 0.15 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. Actually installing orphan-sysvinit-scripts succeeds, but trigger processing after a subsequent installation of rsyslog fails. >From the attached log (scroll to the bottom...): + apt-get -yf --force-yes -t sid install orphan-sysvinit-scripts=0.15 rsyslog=8.2312.0-3 Reading package lists... Building dependency tree... Reading state information... orphan-sysvinit-scripts is already the newest version (0.15). The following additional packages will be installed: libestr0 libfastjson4 liblognorm5 Suggested packages: rsyslog-mysql | rsyslog-pgsql rsyslog-mongodb rsyslog-doc rsyslog-openssl | rsyslog-gnutls rsyslog-gssapi rsyslog-relp Recommended packages: logrotate The following NEW packages will be installed: libestr0 libfastjson4 liblognorm5 rsyslog 0 upgraded, 4 newly installed, 0 to remove and 14 not upgraded. Need to get 832 kB of archives. After this operation, 2312 kB of additional disk space will be used. Get:1 http://ftp.de.debian.org/debian trixie/main amd64 libestr0 amd64 0.1.11-1 [9204 B] Get:2 http://ftp.de.debian.org/debian trixie/main amd64 libfastjson4 amd64 1.2304.0-1 [28.9 kB] Get:3 http://ftp.de.debian.org/debian trixie/main amd64 liblognorm5 amd64 2.0.6-4 [67.2 kB] Get:4 http://ftp.de.debian.org/debian sid/main amd64 rsyslog amd64 8.2312.0-3 [727 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 832 kB in 0s (30.5 MB/s) Selecting previously unselected package libestr0:amd64. Preparing to unpack .../libestr0_0.1.11-1_amd64.deb ... Unpacking libestr0:amd64 (0.1.11-1) ... Selecting previously unselected package libfastjson4:amd64. Preparing to unpack .../libfastjson4_1.2304.0-1_amd64.deb ... Unpacking libfastjson4:amd64 (1.2304.0-1) ... Selecting previously unselected package liblognorm5:amd64. Preparing to unpack .../liblognorm5_2.0.6-4_amd64.deb ... Unpacking liblognorm5:amd64 (2.0.6-4) ... Selecting previously unselected package rsyslog. Preparing to unpack .../rsyslog_8.2312.0-3_amd64.deb ... Unpacking rsyslog (8.2312.0-3) ... Setting up libestr0:amd64 (0.1.11-1) ... Setting up libfastjson4:amd64 (1.2304.0-1) ... Setting up liblognorm5:amd64 (2.0.6-4) ... Setting up rsyslog (8.2312.0-3) ... Processing triggers for libc-bin (2.37-13) ... Processing triggers for orphan-sysvinit-scripts (0.15) ... Creating config file /etc/init.d/rsyslog with new version cp: cannot create regular file '/etc/init.d/rsyslog': No such file or directory dpkg: error processing package orphan-sysvinit-scripts (--configure): installed orphan-sysvinit-scripts package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: orphan-sysvinit-scripts W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Sub-process /usr/bin/dpkg returned an error code (1) + apt-get -yf --force-yes install orphan-sysvinit-scripts=0.15 rsyslog=8.2312.0-3 Reading package lists... Building dependency tree... Reading state information... orphan-sysvinit-scripts is already the newest version (0.15). rsyslog is already the newest version (8.2312.0-3). 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up orphan-sysvinit-scripts (0.15) ... Creating config file /etc/init.d/rsyslog with new version cp: cannot create regular file '/etc/init.d/rsyslog': No such file or directory dpkg: error processing package orphan-sysvinit-scripts (--configure): installed orphan-sysvinit-scripts package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: orphan-sysvinit-scripts W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Sub-process /usr/bin/dpkg returned an error code (1) /etc/init.d/ no longer seems to be shipped by any dependent package. Please ship /etc/init.d/ as an empty directory s.t. dkpg knows ownership and takes care of creation and removal and proper refcounting. Please do *not* manage creation manually in maintainer scripts. cheers, Andreas orphan-sysvinit-scripts=0.15_rsyslog=8.2312.0-3.log.gz Description: application/gzip
Processed: [Help] Started to replace future but failed
Processing control commands: > tags -1 help Bug #1056423 [src:mdp] mdp's autopkg tests fail with Python 3.12 Added tag(s) help. -- 1056423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056423: [Help] Started to replace future but failed
Control: tags -1 help Hi Alexandre, I started to follow your hint to replace future inside the code but I'm obviously struck as you can see in Salsa-CI[1]. Any help would be welcome (please also review my patch since I'm not sure about all changes). Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/mdp/-/jobs/5148982 -- http://fam-tille.de
Bug#1060429: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
I've reassigned it to solo1-cli, because I thought it wasn't a library (and the start of the docs lead me to it), but actually it is a library. My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.
Processed: reassign 1060429 to python-django-solo
Processing commands for cont...@bugs.debian.org: > reassign 1060429 python-django-solo Bug #1060429 [solo1-cli] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py Bug reassigned from package 'solo1-cli' to 'python-django-solo'. Ignoring request to alter found versions of bug #1060429 to the same values previously set Ignoring request to alter fixed versions of bug #1060429 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1060429 to solo1-cli
Processing commands for cont...@bugs.debian.org: > reassign 1060429 solo1-cli Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py Bug reassigned from package 'python-django-solo' to 'solo1-cli'. No longer marked as found in versions python3-django-solo/2.1.0-1 and 2.1.0-1. Ignoring request to alter fixed versions of bug #1060429 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060285: mptcpd: FTBFS with a segmentation fault in the testsuite when SCTP disabled and no /etc/protocols
Hi Aurélien, On 10/01/2024 19:13, Matthieu Baerts wrote: > On 08/01/2024 21:18, Aurelien Jarno wrote: (...) >> In the latest rebuild of mptpcd, the conditions where met only on the >> riscv64 buildd, and riscv64 is not a release architecture. That said a >> few mips64el buildds also met the 3 conditions and it will be the case >> of more and more buildds once they are upgraded to bookworm. I am >> therefore filling this issue as severity serious. > > Many thanks for the explanation! > > I will wait for the different pipelines to be over, before sending a new > version to mentors.debian.net! This new version has been sent to mentors.debian.net: https://mentors.debian.net/package/mptcpd/ https://mentors.debian.net/debian/pool/main/m/mptcpd/mptcpd_0.12-3.dsc (I guess I will need to prepare a v0.12-4 because of #1060476) Cheers, Matt -- Sponsored by the NGI0 Core fund.
Processed: severity of 1059922 is important
Processing commands for cont...@bugs.debian.org: > severity 1059922 important Bug #1059922 [nut-server] nut-server: upsd fails to start since version 2.8.1 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059922: nut-server: upsd fails to start since version 2.8.1
severity 1059922 important thanks > Dear Laurent Bigonville, Hello Jörg, > with version 2.8.0-7 an EATON UPS connected to a debian computer via > USB was working in standalone mode as expected. The only change in the > config files was in /etc/nut/ups.conf where I added the following lines: > > [Eaton] > driver = usbhid-ups > port = auto > vendorid = 0463 > pollfreq = 30 > > After the upgrade to version 2.8.1-1 the upsd daemon would fail to > start. The output in /var/log/syslog is > > upsd[12132]: not listening on ::1 port 3493 > upsd[12132]: listening on 127.0.0.1 port 3493 > upsd[12132]: no listening interface available > > instead of > > upsd[12553]: listening on 127.0.0.1 port 3493 > upsd[12553]: not listening on ::1 port 3493 > upsd[12553]: Connected to UPS [Eaton]: usbhid-ups-Eaton > upsd[12555]: Startup successful > > for the working version 2.8.0. > Any ideas? Could you please attach the other configuration files here (please check for clear-text passwords)? Do you have the loopback (127.0.0.1/::1) interface properly working? I cannot reproduce this at home where I have also an EATON UPS Kind regards, Laurent Bigonville
Processed: netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move
Processing control commands: > affects -1 + netplan.io Bug #1060661 [netplan-generator] netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move Added indication that 1060661 affects netplan.io -- 1060661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
Processing control commands: > found -1 python3-django-solo/2.1.0-1 Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py The source python3-django-solo and version 2.1.0-1 do not appear to match any binary packages Marked as found in versions python3-django-solo/2.1.0-1. > affects -1 = solo1-cli Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py Removed indication that 1060429 affects python3-django-solo Added indication that 1060429 affects solo1-cli -- 1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060429: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py
Control: found -1 python3-django-solo/2.1.0-1 Control: affects -1 = solo1-cli Philip Rinn wrote: > thanks for the bug report, but I guess you missed that solo1-cli.ships this > file for years (in stable, testing, unstable) while python-django-solo was > just uploaded yesterday. So I think the bug is in python-django-solo actually. I concur. I am not sure how this got misdetected. Presumably, the heuristic concluded that since solo1-cli from experimental was conflicting with a package from unstable that it must be the cause. I'll have to see how I can avoid future misdetections of the same kind. Sorry for the noise. Helmut
Bug#1060661: netplan-generator: ineffective Replaces for /usr/lib/systemd/system-generators/netplan due to /usr-move
Package: netplan-generator Version: 0.107.1-1 Severity: serious Justification: file loss in package upgrade User: helm...@debian.org Usertags: dep17p1 Control: affects -1 + netplan.io Hi Lukas, netplan was on my radar for /usr-merge for a while, but unfortunately I didn't get down to it before bad things happened. I think this is your first upload since we changed systemd.pc to point to /usr. Earlier, netplan-generator would install /lib/systemd/system-generators/netplan and since this upload it installs to the same location below /usr. This wouldn't be a problem if that file weren't installed in netplan.io in bookworm. Now upgrading from bookworm to unstable would both move this file from / to /usr and from netplan.io to netplan-generator. Normally, the Replaces that you declare are sufficient, but the aliasing added by /usr-merge changes this and makes the file subject to loss in an upgrade. For more information refer to DEP17 P1. You have two possible mitigations for this. The simple mitigation (DEP17 M7) is upgrading those Breaks+Replaces for netplan.io to Conflicts. This still can cause file loss if netplan.io is being removed in an upgrade where netplan-generator is being installed and the upgrade is being performed with dpkg. I'd consider that relatively unlikely. If you want to handle this case correctly, the recommended way is using "protective diversions" (DEP17 M8). You keep Breaks+Replaces as is and extend maintainer scripts. netplan-generator.preinst: dpkg-divert --no-rename --divert /lib/systemd/system-generators/netplan.usr-is-merged --add /lib/systemd/system-generators/netplan netplan-generator.postinst: dpkg-divert --no-rename --divert /lib/systemd/system-generators/netplan.usr-is-merged --remove /lib/systemd/system-generators/netplan This diversion redirects the deletion of the file being replaced to a location that does not exist and hence prevents the loss. Beyond this, there also is an issue with /usr/lib/netplan. It is an empty directory and since netplan.io formerly installed files to /lib/netplan, removing netplan.io can make dpkg think that /lib/netplan can be deleted. When it does so, it actually deletes /usr/lib/netplan (DEP17 P6). Your options are: * Do not install /usr/lib/netplan and make the generator work in the absence of that directory. * Ship a placeholder file inside. * Have a postinst script that recreates it after loss. For this to work, you have to install a trigger interest in /lib/netplan to make dpkg rerun your postinst after the loss. On top of this, none of the moves nor mitigations are applicable to bookworm. If you plan to support backports for bookworm, you need to ensure that such backports do not move files to /usr. It also means that your possible M8 mitigation has to add protective diversions on every upgrade without a version check as it could be upgrading from bookworm-backports. Can you handle these issues? In case you want a stop-gap measure, for now, I suggest temporarily moving back the generator to /lib/systemd in unstable. Doing so unbreaks the upgrade from bookworm and makes this bug non-rc, but is not a long-term solution. I'm happy to review a patch. Let me know if you cannot handle this and I'll look in to preparing a NMU. If you have questions, don't hesitate to ask. Helmut DEP1: https://subdivi.de/~helmut/dep17.html
Bug#1060660: newt: does not trap errors from python extension build (policy 4.6)
Source: newt Version: 0.52.24-1 Severity: serious Justification: policy 4.6 Debian policy requires that failing a build step makes the package build fail. When the Python extension build fails, the upstream Makefile continues in violation of this policy and may result in a seemingly successful build missing content. Helmut
Bug#1059869: marked as done (autopkgtest fails)
Your message dated Fri, 12 Jan 2024 09:34:24 + with message-id and subject line Bug#1059869: fixed in plakativ 0.5.2-1 has caused the Debian Bug report #1059869, regarding autopkgtest fails 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.) -- 1059869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plakativ Version: 5.0.1-2 Severity: important The tests fail with the latest pymupdf: AttributeError: 'Shape' object has no attribute 'insertText' https://ci.debian.net/packages/p/plakativ/testing/amd64/41418631/ The methon name has changed to insert_text. --- End Message --- --- Begin Message --- Source: plakativ Source-Version: 0.5.2-1 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of plakativ, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated plakativ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 10:19:34 +0100 Source: plakativ Architecture: source Version: 0.5.2-1 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1059869 Changes: plakativ (0.5.2-1) unstable; urgency=medium . * New upstream version 0.5.2 * debian/watch: refresh with http://pypi.debian.net/plakativ/watch * debian/tests/plakativ_test.py: convert to snake_case naming for pymupdf 1.23.0 and later (closes: #1059869) Checksums-Sha1: adae767826d6cf67560e2d413715269fb91c2ed5 2198 plakativ_0.5.2-1.dsc 6f2f46350bd09953cc4c3daf4089fdb8fe665adb 38461 plakativ_0.5.2.orig.tar.gz a28e4060ec4354b6777fd4cf8818ab6db01f820a 11024 plakativ_0.5.2-1.debian.tar.xz Checksums-Sha256: 2041340333cb6883322744a41a43df96f6c4ca88fee20e889d37bcb9c4e68e48 2198 plakativ_0.5.2-1.dsc a51471fdc0607fe1caf4d6753676a42ff75bc469f550d1c9386bc2dc8ef44062 38461 plakativ_0.5.2.orig.tar.gz f53f565d160ee918321646be5827f381dad409a48875e0223513d66c47c9b380 11024 plakativ_0.5.2-1.debian.tar.xz Files: c094574031fcc0da28510adcf53499b6 2198 python optional plakativ_0.5.2-1.dsc 0522523ab0ef1ba6900e8028bc59ff94 38461 python optional plakativ_0.5.2.orig.tar.gz 951f02347a15e10a5a77b1c4710e9748 11024 python optional plakativ_0.5.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmWhBFEACgkQ8sulx4+9 g+FmjxAAiizZSWK+4W1AFTungQQiPHDeaEf8JSaSSpB06k+Hl671ETToyGuo4tEd OWSL74CpuAgV0jlxFIhBSeDjx2cwRgtVddMjcYRl/3eU4XU6PTkuUDZv8yWV8jeZ N65BvBX0aFSgkOWM/BaYWQ0K9zcshAE3eeK/cEya0HuTKSgxH9tZEwd/3rBY27HX zNbEILoKNZxqJrONPPrbhlE7FmSzotqeZph5Rdkc9t/0YLBwpU3ISCXZ017atmkN Lpo3+WvCOHphwDmq5C2xVB5zmp+VZmSFBVl9EGRFrhy2u/vFOn9NvEcN//z2deit RZkL2DSw7VD0rXuT1PhDY7KsNzWEqlZ8k9O487DgzACY/BqXp+ZChCAFFR8flFMv vQfP0uaUvjwDygrNJ0gXi2r2zizeK1SCVXEDI4PUzUkhYiGBb0RTJQtXVrB4cDUl cQnOg3uITQOSW803T/nHKeDgZrY8yCQOqQZMKxIX+Xug1oxjNL2B44DnGLAJ06lO vWbPPQEjmbes1TEnMH+G45VWPzPaQAsfyfmUv/IHD9mRsjk8j0V9lmrYHUDYfOK9 QEtk6dcj2pc7DuPJLaO7ezl/c+JFt17FFqoZL5zeegfOigwsZLKOHhfowkEsXEry Esx0HXL4SIG2SbbxRMuHt/IfYvpbdKmNbtMkTVuZbziRlf+Q+y4= =YI7o -END PGP SIGNATURE End Message ---
Bug#1042685: marked as done (flufl.password: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Fri, 12 Jan 2024 09:34:09 + with message-id and subject line Bug#1042685: fixed in flufl.password 1.3-6 has caused the Debian Bug report #1042685, regarding flufl.password: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flufl.password Version: 1.3-5 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, flufl.password fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 setup.py build_sphinx > /usr/lib/python3/dist-packages/setuptools/dist.py:945: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. > !! > > > > Please replace its usage with implicit namespaces (PEP 420). > > See > https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages > for details. > > > > !! > ep.load()(self, ep.name, value) > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:12: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/flufl.password_1.3-5_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: flufl.password Source-Version: 1.3-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of flufl.password, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated flufl.password package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 10:06:35 +0100 Source: flufl.password Architecture: source Version: 1.3-6 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andreas Tille Closes: 924207 974522 1042685 Changes: flufl.password (1.3-6) unstable; urgency=medium . * Team upload. * d/python-flufl.password.links -> d/python-flufl.password-doc.links. Fix link. (Closes: #924207) * Use sphinx-build Closes: #1042685 * Testsuite:
Bug#965837: tart: Change of debhelper compat
On Fri, 12 Jan 2024 17:12:36 +0800 i...@0w.al wrote: > Hi. > > I have changed the compat version from 5 to 13 to fix the build error, and > fixed some lintian warnings > > Clansty > Hi. I forgot to close the bug-id. Here’s the update of the patch. Clansty tart_3.10-1.1.debdiff Description: Binary data
Bug#1060658: megapixels don't start could not find any config file
Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found.
Bug#1059869: autopkgtest fails
On 2024-01-11 23:40, Bastian Germann wrote: Ping. It is now 1 week until this will auto-remove several packages. Please consider releasing and packaging the new release. Whoops, sorry!! And thank you for the ping. This has now been taken care of. The version I just uploaded has the autopkgtest running fine on salsa so I guess this issue is indeed fixed. Thanks! cheers, josch
Bug#965837: tart: Change of debhelper compat
Hi. I have changed the compat version from 5 to 13 to fix the build error, and fixed some lintian warnings Clansty tart_3.10-1.1.debdiff Description: Binary data
Bug#1052849: marked as done (python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 12 Jan 2024 08:41:06 +
with message-id
and subject line Bug#1052849: fixed in python-pkginfo 1.9.6-1
has caused the Debian Bug report #1052849,
regarding python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
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.)
--
1052849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pkginfo
Version: 1.8.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/installed.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/wheel.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/utils.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/index.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/commandline.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/develop.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/_compat.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/bdist.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/sdist.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> copying pkginfo/distribution.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo
> creating /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_wheel.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_index.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_installed.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_utils.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_distribution.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_sdist.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_develop.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_bdist.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> copying pkginfo/tests/test_commandline.py ->
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> python3 setup.py build_sphinx
> running build_sphinx
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 4 source files that are out of date
> updating environment: [new config] 4 added, 0 changed, 0 removed
> reading sources... [ 25%] distributions
> reading sources... [ 50%] index
> reading sources... [ 75%] indexes
> reading sources... [100%] metadata
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 25%] distributions
> writing output... [ 50%] index
> writing output... [ 75%] indexes
> writing output... [100%] metadata
>
> generating indices... genindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
>
> The HTML pages are in build/sphinx/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:314: cp -R pkginfo/tests/funny pkginfo/tests/manky
> pkginfo/tests/silly pkginfo/tests/wonky
> /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests
> I: pybuild base:291: cd
> /<>/.pybuild/cpython3_3.11_pkginfo/build; python3.11 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2,
Bug#1042599: marked as done (python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Fri, 12 Jan 2024 08:41:06 + with message-id and subject line Bug#1042599: fixed in python-pkginfo 1.9.6-1 has caused the Debian Bug report #1042599, regarding python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pkginfo Version: 1.8.2-2 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-pkginfo fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/installed.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/wheel.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/utils.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/index.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/__init__.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/commandline.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/develop.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/_compat.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/bdist.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/sdist.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > copying pkginfo/distribution.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo > creating /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_wheel.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_index.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_installed.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_utils.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_distribution.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/__init__.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_sdist.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_develop.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_bdist.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_commandline.py -> > /<>/.pybuild/cpython3_3.11_pkginfo/build/pkginfo/tests > python3 setup.py build_sphinx > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/python-pkginfo_1.8.2-2_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or:
Bug#1055718: python-openstep-plist ftbfs with Python 3.12
Dear Maintainer, I was able to build successfully python-openstep-plist/0.3.1-1~exp1 in a sid chroot environment for amd64 architecture. 0.3.1-1~exp1 landed in experimental for a while, Is there some concern that prevents upload to unstable? Please note that this issue affects (at least) fontmake [1] and glyphslib [2] Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058388 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058432
Bug#1042664: marked as done (flufl.enum: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Fri, 12 Jan 2024 08:38:28 + with message-id and subject line Bug#1042664: fixed in flufl.enum 4.1.1-6 has caused the Debian Bug report #1042664, regarding flufl.enum: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flufl.enum Version: 4.1.1-5 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, flufl.enum fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 setup.py build_sphinx > /usr/lib/python3/dist-packages/setuptools/dist.py:945: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. > !! > > > > Please replace its usage with implicit namespaces (PEP 420). > > See > https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages > for details. > > > > !! > ep.load()(self, ep.name, value) > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:14: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/flufl.enum_4.1.1-5_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: flufl.enum Source-Version: 4.1.1-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of flufl.enum, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated flufl.enum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 08:43:54 +0100 Source: flufl.enum Architecture: source Version: 4.1.1-6 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andreas Tille Closes: 1042664 Changes: flufl.enum (4.1.1-6) unstable; urgency=medium . * Team upload. * Use sphinx-build Closes: #1042664 * Standards-Version: 4.6.2 (routine-update) * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root:
Bug#1058321: python-loompy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, > > E If you are not working on Numba development, the original error was: > > 'cannot import name '_typeconv' from 'numba.core.typeconv' > > (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > > E For help, please visit: > > E > > E > > https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've verified your package builds fine locally and autopkg tests pass as well. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301
Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Hi Stefano, Am Thu, Jan 11, 2024 at 08:25:46PM + schrieb Stefano Rivera: > > The test is expecting the module to be installed in the test > environment. Either we could try harder to emulate that, or skip the > tests. I admit I tried to copy around the module before running the test with no success. It would be great if this "could try harded" could be taken over by pybuild. ;-) > I committed a patch to run the test inside tox, which will install it in > a virtualenv before running the test. Looks good, thanks a lot. I realised there are quite some low hanging RC bugs in DPT where I harvested some but I have to stop after today with this due to new tasks. In Debian Med team we are squashing those bugs usually in our Advent bug squashing party where everybody tries to close one bug (not open one door ;-) ) in advent time. It might make sense to establish such regular bug squashing parties also in other teams. Kind regards Andreas. -- http://fam-tille.de
