Bug#1008686: marked as done (Puddletag: name 'operatorPrecedence' is not defined)
Your message dated Thu, 07 Jul 2022 04:37:42 + with message-id and subject line Bug#1008686: fixed in puddletag 2.2.0-1 has caused the Debian Bug report #1008686, regarding Puddletag: name 'operatorPrecedence' is not defined 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.) -- 1008686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package:puddletag Version:2.0.1-3 Severity: critical Hello, Running Debian sid, it is not possible to launch puddletag Debian Forums has a possible fix: https://forums.debian.net/viewtopic.php?f=6=151493 sudo sed -i 's/operatorPrecedence/infixNotation/g' /usr/lib/python3/dist-packages/puddlestuff/audio_filter.py Thanks! --- End Message --- --- Begin Message --- Source: puddletag Source-Version: 2.2.0-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of puddletag, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated puddletag 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: Thu, 07 Jul 2022 00:16:40 -0400 Source: puddletag Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1008686 Changes: puddletag (2.2.0-1) unstable; urgency=medium . * New upstream release; Closes: #1008686 * debian/rules - use pybuild - rework build process for new doc source location - disable tests, there are none to run anyway - override the shebang to be python3 - bump Standards-Version to 4.6.1.0 (no changes needed) * debian/control - use pyproject build plugin - add setuptools to b-d * debian/py3dist-overrides - override six to be an unversioned depends Checksums-Sha1: 493678767542ec69f28e7c77670882572a9d282b 2061 puddletag_2.2.0-1.dsc d0e952fc2acac27117f7b6080f226119c3b8a8bf 11756340 puddletag_2.2.0.orig.tar.xz 7e53080db418fa75c6f06a9f1cbee0337ad20167 4544 puddletag_2.2.0-1.debian.tar.xz 3a0ef94bd776c57dfaa02e414b4bdf26346df6bb 7042 puddletag_2.2.0-1_source.buildinfo Checksums-Sha256: a5480c57c60e202854a35e7f54a3544d6492d5a7a402176eea9298da6c74f52e 2061 puddletag_2.2.0-1.dsc 3196d9bc83694afcdf0b39655f13b9e89edd322deea6e386193581f04ed8c257 11756340 puddletag_2.2.0.orig.tar.xz 134e529d5af26c57d97afbdee0ba9050769f7051dcd1c0256bf7534662302335 4544 puddletag_2.2.0-1.debian.tar.xz 7515f8a7a25c9c6bf212efdac963b23b259d5c98260bd95f41d2a49de61052f4 7042 puddletag_2.2.0-1_source.buildinfo Files: 4409d346b3a0987900ab13bb6dbfd21c 2061 sound optional puddletag_2.2.0-1.dsc 29bc8030de12d478e3a87ba9b11d4371 11756340 sound optional puddletag_2.2.0.orig.tar.xz 7de35094ed6a35908f9836fc03c159d0 4544 sound optional puddletag_2.2.0-1.debian.tar.xz ecf4c02ef9ff074b37db211c76cb537c 7042 sound optional puddletag_2.2.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmLGXkYACgkQh588mTgB qU/LgBAAhKhPm0S1tzDGJR82nTaoK31PJCO54qHjysWOUAdyF0s9JrVPdM4qQJpz R831L8zPoQotqtklwoN2ma4eRSuj6AULH7S8LZmrEpeyiT0pze1267/HaFQ2zJXH 4d8N/sAtsE2CRnIF7SQOphBkd7fwGL6EW56VkG6BhfNlvx0Vrglz45nydl16pQsj ui6eJVzR7fqPxZWVLI6o1iFlzNAsxzv48NAZ45EZEOBwYDS2+F6es4tUcbkkav78 hOF0giBKMqTkVzu5C4ukXzqY5+ojkh+E08x2ZuyYfrArDZ1SpMkQinZjsZk98V2z ytJGY1g2tZEQAyHwoVePy51WtrCPABGG0bifSuImxMUJIv6czTmgHsVEddS1B29H SvAKA3Owquu06xH/2CU/fXrw8ljoRUO2tTE4ijUAda1K5ZrPnQWHws2jRsxQILga UGg6eh1CalfEyPQ8cnKddrB4Yj6laqS0jSSnxqI26Dqpt+lqACyho5Sl1Sj0UyoU rAEXY8UHWNnM0EqgLWPQLam1DO1vbcA3Dai/2U2bkXFLbl0S9dfXW+spihwVL7Ww gSAJGZnyya3vMEEXtH3weaPX3qBrBm2zmOkIJz4jeC8Khoa3tLI4312OiAA+RYe8 aEKKW/H9BCI6GPer0xvyprPhT5wH7VY/+pRuJ4taAYy+d23dJy8= =yXqY -END PGP SIGNATURE End Message ---
Bug#1014501: gnunet-fuse: FTBFS with glibc 2.34
Package: gnunet-fuse
Version: 0.15.0-1
Severity: serious
Tags: patch experimental
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi Daniel,
gnunet-fuse is failing to build from source in Ubuntu, because Ubuntu has
updated to glibc 2.34 where pthread_mutexattr_setkind_np has been dropped:
[...]
gcc -fno-strict-aliasing -Wall -g -O2 -ffile-prefix-map=/<>=.
-flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro
-o gnunet-fuse gnunet_fuse-gnunet-fuse.o gnunet_fuse-gfs_download.o
gnunet_fuse-mutex.o gnunet_fuse-readdir.o gnunet_fuse-read.o gnunet_fuse-open.o
gnunet_fuse-getattr.o -lgnunetutil -lfuse -lgnunetfs -lgnunetutil -lpthread
/usr/bin/ld: /tmp/cclaLsKU.ltrans0.ltrans.o: in function
`GNUNET_FUSE_path_info_create':
./src/fuse/mutex.c:71: undefined reference to `pthread_mutexattr_setkind_np'
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile:463: gnunet-fuse] Error 1
[...]
(https://launchpad.net/ubuntu/+source/gnunet-fuse/0.15.0-1/+build/23574025)
This will affect the package in Debian as well once glibc is updated in
unstable to 2.34 or later (currently, 2.34 is only in experimental).
gnunet-fuse already supports the more standard pthread_mutexattr_settype()
interface, but doesn't use it on Linux platforms. I've uploaded the
attached patch to Ubuntu which switches it to use the standard interface
everywhere.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gnunet-fuse-0.15.0/debian/patches/glibc-2.34-compat.patch
gnunet-fuse-0.15.0/debian/patches/glibc-2.34-compat.patch
--- gnunet-fuse-0.15.0/debian/patches/glibc-2.34-compat.patch 1969-12-31
16:00:00.0 -0800
+++ gnunet-fuse-0.15.0/debian/patches/glibc-2.34-compat.patch 2022-07-06
19:51:20.0 -0700
@@ -0,0 +1,54 @@
+Description: replace mutexattr_setkind_np with standard mutexattr_settype
+ pthread_muteaxttr_settype() has been supported since at least glibc 2.19,
+ and pthread_mutexattr_setkind_np() is no longer supported as of glibc 2.34.
+ Use the standard interface.
+Author: Steve Langasek
+Forwarded: no
+Last-Update: 2022-07-06
+
+Index: gnunet-fuse-0.15.0/src/fuse/mutex.c
+===
+--- gnunet-fuse-0.15.0.orig/src/fuse/mutex.c
gnunet-fuse-0.15.0/src/fuse/mutex.c
+@@ -36,17 +36,6 @@
+ #endif
+
+ /**
+- * This prototype is somehow missing in various Linux pthread
+- * include files. But we need it and it seems to be available
+- * on all pthread-systems so far. Odd.
+- */
+-#ifndef _MSC_VER
+-extern int pthread_mutexattr_setkind_np (pthread_mutexattr_t * attr,
+- int kind);
+-#endif
+-
+-
+-/**
+ * @brief Structure for MUTual EXclusion (Mutex).
+ */
+ struct GNUNET_Mutex
+@@ -67,23 +56,13 @@
+ pthread_mutexattr_init ();
+ if (isRecursive)
+ {
+-#ifdef __linux__
+- GNUNET_assert (0 == pthread_mutexattr_setkind_np
+- (, PTHREAD_MUTEX_RECURSIVE_NP));
+-#elif BSD || SOLARIS || OSX || WINDOWS
+ GNUNET_assert (0 == pthread_mutexattr_settype
+(, PTHREAD_MUTEX_RECURSIVE));
+-#endif
+ }
+ else
+ {
+-#ifdef __linux__
+- GNUNET_assert (0 == pthread_mutexattr_setkind_np
+- (, PTHREAD_MUTEX_ERRORCHECK_NP));
+-#else
+ GNUNET_assert (0 == pthread_mutexattr_settype
+(, PTHREAD_MUTEX_ERRORCHECK));
+-#endif
+ }
+ mut = GNUNET_new (struct GNUNET_Mutex);
+ GNUNET_assert (0 == pthread_mutex_init (>pt, ));
diff -Nru gnunet-fuse-0.15.0/debian/patches/series
gnunet-fuse-0.15.0/debian/patches/series
--- gnunet-fuse-0.15.0/debian/patches/series1969-12-31 16:00:00.0
-0800
+++ gnunet-fuse-0.15.0/debian/patches/series2022-07-06 19:46:30.0
-0700
@@ -0,0 +1 @@
+glibc-2.34-compat.patch
Processed: Bug#1008686 marked as pending in puddletag
Processing control commands: > tag -1 pending Bug #1008686 [puddletag] Puddletag: name 'operatorPrecedence' is not defined Added tag(s) pending. -- 1008686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1014490, tagging 1014492, tagging 1014493, tagging 1014494
Processing commands for cont...@bugs.debian.org: > tags 1014490 + upstream Bug #1014490 [src:radare2] radare2: CVE-2021-44975 CVE-2021-44974 CVE-2021-4021 Added tag(s) upstream. > tags 1014492 + upstream Bug #1014492 [src:guzzle] guzzle: CVE-2022-31090 CVE-2022-31091 Added tag(s) upstream. > tags 1014493 + upstream Bug #1014493 [src:dwarfutils] dwarfutils: CVE-2022-34299 Added tag(s) upstream. > tags 1014494 + upstream Bug #1014494 [src:tiff] tiff: CVE-2022-2056 CVE-2022-2057 CVE-2022-2058 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014490 1014492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014492 1014493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014493 1014494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008686: marked as pending in puddletag
Control: tag -1 pending Hello, Bug #1008686 in puddletag 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/python-team/packages/puddletag/-/commit/f64d2e40b2db18a177a5bbae8798698a7a9a9417 New upstream release; Closes: #1008686 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008686
Bug#1014489: marked as done (deepdiff: autopkgtest failing due to missing dependencies)
Your message dated Thu, 07 Jul 2022 03:48:56 + with message-id and subject line Bug#1014489: fixed in deepdiff 5.8.2-3 has caused the Debian Bug report #1014489, regarding deepdiff: autopkgtest failing due to missing dependencies 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.) -- 1014489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deepdiff Version: 5.8.2-2 Severity: serious The recent patch to add python3-toml and python3-clevercsv to the Build-Depends forgot to add the same dependencies to the autopkgtest dependencies. As a result, the autopkgtests are now failing and this package is preventing the migration of pytest to testing. Best wishes, Julian --- End Message --- --- Begin Message --- Source: deepdiff Source-Version: 5.8.2-3 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of deepdiff, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated deepdiff 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: Wed, 06 Jul 2022 23:30:41 -0400 Source: deepdiff Architecture: source Version: 5.8.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Sandro Tosi Closes: 1014489 Changes: deepdiff (5.8.2-3) unstable; urgency=medium . * debian/tests/control - install build-deps when running autopkgtests; Closes: #1014489 Checksums-Sha1: 6455640d0d5bde4195eeced9ff1ae9982d619a70 2235 deepdiff_5.8.2-3.dsc 2c95cdbb3025e3bacfc8e3315b0e57000c40702b 2848 deepdiff_5.8.2-3.debian.tar.xz c13d6acb911358a46330c915e66754f8e70f553d 7806 deepdiff_5.8.2-3_source.buildinfo Checksums-Sha256: 899fc49b91896956f609c8bc9e9b8449f744f5b9f7a9011ba176624fbe0029d7 2235 deepdiff_5.8.2-3.dsc 25f126b5944a0021d0e96fe8a2fa0069d04920b0d68c9cbda74cde8ba0b549cc 2848 deepdiff_5.8.2-3.debian.tar.xz 191fed861224743b9093f7bee4bc398f87c45e13100411191fd43d9edf2b73f6 7806 deepdiff_5.8.2-3_source.buildinfo Files: 697c4a9d4d2e5fe88cb98debb35333f9 2235 python optional deepdiff_5.8.2-3.dsc 234a246564f427c00aeaa8592edbc256 2848 python optional deepdiff_5.8.2-3.debian.tar.xz f76f3eea235258a5a94cc946812976ce 7806 python optional deepdiff_5.8.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmLGU30ACgkQh588mTgB qU/78hAA03rtsdzPv7c5kOrHTw0PHy8TDWv4o+TcnwAj64RIJtRh733qqbh3rTHC uRXWkOEhb0rIGBiOOT7ijmGFL+FHXpAuKGTJ7bzRvu0B3W0ANk2NZqx28pqwitP2 zzho6zIDZ30KBTr1W7vKWTKw8jc2nc6N5/eD7ao8BTAaxRMjSZBOZIvsvjZDLX3N zl+53hyEi8k+ruHYFyBYKjZlMuAyHqfjV2XnS1m0PGlfkLhQtX0bx6L34q4rpJyh CHWI+iK27Y8wO0NOxy3zkQFc8tcbeey2KYoV8xLEZ7zAfaMi+WVnkg7dbqmE6Re8 JtsqvxjyAmDlMlPb/rTCJiGZtckq6it52Mlpry715kve6FkNYrSUSBuaKv3J9gc8 9vDBeHRncJc4amx6S/sL5pKJVku7NQ9i/ZSUBTwhgm/qFUexYUPuzb5Ulga2+5Tv 0H1C2HCekM+5FTrzwod3SqupmmEscwYTaERWSXBsgPbaxYBfU1KPhCzFK5aDLHCg 5kgkhqPon8MuN8FS2m2/wmiDfxLUsHC9LdAYbdKRvT5exJWFZoJV0x4WVIVV4Hwu kn2utaDtqriucxHzgwJ1IDvPPhhlY6iL+hZlPVSHSywQcdB7D8LahzVZfvGdLQEf VmOJyl0XYkrX1N8nO4aBN+KMGy2vuUKF98tSwj3VawZ3IzvqGUI= =ZD8+ -END PGP SIGNATURE End Message ---
Bug#1014489: marked as pending in deepdiff
Control: tag -1 pending Hello, Bug #1014489 in deepdiff 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/python-team/packages/deepdiff/-/commit/38007d25cf6843d8d46787cd176b8001291816d2 install build-deps when running autopkgtests; Closes: #1014489 (this message was generated automatically) -- Greetings https://bugs.debian.org/1014489
Processed: Bug#1014489 marked as pending in deepdiff
Processing control commands: > tag -1 pending Bug #1014489 [src:deepdiff] deepdiff: autopkgtest failing due to missing dependencies Added tag(s) pending. -- 1014489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014499: libsbig: builds uninstallable libsbig-dev package on unsupported archs
Package: libsbig
Version: 4.9.9-2
Severity: serious
Tags: patch
Justification: uninstallable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi Thorsten,
In Ubuntu I've noticed that libsbig is not releasable because the package
autobuilds a -dev package on all archs, but it is uninstallable on most
archs because the runtime library package is only available on amd64, armhf,
and arm64.
This also prevents the package from being released to Debian testing.
I'm assuming that the -dev package is meant to only be provided on the archs
where the runtime library package is provided, rather than it serving some
other limited function on these other architectures; so I have uploaded the
attached patch to Ubuntu to get the two binary packages in sync.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libsbig-4.9.9/debian/control libsbig-4.9.9/debian/control
--- libsbig-4.9.9/debian/control2022-06-07 14:59:12.0 -0700
+++ libsbig-4.9.9/debian/control2022-07-06 18:29:11.0 -0700
@@ -27,7 +27,7 @@
Package: libsbig-dev
Section: non-free/libdevel
-Architecture: any
+Architecture: amd64 armhf arm64
Depends: libsbig4 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
Description: SBIG Universal Library Driver - development files
The Official Santa Barbra Instrument Group (SBIG) Universal Library
Processed: severity of 1014169 is serious
Processing commands for cont...@bugs.debian.org: > severity 1014169 serious Bug #1014169 [rinutils] rinutils FTBFS Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014260: marked as done (libuhd4.2.0-dpdk-tests: flie conflicts with libuhd4.1.0-dpdk-tests)
Your message dated Thu, 07 Jul 2022 01:03:55 + with message-id and subject line Bug#1014260: fixed in uhd 4.2.0.0+ds1-3 has caused the Debian Bug report #1014260, regarding libuhd4.2.0-dpdk-tests: flie conflicts with libuhd4.1.0-dpdk-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.) -- 1014260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libuhd4.2.0-dpdk-tests Version: 4.2.0.0+ds1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libuhd4.2.0-dpdk_4.2.0.0+ds1-2_amd64.deb ... Unpacking libuhd4.2.0-dpdk:amd64 (4.2.0.0+ds1-2) ... Selecting previously unselected package libuhd4.2.0-dpdk-tests. Preparing to unpack .../libuhd4.2.0-dpdk-tests_4.2.0.0+ds1-2_amd64.deb ... Unpacking libuhd4.2.0-dpdk-tests (4.2.0.0+ds1-2) ... dpkg: error processing archive /var/cache/apt/archives/libuhd4.2.0-dpdk-tests_4.2.0.0+ds1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/uhd/tests/dpdk_port_test', which is also in package libuhd4.1.0-dpdk-tests 4.1.0.5-3+b2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libuhd4.2.0-dpdk-tests_4.2.0.0+ds1-2_amd64.deb The package name suggests that these two should be co-installable, so you should probably move the tests to a versioned subdirectory of /usr/lib/uhd/ Otherwise please consider removing the version from the package name. cheers, Andreas libuhd4.1.0-dpdk-tests=4.1.0.5-3+b2_libuhd4.2.0-dpdk-tests=4.2.0.0+ds1-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: uhd Source-Version: 4.2.0.0+ds1-3 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of uhd, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated uhd 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: Wed, 06 Jul 2022 19:58:38 -0400 Source: uhd Architecture: source Version: 4.2.0.0+ds1-3 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1014239 1014260 Changes: uhd (4.2.0.0+ds1-3) unstable; urgency=medium . * Re-enable python3-uhd on mipsel (Closes: 1014239) * Use versioned subdirectory for libuhd4.2.0-dpdk-tests (Closes: #1014260) Checksums-Sha1: b54959d760e0cdee1e1839f475c70acb2e3e418a 2840 uhd_4.2.0.0+ds1-3.dsc 0877123184099cc5010ec03953d79db02cbd3b2c 59528 uhd_4.2.0.0+ds1-3.debian.tar.xz ad3ffa1a09f081c153b63aca1fdaad3c148873e6 24973 uhd_4.2.0.0+ds1-3_amd64.buildinfo Checksums-Sha256: b3d848d2037db98aea2bf4fbabd797f5b5bb00c19c1fd28e166ddd83f65989f5 2840 uhd_4.2.0.0+ds1-3.dsc 3b304706f1c3b3a3b08c19c16e369041564acf8d8930b7c514a5c66aec47319b 59528 uhd_4.2.0.0+ds1-3.debian.tar.xz 61c86dc857ad9fcbf20922f5d0e51d14fcd95272a569ba72275a8c5923c343c8 24973 uhd_4.2.0.0+ds1-3_amd64.buildinfo Files: b8bb6718d9549e88be08cc7ae64415f9 2840 science optional uhd_4.2.0.0+ds1-3.dsc 20882d12c39136c5b41991c35dcfb366 59528 science optional uhd_4.2.0.0+ds1-3.debian.tar.xz 94f763877f7f9bad4b70b9be8d0b3c68 24973 science optional uhd_4.2.0.0+ds1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmLGK8sACgkQUEHxiR9E 4JCI7hAAwzOjksXzPjSkzEExRNRT3RHMuy7J8+o1E+Q77FZbj5hCnKhJUxmsJptt SCUa5wvOPt9HicjDRKhLMuehznxia6crKH99GbJj+65dtELMKmv3/2CHbvwpCqbJ usITXpKpP4Ke3Cnx0roS1yZrODQ2DXwQa1utkX5nR7gtqd0JZkcXyAeKNZ2catB7 XknwK3IyOcK+5P6sdKUBD6mZpNaLhoPNaAuwAwcNlN7SLTFmf9sW7dm5iu8EU/s2 Uk6j/r+0jT7DG0cExowPK6LEW540/gtTB9Urxht9sfNiCDGQqg4DbxmfRzfJHMm/
Bug#1014239: marked as done (uhd: FTBFS on mipsel: mv: cannot stat 'debian/tmp/usr/bin/usrp_hwd.py': No such file or directory)
Your message dated Thu, 07 Jul 2022 01:03:55 + with message-id and subject line Bug#1014239: fixed in uhd 4.2.0.0+ds1-3 has caused the Debian Bug report #1014239, regarding uhd: FTBFS on mipsel: mv: cannot stat 'debian/tmp/usr/bin/usrp_hwd.py': No such file or directory 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.) -- 1014239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhd Version: 4.2.0.0+ds1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=uhd=mipsel=4.2.0.0%2Bds1-2=1656636367=0 -- Installing: /<>/debian/tmp/usr/share/man/man1/uhd_usrp_probe.1.gz -- Installing: /<>/debian/tmp/usr/share/man/man1/usrp_n2xx_simple_net_burner.1.gz -- Installing: /<>/debian/tmp/usr/share/man/man1/usrp2_card_burner.1.gz mv debian/tmp/usr/bin/usrp_hwd.py debian/tmp/usr/bin/usrp_hwd mv: cannot stat 'debian/tmp/usr/bin/usrp_hwd.py': No such file or directory make[1]: *** [debian/rules:45: override_dh_auto_install-arch] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:18: binary-arch] Error 2 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: uhd Source-Version: 4.2.0.0+ds1-3 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of uhd, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated uhd 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: Wed, 06 Jul 2022 19:58:38 -0400 Source: uhd Architecture: source Version: 4.2.0.0+ds1-3 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1014239 1014260 Changes: uhd (4.2.0.0+ds1-3) unstable; urgency=medium . * Re-enable python3-uhd on mipsel (Closes: 1014239) * Use versioned subdirectory for libuhd4.2.0-dpdk-tests (Closes: #1014260) Checksums-Sha1: b54959d760e0cdee1e1839f475c70acb2e3e418a 2840 uhd_4.2.0.0+ds1-3.dsc 0877123184099cc5010ec03953d79db02cbd3b2c 59528 uhd_4.2.0.0+ds1-3.debian.tar.xz ad3ffa1a09f081c153b63aca1fdaad3c148873e6 24973 uhd_4.2.0.0+ds1-3_amd64.buildinfo Checksums-Sha256: b3d848d2037db98aea2bf4fbabd797f5b5bb00c19c1fd28e166ddd83f65989f5 2840 uhd_4.2.0.0+ds1-3.dsc 3b304706f1c3b3a3b08c19c16e369041564acf8d8930b7c514a5c66aec47319b 59528 uhd_4.2.0.0+ds1-3.debian.tar.xz 61c86dc857ad9fcbf20922f5d0e51d14fcd95272a569ba72275a8c5923c343c8 24973 uhd_4.2.0.0+ds1-3_amd64.buildinfo Files: b8bb6718d9549e88be08cc7ae64415f9 2840 science optional uhd_4.2.0.0+ds1-3.dsc 20882d12c39136c5b41991c35dcfb366 59528 science optional uhd_4.2.0.0+ds1-3.debian.tar.xz 94f763877f7f9bad4b70b9be8d0b3c68 24973 science optional uhd_4.2.0.0+ds1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmLGK8sACgkQUEHxiR9E 4JCI7hAAwzOjksXzPjSkzEExRNRT3RHMuy7J8+o1E+Q77FZbj5hCnKhJUxmsJptt SCUa5wvOPt9HicjDRKhLMuehznxia6crKH99GbJj+65dtELMKmv3/2CHbvwpCqbJ usITXpKpP4Ke3Cnx0roS1yZrODQ2DXwQa1utkX5nR7gtqd0JZkcXyAeKNZ2catB7 XknwK3IyOcK+5P6sdKUBD6mZpNaLhoPNaAuwAwcNlN7SLTFmf9sW7dm5iu8EU/s2 Uk6j/r+0jT7DG0cExowPK6LEW540/gtTB9Urxht9sfNiCDGQqg4DbxmfRzfJHMm/ iq3FtlJbr7Y18xeGKg57DCt3gOaB83OAtBDFVno8R4X4oadc3Lt6BiXi3htcxKwD Ey0bSuWZMbDncLEyv7k1K68xwlib+755Sc/eUuQtHqcnCjZlHxThv1lb9mKKVIJ7 2QSw5SR6g+1A3LqRLA1LqJiQ0vuuH+eHnUxgqMNS4ITllpEy1tUKhbAjSaknxZnP VOvUWWj/kjFNJusCN5uptqo+V/1MDRPNmlW9aC10qJeiNwICXVEoQFDwzZ4mK+AA JjXMwiufEBHg8uXw3Dsf4ecvxpOBcbBdXK1U/CdI9E10ZJLnlz90UGABMJ3nYwNL DMT3GmlVmgoC0Bmfdp9MXJjo7mwBXVSesbzdGhASkQeGgbEXXKQ= =zu4T -END PGP SIGNATURE End Message ---
Bug#1014496: sphde: FTBFS on armhf et al
Package: sphde
Version: 1.4.0-3
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi Frédéric,
sphde 1.4.0-3 has been stuck in unstable for 230 days because it fails to
build on several architectures. The same problem affects Ubuntu, so I've
had a look at resolving the build failure.
It appears that of all the patches you added in this version, only the first
patch is actually required to fix the build failure with current gcc (at
least per my tests in Ubuntu); and the third of these patches is the one
that introduces the test hang on armhf. Removing this patch is sufficient
to let the package build on all archs in Ubuntu, and hopefully this is true
for Debian as well.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
---
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
2021-11-18 08:15:46.0 -0800
+++
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
2022-07-06 17:18:10.0 -0700
@@ -23,13 +23,13 @@
src/sassim.cpp | 17 +
1 file changed, 17 insertions(+)
-diff --git a/src/sassim.cpp b/src/sassim.cpp
-index 53bda2a..1410919 100644
a/src/sassim.cpp
-+++ b/src/sassim.cpp
-@@ -36,6 +36,10 @@
+Index: sphde-1.4.0/src/sassim.cpp
+===
+--- sphde-1.4.0.orig/src/sassim.cpp
sphde-1.4.0/src/sassim.cpp
+@@ -35,6 +35,10 @@
+ #include
#include
- #include
+#if __GNUC__
+#include
@@ -38,7 +38,7 @@
#include "sasio.h"
#include "freenode.h"
#include "sasanchr.h"
-@@ -688,6 +692,15 @@ destroySASSem (SASAnchor_t * anchor)
+@@ -484,6 +488,15 @@
#endif
}
@@ -54,7 +54,7 @@
static void
initRegion ()
{
-@@ -769,6 +782,10 @@ initRegion ()
+@@ -565,6 +578,10 @@
initSASSem (anchor);
}
diff -Nru sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch
sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch
--- sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch
2021-11-18 08:15:46.0 -0800
+++ sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch
2022-07-06 16:13:17.0 -0700
@@ -27,15 +27,14 @@
src/tests/sassim_t.c | 3 +--
4 files changed, 54 insertions(+), 4 deletions(-)
-diff --git a/src/sasshm.c b/src/sasshm.c
-index 402e7e0..4a1e01a 100644
a/src/sasshm.c
-+++ b/src/sasshm.c
-@@ -106,6 +106,56 @@ SASAllocateShmID (key_t key_id, void *addr, long size)
- return (shm_id);
+Index: sphde-1.4.0/src/sasshm.c
+===
+--- sphde-1.4.0.orig/src/sasshm.c
sphde-1.4.0/src/sasshm.c
+@@ -107,6 +107,56 @@
}
-+int
+ int
+SASAllocateShmID_clear (key_t key_id, void *addr, long size)
+{
+ int shm_id;
@@ -85,14 +84,15 @@
+ return (shm_id);
+}
+
- int
++int
SASAllocateShmName (char *key_name, void *addr, long size)
{
-diff --git a/src/sasshm.h b/src/sasshm.h
-index e45f28e..40599ff 100644
a/src/sasshm.h
-+++ b/src/sasshm.h
-@@ -36,6 +36,8 @@ extern __C__ int SASAllocateShm( void* addr, long size );
+ key_t shm_key;
+Index: sphde-1.4.0/src/sasshm.h
+===
+--- sphde-1.4.0.orig/src/sasshm.h
sphde-1.4.0/src/sasshm.h
+@@ -36,6 +36,8 @@
extern __C__ int SASAllocateShmID(key_t key_id, void* addr, long size );
@@ -101,11 +101,11 @@
extern __C__ int SASAllocateShmName(char *key_name, void* addr, long size );
extern __C__ int SASAllocateShmNameProj( char* key_name, char proj,
-diff --git a/src/tests/sascompoundheap_t.c b/src/tests/sascompoundheap_t.c
-index 04543bb..f1b9f50 100644
a/src/tests/sascompoundheap_t.c
-+++ b/src/tests/sascompoundheap_t.c
-@@ -122,14 +122,13 @@ sassim_compound_heap_test1 ()
+Index: sphde-1.4.0/src/tests/sascompoundheap_t.c
+===
+--- sphde-1.4.0.orig/src/tests/sascompoundheap_t.c
sphde-1.4.0/src/tests/sascompoundheap_t.c
+@@ -122,14 +122,13 @@
sasshm_t lock_mem = 0;
key_t test_heap = 1234;
@@ -121,11 +121,11 @@
compoundHeap =
SASCompoundHeapInit (compoundHeap, __SAS_SHMAP_MAX, block__Size512, 0);
SASSIM_PRINT_MSG ("SASCompoundHeapInit (%p, %ld) success", compoundHeap,
-diff --git a/src/tests/sassim_t.c b/src/tests/sassim_t.c
-index 6741d2e..22ebdf8 100644
a/src/tests/sassim_t.c
-+++
Bug#1014491: marked as done (python3-torch: import fails: undefined symbol)
Your message dated Wed, 06 Jul 2022 16:13:53 -0700 with message-id <87ilo9kewh@secretsauce.net> and subject line Re: Bug#1014491: python3-torch: import fails: undefined symbol has caused the Debian Bug report #1014491, regarding python3-torch: import fails: undefined symbol 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.) -- 1014491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-torch Version: 1.8.1-5+b1 Severity: grave X-Debbugs-Cc: none, Dima Kogan Hi. Thanks for maintaining pytorch. I can't imagine the pain it took to get this packaged. Currently it doesn't work, unfortunately: $ python3 -mtorch Traceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main mod_name, mod_spec, code = _get_module_details(mod_name, _Error) File "/usr/lib/python3.10/runpy.py", line 146, in _get_module_details return _get_module_details(pkg_main_name, error) File "/usr/lib/python3.10/runpy.py", line 110, in _get_module_details __import__(pkg_name) File "/usr/lib/python3/dist-packages/torch/__init__.py", line 196, in from torch._C import * ImportError: /usr/lib/x86_64-linux-gnu/libtorch_cpu.so.1.8: undefined symbol: _ZN4onnx12optimization8OptimizeERKNS_10ModelProtoERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISA_EE This symbol is missing. I looked around, and I can't figure out which package was supposed to provide it. Without it the linking fails, and the package is unusable. Am I missing some dependency? -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8), LANGUAGE=en_US.utf-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-torch depends on: ii libc6 2.33-7 ii libdnnl22.6-1 ii libgcc-s1 12.1.0-4 ii libgloo00.0~git20220518.5b14351-1 ii libgoogle-glog0v6 0.6.0-1 ii libonnx11.12.0-1 ii libprotobuf23 3.12.4-1+b2 ii libstdc++6 12.1.0-4 ii libtorch-test 1.8.1-5+b1 ii libtorch1.8 1.8.1-5+b1 ii python3 3.10.4-1+b1 ii python3-future 0.18.2-5 ii python3-numpy [python3-numpy-abi9] 1:1.21.5-1 ii python3-pkg-resources 59.6.0-1 ii python3-requests2.25.1+dfsg-2 ii python3-six 1.15.0-2 ii python3-typing-extensions 3.10.0.2-1 ii python3-yaml5.4.1-1+b1 ii python3.10 3.10.5-1 Versions of packages python3-torch recommends: ii build-essential 12.9 pn libtorch-dev ii ninja-build 1.10.1-1 pn pybind11-dev Versions of packages python3-torch suggests: ii python3-hypothesis 5.43.3-1 ii python3-pytest 6.2.5-1 -- no debconf information --- End Message --- --- Begin Message --- Thanks for the description. If the fix is already in NEW, then there's nothing much to do here, so I'm closing this report. Thanks again for working on this.--- End Message ---
Bug#1014484: marked as done (python-async-lru: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - Future exception was never retrieved; ZeroDivisionError)
Your message dated Wed, 06 Jul 2022 23:05:52 + with message-id and subject line Bug#1014484: fixed in python-async-lru 1.0.3-3 has caused the Debian Bug report #1014484, regarding python-async-lru: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - Future exception was never retrieved; ZeroDivisionError 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.) -- 1014484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-async-lru Version: 1.0.3-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/python-async-lru/ I had a closer look at the error logs and identified the regression as: 'Future exception was never retrieved; ZeroDivisionError'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-async-lru Source-Version: 1.0.3-3 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of python-async-lru, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated python-async-lru 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, 07 Jul 2022 00:45:21 +0200 Source: python-async-lru Architecture: source Version: 1.0.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Timo Röhling Closes: 1014484 Changes: python-async-lru (1.0.3-3) unstable; urgency=medium . * Ignore benign runtime warnings for not awaited coroutines (Closes: #1014484) Checksums-Sha1: 92227507250bc00e00539ca1d3bafa58662b5870 2110 python-async-lru_1.0.3-3.dsc ab888ae58070dd6596f52dea876fc951cce2f087 2580 python-async-lru_1.0.3-3.debian.tar.xz d92e4f319e3aadb0663faebf950ff6e72764c095 7127 python-async-lru_1.0.3-3_amd64.buildinfo Checksums-Sha256: c4870783e2404bfed79f583356ff07021d14c502a74c2f08d4e68fdd38e8c5fe 2110 python-async-lru_1.0.3-3.dsc b9b0fb1233240462ef6c0d4580093b7b9214aed78bf9dfc25f1b35c3f01a73e6 2580 python-async-lru_1.0.3-3.debian.tar.xz ee3e98fb357b936e0c5eab947c2fbcb5a71fcfdd5c4154cda4b11d037f51d444 7127 python-async-lru_1.0.3-3_amd64.buildinfo Files: 5b875e8233a896105a233b96da283b34 2110 python optional python-async-lru_1.0.3-3.dsc fb0936ac47b4b7d8b6e851398f23adc1 2580 python optional python-async-lru_1.0.3-3.debian.tar.xz 395b9f4e4dde6d27b6ec55f63b3a14c1 7127 python optional python-async-lru_1.0.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmLGEOkUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQ+C8H+466LVnKvgwA0ceiIwFTXrUvn5gBAiE/ZsALFR7e 0X5p8U6o3GUthLgTNAohoTewqsbZ73apUDeZ478NYHZDtOj2VhgmmLL1Is38Deqd Dh+5+2deM2YuU+/6BaqFEawsmgwJhafOoLQHgMfvoPgXq/bF4l6GHd6mS4arpm6m f0R/FXRvqs+WulqPsA7SRHL37bNQm/dgNlEqL/a0rBBwABF51W8SWBYsJ0WojLOR RyfMM7IqP0/crL1p/L1GrmYnviU4/l+wb+ncA/oyHCVbrfAo3QtEQkM4AS9CxeKf PoYFPMD9J1Tf88X9TxnYsiwYZG5j16NPGW4fdserum0swmT1cFwferxkr9D0XT4C HXEL7pV5Iii6P1WbsqtDK/3m42fVPQrfgHwRsMJ3IQAEnI5CMxq1gHVsWZATfNv/ QMqwffdfOepXVgdenrXyAtCw0q++EYE+8twUSsR7H1IuHOvolID5nZesMAMuWQk/ TMrvErBebOjsm8eCaHBpe4HZzSmHTNPN2eiz =J3RY -END PGP SIGNATURE End Message ---
Bug#1014115: marked as done (uninstall does not properly remove enablement symlinks)
Your message dated Wed, 06 Jul 2022 22:55:40 + with message-id and subject line Bug#1014115: fixed in systemd 251.2-8 has caused the Debian Bug report #1014115, regarding uninstall does not properly remove enablement symlinks 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.) -- 1014115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-homed Version: 251.2-7 Severity: important (might be even RC, not properly cleaning up state on remove) # find systemd -name *home* -o -name *userdbd* # apt install systemd-homed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: systemd-userdbd The following NEW packages will be installed: systemd-homed systemd-userdbd 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 621 kB of archives. After this operation, 1433 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.debian.org/debian sid/main amd64 systemd-userdbd amd64 251.2-7 [150 kB] Get:2 http://ftp.debian.org/debian sid/main amd64 systemd-homed amd64 251.2-7 [471 kB] Fetched 621 kB in 0s (32.4 MB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package systemd-userdbd. (Reading database ... 498739 files and directories currently installed.) Preparing to unpack .../systemd-userdbd_251.2-7_amd64.deb ... Unpacking systemd-userdbd (251.2-7) ... Selecting previously unselected package systemd-homed. Preparing to unpack .../systemd-homed_251.2-7_amd64.deb ... Unpacking systemd-homed (251.2-7) ... Setting up systemd-userdbd (251.2-7) ... Created symlink /etc/systemd/system/sockets.target.wants/systemd-userdbd.socket -> /lib/systemd/system/systemd-userdbd.socket. Setting up systemd-homed (251.2-7) ... Created symlink /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service -> /lib/systemd/system/systemd-homed-activate.service. Created symlink /etc/systemd/system/dbus-org.freedesktop.home1.service -> /lib/systemd/system/systemd-homed.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> /lib/systemd/system/systemd- homed.service. Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 23. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed.service Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 41. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed-activate.service Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.14.0-1) ... [master 8d9b0a5] committing changes in /etc made by "apt install systemd-homed" Author: Michael Biebl 11 files changed, 33 insertions(+), 3 deletions(-) create mode 100644 systemd/homed.conf create mode 12 systemd/system/dbus-org.freedesktop.home1.service create mode 12 systemd/system/multi-user.target.wants/systemd-homed.service create mode 12 systemd/system/sockets.target.wants/systemd-userdbd.socket create mode 12 systemd/system/systemd-homed.service.wants/systemd-homed-activate.service → Issue number one: Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 23. Now purging the package again: # apt purge systemd-homed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: systemd-homed* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 1172 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 498771 files and directories currently installed.) Removing systemd-homed (251.2-7) ... Processing triggers for dbus (1.14.0-1) ... Processing triggers for man-db (2.10.2-1) ... (Reading database ... 498749 files and directories currently installed.) Purging configuration files for systemd-homed (251.2-7) ... [master 9e93901] committing changes in /etc made by "apt purge systemd-homed" Author: Michael Biebl 7 files changed, 3 insertions(+), 28 deletions(-) delete mode 100644 systemd/homed.conf # find systemd -name *home* systemd/system/dbus-org.freedesktop.home1.service systemd/system/multi-user.target.wants/systemd-homed.service systemd/system/systemd-homed.service.wants
Bug#1014491: python3-torch: import fails: undefined symbol
Hi, Thanks for the bug report. I'm aware of the break, and other users have reported this issue some time before: https://lists.debian.org/debian-ai/2022/06/msg00060.html The break is due to onnx 1.12 upgrade. The pytorch version in the new queue works fine with onnx 1.12, as mentioned in the above mailing list post. If you would like to continue using pytorch 1.8 for a while, you may need to pin onnx to the previous version, or rollback using our snapshot archive. When dealing with the pytorch 1.12 upgrade, I lost (to be honest I would like to stick to 1.8 but we have to go through python 3.10 transition) access to build machines due to complicated reasons, and the access will not be recovered. So in order to continue the pytorch upgrade, I have to upload reverse dependencies to unstable early, so that I can build pytorch and upload to the NEW queue. Theoretically this bug can only be resolved when pytorch 1.12 passes the new queue. On Wed, 2022-07-06 at 14:01 -0700, Dima Kogan wrote: > Package: python3-torch > Version: 1.8.1-5+b1 > Severity: grave > X-Debbugs-Cc: none, Dima Kogan > > Hi. Thanks for maintaining pytorch. I can't imagine the pain it took to > get this packaged. Currently it doesn't work, unfortunately: > > $ python3 -mtorch > > Traceback (most recent call last): > File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main > mod_name, mod_spec, code = _get_module_details(mod_name, _Error) > File "/usr/lib/python3.10/runpy.py", line 146, in _get_module_details > return _get_module_details(pkg_main_name, error) > File "/usr/lib/python3.10/runpy.py", line 110, in _get_module_details > __import__(pkg_name) > File "/usr/lib/python3/dist-packages/torch/__init__.py", line 196, in > > from torch._C import * > ImportError: /usr/lib/x86_64-linux-gnu/libtorch_cpu.so.1.8: undefined > symbol: > _ZN4onnx12optimization8OptimizeERKNS_10ModelProtoERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISA_EE > > This symbol is missing. I looked around, and I can't figure out which > package was supposed to provide it. Without it the linking fails, and > the package is unusable. Am I missing some dependency? > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), > (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, armhf > > Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_US.utf-8), LANGUAGE=en_US.utf-8 > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages python3-torch depends on: > ii libc6 2.33-7 > ii libdnnl22.6-1 > ii libgcc-s1 12.1.0-4 > ii libgloo00.0~git20220518.5b14351-1 > ii libgoogle-glog0v6 0.6.0-1 > ii libonnx11.12.0-1 > ii libprotobuf23 3.12.4-1+b2 > ii libstdc++6 12.1.0-4 > ii libtorch-test 1.8.1-5+b1 > ii libtorch1.8 1.8.1-5+b1 > ii python3 3.10.4-1+b1 > ii python3-future 0.18.2-5 > ii python3-numpy [python3-numpy-abi9] 1:1.21.5-1 > ii python3-pkg-resources 59.6.0-1 > ii python3-requests2.25.1+dfsg-2 > ii python3-six 1.15.0-2 > ii python3-typing-extensions 3.10.0.2-1 > ii python3-yaml5.4.1-1+b1 > ii python3.10 3.10.5-1 > > Versions of packages python3-torch recommends: > ii build-essential 12.9 > pn libtorch-dev > ii ninja-build 1.10.1-1 > pn pybind11-dev > > Versions of packages python3-torch suggests: > ii python3-hypothesis 5.43.3-1 > ii python3-pytest 6.2.5-1 > > -- no debconf information >
Bug#1013467: marked as done (djangorestframework-gis: FTBFS: ModuleNotFoundError: No module named 'pytz')
Your message dated Wed, 06 Jul 2022 22:49:54 +
with message-id
and subject line Bug#1013467: fixed in djangorestframework-gis 1.0-1
has caused the Debian Bug report #1013467,
regarding djangorestframework-gis: FTBFS: ModuleNotFoundError: No module named
'pytz'
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.)
--
1013467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djangorestframework-gis
Version: 0.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
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_test -- --system=custom --test-args="cd {build_dir}; {interpreter}
> tests/manage.py test tests/django_restframework_gis_tests"
> I: pybuild base:239: cd
> /<>/.pybuild/cpython3_3.9_djangorestframework-gis/build;
> python3.9 tests/manage.py test tests/django_restframework_gis_tests
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.9_djangorestframework-gis/build/tests/manage.py",
> line 10, in
> execute_from_command_line(sys.argv)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 420, in execute
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 124, in
> populate
> app_config.ready()
> File
> "/<>/.pybuild/cpython3_3.9_djangorestframework-gis/build/rest_framework_gis/apps.py",
> line 12, in ready
> from rest_framework.serializers import ModelSerializer
> File "/usr/lib/python3/dist-packages/rest_framework/serializers.py", line
> 29, in
> from rest_framework.fields import get_error_detail, set_value
> File "/usr/lib/python3/dist-packages/rest_framework/fields.py", line 32, in
>
> from pytz.exceptions import InvalidTimeError
> ModuleNotFoundError: No module named 'pytz'
> E: pybuild pybuild:369: test: plugin custom failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.9_djangorestframework-gis/build;
> python3.9 tests/manage.py test tests/django_restframework_gis_tests
> I: pybuild base:239: cd
> /<>/.pybuild/cpython3_3.10_djangorestframework-gis/build;
> python3.10 tests/manage.py test tests/django_restframework_gis_tests
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.10_djangorestframework-gis/build/tests/manage.py",
> line 10, in
> execute_from_command_line(sys.argv)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 420, in execute
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 124, in
> populate
> app_config.ready()
> File
> "/<>/.pybuild/cpython3_3.10_djangorestframework-gis/build/rest_framework_gis/apps.py",
> line 12, in ready
> from rest_framework.serializers import ModelSerializer
> File "/usr/lib/python3/dist-packages/rest_framework/serializers.py", line
> 29, in
> from rest_framework.fields import get_error_detail, set_value
> File "/usr/lib/python3/dist-packages/rest_framework/fields.py", line 32, in
>
> from pytz.exceptions import InvalidTimeError
> ModuleNotFoundError: No module named 'pytz'
> E: pybuild pybuild:369: test: plugin custom failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.10_djangorestframework-gis/build;
> python3.10 tests/manage.py test tests/django_restframework_gis_tests
> dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.10"
> --system=custom "--test-args=cd {build_dir}; {interpreter} tests/manage.py
> test tests/django_restframework_gis_tests" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2022/06/24/djangorestframework-gis_0.18-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
Processed: Re: bug #1005719: mumble: FTBFS with OpenSSL 3.0
Processing control commands: > tag -1 +fixed-upstream Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Added tag(s) fixed-upstream. -- 1005719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005719: bug #1005719: mumble: FTBFS with OpenSSL 3.0
Control: tag -1 +fixed-upstream On Wednesday, 6 July 2022 22:11:41 CEST Diederik de Haas wrote: > Control: tag -1 -fixed-upstream > Control: notforwarded -1 > > https://github.com/mumble-voip/mumble/pull/5352 titled > "BUILD(crypto): Migrate to OpenSSL 3.0 API" is merged into master (branch) > with commit f4cea62ed9, but that is NOT part of the 1.4.230 release. Removing the fixed-upstream tag was incorrect, so reinstate it. The original reason why the tag was previously set, was incorrect, but as I describe above, it is now fixed in the master branch. signature.asc Description: This is a digitally signed message part.
Processed: Bug#1014115 marked as pending in systemd
Processing control commands: > tag -1 pending Bug #1014115 [systemd-homed] uninstall does not properly remove enablement symlinks Added tag(s) pending. -- 1014115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014115: marked as pending in systemd
Control: tag -1 pending Hello, Bug #1014115 in systemd 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/systemd-team/systemd/-/commit/dd0c655fa5ff1c65ef0ed1dd427fa3b2a66c9bc1 Add versioned dependency on init-system-helpers to systemd-homed Ensure that we have a version of deb-systemd-helper which properly handles loops in Also= dependencies. Closes: #1014115 (this message was generated automatically) -- Greetings https://bugs.debian.org/1014115
Processed: Bug#1013467 marked as pending in djangorestframework-gis
Processing control commands: > tag -1 pending Bug #1013467 [src:djangorestframework-gis] djangorestframework-gis: FTBFS: ModuleNotFoundError: No module named 'pytz' Added tag(s) pending. -- 1013467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013467: marked as pending in djangorestframework-gis
Control: tag -1 pending Hello, Bug #1013467 in djangorestframework-gis 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/python-team/packages/djangorestframework-gis/-/commit/95529f69498976caca45c9bb24087354e6318a93 New upstream release (Closes: #1013467). (this message was generated automatically) -- Greetings https://bugs.debian.org/1013467
Bug#1014492: guzzle: CVE-2022-31090 CVE-2022-31091
Source: guzzle X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for guzzle. CVE-2022-31090[0]: | Guzzle, an extensible PHP HTTP client. `Authorization` headers on | requests are sensitive information. In affected versions when using | our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option | to specify an `Authorization` header. On making a request which | responds with a redirect to a URI with a different origin (change in | host, scheme or port), if we choose to follow it, we should remove the | `CURLOPT_HTTPAUTH` option before continuing, stopping curl from | appending the `Authorization` header to the new request. Affected | Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. | Affected users using any earlier series of Guzzle should upgrade to | Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in | Guzzle 7.4.2, where a change in host would trigger removal of the | curl-added Authorization header, however this earlier fix did not | cover change in scheme or change in port. If you do not require or | expect redirects to be followed, one should simply disable redirects | all together. Alternatively, one can specify to use the Guzzle steam | handler backend, rather than curl. https://github.com/guzzle/guzzle/security/advisories/GHSA-25mq-v84q-4j7r https://github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 (7.4.5) CVE-2022-31091[1]: | Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` | headers on requests are sensitive information. In affected versions on | making a request which responds with a redirect to a URI with a | different port, if we choose to follow it, we should remove the | `Authorization` and `Cookie` headers from the request, before | containing. Previously, we would only consider a change in host or | scheme. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon | as possible. Affected users using any earlier series of Guzzle should | upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was | implemented in Guzzle 7.4.2, where a change in host would trigger | removal of the curl-added Authorization header, however this earlier | fix did not cover change in scheme or change in port. An alternative | approach would be to use your own redirect middleware, rather than | ours, if you are unable to upgrade. If you do not require or expect | redirects to be followed, one should simply disable redirects all | together. https://github.com/guzzle/guzzle/security/advisories/GHSA-q559-8m2m-g699 https://github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 (7.4.5) If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-31090 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31090 [1] https://security-tracker.debian.org/tracker/CVE-2022-31091 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31091 Please adjust the affected versions in the BTS as needed.
Bug#1014491: python3-torch: import fails: undefined symbol
Package: python3-torch Version: 1.8.1-5+b1 Severity: grave X-Debbugs-Cc: none, Dima Kogan Hi. Thanks for maintaining pytorch. I can't imagine the pain it took to get this packaged. Currently it doesn't work, unfortunately: $ python3 -mtorch Traceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main mod_name, mod_spec, code = _get_module_details(mod_name, _Error) File "/usr/lib/python3.10/runpy.py", line 146, in _get_module_details return _get_module_details(pkg_main_name, error) File "/usr/lib/python3.10/runpy.py", line 110, in _get_module_details __import__(pkg_name) File "/usr/lib/python3/dist-packages/torch/__init__.py", line 196, in from torch._C import * ImportError: /usr/lib/x86_64-linux-gnu/libtorch_cpu.so.1.8: undefined symbol: _ZN4onnx12optimization8OptimizeERKNS_10ModelProtoERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaISA_EE This symbol is missing. I looked around, and I can't figure out which package was supposed to provide it. Without it the linking fails, and the package is unusable. Am I missing some dependency? -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8), LANGUAGE=en_US.utf-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-torch depends on: ii libc6 2.33-7 ii libdnnl22.6-1 ii libgcc-s1 12.1.0-4 ii libgloo00.0~git20220518.5b14351-1 ii libgoogle-glog0v6 0.6.0-1 ii libonnx11.12.0-1 ii libprotobuf23 3.12.4-1+b2 ii libstdc++6 12.1.0-4 ii libtorch-test 1.8.1-5+b1 ii libtorch1.8 1.8.1-5+b1 ii python3 3.10.4-1+b1 ii python3-future 0.18.2-5 ii python3-numpy [python3-numpy-abi9] 1:1.21.5-1 ii python3-pkg-resources 59.6.0-1 ii python3-requests2.25.1+dfsg-2 ii python3-six 1.15.0-2 ii python3-typing-extensions 3.10.0.2-1 ii python3-yaml5.4.1-1+b1 ii python3.10 3.10.5-1 Versions of packages python3-torch recommends: ii build-essential 12.9 pn libtorch-dev ii ninja-build 1.10.1-1 pn pybind11-dev Versions of packages python3-torch suggests: ii python3-hypothesis 5.43.3-1 ii python3-pytest 6.2.5-1 -- no debconf information
Bug#1014489: deepdiff: autopkgtest failing due to missing dependencies
Source: deepdiff Version: 5.8.2-2 Severity: serious The recent patch to add python3-toml and python3-clevercsv to the Build-Depends forgot to add the same dependencies to the autopkgtest dependencies. As a result, the autopkgtests are now failing and this package is preventing the migration of pytest to testing. Best wishes, Julian
Bug#1013812: marked as done (luajit doesn't work on ppc64el; use lua or remove binaries on ppc64el)
Your message dated Wed, 6 Jul 2022 22:30:24 +0200 with message-id and subject line Re: Your mail has caused the Debian Bug report #1013812, regarding luajit doesn't work on ppc64el; use lua or remove binaries on ppc64el 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.) -- 1013812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nginx Version: 1.20.2-2 Severity: serious X-Debbugs-CC: 1004...@bugs.debian.org, lu...@debian.org Control: reopen 1004511 Control: block 1004511 by -1 Control: block 1012362 by 1004511 Control: clone -1 -2 -3 -4 -5 -6 -7 -8 Control: reassign -2 src:aegisub 3.2.2+dfsg-6 Control: reassign -3 src:ettercap 1:0.8.3.1-9 Control: reassign -4 src:knot-resolver 5.5.1-1 Control: reassign -5 src:snort 2.9.15.1-6 Control: reassign -6 src:trafficserver 9.1.2+ds-10 Control: reassign -7 src:uwsgi-plugin-luajit 0.0.7 Control: reassign -8 src:luakit 1:2.3-1 Dear maintainers, We have been working for a while to get a working libluajit on ppc64el (for reference, see history in bug #1012362). In the end we concluded that it's not going to work as commitment upstream is lacking to support ppc64el. Your source package build depends on libluajit-5.1-dev when building on ppc64el and at least one of its binaries depends on libluajit-5.1-2 on that architecture. Please use liblua on ppc64el if that works for your package, otherwise please request removal of the binaries on ppc64el (e.g. by reassigning the bug to ftp.debian.org, lowering severity and re-titling appropriately). Sorry we couldn't solve the problem in a better way. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 9.1.2+ds-13 On Mon, 4 Jul 2022 08:21:45 +0200 Jean Baptiste Favre wrote: Control: fixed 1013812 9.1.2+ds-13 Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1005719: bug #1005719: mumble: FTBFS with OpenSSL 3.0
Control: tag -1 -fixed-upstream Control: notforwarded -1 On 19 May 2022 15:01:12 + Chris Knadle wrote: > Mumble 1.3 is not buildable with OpenSSL 3.0 and there is no patch available > to allow doing so. There was an upstream attempt to backport patches for > Mumble 1.4 for Mumble 1.3 but there were enough issues that the effort had > to be abandoned. > > https://github.com/mumble-voip/mumble/pull/5354 Removing the fixed-upstream tag and the forwarded field. > I'm currently trying to package Mumble 1.4 which could resolve the problem, https://github.com/mumble-voip/mumble/pull/5352 titled "BUILD(crypto): Migrate to OpenSSL 3.0 API" is merged into master (branch) with commit f4cea62ed9, but that is NOT part of the 1.4.230 release. Nonetheless it would still be good to have 1.4.230 in Debian :-) signature.asc Description: This is a digitally signed message part.
Processed: Re: bug #1005719: mumble: FTBFS with OpenSSL 3.0
Processing control commands: > tag -1 -fixed-upstream Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Removed tag(s) fixed-upstream. > notforwarded -1 Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Unset Bug forwarded-to-address -- 1005719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014488: scapy: flaky autopkgtest: No such file or directory: 'isotpsend'
Source: scapy Version: 2.4.4-4 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package on arm64 because it was showing up as a regression for the upload of openssl. I noticed that the test regularly fails and I saw failures on other architectures too, even in stable. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/s/scapy/ https://ci.debian.net/data/autopkgtest/testing/amd64/s/scapy/23043408/log.gz ###(006)=[failed] Check if can-isotp and can-utils are installed on this system >>> p1 = subprocess.Popen(['lsmod'], stdout = subprocess.PIPE) >>> p2 = subprocess.Popen(['grep', '^can_isotp'], stdout = subprocess.PIPE, stdin=p1.stdout) >>> p1.stdout.close() >>> if p1.wait() == 0 and p2.wait() == 0 and b"can_isotp" in p2.stdout.read(): ... p = subprocess.Popen(["isotpsend", "-s1", "-d0", iface0], stdin = subprocess.PIPE) ... p.communicate(b"01") ... if p.returncode == 0: ... ISOTP_KERNEL_MODULE_AVAILABLE = True ... Traceback (most recent call last): File "", line 3, in File "/usr/lib/python3.10/subprocess.py", line 969, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1845, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'isotpsend' sys:1: ResourceWarning: unclosed file <_io.BufferedReader name=9> OpenPGP_signature Description: OpenPGP digital signature
Processed: tagging 1014470, tagging 1014471, tagging 1014468, tagging 1014478
Processing commands for cont...@bugs.debian.org: > tags 1014470 + upstream Bug #1014470 [src:u-boot] u-boot: CVE-2022-30552 CVE-2022-30790 Added tag(s) upstream. > tags 1014471 + upstream Bug #1014471 [src:u-boot] u-boot: CVE-2022-30767 Added tag(s) upstream. > tags 1014468 + upstream Bug #1014468 [src:edk2] edk2: CVE-2021-38576 CVE-2021-38577 CVE-2021-38578 Added tag(s) upstream. > tags 1014478 + upstream Bug #1014478 [src:radare2] radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022-0476 CVE-2022-0518 CVE-2022-0519 CVE-2022-0521 CVE-2022-0523 CVE-2022-0559 CVE-2022-0676 CVE-2022-0695 CVE-2022-0712 CVE-2022-0713 CVE-2022-0139 CVE-2022-0173 CVE-2022-0419 CVE-2022-1031 CVE-2022-1283 CVE-2022-1284 CVE-2022-1296 CVE-2022-1297 CVE-2022-1382 CVE-2022-1444 CVE-2022-1437 CVE-2022-1451 CVE-2022-1452 CVE-2022-1649 CVE-2022-1383 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014468 1014470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014470 1014471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014471 1014478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1014478 in 5.5.0+dfsg-1
Processing commands for cont...@bugs.debian.org: > found 1014478 5.5.0+dfsg-1 Bug #1014478 [src:radare2] radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022-0476 CVE-2022-0518 CVE-2022-0519 CVE-2022-0521 CVE-2022-0523 CVE-2022-0559 CVE-2022-0676 CVE-2022-0695 CVE-2022-0712 CVE-2022-0713 CVE-2022-0139 CVE-2022-0173 CVE-2022-0419 CVE-2022-1031 CVE-2022-1283 CVE-2022-1284 CVE-2022-1296 CVE-2022-1297 CVE-2022-1382 CVE-2022-1444 CVE-2022-1437 CVE-2022-1451 CVE-2022-1452 CVE-2022-1649 CVE-2022-1383 Marked as found in versions radare2/5.5.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1004387: Upstream seems abandoned
Processing control commands: > severity -1 important Bug #1004387 [python3-pyinotify] Upstream seems abandoned Severity set to 'important' from 'serious' -- 1004387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004387: Upstream seems abandoned
Control: severity -1 important Am 06.07.22 um 21:08 schrieb Enrico Zini: Feel free to remove the 'serious' severity.
Bug#1014481: marked as done (junitparser: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k-)
Your message dated Wed, 06 Jul 2022 19:04:15 + with message-id and subject line Bug#1014481: fixed in junitparser 2.7.0-2 has caused the Debian Bug report #1014481, regarding junitparser: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k- 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.) -- 1014481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: junitparser Version: 2.7.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/junitparser/ I had a closer look at the error logs and identified the regression as: 'deprecated pytest feature: -k-'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: junitparser Source-Version: 2.7.0-2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of junitparser, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated junitparser 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: Wed, 06 Jul 2022 20:44:37 +0200 Source: junitparser Architecture: source Version: 2.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1014481 Changes: junitparser (2.7.0-2) unstable; urgency=medium . * Eliminate one more pytest -k- occurence (Closes: #1014481) Checksums-Sha1: 50c104dfa5a12dcf1011a321256e0ab8acbe7feb 2023 junitparser_2.7.0-2.dsc 0b7da3ddfd05e9d17577eec5cbbf499bcc8f1f26 3352 junitparser_2.7.0-2.debian.tar.xz 5e402e085524ed9287b3b22637b5be31e61a397b 6605 junitparser_2.7.0-2_source.buildinfo Checksums-Sha256: c97f594d3a85752db71b5728a5efd4e1a52aca1aacb4b9337826890b0c8f16e2 2023 junitparser_2.7.0-2.dsc 622ef46bf2d7334dbe026c4a70a09ab113f82474ea7c84b44e1e775353287585 3352 junitparser_2.7.0-2.debian.tar.xz 206c9eea1e987f99d04262770fb71d04a072a3d1142df77fb5eee3aa2e5d2cd2 6605 junitparser_2.7.0-2_source.buildinfo Files: 03aa40a5d1d81be238446f6c83bc4fd4 2023 python optional junitparser_2.7.0-2.dsc cd1ca405f5d41c210784b1ddc957ad37 3352 python optional junitparser_2.7.0-2.debian.tar.xz 8c5c85a59689fe6af496b8b85047f694 6605 python optional junitparser_2.7.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHHBAEBCgAxFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmLF2K0THGJhZ2VAbGlu dXRyb25peC5kZQAKCRAfXHqLRVZDFIT7C/sGo8c/S4RgkQ89IGVcunNp+FIreBL+ 6ZfNeYE0CHGrdwF5ww2P1VGH7GR7APHT7HDhiG8RPD0TOBiMRn8IDebL1sCmpQgA v2ht8S5Gz+l1I6gLJr1jokWH17lA6RvV+yCqSsKiLMSF+WQxlRjegULfM9GkksxN JxEVe1CE3RhAavkZdvps0k7jiAkdLut7wInriCVO7QK7klAId1XDQSD9Ha9spdE9 pHUc9ozWlRfjtCVUvVzWkPB6B7lqifcVv6LjY42RVvuk/uxFmsLc432feRA+n06n hJhTn/siYZdAz8bdVIVd6TrKUEt0fFFh/B4z030ddoYjfcCaIiZwubnO6/+h8Kmp vWiKfQejnojjxNNwx5StjPzmHOcNs+YNdxb3c+oDbO0V8IaN5qJSjFObYTTAKRZY sDUf4NGCTA6vIeiEq1iI2kognP61+LhkS+6+SG/JyEVECgf5yfGJsZuPhhoy5vB3 KcHIARNRwdNymAydYOMCAH4Z1uLmg29yxcg= =dSpq -END PGP SIGNATURE End Message ---
Bug#1014108: marked as done (python-ldap: autopkgtest regression: Command 'slapadd' not found)
Your message dated Wed, 06 Jul 2022 18:50:05 +
with message-id
and subject line Bug#1014108: fixed in python-ldap 3.4.0-2
has caused the Debian Bug report #1014108,
regarding python-ldap: autopkgtest regression: Command 'slapadd' not found
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.)
--
1014108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ldap
Version: 3.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-ldap the autopkgtest of python-ldap fails
in testing when that autopkgtest is run with the binary packages of
python-ldap from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
python-ldapfrom testing3.4.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? It seems like a missing
new (test) dependency.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-ldap
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-ldap/23177881/log.gz
==
ERROR: setUpClass (t_bind.TestBinds)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_cext.TestLdapCExtension)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.v0m7b8wh/downtmp/autopkgtest_tmp/Tests/t_cext.py",
line 30, in setUpClass
super().setUpClass()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_edit.EditionTests)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.v0m7b8wh/downtmp/autopkgtest_tmp/Tests/t_edit.py",
line 16, in setUpClass
super().setUpClass()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_ldap_options.TestLDAPObjectOptions)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
Processed: python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - AssertionError
Processing control commands: > affects -1 src:pytest Bug #1014487 [src:python-parameterized] python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - AssertionError Added indication that 1014487 affects src:pytest -- 1014487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014487: python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - AssertionError
Source: python-parameterized Version: 0.8.1-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/python-parameterized/ I had a closer look at the error logs and identified the regression as: 'AssertionError'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1014486: python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 1
Source: python-etelemetry Version: 0.3.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/python-etelemetry/ I had a closer look at the error logs and identified the regression as: 'non-zero exit status 1'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 1
Processing control commands: > affects -1 src:pytest Bug #1014486 [src:python-etelemetry] python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 1 Added indication that 1014486 affects src:pytest -- 1014486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-b2sdk: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 5
Processing control commands: > affects -1 src:pytest Bug #1014485 [src:python-b2sdk] python-b2sdk: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 5 Added indication that 1014485 affects src:pytest -- 1014485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014485: python-b2sdk: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 5
Source: python-b2sdk Version: 1.3.0-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/python-b2sdk/ I had a closer look at the error logs and identified the regression as: 'non-zero exit status 5'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: python-async-lru: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - Future exception was never retrieved; ZeroDivisionError
Processing control commands: > affects -1 src:pytest Bug #1014484 [src:python-async-lru] python-async-lru: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - Future exception was never retrieved; ZeroDivisionError Added indication that 1014484 affects src:pytest -- 1014484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pytest-twisted: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - fixture 'testdir' not found
Processing control commands: > affects -1 src:pytest Bug #1014483 [src:pytest-twisted] pytest-twisted: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - fixture 'testdir' not found Added indication that 1014483 affects src:pytest -- 1014483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014484: python-async-lru: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - Future exception was never retrieved; ZeroDivisionError
Source: python-async-lru Version: 1.0.3-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/python-async-lru/ I had a closer look at the error logs and identified the regression as: 'Future exception was never retrieved; ZeroDivisionError'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1014483: pytest-twisted: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - fixture 'testdir' not found
Source: pytest-twisted Version: 1.13.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/pytest-twisted/ I had a closer look at the error logs and identified the regression as: 'fixture 'testdir' not found'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: nibabel: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ResourceWarning: unclosed file
Processing control commands: > affects -1 src:pytest Bug #1014482 [src:nibabel] nibabel: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ResourceWarning: unclosed file Added indication that 1014482 affects src:pytest -- 1014482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014482: nibabel: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ResourceWarning: unclosed file
Source: nibabel Version: 3.2.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/nibabel/ I had a closer look at the error logs and identified the regression as: 'ResourceWarning: unclosed file'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1014481: junitparser: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k-
Source: junitparser Version: 2.7.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/junitparser/ I had a closer look at the error logs and identified the regression as: 'deprecated pytest feature: -k-'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: junitparser: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k-
Processing control commands: > affects -1 src:pytest Bug #1014481 [src:junitparser] junitparser: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k- Added indication that 1014481 affects src:pytest -- 1014481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014480: deepdiff: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ImportError: Toml needs to be installed.
Source: deepdiff Version: 5.8.2-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian-pyt...@lists.debian.org Usertags: pytest7 User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:pytest Dear maintainer(s), The latest version of pytest in unstable (7.1.2-2) seems to be breaking the autopkgtests for this package. This regression currently keeps pytest from migrating to testing. You can find the CI logs here: https://ci.debian.net/packages/d/deepdiff/ I had a closer look at the error logs and identified the regression as: 'ImportError: Toml needs to be installed.'. Hopefully, that's helpful! If you fail to reproduce this, please provide a build log and diff it with the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: deepdiff: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ImportError: Toml needs to be installed.
Processing control commands: > affects -1 src:pytest Bug #1014480 [src:deepdiff] deepdiff: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ImportError: Toml needs to be installed. Added indication that 1014480 affects src:pytest -- 1014480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1014108 marked as pending in python-ldap
Processing control commands: > tag -1 pending Bug #1014108 [src:python-ldap] python-ldap: autopkgtest regression: Command 'slapadd' not found Added tag(s) pending. -- 1014108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014108: marked as pending in python-ldap
Control: tag -1 pending Hello, Bug #1014108 in python-ldap 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/python-team/packages/python-ldap/-/commit/4ff10772296bf462ab4b7b759bc75ee728f90642 Add patch to search for slapadd in sbin path (Closes: #1014108). (this message was generated automatically) -- Greetings https://bugs.debian.org/1014108
Bug#1014478: radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022-0476 CVE-2022-0
Source: radare2 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for radare2. CVE-2022-1714[0]: | Heap-based Buffer Overflow in GitHub repository radareorg/radare2 | prior to 5.7.0. The bug causes the program reads data past the end of | the intented buffer. Typically, this can allow attackers to read | sensitive information from other memory locations or cause a crash. https://huntr.dev/bounties/1c22055b-b015-47a8-a57b-4982978751d0 https://github.com/radareorg/radare2/commit/3ecdbf8e21186a9c5a4d3cfa3b1e9fd27045340e CVE-2022-1809[1]: | Access of Uninitialized Pointer in GitHub repository radareorg/radare2 | prior to 5.7.0. https://huntr.dev/bounties/0730a95e-c485-4ff2-9a5d-bb3abfda0b17 https://github.com/radareorg/radare2/commit/919e3ac1a13f753c73e7a8e8d8bb4a143218732d CVE-2022-1899[2]: | Out-of-bounds Read in GitHub repository radareorg/radare2 prior to | 5.7.0. https://huntr.dev/bounties/8a3dc5cb-08b3-4807-82b2-77f08c137a04 https://github.com/radareorg/radare2/commit/193f4fe01d7f626e2ea937450f2e0c4604420e9d CVE-2022-0849[3]: | Use After Free in r_reg_get_name_idx in GitHub repository | radareorg/radare2 prior to 5.6.6. https://huntr.dev/bounties/29c5f76e-5f1f-43ab-a0c8-e31951e407b6 https://github.com/radareorg/radare2/commit/10517e3ff0e609697eb8cde60ec8dc999ee5ea24 CVE-2022-1052[4]: | Heap Buffer Overflow in iterate_chained_fixups in GitHub repository | radareorg/radare2 prior to 5.6.6. https://huntr.dev/bounties/3b3b7f77-ab8d-4de3-999b-eeec0a3eebe7 https://github.com/radareorg/radare2/commit/0052500c1ed5bf8263b26b9fd7773dbdc6f170c4 CVE-2022-1061[5]: | Heap Buffer Overflow in parseDragons in GitHub repository | radareorg/radare2 prior to 5.6.8. https://huntr.dev/bounties/a7546dae-01c5-4fb0-8a8e-c04ea4e9bac7 https://github.com/radareorg/radare2/commit/d4ce40b516ffd70cf2e9e36832d8de139117d522 CVE-2022-1207[6]: | Out-of-bounds read in GitHub repository radareorg/radare2 prior to | 5.6.8. This vulnerability allows attackers to read sensitive | information from outside the allocated buffer boundary. https://huntr.dev/bounties/7b979e76-ae54-4132-b455-0833e45195eb https://github.com/radareorg/radare2/commit/605785b65dd356d46d4487faa41dbf90943b8bc1 CVE-2022-1237[7]: | Improper Validation of Array Index in GitHub repository | radareorg/radare2 prior to 5.6.8. This vulnerability is heap overflow | and may be exploitable. For more general description of heap buffer | overflow, see [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/ad3c9c4c-76e7-40c8-bd4a-c095acd8bb40 https://github.com/radareorg/radare2/commit/2d782cdaa2112c10b8dd5e7a93c134b2ada9c1a6 CVE-2022-1238[8]: | Heap-based Buffer Overflow in libr/bin/format/ne/ne.c in GitHub | repository radareorg/radare2 prior to 5.6.8. This vulnerability is | heap overflow and may be exploitable. For more general description of | heap buffer overflow, see | [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/47422cdf-aad2-4405-a6a1-6f63a3a93200 https://github.com/radareorg/radare2/commit/c40a4f9862104ede15d0ba05ccbf805923070778 CVE-2022-1240[9]: | Heap buffer overflow in libr/bin/format/mach0/mach0.c in GitHub | repository radareorg/radare2 prior to 5.8.6. If address sanitizer is | disabled during the compiling, the program should executes into the | `r_str_ncpy` function. Therefore I think it is very likely to be | exploitable. For more general description of heap buffer overflow, see | [CWE](https://cwe.mitre.org/data/definitions/122.html). https://huntr.dev/bounties/e589bd97-4c74-4e79-93b5-0951a281facc https://github.com/radareorg/radare2/commit/ca8d8b39f3e34a4fd943270330b80f1148129de4 CVE-2022-1244[10]: | heap-buffer-overflow in GitHub repository radareorg/radare2 prior to | 5.6.8. This vulnerability is capable of inducing denial of service. https://huntr.dev/bounties/8ae2c61a-2220-47a5-bfe8-fe6d41ab1f82 https://github.com/radareorg/radare2/commit/2b77b277d67ce061ee6ef839e7139ebc2103c1e3 CVE-2022-0476[11]: | Denial of Service in GitHub repository radareorg/radare2 prior to | 5.6.4. https://huntr.dev/bounties/81ddfbda-6c9f-4b69-83ff-85b15141e35d https://github.com/radareorg/radare2/commit/27fe8031782d3a06c3998eaa94354867864f9f1b CVE-2022-0518[12]: | Heap-based Buffer Overflow in GitHub repository radareorg/radare2 | prior to 5.6.2. https://huntr.dev/bounties/10051adf-7ddc-4042-8fd0-8e9e0c5b1184 https://github.com/radareorg/radare2/commit/9650e3c352f675687bf6c6f65ff2c4a3d0e288fa CVE-2022-0519[13]: | Buffer Access with Incorrect Length Value in GitHub repository | radareorg/radare2 prior to 5.6.2. https://huntr.dev/bounties/af85b9e1-d1cf-4c0e-ba12-525b82b7c1e3 https://github.com/radareorg/radare2/commit/6c4428f018d385fc80a33ecddcb37becea685dd5 CVE-2022-0521[14]: | Access of Memory Location After End of Buffer in GitHub repository | radareorg/radare2 prior to 5.6.2.
Processed: Bug#1013710 marked as pending in python-can
Processing control commands: > tag -1 pending Bug #1013710 [src:python-can] python-can: FTBFS: pytest7 regression, AttributeError: pytest.approx is not supported in a boolean context Ignoring request to alter tags of bug #1013710 to the same tags previously set -- 1013710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013710: marked as pending in python-can
Control: tag -1 pending Hello, Bug #1013710 in python-can 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/python-team/packages/python-can/-/commit/02b04f344c5dd324e65071ff1e12873e1e37338f Add patch to fix pytest.approx assertions Closes: #1013710 (this message was generated automatically) -- Greetings https://bugs.debian.org/1013710
Bug#1013710: marked as pending in python-can
Control: tag -1 pending Hello, Bug #1013710 in python-can 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/python-team/packages/python-can/-/commit/75a36667b5c62dbb271d5d8ec0cc669d5afa526b Bump d/changelog Closes: #1013710 (this message was generated automatically) -- Greetings https://bugs.debian.org/1013710
Processed: Bug#1013710 marked as pending in python-can
Processing control commands: > tag -1 pending Bug #1013710 [src:python-can] python-can: FTBFS: pytest7 regression, AttributeError: pytest.approx is not supported in a boolean context Added tag(s) pending. -- 1013710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1014239 is forwarded to https://salsa.debian.org/bottoms/pkg-uhd/-/merge_requests/2
Processing commands for cont...@bugs.debian.org: > forwarded 1014239 https://salsa.debian.org/bottoms/pkg-uhd/-/merge_requests/2 Bug #1014239 [src:uhd] uhd: FTBFS on mipsel: mv: cannot stat 'debian/tmp/usr/bin/usrp_hwd.py': No such file or directory Set Bug forwarded-to-address to 'https://salsa.debian.org/bottoms/pkg-uhd/-/merge_requests/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004387: Upstream seems abandoned
On Wed, 26 Jan 2022 15:42:43 +0100 Enrico Zini wrote: This project is unrelated to the *PyInotify* project that existed prior to this one (this project began in 2015). That project is defunct and no longer available. Why is it defunct? Is it also in Debian? If not this is not a serious bug.
Bug#1014462: libzapojit: unmaintained, only used by gnome-documents
Source: libzapojit Version: 3.34.0-4 Severity: serious libzapojit has been archived. That means that bug reports, bug fixes, translations, etc. are no longer being accepted for it. https://gitlab.gnome.org/GNOME/libzapojit https://discourse.gnome.org/t/gnome-online-miners-is-archived/10374 It was only really used by gnome-documents which is being removed from Debian. Therefore, we'll remove libzapojit too. Thank you, Jeremy Bicha
Processed: gnome-online-miners: unmaintained
Processing control commands: > block -1 by 1014423 Bug #1014461 [src:gnome-online-miners] gnome-online-miners: unmaintained 1014461 was not blocked by any bugs. 1014461 was not blocking any bugs. Added blocking bug(s) of 1014461: 1014423 -- 1014461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014461: gnome-online-miners: unmaintained
Source: gnome-online-miners Version: 3.34.0-4 Severity: serious Control: block -1 by 1014423 gnome-online-miners has been archived. That means that bug reports, bug fixes, translations, etc. are no longer being accepted for it. https://gitlab.gnome.org/GNOME/gnome-online-miners https://discourse.gnome.org/t/gnome-online-miners-is-archived/10374 We will probably remove gnome-online-miners from Debian soon. Thank you, Jeremy Bicha
Bug#1013659: marked as done (apertium-spa: FTBFS: configure: error: You don't have lrx-comp installed)
Your message dated Wed, 06 Jul 2022 13:48:53 + with message-id and subject line Bug#1013659: fixed in apertium-spa 1.1.0~r79716-3 has caused the Debian Bug report #1013659, regarding apertium-spa: FTBFS: configure: error: You don't have lrx-comp installed 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.) -- 1013659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-spa Version: 1.1.0~r79716-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for lttoolbox >= 3.3.2... yes > checking for lt-print... /usr/bin/lt-print > checking for cg-comp... /usr/bin/cg-comp > checking for cg-proc... /usr/bin/cg-proc > checking for lrx-comp... false > configure: error: You don't have lrx-comp installed > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/06/24/apertium-spa_1.1.0~r79716-2.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! 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 If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: apertium-spa Source-Version: 1.1.0~r79716-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of apertium-spa, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated apertium-spa 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: Wed, 06 Jul 2022 19:05:37 +0530 Source: apertium-spa Architecture: source Version: 1.1.0~r79716-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Nilesh Patra Closes: 1013659 Changes: apertium-spa (1.1.0~r79716-3) unstable; urgency=medium . * Team upload. * B-D on apertium-lex-tools-dev instead of apertium-lex-tools (Closes: #1013659) * Drop compat file, rely on debhelper-compat and bump compat level to 13 * Bump Standards-Version to 4.6.1 (no changes needed) Checksums-Sha1: 45e15529e3d3713d13a64627de669ecde3d8c995 2144 apertium-spa_1.1.0~r79716-3.dsc 3dfb55e09086526d7af24805165323326f605788 2360 apertium-spa_1.1.0~r79716-3.debian.tar.xz a3788a6266afa0715dddf3ace7db88189301034f 6869 apertium-spa_1.1.0~r79716-3_amd64.buildinfo Checksums-Sha256: d8e1ba4b2049844ef32c228a888ce3284ac768d9f4233b071bca1bb8d1c02674 2144 apertium-spa_1.1.0~r79716-3.dsc cefd52270b36e139c5fa3cd4624964d2faf0364859f5716c3ab6f12549388114 2360 apertium-spa_1.1.0~r79716-3.debian.tar.xz ca549c2fcc7bcd0ed43070b9908c22760f07e43db772c905adc8fe0dca55442b 6869 apertium-spa_1.1.0~r79716-3_amd64.buildinfo Files: 12e8304cfe23021c878693924d5b4e0c 2144 science optional apertium-spa_1.1.0~r79716-3.dsc 16a661b9f5ccbbad29b6395a1b668ca6 2360 science optional apertium-spa_1.1.0~r79716-3.debian.tar.xz 4b7421f6b4555f08a03c95434c5edfc3 6869 science optional apertium-spa_1.1.0~r79716-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmLFkTASHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxbcAP/jlIUgUYgASJK9HyArjdeSZljGkqc4j5 hYLhtJcK/o5TOWvQYdut7BATxC7+CcOptWTQvKjV1E1pkmSSKBdAA2comWERHEg4 Q19vtDW5SVvRnAozuBlwkbCwTNxxnJkJfe7qjlT1GF+KW56x0qW8/P0uInQ3AwG+ kLVZB12rGeD1znuJmTk+FRE7b1iqL553ECV8beL34sHppP3QJLz7B/jE82GZXl2h
Bug#1004587: closed by Debian FTP Masters (reply to Timo Röhling ) (Bug#1004587: fixed in pyglet 1.5.26+ds-1)
On Wed, 6 Jul 2022 00:21:28 +0200 Sebastian Ramacher wrote: As the dependencies are hard-coded in Depends, the dependencies also need to be updated. Oh, of course, I'm sorry! Fixed upload incoming. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#928224: marked as done (Valgrind is broken on armhf)
Your message dated Wed, 06 Jul 2022 12:49:29 + with message-id and subject line Bug#928224: fixed in valgrind 1:3.18.1-1.1 has caused the Debian Bug report #928224, regarding Valgrind is broken on armhf 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.) -- 928224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: valgrind Version: 1:3.14.0-3 Severity: important Hi, i encountered a bug in valgrind. I tried to analyze an application on an armhf platform but valgrind didn't worked. It does not even work on /bin/true (output below). Installed libc6 version: libc6-dgb:armhf 2.28-8 valgrind /bin/true ==12463== Memcheck, a memory error detector ==12463== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==12463== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==12463== Command: /bin/true ==12463== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: index valgrind: in an object with soname matching: ld-linux-armhf.so.3 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-armhf.so.3 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. Best regards, Benjamin --- End Message --- --- Begin Message --- Source: valgrind Source-Version: 1:3.18.1-1.1 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of valgrind, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated valgrind 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, 01 Jul 2022 13:58:19 +0200 Source: valgrind Architecture: source Version: 1:3.18.1-1.1 Distribution: unstable Urgency: medium Maintainer: Alessandro Ghedini Changed-By: Mathieu Malaterre Closes: 928224 Changes: valgrind (1:3.18.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix remove neon requirement from armhf binaries. Closes: #928224 Checksums-Sha1: 17b6cbaef40901ab75ab29bf8788d0ffa2ce52af 2446 valgrind_3.18.1-1.1.dsc 97dd37dfb5dae75c1a547f7e6af309fe4cbacd55 27132 valgrind_3.18.1-1.1.debian.tar.xz 1eb869485b29559281b9993cb8ab50a9c779344d 9302 valgrind_3.18.1-1.1_source.buildinfo Checksums-Sha256: 9608e9978c79d3e3c4fe350afd263fdd66dfa3cf3048f1d6982c548f1a1b412d 2446 valgrind_3.18.1-1.1.dsc a94dda87a22ba869836f214204cbe55b50d3906b7a10c31b605f3b357db851b4 27132 valgrind_3.18.1-1.1.debian.tar.xz ef9cb66c3372c3e816ad10dcce194b110947db9fdd7f05b65d3b83d6615fe320 9302 valgrind_3.18.1-1.1_source.buildinfo Files: 205ea8be27cf683952cf8f17528cf5b8 2446 devel optional valgrind_3.18.1-1.1.dsc 530ba2c98295ba16e03db9585723051b 27132 devel optional valgrind_3.18.1-1.1.debian.tar.xz 5219011eb9f3197c432c32f20651b101 9302 devel optional valgrind_3.18.1-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmK+5HkRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0VDIBAAlGWtcLH8XxDAykLc0MwezWYcyIldmMU9
Bug#1014091: marked as done (armhf: gcc has wrong configuration)
Your message dated Wed, 06 Jul 2022 12:49:29 + with message-id and subject line Bug#928224: fixed in valgrind 1:3.18.1-1.1 has caused the Debian Bug report #928224, regarding armhf: gcc has wrong configuration 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.) -- 928224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-11 Version: 11.3.0-3 This is a followup to bug #928224. It turns out that gcc-11 is now generating neon instructions, which contradicts our definition of armhf. Reference: $ ssh abel.debian.org [...] malat@abel ~ % gcc-11 --verbose Using built-in specs. COLLECT_GCC=gcc-11 COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/11/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Debian 11.3.0-3' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=arm-linux-gnueabihf- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-sjlj-exceptions --with-arch=armv7-a+fp --with-float=hard --with-mode=thumb --disable-werror --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.3.0 (Debian 11.3.0-3) I suspect the issue is the following: [...] --with-arch=armv7-a+fp [...] I believe gcc-11 and above needs instead something like: [...] --with-arch=armv7-a+vfpv3-fp16+nosimd [...] --- End Message --- --- Begin Message --- Source: valgrind Source-Version: 1:3.18.1-1.1 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of valgrind, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated valgrind 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, 01 Jul 2022 13:58:19 +0200 Source: valgrind Architecture: source Version: 1:3.18.1-1.1 Distribution: unstable Urgency: medium Maintainer: Alessandro Ghedini Changed-By: Mathieu Malaterre Closes: 928224 Changes: valgrind (1:3.18.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix remove neon requirement from armhf binaries. Closes: #928224 Checksums-Sha1: 17b6cbaef40901ab75ab29bf8788d0ffa2ce52af 2446 valgrind_3.18.1-1.1.dsc 97dd37dfb5dae75c1a547f7e6af309fe4cbacd55 27132 valgrind_3.18.1-1.1.debian.tar.xz 1eb869485b29559281b9993cb8ab50a9c779344d 9302 valgrind_3.18.1-1.1_source.buildinfo Checksums-Sha256: 9608e9978c79d3e3c4fe350afd263fdd66dfa3cf3048f1d6982c548f1a1b412d 2446 valgrind_3.18.1-1.1.dsc a94dda87a22ba869836f214204cbe55b50d3906b7a10c31b605f3b357db851b4 27132 valgrind_3.18.1-1.1.debian.tar.xz ef9cb66c3372c3e816ad10dcce194b110947db9fdd7f05b65d3b83d6615fe320 9302 valgrind_3.18.1-1.1_source.buildinfo Files: 205ea8be27cf683952cf8f17528cf5b8 2446 devel optional valgrind_3.18.1-1.1.dsc 530ba2c98295ba16e03db9585723051b 27132 devel optional valgrind_3.18.1-1.1.debian.tar.xz 5219011eb9f3197c432c32f20651b101 9302 devel optional valgrind_3.18.1-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmK+5HkRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0VDIBAAlGWtcLH8XxDAykLc0MwezWYcyIldmMU9 nKSQZxbc3SzLE6XsLWLf00J28YhVumS2JmBpOOHXyC71LQeAaxmYX8+yGeC4qc+j PrzMe0xpnrLxyLtIDZRsky8OZOzXoRbVsgO26xJeHfXFySm0dWN9Om6XykF5mMMo cokSptsyOc38K5XBaRhCYL6vQWff47inVI3No2CoKRRPSa5CwnGhXiImnIE5wzsU
Bug#1004587: marked as done (pyglet: FTBFS with ffmpeg 5.0)
Your message dated Wed, 06 Jul 2022 12:49:19 + with message-id and subject line Bug#1004587: fixed in pyglet 1.5.26+ds-2 has caused the Debian Bug report #1004587, regarding pyglet: FTBFS with ffmpeg 5.0 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.) -- 1004587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyglet Version: 1.5.14-2 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 pyglet FTBFS with ffmpeg 5.0 (available in experimental): |dh_auto_test -O--buildsystem=pybuild | I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pyglet/build; python3.10 -m pytest >/dev/null 2>&1; cd /<>/.pybuild/cpython3_3.10_pyglet/build; xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" python3.10 -m pytest -v -k "not interactive and not PulseAudio and not test_pulse and not test_player_play and not test_player_play_multiple and not test_player_silent_audio_driver and not test_freetype_face and not test_fontconfig and not test_linux_fontconfig and not test_driver and not test_openal and not ClockTimingTestCase" --ignore=tests/interactive | = test session starts == | platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- /usr/bin/python3.10 | cachedir: .pytest_cache | rootdir: /<> | collecting ... collected 400 items / 5 errors / 87 deselected / 308 selected | ERRORS | _ ERROR collecting .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_directsound.py _ | tests/integration/media/test_directsound.py:11: in | from pyglet.media.codecs import AudioFormat | pyglet/media/__init__.py:143: in | add_default_media_codecs() | pyglet/media/codecs/__init__.py:102: in add_default_media_codecs | if have_ffmpeg(): | pyglet/media/codecs/__init__.py:118: in have_ffmpeg | from . import ffmpeg_lib | pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in | from .libavcodec import * | pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in | from . import libavutil | pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in | avutil.av_frame_get_best_effort_timestamp.restype = c_int64 | /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__ | func = self.__getitem__(name) | /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__ | func = self._FuncPtr((name_or_ordinal, self)) | E AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined symbol: av_frame_get_best_effort_timestamp | _ ERROR collecting .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_player.py _ | tests/integration/media/test_player.py:11: in | from pyglet.media import Player | pyglet/media/__init__.py:143: in | add_default_media_codecs() | pyglet/media/codecs/__init__.py:102: in add_default_media_codecs | if have_ffmpeg(): | pyglet/media/codecs/__init__.py:118: in have_ffmpeg | from . import ffmpeg_lib | pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in | from .libavcodec import * | pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in | from . import libavutil | pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in | avutil.av_frame_get_best_effort_timestamp.restype = c_int64 | /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__ | func = self.__getitem__(name) | /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__ | func = self._FuncPtr((name_or_ordinal, self)) | E AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined symbol: av_frame_get_best_effort_timestamp | _ ERROR collecting .pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_pulse.py _ | tests/integration/media/test_pulse.py:12: in | from pyglet.media.drivers.pulse import interface | pyglet/media/drivers/pulse/__init__.py:36: in | from .adaptation import PulseAudioDriver | pyglet/media/drivers/pulse/adaptation.py:39: in | from pyglet.media.events import MediaEvent | pyglet/media/__init__.py:143: in | add_default_media_codecs() | pyglet/media/codecs/__init__.py:102: in add_default_media_codecs | if have_ffmpeg(): | pyglet/media/codecs/__init__.py:118: in have_ffmpeg | from . import ffmpeg_lib | pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in | from .libavcodec import * | pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in | from . import libavutil |
Processed: Bug#1004587 marked as pending in pyglet
Processing control commands: > tag -1 pending Bug #1004587 [src:pyglet] pyglet: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1004587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004587: marked as pending in pyglet
Control: tag -1 pending Hello, Bug #1004587 in pyglet 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/python-team/packages/pyglet/-/commit/c99e0ffcaf6953b0b60f5c71fe9c158a66df7137 Manually update library dependencies Closes: #1004587 (this message was generated automatically) -- Greetings https://bugs.debian.org/1004587
Bug#1014452: pyresample: Test failures with rasterio 1.3.0
Source: pyresample Version: 1.23.0-1 Severity: serious Tags: ftbfs upstream Dear Maintainer, Your package FTBFS with rasterio 1.3.0 due to test failures which also affect the autopkgtests: TestMisc.test_get_area_def_from_raster self = def test_get_area_def_from_raster(self): from affine import Affine > from rasterio.crs import CRS as RCRS /usr/lib/python3/dist-packages/pyresample/test/test_utils.py:441: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/rasterio/__init__.py:14: in from rasterio.crs import CRS rasterio/crs.pyx:1: in init rasterio.crs ??? rasterio/_base.pyx:22: in init rasterio._base ??? /usr/lib/python3/dist-packages/rasterio/dtypes.py:10: in from rasterio.env import GDALVersion /usr/lib/python3/dist-packages/rasterio/env.py:16: in from rasterio._env import ( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > ??? E ImportError: /usr/lib/python3/dist-packages/rasterio/_filepath.cpython-39-x86_64-linux-gnu.so: undefined symbol: VSIAllocFilesystemPluginCallbacksStruct rasterio/_env.pyx:1: ImportError ___ TestMisc.test_get_area_def_from_raster_extracts_proj_id self = def test_get_area_def_from_raster_extracts_proj_id(self): > from rasterio.crs import CRS as RCRS /usr/lib/python3/dist-packages/pyresample/test/test_utils.py:465: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ """Rasterio""" from collections import namedtuple from contextlib import ExitStack import logging from logging import NullHandler import os import warnings import rasterio._loading > with rasterio._loading.add_gdal_dll_directories(): E AttributeError: partially initialized module 'rasterio' has no attribute '_loading' (most likely due to a circular import) /usr/lib/python3/dist-packages/rasterio/__init__.py:11: AttributeError Other tests raise the same AttributeError, see: https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyresample/23427351/log.gz Kind Regards, Bas
Bug#1014335: lnav: FTBFS: 1 test fails due to quoting differences
Hey Andreas,
On Mon, Jul 04, 2022 at 03:13:16PM +0200, Andreas Beckmann wrote:
> Source: lnav
> Version: 0.10.1-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Control: found -1 0.9.0-2
>
> Hi,
>
> lnav in sid and experimental recently started to FTBFS, since some
> (transitive) build-depends seems to have changed the quoting style in
> the stuff it generates. Is the new one even correct?
> (Looks to me like the change from an array to a string.)
>
> FAIL: test_sql_json_func.sh
> ===
>
> test: ./drive_sql SELECT id, json_group_object(key, value) as stack FROM (
> SELECT 1 as id, 1 as key, 10 as value UNION ALL SELECT 1 as id, 2 as key,
> json_array(1, 2, 3) as value UNION ALL SELECT 1 as id, 3 as key, 30.5 as
> value)
> json_group_object with number keys does not work
> --- - 2022-07-04 06:29:15.368031500 +
> +++ test_sql_json_func.sh_32.tmp2022-07-04 06:29:15.346400398 +
> @@ -1,3 +1,3 @@
> Row 0:
>Column id: 1
> - Column stack: {"1":10,"2":[1,2,3],"3":30.5}
> + Column stack: {"1":10,"2":"[1,2,3]","3":30.5}
> FAIL test_sql_json_func.sh (exit status: 1)
>
>
> Testsuite summary for lnav 0.10.1
>
> # TOTAL: 36
> # PASS: 35
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> See test/test-suite.log
Thanks for the report! I was in fact holding back the experimental
upload to move to unstable, because lnav FTBFS due to test failures
htere (but for different ones). But now it fails as well on unstable.
Will try to find time to address those and move to the 0.10.x version
as well.
Regards,
Salvatore
Bug#1012685: marked as done (tilix: Broken binary dependency due to ldc 1.29)
Your message dated Wed, 6 Jul 2022 12:09:41 +0200 with message-id and subject line reported bug is in error. tilix is installable. has caused the Debian Bug report #1012685, regarding tilix: Broken binary dependency due to ldc 1.29 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.) -- 1012685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tilix Severity: serious Version: 1.9.5-1 X-Debbugs-CC: jbi...@debian.org m...@debian.org Dear Debian tilix package maintainer, According to https://tracker.debian.org/pkg/tilix , package tilix was removed from Testing and has impossible dependency on disappeared shared library provided by src:ldc. Please consider solving this issue. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- The bug report is apparently erroneously reported against tilix version 1.9.5-1 - which actually fixed the issue, as far as I can tell. Version 1.9.5-1 is installable (no "impossible dependency") in debian/sid--- End Message ---
Bug#1012685: reported bug is in error. tilix is installable.
The bug report is apparently erroneously reported against tilix version 1.9.5-1 - which actually fixed the issue, as far as I can tell. Version 1.9.5-1 is installable (no "impossible dependency") in debian/sid
Processed (with 1 error): ROM: RM: yubikey-personalization-gui -- deprecated and replaced upstream
Processing commands for cont...@bugs.debian.org: > reassign 1014276 ftp.debian.org Bug #1014276 [yubikey-personalization-gui] yubikey-personalization-gui: rfm: don't ship with bookworm Bug reassigned from package 'yubikey-personalization-gui' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #1014276 to the same values previously set Ignoring request to alter fixed versions of bug #1014276 to the same values previously set > retitle ROM: RM: yubikey-personalization-gui -- deprecated and replaced Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: ITS: openscap
Processing control commands: > tags 1000279 + patch pending Bug #1000279 [src:openscap] FTBFS: CMake Error: Unknown argument --enable-perl Ignoring request to alter tags of bug #1000279 to the same tags previously set > tags 1001075 + patch pending Bug #1001075 [openscap-common] openscap-common: missing Breaks+Replaces: libopenscap8 (<< 1.3.5) Ignoring request to alter tags of bug #1001075 to the same tags previously set > tags 1012868 + patch pending Bug #1012868 [src:openscap] ITS: openscap Ignoring request to alter tags of bug #1012868 to the same tags previously set -- 1000279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000279 1001075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001075 1012868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013487: marked as done (django-filter: FTBFS: AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'localize')
Your message dated Wed, 06 Jul 2022 07:18:57 +
with message-id
and subject line Bug#1013487: fixed in django-filter 22.1-1
has caused the Debian Bug report #1013487,
regarding django-filter: FTBFS: AttributeError: 'zoneinfo.ZoneInfo' object has
no attribute 'localize'
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.)
--
1013487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-filter
Version: 2.4.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
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_test -- --system=custom --test-args="{interpreter} ./runtests.py"
> I: pybuild base:239: python3.9 ./runtests.py
> Creating test database for alias 'default'...
> Found 512 test(s).
> System check identified some issues:
>
> WARNINGS:
> drf_test_app.BaseFilterableItem: (models.W042) Auto-created primary key used
> when not defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> RestFrameworkTestConfig.default_auto_field attribute to point to a subclass
> of AutoField, e.g. 'django.db.models.BigAutoField'.
> drf_test_app.BasicModel: (models.W042) Auto-created primary key used when not
> defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> RestFrameworkTestConfig.default_auto_field attribute to point to a subclass
> of AutoField, e.g. 'django.db.models.BigAutoField'.
> drf_test_app.DjangoFilterOrderingModel: (models.W042) Auto-created primary
> key used when not defining a primary key type, by default
> 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> RestFrameworkTestConfig.default_auto_field attribute to point to a subclass
> of AutoField, e.g. 'django.db.models.BigAutoField'.
> tests.Account: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.AdminUser: (models.W042) Auto-created primary key used when not
> defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.Article: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.Book: (models.W042) Auto-created primary key used when not defining a
> primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.Business: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.Comment: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.Company: (models.W042) Auto-created primary key used when not defining
> a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
> AppConfig.default_auto_field attribute to point to a subclass of AutoField,
> e.g. 'django.db.models.BigAutoField'.
> tests.DirectedNode: (models.W042) Auto-created primary key used when not
> defining a primary key type, by default 'django.db.models.AutoField'.
> HINT: Configure the DEFAULT_AUTO_FIELD setting or the
>
Processed: re: ITS: openscap
Processing control commands: > tags 1000279 + patch pending Bug #1000279 [src:openscap] FTBFS: CMake Error: Unknown argument --enable-perl Added tag(s) pending and patch. > tags 1001075 + patch pending Bug #1001075 [openscap-common] openscap-common: missing Breaks+Replaces: libopenscap8 (<< 1.3.5) Added tag(s) patch and pending. > tags 1012868 + patch pending Bug #1012868 [src:openscap] ITS: openscap Added tag(s) pending and patch. -- 1000279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000279 1001075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001075 1012868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964654: kcov: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libbfd.a(plugin.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5'
Dear Alessandro, Any chance you could merge the suggested MR ? Thanks
