Processed: bug 1032104 is forwarded to https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u https://lore.kernel.org/regressions/480932026.4
Processing commands for cont...@bugs.debian.org: > forwarded 1032104 > https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u > > https://lore.kernel.org/regressions/480932026.45576726.1699374859845.javamail.zim...@raptorengineeringinc.com/ > https://lore.kernel.org/all/2b015a34-220e-674e-7301-2cf17ef45...@kernel.dk/ Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read Changed Bug forwarded-to-address to 'https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u https://lore.kernel.org/regressions/480932026.45576726.1699374859845.javamail.zim...@raptorengineeringinc.com/ https://lore.kernel.org/all/2b015a34-220e-674e-7301-2cf17ef45...@kernel.dk/' from '! https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055729: marked as done (FTBFS: faad2 fails to build on i386, blocking DSA fix transition)
Your message dated Tue, 14 Nov 2023 07:49:07 + with message-id and subject line Bug#1055729: fixed in faad2 2.11.1-1 has caused the Debian Bug report #1055729, regarding FTBFS: faad2 fails to build on i386, blocking DSA fix transition 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.) -- 1055729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Severity: serious Package: faad2 Tags: patch upstream security fixed-upstream Please apply upstream fix https://github.com/knik0/faad2/commit/1001f9576cbb29242671c489cd861de61cfe08e2?diff=unified Kind regards, Sven --- End Message --- --- Begin Message --- Source: faad2 Source-Version: 2.11.1-1 Done: Fabian Greffrath We believe that the bug you reported is fixed in the latest version of faad2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath (supplier of updated faad2 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: Tue, 14 Nov 2023 08:32:47 +0100 Source: faad2 Architecture: source Version: 2.11.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Fabian Greffrath Closes: 1055729 Changes: faad2 (2.11.1-1) unstable; urgency=medium . * Add fixed CVE ids to previous debian/changelog entry. * New upstream version 2.11.1 + Check for lrintf() availability, link with -lm and define HAVE_LRINTF accordingly (Closes: #1055729). * Upstream installs the frontend manpage again, so do we. * Add "Build-Depends-Package: libfaad-dev" to libfaad_drm.so.2 symbols. * Bump Standards-Version to 4.6.2. * Bump Debian packaging copyright to 2023. Checksums-Sha1: 9c659a014642d5f18d7f09a3070249690f50f276 2111 faad2_2.11.1-1.dsc 72fed60d3970c35322294ca0f4527f01677aa696 657255 faad2_2.11.1.orig.tar.gz 85cbe70677c4bf3e088239dd45da26972499f4fe 8520 faad2_2.11.1-1.debian.tar.xz 5f4fb07f0b021ffca28dbe4461c03d6830a2b18f 7562 faad2_2.11.1-1_amd64.buildinfo Checksums-Sha256: 29a6b4d1ed73fcf48fb6d77e20f312aede16ede645c3ef72667fda1e59d08eaf 2111 faad2_2.11.1-1.dsc 72dbc0494de9ee38d240f670eccf2b10ef715fd0508c305532ca3def3225bb06 657255 faad2_2.11.1.orig.tar.gz b4159d9ec8af88f08d0bbf6bb5088ed25ed579692cfad8c459cc0b3891e917f2 8520 faad2_2.11.1-1.debian.tar.xz d069dd1ea4d342ab1392a65229c8af614647807ac75daa59ac806b262466b24e 7562 faad2_2.11.1-1_amd64.buildinfo Files: acf84f267daae89cf15d14bc8bb4cd66 2111 libs optional faad2_2.11.1-1.dsc f85b2514c4fb2f87d22a3bc879d83277 657255 libs optional faad2_2.11.1.orig.tar.gz 91b9314dd5c770674bd53db98d370c92 8520 libs optional faad2_2.11.1-1.debian.tar.xz ccefbb1dad707c49fbfdd54e175a27d9 7562 libs optional faad2_2.11.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmVTIxkSHGZhYmlhbkBk ZWJpYW4ub3JnAAoJEMvqjpcMzVnfUBQQALoxlsREqmTg2We3fGbVtBjYDQrIbwf2 O9gcs2+Ui/wP7Ek2RF+g4MCtqvX0A2SgGdS0Uug87ALXMvAPlh6OyIFmPu2Rh/xM HXTd4RYWlMyJzzNp3jSlmAEy/OSxPNu1kW9AWwFMfDNIPEkc5qJpTIX209Oj2oD3 VAMNkWf7tzAViJMxy83nB/x1/a6BcQw1AEJysWjw4S9HrrQ33wFLx/+n7XqWdmqL 6ZSwvnsS2x6ENXUdwbpJVrgisx7yfFjH7SctqmLUTGHVmTIaL0G10TWDWaHTKRrj bb0Q/WxwpMQcu3D7NGZnFgNZG55G6423rEgS5FDyvuLwFbHTHNWVhF/ARjxm5gCN shsiWXpD0J92iYiYXXk/Vw8yWZ34yRPMZBVUB4Im2qUPhwFET68EUxpwnpEXbMXA u8dxKMHmhz42HMKCMuOMgi52TuZjjB0emM/M+WMKg2gox6Gi/e46bcHUZaqgJLmE rV0tEhuUhP35Vzo/Fncd4PJ0Wnvg6dbuKftB3nckhEypEFTgAtnyYt0n3N9tWrU8 OAcmpenGz6174t7+6h/nWC1KgYntQCOwe8ipoU/4YJR6jCq8nmgrQRlnyHp47YJj UyEDmFw3fHVx/nZFopAST14EPTLeZUggJkNZM1jMn9wMibGCltvMSkIkRrlTs/KY GYh/OTrSPPJk =Ws9v -END PGP SIGNATURE End Message ---
Bug#1032104: Status update
I have traced this bug to a missing memory barrier in the powerpc IPI handling code. io_uring uses task_work_add() to schedule I/O worker creation, which in turn issues an IPI, and when precise timing conditions are met the inconsistent state between the two CPU cores can lead to corruption of userspace data in RAM. I have sent a patch upstream, and created a merge request for Debian here: https://salsa.debian.org/kernel-team/linux/-/merge_requests/907
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1032104 ! > https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read Changed Bug forwarded-to-address to '! https://lore.kernel.org/regressions/19221908.47168775.1699937769845.javamail.zim...@raptorengineeringinc.com/T/#u' from 'https://lore.kernel.org/regressions/480932026.45576726.1699374859845.javamail.zim...@raptorengineeringinc.com/ https://lore.kernel.org/all/2b015a34-220e-674e-7301-2cf17ef45...@kernel.dk/'. > tags 1032104 + patch Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055895: marked as done (rust-self-cell: RUSTSEC-2023-0070)
Your message dated Tue, 14 Nov 2023 04:04:15 + with message-id and subject line Bug#1055895: fixed in rust-self-cell 1.0.2-1 has caused the Debian Bug report #1055895, regarding rust-self-cell: RUSTSEC-2023-0070 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.) -- 1055895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-self-cell Version: 1.0.1-1 Tags: security upstream Justification: user security hole Forwarded: https://github.com/Voultapher/self_cell/issues/49 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi Please see https://rustsec.org/advisories/RUSTSEC-2023-0070.html Regards, Salvatore --- End Message --- --- Begin Message --- Source: rust-self-cell Source-Version: 1.0.2-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-self-cell, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-self-cell 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: Tue, 14 Nov 2023 02:59:23 + Source: rust-self-cell Architecture: source Version: 1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1055895 Changes: rust-self-cell (1.0.2-1) unstable; urgency=medium . * Team upload. * Package self_cell 1.0.2 from crates.io using debcargo 2.6.0 (Closes: #1055895) * Relax dev-dependency on once_cell, upstream restricted it for MSRV related reasons which are not applicable to Debian. Checksums-Sha1: 248beffb367644b486b907a27b735480de3a97b9 2191 rust-self-cell_1.0.2-1.dsc ecc2b4af4648d3afabbcfd72fa553971ffee6cb4 15097 rust-self-cell_1.0.2.orig.tar.gz 51b2e6039fad7ef05de899b2979a12fc86aeb8a1 2316 rust-self-cell_1.0.2-1.debian.tar.xz 37a02bafd2c66480006a742528b610e92604718b 7711 rust-self-cell_1.0.2-1_source.buildinfo Checksums-Sha256: 0147ba35021582d3bea84835919c0f0d3516b04faf50362f9a705937749c9e7b 2191 rust-self-cell_1.0.2-1.dsc e388332cd64eb80cd595a00941baf513caffae8dce9cfd0467fc9c66397dade6 15097 rust-self-cell_1.0.2.orig.tar.gz 413dcabf91db251c339a9af42e813170422e671a2d014bdba7a0900f20bdaa31 2316 rust-self-cell_1.0.2-1.debian.tar.xz 98d1d2574d1e8cddc73fd58c2f94eba73e82fddfcd042aeeb876bcbaccb2af91 7711 rust-self-cell_1.0.2-1_source.buildinfo Files: 44d1a06f2c4acca7043d799b1b0f273a 2191 rust optional rust-self-cell_1.0.2-1.dsc 60d7d6bc0241fd15def3a0ba6d45dafc 15097 rust optional rust-self-cell_1.0.2.orig.tar.gz c6dbe5228fc601865ba7302eebf5b03f 2316 rust optional rust-self-cell_1.0.2-1.debian.tar.xz d755e5eca773e7d2ca36280eadd3ffdd 7711 rust optional rust-self-cell_1.0.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmVS6ggUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvbHRAAgj1L6rWXbIdQBBBDNBSXMesLBgjt LyeXY+bR752RPKgw7XHk3QWu9RN/brY4WKG6jkuCwnIPVKiONlajUO8OVv2/KnH0 U+j8nlrRX/VkujdjRLk/M6AMSSu/2PqqFNBdwTIClD7+SGx3PIBE9DOX9YO3G+j0 5x1BKYTH20FrO0yYIQAfnR4z4LibfOe6Sp9ndGg0NkUBvGRWKs/9X+1R8YRU4rZo iXAZAA4pV8uxJSDrNi/xUVfIKL7c2/IiIcLa1qNq81HzOSgS1s3poKEppjoAhwTy UASI5GYMqdLo57MHosUd8q9NGphjB5n8H35Og/UDd0uVDXZNUdpoovgsdetZ8UI2 SptS95rSXsnb07wB4G877/EfI0Xtnfj3NZUSv8vigUdTUnNTDsoThzsi/aX60tvv JUInNXtu9gZLhxkSUxvUcGnaG5l2pUMSGrTNXjxCoI3gsbNnQOIK2Nspna26sbU1 LHfCLkq0ilp9e1FbbHZyChbut/H01G1ki6tDlLOixXuY31T45hO5yZBdrKIKNsQN 5vEWkJr6sYZzzzmUus23FZt01FXo5ySzEDZ5ufI9/lpz2ZzUQEBpKKR6CyPrxvFg oGv8mQhK+NWSrihdxw40ilNojWF460Eq9lpjdudkIbUH5R/kB/vMpHLtQ8U7gKlF RDxj25kn3st/r30= =W4An -END PGP SIGNATURE End Message ---
Bug#1055895: [Pkg-rust-maintainers] Bug#1055895: rust-self-cell: RUSTSEC-2023-0070
Please see https://rustsec.org/advisories/RUSTSEC-2023-0070.html I have read the upstream advisory and the linked bug report and while I don't fully understand the nitty gritty details my understanding of the issue is. * It was discovered that code (which was not marked as unsafe) could mis-use self-cell in a way that invoked undefined behaviour. * This was fixed by adding an additional compile time check which will cause the build to fail in such cases. Based on this understanding I have * Uploaded the new version of rust-self-cell * Performed a rebuild test of the only reverse dependency rust-coreutils, it built successfully, so presumably it is not impacted by this issue.
Bug#1055540: marked as done (obs-time-source: FTBFS on several archs: linker input file not found)
Your message dated Mon, 13 Nov 2023 23:04:09 + with message-id and subject line Bug#1055540: fixed in obs-time-source 0.2-2 has caused the Debian Bug report #1055540, regarding obs-time-source: FTBFS on several archs: linker input file not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: obs-time-source Version: 0.1-1 Severity: serious Tags: upstream ftbfs Justification: Fails to Build from Source X-Debbugs-Cc: ~krystianch/public-in...@lists.sr.ht The package fails to build from source on several architectures. An example for arm64: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v [1/2] cc -Itime-source.so.p -I. -I.. -I/usr/include/obs -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_OBSCONFIG_H -DSIMDE_ENABLE_OPENMP '$<$,$>:-fopenmp-simd>' '$<$,$>:-fopenmp-simd>' -MD -MQ time-source.so.p/time-source.c.o -MF time-source.so.p/time-source.c.o.d -o time-source.so.p/time-source.c.o -c ../time-source.c FAILED: time-source.so.p/time-source.c.o cc -Itime-source.so.p -I. -I.. -I/usr/include/obs -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_OBSCONFIG_H -DSIMDE_ENABLE_OPENMP '$<$,$>:-fopenmp-simd>' '$<$,$>:-fopenmp-simd>' -MD -MQ time-source.so.p/time-source.c.o -MF time-source.so.p/time-source.c.o.d -o time-source.so.p/time-source.c.o -c ../time-source.c ../time-source.c: In function ‘time_source_update’: ../time-source.c:95:9: warning: ‘__builtin_strncpy’ specified bound 64 equals destination size [-Wstringop-truncation] 95 | strncpy(context->format, obs_data_get_string(settings, "format"), | ^ cc: warning: $<$,$>:-fopenmp-simd>: linker input file unused because linking not done cc: error: $<$,$>:-fopenmp-simd>: linker input file not found: No such file or directory cc: warning: $<$,$>:-fopenmp-simd>: linker input file unused because linking not done cc: error: $<$,$>:-fopenmp-simd>: linker input file not found: No such file or directory ninja: build stopped: subcommand failed. dh_auto_build: error: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make: *** [debian/rules:13: binary-arch] Error 25 Eriberto -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 obs-time-source depends on: ii libc62.36-9+deb12u3 ii libcairo21.16.0-7 ii libglib2.0-0 2.74.6-2 ii libobs0 29.0.2+dfsg-1+b1 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii obs-studio 29.0.2+dfsg-1+b1 obs-time-source recommends no packages. obs-time-source suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: obs-time-source Source-Version: 0.2-2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of obs-time-source, which is due to be installed in the Debian FTP archive. A summary of the changes between this
Bug#1055540: obs-time-source: FTBFS on several archs: linker input file not found
Some tests were made over Debian, Alpine and Fedora and the issue causing the FTBFS is present only on Debian. The Meson finds the libobs, but fails to build using it. Maybe it can be something related to #998853. The upstream doesn't have a solution because he uses Alpine and the build is perfect there (this bug is unreproducible outside of Debian). My solution (or temporary solution): commonly, plugins for OBS are build with CMake, so I made a patch[1] to use it instead of Meson. This solution works fine and it is based in CMakeLists.txt files provided by Exeldro in several plugins, like obs-move-transition[2]. [1] https://salsa.debian.org/debian/obs-time-source/-/blob/debian/master/debian/patches/010_use-cmake.patch [2] https://salsa.debian.org/debian/obs-move-transition/-/blob/debian/master/CMakeLists.txt Eriberto
Bug#1055901: [Pkg-raspi-maintainers] Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/
On 11/13/23 23:20, Cyril Brulebois wrote: Hilmar Preusse (2023-11-13): Hi, the package fails to install on my system. I simply assumes that /boot/firmware is a mount point and fails if this is not the case. If /boot/firmware is expected to be a mount point the installer should have created it. The system was once installed as bullseye and later upgraded to bookworm. What exactly is your system? What is that rpt suffix? It is an raspi3, not sure if that is the needed information, here comes the apt-cache policy hille@rasppi1:~ $ apt-cache policy raspi-firmware raspi-firmware: Installed: 1:1.20231024+ds-1+rpt1 Candidate: 1:1.20231024+ds-1+rpt1 Version table: *** 1:1.20231024+ds-1+rpt1 500 500 http://archive.raspberrypi.org/debian bookworm/main arm64 Packages 500 http://archive.raspberrypi.org/debian bookworm/main armhf Packages 100 /var/lib/dpkg/status 1.20220830+ds-1 500 500 http://deb.debian.org/debian bookworm/non-free-firmware arm64 Packages 500 http://deb.debian.org/debian bookworm/non-free-firmware armhf Packages Does that help you anyhow? Hilmar -- Testmail OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055901: [Pkg-raspi-maintainers] Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/
Hi, Hilmar Preusse (2023-11-13): > Package: raspi-firmware > Version: 1:1.20231024+ds-1+rpt1 > Severity: serious > Justification: Policy 6.4 > > Hello, > > the package fails to install on my system. I simply assumes that > /boot/firmware is a > mount point and fails if this is not the case. If /boot/firmware is expected > to be a > mount point the installer should have created it. The system was once > installed as > bullseye and later upgraded to bookworm. What exactly is your system? What is that rpt suffix? > Versions of packages raspi-firmware suggests: > ii bluez-firmware 1.2-9+rpt2 > ii firmware-brcm80211 1:20230210-5+rpt1 > ii firmware-misc-nonfree 1:20230210-5+rpt1 Here too. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)
On 11/13/23 23:03, Debian Bug Tracking System wrote: Hi, Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1055901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055901. Here is the error message I get: hille@rasppi1:~ $ sudo apt -f install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up raspi-firmware (1:1.20231024+ds-1+rpt1) ... Error: missing /boot/firmware, did you forget to mount it? dpkg: error processing package raspi-firmware (--configure): installed raspi-firmware package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of rpi-eeprom: rpi-eeprom depends on raspi-firmware; however: Package raspi-firmware is not configured yet. dpkg: error processing package rpi-eeprom (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.142) ... Errors were encountered while processing: raspi-firmware rpi-eeprom E: Sub-process /usr/bin/dpkg returned an error code (1) Hilmar -- Testmail OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055901: raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/
Package: raspi-firmware Version: 1:1.20231024+ds-1+rpt1 Severity: serious Justification: Policy 6.4 Hello, the package fails to install on my system. I simply assumes that /boot/firmware is a mount point and fails if this is not the case. If /boot/firmware is expected to be a mount point the installer should have created it. The system was once installed as bullseye and later upgraded to bookworm. Himar -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9+rpt2 ii firmware-brcm80211 1:20230210-5+rpt1 ii firmware-misc-nonfree 1:20230210-5+rpt1 -- no debconf information
Processed: Fixed 1054750
Processing commands for cont...@bugs.debian.org: > fixed 1054750 reuse/2.1.0-1 Bug #1054750 [src:reuse] reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1 Marked as fixed in versions reuse/2.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055896: cod-tools: FTBFS: source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did you mean ‘OP_CONST’?
Source: cod-tools
Version: 3.7.0+dfsg-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=cod-tools=s390x=3.7.0%2Bdfsg-1%2Bb4=1699906136=0
make[2]: Entering directory '/<>/src/lib/perl5/COD/SPGLib'
swig -perl5 -Wall -outdir lib/COD/ source.i
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-unused-value \
-I. -c \
`perl -MConfig -e 'print join(" ", @Config{qw(ccflags optimize
cccdlflags)}, "-I$Config{archlib}/CORE")'` \
source.c source_wrap.c
source.c: In function ‘get_sym_dataset’:
source.c:33:5: error: ‘SPGCONST’ undeclared (first use in this function); did
you mean ‘OP_CONST’?
33 | SPGCONST double lattice[3][3];
| ^~~~
| OP_CONST
source.c:33:5: note: each undeclared identifier is reported only once for each
function it appears in
source.c:33:13: error: expected ‘;’ before ‘double’
33 | SPGCONST double lattice[3][3];
| ^~~
| ;
source.c:36:13: error: ‘lattice’ undeclared (first use in this function); did
you mean ‘lattice_av’?
36 | lattice[i][j] = SvNV( (SV*)
| ^~~
| lattice_av
source.c:44:13: error: expected ‘;’ before ‘double’
44 | SPGCONST double positions[natoms][3];
| ^~~
| ;
source.c:49:13: error: ‘positions’ undeclared (first use in this function)
49 | positions[i][j] = SvNV( (SV*)
| ^
make[2]: *** [Makelocal-SWIG-module:36: source.o] Error 1
Cheers
--
Sebastian Ramacher
Processed: severity of 1055895 is grave
Processing commands for cont...@bugs.debian.org: > severity 1055895 grave Bug #1055895 [src:rust-self-cell] rust-self-cell: RUSTSEC-2023-0070 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1055895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1055880 is serious, tagging 1055880
Processing commands for cont...@bugs.debian.org: > severity 1055880 serious Bug #1055880 [kaidan] kaidan missing two dependencies Severity set to 'serious' from 'grave' > tags 1055880 + pending Bug #1055880 [kaidan] kaidan missing two dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055670: marked as done (fwknop-server: must Depends: apparmor-profiles-extra)
Your message dated Mon, 13 Nov 2023 19:19:24 + with message-id and subject line Bug#1055670: fixed in fwknop 2.6.10-19 has caused the Debian Bug report #1055670, regarding fwknop-server: must Depends: apparmor-profiles-extra 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.) -- 1055670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fwknop-server Version: 2.6.10-18 Severity: serious Tags: patch security Justification: Policy 7.2 X-Debbugs-Cc: Debian Security Team Dear Maintainer, The latest update breaks apparmor for the whole system. /etc/apparmor.d/usr.sbin.fwknopd: include This must declare Depends: apparmor-profiles-extra. Otherwise the apparmor service can't parse the file and will refuse to start. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwknop-server depends on: ii init-system-helpers 1.65.2 ii iptables 1.8.9-2 ii libc62.37-12 ii libfko3 2.6.10-18 ii libpcap0.8 1.10.4-4 fwknop-server recommends no packages. fwknop-server suggests no packages. -- Configuration Files: /etc/fwknop/access.conf [Errno 13] Permission denied: '/etc/fwknop/access.conf' /etc/fwknop/fwknopd.conf [Errno 13] Permission denied: '/etc/fwknop/fwknopd.conf' -- no debconf information --- End Message --- --- Begin Message --- Source: fwknop Source-Version: 2.6.10-19 Done: Francois Marier We believe that the bug you reported is fixed in the latest version of fwknop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Marier (supplier of updated fwknop 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: Mon, 13 Nov 2023 10:48:47 -0800 Source: fwknop Architecture: source Version: 2.6.10-19 Distribution: unstable Urgency: medium Maintainer: Francois Marier Changed-By: Francois Marier Closes: 949331 1055670 Changes: fwknop (2.6.10-19) unstable; urgency=medium . * Move apparmor profile back into fwknop-apparmor-profile. * Add missing apparmor-profiles-extra dependency (closes: #1055670). * Add Breaks/Replaces on fwknop-server for fwknop-apparmor-profile. * Switch to NFQ (closes: #949331). Checksums-Sha1: 81569da7defe367f1524a6fb6825d7fe4d26953d 2761 fwknop_2.6.10-19.dsc 6607b73c47b6e2e19161f943bad96e863e52282a 20652 fwknop_2.6.10-19.debian.tar.xz ba3407e1596590635bf809d3739c9614d09f9b99 12926 fwknop_2.6.10-19_source.buildinfo Checksums-Sha256: 995443b4633ce5738709080d1ac0899bb957a90b4af75a568677da81c12ad6c8 2761 fwknop_2.6.10-19.dsc 1130af534314ff9dee387da97b965ce840010bdae28e2ff31f224d9e0bd7ec5e 20652 fwknop_2.6.10-19.debian.tar.xz 7043605f64a0566f507f7636670d443e7dc6e287da6101acf37bd6cde407ca4e 12926 fwknop_2.6.10-19_source.buildinfo Files: 6d22c235b334e68d3122f1ef83802c0f 2761 admin optional fwknop_2.6.10-19.dsc 03540e1be648cb1e209e6444336ff582 20652 admin optional fwknop_2.6.10-19.debian.tar.xz a4e1217ac4be80e0069a91487ac2f467 12926 admin optional fwknop_2.6.10-19_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmVSc2xfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8 mNHZ2Q/9Fi7LEGUA9BKEUYvFL7IcXfsCkaAILXS6moEMZev2Y6jXxorbetCwBeT+ /b2ucKer+vL/mmRd3rjsyv6Keki86Z1FwZf7pUPiIHkJ9NUFkyD+2SqdpoFa1fXE UpDCgtlHzAOF6VCJ28MZcZ9iBs2fUbUPCqRL50BE3PJH82l3N4xRoiL6SoelxCQV wb9/pHp2AO+37BIfqDqt2sMY1NQDoTPh87pEp8quu7cb0ezNxgKzM30OfPj+nfdD
Bug#1055783: marked as done (glib: FTBFS on armhf: test failure)
Your message dated Mon, 13 Nov 2023 18:35:15 + with message-id and subject line Bug#1055783: fixed in glib2.0 2.78.1-4 has caused the Debian Bug report #1055783, regarding glib: FTBFS on armhf: test failure 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.) -- 1055783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib2.0 Version: 2.78.1-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=glib2.0=armhf=2.78.1-3=1699604499=0 89/367 glib:glib+core+slow / thread-pool-slow RUNNING >>> G_DEBUG=gc-friendly >>> G_TEST_BUILDDIR=/<>/debian/build/deb/glib/tests >>> G_TEST_SRCDIR=/<>/glib/tests G_ENABLE_DIAGNOSTIC=1 >>> MALLOC_PERTURB_=229 LD_LIBRARY_PATH=/<>/debian/build/deb/glib >>> MALLOC_CHECK_=2 >>> /<>/debian/build/deb/glib/tests/thread-pool-slow ▶ 89/367 /threadpool/basics - GLib:ERROR:../../../glib/tests/thread-pool-slow.c:221:test_thread_sort_entry_func: assertion failed (last_thread_id <= thread_id): (16 <= 8) FAIL ▶ 89/367 ERROR 89/367 glib:glib+core+slow / thread-pool-slow ERROR 9.08s killed by signal 6 SIGABRT ― ✀ ― stderr: ** GLib:ERROR:../../../glib/tests/thread-pool-slow.c:221:test_thread_sort_entry_func: assertion failed (last_thread_id <= thread_id): (16 <= 8) (test program exited with status code -6) […] Summary of Failures: 89/367 glib:glib+core+slow / thread-pool-slow ERROR 9.08s killed by signal 6 SIGABRT Ok: 363 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:3 Timeout:0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: glib2.0 Source-Version: 2.78.1-4 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of glib2.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated glib2.0 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: Mon, 13 Nov 2023 16:37:33 + Source: glib2.0 Architecture: source Version: 2.78.1-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1055783 Changes: glib2.0 (2.78.1-4) unstable; urgency=medium . * d/p/tests-Fix-a-race-in-thread-pool-slow.patch: Add patch from upstream git fixing a race condition in a test (hopefully Closes: #1055783) Checksums-Sha1: 6671f27840b1fedb468d2fec2d4da41ba40c4870 3648 glib2.0_2.78.1-4.dsc 68c9d6258271b9d3ec87ae7ed96694f7f9296c0c 126452 glib2.0_2.78.1-4.debian.tar.xz 59d7ed264e2f222c2c0d5d26863a0bae312e16c1 7045 glib2.0_2.78.1-4_source.buildinfo Checksums-Sha256: 83726c95a55e9c623b63bdee774a514b6493b1c889356ae0af01eb8056c7 3648 glib2.0_2.78.1-4.dsc b819f71aa9014dce4026cc32ed3921dccbb937a1aa6309793b86d9426854479c 126452 glib2.0_2.78.1-4.debian.tar.xz 4b1a35c30a77bd40742d8c69b0261d731249e66f47295f51b054bb0deb61de1e 7045 glib2.0_2.78.1-4_source.buildinfo Files: f8f0b18ae4104d2ca669b44416d7c544 3648 libs optional glib2.0_2.78.1-4.dsc 3b8d159cc968ea7cce05ac9b51761609 126452 libs optional glib2.0_2.78.1-4.debian.tar.xz 4355dd6a51b0c9f0ec751f98fb17afe9 7045 libs optional glib2.0_2.78.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmVSajwACgkQ4FrhR4+B TE9RFhAAqa02D2D2KHQQW42yhcVQgIFZMQ8n9uv/9cB/qsmoqgHXbi1kCxUYKBXH HPIO4OKt5AdEJ5QEx/HMh/PoJ3NFF7QlmOmVRYDDxprx8RFmFAWyFdAUGRVoHXtY 9CZj6rhICizLOuP6YZEB+CKqawWYikpzDnTrk7O/FFYIqtwS7Jk5ZRyPVZdpU17d PZvb4sk9U1gWo8uku9rvrh2iQ+BGs5zc+fYaKUH/H4epS1PxQea3rXbs7wMA7uFO
Bug#1055892: sunpy: FTBFS in bookworm: leap-second file is expired.
Package: src:sunpy Version: 4.1.2-1 Severity: serious Tags: ftbfs bookworm upstream Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build. The error I got is the same in reproducible-builds: https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/sunpy_4.1.2-1.rbuild.log.gz This failure is almost the same as Bug #1055877 in ndcube, so everything I said there applies here as well (we want packages to build always during the lifetime of stable, etc). Sorry, I don't have a patch in this case. Since there are now (at least) two affected packages, maybe it would be worth to think of a common solution for both packages which does not involve skipping each and every test having the time bomb. Thanks.
Processed: transition: gdal
Processing control commands: > affects -1 + src:gdal Bug #1055891 [release.debian.org] transition: gdal Added indication that 1055891 affects src:gdal > forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Bug #1055891 [release.debian.org] transition: gdal Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-gdal.html'. > block -1 by 1051433 Bug #1055891 [release.debian.org] transition: gdal 1055891 was not blocked by any bugs. 1055891 was not blocking any bugs. Added blocking bug(s) of 1055891: 1051433 -- 1055891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 1053004 5.1+ds-4+deb10u1 Bug #1053004 [src:phppgadmin] phppgadmin: CVE-2023-40619 The source 'phppgadmin' and version '5.1+ds-4+deb10u1' do not appear to match any binary packages Marked as fixed in versions phppgadmin/5.1+ds-4+deb10u1. > # > https://tracker.debian.org/news/1475649/accepted-phppgadmin-51ds-4deb10u1-source-all-into-oldoldstable/ > thanks Stopping processing here. Please contact me if you need assistance. -- 1053004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055154: marked as done (ugrep: FTBFS on mipse64el)
Your message dated Mon, 13 Nov 2023 14:38:15 +
with message-id
and subject line Bug#1055154: fixed in ugrep 4.3.2+dfsg-2
has caused the Debian Bug report #1055154,
regarding ugrep: FTBFS on mipse64el
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.)
--
1055154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ugrep
Version: 4.3.1+dfsg-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=ugrep=mips64el=4.3.1%2Bdfsg-1=1698744731=0
make[1]: Entering directory '/<>'
*** SINGLE-THREADED TESTS ***
cd ./tests && env UGREP_ABS_PATH=/<>/./bin/ugrep
CONFIGH_ABS_PATH=/<>/./config.h ./verify.sh -J1
ugrep 4.3.1 mips64el-unknown-linux-gnuabi64 +pcre2jit +zlib +bzip2 +lzma +lz4
+zstd
Have libpcre2? yes
Have libz? yes
Have libbz2? yes
Have liblzma? yes
Have liblz4? yes
Have libzstd? yes
..---
- 2023-10-31 09:31:59.204921565 +
+++ out/archive.cpio.out2023-10-27 12:58:31.0 +
@@ -1,2 +1,8 @@
␛[1;35marchive.cpio{Hello.bat}␛[m␛[1;36m:␛[m1
-␛[1;35marchive.cpio{Hello.class}␛[m␛[1;36m:␛[m0
+␛[1;35marchive.cpio{Hello.class}␛[m␛[1;36m:␛[m1
+␛[1;35marchive.cpio{Hello.java}␛[m␛[1;36m:␛[m2
+␛[1;35marchive.cpio{Hello.pdf}␛[m␛[1;36m:␛[m1
+␛[1;35marchive.cpio{Hello.sh}␛[m␛[1;36m:␛[m1
+␛[1;35marchive.cpio{Hello.txt}␛[m␛[1;36m:␛[m1
+␛[1;35marchive.cpio{empty.txt}␛[m␛[1;36m:␛[m0
+␛[1;35marchive.cpio{emptyline.txt}␛[m␛[1;36m:␛[m0
␛[1;31mError:␛[0m␛[1m ugrep --sort -z -c Hello archive.cpio ␛[1;31mfailed␛[0m
make[1]: *** [Makefile:975: test] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 test "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1
returned exit code 2
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ugrep
Source-Version: 4.3.2+dfsg-2
Done: Ricardo Ribalda Delgado
We believe that the bug you reported is fixed in the latest version of
ugrep, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ricardo Ribalda Delgado (supplier of updated ugrep
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: Mon, 13 Nov 2023 14:36:58 +0100
Source: ugrep
Architecture: source
Version: 4.3.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Ribalda Delgado
Changed-By: Ricardo Ribalda Delgado
Closes: 1055154
Changes:
ugrep (4.3.2+dfsg-2) unstable; urgency=medium
.
* Do not run tests in mips64el. It is flaky in that platform. (Closes:
#1055154)
Checksums-Sha1:
e4ccabec960f967015c3736cf045a8fd45c95aed 2014 ugrep_4.3.2+dfsg-2.dsc
bb6d193566a948a5202f681413a665633c8df3c9 8108 ugrep_4.3.2+dfsg-2.debian.tar.xz
a23d1ca16d4325a1cdd5fa061bd736a7c7cd47b0 6103
ugrep_4.3.2+dfsg-2_source.buildinfo
Checksums-Sha256:
6e97faecadf774f3179a18f721363d36b4092e25757d508bbb117b76e55c28bf 2014
ugrep_4.3.2+dfsg-2.dsc
b02cabc60818ce34d8719e0dc5828cc3d3759552b35bcea9adc9372e8179b771 8108
ugrep_4.3.2+dfsg-2.debian.tar.xz
e7bf2ccc82d734ca443a5579d5136c3d44063ad3c2e5c2ddf7d9d67c53821f05 6103
Bug#1050854: Please push your changes to python-xarray
Hi Apologies I am swamped on this. Please go ahead and apply. Thanks Alastair On 13/11/2023 12:51, Andreas Tille wrote: Ping? I'd love to apply the patch from the bug report and push everything properly. If I do not hear from you I might consider mass-commiting all the releases you made without pushing to the repository in one single commit and add what I'd like to commit. Kind regards Andreas. Am Tue, Nov 07, 2023 at 09:26:13AM +0100 schrieb Andreas Tille: Hi Alastair, I realised that the Git repository on salsa[1] is lagging a couple of uploads behind the package pool. Please be so kind to push your changes to Salsa. Thanks a lot for your work on this package Andreas. [1] https://salsa.debian.org/science-team/python-xarray -- http://fam-tille.de -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 e: mckins...@debian.org, im: @alastair:mckinstry.ie
Bug#1054933: marked as done (yi: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-
Your message dated Mon, 13 Nov 2023 14:55:48 +0100 with message-id <169988374859.32117.508216297783495278.reportbug@localhost> and subject line yi: bug no longer found has caused the Debian Bug report #1054933, regarding yi: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, libghc-data-default-dev-0.7.1.1-6d3b3, libghc-directory-dev-1.3.6.2-311c9, libghc-dlist-dev-1.0-366f6, libghc-dynamic-state-dev-0.3.1-d49ee, libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, libghc-hashable-dev-1.3.5.0-3fad8, libghc-listlike-dev-4.7.7-58f6d, libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-mtl-dev-2.2.2-e3bae, libghc-old-locale-dev-1.0.0.7-60e52, libghc-oo-prototypes-dev-0.1.0.0-9dda4, libghc-parsec-dev-3.1.14.0-377f0, libghc-pointedlist-dev-0.6.1-f22c9, libghc-process-dev-1.6.13.2-9f25f, libghc-process-extras-dev-0.7.4-d5396, libghc-split-dev-0.2.3.5-0c13f, libghc-text-dev-1.2.5.0-8553e, libghc-time-dev-1.9.3-bda76, libghc-transformers-base-dev-0.4.6-a0a78, libghc-unix-compat-dev-0.5.4-1f010, libghc-unix-dev-2.7.2.2-bdab4, libghc-unordered-containers-dev-0.2.17.0-1d16d, libghc-xdg-basedir-dev-0.2.2-01215, libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, libghc-array-prof-0.5.4.0-0b6fa, libghc-attoparsec-prof-0.14.4-9b901, libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, libghc-data-default-prof-0.7.1.1-6d3b3, libghc-directory-prof-1.3.6.2-311c9, libghc-dlist-prof-1.0-366f6, libghc-dynamic-state-prof-0.3.1-d49ee, libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, libghc-hashable-prof-1.3.5.0-3fad8, libghc-listlike-prof-4.7.7-58f6d, libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-mtl-prof-2.2.2-e3bae, libghc-old-locale-prof-1.0.0.7-60e52, libghc-oo-prototypes-prof-0.1.0.0-9dda4, libghc-parsec-prof-3.1.14.0-377f0, libghc-pointedlist-prof-0.6.1-f22c9, libghc-process-extras-prof-0.7.4-d5396, libghc-process-prof-1.6.13.2-9f25f, libghc-split-prof-0.2.3.5-0c13f, libghc-text-prof-1.2.5.0-8553e, libghc-time-prof-1.9.3-bda76, libghc-transformers-base-prof-0.4.6-a0a78, libghc-unix-compat-prof-0.5.4-1f010, libghc-unix-prof-2.7.2.2-bdab4, libghc-unordered-containers-prof-0.2.17.0-1d16d, libghc-xdg-basedir-prof-0.2.2-01215, libghc-yi-language-prof-0.19.0-ac372, libghc-yi-rope-prof-0.11-1df98, libghc-base-dev-4.15.1.0-6a406, libghc-containers-dev-0.6.4.1-31c3b, libghc-data-default-dev-0.7.1.1-6d3b3, libghc-dlist-dev-1.0-366f6, libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-pointedlist-dev-0.6.1-f22c9, libghc-stm-dev-2.5.0.0-4cba8, libghc-text-dev-1.2.5.0-8553e, libghc-vty-dev-5.33-73986, libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, libghc-base-prof-4.15.1.0-6a406, libghc-containers-prof-0.6.4.1-31c3b, libghc-data-default-prof-0.7.1.1-6d3b3, libghc-dlist-prof-1.0-366f6, libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-pointedlist-prof-0.6.1-f22c9, libghc-stm-prof-2.5.0.0-4cba8, libghc-text-prof-1.2.5.0-8553e, libghc-vty-prof-5.33-73986, libghc-yi-language-prof-0.19.0-ac372, libghc-yi-rope-prof-0.11-1df98, libghc-base-dev-4.15.1.0-6a406, libghc-containers-dev-0.6.4.1-31c3b, libghc-filepath-dev-1.4.2.1-4459f, libghc-hclip-dev-3.0.0.4-4b4fb, libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-mtl-dev-2.2.2-e3bae, libghc-oo-prototypes-dev-0.1.0.0-9dda4, libghc-text-dev-1.2.5.0-8553e, libghc-transformers-base-dev-0.4.6-a0a78, libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, libghc-base-prof-4.15.1.0-6a406, libghc-containers-prof-0.6.4.1-31c3b, libghc-filepath-prof-1.4.2.1-4459f, libghc-hclip-prof-3.0.0.4-4b4fb, libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-mtl-prof-2.2.2-e3bae, libghc-oo-prototypes-prof-0.1.0.0-9dda4, libghc-text-prof-1.2.5.0-8553e, libghc-transformers-base-prof-0.4.6-a0a78, libghc-yi-language-prof-0.19.0-ac372, libghc-yi-rope-prof-0.11-1df98, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-containers-dev-0.6.4.1-31c3b, libghc-data-default-dev-0.7.1.1-6d3b3, libghc-directory-dev-1.3.6.2-311c9, libghc-filepath-dev-1.4.2.1-4459f, libghc-hclip-dev-3.0.0.4-4b4fb, libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-mtl-dev-2.2.2-e3bae, libghc-oo-prototypes-dev-0.1.0.0-9dda4, libghc-pointedlist-dev-0.6.1-f22c9, libghc-safe-dev-0.3.19-b4ca4, libghc-text-dev-1.2.5.0-8553e, libghc-transformers-base-dev-0.4.6-a0a78, libghc-unordered-containers-dev-0.2.17.0-1d16d, libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, libghc-attoparsec-prof-0.14.4-9b901, libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, libghc-containers-prof-0.6.4.1-31c3b,
Processed: found 1055679 in 2.12-1, found 1055679 in 2.5-1, tagging 1055679, reassign 1036268 to src:mutter ...
Processing commands for cont...@bugs.debian.org:
> found 1055679 2.12-1
Bug #1055679 {Done: Jakub Ružička }
[nvchecker,python3-nvchecker] nvchecker and python3-nvchecker have an
undeclared file conflict on 56 files
There is no source info for the package 'nvchecker' at version '2.12-1' with
architecture ''
Marked as found in versions python-nvchecker/2.12-1.
> found 1055679 2.5-1
Bug #1055679 {Done: Jakub Ružička }
[nvchecker,python3-nvchecker] nvchecker and python3-nvchecker have an
undeclared file conflict on 56 files
There is no source info for the package 'python3-nvchecker' at version '2.5-1'
with architecture ''
Marked as found in versions nvchecker/2.5-1.
> tags 1055679 + sid trixie
Bug #1055679 {Done: Jakub Ružička }
[nvchecker,python3-nvchecker] nvchecker and python3-nvchecker have an
undeclared file conflict on 56 files
Added tag(s) trixie and sid.
> reassign 1036268 src:mutter 43.4-2
Bug #1036268 {Done: Simon McVittie } [gnome-shell]
gnome-shell: Session crashes, thrown out to login screen, after the session has
been idle & screen switched off
Bug reassigned from package 'gnome-shell' to 'src:mutter'.
No longer marked as found in versions gnome-shell/43.4-1.
No longer marked as fixed in versions mutter/43.6-1 and mutter/43.6-1~deb12u1.
Bug #1036268 {Done: Simon McVittie } [src:mutter] gnome-shell:
Session crashes, thrown out to login screen, after the session has been idle &
screen switched off
Marked as found in versions mutter/43.4-2.
> fixed 1036268 43.6-1
Bug #1036268 {Done: Simon McVittie } [src:mutter] gnome-shell:
Session crashes, thrown out to login screen, after the session has been idle &
screen switched off
Marked as fixed in versions mutter/43.6-1.
> fixed 1036268 43.6-1~deb12u1
Bug #1036268 {Done: Simon McVittie } [src:mutter] gnome-shell:
Session crashes, thrown out to login screen, after the session has been idle &
screen switched off
Marked as fixed in versions mutter/43.6-1~deb12u1.
> affects 1036268 + src:gnome-shell
Bug #1036268 {Done: Simon McVittie } [src:mutter] gnome-shell:
Session crashes, thrown out to login screen, after the session has been idle &
screen switched off
Added indication that 1036268 affects src:gnome-shell
> tags 1046259 + experimental
Bug #1046259 {Done: Andreas Metzler } [src:libvigraimpex]
libvigraimpex: Fails to build source after successful build
Added tag(s) experimental.
> reassign 1052908 src:eccodes 2.31.2-1
Bug #1052908 {Done: Alastair McKinstry } [src:flexpart]
flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for
reading at (1): No such file or directory
Bug reassigned from package 'src:flexpart' to 'src:eccodes'.
No longer marked as found in versions flexpart/9.02-26.
No longer marked as fixed in versions eccodes/2.31.2-2.
Bug #1052908 {Done: Alastair McKinstry } [src:eccodes]
flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for
reading at (1): No such file or directory
Marked as found in versions eccodes/2.31.2-1.
> fixed 1052908 2.31.2-2
Bug #1052908 {Done: Alastair McKinstry } [src:eccodes]
flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for
reading at (1): No such file or directory
Marked as fixed in versions eccodes/2.31.2-2.
> affects 1052908 + src:flexpart
Bug #1052908 {Done: Alastair McKinstry } [src:eccodes]
flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for
reading at (1): No such file or directory
Added indication that 1052908 affects src:flexpart
> reassign 1052890 src:eccodes 2.31.2-1
Bug #1052890 {Done: Alastair McKinstry } [src:flextra]
flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading
at (1): No such file or directory
Bug reassigned from package 'src:flextra' to 'src:eccodes'.
No longer marked as found in versions flextra/5.0-17.
No longer marked as fixed in versions eccodes/2.31.2-2.
Bug #1052890 {Done: Alastair McKinstry } [src:eccodes]
flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading
at (1): No such file or directory
Marked as found in versions eccodes/2.31.2-1.
> fixed 1052890 2.31.2-2
Bug #1052890 {Done: Alastair McKinstry } [src:eccodes]
flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading
at (1): No such file or directory
Marked as fixed in versions eccodes/2.31.2-2.
> affects 1052890 + src:flextra
Bug #1052890 {Done: Alastair McKinstry } [src:eccodes]
flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading
at (1): No such file or directory
Added indication that 1052890 affects src:flextra
> reassign 1053162 src:newtonsoft-json 6.0.8+dfsg-1.1
Bug #1053162 {Done: Bastian Germann }
[nupkg-newtonsoft.json.6.0.8] nupkg-newtonsoft.json.6.0.8: Please drop to
prevent autoremoval
Bug reassigned from package 'nupkg-newtonsoft.json.6.0.8' to
'src:newtonsoft-json'.
Ignoring request to alter found versions of bug #1053162 to the same values
previously set
No longer marked as fixed in versions
Bug#1042609: sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError')
Hi Faidon! On Mon, Nov 13, 2023 at 10:52:58AM +0200, Faidon Liambotis wrote: > Upstream commit 6f8de39¹, the only commit since 0.9.2, replaces > sphinx.util.SphinxParallelError by sphinx.util.DownloadFiles. > > I've verified that backporting this commit makes the package build > successfully in unstable, with Sphinx 7.2.6-2. > > However, the very same commit changes requirements.txt from > "Sphinx>=3.2.1" to "Sphinx<7". > > I'm not sure why. I'm not using, nor am I familiar with this plugin, so > I was hoping someone else that is could perhaps validate whether besides > being able to be built, the package actually works. > > 1: > https://github.com/mgaitan/sphinxcontrib-mermaid/commit/6f8de39a84fddc398542e9d4dc74ba55101e7d5e The SphinxParallelError class is defined in sphinx.errors module. It was available in sphinx.util because that module happened to import it from sphinx.errors, but that is no longer the case since Sphinx 6.1. Probably the author of the linked commit was testing with Sphinx 6.1 (or 6.2), but had different problems with early Sphinx 7 versions (only Sphinx 7.0.1 was available at that moment), so changed the dependency to <7. The change in README.rst looks trivial, so if it helps, I would go ahead and cherry-pick it to our packaging without the requirements.txt change. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1050854: Please push your changes to python-xarray
Ping? I'd love to apply the patch from the bug report and push everything properly. If I do not hear from you I might consider mass-commiting all the releases you made without pushing to the repository in one single commit and add what I'd like to commit. Kind regards Andreas. Am Tue, Nov 07, 2023 at 09:26:13AM +0100 schrieb Andreas Tille: > Hi Alastair, > > I realised that the Git repository on salsa[1] is lagging a couple of > uploads behind the package pool. Please be so kind to push your changes > to Salsa. > > Thanks a lot for your work on this package > Andreas. > > [1] https://salsa.debian.org/science-team/python-xarray > > -- > http://fam-tille.de > > -- http://fam-tille.de
Bug#1055880: kaidan missing two dependencies
Package: kaidan version: 0.9.1-1 severity: grave justification: fails to start Though fix is easy, missing dependencies are qml-module-org-kde-kquickimageeditor and qml-module-org-kde-kirigami-addons-labs-mobileform After installing these manually, kaidan starts as expected.
Bug#1055877: ndcube: FTBFS in bookworm: leap-second file is expired
A more simple approach would be to modify debian/rules so that (all) the tests are skipped after a certain date, as in the attached patch. Thanks.--- a/debian/rules +++ b/debian/rules @@ -7,6 +7,9 @@ export PYBUILD_TEST_ARGS=../../../ndcube export http_proxy=127.0.0.1:9 export HOME=$(shell mktemp -d) +CURRENT_TS := $(shell date +%s) +EXPIRE_TS := $(shell date +%s -d "2023-12-01") + BUILD_DATE = $(shell LC_ALL=C date -u "+%B %d, %Y" -d "@$(SOURCE_DATE_EPOCH)") SPHINXOPTS := -D html_last_updated_fmt="$(BUILD_DATE)" -D html_show_copyright=0 @@ -36,3 +39,6 @@ override_dh_link: dh_link # Remove duplicates in documentation package jdupes -rl debian/python3-ndcube-doc/usr + +override_dh_auto_test: + [ "$(CURRENT_TS)" -gt "$(EXPIRE_TS)" ] || dh_auto_test
Bug#1055877: ndcube: FTBFS in bookworm: leap-second file is expired
Package: src:ndcube
Version: 2.0.3-1
Severity: serious
Tags: ftbfs bookworm patch upstream
Dear maintainer:
During a rebuild of all packages in bookworm, this package failed to build
with the following error:
---
files = None
def update_leap_seconds(files=None):
"""If the current ERFA leap second table is out of date, try to update
it.
Uses `astropy.utils.iers.LeapSeconds.auto_open` to try to find an
up-to-date table. See that routine for the definition of "out of date".
In order to make it safe to call this any time, all exceptions are turned
into warnings,
Parameters
--
files : list of path-like, optional
List of files/URLs to attempt to open. By default, uses defined by
`astropy.utils.iers.LeapSeconds.auto_open`, which includes the table
used by ERFA itself, so if that is up to date, nothing will happen.
Returns
---
n_update : int
Number of items updated.
"""
try:
from astropy.utils import iers
table = iers.LeapSeconds.auto_open(files)
return erfa.leap_seconds.update(table)
except Exception as exc:
warn(
f"leap-second auto-update failed due to the following exception:
{exc!r}",
AstropyWarning,
)
E astropy.utils.exceptions.AstropyWarning: leap-second auto-update
failed due to the following exception: IERSStaleWarning('leap-second file is
expired.')
/usr/lib/python3/dist-packages/astropy/time/core.py:3315: AstropyWarning
=== short test summary info
FAILED
../../../ndcube/extra_coords/tests/test_extra_coords.py::test_two_1d_from_lut
= 1 failed, 276 passed, 5 skipped, 27 deselected, 9 xfailed, 2 xpassed in 4.68s
=
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.11_ndcube/build; python3.11 -m pytest
../../../ndcube
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit
code 13
make: *** [debian/rules:14: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
In reproducible-builds, the same package version (2.0.3-1) builds ok in trixie:
https://tests.reproducible-builds.org/debian/rbuild/trixie/amd64/ndcube_2.0.3-1.rbuild.log.gz
but not the second build, which is tried one month in the future precisely
to catch errors like this one:
https://tests.reproducible-builds.org/debian/logs/trixie/amd64/ndcube_2.0.3-1.build2.log.gz
Note that because exactly the same package version builds ok in trixie but not in
bookworm, we could be tempted to consider this as a bug in the package which provides the
leap-second file, which is "not updated enough in bookworm".
However, I don't think this would be a good idea, as this problem would become
some sort
of time-bomb. We want packages to build ok from source not only at release time
but also
during all the lifetime of bookworm as stable (and if possible, forever), i.e.
users should
not be forced to upgrade all the time so that the packages continue to build ok.
I attach a patch which works for me in bookworm. Please double-check, no
warranty, etc.
Alternatively, all those unconditional skip marks could be
changed to something like this, in pseudocode:
skipif(currentdate >
hardcoded-expiration-date-of-leapsecond-file-at-upload-time)
but I don't really know if it worth the effort.
I'm tagging this as "upstream" because I believe there should be an easier way
to deal with this.
Thanks.commit 079219c8ad4bc798065a28528283f59373be2623
Author: Santiago Vila
Date: Mon Nov 13 13:15:00 2023 +0100
skip-time-bombs
diff --git a/ndcube/extra_coords/tests/test_extra_coords.py
b/ndcube/extra_coords/tests/test_extra_coords.py
index f3463b2..197b934 100644
--- a/ndcube/extra_coords/tests/test_extra_coords.py
+++ b/ndcube/extra_coords/tests/test_extra_coords.py
@@ -158,6 +158,7 @@ def test_single_from_lut(extra_coords_wave):
assert ec.wcs.world_axis_names == ("wave",)
+@pytest.mark.skip(reason="time bomb")
def test_two_1d_from_lut(time_lut):
cube = MagicMock()
cube.dimensions = [10] * u.pix
@@ -174,6 +175,7 @@ def test_two_1d_from_lut(time_lut):
assert ec.wcs.world_axis_names == ("time", "exposure_time")
+@pytest.mark.skip(reason="time bomb")
def test_two_1d_from_lookup_tables(time_lut):
"""
Create ExtraCoords from both tables at once using `from_lookup_tables`
with `physical_types`.
@@ -252,6 +254,7 @@ def test_skycoord_mesh_false(skycoord_2d_lut):
assert ec.wcs.world_axis_names == ("lat", "lon")
+@pytest.mark.skip(reason="time bomb")
def test_extra_coords_index(skycoord_2d_lut, time_lut):
cube = MagicMock()
Bug#1042356: marked as done (rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25)
Your message dated Mon, 13 Nov 2023 12:04:08 +
with message-id
and subject line Bug#1042356: fixed in rapid-photo-downloader 0.9.34+repack-1
has caused the Debian Bug report #1042356,
regarding rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean]
Error 25
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.)
--
1042356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rapid-photo-downloader
Version: 0.9.33-1.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):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean
> error in rapid-photo-downloader setup command: 'python_requires' must be a
> string containing valid version specifiers; Invalid specifier: '>=3.6.*'
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:8: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/rapid-photo-downloader_0.9.33-1.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: rapid-photo-downloader
Source-Version: 0.9.34+repack-1
Done: Dr. Tobias Quathamer
We believe that the bug you reported is fixed in the latest version of
rapid-photo-downloader, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dr. Tobias Quathamer (supplier of updated
rapid-photo-downloader 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: Mon, 13 Nov 2023 12:34:30 +0100
Source: rapid-photo-downloader
Architecture: source
Version: 0.9.34+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer
Changed-By: Dr. Tobias Quathamer
Closes: 1042356
Changes:
rapid-photo-downloader (0.9.34+repack-1) unstable; urgency=medium
.
* New upstream version 0.9.34
- Fix build with setuptools 67.x.
Thanks to Antoine Beaupré (Closes: #1042356)
Because d/patches are not applied for the clean target,
the build fails due to the wrong python_requires version string.
The repackaged source changes the file setup.py and uses
the version string suggested in the above mentioned bug report.
Upstream has fixed this in VCS, but there's no released
version yet. For the next upstream version, there shouldn't
be a repacking necessary.
* Update d/copyright
* Update Standards-Version to 4.6.2, no changes needed
* Fix lintian warning for d/copyright and move paragraph
Checksums-Sha1:
5e96b6cd9373e7e98f5098670267f91d5978aa50 2300
rapid-photo-downloader_0.9.34+repack-1.dsc
ced95cbeda44cc6b572e1b9054a48b5e4740e8ab 8833667
rapid-photo-downloader_0.9.34+repack.orig.tar.gz
faf04fe4fda8e8b01a0a66d9011e7299ca72161b 3480580
rapid-photo-downloader_0.9.34+repack-1.debian.tar.xz
c956db1d2b27824c1a52c6298d4e137c6cc4f9cd 11122
rapid-photo-downloader_0.9.34+repack-1_amd64.buildinfo
Checksums-Sha256:
f7c9ddf2d5d7cdc7633056141045051de26f1395a994a86ac704fa9eef53a759
Bug#1054684: marked as done (spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such file or directory)
Your message dated Mon, 13 Nov 2023 11:00:10 + with message-id and subject line Bug#1054684: fixed in spdlog 1:1.12.0+ds-1~exp has caused the Debian Bug report #1054684, regarding spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spdlog Version: 1:1.10.0+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DFMT_SHARED > -DSPDLOG_FMT_EXTERNAL -I/<>/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -MD -MT > tests/CMakeFiles/spdlog-utests-ho.dir/test_misc.cpp.o -MF > CMakeFiles/spdlog-utests-ho.dir/test_misc.cpp.o.d -o > CMakeFiles/spdlog-utests-ho.dir/test_misc.cpp.o -c > /<>/tests/test_misc.cpp > In file included from /<>/tests/test_daily_logger.cpp:4: > /<>/tests/includes.h:3:10: fatal error: catch2/catch.hpp: No > such file or directory > 3 | #include > | ^~ > In file included from /<>/tests/test_file_logging.cpp:4: > /<>/tests/includes.h:3:10: fatal error: catch2/catch.hpp: No > such file or directory > 3 | #include > | ^~ > compilation terminated. > compilation terminated. > make[3]: *** [tests/CMakeFiles/spdlog-utests-ho.dir/build.make:107: > tests/CMakeFiles/spdlog-utests-ho.dir/test_daily_logger.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/10/27/spdlog_1.10.0+ds-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: spdlog Source-Version: 1:1.12.0+ds-1~exp Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of spdlog, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated spdlog 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: Mon, 13 Nov 2023 01:49:23 -0500 Source: spdlog Binary: libspdlog-dev libspdlog1.12 libspdlog1.12-dbgsym Architecture: source amd64 Version: 1:1.12.0+ds-1~exp Distribution: experimental Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andrius Merkys Description: libspdlog-dev - Very fast, header only or compiled, C++ logging library libspdlog1.12 - Very fast C++ logging library Closes: 1053774 1054684 Changes: spdlog (1:1.12.0+ds-1~exp) experimental; urgency=medium . * Team upload . [ Andreas Tille ] * New upstream version Closes: #1053774, #1054684 * Remove constraints unnecessary since bullseye (oldstable): + libspdlog1.10: Drop conflict with removed package nheko (<< 0.7.2-3+b1) in Breaks. . [ Andrius Merkys ] * Apply upstream patch to fix tests. * Adapt to soversion change. Checksums-Sha1: 671d145a33d4b50ff28208ce79b800f0d755ab1c 2179 spdlog_1.12.0+ds-1~exp.dsc 60b7a204b455746aebeb5f336fd39e74d59a4ea8 90352 spdlog_1.12.0+ds.orig.tar.xz
Bug#1053774: marked as done (spdlog: need new upstream release 1.12 for catch2 v3)
Your message dated Mon, 13 Nov 2023 11:00:10 + with message-id and subject line Bug#1053774: fixed in spdlog 1:1.12.0+ds-1~exp has caused the Debian Bug report #1053774, regarding spdlog: need new upstream release 1.12 for catch2 v3 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.) -- 1053774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spdlog Version: 1:1.10.0+ds-1 Severity: serious Justification: debci catch2 v3 was recently uploaded, but breaks spdlog's tests. spdlog upstream has released v1.12.0 which uses catch2 v3. --- End Message --- --- Begin Message --- Source: spdlog Source-Version: 1:1.12.0+ds-1~exp Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of spdlog, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated spdlog 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: Mon, 13 Nov 2023 01:49:23 -0500 Source: spdlog Binary: libspdlog-dev libspdlog1.12 libspdlog1.12-dbgsym Architecture: source amd64 Version: 1:1.12.0+ds-1~exp Distribution: experimental Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andrius Merkys Description: libspdlog-dev - Very fast, header only or compiled, C++ logging library libspdlog1.12 - Very fast C++ logging library Closes: 1053774 1054684 Changes: spdlog (1:1.12.0+ds-1~exp) experimental; urgency=medium . * Team upload . [ Andreas Tille ] * New upstream version Closes: #1053774, #1054684 * Remove constraints unnecessary since bullseye (oldstable): + libspdlog1.10: Drop conflict with removed package nheko (<< 0.7.2-3+b1) in Breaks. . [ Andrius Merkys ] * Apply upstream patch to fix tests. * Adapt to soversion change. Checksums-Sha1: 671d145a33d4b50ff28208ce79b800f0d755ab1c 2179 spdlog_1.12.0+ds-1~exp.dsc 60b7a204b455746aebeb5f336fd39e74d59a4ea8 90352 spdlog_1.12.0+ds.orig.tar.xz 3d22c8de209630e62d6d74eadcd5e62110b6e9ca 7472 spdlog_1.12.0+ds-1~exp.debian.tar.xz 65e4d3fd4b2f82b2322af270035a459eb03b90f3 85152 libspdlog-dev_1.12.0+ds-1~exp_amd64.deb c3a89f3859eadde072ec6943dd83508ec36bf78e 2105064 libspdlog1.12-dbgsym_1.12.0+ds-1~exp_amd64.deb b0c981127d9782e7e586d4603ff3681ab0549cd1 135196 libspdlog1.12_1.12.0+ds-1~exp_amd64.deb 888b7f89e97f91fb10658d41931829f93fd74459 8932 spdlog_1.12.0+ds-1~exp_amd64.buildinfo Checksums-Sha256: 4921d6f501f28b8158000d8416d4c2d4081596aca905c9f21f1b17a5f6dc6e56 2179 spdlog_1.12.0+ds-1~exp.dsc b74b560d021ce4d49a4e68e320a6044e7af91124aa2e12a93357ed888c4cf328 90352 spdlog_1.12.0+ds.orig.tar.xz 55d162ba732e5d743f2eee9aa26f86b0cf4b0e08f2454b61b84f555805581451 7472 spdlog_1.12.0+ds-1~exp.debian.tar.xz 04a4fce7544248f7d3bdb2242e215967de73c19e550b5c94c5b28cb8d699f6da 85152 libspdlog-dev_1.12.0+ds-1~exp_amd64.deb 8094b62928cf9b372dd2ff82c2763b7541f9f796516265c0d92775e560bb4512 2105064 libspdlog1.12-dbgsym_1.12.0+ds-1~exp_amd64.deb a9d72d8ac70cd994b93e539d6a1f242a3c883e006aa144995dcdb262ce9c7519 135196 libspdlog1.12_1.12.0+ds-1~exp_amd64.deb 65cf400f74bb1cc45600fa4bb9fc543035c4974b7ac68855f32bc989b7bcf156 8932 spdlog_1.12.0+ds-1~exp_amd64.buildinfo Files: cd6b02bb40373462518a3d1f98e04446 2179 libdevel optional spdlog_1.12.0+ds-1~exp.dsc 3d1f07fa49d443a4b20e5c4edfd16005 90352 libdevel optional spdlog_1.12.0+ds.orig.tar.xz 2eb1c0c394d28eb8f857917575c85519 7472 libdevel optional spdlog_1.12.0+ds-1~exp.debian.tar.xz 8f5705cdaf0f5eaf6a7404741306d4e8 85152 libdevel optional libspdlog-dev_1.12.0+ds-1~exp_amd64.deb 8e3929d693754fd54aec7dc2312b6e1d 2105064 debug optional libspdlog1.12-dbgsym_1.12.0+ds-1~exp_amd64.deb 843f228d5e6838cd3443ab06f77a3631 135196 libs optional libspdlog1.12_1.12.0+ds-1~exp_amd64.deb a29fa8ed920352d219332dd318f69bd4 8932 libdevel optional spdlog_1.12.0+ds-1~exp_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmVRyV0SHG1lcmt5c0Bk
Processed: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed.
Processing control commands: > close -1 1.0.15136.3-1 Bug #1055874 [src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed. Marked as fixed in versions intel-graphics-compiler/1.0.15136.3-1. Bug #1055874 [src:intel-graphics-compiler] intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed. Marked Bug as done -- 1055874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055874: intel-graphics-compiler: FTBFS in bookworm: Assertion `SupportedIntrinsics.find(CPU) != SupportedI,ntrinsics.end() && "Unknown Platform"' failed.
Package: src:intel-graphics-compiler Version: 1.0.12504.6-1 Severity: serious Tags: ftbfs bookworm Control: close -1 1.0.15136.3-1 Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build with the following error: cd /<>/build/IGC/VectorCompiler/lib/BiF && ../../../Release/vcb -o VCEmulation64_SKL.vc cg.bc -cpu SKL VCEmulation64.opt.bc cd /<>/build/IGC/VectorCompiler/lib/BiF && ../../../Release/vcb -o VCEmulation64_BDW.vc cg.bc -cpu BDW VCEmulation64.opt.bc vcb: ./GenXIntrinsics/lib/GenXIntrinsics/GenXIntrinsics.cpp:476: bool llvm::GenXIntrinsic::isSupport edPlatform(const std::string&, unsigned int): Assertion `SupportedIntrinsics.find(CPU) != SupportedI ntrinsics.end() && "Unknown Platform"' failed. vcb: ./GenXIntrinsics/lib/GenXIntrinsics/GenXIntrinsics.cpp:476: bool llvm::GenXIntrinsic::isSupport edPlatform(const std::string&, unsigned int): Assertion `SupportedIntrinsics.find(CPU) != SupportedI ntrinsics.end() && "Unknown Platform"' failed. Aborted Aborted make[3]: *** [IGC/VectorCompiler/lib/BiF/CMakeFiles/VCBiFPreparation.dir/build.make:230: IGC/VectorC ompiler/lib/BiF/VCEmulation64_SKL.vccg.bc] Error 134 make[3]: *** Waiting for unfinished jobs make[3]: *** [IGC/VectorCompiler/lib/BiF/CMakeFiles/VCBiFPreparation.dir/build.make:170: IGC/VectorCompiler/lib/BiF/VCEmulation64_BDW.vccg.bc] Error 134 make[3]: Leaving directory '/<>/build' I get this error on virtual machines from three different cloud vendors (Hetzner, GCP and AWS), and the same thing happens here: https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/intel-graphics-compiler_1.0.12504.6-1.rbuild.log.gz so I believe this is a general problem. However, if you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. Also, if this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Processed: 1053774 and 1054684 are pending
Processing commands for cont...@bugs.debian.org: > tag 1053774 + pending Bug #1053774 [src:spdlog] spdlog: need new upstream release 1.12 for catch2 v3 Added tag(s) pending. > tag 1054684 + pending Bug #1054684 [src:spdlog] spdlog: FTBFS: includes.h:3:10: fatal error: catch2/catch.hpp: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053774 1054684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024079: uvloop FTBFS on IPV6-only buildds
It looks like the test_aiohttp.py test is using hardcoded IPv4 addresses, causing the test to fail on hosts where no IPv4 interfaces are available. The attached patch should make the test agnostic to IP version. Best regards, Dale Richards aiohttp-test-IPv6-fix.patch Description: Binary data publickey - dale@dalerichards.net - 51198588.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#1042609: sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError')
Hi, This is now RC, which means sphinxcontrib-mermaid has been marked for autoremoval, including its reverse dependencies (one of which I maintain). On Sun, Jul 30, 2023 at 08:30:07PM +0200, Lucas Nussbaum wrote: > sphinxcontrib-mermaid fails to build with Sphinx 7.1 and docutils 0.20, both > of which > are currently available in experimental. > > Relevant part (hopefully): > [...] > > [2Kreading sources... [ 50%] index > > > > Mermaid error: > > Could not import sphinx.util.SphinxParallelError (exception: No module > > named 'sphinx.util.SphinxParallelError') Upstream commit 6f8de39¹, the only commit since 0.9.2, replaces sphinx.util.SphinxParallelError by sphinx.util.DownloadFiles. I've verified that backporting this commit makes the package build successfully in unstable, with Sphinx 7.2.6-2. However, the very same commit changes requirements.txt from "Sphinx>=3.2.1" to "Sphinx<7". I'm not sure why. I'm not using, nor am I familiar with this plugin, so I was hoping someone else that is could perhaps validate whether besides being able to be built, the package actually works. Hope this helps, Faidon 1: https://github.com/mgaitan/sphinxcontrib-mermaid/commit/6f8de39a84fddc398542e9d4dc74ba55101e7d5e
Processed: unarchive
Processing commands for cont...@bugs.debian.org:
> unarchive 993014
Bug #993014 {Done: Michael Tokarev } [src:cifs-utils]
cifs-utils non-parallel FTBFS
Unarchived Bug 993014
> tags 993014 + bullseye
Bug #993014 {Done: Michael Tokarev } [src:cifs-utils]
cifs-utils non-parallel FTBFS
Added tag(s) bullseye.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
993014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
