Processed: golang-github-pion-webrtc.v3 accesses the internet during build

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > affects -1 buildd.debian.org Bug #1070410 [src:golang-github-pion-webrtc.v3] golang-github-pion-webrtc.v3 accesses the internet during build Added indication that 1070410 affects buildd.debian.org -- 1070410:

Bug#1070410: golang-github-pion-webrtc.v3 accesses the internet during build

2024-05-04 Thread Jochen Sprickerhof
Source: golang-github-pion-webrtc.v3 Version: 3.1.56-2 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-pion-webrtc.v3 attempts network access during build. This is forbidden by Policy

Bug#1070409: golang-github-pion-ice.v2: accesses the internet during build

2024-05-04 Thread Jochen Sprickerhof
Source: golang-github-pion-ice.v2 Version: 2.3.1-1 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-pion-ice.v2 attempts network access during build. This is forbidden by Policy 4.9:

Processed: golang-github-pion-ice.v2: accesses the internet during build

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > affects -1 buildd.debian.org Bug #1070409 [src:golang-github-pion-ice.v2] golang-github-pion-ice.v2: accesses the internet during build Added indication that 1070409 affects buildd.debian.org -- 1070409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070409

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-05-04 Thread Shmerl
On Sat, 4 May 2024 21:10:10 +0300 Jussi Pakkanen wrote: > The script runs fine on x64_64 but fails on arm64 (and probably also > x86, but I did not test it). This would imply something wonky going on > in the toolchain. The question then becomes where this should be > reported to. May be for

Bug#1068390: marked as done (src:translate-toolkit: unsatisfied build dependency in testing: python3-levenshtein)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 11:25:12 +1000 with message-id and subject line Re: Bug#1068390: src:translate-toolkit: unsatisfied build dependency in testing: python3-levenshtein has caused the Debian Bug report #1068390, regarding src:translate-toolkit: unsatisfied build dependency in

Processed: Re: slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration]

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch pending Bug #1066213 [src:slrn] slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration] Added tag(s) pending and patch. -- 1066213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066213

Bug#1066213: slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration]

2024-05-04 Thread Andreas Beckmann
Followup-For: Bug #1066213 Control: tag -1 patch pending Hi, this was fixed and tagged in git a week ago, but so far no upload happened. Andreas

Bug#1061216: Please upgrade to llvm-toolchain-17

2024-05-04 Thread Gregor Riepl
As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -17. This package depends on 14. Not possible at this time. Trying to build openvdb 10.0.1 against LLVM 17 results in the following error: CMake Error at

Bug#1070403: marked as done (does not start because of an "OpenSSL version mismatch")

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 23:54:29 + with message-id and subject line Bug#1070403: fixed in openssh-ssh1 1:7.5p1-17 has caused the Debian Bug report #1070403, regarding does not start because of an "OpenSSL version mismatch" to be marked as done. This means that you claim that the

Bug#1061205: marked as done (qt6-tools: Please upgrade to llvm-toolchain-18)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 23:30:08 + with message-id and subject line Bug#1061205: fixed in qt6-tools 6.4.2-4 has caused the Debian Bug report #1061205, regarding qt6-tools: Please upgrade to llvm-toolchain-18 to be marked as done. This means that you claim that the problem has

Processed: Bug#1070403 marked as pending in openssh-ssh1

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070403 [openssh-client-ssh1] does not start because of an "OpenSSL version mismatch" Added tag(s) pending. -- 1070403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070403 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1070403: marked as pending in openssh-ssh1

2024-05-04 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1070403 in openssh-ssh1 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1067073: marked as done (libncursesada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:18:07 +0200 with message-id and subject line close 1067073 has caused the Debian Bug report #1067073, regarding libncursesada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed to be marked as done. This means

Bug#1067353: marked as done (anet: FTBFS: unsatisfiable build-dependencies: gnat (< 13), gnat-12)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:11:59 +0200 with message-id and subject line close 1067353 has caused the Debian Bug report #1067353, regarding anet: FTBFS: unsatisfiable build-dependencies: gnat (< 13), gnat-12 to be marked as done. This means that you claim that the problem has been

Bug#1069469: marked as done (libahven-dev not installable on armhf)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:14:03 +0200 with message-id and subject line close 1067224 1069469 has caused the Debian Bug report #1069469, regarding libahven-dev not installable on armhf to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1067224: marked as done (libahven ftbfs on time_t64 architectures)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:14:03 +0200 with message-id and subject line close 1067224 1069469 has caused the Debian Bug report #1067224, regarding libahven ftbfs on time_t64 architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1069421: marked as done (dbusada: FTBFS on armhf: build-dependency not installable: libahven-dev)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:03:28 +0200 with message-id and subject line close 1069421 has caused the Debian Bug report #1069421, regarding dbusada: FTBFS on armhf: build-dependency not installable: libahven-dev to be marked as done. This means that you claim that the problem has been

Bug#1069468: marked as done (pcscada: FTBFS on armhf: build-dependency not installable: libahven-dev)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:00:06 +0200 with message-id and subject line close 1069468 has caused the Debian Bug report #1069468, regarding pcscada: FTBFS on armhf: build-dependency not installable: libahven-dev to be marked as done. This means that you claim that the problem has been

Bug#1069454: marked as done (libalog: FTBFS on armhf: build-dependency not installable: libahven-dev)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 01:01:38 +0200 with message-id and subject line close 1069454 has caused the Debian Bug report #1069454, regarding libalog: FTBFS on armhf: build-dependency not installable: libahven-dev to be marked as done. This means that you claim that the problem has been

Bug#1069467: marked as done (gprbuild: FTBFS on armhf: unsatisfiable build-dependencies: gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gna

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 00:57:42 +0200 with message-id and subject line close 1069467 has caused the Debian Bug report #1069467, regarding gprbuild: FTBFS on armhf: unsatisfiable build-dependencies: gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16,

Bug#1067629: marked as done (FTBFS: Build killed with signal TERM after 150 minutes of inactivity)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 00:53:19 +0200 with message-id and subject line close 1067629 has caused the Debian Bug report #1067629, regarding FTBFS: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been

Bug#1070403: does not start because of an "OpenSSL version mismatch"

2024-05-04 Thread Tommaso Colombo
Package: openssh-client-ssh1 Version: 1:7.5p1-16 Severity: grave X-Debbugs-Cc: acct.deb...@tmcl.it Any attempt to use ssh1 fails with: "OpenSSL version mismatch. Built against 30100050, you have 30200020" It looks like the cause is an runtime check of the OpenSSL version, which requires that

Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

2024-05-04 Thread Andreas Beckmann
Followup-For: Bug #1068665 Control: tag -1 pending Hi, in order to make progress with the t64 transition, I've uploaded Emanuele's patch as a NMU to DELAYED/2. Please let me know if I should delay it longer. Andreas

Processed: Re: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068665 [src:cfengine3] cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed Added tag(s) pending. -- 1068665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 21:17:14 + with message-id and subject line Bug#1064516: fixed in ruby-rack 2.2.7-1.1 has caused the Debian Bug report #1064516, regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 to be marked as done. This means that you claim that the

Processed: sqlite3 breaks tracker autopkgtest: killed by signal 6 SIGABRT

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 sqlite3/3.45.3-1 Bug #1070401 [src:sqlite3, src:tracker] sqlite3 breaks tracker autopkgtest: killed by signal 6 SIGABRT Marked as found in versions sqlite3/3.45.3-1. > found -1 tracker/3.4.2-3 Bug #1070401 [src:sqlite3, src:tracker] sqlite3 breaks tracker

Bug#1069344: marked as done (netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test])

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 21:50:00 +0200 with message-id <4767c8c8-976b-58b1-1a5a-af75d7c2c...@debian.org> and subject line Re: netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test] has caused the Debian Bug report #1069344, regarding netgen: FTBFS on armhf [debian/rules:66:

Bug#1063077: marked as done (syslog-ng: identified for time_t transition but no ABI in shlibs)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 19:34:39 + with message-id and subject line Bug#1063077: fixed in syslog-ng 4.4.0-1 has caused the Debian Bug report #1063077, regarding syslog-ng: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you claim that

Bug#1070365: marked as done (lyskom-elisp-client: FTBFS: tries to write to /usr/local)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 19:30:10 + with message-id and subject line Bug#1070365: fixed in lyskom-elisp-client 0.48+git.20231226.364902c3-3 has caused the Debian Bug report #1070365, regarding lyskom-elisp-client: FTBFS: tries to write to /usr/local to be marked as done. This

Bug#1069535: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure retu

2024-05-04 Thread Otto Kekäläinen
control: forward -1 https://github.com/codership/galera/issues/659 control: forwarded -1 https://github.com/codership/galera/issues/659

Processed (with 1 error): Re: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--outpu

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > forward -1 https://github.com/codership/galera/issues/659 Unknown command or malformed arguments to command. > forwarded -1 https://github.com/codership/galera/issues/659 Bug #1069535 [src:galera-3] galera-3: FTBFS on armel: dh_auto_test: error: cd

Processed: tagging 1070370, found 1070370 in 1.3a-3, found 1070370 in 1.3a-1.2, found 1070370 in 1.3a-1.1 ...

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1070370 + upstream Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837 Added tag(s) upstream. > found 1070370 1.3a-3 Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837 Marked as found in

Bug#1069535: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure retu

2024-05-04 Thread Otto Kekäläinen
Forwarded: https://github.com/codership/galera/issues/659

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

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1062896 shishi/1.0.3-2 Bug #1062896 {Done: Simon Josefsson } [src:shishi] shishi: NMU diff for 64-bit time_t transition No longer marked as found in versions shishi/1.0.3-2. > End of message, stopping processing here. Please contact me

Processed: severity of 1021656 is serious

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1021656 serious Bug #1021656 [tt-rss] please package new upstream release Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1021656:

Processed: Re: Bug#1064486: rnp: FTBFS: Errors while running CTest

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1064486 0.16.3-1 Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest Marked as found in versions rnp/0.16.3-1. > tags 1064486 + ftbfs bookworm trixie sid Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest Added tag(s)

Processed: severity of 1054608 is serious

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1054608 serious Bug #1054608 [tt-rss] tt-rss: New entries always marked as read even if the unread counter is not null Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#1064486: rnp: FTBFS: Errors while running CTest

2024-05-04 Thread Santiago Vila
found 1064486 0.16.3-1 tags 1064486 + ftbfs bookworm trixie sid thanks El 20/4/24 a las 14:12, Andreas Metzler escribió: FWIW I also get testsuite errors on current sid on amd64 The following tests FAILED: 83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed) 90 -

Processed: pistache: Please disable network tests in bookworm as well

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.0.5+ds-4 Bug #1070397 [src:pistache] pistache: Please disable network tests in bookworm as well Marked as fixed in versions pistache/0.0.5+ds-4. -- 1070397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070397 Debian Bug Tracking System Contact

Bug#1070397: pistache: Please disable network tests in bookworm as well

2024-05-04 Thread Santiago Vila
Package: src:pistache Version: 0.0.5+ds-3 Severity: serious Tags: bookworm ftbfs Control: fixed -1 0.0.5+ds-4 Dear maintainer: Please disable network tests in bookworm as well, as they have started to fail even when network access is allowed during build: [ RUN ] net_test.address_creation

Bug#1069337: marked as done (Update Depends for the time64 library renames)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 18:58:46 + with message-id and subject line Bug#1069337: fixed in thunderbird 1:125.0~b3-1 has caused the Debian Bug report #1069337, regarding Update Depends for the time64 library renames to be marked as done. This means that you claim that the problem

Bug#1070395: tinyproxy: CVE-2023-40533 CVE-2023-49606

2024-05-04 Thread Moritz Mühlenhoff
Source: tinyproxy X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for tinyproxy. CVE-2023-40533[0]: | An uninitialized memory use vulnerability exists in Tinyproxy 1.11.1 | while parsing HTTP requests. In certain

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-05-04 Thread Jussi Pakkanen
On Sat, 4 May 2024 at 13:27, Jussi Pakkanen wrote: > Disabling tests is also not a great because it just hides the bug. > Thus other packages that actually use this functionality are going to > hit this eventually and file more bugs on Meson. That is a waste of > everybody's time and energy. I

Processed: Re: libkkc: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: Marisa.gir] Error 1

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1060951 1.78.1-15 Bug #1060951 [src:gobject-introspection] Build regression in multiarch g-ir-scanner Marked as found in versions gobject-introspection/1.78.1-15. > End of message, stopping processing here. Please contact me if you need

Bug#1070388: jupyterhub: CVE-2024-28233

2024-05-04 Thread Moritz Mühlenhoff
Source: jupyterhub X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for jupyterhub. CVE-2024-28233[0]: | JupyterHub is an open source multi-user server for Jupyter | notebooks. By tricking a user into visiting a malicious

Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391

2024-05-04 Thread Moritz Mühlenhoff
Source: gdcm X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for gdcm. These are fixed in 3.0.24: CVE-2024-25569[0]: | An out-of-bounds read vulnerability exists in the | RAWCodec::DecodeBytes functionality of Mathieu

Bug#1066032: marked as done (pygobject: FTBFS on armhf: time_t build test failure)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 16:50:02 + with message-id and subject line Bug#1066032: fixed in gobject-introspection 1.80.1-2 has caused the Debian Bug report #1066032, regarding pygobject: FTBFS on armhf: time_t build test failure to be marked as done. This means that you claim that

Bug#1066900: marked as done (g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 16:50:02 + with message-id and subject line Bug#1066900: fixed in gobject-introspection 1.80.1-2 has caused the Debian Bug report #1066900, regarding g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes to be marked as

Bug#1066470: marked as done (kxl: FTBFS: KXLsound.c:75:9: error: implicit declaration of function 'read'; did you mean 'fread'? [-Werror=implicit-function-declaration])

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 16:36:08 + with message-id and subject line Bug#1066470: fixed in kxl 1.2.4-1 has caused the Debian Bug report #1066470, regarding kxl: FTBFS: KXLsound.c:75:9: error: implicit declaration of function 'read'; did you mean 'fread'?

Processed: notfound 1068068 in bobcat/6.04.00-1, notfound 1068068 in bobcat/11.01.02-1

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1068068 bobcat/6.04.00-1 Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] Need rebootstrapping on armel and armhf Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] bisonc++: FTBFS on armel, armhf

Bug#1070343: openfortivpn: stopped working after today's upgrade in Debian testing

2024-05-04 Thread Francesco Poli
Control: severity -1 important Control: retitle -1 please warn users about the option --pppd-accept-remote needed for ppp >= 2.5.0 On Sat, 04 May 2024 00:23:32 +0200 Francesco Poli (wintermute) wrote: [...] > Peer refused to agree to his IP address [...] I tried to downgrade ppp to version

Processed: Re: Bug#1070343: openfortivpn: stopped working after today's upgrade in Debian testing

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1070343 [openfortivpn] openfortivpn: stopped working after today's upgrade in Debian testing Severity set to 'important' from 'grave' > retitle -1 please warn users about the option --pppd-accept-remote needed for > ppp >= 2.5.0 Bug

Bug#1069490: marked as done (superlu-dist: FTBFS on armhf: tests fail)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 18:02:19 +0200 with message-id <5d090b3553aabb32fae284d4d4c87...@debian.org> and subject line Re: Bug#1069490 superlu-dist: FTBFS on armhf: tests fail has caused the Debian Bug report #1069490, regarding superlu-dist: FTBFS on armhf: tests fail to be marked as

Bug#1069472: marked as done (mpi4py-fft: FTBFS on armhf: tests fail)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 18:03:56 +0200 with message-id <9752a5007e505b40ac4ff58c858c3...@debian.org> and subject line Re: Bug#1069472 mpi4py-fft: FTBFS on armhf: tests fail has caused the Debian Bug report #1069472, regarding mpi4py-fft: FTBFS on armhf: tests fail to be marked as done.

Processed: Re: scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: execute_after_dh_auto_install] Error 1

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 ftbfs Bug #1069377 [src:scipy] scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: execute_after_dh_auto_install] Error 1 Ignoring request to alter tags of bug #1069377 to the same tags previously set -- 1069377:

Bug#1069377: scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: execute_after_dh_auto_install] Error 1

2024-05-04 Thread Drew Parsons
Source: scipy Followup-For: Bug #1069377 Control: tags -1 ftbfs This is an odd error. Looks as if the behaviour changed in respect to which exception gets emitted. There's a new release needing to get packaged. Likely it resolves the issue.

Bug#1069445: marked as done (h5py: FTBFS on armhf: tests fail)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 17:54:42 +0200 with message-id and subject line Re: Bug#1069445 h5py: FTBFS on armhf: tests fail has caused the Debian Bug report #1069445, regarding h5py: FTBFS on armhf: tests fail to be marked as done. This means that you claim that the problem has been

Bug#1070334: marked as done (libnet-frame-device-perl needs network access during build)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 15:49:22 + with message-id and subject line Bug#1070334: fixed in libnet-frame-device-perl 1.12-2 has caused the Debian Bug report #1070334, regarding libnet-frame-device-perl needs network access during build to be marked as done. This means that you

Processed: Re: topal: FTBFS: debian/rules: debian_packaging.mk: No such file or directory

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #1067320 [src:topal] topal: FTBFS: debian/rules:8: /usr/share/ada/debian_packaging.mk: No such file or directory Added tag(s) patch. -- 1067320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067320 Debian Bug Tracking System Contact

Bug#1067320: topal: FTBFS: debian/rules: debian_packaging.mk: No such file or directory

2024-05-04 Thread Nicolas Boulenguez
Source: topal Followup-For: Bug #1067320 Control: tag -1 + patch Hello. Attachment 002 below fixes this bug. Would you be OK with a non maintainer upload? The other attachments are unrelated sugestions. Would you be OK with a salsa.debian.org/debian/topal git repository? PATH 1/10 updates the

Processed: Re: mpich: libpmix-dev only available on 64-bit architectures

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1070318 normal Bug #1070318 [src:mpich] mpich: libpmix-dev only available on 64-bit architectures Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070318:

Processed: Re: slurm-wlm-contrib: libpmix-dev only available on 64-bit architectures

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1070320 normal Bug #1070320 [src:slurm-wlm-contrib] slurm-wlm-contrib: libpmix-dev only available on 64-bit architectures Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#1070270: riseup-vpn: client no longer works due to cert verification problem

2024-05-04 Thread Nilesh Patra
Hi Matt, Quoting Matt Taggart: > Package: riseup-vpn > Version: 0.21.11+ds1-5+b1 > Severity: grave > > When attempting to run the bookworm riseup-vpn package, it fails to > connect to riseup's servers and gives the following output: > > 2024/05/01 18:21:23 Error fetching eip v3 >

Processed: Bug#1070334 marked as pending in libnet-frame-device-perl

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070334 [src:libnet-frame-device-perl] libnet-frame-device-perl needs network access during build Added tag(s) pending. -- 1070334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070334 Debian Bug Tracking System Contact

Bug#1070334: marked as pending in libnet-frame-device-perl

2024-05-04 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1070334 in libnet-frame-device-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Re: Bug#1070334: libnet-frame-device-perl needs network access during build

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1070334 [src:libnet-frame-device-perl] libnet-frame-device-perl needs network access during build Added tag(s) patch. -- 1070334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070334 Debian Bug Tracking System Contact

Bug#1070334: libnet-frame-device-perl needs network access during build

2024-05-04 Thread Étienne Mollier
Control: tags -1 + patch Étienne Mollier, on 2024-05-03: > Has someone an idea of better approach? Answering to myself, the test suite does not actually attempt to access the Internet, but it does attempt to access the device on the build machine that can route by default to 1.1.1.1. This is

Bug#1070369: sssd: CVE-2023-3758

2024-05-04 Thread Salvatore Bonaccorso
Source: sssd Version: 2.9.4-2 Severity: grave Tags: security upstream Forwarded: https://github.com/SSSD/sssd/pull/7302 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for sssd. CVE-2023-3758[0]: | A race condition flaw was found in sssd

Bug#1069984: marked as done (alire: Build-depends on NBS package libgnatcoll21-dev)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 17:00:25 +0200 with message-id and subject line Bug#1069984: alire: Build-depends on NBS package libgnatcoll21-dev has caused the Debian Bug report #1069984, regarding alire: Build-depends on NBS package libgnatcoll21-dev to be marked as done. This means that

Bug#1070365: lyskom-elisp-client: FTBFS: tries to write to /usr/local

2024-05-04 Thread Andreas Beckmann
Source: lyskom-elisp-client Version: 0.48+git.20231226.364902c3-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, lyskom-elisp-client FTBFS in the minimal chroots used by the buildds: https://buildd.debian.org/status/package.php?p=lyskom-elisp-client ... cp

Bug#1052090: marked as done (gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 46)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 14:46:23 + with message-id and subject line Bug#1070323: Removed package(s) from unstable has caused the Debian Bug report #1052090, regarding gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 46 to be marked as done. This means

Bug#1069984: alire: Build-depends on NBS package libgnatcoll21-dev

2024-05-04 Thread Nicolas Boulenguez
Source: alire Followup-For: Bug #1069984 Hello. This bug is already fixed in 1.2.1-1.1. The ideal way to close a bug is usually in debian/changelog, but this bug was open after its fix has been uploaded to experimental, so you should probably close it as described at

Processed: Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/dask/dask/pull/11035 Bug #1068422 [python3-dask] can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object Set Bug forwarded-to-address to

Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

2024-05-04 Thread Rebecca N. Palmer
Control: forwarded -1 https://github.com/dask/dask/pull/11035 Control: tags -1 fixed-upstream patch Thanks and probably yes (but I haven't tested that fix myself), as while it didn't happen in 3.11.8, it *does* happen in 3.11.9: https://ci.debian.net/packages/d/dask/unstable/amd64/46185892/

Bug#1068610: dico: binary-all FTBFS

2024-05-04 Thread Andreas Beckmann
Followup-For: Bug #1068610 Control: tag -1 pending Hi, I've taken Holgers patch and imported it into the git repository on salsa and uploaded it to DELAYED/2 to make progress with the t64 transition. Please let me know if I should delay it longer. I've also fixed building the package twice in a

Processed: Re: dico: binary-all FTBFS

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068610 [src:dico] dico: binary-all FTBFS Added tag(s) pending. -- 1068610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1068057: marked as done (libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! ))

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 15:34:59 +0200 with message-id and subject line close 1068057 has caused the Debian Bug report #1068057, regarding libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! ) to be marked as done. This means that you claim that the

Bug#1065529: marked as done (interimap: Testsuite fails with openssl 3.2)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 13:34:29 + with message-id and subject line Bug#1065529: fixed in interimap 0.5.7-3 has caused the Debian Bug report #1065529, regarding interimap: Testsuite fails with openssl 3.2 to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1070331: RFS: nq/0.5-0.1 [NMU] -- Lightweight queue system

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1005961 Bug #1070331 [sponsorship-requests] RFS: nq/0.5-0.1 [NMU] -- Lightweight queue system 1070331 was not blocked by any bugs. 1070331 was not blocking any bugs. Added blocking bug(s) of 1070331: 1005961 -- 1070331:

Bug#1066579: marked as done (yubico-pam: FTBFS: ../pam_yubico.c:657:8: error: implicit declaration of function ‘mkostemp’; did you mean ‘mkstemp’? [-Werror=implicit-function-declaration])

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 12:20:46 + with message-id and subject line Bug#1066579: fixed in yubico-pam 2.27-1 has caused the Debian Bug report #1066579, regarding yubico-pam: FTBFS: ../pam_yubico.c:657:8: error: implicit declaration of function ‘mkostemp’; did you mean ‘mkstemp’?

Bug#1059668: nmu FTBFS

2024-05-04 Thread Alexandre Detiste
Hi, I upload this to allow new paramiko to migrate. Greetings tchet@quieter:~/deb/python-icecream$ cat debian/patches/python3.12 Forwarded: https://github.com/gruns/icecream/pull/147/files --- a/tests/test_icecream.py +++ b/tests/test_icecream.py @@ -570,7 +570,7 @@

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

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 13:13:00 +0200 with message-id and subject line FTBFS has caused the Debian Bug report #1060963, regarding paramiko: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 to be marked as done. This

Bug#1061208: marked as done (rocm-hipamd: Please upgrade to llvm-toolchain-18)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 13:05:27 +0200 with message-id <3b21eee9-2a53-4e41-8ea8-2eec927dd...@debian.org> and subject line Fixed in 5.7.1-1 has caused the Debian Bug report #1061208, regarding rocm-hipamd: Please upgrade to llvm-toolchain-18 to be marked as done. This means that you

Processed: your mail

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1061216 openvdb: Please upgrade to llvm-toolchain-18 Bug #1061216 [src:openvdb] Please upgrade to llvm-toolchain-17 Changed Bug title to 'openvdb: Please upgrade to llvm-toolchain-18' from 'Please upgrade to llvm-toolchain-17'. > End of

Processed (with 1 error): retitle

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1061205 qt6-tools: Please upgrade to llvm-toolchain-18 Bug #1061205 [src:qt6-tools] Please upgrade to llvm-toolchain-17 Changed Bug title to 'qt6-tools: Please upgrade to llvm-toolchain-18' from 'Please upgrade to llvm-toolchain-17'. >

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-05-04 Thread Jussi Pakkanen
On Fri, 3 May 2024 at 06:42, Shmerl wrote: > If real solution for this requires upstream involvement, may be it's worth > disabling > these tests, until upstream is actually not broken? That would at least move > things > forward, otherwise it might be stuck for who knows how long? I am the

Bug#1069369: marked as done (lua-sec: FTBFS on arm64: ld: cannot find -lz: No such file or directory)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 10:22:32 + with message-id and subject line Bug#1069369: fixed in lua-sec 1.3.2-2 has caused the Debian Bug report #1069369, regarding lua-sec: FTBFS on arm64: ld: cannot find -lz: No such file or directory to be marked as done. This means that you claim

Bug#1070300: pmix_psquash_base_select failed during MPI_INIT on 32bit architectures

2024-05-04 Thread Samuel Thibault
Samuel Thibault, le ven. 03 mai 2024 19:00:22 +0200, a ecrit: > This has been posing migration issues for quite some time, I have > uploaded the attached fix to delayed/0. Some of the components depend on libmca_common_libdstore which also needs to be installed, otherwise openmpi emits some text

Bug#1070217: chromium: Symbol lookup error with libsnappy1v5>=1.2.0

2024-05-04 Thread Martin Steigerwald
Martin Steigerwald - 02.05.24, 16:43:28 CEST: > Work-around for affected users: Of course this work-around is no longer necessary. Thank you for the quick fix, Laszlo. I appreciate it. -- Martin

Bug#1070352: rust-err-derive: fails to build from source on all architectures

2024-05-04 Thread Jonas Smedegaard
Source: rust-err-derive Version: 0.3.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package fails to build from source om all architectures. -BEGIN PGP SIGNATURE-

Bug#1043002: marked as done (pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2024 10:49:04 +0200 with message-id <01552f84-aaaf-4a84-9886-d844f14e6...@debian.org> and subject line Re: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends has caused the Debian Bug report #1043002, regarding pdm: Please

Processed: reset severity

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1016957 wishlist Bug #1016957 [src:kbd-chooser] kbd-chooser: please add support for riscv64 Severity set to 'wishlist' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1016957:

Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

2024-05-04 Thread Preuße
Control: found -1 fq/0.9.0-2 Control: found -1 nq/0.3.1-4 On 18.02.2022 08:39, Axel Beckert wrote: Hello, Trying to install fq fails for me as follows: Preparing to unpack .../archives/fq_0.0.4-2_amd64.deb ... Unpacking fq (0.0.4-2) ... dpkg: error processing archive

Processed: Re: Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

2024-05-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 fq/0.9.0-2 Bug #1005961 {Done: Daniel Milde } [nq,fq] nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4 Marked as found in versions fq/0.9.0-2 and reopened. > found -1 nq/0.3.1-4 Bug #1005961 [nq,fq] nq,fq: trying to overwrite

Processed: unarchive Bug#1005961

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1005961 Bug #1005961 {Done: Daniel Milde } [nq,fq] nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4 Unarchived Bug 1005961 > End of message, stopping processing here. Please contact me if you need

Bug#1069878: marked as done (dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 07:49:11 + with message-id and subject line Bug#1069878: fixed in dm-writeboost 2.2.17-0.1 has caused the Debian Bug report #1069878, regarding dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’

Processed: severity of 1069538 is important

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Arch: all builds are done on amd64 buildds only > severity 1069538 normal Bug #1069538 [src:zeroc-ice] zeroc-ice: FTBFS on armel: Gradle / Java heap space Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please

Processed: found 1069439 in 3.9.1-1

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069439 3.9.1-1 Bug #1069439 [src:arpack] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1 Marked as found in versions arpack/3.9.1-1. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: severity of 1058493 is grave

2024-05-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1058493 grave Bug #1058493 [src:gamescope] gamescope: Please update to wlroots 0.17 Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1058493:

  1   2   >