Bug#1051885: marked as done (kdevelop: FTBFS with llvm-toolchain-16 as default)
Your message dated Thu, 14 Sep 2023 06:21:05 + with message-id and subject line Bug#1051885: fixed in kdevelop 4:22.12.2-3 has caused the Debian Bug report #1051885, regarding kdevelop: FTBFS with llvm-toolchain-16 as default 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.) -- 1051885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdevelop Version: 4:22.12.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kdevelop&arch=amd64&ver=4%3A22.12.2-2%2Bb1&stamp=1694630976&raw=0 Typical components: all All LLVM libraries (default). engineEither a native JIT or a bitcode interpreter. CMake Error at cmake/modules/FindClang.cmake:113 (message): Could not find Clang builtin directory Call Stack (most recent call first): plugins/CMakeLists.txt:39 (find_package) -- Configuring incomplete, errors occurred! cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: kdevelop Source-Version: 4:22.12.2-3 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kdevelop, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kdevelop 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, 14 Sep 2023 07:35:46 +0200 Source: kdevelop Architecture: source Version: 4:22.12.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 1051885 Changes: kdevelop (4:22.12.2-3) unstable; urgency=medium . * Backport upstream commit 1a92bed73ae31e6f90c3bffe455f8e3c46ac4905, commit 9913f734d8aab75ea2e97c699cd926e9fd7a40b6, and commit 1c7bdc2e0f8dcf2aeb682ab3f5e317e3a97435ea, and ede1cf4ad6f945349060db9446c489e3fd34dec4 to find LLVM/Clang >= 16, and build with it; patches upstream_Drop-custom-Find-modules-and-use-upstream-ClangConfi.patch, upstream_Don-t-look-for-Clang-s-builtin-dir-in-unclean-versio.patch, upstream_Look-for-Clang-16-builtin-dir-in-major-version-subdi.patch, upstream_Don-t-cast-out-of-enum-range-1-to-CommonIntegralType.patch (Closes: #1051885) - refresh optional-clang.diff to apply cleanly on top of them * Disable the usage of LLVM/Clang on loong64 & sparc64, as it is not available on these architectures. Checksums-Sha1: d4caf6c74f6865828463588329391ea1946a935b 4093 kdevelop_22.12.2-3.dsc 8c2b8c5858155a4857e1929ab0d91a85e7af8691 42056 kdevelop_22.12.2-3.debian.tar.xz 1b3ebcde863adcaf625eb9fdc97b7406814a84ac 21542 kdevelop_22.12.2-3_source.buildinfo Checksums-Sha256: 8c1c614d92afd8778cef2201c594ae8a9947782711da37e4f83628391d616962 4093 kdevelop_22.12.2-3.dsc 087ee8025e6e78510346eb35a4e41f88384b02206c7affa3d9f478181c7bfa53 42056 kdevelop_22.12.2-3.debian.tar.xz a43dee48946fa72b3be05a64674535e437d7ec360f771540fda9665749426fd7 21542 kdevelop_22.12.2-3_source.buildinfo Files: ba5c7dc9e40dd7bba089155976d83f8b 4093 devel optional kdevelop_22.12.2-3.dsc 6ee2d013a5529a98f1966453eefb6d57 42056 devel optional kdevelop_22.12.2-3.debian.tar.xz 255109965c322adaa5b3209a749a6676 21542 devel optional kdevelop_22.12.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmUCm/YACgkQLRkciEOx P03qzhAAjnc1zbTNR5QWAQuwzYwco7z8S5C6eph6HprgdjTWFfjfFXAgtJmNs2eD 9LeywXej6eyudQEOlCXu8318vs455joPoygrBYNoQD3HcHeRjt9E1AnUamS2U8pS NMwizm8k3aNMyNnnJtf+Ke1RXZjvSItdNzVS//mj5Ee1td309f7+1quLSnzsO9bY 4Pk4uvRPHBBSlXSx7mCqTrIjhOWzSMCL39ZDgCjFefhAklo/voEelGF+j3oRYp6N sGfuq6OGL2/rHp7PMP9xrUjZ8sloXBDaE8yWbL5w9xnseKJaZ8yfcgRvSlJAG1LR 9WI9iZ+jGOT7E+X+ee3hoRrN7o2xE9hYRApQ6MiV6lx9bwlAq0sHrsDui9fUpcar 09+AC77rrQkrVhS6wstFSwWb9eLppLT9dPKZtWQAZWyeeHMPo8IiA1+iy9K8rx9F JTvF2u7rz8o+0et0D7CzTajqp455M1lhmgX/Jr9etEqxqhMILViDQsmgb/jIXgPA i3aNDFVR
Processed: retitle 1051864 to sparse: FTBFS with llvm-toolchain-16 as default
Processing commands for cont...@bugs.debian.org: > retitle 1051864 sparse: FTBFS with llvm-toolchain-16 as default Bug #1051864 [src:sparse] sparce: FTBFS with llvm-toolchain-16 as default Changed Bug title to 'sparse: FTBFS with llvm-toolchain-16 as default' from 'sparce: FTBFS with llvm-toolchain-16 as default'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1051863 to ldc: FTBFS with llvm-toolchain-16 as default
Processing commands for cont...@bugs.debian.org: > retitle 1051863 ldc: FTBFS with llvm-toolchain-16 as default Bug #1051863 [src:ldc] ldc: FRBFS with llvm-toolchain-16 as default Changed Bug title to 'ldc: FTBFS with llvm-toolchain-16 as default' from 'ldc: FRBFS with llvm-toolchain-16 as default'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: fluidsynth: Consider building with pipewire support
Processing control commands:
> reopen -1
Bug #1051819 {Done: Nicholas D Steeves } [fluidsynth]
fluidsynth: Consider building with pipewire support
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fluidsynth/2.3.3-2.
> notfixed -1 2.3.1-2
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Ignoring request to alter fixed versions of bug #1051819 to the same values
previously set
> severity -1 serious
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Severity set to 'serious' from 'wishlist'
> tags -1 patch
Bug #1051819 [fluidsynth] fluidsynth: Consider building with pipewire support
Added tag(s) patch.
--
1051819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051909: ring: FTBFS: error: using typedef-name ‘using dht::Logger = struct dht::log::Logger’ after ‘struct’
Source: ring Version: 20230206.0~ds2-1.3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, ring fails to build from source. From my build log on amd64: | /bin/bash ../libtool --tag=CXX --mode=compile g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD -DASIO_STANDALONE -I/<>/daemon/contrib/x86_64-linux-gnu/include -DPJ_AUTOCONF=1 -I/usr/include/jsoncpp -I/<>/daemon/src -I/<>/daemon/src/config -I/<>/daemon/src/media -I/<>/daemon/test -I/<>/daemon/src/jami -DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE -DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 -O3 -Wno-deprecated -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MT client/conversation_interface.lo -MD -MP -MF $depbase.Tpo -c -o client/conversation_interface.lo client/conversation_interface.cpp &&\ | mv -f $depbase.Tpo $depbase.Plo | make[4]: *** [Makefile:2669: account_factory.lo] Error 1 | make[4]: *** Waiting for unfinished jobs | libtool: compile: g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD -DASIO_STANDALONE "-I/<>/daemon/contrib/x86_64-linux-gnu/include" -DPJ_AUTOCONF=1 -I/usr/include/jsoncpp "-I/<>/daemon/src" "-I/<>/daemon/src/config" "-I/<>/daemon/src/media" "-I/<>/daemon/test" "-I/<>/daemon/src/jami" -DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE -DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 -O3 -Wno-deprecated -g -O2 "-ffile-prefix-map=/<>=." -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MT client/conversation_interface.lo -MD -MP -MF client/.deps/conversation_interface.Tpo -c client/conversation_interface.cpp -o client/conversation_interface.o | make[4]: *** [Makefile:2669: call.lo] Error 1 | make[4]: *** [Makefile:2669: manager.lo] Error 1 | make[4]: *** [Makefile:2669: conference.lo] Error 1 | In file included from ./jamidht/account_manager.h:28, | from ./jamidht/conversation_module.h:25, | from ./jamidht/jamiaccount.h:49, | from client/datatransfer.cpp:26: | ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logger = struct dht::log::Logger’ after ‘struct’ |43 | struct Logger; | |^~ | In file included from /usr/include/opendht/dhtrunner.h:28, | from ./connectivity/connectionmanager.h:24, | from ./jamidht/jamiaccount.h:46: | /usr/include/opendht/logger.h:117:7: note: ‘using dht::Logger = struct dht::log::Logger’ has a previous declaration here | 117 | using Logger = log::Logger; | | ^~ | In file included from ./jamidht/account_manager.h:28, | from ./jamidht/conversation_module.h:25, | from ./jamidht/jamiaccount.h:49, | from client/configurationmanager.cpp:39: | ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logger = struct dht::log::Logger’ after ‘struct’ |43 | struct Logger; | |^~ | In file included from /usr/include/opendht/dhtrunner.h:28, | from ./connectivity/connectionmanager.h:24, | from ./jamidht/jamiaccount.h:46: | /usr/include/opendht/logger.h:117:7: note: ‘using dht::Logger = struct dht::log::Logger’ has a previous declaration here | 117 | using Logger = log::Logger; | | ^~ | In file included from ./jamidht/account_manager.h:28, | from ./jamidht/conversation_module.h:25, | from ./jamidht/jamiaccount.h:49, | from client/callmanager.cpp:38: | ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logger = struct dht::log::Logger’ after ‘struct’ |43 | struct Logger; | |^~ | In file included from /usr/include/opendht/dhtrunner.h:28, | from ./connectivity/connectionmanager.h:24, | from ./jamidht/jamiaccount.h:46: | /usr/include/opendht/logger.h:117:7: note: ‘using dht::Logger = struct dht::log::Logger’ has a previous declaration here | 117 | using Logger = log::Logger; | | ^~ | In file included from ./jamidht/account_manager.h:28, | from ./jamidht/conversation_module.h:25, | from ./jamidht/jamiaccount.h:49, | from client/conversation_interface.cpp:33: | ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logge
Bug#1051249: marked as done (linux: s390x: FTBFS: kernel-wedge install-files: missing modules mptfc, mptsas and mptspi)
Your message dated Thu, 14 Sep 2023 05:00:10 + with message-id and subject line Bug#1051249: fixed in linux 6.5.3-1 has caused the Debian Bug report #1051249, regarding linux: s390x: FTBFS: kernel-wedge install-files: missing modules mptfc, mptsas and mptspi 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.) -- 1051249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 6.5~rc4-1~exp1 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: car...@debian.org linux/6.5~rc4-1~exp1 onwards in experimental FTBFS for s390x: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=s390x&ver=6.5%7Erc4-1%7Eexp1&stamp=1691173177&raw=0 Regards, Salvatore --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.5.3-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux 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, 13 Sep 2023 22:20:48 +0200 Source: linux Architecture: source Version: 6.5.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1025845 1041007 1051249 1051455 Changes: linux (6.5.3-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.2 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.3 . [ Christian Göttsche ] * Enable KFENCE support (not enabled by default) (Closes: #1025845) . [ Diederik de Haas ] * net/xdp: Enable XDP_SOCKETS_DIAG as module (Closes: #1051455) . [ Ben Hutchings ] * udeb: Make MPT modules optional in scsi-modules (fixes FTBFS on s390x) (Closes: #1051249) . [ Salvatore Bonaccorso ] * Refresh "radeon, amdgpu: Firmware is required for DRM and KMS on R600 onward" * Set ABI to 1 * [rt] Update to 6.5.2-rt8 . [ Emanuele Rocca ] * [arm64] Add reset-rzg2l-usbphy-ctrl to usb-modules udeb in order to enable USB support on Renesas RZ/G2L-SMARC boards. * [arm64,armhf] drivers/hwspinlock: Enable CONFIG_HWSPINLOCK * [arm64] Add support for Lenovo ThinkPad X13s: enable as modules SC_DISPCC_8280XP, SC_GCC_8280XP, SC_GPUCC_8280XP, QCOM_SPMI_ADC5, INTERCONNECT_QCOM_OSM_L3, INTERCONNECT_QCOM_SC8280XP, LEDS_QCOM_LPG, QCOM_IPCC, QCOM_FASTRPC, NVMEM_SPMI_SDAM, PHY_QCOM_EDP, PHY_QCOM_QMP_PCIE, PHY_QCOM_USB_SNPS_FEMTO_V2, PINCTRL_SC8280XP, PINCTRL_SC8280XP_LPASS_LPI, PINCTRL_LPASS_LPI, POWER_RESET_QCOM_PON, BATTERY_QCOM_BATTMGR, QCOM_Q6V5_ADSP, QCOM_Q6V5_PAS, QCOM_Q6V5_WCSS, QCOM_SYSMON, QCOM_LLCC, QCOM_OCMEM, QCOM_PMIC_GLINK, QCOM_STATS, QCOM_APR, QCOM_ICC_BWMON, SPI_QCOM_GENI, TYPEC_MUX_GPIO_SBU, QRTR_SMD, SND_SOC_WCD938X_SDW, SND_SOC_LPASS_WSA_MACRO, SND_SOC_LPASS_VA_MACRO, SND_SOC_LPASS_RX_MACRO, SND_SOC_LPASS_TX_MACRO, SND_SOC_QDSP6 (Thanks Steve Capper!) * [arm64] Add Thinkpad X13s modules to udebs . [ Vincent Blut ] * drivers/char/hw_random: Change HW_RANDOM from module to built-in (Closes: #1041007) * drivers/char/tpm: Do not explicitly set HW_RANDOM_TPM * [arm64, cloud, x86] drivers/char/tpm: Do not explicitly enable TCG_TPM * [arm*,ppc64*,sparc64,s390x] drivers/char/hw_random: Prevent some HW Random Number Generator drivers from being built-in Checksums-Sha1: 077843e2f9c08cc1def55e134ff52e8067609573 288931 linux_6.5.3-1.dsc 90adc41d78bcec83f78851281ba290052570d36c 141462376 linux_6.5.3.orig.tar.xz a3bbbf54f9b9d60d69afa331ff96392fdab6a8a5 1493144 linux_6.5.3-1.debian.tar.xz a2e326f7933128849657e7472fe053c721c5f4af 6858 linux_6.5.3-1_source.buildinfo Checksums-Sha256: e41e0a33c5eb34d3c53d50ad358ef5485107c148281ef9bf58f4c2a8a2080c66 288931 linux_6.5.3-1.dsc 55bc546f0b3e5b1fd984f0e22155fa9e0e7eca20fcb5f327a86f9ecfa3789983 141462376 linux_6.5.3.orig.tar.xz f71a0ee85d794ce35b9
Processed: tagging 1051889, bug 1051889 is forwarded to https://sourceforge.net/p/freeimage/bugs/319/ ...
Processing commands for cont...@bugs.debian.org: > tags 1051889 + upstream Bug #1051889 [src:freeimage] freeimage: CVE-2020-22524 Added tag(s) upstream. > forwarded 1051889 https://sourceforge.net/p/freeimage/bugs/319/ Bug #1051889 [src:freeimage] freeimage: CVE-2020-22524 Set Bug forwarded-to-address to 'https://sourceforge.net/p/freeimage/bugs/319/'. > tags 1051890 + upstream Bug #1051890 [src:libsndfile] libsndfile: CVE-2022-33064 Added tag(s) upstream. > forwarded 1051890 https://github.com/libsndfile/libsndfile/issues/832 Bug #1051890 [src:libsndfile] libsndfile: CVE-2022-33064 Set Bug forwarded-to-address to 'https://github.com/libsndfile/libsndfile/issues/832'. > tags 1051891 + upstream Bug #1051891 [src:libsndfile] libsndfile: CVE-2022-33065 Added tag(s) upstream. > forwarded 1051891 https://github.com/libsndfile/libsndfile/issues/833 > https://github.com/libsndfile/libsndfile/issues/789 Bug #1051891 [src:libsndfile] libsndfile: CVE-2022-33065 Set Bug forwarded-to-address to 'https://github.com/libsndfile/libsndfile/issues/833 https://github.com/libsndfile/libsndfile/issues/789'. > tags 1051892 + upstream Bug #1051892 [src:firmware-nonfree] firmware-nonfree: CVE-2022-27635 CVE-2022-36351 CVE-2022-38076 CVE-2022-40964 CVE-2022-46329 Added tag(s) upstream. > found 1051892 20230515-3 Bug #1051892 [src:firmware-nonfree] firmware-nonfree: CVE-2022-27635 CVE-2022-36351 CVE-2022-38076 CVE-2022-40964 CVE-2022-46329 Marked as found in versions firmware-nonfree/20230515-3. > tags 1051893 + upstream Bug #1051893 [src:libsass] libsass: CVE-2022-43357 Added tag(s) upstream. > forwarded 1051893 https://github.com/sass/libsass/issues/3177 Bug #1051893 [src:libsass] libsass: CVE-2022-43357 Set Bug forwarded-to-address to 'https://github.com/sass/libsass/issues/3177'. > tags 1051894 + upstream Bug #1051894 [src:libsass] libsass: CVE-2022-26592 Added tag(s) upstream. > forwarded 1051894 https://github.com/sass/libsass/issues/3174 Bug #1051894 [src:libsass] libsass: CVE-2022-26592 Set Bug forwarded-to-address to 'https://github.com/sass/libsass/issues/3174'. > tags 1051895 + upstream Bug #1051895 [src:libsass] libsass: CVE-2022-43358 Added tag(s) upstream. > forwarded 1051895 https://github.com/sass/libsass/issues/3178 Bug #1051895 [src:libsass] libsass: CVE-2022-43358 Set Bug forwarded-to-address to 'https://github.com/sass/libsass/issues/3178'. > tags 1051896 + upstream Bug #1051896 [src:rkhunter] rkhunter: CVE-2023-4413 Added tag(s) upstream. > tags 1051897 + upstream Bug #1051897 [src:ansible] ansible: CVE-2023-4380 Added tag(s) upstream. > tags 1051898 + upstream Bug #1051898 [src:radare2] radare2: CVE-2023-4322 Added tag(s) upstream. > tags 1051899 + upstream Bug #1051899 [src:qemu] qemu: CVE-2023-42467 Added tag(s) upstream. > forwarded 1051899 https://gitlab.com/qemu-project/qemu/-/issues/1813 Bug #1051899 [src:qemu] qemu: CVE-2023-42467 Set Bug forwarded-to-address to 'https://gitlab.com/qemu-project/qemu/-/issues/1813'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051889 1051890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051890 1051891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051891 1051892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051892 1051893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051893 1051894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051894 1051895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051895 1051896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051896 1051897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051897 1051898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051898 1051899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tags 1051822 patch
Processing commands for cont...@bugs.debian.org: > tags 1051822 patch Bug #1051822 [chrony] installed chrony package post-installation script subprocess returned error exit status 1 Added tag(s) patch. > stop Stopping processing here. Please contact me if you need assistance. -- 1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
On Wed, 2023-09-13 15:15:10 +0200, Vincent Blut wrote:
> Control: tags -1 + moreinfo
>
> Hi Anibal,
>
> Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit :
>> Package: chrony
>> Version: 4.2-2
>> Severity: critical
>>
>> # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb
>> (Reading database ... 34682 files and directories currently installed.)
>> Preparing to unpack .../archives/chrony_4.4-1_i386.deb ...
>> Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service
>> not loaded.
>> Unpacking chrony (4.4-1) over (4.3-4) ...
>> Setting up chrony (4.4-1) ...
>> Unknown option: comment
>> adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
>> [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID]
>> [--disabled-password] [--disabled-login] [--add_extra_groups] USER
>>Add a normal user
>>
>> adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
>> [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password]
>> [--disabled-login] [--add_extra_groups] USER
>>Add a system user
>>
>> adduser --group [--gid ID] GROUP
>> addgroup [--gid ID] GROUP
>>Add a user group
>>
>> addgroup --system [--gid ID] GROUP
>>Add a system group
>>
>> adduser USER GROUP
>>Add an existing user to an existing group
>>
>> general options:
>> --quiet | -q don't give process information to stdout
>> --force-badname allow usernames which do not match the
>> NAME_REGEX configuration variable
>> --help | -h usage message
>> --version | -vversion number and copyright
>> --conf | -c FILE use FILE as configuration file
>>
>> dpkg: error processing package chrony (--install):
>> installed chrony package post-installation script subprocess returned error
>> exit status 1
>> Processing triggers for man-db (2.11.2-3) ...
>> Errors were encountered while processing:
>> chrony
>
> I don't seem to be able to reproduce this issue. Could you please give me more
> information on the system on which you were upgrading chrony? It seems you
> were
> upgrading from chrony 4.3-4, so I guess this system is running
> testing/unstable‽
>
> Cheers,
> Vincent
Dear Vincent,
I tried again to upgrade chrony on another machine and it failed.
Setting up chrony (4.4-1) ...
Unknown option: comment
adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
[--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID]
[--disabled-password] [--disabled-login] [--add_extra_groups] USER
Add a normal user
adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID]
[--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password]
[--disabled-login] [--add_extra_groups] USER
Add a system user
adduser --group [--gid ID] GROUP
addgroup [--gid ID] GROUP
Add a user group
addgroup --system [--gid ID] GROUP
Add a system group
adduser USER GROUP
Add an existing user to an existing group
general options:
--quiet | -q don't give process information to stdout
--force-badname allow usernames which do not match the
NAME_REGEX configuration variable
--help | -h usage message
--version | -vversion number and copyright
--conf | -c FILE use FILE as configuration file
dpkg: error processing package chrony (--configure):
installed chrony package post-installation script subprocess returned error
exit status 1
...
Errors were encountered while processing:
chrony
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ dpkg -l adduser chrony
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ri adduser3.118all add and remove users and groups
iF chrony 4.4-1i386 Versatile implementation of the
Network Time Protocol
I know updating adduser from 3.118 to 3.137 will fix this bug.
I tried dpkg -i chrony_4.4-1_i386.deb with the same messages above. I
did not upgrade adduser this time.
I suggest to replace line 28 in debian/control as follows:
--- control 2023-09-14 13:52:34.323543535 +1000
+++ control 2023-09-14 13:55:18.960189965 +1000
@@ -25,7 +25,7 @@ Rules-Requires-Root: no
Package: chrony
Architecture: linux-any
Pre-Depends: ${misc:Pre-Depends}
-Depends: adduser,
+Depends: adduser (>= 3.137),
iproute2 [linux-any],
tzdata-legacy,
ucf,
I will not touch the machine and will install any test package from you.
Please let me know what would you like me to do.
Thank you for your time and for helping me with this bug.
Kind regards,
Aníbal
Processed: tagging 1051885
Processing commands for cont...@bugs.debian.org: > tags 1051885 + pending Bug #1051885 [src:kdevelop] kdevelop: FTBFS with llvm-toolchain-16 as default Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051629: marked as done (chromium: Crash with seqfault when starting)
Your message dated Thu, 14 Sep 2023 03:33:59 + with message-id and subject line Bug#1051355: fixed in chromium 117.0.5938.62-1 has caused the Debian Bug report #1051355, regarding chromium: Crash with seqfault when starting 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.) -- 1051355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 116.0.5845.180-1 Severity: grave Justification: renders package unusable Dear Maintainer, Crash when starting: [411709:411709:0910/203433.221232:ERROR:chrome_browser_cloud_management_controller.cc(163)] Cloud management controller initialization aborted as CBCM is not enabled. [411709:411709:0910/203433.290281:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [411709:411737:0910/203433.474597:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 [0910/203433.684242:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0910/203433.684772:ERROR:elf_dynamic_array_reader.h(64)] tag not found Trace/breakpoint trap -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 116.0.5845.180-1 ii libasound2 1.2.9-2 ii libatk-bridge2.0-0 2.49.91-2 ii libatk1.0-0 2.49.91-2 ii libatomic1 13.2.0-3 ii libatspi2.0-02.49.91-2 ii libbrotli1 1.0.9-2+b6 ii libc62.37-8 ii libcairo21.17.8-3 ii libcups2 2.4.2-5 ii libdbus-1-3 1.14.10-1 ii libdouble-conversion33.3.0-1 ii libdrm2 2.4.115-1 ii libevent-2.1-7 2.1.12-stable-8 ii libexpat12.5.0-2 ii libflac121.4.3+ds-2 ii libfontconfig1 2.14.2-5 ii libfreetype6 2.13.2+dfsg-1 ii libgbm1 23.1.7-1 ii libgcc-s113.2.0-3 ii libglib2.0-0 2.78.0-1 ii libgtk-3-0 3.24.38-4 ii libjpeg62-turbo 1:2.1.5-2 ii libjsoncpp25 1.9.5-6 ii liblcms2-2 2.14-2 ii libminizip1 1:1.2.13.dfsg-3 ii libnspr4 2:4.35-1.1 ii libnss3 2:3.92-1 ii libopenh264-72.3.1+dfsg-3 ii libopenjp2-7 2.5.0-2 ii libopus0 1.4-1 ii libpango-1.0-0 1.51.0+ds-2 ii libpng16-16 1.6.40-1 ii libpulse016.1+dfsg1-2+b1 ii libsnappy1v5 1.1.10-1 ii libstdc++6 13.2.0-3 ii libwebp7 1.2.4-0.2 ii libwebpdemux21.2.4-0.2 ii libwebpmux3
Bug#1051355: marked as done (chromium: Segmentation fault)
Your message dated Thu, 14 Sep 2023 03:33:59 + with message-id and subject line Bug#1051355: fixed in chromium 117.0.5938.62-1 has caused the Debian Bug report #1051355, regarding chromium: Segmentation fault 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.) -- 1051355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 116.0.5845.180-1 Severity: grave Justification: Renders package unusable Dear Maintainer, Your package is currently unusable, making it impossible to use it. Please consider fixing this so other users can use it normally. Thanks. Just reiterating that the browser doesn't even open in Gnome 44 with Wayland. The output in the terminal is as follows: [4562:4562:0906/161027.517475:ERROR:chrome_browser_cloud_management_controller.cc(163)] Cloud management controller initialization aborted as CBCM is not enabled. [4562:4590:0906/161028.019651:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 [0906/161028.521029:ERROR:elf_dynamic_array_reader.h(64)] tag not found Falha de segmentação -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common116.0.5845.180-1 ii libasound2 1.2.9-2 ii libatk-bridge2.0-0 2.49.91-2 ii libatk1.0-02.49.91-2 ii libatomic1 13.2.0-2 ii libatspi2.0-0 2.49.91-2 ii libbrotli1 1.0.9-2+b6 ii libc6 2.37-7 ii libcairo2 1.16.0-7 ii libcups2 2.4.2-5 ii libdbus-1-31.14.10-1 ii libdouble-conversion3 3.3.0-1 ii libdrm22.4.115-1 ii libevent-2.1-7 2.1.12-stable-8 ii libexpat1 2.5.0-2 ii libflac12 1.4.3+ds-2 ii libfontconfig1 2.14.2-4 ii libfreetype6 2.13.2+dfsg-1 ii libgbm123.1.6-1 ii libgcc-s1 13.2.0-2 ii libglib2.0-0 2.77.2-1 ii libgtk-3-0 3.24.38-4 ii libjpeg62-turbo1:2.1.5-2 ii libjsoncpp25 1.9.5-6 ii liblcms2-2 2.14-2 ii libminizip11:1.2.13.dfsg-3 ii libnspr4 2:4.35-1.1 ii libnss32:3.92-1 ii libopenh264-7 2.3.1+dfsg-3 ii libopenjp2-7 2.5.0-2 ii libopus0 1.4-1 ii libpango-1.0-0 1.51.0+ds-2 ii libpng16-161.6.40-1 ii libpulse0 16.1+dfsg1-2+b1 ii libsnappy1v5 1.1.10-1 ii libstdc++6 13.2.0-2 ii libwebp7 1.2.4-0.2 ii libwebpdemux2 1.2.4-0.2 ii libwebpmux31.2.4-0.2 ii libwoff1 1.0.2-2 ii libx11-6 2:1.8.6-1 ii libxcb11.15-1 ii libxcomposite1
Bug#1051901: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host
I ran more tests, and could reproduce what I think is the same bug without relying on WINE. Trying to play an audio file using mpv:i386 [1] on an amd64 host causes a segfault. While mpv:amd64 has no issue. [1]: https://packages.debian.org/sid/mpv I think the problem might actually be related to trying to play sounds using any i386 binary (so the i386 libasound.so.2) on an amd64 host. OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 1051901 libasound2: 1.2.10 breaks ability to play audio using i386 > binaries on amd64 host Bug #1051901 [libasound2] 1.2.10 breaks ability to play audio using i386 binaries on amd64 host Changed Bug title to 'libasound2: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host' from '1.2.10 breaks ability to play audio using i386 binaries on amd64 host'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 1051901 1.2.10 breaks ability to play audio using i386 binaries on > amd64 host Bug #1051901 [libasound2] libasound2: 1.2.10 breaks ability to run i386 WINE on an amd64 host Changed Bug title to '1.2.10 breaks ability to play audio using i386 binaries on amd64 host' from 'libasound2: 1.2.10 breaks ability to run i386 WINE on an amd64 host'. > severity 1051901 serious Bug #1051901 [libasound2] 1.2.10 breaks ability to play audio using i386 binaries on amd64 host Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051523: Doxygen changes breaks krb5 documentation build
On 9/12/23 03:01, Paolo Greppi wrote: This may well be a doxygen bug, can anybody tell if there is any pattern? I believe this is a deliberate behavior change in Doxygen 1.9.7, made to address a problem affecting a different doxygen-to-RST converter: https://github.com/doxygen/doxygen/pull/9797 https://github.com/doxygen/doxygen/issues/8790 (doxyrest doesn't appear to be packaged by Debian, or I'd investigate whether we could use it instead of the current homegrown bridge. But that would be a longer-term change anyway.) Although it might be difficult to modify the current scripts to handle this change, the deduplication only arises because of @group declarations in krb5.hin, which don't have any effect on the generated RST files. I have filed a PR to remove these and the associated @ref declarations: https://github.com/krb5/krb5/pull/1316
Processed: retitle 1051900 to ohcount: aborts with segfault or bus error 90% of the time on arm64
Processing commands for cont...@bugs.debian.org: > retitle 1051900 ohcount: aborts with segfault or bus error 90% of the time on > arm64 Bug #1051900 [ohcount] ohcount: aborts with segfaul or bus error 90% of the time on arm64 Changed Bug title to 'ohcount: aborts with segfault or bus error 90% of the time on arm64' from 'ohcount: aborts with segfaul or bus error 90% of the time on arm64'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051900: ohcount: aborts with segfaul or bus error 90% of the time on arm64
Package: ohcount Version: 4.0.0-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debian-...@lists.debian.org Dear Maintainer, ohcount segfaults (and sometimes aborts with a Bus error) on arm64, almost 90% of the time. I tried this on an up to date arm64 Debian testing against the hexchat source code, but it's also reproducible on the ohcount source code itself. The same test, when performced on an up to date amd64 Debian testing, finishes successfully 100% of the time. For example this is a sample session with 10 runs against the source of ohcount itself: $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Bus error $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Segmentation fault $ ohcount Examining 1192 file(s) Bus error -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.4.0-3-arm64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ohcount depends on: ii file 1:5.45-2 ii libc6 2.37-7 ii libmagic1 1:5.45-2 ii libpcre3 2:8.39-15 ii ruby 1:3.1 ii ruby-diff-lcs 1.5.0-1 ohcount recommends no packages. Versions of packages ohcount suggests: pn ohcount-doc -- no debconf information signature.asc Description: PGP signature
Bug#1051752: marked as done (uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures)
Your message dated Wed, 13 Sep 2023 21:44:45 + with message-id and subject line Bug#1051752: fixed in uwsgi 2.0.22-2 has caused the Debian Bug report #1051752, regarding uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures 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.) -- 1051752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uwsgi Version: 2.0.22-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org glusterfs dropped support for 32 bit architectures (see #1050629 for details) and the binaries are being removed from trixie. uwsgi-plugin-glusterfs is the last remaining binary package depending on them on 32 bit architectures which prevents their removal. Please remove uwsgi-plugin-glusterfs on all 32 bit architectures. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: uwsgi Source-Version: 2.0.22-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of uwsgi, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated uwsgi 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, 13 Sep 2023 22:03:09 +0200 Source: uwsgi Architecture: source Version: 2.0.22-2 Distribution: unstable Urgency: medium Maintainer: uWSGI packaging team Changed-By: Jonas Smedegaard Closes: 1050753 1051752 Changes: uwsgi (2.0.22-2) unstable; urgency=medium . * exclude arches armel armhf i386 from glusterfs build-dependencies, and add arch riscv64; closes: bug#1051752, thanks to Sebastian Ramacher * exclude arch mipsel from gccgo build-dependencies * exclude arch mipsel from greenlet build-dependencies, and add arch riscv64 * exclude arch mipsel from mono build-dependencies * exclude arch mipsel from openjdk17 build-dependencies, and add arch riscv64 * exclude arch mipsel from rados build-dependencies * drop binary package uwsgi-plugin-lua5.2; stop build-depend on liblua5.2-dev; closes: bug#1050753, thanks to Bastian Germann Checksums-Sha1: c5b79ec5f70d81b89ff3f543fee3ee4140e8925f 6990 uwsgi_2.0.22-2.dsc 371f85134dff7bfe68111c8141a3bc0d29f28244 69472 uwsgi_2.0.22-2.debian.tar.xz ccf1fe4eadc26f344b00ff026562f271ba10e943 37701 uwsgi_2.0.22-2_amd64.buildinfo Checksums-Sha256: e5a72b674ed022c8276c58afbc11afb05e44e366b7d4dbfb3209232be2106a3b 6990 uwsgi_2.0.22-2.dsc 4a50cbeb366b323be771d004d4e05026b896d0c1ba85fd6428be4beea2889020 69472 uwsgi_2.0.22-2.debian.tar.xz 87eb1364c0464817fe197868a480f0325a8e01d269e1f4b1bb1c19c12f7d3539 37701 uwsgi_2.0.22-2_amd64.buildinfo Files: bbc48cd0025ce1fa654e5a0596b5b735 6990 httpd optional uwsgi_2.0.22-2.dsc 4825bf1c224f0920d7981c2b3e9bb560 69472 httpd optional uwsgi_2.0.22-2.debian.tar.xz 4b4eb88ba1f37e874dcce42f4a735d2c 37701 httpd optional uwsgi_2.0.22-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUCGnkACgkQLHwxRsGg ASG50xAAk+q60QhlyOXoEzOv7Irpg2fXN3YLCvb0ybJvto3LJPpAp08T3ytVcf3r xkcFGEPek0uGr7g6ryHb6Mlkw3AH9f/gUs2AxHiwun3GnRWsMIP9gLYqfjukFy5b kJ5NdFGZ7/OcsWG5mif70REZliG2KCReUxxsnhXujJEnlhVKZ4NwYXXZgFXhVMkO 2bRi0c4wKZIQiuI+4GQmbsLt5zWaKao5UwS7+JuTssDFLApWbIfSgEpK/+3KkmIM YFq6ZuSaNHEMIYlQSFQMkHYlPkjfurGTssLr+SvCrHVqZX5YgqbefKxAx952gvMu rpU4PpsIdr072cq3j4vjPAK2jCEIK8DLqAJxElwCF3Rj3dlJ/tXq2DnJYJDiHsLD 7HqkFI/vGac+r9I1l4UNiPabrHNKVAnC995zSMHEwVs3x4UffdKiJunjUIDoi2eQ 7NcAAQREAJDQ25B4tX2kmyXmpxDJ7kicbEMdyYXOnRwIEpPkpu4gRT9wnZEqXnRZ AR9K2qFHTzu2Sc3IGqHKxOBDJ1xRkBYakLFXgfzStfpThDmoctOdtuaQBcC90SSZ l8ILfXi2DWJ1xEIURhindmMWOMzhJvOq7DyrgUUiVJJD6O3/xOi8eQGUQltQ+00H VnKcG0Qn+Wdz7mqPyOuAFQ6Dcfqo1uAupoicjZX4xc/LxFo1TbQ= =UPVB -END PGP SIGNATURE End Message ---
Bug#1050903: marked as done (telegram-desktop: segmentation fault)
Your message dated Wed, 13 Sep 2023 21:42:31 + with message-id and subject line Bug#1050903: fixed in telegram-desktop 4.9.7+ds-1 has caused the Debian Bug report #1050903, regarding telegram-desktop: segmentation fault 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.) -- 1050903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: telegram-desktop Version: 4.9.3+ds-1 Severity: grave Justification: renders package unusable Dear Maintainer, Package again presents segmentation fault in some features like viewing the user profile. The same user has views of stories that do not get to be listed with the application presenting a segmentation fault afterwards. telegram-desktop -debug (telegram-desktop:8895): Telegram-WARNING **: 07:23:35.375: Application has been built with foreign rlottie, animated emojis won't be colored t o the selected pack. (telegram-desktop:8895): Telegram-WARNING **: 07:23:35.375: Application was built without embedded fonts, this may lead to font issues. On Debi an-based systems, make sure you have the fonts-open-sans package installed QPainter::begin: Paint device returned engine == 0, type: 2 QWidget::render: Cannot render with an inactive painter qt.svg: Error while inflating gzip file: SVG format check failed qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Falha de segmentação (imagem do núcleo gravada) -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libabsl2022062320220623.1-3 ii libavcodec60 7:6.0-6 ii libavfilter9 7:6.0-6 ii libavformat60 7:6.0-6 ii libavutil587:6.0-6 ii libc6 2.37-7 ii libgcc-s1 13.2.0-2 ii libglib2.0-0 2.77.2-1 ii libglibmm-2.68-1 2.77.0-1 ii libhunspell-1.7-0 1.7.2+really1.7.2-10 ii libjpeg62-turbo1:2.1.5-2 ii libkf5coreaddons5 5.107.0-1 ii liblz4-1 1.9.4-1 ii libminizip11:1.2.13.dfsg-3 ii libopenal1 1:1.23.1-3 ii libopus0 1.4-1 ii libqrcodegencpp1 1.8.0-1.1 ii libqt5core5a [qtbase-abi-5-15-10] 5.15.10+dfsg-3 ii libqt5gui5 5.15.10+dfsg-3 ii libqt5network5 5.15.10+dfsg-3 ii libqt5svg5 5.15.10-2 ii libqt5widgets5 5.15.10+dfsg-3 ii librlottie0-1 0.1+dfsg-4 ii libsigc++-3.0-03.4.0-7 ii libsrtp2-1 2.5.0-3 ii libssl33.0.10-1 ii libstdc++6 13.2.0-2 ii libswresample4 7:6.0-6 ii libswscale77:6.0-6 ii libvpx71.12.0-1 ii libx11-6 2:1.8.6-1 ii libxcb-keysyms10.4.0-1+b2 ii libxcb-record0 1.15-1 ii libxcb-screensaver01.15-1 ii libxcb11.15-1 ii libxcomposite1 1:0.4.5-1 ii libxdamage11:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxrandr2 2:1.5.2-2+b1 ii libxtst6 2:1.2.3-1.1 ii libxxhash0 0.8.1-1 ii libyuv00.0~git20230616.a366ad7-1 ii qt5-image-formats-plugins 5.15.10-2 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-2 ii libwebkit2gtk-4.0-37 2.40.5-1 telegram-desktop suggests no packages. Versions of packages telegram-desktop is related to: ii xdg-desktop-portal 1.16.0-3 ii xdg-desktop-portal-gtk [xdg-desktop-porta
Bug#1051828: marked as done (pytorch: needs-root for autopkgtests?)
Your message dated Wed, 13 Sep 2023 21:35:27 + with message-id and subject line Bug#1051828: fixed in pytorch 2.0.1+dfsg-4 has caused the Debian Bug report #1051828, regarding pytorch: needs-root for autopkgtests? 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.) -- 1051828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytorch Version: 2.0.1+dfsg-2 Severity: serious Hello, I just found this failure on Ubuntu builders. 5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any: cd debian/tests ; find /usr -xtype l -print 5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any: [--- 5393s find: ‘/usr/share/polkit-1/rules.d’: Permission denied 5396s /usr/share/doc/openssl/changelog.gz 5396s /usr/share/doc/perl/Changes.gz 5396s /usr/share/doc/python3-keyring/NEWS.rst.gz 5396s /usr/share/doc/libucx0/README 5396s /usr/share/doc/libhdf5-103-1/RELEASE.txt.gz 5396s /usr/share/doc/libhdf5-hl-100/RELEASE.txt.gz 5396s /usr/share/doc/xfsprogs/changelog.gz 5396s /usr/share/doc/python3-wadllib/NEWS.rst.gz 5396s /usr/share/doc/libxml2/NEWS.gz 5396s /usr/share/locale/cs/LC_TIME/coreutils.mo 5396s /usr/share/locale/zh_TW/LC_TIME/coreutils.mo 5396s /usr/share/locale/eo/LC_TIME/coreutils.mo 5396s /usr/share/locale/tr/LC_TIME/coreutils.mo 5396s /usr/share/locale/fr/LC_TIME/coreutils.mo 5396s /usr/share/locale/eu/LC_TIME/coreutils.mo 5396s /usr/share/locale/da/LC_TIME/coreutils.mo 5396s /usr/share/locale/vi/LC_TIME/coreutils.mo 5396s /usr/share/locale/it/LC_TIME/coreutils.mo 5396s /usr/share/locale/fi/LC_TIME/coreutils.mo 5396s /usr/share/locale/lt/LC_TIME/coreutils.mo 5396s /usr/share/locale/nb/LC_TIME/coreutils.mo 5396s /usr/share/locale/el/LC_TIME/coreutils.mo 5396s /usr/share/locale/de/LC_TIME/coreutils.mo 5396s /usr/share/locale/hu/LC_TIME/coreutils.mo 5396s /usr/share/locale/ro/LC_TIME/coreutils.mo 5396s /usr/share/locale/es/LC_TIME/coreutils.mo 5396s /usr/share/locale/id/LC_TIME/coreutils.mo 5396s /usr/share/locale/et/LC_TIME/coreutils.mo 5396s /usr/share/locale/sl/LC_TIME/coreutils.mo 5396s /usr/share/locale/nl/LC_TIME/coreutils.mo 5396s /usr/share/locale/sr/LC_TIME/coreutils.mo 5396s /usr/share/locale/ga/LC_TIME/coreutils.mo 5396s /usr/share/locale/be/LC_TIME/coreutils.mo 5396s /usr/share/locale/kk/LC_TIME/coreutils.mo 5396s /usr/share/locale/pt_BR/LC_TIME/coreutils.mo 5396s /usr/share/locale/af/LC_TIME/coreutils.mo 5396s /usr/share/locale/uk/LC_TIME/coreutils.mo 5396s /usr/share/locale/ia/LC_TIME/coreutils.mo 5396s /usr/share/locale/gl/LC_TIME/coreutils.mo 5396s /usr/share/locale/pl/LC_TIME/coreutils.mo 5396s /usr/share/locale/ms/LC_TIME/coreutils.mo 5396s /usr/share/locale/ko/LC_TIME/coreutils.mo 5396s /usr/share/locale/lg/LC_TIME/coreutils.mo 5396s /usr/share/locale/bg/LC_TIME/coreutils.mo 5396s /usr/share/locale/sv/LC_TIME/coreutils.mo 5396s /usr/share/locale/ja/LC_TIME/coreutils.mo 5396s /usr/share/locale/hr/LC_TIME/coreutils.mo 5396s /usr/share/locale/pt/LC_TIME/coreutils.mo 5396s /usr/share/locale/ca/LC_TIME/coreutils.mo 5396s /usr/share/locale/sk/LC_TIME/coreutils.mo 5396s /usr/share/locale/zh_CN/LC_TIME/coreutils.mo 5396s /usr/share/locale/ru/LC_TIME/coreutils.mo 5396s /usr/src/linux-headers-6.5.0-5-generic/rust 5396s /usr/src/linux-headers-6.3.0-7-generic/rust 5396s /usr/lib/aarch64-linux-gnu/qt-default/qtchooser/default.conf 5396s autopkgtest [13:15:15]: test show_dangling_symlink_if_any: ---] 5397s autopkgtest [13:15:16]: test show_dangling_symlink_if_any: - - - - - - - - - - results - - - - - - - - - - 5397s show_dangling_symlink_if_any FAIL non-zero exit status 1 5397s autopkgtest [13:15:16]: test 1_of_98__cpptest__CppSignature_test: preparing testbed This permission denied looks making the test fail, I'm not sure if you want to just ignore the find error, or declare the test as need-root capability. G. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pytorch Source-Version: 2.0.1+dfsg-4 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of pytorch, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated pytorch
Bug#1032647: Keeping 525.105.17-1 for bookworm?
On 14/08/2023 10.24, attilio giuseppe carolillo wrote: when do you think 535 drivers will be available in Sid/experimental? I expect new upstream releases for the 470/525 series end of September which I'd like to get into the next Debian (old)stable point releases in October. Thereafter I'll look into 535 for sid. Andreas
Bug#1051889: freeimage: CVE-2020-22524
Source: freeimage X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for freeimage. CVE-2020-22524[0]: | Buffer Overflow vulnerability in FreeImage_Load function in | FreeImage Library 3.19.0(r1828) allows attackers to cuase a denial | of service via crafted PFM file. https://sourceforge.net/p/freeimage/bugs/319/ Fixed with r1848 from http://svn.code.sf.net/p/freeimage/svn/FreeImage/ If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-22524 https://www.cve.org/CVERecord?id=CVE-2020-22524 Please adjust the affected versions in the BTS as needed.
Bug#1051888: Should Kino be removed?
Source: kino Version: 1.3.4+dfsg0-1.1 Severity: serious Your package came up as a candidate for removal from Debian: - Dead upstream for a decade - FTBFS with ffmpeg 5 since 1.5 years (Debian is at ffmpeg 6 by now) - Depends on various legacy libs (GTK2, Glade) If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1051886: pyside2: FTBFS with llvm-toolchain-16 as default
Source: pyside2
Version: 5.15.10-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=pyside2&arch=amd64&ver=5.15.10-3%2Bb1&stamp=1694633885&raw=0
In file included from
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:63:
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.h:55:235:
error: ‘DragMove’ is not a member of ‘QOpenGLShader’
55 | QDragMoveEventWrapper(const QPoint & pos, QFlags
actions, const QMimeData * data, QFlags buttons,
QFlags modifiers, QFlags
type = QOpenGLShader::DragMove);
|
^~~~
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:
In constructor ‘QDragMoveEventWrapper::QDragMoveEventWrapper(const QPoint&,
QFlags, const QMimeData*, QFlags,
QFlags, QFlags)’:
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:103:295:
error: invalid user-defined conversion from
‘QFlags’ to ‘QEvent::Type’ [-fpermissive]
103 | QDragMoveEventWrapper::QDragMoveEventWrapper(const QPoint & pos,
QFlags actions, const QMimeData * data, QFlags
buttons, QFlags modifiers,
QFlags type) : QDragMoveEvent(pos, actions, data,
buttons, modifiers, type)
|
^~~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1305,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:43,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:44,
from /usr/include/x86_64-linux-gnu/qt5/QtCore/QDebug:1,
from
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:48:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:138:29: note: candidate is:
‘constexpr QFlags::operator Int() const [with Enum =
QOpenGLShader::ShaderTypeBit; Int = unsigned int]’ (near match)
138 | Q_DECL_CONSTEXPR inline operator Int() const noexcept { return i; }
| ^~~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:138:29: note: no known
conversion from ‘QFlags::Int’ {aka ‘unsigned
int’} to ‘QEvent::Type’
In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtextlayout.h:49,
from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtextobject.h:46,
from /usr/include/x86_64-linux-gnu/qt5/QtGui/QTextBlock:1,
from
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/pyside2_qtgui_python.h:60,
from
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:60:
/usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:685:84: note: initializing
argument 6 of ‘QDragMoveEvent::QDragMoveEvent(const QPoint&, Qt::DropActions,
const QMimeData*, Qt::MouseButtons, Qt::KeyboardModifiers, QEvent::Type)’
685 |Qt::MouseButtons buttons, Qt::KeyboardModifiers
modifiers, Type type = DragMove);
|
~^~~
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:
In function ‘int Sbk_QDragMoveEvent_Init(PyObject*, PyObject*, PyObject*)’:
/<>/pyside3_build/py3.11-qt5.15.10-64bit-relwithdebinfo/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:218:73:
error: ‘DragMove’ is not a member of ‘QOpenGLShader’
218 | ::QFlags cppArg5 =
QOpenGLShader::DragMove;
|
^~~~
make[3]: *** [PySide2/QtGui/CMakeFiles/QtGui.dir/build.make:559:
PySide2/QtGui/CMakeFiles/QtGui.dir/PySide2/QtGui/qdragmoveevent_wrapper.cpp.o]
Error 1
make[3]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
Processed: tagging 1051885
Processing commands for cont...@bugs.debian.org: > tags 1051885 + sid trixie Bug #1051885 [src:kdevelop] kdevelop: FTBFS with llvm-toolchain-16 as default Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051885: kdevelop: FTBFS with llvm-toolchain-16 as default
Source: kdevelop Version: 4:22.12.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kdevelop&arch=amd64&ver=4%3A22.12.2-2%2Bb1&stamp=1694630976&raw=0 Typical components: all All LLVM libraries (default). engineEither a native JIT or a bitcode interpreter. CMake Error at cmake/modules/FindClang.cmake:113 (message): Could not find Clang builtin directory Call Stack (most recent call first): plugins/CMakeLists.txt:39 (find_package) -- Configuring incomplete, errors occurred! cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt Cheers -- Sebastian Ramacher
Bug#1051883: qttools-opensource-src: FTBFS with llvm-toolchain-16 as default
Source: qttools-opensource-src Version: 5.15.10-3 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=qttools-opensource-src&arch=amd64&ver=5.15.10-3%2Bb1&stamp=1694632815&raw=0 * Start testing of tst_QtDiag * Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.1.0), debian unknown PASS : tst_QtDiag::initTestCase() QDEBUG : tst_QtDiag::run() Launching "/<>/bin/qtdiag" QDEBUG : tst_QtDiag::run() Qt 5.15.10 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.1.0) on "minimal" OS: Debian GNU/Linux trixie/sid [linux version 5.10.0-25-amd64] Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 Environment: QMAKE="/usr/lib/qt5/bin/qmake" QT_PLUGIN_PATH="/usr/lib/x86_64-linux-gnu/qt5/plugins" QT_QPA_PLATFORM="minimal" QT_QTESTLIB_RUNNING="1" QT_SELECT="qt5" Features: QT_NO_EXCEPTIONS Library info: PrefixPath: /usr DocumentationPath: /usr/share/qt5/doc HeadersPath: /usr/include/x86_64-linux-gnu/qt5 LibrariesPath: /usr/lib/x86_64-linux-gnu LibraryExecutablesPath: /usr/lib/x86_64-linux-gnu/qt5/libexec BinariesPath: /usr/lib/qt5/bin PluginsPath: /usr/lib/x86_64-linux-gnu/qt5/plugins ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/imports Qml2ImportsPath: /usr/lib/x86_64-linux-gnu/qt5/qml ArchDataPath: /usr/lib/x86_64-linux-gnu/qt5 DataPath: /usr/share/qt5 TranslationsPath: /usr/share/qt5/translations ExamplesPath: /usr/lib/x86_64-linux-gnu/qt5/examples TestsPath: /usr/tests SettingsPath: /etc/xdg Standard paths [*...* denote writable entry]: DesktopLocation: "Desktop" */<>/debian/.debhelper/generated/_source/home/Desktop* DocumentsLocation: "Documents" */<>/debian/.debhelper/generated/_source/home/Documents* FontsLocation: "Fonts" */<>/debian/.debhelper/generated/_source/home/.local/share/fonts* /<>/debian/.debhelper/generated/_source/home/.fonts /usr/local/share/fonts /usr/share/fonts ApplicationsLocation: "Applications" */<>/debian/.debhelper/generated/_source/home/.local/share/applications* /usr/local/share/applications /usr/share/applications MusicLocation: "Music" */<>/debian/.debhelper/generated/_source/home/Music* MoviesLocation: "Movies" */<>/debian/.debhelper/generated/_source/home/Videos* PicturesLocation: "Pictures" */<>/debian/.debhelper/generated/_source/home/Pictures* TempLocation: "Temporary Directory" */tmp* HomeLocation: "Home" */<>/debian/.debhelper/generated/_source/home* AppLocalDataLocation: "Application Data" */<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag* /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag CacheLocation: "Cache" */<>/debian/.debhelper/generated/_source/home/.cache/QtProject/qtdiag* GenericDataLocation: "Shared Data" */<>/debian/.debhelper/generated/_source/home/.local/share* /usr/local/share /usr/share RuntimeLocation: "Runtime" */tmp/dh-xdg-rundir-ueoJZ1G6* ConfigLocation: "Configuration" */<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg DownloadLocation: "Download" */<>/debian/.debhelper/generated/_source/home/Downloads* GenericCacheLocation: "Shared Cache" */<>/debian/.debhelper/generated/_source/home/.cache* GenericConfigLocation: "Shared Configuration" */<>/debian/.debhelper/generated/_source/home/.config* /etc/xdg AppDataLocation: "Application Data" */<>/debian/.debhelper/generated/_source/home/.local/share/QtProject/qtdiag* /usr/local/share/QtProject/qtdiag /usr/share/QtProject/qtdiag AppConfigLocation: "Application Configuration" */<>/debian/.debhelper/generated/_source/home/.config/QtProject/qtdiag* /etc/xdg/QtProject/qtdiag File selectors (increasing order of precedence): C unix linux debian Network: Using "OpenSSL 3.0.10 1 Aug 2023", version: 0x30a0 Platform capabilities: ThreadedPixmaps MultipleWindows NonFullScreenWindows NativeWidgets WindowManagement Style hints: mouseDoubleClickInterval: 400 mousePressAndHoldInterval: 800 startDragDistance: 10 startDragTime: 500 startDragVelocity: 0 keyboardInputInterval: 400 keyboardAutoRepeatRate: 30 cursorFlashTime: 1000 showIsFullScreen: 0 showIsMaximized: 0 passwordMaskDelay: 0 passwordMaskCharacter: U+25CF fontSmoothingGamma: 1.7 useRtlExtensions: 0 setFocusOnTouchRelease: 0 tabFocusBehavior: Qt::TabFocusAllControls singleClickActivation: 0 Additional style hints (QPlatformIntegration): ReplayMousePressOutsidePopup: 1 Theme: Platforms requested : available : Styles requested: available: Windows,Fusion Fonts: General font : "Helvetica" 12 Fixed font : "Helvetica" 12 Title font : "Helvetica" 12 Smallest font: "Helvetica" 12 Palette: QPalette::WindowText: #ff00 QPalette::Button: #ffefefef QPale
Bug#1051881: postgresql-15: FTBFS with llvm-toolchain-16 as default
Source: postgresql-15 Version: 15.4-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=postgresql-15&arch=amd64&ver=15.4-2%2Bb1&stamp=1694632271&raw=0 2023-09-13 19:10:56.959 UTC checkpointer[931151] LOG: checkpoint complete: wrote 857 buffers (5.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.001 s, total=0.020 s; sync files=0, longest=0.000 s, average=0.000 s; distance=9001 kB, estimate=132962 kB 2023-09-13 19:10:57.025 UTC postmaster[931148] LOG: database system is shut down build/src/test/regress/regression.out test test_setup ... FAILED 357 ms test tablespace ... FAILED 399 ms parallel group (20 tests): int8 oid name varchar bit char regproc boolean pg_lsn text int4 txid int2 money float8 enum uuid float4 rangetypes numeric boolean ... FAILED 225 ms char ... FAILED 214 ms name ... FAILED 198 ms varchar ... FAILED 205 ms text ... FAILED 239 ms int2 ... FAILED 252 ms int4 ... FAILED 246 ms int8 ... FAILED 182 ms oid ... FAILED 188 ms float4 ... FAILED 278 ms float8 ... FAILED 260 ms bit ... FAILED 205 ms numeric ... FAILED 604 ms txid ... FAILED 244 ms uuid ... FAILED 267 ms enum ... FAILED 265 ms money... FAILED 250 ms rangetypes ... FAILED 601 ms pg_lsn ... FAILED 230 ms regproc ... FAILED 211 ms parallel group (19 tests): circle time lseg line numerology point macaddr path timetz date macaddr8 inet interval strings polygon multirangetypes box timestamp timestamptz strings ... FAILED 307 ms numerology ... FAILED 172 ms point... FAILED 183 ms lseg ... FAILED 150 ms line ... FAILED 167 ms box ... FAILED 436 ms path ... FAILED 195 ms polygon ... FAILED 412 ms circle ... FAILED 130 ms date ... FAILED 219 ms time ... FAILED 136 ms timetz ... FAILED 207 ms timestamp... FAILED 535 ms timestamptz ... FAILED 572 ms interval ... FAILED 253 ms inet ... FAILED 244 ms macaddr ... FAILED 190 ms macaddr8 ... FAILED 218 ms multirangetypes ... FAILED 417 ms parallel group (12 tests): comments unicode mvcc misc_sanity expressions tstypes xid horology geometry type_sanity opr_sanity regex geometry ... FAILED 195 ms horology ... FAILED 190 ms tstypes ... FAILED 159 ms regex... FAILED 608 ms type_sanity ... FAILED 210 ms opr_sanity ... FAILED 462 ms misc_sanity ... FAILED 124 ms comments ... FAILED 110 ms expressions ... FAILED 156 ms unicode ... FAILED 118 ms xid ... FAILED 159 ms mvcc ... FAILED 118 ms parallel group (5 tests): copydml copyselect copy insert_conflict insert copy ... FAILED 109 ms copyselect ... FAILED 80 ms copydml ... FAILED 78 ms insert ... FAILED 319 ms insert_conflict ... FAILED 193 ms parallel group (7 tests): create_function_c create_type create_schema create_operator create_procedure create_misc create_table create_function_c... FAILED 65 ms create_misc ... FAILED 121 ms create_operator ... FAILED 98 ms create_procedure ... FAILED 100 ms create_table ... FAILED 418 ms create_type
Bug#1051880: faust: FTBFS with llvm-toolchain-16 as default
Source: faust Version: 2.60.3+ds2-1 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=faust&arch=amd64&ver=2.60.3%2Bds2-1%2Bb1&stamp=1694632020&raw=0 mkdir -p __tmp_llvm_lib__/libLLVMCFGuard.dir && cd __tmp_llvm_lib__/libLLVMCFGuard.dir && ar -x /usr/lib/llvm-16/lib/libLLVMCFGuard.a make[7]: [Make.llvm.static:56: __tmp_llvm_lib__/libLLVMFrontendOpenACC.dir] Error 1 (ignored) mkdir -p __tmp_llvm_lib__/libLLVMFrontendOpenACC.dir && cd __tmp_llvm_lib__/libLLVMFrontendOpenACC.dir && ar -x /usr/lib/llvm-16/lib/libLLVMFrontendOpenACC.a make[7]: [Make.llvm.static:56: __tmp_llvm_lib__/libLLVMFrontendHLSL.dir] Error 1 (ignored) mkdir -p __tmp_llvm_lib__/libLLVMFrontendHLSL.dir && cd __tmp_llvm_lib__/libLLVMFrontendHLSL.dir && ar -x /usr/lib/llvm-16/lib/libLLVMFrontendHLSL.a make[7]: [Make.llvm.static:56: __tmp_llvm_lib__/libLLVMExtensions.dir] Error 1 (ignored) mkdir -p __tmp_llvm_lib__/libLLVMExtensions.dir && cd __tmp_llvm_lib__/libLLVMExtensions.dir && ar -x /usr/lib/llvm-16/lib/libLLVMExtensions.a make[7]: *** No rule to make target '__tmp_llvm_lib__/libPolly.dir', needed by 'lib/libfaustwithllvm.a'. Stop. make[7]: Leaving directory '/<>/build' gmake[6]: *** [CMakeFiles/staticlib.dir/build.make:3284: /<>/build/lib/libfaust.a] Error 2 gmake[6]: *** Deleting file '/<>/build/lib/libfaust.a' gmake[6]: Leaving directory '/<>/build/faustdir' Cheers -- Sebastian Ramacher
Processed: Re: linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Processing control commands: > tag -1 wontfix Bug #1051849 [dkms] linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64 Added tag(s) wontfix. > close -1 Bug #1051849 [dkms] linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64 Marked Bug as done -- 1051849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051849: linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Control: tag -1 wontfix Control: close -1 On Wed, 13 Sep 2023 11:40:28 -0400 Michael Cuffaro wrote: CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.o /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.c: In function ‘rtw_regd_init’: /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.c:409:36: error: ‘REGULATORY_IGNORE_STALE_KICKOFF’ undeclared (first use in this function) 409 | wiphy->regulatory_flags |= REGULATORY_IGNORE_STALE_KICKOFF; |^~~ /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.c:409:36: note: each undeclared identifier is reported only once for each function it appears in CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/rtw_rhashtable.o make[2]: *** [/usr/src/linux-headers-6.1.0-12-common/scripts/Makefile.build:255: /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.o] Error 1 This error (and fixing it) is in the realm of the rtl88x2bu dkms kernel module which is not packaged in Debian, but provided by some third party. Please report the bug there. It was probably caused by some changes getting backported (by Linux upstream to the stable 6.1 tree, not by the Debian kernel maintainers) that cause some out-of-tree modules to fail building. That happens all the time. There is no general CI for out-of-tree modules ... but at least we have some for the *-dkms packages in Debian, so breakage can be noticed early for *packaged* out-of-tree modules in Debian. There is nothing the dkms (or any other) Debian package can do about it, therefore I'm closing this bug as "wontfix". Andreas
Bug#1051870: libpmix2: broken library symlink
Package: libpmix2 Version: 5.0.1-1 Severity: grave Justification: renders package unusable Dear maintainer, Starting with version 5.0.1-1, the libpmix2 package ships a dead symlink for /usr/lib//libpmix.so.2. For instance: $ dpkg -c libpmix2_5.0.1-1_amd64.deb | grep libpmix.so -rw-r--r-- root/root 2184040 2023-08-08 10:50 ./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2.13.1 lrwxrwxrwx root/root 0 2023-08-08 10:50 ./usr/lib/x86_64-linux-gnu/libpmix.so.2 -> pmix2/lib/libpmix.so.2.13.0 lrwxrwxrwx root/root 0 2023-08-08 10:50 ./usr/lib/x86_64-linux-gnu/libpmix.so.2.13.0 -> pmix2/lib/libpmix.so.2.13.0 lrwxrwxrwx root/root 0 2023-08-08 10:50 ./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2 -> libpmix.so.2.13.1 This breaks libraries depending on it and causes packages to FTBFS. Regards Aurelien
Processed: limit source to linux, tagging 1025845, tagging 1051249
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1025845 + pending Bug #1025845 [src:linux] linux: please enable CONFIG_KFENCE Added tag(s) pending. > tags 1051249 + pending Bug #1051249 [src:linux] linux: s390x: FTBFS: kernel-wedge install-files: missing modules mptfc, mptsas and mptspi Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025845 1051249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051866: gpac: CVE-2023-0770 CVE-2023-0760 CVE-2023-0358 CVE-2023-23145 CVE-2023-23144 CVE-2023-23143 CVE-2022-4202 CVE-2022-45343 CVE-2022-45283 CVE-2022-45202 CVE-2022-43045 CVE-2022-43044 CVE-
Source: gpac Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi Some of the CVEs in #1033116 seems to not have been addressed (and in part were addressed in a DSA already). Here a fresh bug for the remaining ones. Hi, The following vulnerabilities were published for gpac. CVE-2023-0770[0]: | Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to | 2.2. CVE-2023-0760[1]: | Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to | V2.1.0-DEV. CVE-2023-0358[2]: | Use After Free in GitHub repository gpac/gpac prior to 2.3.0-DEV. CVE-2023-23145[3]: | GPAC version 2.2-rev0-gab012bbfb-master was discovered to contain a | memory leak in lsr_read_rare_full function. CVE-2023-23144[4]: | Integer overflow vulnerability in function Q_DecCoordOnUnitSphere | file bifs/unquantize.c in GPAC version 2.2-rev0-gab012bbfb-master. CVE-2023-23143[5]: | Buffer overflow vulnerability in function avc_parse_slice in file | media_tools/av_parsers.c. GPAC version 2.3-DEV- | rev1-g4669ba229-master. CVE-2022-4202[6]: | A vulnerability, which was classified as problematic, was found in | GPAC 2.1-DEV-rev490-g68064e101-master. Affected is the function | lsr_translate_coords of the file laser/lsr_dec.c. The manipulation | leads to integer overflow. It is possible to launch the attack | remotely. The exploit has been disclosed to the public and may be | used. The name of the patch is | b3d821c4ae9ba62b3a194d9dcb5e99f17bd56908. It is recommended to apply | a patch to fix this issue. VDB-214518 is the identifier assigned to | this vulnerability. CVE-2022-45343[7]: | GPAC v2.1-DEV-rev478-g696e6f868-master was discovered to contain a | heap use-after-free via the Q_IsTypeOn function at | /gpac/src/bifs/unquantize.c. CVE-2022-45283[8]: | GPAC MP4box v2.0.0 was discovered to contain a stack overflow in the | smil_parse_time_list parameter at /scenegraph/svg_attributes.c. CVE-2022-45202[9]: | GPAC v2.1-DEV-rev428-gcb8ae46c8-master was discovered to contain a | stack overflow via the function dimC_box_read at | isomedia/box_code_3gpp.c. CVE-2022-43045[10]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_dump_vrml_sffield at | /scene_manager/scene_dump.c. CVE-2022-43044[11]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_isom_get_meta_item_info | at /isomedia/meta.c. CVE-2022-43043[12]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function BD_CheckSFTimeOffset at | /bifs/field_decode.c. CVE-2022-43042[13]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | heap buffer overflow via the function FixSDTPInTRAF at | isomedia/isom_intern.c. CVE-2022-43040[14]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | heap buffer overflow via the function gf_isom_box_dump_start_ex at | /isomedia/box_funcs.c. CVE-2022-43039[15]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function | gf_isom_meta_restore_items_ref at /isomedia/meta.c. CVE-2022-3222[16]: | Uncontrolled Recursion in GitHub repository gpac/gpac prior to | 2.1.0-DEV. 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-2023-0770 https://www.cve.org/CVERecord?id=CVE-2023-0770 [1] https://security-tracker.debian.org/tracker/CVE-2023-0760 https://www.cve.org/CVERecord?id=CVE-2023-0760 [2] https://security-tracker.debian.org/tracker/CVE-2023-0358 https://www.cve.org/CVERecord?id=CVE-2023-0358 [3] https://security-tracker.debian.org/tracker/CVE-2023-23145 https://www.cve.org/CVERecord?id=CVE-2023-23145 [4] https://security-tracker.debian.org/tracker/CVE-2023-23144 https://www.cve.org/CVERecord?id=CVE-2023-23144 [5] https://security-tracker.debian.org/tracker/CVE-2023-23143 https://www.cve.org/CVERecord?id=CVE-2023-23143 [6] https://security-tracker.debian.org/tracker/CVE-2022-4202 https://www.cve.org/CVERecord?id=CVE-2022-4202 [7] https://security-tracker.debian.org/tracker/CVE-2022-45343 https://www.cve.org/CVERecord?id=CVE-2022-45343 [8] https://security-tracker.debian.org/tracker/CVE-2022-45283 https://www.cve.org/CVERecord?id=CVE-2022-45283 [9] https://security-tracker.debian.org/tracker/CVE-2022-45202 https://www.cve.org/CVERecord?id=CVE-2022-45202 [10] https://security-tracker.debian.org/tracker/CVE-2022-43045 https://www.cve.org/CVERecord?id=CVE-2022-43045 [11] https://security-tracker.debian.org/tracker/CVE-2022-43044 https://www.cve.org/CVERecord?id=CVE-2022-43044 [12] https://security-tracker.debian.org/tracker/CVE-2022-43043 https://www.cve.org/CVERecord?id=CVE
Processed: tagging 1051859, tagging 1051860, tagging 1051863, tagging 1051864
Processing commands for cont...@bugs.debian.org: > tags 1051859 + sid trixie Bug #1051859 [src:ghdl] ghdl: BD-Uninstallable Added tag(s) sid and trixie. > tags 1051860 + sid trixie Bug #1051860 [src:ccls] ccls: FTBFS with llvm-toolchain-16 das default Added tag(s) sid and trixie. > tags 1051863 + sid trixie Bug #1051863 [src:ldc] ldc: FRBFS with llvm-toolchain-16 as default Added tag(s) trixie and sid. > tags 1051864 + sid trixie Bug #1051864 [src:sparse] sparce: FTBFS with llvm-toolchain-16 as default Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051859 1051860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051860 1051863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051863 1051864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051864: sparce: FTBFS with llvm-toolchain-16 as default
Source: sparse Version: 0.6.4-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=sparse&arch=amd64&ver=0.6.4-3%2Bb1&stamp=1694628480&raw=0 g++ -L/usr/lib/llvm-16/lib -Wl,-z,relro -Wl,-z,now -Wl,--as-needed sparse-llvm.o libsparse.a -lLLVM-16 -o sparse-llvm /usr/bin/ld: sparse-llvm.o: in function `get_sym_value': ././sparse-llvm.c:305:(.text+0x7b2): undefined reference to `LLVMConstGEP' /usr/bin/ld: sparse-llvm.o: in function `calc_gep': ././sparse-llvm.c:488:(.text+0xe37): undefined reference to `LLVMBuildInBoundsGEP' /usr/bin/ld: sparse-llvm.o: in function `output_op_load': ././sparse-llvm.c:714:(.text+0x24a9): undefined reference to `LLVMBuildLoad' /usr/bin/ld: sparse-llvm.o: in function `output_op_call': ././sparse-llvm.c:822:(.text+0x262e): undefined reference to `LLVMBuildCall' collect2: error: ld returned 1 exit status Cheers -- Sebastian Ramacher
Bug#1051863: ldc: FRBFS with llvm-toolchain-16 as default
Source: ldc
Version: 1:1.30.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=ldc&arch=amd64&ver=1%3A1.30.0-1%2Bb2&stamp=1694629363&raw=0
[ 14%] Building CXX object CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o
/usr/bin/c++ -DLDC_ENABLE_PLUGINS -DLDC_LLVM_SUPPORTED_TARGET_AArch64=1
-DLDC_LLVM_SUPPORTED_TARGET_AMDGPU=1 -DLDC_LLVM_SUPPORTED_TARGET_ARM=1
-DLDC_LLVM_SUPPORTED_TARGET_AVR=1 -DLDC_LLVM_SUPPORTED_TARGET_BPF=1
-DLDC_LLVM_SUPPORTED_TARGET_Hexagon=1 -DLDC_LLVM_SUPPORTED_TARGET_Lanai=1
-DLDC_LLVM_SUPPORTED_TARGET_LoongArch=1 -DLDC_LLVM_SUPPORTED_TARGET_M68k=1
-DLDC_LLVM_SUPPORTED_TARGET_MSP430=1 -DLDC_LLVM_SUPPORTED_TARGET_Mips=1
-DLDC_LLVM_SUPPORTED_TARGET_NVPTX=1 -DLDC_LLVM_SUPPORTED_TARGET_PowerPC=1
-DLDC_LLVM_SUPPORTED_TARGET_RISCV=1 -DLDC_LLVM_SUPPORTED_TARGET_Sparc=1
-DLDC_LLVM_SUPPORTED_TARGET_SystemZ=1 -DLDC_LLVM_SUPPORTED_TARGET_VE=1
-DLDC_LLVM_SUPPORTED_TARGET_WebAssembly=1 -DLDC_LLVM_SUPPORTED_TARGET_X86=1
-DLDC_LLVM_SUPPORTED_TARGET_XCore=1 -DLDC_LLVM_SUPPORTED_TARGET_Xtensa=1
-I/<>/. -I/<>/dmd -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DDMDV2
-I/usr/lib/llvm-16/include -std=c++17 -fno-exceptions -D_GNU_SOURCE
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti
-Wall -Wextra -Wno-unused-parameter -Wno-comment
-Wno-missing-field-initializers -Wno-non-virtual-dtor -Wno-pedantic
-fvisibility-inlines-hidden -DLDC_POSIX -DIN_LLVM -DOPAQUE_VTBLS
"-DLDC_INSTALL_PREFIX=R\"(/usr)\"" -DLDC_LLVM_VER=1600
"-DLDC_LIBDIR_SUFFIX=R\"()\"" -DLDC_HOST_GDMD=1 -DLDC_HOST_FE_VER=2103
"-DLDC_LLVM_LIBDIR=R\"(/usr/lib/llvm-16/lib)\"" -DNDEBUG -MD -MT
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o -MF
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o.d -o
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o -c /<>/gen/asm-gcc.cpp
In file included from /<>/gen/abi-x86.cpp:12:
/<>/./gen/abi-generic.h: In member function ‘virtual llvm::Value*
BaseBitcastABIRewrite::put(DValue*, bool, bool)’:
/<>/./gen/abi-generic.h:142:68: warning: ‘llvm::Type*
llvm::Type::getPointerElementType() const’ is deprecated: Deprecated without
replacement, see https://llvm.org/docs/OpaquePointers.html for context and
migration instructions [-Wdeprecated-declarations]
142 | LLType *pointeeType = address->getType()->getPointerElementType();
| ~^~
In file included from /<>/./gen/llvm.h:20,
from /<>/./gen/attributes.h:12,
from /<>/./gen/tollvm.h:22,
from /<>/./gen/dibuilder.h:12,
from /<>/./gen/irstate.h:18,
from /<>/./gen/abi-generic.h:17:
/usr/lib/llvm-16/include/llvm/IR/Type.h:409:9: note: declared here
409 | Type *getPointerElementType() const {
| ^
/<>/gen/abi-x86.cpp: In member function ‘void
X86TargetABI::workaroundIssue1356(std::vector&) const’:
/<>/gen/abi-x86.cpp:270:41: error: ‘struct llvm::MaybeAlign’ has
no member named ‘getValueOr’
270 | if (arg->attrs.getAlignment().getValueOr(align4) > align4)
| ^~
make[4]: *** [CMakeFiles/LDCShared.dir/build.make:219:
CMakeFiles/LDCShared.dir/gen/abi-x86.cpp.o] Error 1
make[4]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
Bug#1051860: ccls: FTBFS with llvm-toolchain-16 das default
Source: ccls
Version: 0.20220729-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=ccls&arch=arm64&ver=0.20220729-2%2Bb1&stamp=1694628056&raw=0
/usr/bin/c++ -I/<>/src -isystem /<>/third_party
-isystem /usr/lib/llvm-16/include -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -mbranch-protection=standard -Wdate-time
-D_FORTIFY_SOURCE=2 -std=c++17 -Wall -Wno-sign-compare -Wno-return-type
-Wno-unused-result -MD -MT CMakeFiles/ccls.dir/src/pipeline.cc.o -MF
CMakeFiles/ccls.dir/src/pipeline.cc.o.d -o
CMakeFiles/ccls.dir/src/pipeline.cc.o -c /<>/src/pipeline.cc
/<>/src/indexer.cc:1097:8: error: ‘void
ccls::{anonymous}::IndexPPCallbacks::InclusionDirective(clang::SourceLocation,
const clang::Token&, llvm::StringRef, bool, clang::CharSourceRange,
llvm::Optional, llvm::StringRef, llvm::StringRef, const
clang::Module*, clang::SrcMgr::CharacteristicKind)’ marked ‘override’, but does
not override
1097 | void InclusionDirective(SourceLocation hashLoc, const Token &tok,
|^~
Cheers
--
Sebastian Ramacher
Bug#1051859: ghdl: BD-Uninstallable
Source: ghdl Version: 2.0.0+dfsg-6.2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=ghdl Dependency installability problem for ghdl on amd64: ghdl build-depends on missing: - llvm-dev:amd64 (< 1:15~) Cheers -- Sebastian Ramacher
Bug#1051858: clazy: FTBFS with llvm-toochain-16 as default
Source: clazy Version: 1.11-4 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=clazy&arch=armhf&ver=1.11-4%2Bb1&stamp=1694627460&raw=0 [ 1%] Building CXX object CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.gch /usr/bin/c++ -DClazyPlugin_EXPORTS -DHAS_STD_FILESYSTEM -DHAVE_CLANG_CONFIG_H -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -I/<>/obj-arm-linux-gnueabihf -I/usr/lib/llvm-16/include -I/usr/lib/llvm-16/tools/clang/include -I/tools/clang/include -I/<> -I/<>/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-class-memaccess -Wdate-time -D_FORTIFY_SOURCE=2 -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -fno-exceptions -fno-rtti -fPIC -std=gnu++17 -fPIC -Winvalid-pch -x c++-header -include /<>/obj-arm-linux-gnueabihf/CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx -MD -MT CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.gch -MF CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.gch.d -o CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.gch -c /<>/obj-arm-linux-gnueabihf/CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.cxx make[3]: Leaving directory '/<>/obj-arm-linux-gnueabihf' [ 1%] Built target man In file included from /<>/src/checkbase.h:29, from /<>/obj-arm-linux-gnueabihf/CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx:5, from : /<>/src/SourceCompatibilityHelpers.h: In function ‘auto clazy::getBuffer(const clang::SourceManager&, clang::FileID, bool*)’: /<>/src/SourceCompatibilityHelpers.h:112:24: error: ‘class std::optional’ has no member named ‘hasValue’; did you mean ‘has_value’? 112 | *invalid = !buffer.hasValue(); |^~~~ |has_value /<>/src/checkbase.h: At global scope: /<>/src/checkbase.h:93:10: error: ‘void ClazyPreprocessorCallbacks::InclusionDirective(clang::SourceLocation, const clang::Token&, llvm::StringRef, bool, clang::CharSourceRange, clazy::OptionalFileEntryRef, llvm::StringRef, llvm::StringRef, const clang::Module*, clang::SrcMgr::CharacteristicKind)’ marked ‘override’, but does not override 93 | void InclusionDirective(clang::SourceLocation HashLoc, const clang::Token &IncludeTok, clang::StringRef FileName, bool IsAngled, | ^~ make[3]: *** [CMakeFiles/ClazyPlugin.dir/build.make:80: CMakeFiles/ClazyPlugin.dir/cmake_pch.hxx.gch] Error 1 -- Sebastian Ramacher
Bug#1042336: moment-timezone.js: FTBFS: cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory
Hi, Thanks Daniel for spotting this, somehow I had missed all notifications and did not even realise Prometheus was about to be removed from testing :( I have just ported the patch from Benjamin and after I finish building the package I will upload it. On 10/09/2023 06:50, Daniel Swarbrick wrote: On Wed, 26 Jul 2023 22:08:15 +0200 Lucas Nussbaum wrote: > Relevant part (hopefully): > > mkdir -p temp/zic/2023c temp/zdump/2023c > > cp -RL /usr/share/zoneinfo/posix/* temp/zic/2023c/ > > cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory > > make[1]: *** [debian/rules:51: data/unpacked/2023c.json] Error 1 This appears to have broken due to a change in the tzdata package which landed in both Debian and Ubuntu[1]. The Ubuntu moment-timezone.js package was adapted[2] to accommodate this change, but the Debian package was not. [1]: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2008076 [2]: https://git.launchpad.net/ubuntu/+source/moment-timezone.js/commit/debian?h=applied/ubuntu/lunar -- Martina Ferrari (Tina)
Processed: Re: Bug#1051849: linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Processing control commands: > reassign -1 dkms Bug #1051849 [src:linux] linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64 Bug reassigned from package 'src:linux' to 'dkms'. No longer marked as found in versions linux/6.1.52-1. Ignoring request to alter fixed versions of bug #1051849 to the same values previously set > tag -1 -ftbfs Bug #1051849 [dkms] linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64 Removed tag(s) ftbfs. -- 1051849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051849: linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Control: reassign -1 dkms Control: tag -1 -ftbfs On Wednesday, 13 September 2023 17:40:28 CEST Michael Cuffaro wrote: > Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64) > Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information. No idea where you got that from, but it's a dkms 'package' responsibility to adjust for kernel changes. signature.asc Description: This is a digitally signed message part.
Bug#1040682: marked as done (FTBFS in colord with meson 1.2.0 rc2)
Your message dated Wed, 13 Sep 2023 16:04:17 + with message-id and subject line Bug#1040682: fixed in colord 1.4.6-3 has caused the Debian Bug report #1040682, regarding FTBFS in colord with meson 1.2.0 rc2 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.) -- 1040682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: colord Version: 1.4.6-2.2 Severity: serious Tags: ftbfs colord successfully passes dh_auto_configure, but fails to build immediately after: ``` dh override_dh_auto_configure-arch make[1]: Leaving directory '/<>' debian/rules override_dh_auto_configure-indep make[1]: Entering directory '/<>' meson configure -Dsession_example=false -Ddaemon_user=colord -Dvapi=true -Ddocs=false -Dinstalled_tests=true -Dargyllcms_sensor=true -Dsane=true -Dprint_profiles=true ERROR: No valid build directory found, cannot modify options. make[1]: *** [debian/rules:38: override_dh_auto_configure-indep] Error 1 ``` The cause of this is that setup options are passed to meson's "print the values of all options" subcommand. Previous versions of meson would print the following warning: The source directory instead of the build directory was specified. Only the default values for the project are printed, and all command line parameters are ignored. The release candidate makes this an error instead. If you want to print the values of available options, simply avoid passing arguments; this works both in a source directory and a build directory. -- Eli Schwartz --- End Message --- --- Begin Message --- Source: colord Source-Version: 1.4.6-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of colord, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated colord 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, 13 Sep 2023 11:07:00 -0400 Source: colord Built-For-Profiles: noudeb Architecture: source Version: 1.4.6-3 Distribution: unstable Urgency: medium Maintainer: Christopher James Halse Rogers Changed-By: Jeremy Bícha Closes: 1032263 1040682 Changes: colord (1.4.6-3) unstable; urgency=medium . * Team upload (Closes: #1032263) * Simplify handling of arch:all/arch:any builds (Closes: #1040682) Checksums-Sha1: 263ac8ef773f3d3958d787f3de86e9b3e1870b40 3303 colord_1.4.6-3.dsc b5e6d2e0942ea685df32734638658e8df435ac20 28776 colord_1.4.6-3.debian.tar.xz 58388605b8c3bbf0aa5eec71c4efe484a1ce5a20 13271 colord_1.4.6-3_source.buildinfo Checksums-Sha256: a1799305f3e24b64b158fd8bff580bec102b7e28d06b2abcbb91f42f03f9a548 3303 colord_1.4.6-3.dsc 033f1384fe6ce8738eb2d975238763b5671cd45fecc251be36e7825db3209b2c 28776 colord_1.4.6-3.debian.tar.xz 42741479cc02e0b4bbf053b32ed53d34f8b070923ab00cbfa10a45a88d6d8090 13271 colord_1.4.6-3_source.buildinfo Files: c76c1f78b0ba95195322d39f311f0adf 3303 graphics optional colord_1.4.6-3.dsc 9f3822fec2baad6c01c78c14951b2eba 28776 graphics optional colord_1.4.6-3.debian.tar.xz 4d79bb6f3b8db0f87cc5bafe8031d1cb 13271 graphics optional colord_1.4.6-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmUB2gAACgkQ5mx3Wuv+ bH0QaQ/+Pmf7nnmTo8NXmX3xt1mzeh8RJytLnQqZ8qQ0ThVMh1vA3yIPGSYmHleG 8oDFlVtPYvnevo6b6dB7xmTj+wpnZUi9MdQQY5BNaxGfYaaR/GTn7v0QZSzMuDIn 80g4aq7kOc2gNgJgniWGPeNgLnfcZr+ycpqYOxDUf4T8KWkI1dtQHBhzp39BtrHD MQ96XUWb4y11QEDKFC8731f2Mea7XPGD/vJeYJ+AYzuo2vv9a/oYaln5qIZVGL5X wqrA8aQEy6yWczC1OC98BAMVEKLAQcJYQi9yxVTbmFUuNi9prfLr7e06/6brGFRY 5z0Ra8yGb2INJEwccoQZLGo9j12YilGT9+/nHiIvElZ+mx1Ylmc1BanaNBxUGZi+ czRJuDTQn6Oaz86EViB1QP8bMzV2Oz0QfnMtDSRO0Dx8zsfsmDmCkY+g6oebnHZR kQ8fqWSLTfFPdcsKSoDsns98/IvcHTck7sqXo04+tqGzaEWqh1R2ztWIa1rN3yFe k2+rexr1fOcu5dZ+VCS4fXO/QXHaD8GBEvYGqBm7LgU+xIDNR3dCSODUYM30YttB Xbmq0W1nMjqRJxQLDFXRytjXUlgS8M5oRoU4jJ7te9q3b454IdFmNDRNfuxOfzEn h/jjO6UxGmUs8K1PSd3+acVPFFSedhOoBkvpSWKa4ZznYNapixg= =h8MH -END PGP SIGNATURE End Message ---
Bug#1051850: pastescript: FTBFS due to new dh-python clean behaviour
Package: pastescript Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu mantic ubuntu-patch X-Debbugs-Cc: scho...@ubuntu.com Hi, In Ubuntu, the attached patch was applied to work around dh-python removing the test FakePlugin.egg-info directory in the clean step, which is needed for some tests. This is fairly ugly, since Ubuntu has a fairly tight schedule and release is looming, but I'm hoping we'll come up with a better solve in bug 1051837 -- System Information: Debian Release: trixie/sid APT prefers mantic APT policy: (500, 'mantic') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-7-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pastescript-3.2.1/debian/rules pastescript-3.2.1/debian/rules --- pastescript-3.2.1/debian/rules 2022-11-20 12:38:22.0 +0100 +++ pastescript-3.2.1/debian/rules 2023-09-13 12:18:46.0 +0200 @@ -27,3 +27,9 @@ override_dh_installchangelogs: dh_installchangelogs docs/news.txt + +override_dh_auto_clean: + # Work around LP: #2035337 + mv tests/fake_packages/FakePlugin.egg/FakePlugin.egg-info/ fakeplugin.back + dh_auto_clean + mv fakeplugin.back tests/fake_packages/FakePlugin.egg/FakePlugin.egg-info/
Bug#1051849: linux-image-6.1.0-12-amd64: Failure to upgrade to linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Package: src:linux Version: 6.1.52-1 Severity: grave Tags: ftbfs Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I ran apt full-upgrade as I usually do * What exactly did you do (or not do) that was effective (or ineffective)? After getting the error I tried apt -f install * What was the outcome of this action? $ sudo apt -f install Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.1.0-10-amd64 linux-headers-6.1.0-10-common linux-image-6.1.0-10-amd64 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up linux-image-6.1.0-12-amd64 (6.1.52-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-12-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... './driverctl' make all(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-12-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.1.0-12-amd64 (--configure): installed linux-image-6.1.0-12-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-headers-6.1.0-12-amd64 (6.1.52-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-12-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... './driverctl' make all...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64) Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-12-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-12-amd64.postinst line 11. dpkg: error processing package linux-headers-6.1.0-12-amd64 (--configure): installed linux-headers-6.1.0-12-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.1.0-12-amd64 (= 6.1.52-1); however: Package linux-headers-6.1.0-12-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.1.0-12-amd64 (= 6.1.52-1); however: Package linux-image-6.1.0-12-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.1.0-12-amd64 linux-headers-6.1.0-12-amd64 linux-headers-amd64 linux-image-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Here are the contents of /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log: $ cat /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log DKMS make.log for rtl88x2bu-5.13.1 for kernel 6.1.0-12-amd64 (x86_64) Wed 13 Sep 2023 11:09:22 AM EDT make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.0-12-amd64/build M=/var/lib/dkms/rtl88x2bu/5.13.1/build modules make[1]: Entering directory '/usr/src/linux-headers-6.1.0-12-amd64' CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl
Bug#1042342: marked as pending in yarl
Control: tag -1 pending Hello, Bug #1042342 in yarl 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/yarl/-/commit/56bd15a47b215e9d1d515854e234cc8d7dfba584 d/patches/square_bracket_handling.patch: cherry-picked from upstream. Fixes FTBFS. Closes: #1042342 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042342
Processed: Bug#1042342 marked as pending in yarl
Processing control commands:
> tag -1 pending
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Ignoring request to alter tags of bug #1042342 to the same tags previously set
--
1042342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042342: yarl: fix pushed to repo, permission to release?
Control: tags 1042342 + patch
Control: tags 1042342 + pending
Dear maintainer,
I've pushed a commit using a patch cherry-picked from upstream[0] to fix this
issue.
If you don't object, I'll make a team upload of yarl (versioned as 1.8.2-2) with
this fix.
Regards,
[0] https://github.com/aio-libs/yarl/pull/882
diff -Nru yarl-1.8.2/debian/changelog yarl-1.8.2/debian/changelog
--- yarl-1.8.2/debian/changelog 2023-01-17 20:02:27.0 +0100
+++ yarl-1.8.2/debian/changelog 2023-09-13 17:23:01.0 +0200
@@ -1,3 +1,11 @@
+yarl (1.8.2-2) UNRELEASED; urgency=medium
+
+ * Team upload.
+ * d/patches/square_bracket_handling.patch: cherry-picked from upstream.
+Fixes FTBFS. Closes: #1042342
+
+ -- Michael R. Crusoe Wed, 13 Sep 2023 17:23:01 +0200
+
yarl (1.8.2-1) unstable; urgency=medium
* New upstream release
diff -Nru yarl-1.8.2/debian/patches/series yarl-1.8.2/debian/patches/series
--- yarl-1.8.2/debian/patches/series2023-01-17 20:02:27.0 +0100
+++ yarl-1.8.2/debian/patches/series2023-09-13 17:21:57.0 +0200
@@ -1,3 +1,4 @@
+square_bracket_handling.patch
0001-do-not-add-changelog-to-long-description.patch
0002-docs-disable-intersphinx.patch
0003-docs-disable-sidebar_collapse-option.patch
diff -Nru yarl-1.8.2/debian/patches/square_bracket_handling.patch
yarl-1.8.2/debian/patches/square_bracket_handling.patch
--- yarl-1.8.2/debian/patches/square_bracket_handling.patch 1970-01-01
01:00:00.0 +0100
+++ yarl-1.8.2/debian/patches/square_bracket_handling.patch 2023-09-13
17:22:02.0 +0200
@@ -0,0 +1,125 @@
+From 5c977b52a33bf58f016e5968934c3fcb8b49b239 Mon Sep 17 00:00:00 2001
+From: Martijn Pieters
+Date: Tue, 6 Jun 2023 17:38:47 +0100
+Subject: [PATCH] Correct square bracket handling in URL netloc
+
+- The human representation of usernames and passwords should percent-
+ encode square brackets.
+- Clean up the test suite to remove tests that use invalid hostnames
+ (square brackets in a host name must only be used for IPv6 addresses).
+- Rename the remaining test using IPvFuture address syntax to make this
+ explicit.
+- Drop a test for IPv6 addresses with a zone id; zone id support is
+ controversial and expilictly excluded from the WHATWG URL standard.
+ Zone ids *without percent characters in their name* continue to work
+ as long as urllib.parse.urlsplit() accepts them but this is not
+ something that yarl.URL() needs to support explicitly.
+---
+ CHANGES/876.bugfix.rst| 1 +
+ tests/test_url.py | 10 ++
+ tests/test_url_parsing.py | 28 ++--
+ yarl/_url.py | 4 ++--
+ 4 files changed, 7 insertions(+), 36 deletions(-)
+ create mode 100644 CHANGES/876.bugfix.rst
+
+--- /dev/null
yarl/CHANGES/876.bugfix.rst
+@@ -0,0 +1 @@
++Fixed the human representation of URLs with square brackets in usernames and
passwords.
+--- yarl.orig/tests/test_url.py
yarl/tests/test_url.py
+@@ -235,12 +235,6 @@
+ assert url.host == url.raw_host
+
+
+-def test_ipv6_zone():
+-url = URL("http://[fe80::822a:a8ff:fe49:470c%ÑеÑÑ%42]:123";)
+-assert url.raw_host == "fe80::822a:a8ff:fe49:470c%ÑеÑÑ%42"
+-assert url.host == url.raw_host
+-
+-
+ def test_ipv4_zone():
+ # I'm unsure if it is correct.
+ url = URL("http://1.2.3.4%ÑеÑÑ%42:123";)
+@@ -1514,8 +1508,8 @@
+ s = url.human_repr()
+ assert URL(s) == url
+ assert (
+-s == "http:// !\"%23$%25&'()*+,-.%2F%3A;<=>%3F%40[\\]^_`{|}~"
+-": !\"%23$%25&'()*+,-.%2F%3A;<=>%3F%40[\\]^_`{|}~"
++s == "http:// !\"%23$%25&'()*+,-.%2F%3A;<=>%3F%40%5B\\%5D^_`{|}~"
++": !\"%23$%25&'()*+,-.%2F%3A;<=>%3F%40%5B\\%5D^_`{|}~"
+ "@Ñ
оÑÑ.домен:8080"
+ "/ !\"%23$%25&'()*+,-./:;<=>%3F@[\\]^_`{|}~"
+ "? !\"%23$%25%26'()*%2B,-./:%3B<%3D>?@[\\]^_`{|}~"
+--- yarl.orig/tests/test_url_parsing.py
yarl/tests/test_url_parsing.py
+@@ -178,14 +178,6 @@
+ assert u.query_string == ""
+ assert u.fragment == ""
+
+-def test_masked_ipv4(self):
+-u = URL("//[127.0.0.1]/")
+-assert u.scheme == ""
+-assert u.host == "127.0.0.1"
+-assert u.path == "/"
+-assert u.query_string == ""
+-assert u.fragment == ""
+-
+ def test_ipv6(self):
+ u = URL("//[::1]/")
+ assert u.scheme == ""
+@@ -194,15 +186,7 @@
+ assert u.query_string == ""
+ assert u.fragment == ""
+
+-def test_strange_ip(self):
+-u = URL("//[-1]/")
+-assert u.scheme == ""
+-assert u.host == "-1"
+-assert u.path == "/"
+-assert u.query_string == ""
+-assert u.fragment == ""
+-
+-def test_strange_ip_2(self):
++def test_ipvfuture_address(self):
+ u = URL("//[v1.-1]/")
+ assert u.scheme == ""
+ assert u.host == "v1.-1"
+@@ -210,14 +194,6 @@
+ assert u.query_string == ""
+ assert u.fragment == ""
+
+-def test_strange_ip
Processed: yarl: fix pushed to repo, permission to release?
Processing control commands:
> tags 1042342 + patch
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) patch.
> tags 1042342 + pending
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1042342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1050942: marked as done (FTBFS: Failed 1/1 test programs. 5/246 subtests failed.)
Your message dated Wed, 13 Sep 2023 15:04:37 + with message-id and subject line Bug#1050942: fixed in blhc 0.13+git20230913.fb2c46d-1 has caused the Debian Bug report #1050942, regarding FTBFS: Failed 1/1 test programs. 5/246 subtests failed. 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.) -- 1050942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: blhc Version: 0.13-5 Severity: serious Tags: ftbfs upstream Justification: fails to build from source X-Debbugs-Cc: eribe...@debian.org, Simon Ruderich Dear Simon Ruderich, Currently blhc fails to build from source in Debian Sid. This issue was detected in Salsa[1]. [1] https://salsa.debian.org/debian/blhc/-/jobs/4635438 I also tested it in a fresh jail: dh_auto_test /usr/bin/perl Build test --verbose 1 # Failed test './t/logs/arch-avr32 --color (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. # LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o # CFLAGS missing (-fstack-protector-strong): gcc -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Wformat-security -Werror=format-security -Wall -c test.c # LDFLAGS missing (-Wl,-z,relro): gcc -o test test.o # ' # expected: 'CFLAGS missing (-fstack-protector-strong): gcc -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Wformat-security -Werror=format-security -Wall -c test.c # ' # Failed test './t/logs/arch-avr32 (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # checking './t/logs/debian-hardening-wrapper'... # HARDENING WRAPPER: no checks possible, aborting # ' # Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong --ignore-arch-flag mipsel:-Werror=format-security (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # CFLAGS missing (-O2): gcc -g -fstack-protector-strong -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -c test-c.c # ' # Failed test './t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" --ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output)' # at t/tests.t line 45. # got: 'Use of uninitialized value $os in pattern match (m//) at ./bin/blhc line 1194. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1198. # Use of uninitialized value $cpu in pattern match (m//) at ./bin/blhc line 1202. [...] # Looks like you failed 5 tests of 246. t/tests.t .. 1..246 [...] not ok 14 - ./t/logs/arch-avr32 --color (output) [...] not ok 164 - ./t/logs/arch-avr32 (output) [...] not ok 242 - ./t/logs/bad-ldflags ./t/logs/empty ./t/logs/arch-avr32 ./t/logs/debian-hardening-wrapper (output) [...] not ok 244 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-flag --ignore-arch-flag i386:-fstack-protector-strong --ignore-arch-flag mipsel:-Werror=format-security (output) [...] not ok 246 - ./t/logs/arch-i386 ./t/logs/arch-amd64 ./t/logs/arch-avr32 ./t/logs/ignore-line --ignore-arch-line "i386:gcc .+ -fPIE .+" --ignore-arch-line "mipsel:gcc .+ -Wl,-z,relro -Wl,-z,now .+" (output) Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/246 subtests Test Summary Report --- t/tests.t (Wstat: 1280 (exited 5) Tests: 246 Failed: 5) Failed tests: 14, 164, 242, 244, 246 Non-zero exit status: 5 Files=1, Tests=246, 3 wallclock secs ( 0.02 usr 0.00 sys + 2.46 cusr 0.37 csys = 2.85 CPU) Result: FAIL Failed 1/1 test programs. 5/246 subtests failed. Regards, Eriberto -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_
Bug#1051847: marked as done (iproute2 ships configuration files in /usr/lib violating debian-policy)
Your message dated Wed, 13 Sep 2023 16:17:40 +0200 with message-id <20230913141740.kjzxnvh2mc7zd...@shell.thinkmo.de> and subject line Re: Bug#1051847: iproute2 ships configuration files in /usr/lib violating debian-policy has caused the Debian Bug report #1051847, regarding iproute2 ships configuration files in /usr/lib violating debian-policy 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.) -- 1051847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iproute2 Version: 6.1.0-3 Severity: serious Justification: Policy 10.7.2 X-Debbugs-Cc: d...@darkboxed.org Dear Maintainer, your iproute2 6.5.0-3 package installs configuration files in /usr/lib/iproute2. This is a blatant violation of debian-policy section 10.7.2. "Configuration files / Location" which states as follows: > Any configuration files created or used by your package must reside > in /etc. If there are several, consider creating a subdirectory of > /etc named after your package. As I've mentioned in Bug#1051577 this is related to upstream commit commit 0a0a8f12fa1b03dd0ccbebf5f85209d1c8a0f580 Read configuration files from /etc and /usr Add support for the so called "stateless" configuration pattern (read from /etc, fall back to /usr), giving system administrators a way to define local configuration without changing any distro-provided files. In practice this means that each configuration file FOO is loaded from /usr/lib/iproute2/FOO unless /etc/iproute2/FOO exists. but moving the config files from /etc/iproute to /usr/lib is misguided and should be overriden in your Debian package. Thanks, --Daniel --- End Message --- --- Begin Message --- Hi Daniel On Wed, Sep 13, 2023 at 04:11:16PM +0200, Daniel Gröber wrote: > your iproute2 6.5.0-3 package installs configuration files in > /usr/lib/iproute2. This is a blatant violation of debian-policy > section 10.7.2. "Configuration files / Location" which states as > follows: No, it does not. The files in /usr are defaults. Those should be copied to /etc for modification, which is config. Bastian -- No problem is insoluble. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4--- End Message ---
Processed: Re: Bug#1051435: fixed in python-hypothesis 6.84.3-1
Processing control commands:
> reopen -1
Bug #1051435 {Done: Timo Röhling }
[src:python-pytest-asyncio] python-pytest-asyncio: failing autopkgtest
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-hypothesis/6.84.3-1.
> severity -1 serious
Bug #1051435 [src:python-pytest-asyncio] python-pytest-asyncio: failing
autopkgtest
Severity set to 'serious' from 'important'
--
1051435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051847: iproute2 ships configuration files in /usr/lib violating debian-policy
Package: iproute2 Version: 6.1.0-3 Severity: serious Justification: Policy 10.7.2 X-Debbugs-Cc: d...@darkboxed.org Dear Maintainer, your iproute2 6.5.0-3 package installs configuration files in /usr/lib/iproute2. This is a blatant violation of debian-policy section 10.7.2. "Configuration files / Location" which states as follows: > Any configuration files created or used by your package must reside > in /etc. If there are several, consider creating a subdirectory of > /etc named after your package. As I've mentioned in Bug#1051577 this is related to upstream commit commit 0a0a8f12fa1b03dd0ccbebf5f85209d1c8a0f580 Read configuration files from /etc and /usr Add support for the so called "stateless" configuration pattern (read from /etc, fall back to /usr), giving system administrators a way to define local configuration without changing any distro-provided files. In practice this means that each configuration file FOO is loaded from /usr/lib/iproute2/FOO unless /etc/iproute2/FOO exists. but moving the config files from /etc/iproute to /usr/lib is misguided and should be overriden in your Debian package. Thanks, --Daniel
Bug#1025825: ImportError: cannot import name 'safe_join' from 'flask'
The following patch should fix the problem. renzo diff -Naur grip-4.2.0/debian/control grip-4.2.0.fixed/debian/control --- grip-4.2.0/debian/control 2016-07-03 23:21:52.0 +0200 +++ grip-4.2.0.fixed/debian/control 2023-09-13 15:20:13.527645376 +0200 @@ -12,6 +12,7 @@ python3-requests, python3-responses (>= 0.5.0), python3-setuptools + python3-werkzeug Build-Depends-Indep: txt2man Standards-Version: 3.9.8 Testsuite: autopkgtest diff -Naur grip-4.2.0/grip/assets.py grip-4.2.0.fixed/grip/assets.py --- grip-4.2.0/grip/assets.py 2016-04-16 17:51:39.0 +0200 +++ grip-4.2.0.fixed/grip/assets.py 2023-09-13 15:20:59.344112922 +0200 @@ -13,7 +13,7 @@ from urllib.parse import urljoin import requests -from flask import safe_join +from werkzeug.utils import safe_join from .constants import ( STYLE_URLS_SOURCE, STYLE_URLS_RE, STYLE_ASSET_URLS_RE, diff -Naur grip-4.2.0/grip/readers.py grip-4.2.0.fixed/grip/readers.py --- grip-4.2.0/grip/readers.py 2016-04-16 17:51:39.0 +0200 +++ grip-4.2.0.fixed/grip/readers.py2023-09-13 15:21:13.596250094 +0200 @@ -8,7 +8,7 @@ import sys from abc import ABCMeta, abstractmethod -from flask import safe_join +from werkzeug.utils import safe_join from .constants import DEFAULT_FILENAMES, DEFAULT_FILENAME from .exceptions import ReadmeNotFoundError
Processed: Re: Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Processing control commands: > tags -1 + moreinfo Bug #1051822 [chrony] installed chrony package post-installation script subprocess returned error exit status 1 Added tag(s) moreinfo. -- 1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Processing control commands: > tags -1 + moreinfo Bug #1051822 [chrony] installed chrony package post-installation script subprocess returned error exit status 1 Ignoring request to alter tags of bug #1051822 to the same tags previously set -- 1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051822: installed chrony package post-installation script subprocess returned error exit status 1
Control: tags -1 + moreinfo Hi Anibal, Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit : > Package: chrony > Version: 4.2-2 > Severity: critical > > # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb > (Reading database ... 34682 files and directories currently installed.) > Preparing to unpack .../archives/chrony_4.4-1_i386.deb ... > Failed to stop chronyd-restricted.service: Unit chronyd-restricted.service > not loaded. > Unpacking chrony (4.4-1) over (4.3-4) ... > Setting up chrony (4.4-1) ... > Unknown option: comment > adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] > [--firstuid ID] [--lastuid ID] [--gecos GECOS] [--ingroup GROUP | --gid ID] > [--disabled-password] [--disabled-login] [--add_extra_groups] USER >Add a normal user > > adduser --system [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID] > [--gecos GECOS] [--group | --ingroup GROUP | --gid ID] [--disabled-password] > [--disabled-login] [--add_extra_groups] USER >Add a system user > > adduser --group [--gid ID] GROUP > addgroup [--gid ID] GROUP >Add a user group > > addgroup --system [--gid ID] GROUP >Add a system group > > adduser USER GROUP >Add an existing user to an existing group > > general options: > --quiet | -q don't give process information to stdout > --force-badname allow usernames which do not match the > NAME_REGEX configuration variable > --help | -h usage message > --version | -vversion number and copyright > --conf | -c FILE use FILE as configuration file > > dpkg: error processing package chrony (--install): > installed chrony package post-installation script subprocess returned error > exit status 1 > Processing triggers for man-db (2.11.2-3) ... > Errors were encountered while processing: > chrony I don't seem to be able to reproduce this issue. Could you please give me more information on the system on which you were upgrading chrony? It seems you were upgrading from chrony 4.3-4, so I guess this system is running testing/unstable‽ Cheers, Vincent signature.asc Description: PGP signature
Bug#1042181: marked as done (trantor: FTBFS: MsgBuffer.h:77:5: error: ‘uint8_t’ does not name a type)
Your message dated Wed, 13 Sep 2023 12:04:22 + with message-id and subject line Bug#1042181: fixed in trantor 1.5.12+ds-1 has caused the Debian Bug report #1042181, regarding trantor: FTBFS: MsgBuffer.h:77:5: error: ‘uint8_t’ does not name a type 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.) -- 1042181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trantor Version: 1.5.11+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -Dtrantor_EXPORTS -I/<> > -I/<>/obj-x86_64-linux-gnu/exports > -I/<>/trantor/utils -I/<>/trantor/net > -I/<>/trantor/net/inner -I/<>/third_party/wepoll -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -fPIC > -Wall -Wextra -Werror -MD -MT > CMakeFiles/trantor.dir/trantor/utils/TimingWheel.cc.o -MF > CMakeFiles/trantor.dir/trantor/utils/TimingWheel.cc.o.d -o > CMakeFiles/trantor.dir/trantor/utils/TimingWheel.cc.o -c > /<>/trantor/utils/TimingWheel.cc > In file included from /<>/trantor/utils/MsgBuffer.cc:15: > /<>/trantor/utils/MsgBuffer.h:77:5: error: ‘uint8_t’ does not > name a type >77 | uint8_t peekInt8() const > | ^~~ > /<>/trantor/utils/MsgBuffer.h:24:1: note: ‘uint8_t’ is defined > in header ‘’; did you forget to ‘#include ’? >23 | #include > +++ |+#include >24 | #ifdef _WIN32 > /<>/trantor/utils/MsgBuffer.h:88:5: error: ‘uint16_t’ does not > name a type >88 | uint16_t peekInt16() const; > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:88:5: note: ‘uint16_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:95:5: error: ‘uint32_t’ does not > name a type >95 | uint32_t peekInt32() const; > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:95:5: note: ‘uint32_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:102:5: error: ‘uint64_t’ does not > name a type > 102 | uint64_t peekInt64() const; > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:102:5: note: ‘uint64_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:117:5: error: ‘uint8_t’ does not > name a type > 117 | uint8_t readInt8(); > | ^~~ > /<>/trantor/utils/MsgBuffer.h:117:5: note: ‘uint8_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:124:5: error: ‘uint16_t’ does not > name a type > 124 | uint16_t readInt16(); > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:124:5: note: ‘uint16_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:131:5: error: ‘uint32_t’ does not > name a type > 131 | uint32_t readInt32(); > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:131:5: note: ‘uint32_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:138:5: error: ‘uint64_t’ does not > name a type > 138 | uint64_t readInt64(); > | ^~~~ > /<>/trantor/utils/MsgBuffer.h:138:5: note: ‘uint64_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:189:27: error: ‘uint8_t’ does not > name a type > 189 | void appendInt8(const uint8_t b) > | ^~~ > /<>/trantor/utils/MsgBuffer.h:189:27: note: ‘uint8_t’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:199:28: error: ‘uint16_t’ does not > name a type > 199 | void appendInt16(const uint16_t s); > |^~~~ > /<>/trantor/utils/MsgBuffer.h:199:28: note: ‘uint16_t’ is > defined in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:206:28: error: ‘uint32_t’ does not > name a type > 206 | void appendInt32(const uint32_t i); > |^~~~ > /<>/trantor/utils/MsgBuffer.h:206:28: note: ‘uint32_t’ is > defined in header ‘’; did you forget to ‘#include ’? > /<>/trantor/utils/MsgBuffer.h:213:28: error: ‘uint64_t’ does not > name a type > 213 | void appendInt64(const uint64_t l); > |^~~~ > /<>/trantor/utils/MsgBuffer.h:213:28: note: ‘uint64_t’ is > defined in header ‘’; did y
Bug#1050942: FTBFS: Failed 1/1 test programs. 5/246 subtests failed.
Em qua., 13 de set. de 2023 às 03:12, Simon Ruderich escreveu: > > Hi Eriberto, > > should be fixed in fb2c46d [2]. > > Best, > Simon > > [2]: > https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=fb2c46d23c6052c714729d70d33d54011374689b Thanks Simon! Have a nice day.
Processed: found 1051822 4.4-1 notfound 1051822 4.2-2
Processing commands for cont...@bugs.debian.org: > found 1051822 4.4-1 Bug #1051822 [chrony] installed chrony package post-installation script subprocess returned error exit status 1 Marked as found in versions chrony/4.4-1. > notfound 1051822 4.2-2 Bug #1051822 [chrony] installed chrony package post-installation script subprocess returned error exit status 1 No longer marked as found in versions chrony/4.2-2. > stop Stopping processing here. Please contact me if you need assistance. -- 1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): alex4-data: unknown assets license
Processing control commands: > severity -1 serious Bug #1035043 [alex4-data] alex4-data: please request assets be explictly licensed Severity set to 'serious' from 'important' > justification -1 Policy 2.2.1 Unknown command or malformed arguments to command. -- 1035043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051815: marked as done (Builds invalid wasm32 binaries (1.67->1.68 regression))
Your message dated Wed, 13 Sep 2023 09:13:06 + with message-id and subject line Bug#1051815: fixed in wasi-libc 0.0~git20230113.4362b18-2 has caused the Debian Bug report #1051815, regarding Builds invalid wasm32 binaries (1.67->1.68 regression) 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.) -- 1051815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wasmedge Version: 0.13.3+dfsg-1 Severity:serious The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37793933/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37778163/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/37770138/log.gz 93s autopkgtest [14:54:23]: test capi-wasi-env: [--- 93s 1..2 94s ok 1 build wasi_get_env.wasm with cargo/rustc 94s not ok 2 build set_wasm_env with gcc 94s # (in test file debian/tests/capi-wasi-env, line 24) 94s # `assert_output --partial "ENV1: VAL1"' failed 94s # 94s # -- output does not contain substring -- 94s # substring (1 lines): 94s # ENV1: VAL1 94s # output (4 lines): 94s # [2023-09-12 14:54:24.910] [error] execution failed: unreachable, Code: 0x89 94s # [2023-09-12 14:54:24.910] [error] In instruction: unreachable (0x00) , Bytecode offset: 0x9efb 94s # [2023-09-12 14:54:24.910] [error] When executing function name: "print_env" 94s # Execution Failed. Error message: unreachable 94s # -- 94s # 95s autopkgtest [14:54:25]: test capi-wasi-env: ---] 95s autopkgtest [14:54:25]: test capi-wasi-env: - - - - - - - - - - results - - - - - - - - - - 95s capi-wasi-envFAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: wasi-libc Source-Version: 0.0~git20230113.4362b18-2 Done: Fabian Grünbichler We believe that the bug you reported is fixed in the latest version of wasi-libc, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Grünbichler (supplier of updated wasi-libc 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, 13 Sep 2023 08:19:24 +0200 Source: wasi-libc Architecture: source Version: 0.0~git20230113.4362b18-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Fabian Grünbichler Closes: 1051815 Changes: wasi-libc (0.0~git20230113.4362b18-2) unstable; urgency=medium . * Revert "build: enable stack protection" (Closes: #1051815) Checksums-Sha1: 84f97c8c96134ca93997d7908ebc1b4122f35f87 2174 wasi-libc_0.0~git20230113.4362b18-2.dsc 2fbf7564f3ba218e4537a493155330da4cfb26f9 7336 wasi-libc_0.0~git20230113.4362b18-2.debian.tar.xz e8baab69a3012ad29510770a42005a4f3153959c 6742 wasi-libc_0.0~git20230113.4362b18-2_source.buildinfo Checksums-Sha256: 99472f842c59639be0b6d49950e4ddabf8d7a857e9b1c827d92fd0c75feb20f6 2174 wasi-libc_0.0~git20230113.4362b18-2.dsc b140317084fa1e5d448799ebd946bd53ebff4da40eecdb1b92bcc6a2fd4f20ac 7336 wasi-libc_0.0~git20230113.4362b18-2.debian.tar.xz f2fdce555638786af5cc2c26087bfb9085cc867bf2203ff451ae0b3e2c0ac8b9 6742 wasi-libc_0.0~git20230113.4362b18-2_source.buildinfo Files: da3f778f5a9684ec2e101e70dd94a080 2174 devel optional wasi-libc_0.0~git20230113.4362b18-2.dsc 401f6b91cb14efd25ba841e6a7ef9159 7336 devel optional wasi-libc_0.0~git20230113.4362b18-2.debian.tar.xz c32cf4d64873854d6e78c8d61129939d 6742 devel optional wasi-libc_0.0~git20230113.4362b18-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJVBAEBCgA/FiEEbdkGe7ToK0Amc9ppdh5TKjcTRTAFAmUBcokhHGRlYmlhbkBm YWJpYW4uZ3J1ZW5iaWNobGVyLmVtYWlsAAoJEHYeUyo3E0Uw/2cP/3Xe5Z8vv1WR zSF3Xa8SV2m6ENj8ZYt5VfpHKtfGWITO6SrcI7fQvYmKxB+40kqezURtx+Algs0o g0K4Tly9JafvtbEtLOBaLky41V9HUVfLPIdl2laol+WS3pLvkcM4fWFkRpag8kOm ct12y8mHq9lZE0pjuw7KAu60CGfs5CyruxaU+zfycusxR2YoOD1Bi574pWc/u9ay acSSOUOdCkAZVvdw
Bug#1051815: marked as done (Builds invalid wasm32 binaries (1.67->1.68 regression))
Your message dated Wed, 13 Sep 2023 09:12:40 + with message-id and subject line Bug#1051815: fixed in rustc 1.69.0+dfsg1-1~exp2 has caused the Debian Bug report #1051815, regarding Builds invalid wasm32 binaries (1.67->1.68 regression) 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.) -- 1051815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wasmedge Version: 0.13.3+dfsg-1 Severity:serious The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37793933/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37778163/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/37770138/log.gz 93s autopkgtest [14:54:23]: test capi-wasi-env: [--- 93s 1..2 94s ok 1 build wasi_get_env.wasm with cargo/rustc 94s not ok 2 build set_wasm_env with gcc 94s # (in test file debian/tests/capi-wasi-env, line 24) 94s # `assert_output --partial "ENV1: VAL1"' failed 94s # 94s # -- output does not contain substring -- 94s # substring (1 lines): 94s # ENV1: VAL1 94s # output (4 lines): 94s # [2023-09-12 14:54:24.910] [error] execution failed: unreachable, Code: 0x89 94s # [2023-09-12 14:54:24.910] [error] In instruction: unreachable (0x00) , Bytecode offset: 0x9efb 94s # [2023-09-12 14:54:24.910] [error] When executing function name: "print_env" 94s # Execution Failed. Error message: unreachable 94s # -- 94s # 95s autopkgtest [14:54:25]: test capi-wasi-env: ---] 95s autopkgtest [14:54:25]: test capi-wasi-env: - - - - - - - - - - results - - - - - - - - - - 95s capi-wasi-envFAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: rustc Source-Version: 1.69.0+dfsg1-1~exp2 Done: Fabian Grünbichler We believe that the bug you reported is fixed in the latest version of rustc, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Grünbichler (supplier of updated rustc 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, 13 Sep 2023 08:02:53 +0200 Source: rustc Architecture: source Version: 1.69.0+dfsg1-1~exp2 Distribution: experimental Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Fabian Grünbichler Closes: 1051815 Changes: rustc (1.69.0+dfsg1-1~exp2) experimental; urgency=medium . * config: also enable rustdoc explicitly * bump wasi-libc to revert stack protection (Closes: #1051815) Checksums-Sha1: 4631ed4571f74386eeed7048a797bd1ef66a20de 3612 rustc_1.69.0+dfsg1-1~exp2.dsc 4802fc8088054b3f873a8fb16fcb828447342efe 97852 rustc_1.69.0+dfsg1-1~exp2.debian.tar.xz 17bffc1bf8791d1d8b549c0b04426ec15818fbb3 9020 rustc_1.69.0+dfsg1-1~exp2_source.buildinfo Checksums-Sha256: 0434077a4a3d9b990e928b4c731a2b089c2aea38c2351f21e00914b52df4e553 3612 rustc_1.69.0+dfsg1-1~exp2.dsc 9b8b0148cf5088f2b4599c6b5d40736e13fb93617c2e5f60fa9af44e6d099a0a 97852 rustc_1.69.0+dfsg1-1~exp2.debian.tar.xz c9b05470768dbfaa56a232bb328e41f6185b3b0d3a9445d52fc639459478571f 9020 rustc_1.69.0+dfsg1-1~exp2_source.buildinfo Files: fe224183d69f1bb70118cabe173ce528 3612 devel optional rustc_1.69.0+dfsg1-1~exp2.dsc 6f31fae94b0db4773354068403710c4a 97852 devel optional rustc_1.69.0+dfsg1-1~exp2.debian.tar.xz e1c2fc55d1ec25a7ba32b8ce9ebf8eb6 9020 devel optional rustc_1.69.0+dfsg1-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQJVBAEBCgA/FiEEbdkGe7ToK0Amc9ppdh5TKjcTRTAFAmUBc0ghHGRlYmlhbkBm YWJpYW4uZ3J1ZW5iaWNobGVyLmVtYWlsAAoJEHYeUyo3E0UwfkEP/i/dzUk27lzC MBumybqchlkzyeGnVC0TrE//eIqWV6NYtT/d0VJpAZEzRclAf4fNsELlf/luTStl nqXRcj8bDXS4za4yWv6Xc0izKnHCNMK/rAHyZ1bLku+DxF1TrPXoT+6M2Qs82wjv Ffvs3+7QN3U4qltrA9TXQG/Oa0dKMGJiRUxJdp74gpKNxAnA6NOCXDYoQo8rkzoD VNWK/yciAkQH29KbYMReIZYWN6NO9e5EU0uFFUww4OUsB9TqPVSgaOmWEieAzsDH zqBW9UWF81tMrpIlceuo2NieA43EC7j19
Bug#1051090: marked as done (emacsql: FTBFS: 5 unexpected results)
Your message dated Wed, 13 Sep 2023 09:04:05 + with message-id and subject line Bug#1051090: fixed in emacsql 3.1.1+git20230417.6401226+ds-1 has caused the Debian Bug report #1051090, regarding emacsql: FTBFS: 5 unexpected results 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.) -- 1051090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emacsql Version: 3.1.1+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, emacsql fails to build from source with errors in the testsuite. From my build log on amd64: | Ran 24 tests, 19 results as expected, 5 unexpected (2023-09-01 08:04:24+, 0.351282 sec) | | 5 unexpected results: |FAILED emacsql-basic |FAILED emacsql-error |FAILED emacsql-foreign-key |FAILED emacsql-nul-character |FAILED emacsql-special-chars | | dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -L tests --eval "(unless (and (getenv \"AUTOPKGTEST_TMP\") (file-directory-p (getenv \"AUTOPKGTEST_TMP\"))) (setq emacsql-sqlite-executable (concat default-directory \"sqlite/emacsql-sqlite\")))" -l tests/emacsql-compiler-tests.el -l tests/emacsql-external-tests.el --eval \(ert-run-tests-batch-and-exit\) returned exit code 1 | make: *** [debian/rules:4: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 A full build log on riscv64 is also available: https://buildd.debian.org/status/fetch.php?pkg=emacsql&arch=riscv64&ver=3.1.1%2Bds-1&stamp=1693407418&raw=0 Regards Aurelien --- End Message --- --- Begin Message --- Source: emacsql Source-Version: 3.1.1+git20230417.6401226+ds-1 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of emacsql, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated emacsql 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, 13 Sep 2023 09:28:28 +0100 Source: emacsql Architecture: source Version: 3.1.1+git20230417.6401226+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Sean Whitton Closes: 1051090 Changes: emacsql (3.1.1+git20230417.6401226+ds-1) unstable; urgency=medium . [ Aymeric Agon-Rambosson ] * Update to new upstream version 3.1.1+git20230417.6401226+ds : needed to repair magit after release of emacs 1:29.1+1-1 (see https://github.com/magit/forge/issues/535) (Closes: #1051090). * Bump Standards-Version to 4.6.2 (no changes required). * d/control : update Homepage. * Specify dependencies manually between backends and high-level abstractions (discrepancy in version numbering format made backends unupgradeable). * Add new upstream files to d/elpa-emacsql-sqlite.elpa. * d/rules: add binary hardening options. Checksums-Sha1: 6d8924105d5a9a9b83699c069687e4996733aacd 2498 emacsql_3.1.1+git20230417.6401226+ds-1.dsc d000e191cadf92208043c0179d5be1aae77ac9ca 31992 emacsql_3.1.1+git20230417.6401226+ds.orig.tar.xz 975736b985988a26151ee75c2c05abb19fa5c3fc 5352 emacsql_3.1.1+git20230417.6401226+ds-1.debian.tar.xz Checksums-Sha256: bdfbe2c921301da75e17b4688df89cbf8a0b6e8ffd11624023da12332a872491 2498 emacsql_3.1.1+git20230417.6401226+ds-1.dsc da9832a21fe4d2f9fe58a9a96836632093c07995814ab9dde62731e167f7f5eb 31992 emacsql_3.1.1+git20230417.6401226+ds.orig.tar.xz f96249b56a0f430708ccdbb6f8e2589f466891e9c4b854658eca568794297491 5352 emacsql_3.1.1+git20230417.6401226+ds-1.debian.tar.xz Files: 4c2522b539fd69217e0544dcd46051ca 2498 editors optional emacsql_3.1.1+git20230417.6401226+ds-1.dsc 95b2bf7475193bed897dfb038c4a8e1f 31992 editors optional emacsql_3.1.1+git20230417.6401226+ds.orig.tar.xz 1c723a05d06b5d124f2ed19269efdf1f 5352
Bug#1051577: iproute2: obsolete conffiles
On Tue, 2023-09-12 at 23:13 +0200, Luca Boccassi wrote: > On Mon, 11 Sept 2023 at 15:57, Daniel Gröber > wrote: > > > > Hi Luca, > > > > On Mon, Sep 11, 2023 at 01:06:06PM +0100, Luca Boccassi wrote: > > > > I want to question whether removing these conffiles is a good idea at > > > > all. I'm probably one of the few people that actually muck around in > > > > there > > > > but it seems like this is going to break things for any users that do. > > > > > > As far as I understand dpkg's conffile machinery should recognize if > > > you changed anything, and leave it in place. Upstream moved the > > > default ones to /usr, so we just follow what they do. > > > > Right. Think of an admin having to adjust these config files though: > > previously they could just `editor /etc/iproute2/rt_tables` and get on with > > things. Now anyone needing to do that will have to do a doubletake, figure > > out why /etc/iproute2 is missing, realize that it's at /usr/lib/iproute2 > > now, copy that over and finally edit. > > > > Is that friction really warrented to cater to a specialized niche use-case? > > > > Please consider overriding upstream's decision here. > > Yes, it is warranted, both because it's exactly the correct behaviour > for a package, and also because we are certainly not spending time and > resources to go against upstream choices, especially when they are the > right choices. What is the plan for handling updates? AIUI we've lost the dpkg conffile handling but it doesn't look like it's been replaced by anything (e.g. like using ucf to prompt when an update happened perhaps?). Ian.
Processed: block 1050766 with 1051692
Processing commands for cont...@bugs.debian.org: > block 1050766 with 1051692 Bug #1050766 [src:classified-ads] classified-ads: FTBFS: /usr/include/natpmp.h:52:10: fatal error: natpmp_declspec.h: No such file or directory 1050766 was not blocked by any bugs. 1050766 was not blocking any bugs. Added blocking bug(s) of 1050766: 1051692 > thanks Stopping processing here. Please contact me if you need assistance. -- 1050766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034732: marked as done (Keep out of testing)
On Wed, Sep 13, 2023 at 4:04 PM Sebastian Ramacher wrote: > > Control: reopen -1 > > Hi, > > the bug was meant to keep the package out of testing as long as it is > not maintained. Unless you are volunteering to maintain it, this bug is > not fixed. > Yes, it's unfortunately auto-closed by the changelog... -- Shengjing Zhu
Processed: Re: Bug#1034732: marked as done (Keep out of testing)
Processing control commands:
> reopen -1
Bug #1034732 {Done: Shengjing Zhu } [gpac] Keep out of testing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gpac/2.2.1+dfsg1-2.
--
1034732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034732: marked as done (Keep out of testing)
Control: reopen -1 Hi, the bug was meant to keep the package out of testing as long as it is not maintained. Unless you are volunteering to maintain it, this bug is not fixed. Cheers On 2023-09-13 07:51:07 +, Debian Bug Tracking System wrote: > Your message dated Wed, 13 Sep 2023 07:49:09 + > with message-id > and subject line Bug#1034732: fixed in gpac 2.2.1+dfsg1-2 > has caused the Debian Bug report #1034732, > regarding Keep out of testing > 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.) > > > -- > 1034732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034732 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Sat, 22 Apr 2023 23:25:11 +0200 > From: Moritz Muehlenhoff > To: Debian Bug Tracking System > Subject: Keep out of testing > Message-ID: > <168219871136.7375.537807055272067203.reportbug@hullmann.westfalen.local> > > Package: gpac > Version: 2.0.0+dfsg1-2+b1 > Severity: serious > > In some discussion between Reinhard, Sebastian and the Security team we've > come to the > conclusion that gpac isn't suitable to be included in a stable release. The > massive > influx of security issues makes that untenable (and there's no suitable LTS > branch > we could use, which e.g. makes ffmpeg manageable). > > Sebastian has already updated x264 to no longer depend on it, when x264 > 2:0.164.3095+gitbaee400-3 has reached testing, gpac can be dropped. The only > other rdep in ccextractor, which is already out of testing due to a lack of > support for ffmpeg 5. > > Cheers, > Moritz > Date: Wed, 13 Sep 2023 07:49:09 + > From: Debian FTP Masters > To: 1034732-cl...@bugs.debian.org > Subject: Bug#1034732: fixed in gpac 2.2.1+dfsg1-2 > Reply-To: Shengjing Zhu > Message-Id: > -- Sebastian Ramacher
Bug#1034732: marked as done (Keep out of testing)
Your message dated Wed, 13 Sep 2023 07:49:09 + with message-id and subject line Bug#1034732: fixed in gpac 2.2.1+dfsg1-2 has caused the Debian Bug report #1034732, regarding Keep out of testing 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.) -- 1034732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpac Version: 2.0.0+dfsg1-2+b1 Severity: serious In some discussion between Reinhard, Sebastian and the Security team we've come to the conclusion that gpac isn't suitable to be included in a stable release. The massive influx of security issues makes that untenable (and there's no suitable LTS branch we could use, which e.g. makes ffmpeg manageable). Sebastian has already updated x264 to no longer depend on it, when x264 2:0.164.3095+gitbaee400-3 has reached testing, gpac can be dropped. The only other rdep in ccextractor, which is already out of testing due to a lack of support for ffmpeg 5. Cheers, Moritz --- End Message --- --- Begin Message --- Source: gpac Source-Version: 2.2.1+dfsg1-2 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of gpac, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated gpac 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, 13 Sep 2023 14:56:05 +0800 Source: gpac Architecture: source Version: 2.2.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Shengjing Zhu Closes: 1033116 1034187 1034732 1034890 1036701 1041380 Changes: gpac (2.2.1+dfsg1-2) unstable; urgency=medium . * QA upload. * Set maintainer to Debian QA Group (See #1038784) * Upload to unstable. * Backport patch to build with ffmpeg 6.0 (Closes: #1041380) . gpac (2.2.1+dfsg1-1) experimental; urgency=medium . * New upstream version, closes: #1033116, #1034732, #1034187, #1036701, #1034890 * soname bump libgpac11 -> libgpac12 Checksums-Sha1: 515d078cd5d15d313aee64dbd9f4e67cf8f3cef7 1792 gpac_2.2.1+dfsg1-2.dsc 9d039fa233084402316bd9cb408c07e638b9e1d0 37648 gpac_2.2.1+dfsg1-2.debian.tar.xz 701e4931c4284d79759357714aec8292f05c1236 5325 gpac_2.2.1+dfsg1-2_source.buildinfo Checksums-Sha256: fec96c4cc0e5b24291bd9c057959f945bd70f3eff64e19059cebee6f4c71b5cc 1792 gpac_2.2.1+dfsg1-2.dsc af3728f8e7f919a92f63013a2b8c77143202f68d2320fb1c3bede45696cb133b 37648 gpac_2.2.1+dfsg1-2.debian.tar.xz e1f7d5b34b614d5575a1935c714b3deef8e6a3f752888a5e1e793d13c0e842fd 5325 gpac_2.2.1+dfsg1-2_source.buildinfo Files: 97d4a6d4b6b9495e9d629076fdc3f00a 1792 graphics optional gpac_2.2.1+dfsg1-2.dsc 59c4c28301588d18b2772b4d7d2c01d1 37648 graphics optional gpac_2.2.1+dfsg1-2.debian.tar.xz 13e61d51c866f3a27f2b029ed6e9b2b4 5325 graphics optional gpac_2.2.1+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCZQFiHAAKCRB/RPol6lUU y1LPAP46U6+EIJ9QVlkB7/alzOVjS8rwJtv3AXCP8hiN1MQmzwD/eA+xNfWYmjYC ttFLF72wb/NNs+Jvc+UX71Z/j73NJwQ= =4Rgn -END PGP SIGNATURE End Message ---
Bug#1033116: marked as done (gpac: CVE-2022-3222 CVE-2023-0866 CVE-2022-4202 CVE-2022-43039 CVE-2023-23143 CVE-2023-23144 CVE-2023-23145 CVE-2022-43040 CVE-2022-43042 CVE-2022-43043 CVE-2022-43044 CVE
Your message dated Wed, 13 Sep 2023 07:49:09 + with message-id and subject line Bug#1033116: fixed in gpac 2.2.1+dfsg1-2 has caused the Debian Bug report #1033116, regarding gpac: CVE-2022-3222 CVE-2023-0866 CVE-2022-4202 CVE-2022-43039 CVE-2023-23143 CVE-2023-23144 CVE-2023-23145 CVE-2022-43040 CVE-2022-43042 CVE-2022-43043 CVE-2022-43044 CVE-2022-43045 CVE-2022-45202 CVE-2022-45283 CVE-2022-45343 CVE-2022-46489 CVE-2022-46490 CVE-2022-47086 CVE-2022-47087 CVE-2022-47088 CVE-2022-47089 CVE-2022-47091 CVE-2022-47092 CVE-2022-47093 CVE-2022-47094 CVE-2022-47095 CVE-2022-47653 CVE-2022-47654 CVE-2022-47656 CVE-2022-47657 CVE-2022-47658 CVE-2022-47659 CVE-2022-47660 CVE-2022-47661 CVE-2022-47662 CVE-2022-47663 CVE-2023-0358 CVE-2023-0760 CVE-2023-0770 CVE-2023-0817 CVE-2023-0818 CVE-2023-0819 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.) -- 1033116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpac X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for gpac. CVE-2022-3222[0]: | Uncontrolled Recursion in GitHub repository gpac/gpac prior to | 2.1.0-DEV. https://huntr.dev/bounties/b29c69fa-3eac-41e4-9d4f-d861aba18235/ https://github.com/gpac/gpac/commit/4e7736d7ec7bf64026daa611da951993bb42fdaf CVE-2023-0866[2]: | Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to | 2.3.0-DEV. https://huntr.dev/bounties/7d3c5792-d20b-4cb6-9c6d-bb14f3430d7f https://github.com/gpac/gpac/commit/b964fe4226f1424cf676d5822ef898b6b01f5937 CVE-2022-4202[3]: | A vulnerability, which was classified as problematic, was found in | GPAC 2.1-DEV-rev490-g68064e101-master. Affected is the function | lsr_translate_coords of the file laser/lsr_dec.c. The manipulation | leads to integer overflow. It is possible to launch the attack | remotely. The exploit has been disclosed to the public and may be | used. The name of the patch is | b3d821c4ae9ba62b3a194d9dcb5e99f17bd56908. It is recommended to apply a | patch to fix this issue. VDB-214518 is the identifier assigned to this | vulnerability. https://github.com/gpac/gpac/issues/2333 https://github.com/gpac/gpac/commit/b3d821c4ae9ba62b3a194d9dcb5e99f17bd56908 CVE-2022-43039[4]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_isom_meta_restore_items_ref | at /isomedia/meta.c. https://github.com/gpac/gpac/issues/2281 https://github.com/gpac/gpac/commit/62dbd5caad6b89b33535dfa19ef65419f0378303 CVE-2023-23143[5]: | Buffer overflow vulnerability in function avc_parse_slice in file | media_tools/av_parsers.c. GPAC version 2.3-DEV-rev1-g4669ba229-master. https://github.com/gpac/gpac/commit/af6a5e7a96ee01a139cce6c9e4edfc069aad17a6 CVE-2023-23144[6]: | Integer overflow vulnerability in function Q_DecCoordOnUnitSphere file | bifs/unquantize.c in GPAC version 2.2-rev0-gab012bbfb-master. https://github.com/gpac/gpac/commit/3a2458a49b3e6399709d456d7b35e7a6f50cfb86 CVE-2023-23145[7]: | GPAC version 2.2-rev0-gab012bbfb-master was discovered to contain a | memory leak in lsr_read_rare_full function. https://github.com/gpac/gpac/commit/4ade98128cbc41d5115b97a41ca2e59529c8dd5f CVE-2022-43040[8]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a heap | buffer overflow via the function gf_isom_box_dump_start_ex at | /isomedia/box_funcs.c. https://github.com/gpac/gpac/issues/2280 https://github.com/gpac/gpac/commit/f17dae31ebf6ea7af8c512165d9b954c2a6ea46e CVE-2022-43042[9]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a heap | buffer overflow via the function FixSDTPInTRAF at | isomedia/isom_intern.c. https://github.com/gpac/gpac/issues/2278 https://github.com/gpac/gpac/commit/3661da280b3eba75490e75ff20ad440c66e24de9 CVE-2022-43043[10]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function BD_CheckSFTimeOffset at | /bifs/field_decode.c. https://github.com/gpac/gpac/issues/2276 https://github.com/gpac/gpac/commit/6bff06cdb8e9b4e8ed2e789ee9340877759536fd CVE-2022-43044[11]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_isom_get_meta_item_info at | /isomedia/meta.c. https://github.com/gpac/gpac/issues/2282 https://github.com/gpac/gpac/commit/8a0e8e4ab13348cb1ab8e93b950a03d93f158a35 CVE-2022-43045[12]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation v
Bug#1051828: pytorch: needs-root for autopkgtests?
Source: pytorch Version: 2.0.1+dfsg-2 Severity: serious Hello, I just found this failure on Ubuntu builders. 5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any: cd debian/tests ; find /usr -xtype l -print 5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any: [--- 5393s find: ‘/usr/share/polkit-1/rules.d’: Permission denied 5396s /usr/share/doc/openssl/changelog.gz 5396s /usr/share/doc/perl/Changes.gz 5396s /usr/share/doc/python3-keyring/NEWS.rst.gz 5396s /usr/share/doc/libucx0/README 5396s /usr/share/doc/libhdf5-103-1/RELEASE.txt.gz 5396s /usr/share/doc/libhdf5-hl-100/RELEASE.txt.gz 5396s /usr/share/doc/xfsprogs/changelog.gz 5396s /usr/share/doc/python3-wadllib/NEWS.rst.gz 5396s /usr/share/doc/libxml2/NEWS.gz 5396s /usr/share/locale/cs/LC_TIME/coreutils.mo 5396s /usr/share/locale/zh_TW/LC_TIME/coreutils.mo 5396s /usr/share/locale/eo/LC_TIME/coreutils.mo 5396s /usr/share/locale/tr/LC_TIME/coreutils.mo 5396s /usr/share/locale/fr/LC_TIME/coreutils.mo 5396s /usr/share/locale/eu/LC_TIME/coreutils.mo 5396s /usr/share/locale/da/LC_TIME/coreutils.mo 5396s /usr/share/locale/vi/LC_TIME/coreutils.mo 5396s /usr/share/locale/it/LC_TIME/coreutils.mo 5396s /usr/share/locale/fi/LC_TIME/coreutils.mo 5396s /usr/share/locale/lt/LC_TIME/coreutils.mo 5396s /usr/share/locale/nb/LC_TIME/coreutils.mo 5396s /usr/share/locale/el/LC_TIME/coreutils.mo 5396s /usr/share/locale/de/LC_TIME/coreutils.mo 5396s /usr/share/locale/hu/LC_TIME/coreutils.mo 5396s /usr/share/locale/ro/LC_TIME/coreutils.mo 5396s /usr/share/locale/es/LC_TIME/coreutils.mo 5396s /usr/share/locale/id/LC_TIME/coreutils.mo 5396s /usr/share/locale/et/LC_TIME/coreutils.mo 5396s /usr/share/locale/sl/LC_TIME/coreutils.mo 5396s /usr/share/locale/nl/LC_TIME/coreutils.mo 5396s /usr/share/locale/sr/LC_TIME/coreutils.mo 5396s /usr/share/locale/ga/LC_TIME/coreutils.mo 5396s /usr/share/locale/be/LC_TIME/coreutils.mo 5396s /usr/share/locale/kk/LC_TIME/coreutils.mo 5396s /usr/share/locale/pt_BR/LC_TIME/coreutils.mo 5396s /usr/share/locale/af/LC_TIME/coreutils.mo 5396s /usr/share/locale/uk/LC_TIME/coreutils.mo 5396s /usr/share/locale/ia/LC_TIME/coreutils.mo 5396s /usr/share/locale/gl/LC_TIME/coreutils.mo 5396s /usr/share/locale/pl/LC_TIME/coreutils.mo 5396s /usr/share/locale/ms/LC_TIME/coreutils.mo 5396s /usr/share/locale/ko/LC_TIME/coreutils.mo 5396s /usr/share/locale/lg/LC_TIME/coreutils.mo 5396s /usr/share/locale/bg/LC_TIME/coreutils.mo 5396s /usr/share/locale/sv/LC_TIME/coreutils.mo 5396s /usr/share/locale/ja/LC_TIME/coreutils.mo 5396s /usr/share/locale/hr/LC_TIME/coreutils.mo 5396s /usr/share/locale/pt/LC_TIME/coreutils.mo 5396s /usr/share/locale/ca/LC_TIME/coreutils.mo 5396s /usr/share/locale/sk/LC_TIME/coreutils.mo 5396s /usr/share/locale/zh_CN/LC_TIME/coreutils.mo 5396s /usr/share/locale/ru/LC_TIME/coreutils.mo 5396s /usr/src/linux-headers-6.5.0-5-generic/rust 5396s /usr/src/linux-headers-6.3.0-7-generic/rust 5396s /usr/lib/aarch64-linux-gnu/qt-default/qtchooser/default.conf 5396s autopkgtest [13:15:15]: test show_dangling_symlink_if_any: ---] 5397s autopkgtest [13:15:16]: test show_dangling_symlink_if_any: - - - - - - - - - - results - - - - - - - - - - 5397s show_dangling_symlink_if_any FAIL non-zero exit status 1 5397s autopkgtest [13:15:16]: test 1_of_98__cpptest__CppSignature_test: preparing testbed This permission denied looks making the test fail, I'm not sure if you want to just ignore the find error, or declare the test as need-root capability. G. OpenPGP_signature Description: OpenPGP digital signature
