Bug#1086128: [Sbcl-bugs] ppc64el changes cause error with cl-ironclad test suite

2024-12-06 Thread Paul Gevers
Hi Sean, On Sun, 24 Nov 2024 08:47:31 +0800 Sean Whitton wrote: The test execution environment is non-interactive, so we drive it using 'sbcl --script'. I *think* you're aware, but maybe I'm mixing up history: while this is true, the operators of ci.d.n (me and terceiro) can give access to

Bug#1089212: gnome-control-center:FTBFS:build failure on riscv (test-network-panel test timeout)

2024-12-06 Thread Yue Gui
Source: gnome-control-center Version: 1:47.2-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear gnome-control-center Maintainer, The package gnome-control-center build failed on riscv64 caused by test-netwo

Processed: Re: Bug#1070443 closed by Debian FTP Masters (reply to Reinhard Tartler ) (Bug#1070443: fixed in aspectc++ 1:2.3+git20241206-1)

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1070443 {Done: Reinhard Tartler } [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No long

Bug#1070443: closed by Debian FTP Masters (reply to Reinhard Tartler ) (Bug#1070443: fixed in aspectc++ 1:2.3+git20241206-1)

2024-12-06 Thread Adrian Bunk
Control: reopen -1 On Fri, Dec 06, 2024 at 01:21:04PM +, Debian Bug Tracking System wrote: >... > aspectc++ (1:2.3+git20241206-1) unstable; urgency=medium > . >* New upstream version 2.3+git20241206 >... > - Fixes build on arm64, closes: #1070443 >... > Weaving aspects into PreExprP

Bug#1089208: xmlindent FTBFS: strip: unable to copy file 'debian/xmlindent/usr/local/bin/xmlindent'; reason: Permission denied

2024-12-06 Thread Adrian Bunk
Source: xmlindent Version: 0.2.18-0.1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Alexandre Detiste https://buildd.debian.org/status/logs.php?pkg=xmlindent&ver=0.2.18-0.1 ... dh_strip dh_strip: warning: Compatibility levels before 10 are deprecated (level 9 in use) strip: unable to copy file 'd

Processed: libglbinding-dev: The link interface of target "glbinding::glbinding" contains: KHR::KHR but the target was not found.

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:forge src:globjects Bug #1089206 [libglbinding-dev] libglbinding-dev: The link interface of target "glbinding::glbinding" contains: KHR::KHR but the target was not found. Added indication that 1089206 affects src:forge and src:globjects -- 1089206:

Bug#1089206: libglbinding-dev: The link interface of target "glbinding::glbinding" contains: KHR::KHR but the target was not found.

2024-12-06 Thread Adrian Bunk
Package: libglbinding-dev Version: 3.3.0-1 Severity: serious Tags: ftbfs Control: affects -1 src:forge src:globjects https://buildd.debian.org/status/logs.php?pkg=forge&ver=1.0.1-3.1%2Bb2 https://buildd.debian.org/status/logs.php?pkg=globjects&ver=1.1.0-3%2Bb3 ... -- Configuring done (1.4s) CMake

Bug#1089204: librust-lazy-regex-dev: Autopkgtest failure for --no-default-features

2024-12-06 Thread NoisyCoil
Source: librust-lazy-regex-dev Version: 3.1.0-6 Severity: serious Tags: patch upstream Justification: RT X-Debbugs-Cc: noisyc...@tutanota.com Hi, Even after the changes in your last upload, lazy-regex failed the test with all features disabled. I'm attaching a patch to be imported with quilt that

Bug#1089181: chromium: Stable update wants to remove chromium package itself

2024-12-06 Thread Santiago Vila
Is this really a work-around? Yes, it is. (try it!) The problem is that the new chrome package is in security but some of its dependencies do not exist at all in security and are only in bookworm-proposed-updates. So you need both security + bookworm-proposed-updates. Thanks.

Bug#1089181: chromium: Stable update wants to remove chromium package itself

2024-12-06 Thread Nate Bargmann
On Fri, 6 Dec 2024 14:49:07 -0500 Andres Salomon wrote: > Hi, > > For the time being you'll have to add bookworm-proposed-updates to your > /etc/apt/sources.list. For example the following line: > > deb http://deb.debian.org/debian/ bookworm-proposed-updates main Is this really a work-around?

Processed: libqapt: FTBFS: error: expected constructor, destructor, or type conversion before ‘;’ token

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # redacted meant "the bts did not like the subject the first time", here is > the intended one: > retitle 1089202 libqapt: FTBFS: error: expected constructor, destructor, or > type conversion before ‘;’ token Bug #1089202 [src:libqapt] libqapt:

Bug#1089202: libqapt: FTBFS: redacted

2024-12-06 Thread Santiago Vila
Package: src:libqapt Version: 3.0.5-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with kf5,pkgk

Bug#1074981: gdl: FTBFS with gcc-14

2024-12-06 Thread Rebecca N. Palmer
Control: tags -1 patch Now fixes them all and builds successfully, but I have not tested the result. (gdl has no tests in the package.)

Processed: Re: Bug#1074981: gdl: FTBFS with gcc-14

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1074981 [src:gdl] gdl: ftbfs with GCC-14 Added tag(s) patch. -- 1074981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1089200: ksyntax-highlighting: FTBFS: The following tests FAILED: 4 - testhighlighter_test (Failed) 5 - htmlhighlighter_test (Failed)

2024-12-06 Thread Santiago Vila
Package: src:ksyntax-highlighting Version: 5.115.0-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1089199: binutils-sh-elf: FTBFS: error: passing argument 1 of ‘strcpy’ discards ‘const’ qualifier

2024-12-06 Thread Santiago Vila
Package: src:binutils-sh-elf Version: 2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary mkdir -p binutils dh bin

Bug#1089189: chromium: Security update 131.0.6778.108-1~deb12u1 remove chromium from bookworm (unmet dependencies)

2024-12-06 Thread Santiago Vila
Hi. Thanks for the report. Until this is fixed, there is an easy workaround, which is to add a line for "bookworm-proposed-updates" in sources.list, like this: deb http://deb.debian.org/debian bookworm-proposed-updates main Thanks.

Processed: reassign 1089130 to src:linux, forcibly merging 1087495 1089130

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1089130 src:linux Bug #1089130 [linux-headers-6.12-rc6-amd64] linux-headers-6.12-rc6-amd64: aptitude install fail with nvidia-fs/2.16 due to missing dependencies: nvidia-current Bug reassigned from package 'linux-headers-6.12-rc6-amd64'

Processed (with 1 error): forcibly merging 1087495 1089130

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1087495 1089130 Bug #1087495 [src:linux] linux-headers-6.12-rc6-common: Missing file scripts/module-common.c Bug #1087879 [src:linux] linux-kbuild-6.12-rc6 doesn't provide module-common.c Unable to merge bugs because: package of #10891

Bug#1089194: wayvnc: FTBFS: ERROR: Dependency lookup for neatvnc with method 'pkgconfig' failed: Invalid version, need 'neatvnc' ['<0.9.0'] found '0.9.1'.

2024-12-06 Thread Santiago Vila
Package: src:wayvnc Version: 0.8.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_auto

Bug#1089193: ros-image-transport-plugins: FTBFS: Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)

2024-12-06 Thread Santiago Vila
Package: src:ros-image-transport-plugins Version: 1.15.0-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh bi

Processed: forcibly merging 1089181 1089189

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1089181 1089189 Bug #1089181 [chromium] chromium: security update wants to remove chromium package itself Bug #1089182 [chromium] chromium: Cannot install on bookworm, missing abi1-19 Bug #1089189 [chromium] chromium: Security update 1

Bug#1089191: fcitx-rime: FTBFS: error: implicit declaration of function ‘RimeProcessKey’

2024-12-06 Thread Santiago Vila
Package: src:fcitx-rime Version: 0.3.2+git20230425-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1089192: golang-golang-x-net: FTBFS: FAIL: TestNumICANNRules

2024-12-06 Thread Santiago Vila
Package: src:golang-golang-x-net Version: 1:0.27.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary -

Bug#1089190: binutils-or1k-elf: FTBFS: error: passing argument 1 of ‘strcpy’ discards ‘const’ qualifier from pointer target type

2024-12-06 Thread Santiago Vila
Package: src:binutils-or1k-elf Version: 1.0.11 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary -Dsrc -

Processed (with 1 error): forcibly merging 1078556 1079105

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1078556 1079105 Bug #1078556 {Done: Matthias Klose } [bash] bash: 5.2.21-2.1 to 5.2.21-2.1+b1 breaks printf %.2f .1 Bug #1078583 {Done: Matthias Klose } [bash] bash: printf '%5.1f' 1.498 prints multiple lines of numbers Bug #1081424 {

Bug#1089031: marked as done (python-nexusformat: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 21:02:33 + with message-id and subject line Bug#1089031: fixed in python-nexusformat 1.0.6-4 has caused the Debian Bug report #1089031, regarding python-nexusformat: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim that t

Bug#1089030: marked as done (python-mouseinfo: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 21:02:25 + with message-id and subject line Bug#1089030: fixed in python-mouseinfo 0.0~git20230505000925.23791fa-3 has caused the Debian Bug report #1089030, regarding python-mouseinfo: autopkgtest failure with Python 3.13 to be marked as done. This means

Bug#1088769: marked as done (pyscreeze: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 21:01:12 + with message-id and subject line Bug#1088769: fixed in pyscreeze 0.0~git20240820225245.93f2775-6 has caused the Debian Bug report #1088769, regarding pyscreeze: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim

Bug#1088765: marked as done (pyautogui: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 21:01:03 + with message-id and subject line Bug#1088765: fixed in pyautogui 0.0~git20230607111623.b4255d0-6 has caused the Debian Bug report #1088765, regarding pyautogui: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim

Processed: tagging 1089180, notfixed 1088310 in 2.0.2-4+b2, tagging 1088310, tagging 1071050 ...

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1089180 + sid trixie Bug #1089180 [src:guzzle] guzzle: Failing tests with PHP 8.4 Added tag(s) sid and trixie. > notfixed 1088310 2.0.2-4+b2 Bug #1088310 {Done: Thibaut Paumard } [python3-gyoto] gyoto: autopkgtest failure with Python 3.13 No

Bug#1089185: liboqs: CVE-2024-54137

2024-12-06 Thread Salvatore Bonaccorso
Source: liboqs Version: 0.8.0-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for liboqs. CVE-2024-54137[0]: | liboqs is a C-language cryptographic library that provid

Bug#1086378: python-pgpy: FTBFS: Error: gpgme_op_verify: GPGME: Bad data

2024-12-06 Thread Xiyue Deng
Control: forwarded -1 https://github.com/SecurityInnovation/PGPy/issues/471 Xiyue Deng writes: > Hi, > > With much testing, I have identified that this was caused by the change > in gpgme1.0 after upgrading from 1.18.0-6+b1 to 1.23.2-5. More > specifically, gpg.Context.verify (which uses gpgme_

Bug#1088310: marked as done (gyoto: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Dec 2024 21:11:38 +0100 with message-id <38f88bc7-6f62-4eec-b2e1-4d54431fd...@debian.org> and subject line Re: Bug#1088310: gyoto: autopkgtest failure with Python 3.13 has caused the Debian Bug report #1088310, regarding gyoto: autopkgtest failure with Python 3.13 to be ma

Processed: Re: python-pgpy: FTBFS: Error: gpgme_op_verify: GPGME: Bad data

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/SecurityInnovation/PGPy/issues/471 Bug #1086378 [src:python-pgpy] python-pgpy: FTBFS: Error: gpgme_op_verify: GPGME: Bad data Set Bug forwarded-to-address to 'https://github.com/SecurityInnovation/PGPy/issues/471'. -- 1086378: http

Bug#1089182: chromium: Cannot install on bookworm, missing abi1-19

2024-12-06 Thread Michael Tokarev
On Fri, 6 Dec 2024 14:48:20 -0500 Andres Salomon wrote: Hi, For the time being you'll have to add bookworm-proposed-updates to your /etc/apt/sources.list. For example the following line: Even with bookworm-proposed-updates in place, installation of new chromium requires some force, - it can'

Processed: Re: Bug#1088310: gyoto: autopkgtest failure with Python 3.13

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1088310 python3-gyoto Bug #1088310 [src:gyoto] gyoto: autopkgtest failure with Python 3.13 Bug reassigned from package 'src:gyoto' to 'python3-gyoto'. No longer marked as found in versions gyoto/2.0.2-4. Ignoring request to alter fixed ve

Bug#1088310: gyoto: autopkgtest failure with Python 3.13

2024-12-06 Thread Thibaut Paumard
reassign 1088310 python3-gyoto notfound 1088310 2.0.2-4+b2 thanks The point is that this test was ran with with python3-defaults that includes python3.13, but this version of python3-gyoto had been built earlier with a version of python3-all-dev that did not include it. This has been fixed by

Processed: chromium: security update wants to remove chromium package itself

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1089181 1089182 Bug #1089181 [chromium] chromium: security update wants to remove chromium package itself Bug #1089182 [chromium] chromium: Cannot install on bookworm, missing abi1-19 Merged 1089181 1089182 > summary 1089181 chromium i

Bug#994171: marked as done (unable to set up jediepcserver, permission denied)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 19:49:51 + with message-id and subject line Bug#1089183: Removed package(s) from unstable has caused the Debian Bug report #994171, regarding unable to set up jediepcserver, permission denied to be marked as done. This means that you claim that the problem

Bug#1088053: marked as done (cbmplugs: Not compatible with gimp 3)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 19:50:16 + with message-id and subject line Bug#1089148: Removed package(s) from unstable has caused the Debian Bug report #1088053, regarding cbmplugs: Not compatible with gimp 3 to be marked as done. This means that you claim that the problem has been dea

Bug#1089181: chromium: Stable update wants to remove chromium package itself

2024-12-06 Thread Andres Salomon
Hi, For the time being you'll have to add bookworm-proposed-updates to your /etc/apt/sources.list. For example the following line: deb http://deb.debian.org/debian/ bookworm-proposed-updates main I'm asking the release team how best to handle this. Sorry about that! Thanks, Andres On 12/6/

Bug#1089182: chromium: Cannot install on bookworm, missing abi1-19

2024-12-06 Thread Andres Salomon
Hi, For the time being you'll have to add bookworm-proposed-updates to your /etc/apt/sources.list. For example the following line: deb http://deb.debian.org/debian/ bookworm-proposed-updates main I'm asking the release team how best to handle this. Sorry about that! Thanks, Andres On 12/6/2

Processed: chromium: security update wants to remove chromium package itself

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # a little bit more accurate > retitle 1089181 chromium: security update wants to remove chromium package > itself Bug #1089181 [chromium] chromium: Stable update wants to remove chromium package itself Changed Bug title to 'chromium: security u

Bug#1089181: chromium: Stable update wants to remove chromium package itself

2024-12-06 Thread Santiago Vila
Package: chromium Version: 131.0.6778.108-1~deb12u1 Severity: grave Hi. Today's chromium update in stable wants to remove "chromium" and "chromium-l10n": # apt-get dist-upgrade Reading package lists... Done Bu

Bug#1089182: chromium: Cannot install on bookworm, missing abi1-19

2024-12-06 Thread Paul Szabo
Package: chromium Version: 131.0.6778.108-1~deb12u1 Severity: grave Justification: renders package unusable You released version 131.0.6778.108-1~deb12u1 (with DSA-5824-1). This versions is un-installable on bookworm, was built with (Depends:) libc++1-19 (>= 1:19.1.4) libc++abi1-19 (>= 1:19.1

Bug#1089180: guzzle: Failing tests with PHP 8.4

2024-12-06 Thread Ondřej Surý
Source: guzzle Version: 7.4.5-1 Severity: serious Justification: Breaks autopkgtests for many PHP packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, the GuzzleHttp is making many packages to fail (this if from symfony): Deprecated: GuzzleHttp\Promise\queue(): Implicitly m

Bug#1087852: marked as done (ignition-cmake: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:57:14 + with message-id and subject line Bug#1088948: Removed package(s) from unstable has caused the Debian Bug report #1087852, regarding ignition-cmake: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means that

Bug#1087868: marked as done (sdformat: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:54:02 + with message-id and subject line Bug#1088941: Removed package(s) from unstable has caused the Debian Bug report #1087868, regarding sdformat: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means that you cl

Bug#1087863: marked as done (ignition-utils: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:55:50 + with message-id and subject line Bug#1088945: Removed package(s) from unstable has caused the Debian Bug report #1087863, regarding ignition-utils: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means that

Bug#1087851: marked as done (ignition-plugin: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:52:00 + with message-id and subject line Bug#1088940: Removed package(s) from unstable has caused the Debian Bug report #1087851, regarding ignition-plugin: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means tha

Bug#1087858: marked as done (ignition-fuel-tools: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:51:34 + with message-id and subject line Bug#1088939: Removed package(s) from unstable has caused the Debian Bug report #1087858, regarding ignition-fuel-tools: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means

Bug#1087732: marked as done (ppc64-diag: move aliased files from / to /usr (DEP17))

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:49:44 + with message-id and subject line Bug#1087732: fixed in ppc64-diag 2.7.9-1.1 has caused the Debian Bug report #1087732, regarding ppc64-diag: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that the proble

Bug#1088245: marked as done (django-assets: autopkgtest failure with Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:49:30 + with message-id and subject line Bug#1088245: fixed in django-assets 2.0-5 has caused the Debian Bug report #1088245, regarding django-assets: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim that the problem h

Bug#1075384: marked as done (php-pinba: ftbfs with GCC-14)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:48:11 + with message-id and subject line Bug#1088914: Removed package(s) from unstable has caused the Debian Bug report #1075384, regarding php-pinba: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1087668: marked as done (Bismuth needs porting to Plasma 6)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:46:46 + with message-id and subject line Bug#1088841: Removed package(s) from unstable has caused the Debian Bug report #1087668, regarding Bismuth needs porting to Plasma 6 to be marked as done. This means that you claim that the problem has been dealt

Bug#1071050: marked as done (kwin-bismuth: Does not work after binary-only upload as typescript transpiled incorrectly with es2022 features)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:46:46 + with message-id and subject line Bug#1088841: Removed package(s) from unstable has caused the Debian Bug report #1071050, regarding kwin-bismuth: Does not work after binary-only upload as typescript transpiled incorrectly with es2022 features to

Bug#1066682: marked as done (geekcode: FTBFS: gc_appearance.c:61:12: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:47:13 + with message-id and subject line Bug#1088856: Removed package(s) from unstable has caused the Debian Bug report #1066682, regarding geekcode: FTBFS: gc_appearance.c:61:12: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-

Bug#749899: marked as done (xflip and meltdown are almost too fast to be noticed)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:36:17 + with message-id and subject line Bug#1088737: Removed package(s) from unstable has caused the Debian Bug report #749899, regarding xflip and meltdown are almost too fast to be noticed to be marked as done. This means that you claim that the probl

Bug#1054511: marked as done (gnome-shell-extension-panel-osd: needs update for GNOME Shell 46)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:32:33 + with message-id and subject line Bug#1088078: Removed package(s) from unstable has caused the Debian Bug report #1054511, regarding gnome-shell-extension-panel-osd: needs update for GNOME Shell 46 to be marked as done. This means that you claim t

Bug#1075087: marked as done (ignition-physics: ftbfs with GCC-14)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:30:31 + with message-id and subject line Bug#1087596: Removed package(s) from unstable has caused the Debian Bug report #1075087, regarding ignition-physics: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been deal

Bug#1088121: marked as done (bridge-method-injector: FTBFS: dh_install: warning: Cannot find (any matches for) "target/site/apidocs/*")

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:24:53 + with message-id and subject line Bug#1087464: Removed package(s) from unstable has caused the Debian Bug report #1088121, regarding bridge-method-injector: FTBFS: dh_install: warning: Cannot find (any matches for) "target/site/apidocs/*" to be ma

Bug#1084090: marked as done (llvm-toolchain-16: do not release with trixie)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:21:38 + with message-id and subject line Bug#1075944: Removed package(s) from unstable has caused the Debian Bug report #1084090, regarding llvm-toolchain-16: do not release with trixie to be marked as done. This means that you claim that the problem has

Bug#1084676: marked as done (pyro4: removal of Python standard libraries in Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:22:34 + with message-id and subject line Bug#1084735: Removed package(s) from unstable has caused the Debian Bug report #1084676, regarding pyro4: removal of Python standard libraries in Python 3.13 to be marked as done. This means that you claim that th

Bug#1087870: marked as done (llvm-toolchain-16: autopkgtest regression due to new CMake deprecation warning)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:21:38 + with message-id and subject line Bug#1075944: Removed package(s) from unstable has caused the Debian Bug report #1087870, regarding llvm-toolchain-16: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means t

Bug#1084633: marked as done (llvm-toolchain-16: removal of Python standard libraries in Python 3.13)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:21:38 + with message-id and subject line Bug#1075944: Removed package(s) from unstable has caused the Debian Bug report #1084633, regarding llvm-toolchain-16: removal of Python standard libraries in Python 3.13 to be marked as done. This means that you c

Bug#1076410: marked as done (FTBFS with OCaml 5.2.0 (Uses C functions without caml_ prefix))

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 18:21:38 + with message-id and subject line Bug#1075944: Removed package(s) from unstable has caused the Debian Bug report #1076410, regarding FTBFS with OCaml 5.2.0 (Uses C functions without caml_ prefix) to be marked as done. This means that you claim tha

Processed: bug 1089069 is forwarded to https://github.com/Erotemic/ubelt/issues/161

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1089069 https://github.com/Erotemic/ubelt/issues/161 Bug #1089069 [src:ubelt] ubelt: autopkgtest failure with Python 3.13 Set Bug forwarded-to-address to 'https://github.com/Erotemic/ubelt/issues/161'. > thanks Stopping processing here.

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

2024-12-06 Thread Emanuele Rocca
On 2024-12-06 05:25, Emanuele Rocca wrote: > DEB_BUILD_MAINT_OPTIONS=-stackprotector Apologies, I meant: DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

2024-12-06 Thread Emanuele Rocca
Hi, On 2024-12-03 12:27, Andres Salomon wrote: > Currently waiting on #1088699 to fix this. On arm64 I tried building chromium 131.0.6778.85-1~deb12u1 without stack protector, and the resulting build does not crash: DEB_BUILD_MAINT_OPTIONS=-stackprotector Not ideal, but better than a chromium

Bug#1089170: marked as done (postfix-sqlite: sqlite map entry removed from dynamicmaps.cf on upgrade)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 17:22:21 + with message-id and subject line Bug#1089170: fixed in postfix 3.9.1-2 has caused the Debian Bug report #1089170, regarding postfix-sqlite: sqlite map entry removed from dynamicmaps.cf on upgrade to be marked as done. This means that you claim t

Bug#1088046: fixed in readline 8.3~alpha1-2

2024-12-06 Thread Michael Biebl
Hi, this needs to be fixed for trixie. Given this upload targetted an alpha release to experimental, what is the plan for trixie? Michael On Sat, 30 Nov 2024 14:41:28 + Debian FTP Masters wrote: Source: readline Source-Version: 8.3~alpha1-2 Done: Matthias Klose We believe that the bu

Processed: Re: Bug#1089170: postfix-sqlite: sqlite map entry removed from dynamicmaps.cf on upgrade

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1089170 [postfix-sqlite] postfix-sqlite: sqlite map entry removed from dynamicmaps.cf on upgrade Severity set to 'grave' from 'normal' > tag -1 + confirmed pending Bug #1089170 [postfix-sqlite] postfix-sqlite: sqlite map entry removed from dy

Processed: found 1089166 in 1:3.0.0-1

2024-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1089166 1:3.0.0-1 Bug #1089166 {Done: Mark Hindley } [libpgtcl] pfm: Cannot connect to PostgreSQL database. Bug #1050375 {Done: Mark Hindley } [libpgtcl] libpgtcl not installed in default Tcl search path. Marked as found in versions pgtcl/

Processed: Re: Bug#1089166: pfm: Cannot connect to PostgreSQL database.

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libpgtcl Bug #1089166 [pfm] pfm: Cannot connect to PostgreSQL database. Bug reassigned from package 'pfm' to 'libpgtcl'. No longer marked as found in versions pfm/2.0.8-3. Ignoring request to alter fixed versions of bug #1089166 to the same values previo

Bug#1086931: marked as done (drawtiming: build against imagemagick 7)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 15:49:26 + with message-id and subject line Bug#1086931: fixed in drawtiming 0.7.1-11 has caused the Debian Bug report #1086931, regarding drawtiming: build against imagemagick 7 to be marked as done. This means that you claim that the problem has been deal

Bug#1088651: marked as done (gscan2pdf: Segfaults when duplex scan is requested)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 09:32:37 -0600 with message-id <8734j0omi2@complete.org> and subject line Re: Bug#1088651: gscan2pdf: Segfaults when duplex scan is requested has caused the Debian Bug report #1088651, regarding gscan2pdf: Segfaults when duplex scan is requested to be marked

Bug#1087720: marked as done (qcontrol: move aliased files from / to /usr (DEP17))

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 15:20:44 + with message-id and subject line Bug#1087720: fixed in qcontrol 0.5.7-2.1 has caused the Debian Bug report #1087720, regarding qcontrol: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that the problem ha

Bug#968415: susv4: downloaded tarball no longer matches recorded checksum

2024-12-06 Thread David Weinehall
Thanks for this report, and very sorry for being absent from my Debian work. I'll merge this fix and upload a new version this weekend. Kind regards, David Weinehall

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

2024-12-06 Thread Emanuele Rocca
Hi Andres, On 2024-12-03 12:27, Andres Salomon wrote: > Currently waiting on #1088699 to fix this. I tried building the affected chromium version using clang from bookworm-proposed-updates with CC=clang-19 and CXX=clang++-19, and with the following build-depends bumped: lld-19, clang-19, cla

Bug#1088971: marked as pending in autopkgtest

2024-12-06 Thread Paride Legovini
Control: tag -1 pending Hello, Bug #1088971 in autopkgtest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ci-team/autopkgtest/-/commit/439471ae745c9f63fff84006

Processed: Bug#1088971 marked as pending in autopkgtest

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1088971 [src:sbuild] sbuild's autopkg tests fail Added tag(s) pending. -- 1088971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1084805: marked as done (redis: CVE-2024-31227 CVE-2024-31228 CVE-2024-31449)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 13:55:33 + with message-id and subject line Bug#1084805: fixed in redis 5:7.0.15-1~deb12u2 has caused the Debian Bug report #1084805, regarding redis: CVE-2024-31227 CVE-2024-31228 CVE-2024-31449 to be marked as done. This means that you claim that the prob

Bug#1089158: Kernel Panic on Shutdown/Restart During RAID Resync with mdadm on Debian 12.7

2024-12-06 Thread Bastian Blank
Control: notfound -1 6.1.0-28-amd64 Control: forcemerge 1086175 -1 On Fri, Dec 06, 2024 at 01:09:46PM +0100, Vincent Roch wrote: > After installing Debian 12.7 (Bookworm) using the official netinst ISO, the > system encountered a Kernel Panic during a shutdown or reboot when the > `mdadm` utility

Processed: Re: Bug#1089158: Kernel Panic on Shutdown/Restart During RAID Resync with mdadm on Debian 12.7

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 6.1.0-28-amd64 Bug #1089158 [src:linux] Kernel Panic on Shutdown/Restart During RAID Resync with mdadm on Debian 12.7 The source 'linux' and version '6.1.0-28-amd64' do not appear to match any binary packages No longer marked as found in versions linux/

Bug#1076205: marked as done (aspectc++: Please upgrade to llvm-toolchain-18)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 13:19:16 + with message-id and subject line Bug#1076205: fixed in aspectc++ 1:2.3+git20241206-1 has caused the Debian Bug report #1076205, regarding aspectc++: Please upgrade to llvm-toolchain-18 to be marked as done. This means that you claim that the prob

Bug#1070443: marked as done (aspectc++: arm64 FTBFS with glibc 2.38)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 13:19:16 + with message-id and subject line Bug#1070443: fixed in aspectc++ 1:2.3+git20241206-1 has caused the Debian Bug report #1070443, regarding aspectc++: arm64 FTBFS with glibc 2.38 to be marked as done. This means that you claim that the problem has

Bug#1088971: sbuild: autopkgtest failure with glibc/2.40-4

2024-12-06 Thread Paride Legovini
On Fri, 06 Dec 2024 00:56:36 +0100 Johannes Schauer Marin Rodrigues wrote: > [...] In the autopkgtest log, one can see that the > following apt preferences file is written out: > > Package: src:glibc > Pin: release unstable > Pin-Priority: 995 > > But that will only pin binary packages built fr

Bug#1089158: Kernel Panic on Shutdown/Restart During RAID Resync with mdadm on Debian 12.7

2024-12-06 Thread Vincent Roch
Package: src:linux Version: 6.1.0-28-amd64 Severity: critical -- Description -- After installing Debian 12.7 (Bookworm) using the official netinst ISO, the system encountered a Kernel Panic during a shutdown or reboot when the `mdadm` utility was resynchronizing RAID devices. The issue occur

Processed: wget2: test suite fails on IPv6-only hosts

2024-12-06 Thread Debian Bug Tracking System
Processing control commands: > block 1086111 by -1 Bug #1086111 {Done: Paul Gevers } [src:wget2] src:wget2: fails to migrate to testing for too long 1086111 was blocked by: 1088242 1086111 was not blocking any bugs. Added blocking bug(s) of 1086111: 1089156 > forwarded -1 https://gitlab.com/gnuwg

Bug#1086378: python-pgpy: FTBFS: Error: gpgme_op_verify: GPGME: Bad data

2024-12-06 Thread Xiyue Deng
Hi, With much testing, I have identified that this was caused by the change in gpgme1.0 after upgrading from 1.18.0-6+b1 to 1.23.2-5. More specifically, gpg.Context.verify (which uses gpgme_op_verify underneath) now calls "gpg" with "--verify" which caused its behavior to change and resulted in t

Bug#1073882: marked as done (FTBFS with OCaml 5.2.0 (Needs porting))

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Dec 2024 08:39:52 + with message-id and subject line Bug#1073882: fixed in hol-light 1:3.0.0-1 has caused the Debian Bug report #1073882, regarding FTBFS with OCaml 5.2.0 (Needs porting) to be marked as done. This means that you claim that the problem has been dealt

Bug#1081424: marked as done (Bash built-in printf produces garbage number output in current Debian Testing (2024-09-11))

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Dec 2024 09:11:55 +0100 with message-id <443e00fd-8e8c-4391-bf3e-16484ab2e...@debian.org> and subject line Fixed has caused the Debian Bug report #1078556, regarding Bash built-in printf produces garbage number output in current Debian Testing (2024-09-11) to be marked as

Bug#1078556: marked as done (bash: 5.2.21-2.1 to 5.2.21-2.1+b1 breaks printf %.2f .1)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Dec 2024 09:11:55 +0100 with message-id <443e00fd-8e8c-4391-bf3e-16484ab2e...@debian.org> and subject line Fixed has caused the Debian Bug report #1078556, regarding bash: 5.2.21-2.1 to 5.2.21-2.1+b1 breaks printf %.2f .1 to be marked as done. This means that you claim th

Bug#1078583: marked as done (bash: printf '%5.1f' 1.498 prints multiple lines of numbers)

2024-12-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Dec 2024 09:11:55 +0100 with message-id <443e00fd-8e8c-4391-bf3e-16484ab2e...@debian.org> and subject line Fixed has caused the Debian Bug report #1078556, regarding bash: printf '%5.1f' 1.498 prints multiple lines of numbers to be marked as done. This means that you clai