Bug#1061744: ipyparallel ftbfs with Python 3.12 as default

Hi, I cannot reproduce this error. Seems to be that in sid does not fail. -- cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 ⠈⠳⣄ signature.asc Description: PGP signature

Bug#1064612: rust-ahash: Failing autopkgtests

Source: rust-ahash Version: 0.8.8-2 Severity: serious rust-ahash is unable to migrate to Testing because its autopkgtests are failing: https://qa.debian.org/excuses.php?package=rust-ahash Thank you, Jeremy Bícha

Bug#1064613: vtun: Segmentation fault with default config

Package: vtun Version: 3.0.4-2+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: lucaslopez5...@gmail.com Dear Maintainer, I copied the example server file /usr/share/doc/vtun/examples/vtund-server.conf into /etc/vtund.conf and enabled server mode in /etc/default/vtun. Whe

Bug#1064565: marked as done (chromaprint: FTBFS on armel and armhf: double free or corruption (!prev))

Your message dated Sat, 24 Feb 2024 22:49:29 + with message-id and subject line Bug#1064565: fixed in chromaprint 1.5.1-5 has caused the Debian Bug report #1064565, regarding chromaprint: FTBFS on armel and armhf: double free or corruption (!prev) to be marked as done. This means that you cl

Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard

On Mon, 19 Feb 2024 23:16:44 +0100 "Xavier G." wrote: > Dear Maintainer, > > I confirm this issue. > I experienced it with an AMD R7 240 graphics card[1] on a regular Debian > Sid host running kernel 6.6.15. > Booting with the previous kernel (6.6.13) did not change the situation > but I confirm

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On 01/02/2024 00:36, Paul Eggert wrote: On 1/31/24 06:06, Pádraig Brady wrote: To my mind the most protective option takes precedence. That's not how POSIX works with mv -i and mv -f. The last flag wins. I assume this is so that people can have aliases or shell scripts that make -i the default

Processed: Re: synfig: NMU diff for 64-bit time_t transition

Processing control commands: > tags -1 - pending Bug #1063004 [src:synfig] synfig: NMU diff for 64-bit time_t transition Ignoring request to alter tags of bug #1063004 to the same tags previously set > severity -1 serious Bug #1063004 [src:synfig] synfig: NMU diff for 64-bit time_t transition Seve

Processed: severity of 1062879 is serious

Processing commands for cont...@bugs.debian.org: > severity 1062879 serious Bug #1062879 [src:safeclib] safeclib: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062879: https://bugs

Bug#1058363: marked as done (pydoctor: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

Your message dated Sat, 24 Feb 2024 19:06:07 + with message-id and subject line Bug#1058363: fixed in pydoctor 23.9.1-1 has caused the Debian Bug report #1058363, regarding pydoctor: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code

Bug#1063640: marked as done (adwaita-icon-theme: cursor theme not found)

Your message dated Sat, 24 Feb 2024 18:34:26 + with message-id and subject line Bug#1063640: fixed in mutter 45.3-3 has caused the Debian Bug report #1063640, regarding adwaita-icon-theme: cursor theme not found to be marked as done. This means that you claim that the problem has been dealt w

Processed: src:aflplusplus: fails to migrate to testing for too long: Build-Depends not available on mips64el

Processing control commands: > close -1 4.09c-1 Bug #1064590 [src:aflplusplus] src:aflplusplus: fails to migrate to testing for too long: Build-Depends not available on mips64el Marked as fixed in versions aflplusplus/4.09c-1. Bug #1064590 [src:aflplusplus] src:aflplusplus: fails to migrate to te

Bug#1064590: src:aflplusplus: fails to migrate to testing for too long: Build-Depends not available on mips64el

Source: aflplusplus Version: 4.08c-1 Severity: serious Control: close -1 4.09c-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1036828: marked as done (debian-cd: wrong firmware archives built and published for D-I releases?)

Your message dated Sat, 24 Feb 2024 14:46:14 + with message-id <20240224144614.ga3076...@tack.einval.com> and subject line Re: Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases? has caused the Debian Bug report #1036828, regarding debian-cd: wrong firmware ar

Bug#1063596: flint: FTBFS on amd64: test segfault

Hi, I just compiled the package without any issue. A case of eigenbug where you compile three times and it only fails one? Cheers, J.Puydt

Bug#1056813: marked as done (macs: ftbfs with cython 3.0.x)

Your message dated Sat, 24 Feb 2024 12:55:11 + with message-id and subject line Bug#1056813: fixed in macs 3.0.1-1 has caused the Debian Bug report #1056813, regarding macs: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases?

Followup-For: Bug #1036828 X-Debbugs-Cc: k...@debian.org On Sat, 24 Feb 2024 11:01:31 +, I wrote: > Should this bug be closed? (the logic to skip the experimental/sid firmware > image build during non-testing builds is in place for both bookworm and > trixie) Nope, it looks like I've misund

Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases?

Followup-For: Bug #1036828 X-Debbugs-Cc: k...@debian.org Hi Cyril, Should this bug be closed? (the logic to skip the experimental/sid firmware image build during non-testing builds is in place for both bookworm and trixie) Regards, James

Processed: squid-deb-proxy severity 1009067 normal

Processing commands for cont...@bugs.debian.org: > severity 1009067 normal Bug #1009067 [squid-deb-proxy-client] DeprecationWarning: The asyncore module is deprecated and will be removed in Python 3.12. Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please cont

Processed: squid-deb-proxy severity 1009067 grave

Processing commands for cont...@bugs.debian.org: > severity 1009067 grave Bug #1009067 [squid-deb-proxy-client] DeprecationWarning: The asyncore module is deprecated and will be removed in Python 3.12. Severity set to 'grave' from 'normal' > End of message, stopping processing here. Please conta

Processed: tagging 1064553

Processing commands for cont...@bugs.debian.org: > tags 1064553 + sid trixie Bug #1064553 [src:libgdiplus] libgdiplus: build-error on current sid (all warnings being treated as errors) Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1

Processed: tagging 1064555, tagging 1064556, tagging 1064557, tagging 1064558, tagging 1064560, tagging 1064561

Processing commands for cont...@bugs.debian.org: > tags 1064555 + sid trixie Bug #1064555 [src:faketime] faketime: FTBFS on 32 bit architectures: Test Suites summary: 3 succeeded, 1 failed Added tag(s) trixie and sid. > tags 1064556 + sid trixie Bug #1064556 [src:hepmc3] hepmc3: FTBFS on i386: 86

Bug#1064565: chromaprint: FTBFS on armel and armhf: double free or corruption (!prev)

Source: chromaprint Version: 1.5.1-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org cd /<>/obj-arm-linux-gnueabi/tests && ./all_tests [==] Running 94 tests from 25 test suites. [--] Glo

Processed: rustup has an undeclared file conflict

Processing control commands: > affects -1 + rust-mozilla-gdb rust-mozilla-lldb rust-web-clippy rust-web-gdb > rust-web-lldb rustfmt-web Bug #1064564 [rustup] rustup has an undeclared file conflict Added indication that 1064564 affects rust-mozilla-gdb, rust-mozilla-lldb, rust-web-clippy, rust-we

Bug#1064563: libstd-rust-1.70 has an undeclared file conflict

Package: libstd-rust-1.70 Version: 1.70.0+dfsg1-7 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libstd-rust-web-1.70 libstd-rust-1.70 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux

Processed: libstd-rust-1.70 has an undeclared file conflict

Processing control commands: > affects -1 + libstd-rust-web-1.70 Bug #1064563 [libstd-rust-1.70] libstd-rust-1.70 has an undeclared file conflict Added indication that 1064563 affects libstd-rust-web-1.70 -- 1064563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064563 Debian Bug Tracking S

Bug#1064564: rustup has an undeclared file conflict

Package: rustup Version: 1.26.0-4 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + rust-mozilla-gdb rust-mozilla-lldb rust-web-clippy rust-web-gdb rust-web-lldb rustfmt-web rustup has an undeclared file conflict. This may result in an unpack error fr

Processed: 4 packages from rustc-web have an undeclared file conflict

Processing control commands: > affects -1 + libstd-rust-mozilla-dev-windows rust-mozilla-gdb > rust-mozilla-lldb rust-mozilla-src Bug #1064562 [rust-web-gdb,libstd-rust-web-dev-windows,rust-web-src,rust-web-lldb] 4 packages from rustc-web have an undeclared file conflict Added indication that 1

Bug#1064562: 4 packages from rustc-web have an undeclared file conflict

Package: rust-web-gdb,libstd-rust-web-dev-windows,rust-web-src,rust-web-lldb Version: 1.70.0+dfsg1-7~deb12u1 Severity: serious Tags: bookworm User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libstd-rust-mozilla-dev-windows rust-mozilla-gdb rust-mozilla-lldb rust-mozill

Bug#1064561: dune-grid: FTBFS on i386: 98% tests passed, 1 tests failed out of 66

Source: dune-grid Version: 2.9.0-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=dune-grid&arch=i386&ver=2.9.0-2%2Bb1&stamp=1704501448&raw=0 14/66 Test

Bug#1064560: ucommon: FTBFS on armel and armhf: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: ucommon Version: 7.0.1-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=ucommon&arch=armhf&ver=7.0.1-0.1%2Bb1&stamp=1707541460&raw=0 dpkg-gensy

Bug#1064559: pmdk: FTBFS on ppc64el: RUNTESTS: stopping: obj_basic_integration/TEST5 failed, TEST=check FS=pmem BUILD=debug

Source: pmdk Version: 1.13.1-1.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=pmdk&arch=ppc64el&ver=1.13.1-1.1%2Bb1&stamp=1708597682&raw=0 obj_basic_in

Bug#1064558: node-leveldown: FTBFS on mips64el: not ok 1397 Error: batch(array) element must be an object and not `null`

Source: node-leveldown Version: 5.6.0+dfsg-4 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=node-leveldown&arch=mips64el&ver=5.6.0%2Bdfsg-4%2Bb1&stamp=170

Bug#1064557: lodepng: FTBFS on 32 bit architectures: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: lodepng Version: 0.0~git20220618.b4ed2cd-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=lodepng&arch=i386&ver=0.0%7Egit20220618.b4ed2cd-3%2Bb1&s

Bug#1064556: hepmc3: FTBFS on i386: 86% tests passed, 2 tests failed out of 14

Source: hepmc3 Version: 3.1.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=hepmc3&arch=i386&ver=3.1.2-2%2Bb1&stamp=1707514176&raw=0 test 5 Star

Processed: Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Processing control commands: > severity -1 serious Bug #1060104 [src:dcmtk] dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100) Severity set to 'serious' from 'important' -- 1060104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060104 Debian Bug Tracking System Contact ow.

Bug#1064555: faketime: FTBFS on 32 bit architectures: Test Suites summary: 3 succeeded, 1 failed

Source: faketime Version: 0.9.10-2.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=faketime&arch=armel&ver=0.9.10-2.1%2Bb1&stamp=1704500126&raw=0 gcc -c

Bug#1061984: marked as done (libboinc-app7t64 and libboinc7t64 have an undeclared file conflict)

Your message dated Sat, 24 Feb 2024 08:41:48 + with message-id and subject line Bug#1061984: fixed in boinc 7.24.1+dfsg-2exp2 has caused the Debian Bug report #1061984, regarding libboinc-app7t64 and libboinc7t64 have an undeclared file conflict to be marked as done. This means that you claim