Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues in r-cran-popepi which needs an update

2024-06-05 Thread Johannes Ranke
Am Mittwoch, 5. Juni 2024, 22:27:09 CEST schrieb Dirk Eddelbuettel: > On 5 June 2024 at 21:55, Paul Gevers wrote: > | Source: survival > | Version: 3.5-8-1 > | Severity: serious > | Control: close -1 3.6-4-1 > | Tags: sid trixie > | User: release.debian@packages.debian.org > | Usertags: out-of-

Bug#1072668: ocplib-simplex: autopkgtest failures (missing zarith)

2024-06-05 Thread Gianfranco Costamagna
Package: ocplib-simplex Version: 0.5.1-1 Severity: serious Tags: patch Hello, looks like zarith is a test dependency (but not a runtime dependency). 102s autopkgtest [08:43:49]: test upstream-tests: [--- 102s File "dune", line 13, characters 27-33: 102s 13 | (libraries ocpli

Bug#1072667: picotool:FTBFS:build failed(picotool.1.in diff)

2024-06-05 Thread Yue Gui
Source: picotool Version: 1.1.2-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear picotool Maintainer, The picotool package build failed on many archs caused by detecting debian/ picotool.1.in diff.The cru

Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 06 Jun 2024 01:34:02 + with message-id and subject line Bug#1071007: fixed in sherlock 0.14.4+git20240531.e5ad3c4-1 has caused the Debian Bug report #1071007, regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py to be marked as done. This means

Bug#1071007:

2024-06-05 Thread Nilson Silva
In accordance with the other Package Uploaders, Debian Developer, Francisco Vilmar. I will be closing the bug. Since the problem itself, with Sherlock installing its modules in the root of the packages, has been fixed. Nilson F. Silva

Bug#1072657: rust-subtile: Fails to build

2024-06-05 Thread Jeremy Bícha
Source: rust-subtile Version: 0.1.7-1 Severity: serious Tags: ftbfs rust-subtile is failing to build. https://buildd.debian.org/status/package.php?p=rust-subtile Build log excerpt --- error[E0433]: failed to resolve: use of undeclared crate or module `profiling` --> src/ima

Bug#1050989: marked as done (firmware-carl9170: undeclared file conflict with firmware-linux-free)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 22:34:06 + with message-id and subject line Bug#1050989: fixed in carl9170fw 1.9.9-399-gcd480b9-1.2 has caused the Debian Bug report #1050989, regarding firmware-carl9170: undeclared file conflict with firmware-linux-free to be marked as done. This means th

Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free

2024-06-05 Thread Bastian Germann
I am fixing this with another NMU.

Processed: tagging 988094

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 988094 - pending Bug #988094 [chkservice] reportbug: chkservice fails to control certain services Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 988094: https://bugs.debian.org/cgi-bi

Processed: tagging 1024642

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1024642 - pending Bug #1024642 [src:pgcharts] pgcharts: FTBFS: Fatal NAME-CONFLICT: [...] PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistanc

Bug#1070395: marked as done (tinyproxy: CVE-2023-49606)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 21:47:14 + with message-id and subject line Bug#1070395: fixed in tinyproxy 1.11.1-2.1+deb12u1 has caused the Debian Bug report #1070395, regarding tinyproxy: CVE-2023-49606 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1053334: marked as done (galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 21:47:42 + with message-id and subject line Bug#1053334: fixed in galera-4 26.4.18-0+deb11u1 has caused the Debian Bug report #1053334, regarding galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates to be marked as done. This means

Bug#1053334: marked as done (galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 21:47:08 + with message-id and subject line Bug#1053334: fixed in galera-4 26.4.18-0+deb12u1 has caused the Debian Bug report #1053334, regarding galera-4: FTBFS in bullseye and bookworm because of expired SSL certificates to be marked as done. This means

Processed: dt-schema is now broken in sid and testing

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1063562 grave Bug #1063562 [dt-schema] dt-schema: Please add version dependency for jsonschema Severity set to 'grave' from 'normal' > retitle 1063562 dt-schema: broken with python3-jsonschema 4.18+ Bug #1063562 [dt-schema] dt-schema: Ple

Bug#1060518: marked as done (resource-agents: Please switch Build-Depends to systemd-dev)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 20:48:17 + with message-id and subject line Bug#1060518: fixed in resource-agents 1:4.14.0-1 has caused the Debian Bug report #1060518, regarding resource-agents: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim tha

Bug#1072617: marked as done (confget: autopkgtest: invokes feature-check in a partly unsupported way)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 20:34:23 + with message-id and subject line Bug#1072617: fixed in confget 5.1.2-2 has caused the Debian Bug report #1072617, regarding confget: autopkgtest: invokes feature-check in a partly unsupported way to be marked as done. This means that you claim t

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-05 Thread Dirk Eddelbuettel
On 5 June 2024 at 21:57, Paul Gevers wrote: | Source: quantlib-swig | Version: 1.33-1 | Severity: serious | Control: close -1 1.34-1 | Tags: sid trixie ftbfs | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The Release Team considers packages th

Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues

2024-06-05 Thread Dirk Eddelbuettel
On 5 June 2024 at 21:55, Paul Gevers wrote: | Source: survival | Version: 3.5-8-1 | Severity: serious | Control: close -1 3.6-4-1 | Tags: sid trixie | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The Release Team considers packages that are ou

Bug#1072652: context-modules: Migration blocker

2024-06-05 Thread Hilmar Preusse
Source: context-modules Version: 20240428-4 Severity: grave Justification: renders package unusable Package should not migrate to testing for now. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stabl

Bug#1072651: context: Migration blocker

2024-06-05 Thread Hilmar Preusse
Source: context Version: 2024.04.01.20240428+dfsg-2 Severity: grave Justification: renders package unusable Package should not migrate to testing for now. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-05 Thread Paul Gevers
Source: quantlib-swig Version: 1.33-1 Severity: serious Control: close -1 1.34-1 Tags: sid trixie ftbfs 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 d

Processed: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.34-1 Bug #1072650 [src:quantlib-swig] src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64 Marked as fixed in versions quantlib-swig/1.34-1. Bug #1072650 [src:quantlib-swig] src:quantlib-swig: fails to migra

Bug#1072648: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues

2024-06-05 Thread Paul Gevers
Source: survival Version: 3.5-8-1 Severity: serious Control: close -1 3.6-4-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 ha

Processed: src:survival: fails to migrate to testing for too long: triggers autopkgtest issues

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.6-4-1 Bug #1072648 [src:survival] src:survival: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions survival/3.6-4-1. Bug #1072648 [src:survival] src:survival: fails to migrate to testing for too long: trigge

Processed: src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 14.0-1 Bug #1072647 [src:openttd] src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug Marked as fixed in versions openttd/14.0-1. Bug #1072647 [src:openttd] src:openttd: fails to migrate to testing for too long: FTBF

Bug#1072647: src:openttd: fails to migrate to testing for too long: FTBFS on armel and unresolved RC bug

2024-06-05 Thread Paul Gevers
Source: openttd Version: 13.4-1 Severity: serious Control: close -1 14.0-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1070208 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unst

Bug#1072646: src:rust-synstructure: fails to migrate to testing for too long

2024-06-05 Thread Paul Gevers
Source: rust-synstructure Version: 0.12.3-2 Severity: serious Control: close -1 0.13.1-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

Processed: src:rust-synstructure: fails to migrate to testing for too long

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.13.1-1 Bug #1072646 [src:rust-synstructure] src:rust-synstructure: fails to migrate to testing for too long Marked as fixed in versions rust-synstructure/0.13.1-1. Bug #1072646 [src:rust-synstructure] src:rust-synstructure: fails to migrate to testing fo

Bug#1072110: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? -- not the case

2024-06-05 Thread Paul Gevers
Hi, On 01-06-2024 5:05 p.m., Philippe SWARTVAGHER wrote: As I understand it (but I can be wrong), the current state of glslang and shaderc in unstable is correct; mixing versions from testing and unstable triggers bugs that are now fixed in unstable. Ok. Does that mean that the version of glsl

Processed: Re: Bug#890601: firmware-free: Source Package Doesn't Contain Source

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #890601 [firmware-linux-free] firmware-linux-free uses prebuilt blobs instead of building from source Added tag(s) moreinfo. -- 890601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890601 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#890601: firmware-free: Source Package Doesn't Contain Source

2024-06-05 Thread Ben Hutchings
Control: tag -1 moreinfo On Tue, 2024-06-04 at 18:29 +0200, Bastian Germann wrote: > Control: severity -1 serious > > On Fri, 1 Mar 2024 12:48:42 +0100 Salvatore Bonaccorso wrote: > > Would you be fine with those changes s proposed by Bastian, or want to > > have it handled differently? > > > >

Processed: Re: RM: libtar -- RoQA; Abandoned upstream

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1072586 [src:libtar] RM: libtar -- RoQA; Abandoned upstream Severity set to 'serious' from 'wishlist' -- 1072586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072586 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Processed: bug 1039883 is forwarded to https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.lan/t/#u

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1039883 > https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.lan/t/#u Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Set Bug forwarded-to-address to 'https://lore.kernel.org/linux-ext4/zkbhursrs96jd...@eldamar.l

Bug#1072624: marked as done (gsmartcontrol: Does not start)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 18:04:36 + with message-id and subject line Bug#1072624: fixed in gsmartcontrol 1.1.4+git20240531.25f1c62-2 has caused the Debian Bug report #1072624, regarding gsmartcontrol: Does not start to be marked as done. This means that you claim that the problem h

Bug#1072643: Regression: po4a fails on valid non-utf8 file

2024-06-05 Thread Santiago Vila
(Adding this note to the cloned bug) Note: If you take a look at the FTBFS bugs I reported yesterday: https://people.debian.org/~sanvila/build-logs/202406/?C=M;O=A you can see that several of them are also a consequence of this change in po4a. So, I fully support that this kind of behaviour ch

Bug#1070853: strace: test failures on 32bit with 64bit time_t

2024-06-05 Thread Bo YU
Hi, On Wed, Jun 5, 2024 at 9:38 PM Emanuele Rocca wrote: > > Control: retitle -1 strace: test failures on multiple architectures when > using libunwind > > On 2024-05-11 12:21, Adrian Bunk wrote: > > The tests also fail on i386 > > And on arm64 as well. > > The problem has to do with libunwind a

Processed: Re: Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1072594 -1 Bug #1072594 [src:goobox] goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114. Bug 1072594 cloned as bug 1072643 > reassign -1 po4a Bug #1072643 [src:goobox] goobox: F

Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.

2024-06-05 Thread Helge Kreutzmann
clone 1072594 -1 reassign -1 po4a retitle -1 Regression: po4a fails on valid non-utf8 file tags 1072594 + pending thanks Sorry, forgot to actually use the real bug number … -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.

Bug#1072642: curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest)

2024-06-05 Thread Andreas Metzler
Package: curl Version: 8.8.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, I did a local rebuild on sid which failed: srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35 ~300 ~301 ~303 ~304 ~306 ~

Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.

2024-06-05 Thread Helge Kreutzmann
clone 12345 -1 reassign -1 po4a retitle -1 Regression: po4a fails on valid non-utf8 file tags 12345 + pending thanks Hello Santiago, hello Po4a maintainers, excuse the TOFU. The build of goobox currently fails on a po file encoded in ISO-8859-15. The package builds with this file since at least 2

Processed: tags

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1070419 + ftbfs Bug #1070419 [src:gnome-snapshot] src:gnome-snapshot: unsatisfied build dependency in testing: librust-gst-plugin-gtk4-0.11-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1060573: nitrokey-app: Please switch Build-Depends to systemd-dev

2024-06-05 Thread Peter Wienemann
Hi, I looked into this issue and it seems to me that the build dependency on udev is outdated since handling udev rules was migrated to libnitrokey (see [0]). Therefore I think that an easy fix for this issue is to remove the build dependency on udev. Best regards, Peter [0] https://githu

Bug#1067912: nitrokey-app: Update Build-Depends for the time64 library renames

2024-06-05 Thread Peter Wienemann
Hi, I looked into this issue and it seems to me that the build dependency on libqt5concurrent5 is not necessary since it is already covered by qtbase5-dev. Thus I think that an easy fix for this issue is to remove libqt5concurrent5 from the build dependencies. Best regards, Peter

Bug#1072594: goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.

2024-06-05 Thread Helge Kreutzmann
Hello Santiago, Am Wed, Jun 05, 2024 at 02:16:47AM +0200 schrieb Santiago Vila: > During a rebuild of all packages in unstable, your package failed to build: Thanks for notifying me. … > po4a::sgml: Warning: onsgmls produced some errors. This is usually caused by > po4a, which modifies the in

Processed: notforwarded 1072480

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notforwarded 1072480 Bug #1072480 [src:condor] condor: hard-coded dependencies on pre-t64 libraries Unset Bug forwarded-to-address > End of message, stopping processing here. Please contact me if you need assistance. -- 1072480: https://bugs.deb

Processed: forwarded 1072480 https://github.com/htcondor/htcondor/pull/2432

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1072480 https://github.com/htcondor/htcondor/pull/2432 Bug #1072480 [src:condor] condor: hard-coded dependencies on pre-t64 libraries Set Bug forwarded-to-address to 'https://github.com/htcondor/htcondor/pull/2432'. > End of message, st

Processed: tagging 1070853

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1070853 + patch Bug #1070853 [src:strace] strace: test failures on multiple architectures when using libunwind Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070853: https://bugs.debian

Bug#1070853: strace: test failures on 32bit with 64bit time_t

2024-06-05 Thread Emanuele Rocca
Control: retitle -1 strace: test failures on multiple architectures when using libunwind On 2024-05-11 12:21, Adrian Bunk wrote: > The tests also fail on i386 And on arm64 as well. The problem has to do with libunwind as mentioned on the upstream issue, and it was introduced with: https://salsa

Processed: Re: Bug#1070853: strace: test failures on 32bit with 64bit time_t

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 strace: test failures on multiple architectures when using > libunwind Bug #1070853 [src:strace] strace: test failures on 32bit Changed Bug title to 'strace: test failures on multiple architectures when using libunwind' from 'strace: test failures on 32b

Bug#1060772: [Debian-pan-maintainers] Unifying jupyterlab and node-jupyterlab

2024-06-05 Thread Roland Mas
Le 02/06/2024 à 10:58, Yadd a écrit : On 6/2/24 12:53, Yadd wrote: On 6/2/24 10:38, Yadd wrote: In my last commit, I added also a fix for #1060772:   - jupyter-lab uses yarnpkg by default   - in Debian build context, this can be overridden using     YARN_COMMAND=pkgjs-install-minimal Better

Bug#1071704: marked as done (uc-echo: tests fail with scipy 1.12)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 12:50:49 + with message-id and subject line Bug#1071704: fixed in uc-echo 1.12-19 has caused the Debian Bug report #1071704, regarding uc-echo: tests fail with scipy 1.12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1071050: [PATCH] invoke esbuild with --target es2016

2024-06-05 Thread Petr Gajdusek
The build system does not specify target for esbuild, so I guess the behavior depends on esbuild verison. The attached patch invokes `esbuild --target es2016` to fix this. --- Pseudo-Headers --- tag -1 + patch THIS CORRESPONDENCE CONTAINS CONFIDENTIAL INFORMATION OF YAGEO CORPORATION AND

Processed: Re: Bug#1072521: fakeroot hangs on some commands with faked-sysv using 100% CPU

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1072521 [fakeroot] fakeroot hangs on some commands with faked-sysv using 100% CPU Severity set to 'important' from 'critical' -- 1072521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072521 Debian Bug Tracking System Contact ow...@

Bug#1072521: fakeroot hangs on some commands with faked-sysv using 100% CPU

2024-06-05 Thread Helmut Grohne
Control: severity -1 important Hi, On Mon, Jun 03, 2024 at 04:31:39PM +0200, Pierre-Elliott Bécue wrote: > Assigning to fakeroot for now, but not sure it's not something for ftp.d.o (a > binNMU) or libc6. > > Today, after an upgrade, I am not able to build packages with sbuild as > it hanks with

Bug#1072634: r-cran-testthat: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: r-cran-testthat Version: 3.2.1-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-27, r-cran-testthat's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1072632: r-cran-rsqlite: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: r-cran-rsqlite Version: 2.3.4-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-16, r-cran-rsqlite's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] ht

Bug#1072631: r-cran-mockr: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: r-cran-mockr Version: 0.2.1-1 Severity: serious Tags: trixie sid User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-03-01, r-cran-mockr's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Gr

Bug#1072630: r-cran-dplyr: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: r-cran-dplyr Version: 1.1.4-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-16, r-cran-dplyr's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https:

Bug#1072629: r-cran-dials: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: r-cran-dials Version: 1.2.0-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-02-15, r-cran-dials' autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https:/

Bug#1072628: graphlan: autopkgtest regression in testing

2024-06-05 Thread Graham Inggs
Source: graphlan Version: 1.1.3-4 Severity: serious Tags: trixie sid User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-05-22, graphlan's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [

Bug#1072394: marked as done (fcgiwrap: autopkgtest failures: The requested URL returned error: 500)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 11:19:29 + with message-id and subject line Bug#1072394: fixed in fcgiwrap 1.1.0-15 has caused the Debian Bug report #1072394, regarding fcgiwrap: autopkgtest failures: The requested URL returned error: 500 to be marked as done. This means that you claim th

Bug#1072624: gsmartcontrol: Does not start

2024-06-05 Thread Eric Valette
Package: gsmartcontrol Version: 1.1.4+git20240531.25f1c62-1 Severity: grave Justification: renders package unusable gsmartcontrol-root [app] hz::data_file_find(): Data file "[ui:]gsc_executor_log_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open fil

Bug#1069507: marked as done (dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__')

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 08:34:30 + with message-id and subject line Bug#1069507: fixed in dc3dd 7.3.1-3 has caused the Debian Bug report #1069507, regarding dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__' to be marked as

Bug#1069507: marked as pending in dc3dd

2024-06-05 Thread Arnaud Rebillout
Control: tag -1 pending Hello, Bug #1069507 in dc3dd 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/pkg-security-team/dc3dd/-/commit/c848b6a12af7414b95be2de78a

Processed: Bug#1069507 marked as pending in dc3dd

2024-06-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069507 [src:dc3dd] dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__' Added tag(s) pending. -- 1069507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069507 Debian Bug Tracking Sys

Processed: clone the -O-qfeatures bug back into confget's pool

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1071683 -1 Bug #1071683 [feature-check] feature-check: Rust: -O fails on values starting with dashes Bug 1071683 cloned as bug 1072617 > reassign -1 confget Bug #1072617 [feature-check] feature-check: Rust: -O fails on values starting with

Bug#1065387: marked as done (budgie-session: Please switch Build-Depends to systemd-dev)

2024-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Jun 2024 07:19:01 + with message-id and subject line Bug#1065387: fixed in budgie-session 0.9.1-3 has caused the Debian Bug report #1065387, regarding budgie-session: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the