Bug#1102251: marked as done (rust-sudo-rs: failing autopkgtests)

Your message dated Tue, 15 Apr 2025 06:49:37 + with message-id and subject line Bug#1102251: fixed in rust-sudo-rs 0.2.5-3 has caused the Debian Bug report #1102251, regarding rust-sudo-rs: failing autopkgtests to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1094969: git linked with OpenSSL

Hi, On Mon, 2025-04-14 at 16:18 -0500, Richard Laager wrote: > On 2025-04-14 11:10, Russ Allbery wrote: > > I do find it fairly hard to understand the logic behind a position that > > somehow our git-remote-https binary as distributed is a derived work of > > OpenSSL and thus violates the GPLv2 li

Bug#1102947: Debian Bug #1102947

This is the same as bug #1094097. The failed test output shows this error: > munged: Error: Logfile is insecure: invalid ownership of "/tmp" The preconditions for that error are here: https://sources.debian.org/src/munge/0.5.16-1/src/munged/path.c/#L224 munged is checking for that directory t

Bug#1103017: marked as done (libspglib-f08-dev fails to coinstall)

Your message dated Tue, 15 Apr 2025 06:05:12 + with message-id and subject line Bug#1103017: fixed in spglib 2.6.0-3 has caused the Debian Bug report #1103017, regarding libspglib-f08-dev fails to coinstall to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#1102442: android-udev-rules has an undeclared file conflict on /usr/lib/udev/rules.d/51-android.rules

Processing control commands: > fixed -1 android-udev-rules/20250314+ds-4 Bug #1102442 [android-udev-rules] android-udev-rules has an undeclared file conflict on /usr/lib/udev/rules.d/51-android.rules The source android-udev-rules and version 20250314+ds-4 do not appear to match any binary packag

Bug#1102322: android-udev-rules ineffectively Replaces android-sdk-platform-tools-common due to the /usr-move transition (DEP17 P1)

control: fixed -1 20250314+ds-4 is this the same as #1102321? looks very similar. -Roger

Processed: Re: Bug#1102322: android-udev-rules ineffectively Replaces android-sdk-platform-tools-common due to the /usr-move transition (DEP17 P1)

Processing control commands: > fixed -1 20250314+ds-4 Bug #1102322 [android-udev-rules] android-udev-rules ineffectively Replaces android-sdk-platform-tools-common due to the /usr-move transition (DEP17 P1) There is no source info for the package 'android-udev-rules' at version '20250314+ds-4' w

Processed: Re: Bug#1099986: cppcheck: autopkgtest regression on ppc64el: Segmentation fault

Processing commands for cont...@bugs.debian.org: > tags 1099986 - pending patch Bug #1099986 [src:cppcheck] cppcheck: autopkgtest regression on ppc64el: Segmentation fault Removed tag(s) pending and patch. > severity 1099986 normal Bug #1099986 [src:cppcheck] cppcheck: autopkgtest regression on p

Bug#1099986: cppcheck: autopkgtest regression on ppc64el: Segmentation fault

tags 1099986 - pending patch severity 1099986 normal thanks The patch has been applied in 2.17.1-2: = cppcheck (2.17.1-2) unstable; urgency=medium * Disable autopkgtests on ppc64el, thanks to Michael Prokop (see #1099986). = Best regards, Joachim

Bug#1102745: marked as done (ntpsec: FTBFS on s390x: runtests: ../../libaes_siv/tests.c:80: test_malloc_failure: Assertion `ret == 1' failed.)

Your message dated Tue, 15 Apr 2025 05:49:06 + with message-id and subject line Bug#1102745: fixed in ntpsec 1.2.3+dfsg1-7 has caused the Debian Bug report #1102745, regarding ntpsec: FTBFS on s390x: runtests: ../../libaes_siv/tests.c:80: test_malloc_failure: Assertion `ret == 1' failed. to b

Bug#1101679: marked as done (src:r-cran-bslib: fails to migrate to testing for too long)

Your message dated Tue, 15 Apr 2025 05:49:20 + with message-id and subject line Bug#1101679: fixed in r-cran-bslib 0.9.0+dfsg-2 has caused the Debian Bug report #1101679, regarding src:r-cran-bslib: fails to migrate to testing for too long to be marked as done. This means that you claim that

Bug#1102784: spglib: FTBFS: scikit_build_core._vendor.pyproject_metadata.errors.ConfigurationError: "project.license-files" must not be used when "project.license" is not a SPDX license expression

On 2025-04-14 20:39, Sergio Durigan Junior wrote: Apologies, this was an oversight on my end. I've just pushed the branch and the tag. Thanks, Sergio! Best wishes, Andrius

Bug#1103232: apertium-oci-fra: FTBFS: Document oci-fra.t1x does not validate against /usr/share/apertium/transfer.dtd

Package: src:apertium-oci-fra Version: 1.0.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean

Bug#1103231: mercurial: FTBFS: 847 failed tests

Package: src:mercurial Version: 6.9.5-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with

Bug#1087142: marked as done (FTBFS: auto-static-fetch.c:50:13: error: ‘print_escaped_string’ defined but not used)

Your message dated Tue, 15 Apr 2025 00:19:01 + with message-id and subject line Bug#1087142: fixed in tl-parser 0.0.0+git20210107.1933e76f-2 has caused the Debian Bug report #1087142, regarding FTBFS: auto-static-fetch.c:50:13: error: ‘print_escaped_string’ defined but not used to be marked a

Bug#1102198: Some more information

Control: forwarded -1 https://github.com/jelmer/dirty-tracker-rs/issues/13 X-Debbugs-CC: jel...@debian.org I used the BSP in Vienna to dig into this issue, but wasn't able to reproduce the failure of the flaky test. Found out that there is already a patch [0] that disables the flaky test on x

Processed: Some more information

Processing control commands: > forwarded -1 https://github.com/jelmer/dirty-tracker-rs/issues/13 Bug #1102198 [src:rust-dirty-tracker] rust-dirty-tracker: flaky autopkgtest Set Bug forwarded-to-address to 'https://github.com/jelmer/dirty-tracker-rs/issues/13'. -- 1102198: https://bugs.debian.or

Processed: reassign 1103011 to qt6-pdf-dev, forcibly merging 1100320 1103011

Processing commands for cont...@bugs.debian.org: > reassign 1103011 qt6-pdf-dev Bug #1103011 [src:skanpage] skanpage: FTBFS in testing/arm64: make: *** [debian/rules:6: binary] Error 2 Bug reassigned from package 'src:skanpage' to 'qt6-pdf-dev'. No longer marked as found in versions skanpage/24.1

Bug#1103060: pyraf: FTBFS in testing/i386: KeyError: 'setuptools_scm'

Source: pyraf Version: 2.2.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > debian/ru

Bug#1094969: git linked with OpenSSL

Richard Laager writes: > As I have said before: I think that computer programmers have a > tendency to treat licenses as if they are self-executing (and precise > like software). Agreed, this is often a challenge when technical people discuss legal matters, and it helps to keep this in mind. >

Bug#1101623: closing 1101623

close 1101623 thanks

Bug#1103229: ltt-control:FTBFS:build failed(error: 'health_state' undeclared)

Source: ltt-control Version: 2.13.15-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 Dear ltt-control maintainer, The package ltt-control build failed on riscv.The crucial buildd log below: ``` make[4]: Entering directory '/build/reproducible-path/ltt-

Processed: Re: glib-d: Fails to build with glib 2.84

Processing commands for cont...@bugs.debian.org: > reassign 1101383 src:gir-to-d 0.23.3-1 Bug #1101383 [src:glib-d] glib-d: Fails to build with glib 2.84 Bug reassigned from package 'src:glib-d' to 'src:gir-to-d'. No longer marked as found in versions glib-d/2.4.3-2. Ignoring request to alter fixe

Bug#1103204: rkward: FTBFS: The following tests FAILED: 1 - rkward-core_test (Subprocess aborted)

Package: src:rkward Version: 0.8.0-4 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with kf

Bug#1103226: chromium: FTBFS: gen/third_party/blink/renderer/platform/color_data.cc:138:7: error: fallthrough annotation does not directly precede switch label

Package: src:chromium Version: 135.0.7049.84-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] [23872/53626] CXX obj/third

Bug#1103143: marked as done (rl-renderpm: FTBFS in testing/i386: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

 --- Source: rl-renderpm Version: 4.0.3+repack-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > mak

Bug#1103183: atlas-ecmwf: FTBFS: /usr/bin/ld: /lib/x86_64-linux-gnu/libfckit-gfortran.so.0d: undefined reference to `eckit::Exception::Exception(std::__cxx11::basic_string

Package: src:atlas-ecmwf Version: 0.42.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] [ please see the full build log,

Bug#1103225: ecmwflibs: FTBFS: ERROR: ecmwflibs (unittest.loader._FailedTest.ecmwflibs)

Package: src:ecmwflibs Version: 2:0.6.3-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --bu

Bug#1103203: rjava: FTBFS: /usr/bin/ld: cannot find -lzstd: No such file or directory

On 15 April 2025 at 00:19, Santiago Vila wrote: | Package: src:rjava | Version: 1.0-11-1 | Severity: serious | Tags: ftbfs trixie sid | | Dear maintainer: | | During a rebuild of all packages in unstable, your package failed to build: | | --

Bug#1103228: r-cran-sdmtools: FTBFS: pointinpolygon.c:11:20: error: 'PI' undeclared here (not in a function)

Package: src:r-cran-sdmtools Version: 1.1-221.2-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh cl

Bug#1103190: img2pdf: FTBFS: AssertionError: b'4.1089e-06 (8.53093e-08)'

Package: src:img2pdf Version: 0.6.0-3 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with p

Bug#1103196: plip: FTBFS: help2man: can't get `--help' info from /<>/debian/plip/usr/bin/plipcmd

Package: src:plip Version: 2.4.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --buil

Bug#1103205: ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.3" failed. Exiting.

Package: src:ruby-pry-byebug Version: 3.10.1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean

Bug#1103227: r-bioc-grohmm: FTBFS: DecayAlgorithm.c:94:15: error: expected identifier or '(' before 'false'

Package: src:r-bioc-grohmm Version: 1.40.3-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean -

Bug#1103223: cdo: FTBFS: configure: error: Could not link to magics library

Package: src:cdo Version: 2.5.1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --builddire

Bug#1103213: foot: FTBFS: ../wayland.c:878:9: error: enumeration value 'XDG_TOPLEVEL_STATE_CONSTRAINED_LEFT' not handled in switch [-Werror=switch]

Package: src:foot Version: 1.21.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] [148/161] cc -Iutils/xtgettcap.p -Iutil

Bug#1029043: marked as done (AttributeError: module 'adonthell' has no attribute 'audio_load_wave')

Your message dated Mon, 14 Apr 2025 20:37:36 + with message-id and subject line Bug#1029043: fixed in adonthell 0.3.8-2.1+deb12u1 has caused the Debian Bug report #1029043, regarding AttributeError: module 'adonthell' has no attribute 'audio_load_wave' to be marked as done. This means that yo

Bug#1103197: pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy'

Package: src:pympress Version: 1.8.5-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with

Bug#1103191: importlab: FTBFS: help2man: can't get `--help' info from debian/python3-importlab/usr/bin/importlab

Package: src:importlab Version: 0.8.1-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with

Bug#1103217: r-bioc-affxparser: FTBFS: R_affx_cel_parser.cpp:37:33: error: expected primary-expression before 'char'

Package: src:r-bioc-affxparser Version: 1.78.0-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh cle

Bug#1103212: flatbuffers: FTBFS: /usr/lib/python3/dist-packages/setuptools/dist.py:484: SetuptoolsDeprecationWarning: Pattern '../license' cannot contain '..'

Package: src:flatbuffers Version: 23.5.26+dfsg-3 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh cle

Bug#1103215: magics++: FTBFS: /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libodccore.so.0d: undefined reference to `eckit::UserError::UserError(std::__cxx11::basic_string, std:

Package: src:magics++ Version: 4.16.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] /usr/bin/ld: /usr/lib/x86_64-linux

Bug#1103214: golang-github-smallstep-certificates: FTBFS: src/github.com/smallstep/certificates/authority/provisioner/nebula_test.go:58:20: not enough arguments in call to nc.Sign

Package: src:golang-github-smallstep-certificates Version: 0.20.0-4 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian

Bug#1103210: textdistance: FTBFS: RuntimeError: cannot import Levenshtein.distance

Package: src:textdistance Version: 4.6.3-4 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --b

Bug#1103208: supysonic: FTBFS: dh_install: error: missing files, aborting

Package: src:supysonic Version: 0.7.9+ds-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --w

Bug#1103209: symfony: FTBFS: Failed asserting that 0.0 is greater than 0.

Package: src:symfony Version: 6.4.20+dfsg-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean

Bug#1103207: stdeb: FTBFS: help2man: can't get `--help' info from /<>/debian/python3-stdeb/usr/bin/py2dsc

Package: src:stdeb Version: 0.10.0-3 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean rm -f py2dsc.1 pyp

Bug#1103203: rjava: FTBFS: /usr/bin/ld: cannot find -lzstd: No such file or directory

Package: src:rjava Version: 1.0-11-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --buildsy

Bug#1103200: r-bioc-rtracklayer: FTBFS: ucsc/common.c:249:9: error: too many arguments to function 'free'

Package: src:r-bioc-rtracklayer Version: 1.66.0-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh cl

Bug#1103198: r-bioc-cner: FTBFS: ucsc/common.c:360:9: error: too many arguments to function 'free'

Package: src:r-bioc-cner Version: 1.42.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clea

Bug#1103194: pcs: FTBFS: rm: cannot remove '/<>/debian/tmp/usr/lib/python3/dist-packages/*.dist-info/COPYING': No such file or directory

Package: src:pcs Version: 0.12.0-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with pyth

Bug#1103193: openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13

Package: src:openhft-chronicle-wire Version: 1.1.13-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean d

Bug#1103189: gpgme1.0: FTBFS: FAIL! : CryptoConfigTest::testDefault() Compared values are not the same

Package: src:gpgme1.0 Version: 1.24.2-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --buil

Bug#1103187: dssi: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

Package: src:dssi Version: 1.1.1~dfsg0-6 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean dh

Bug#1103188: golang-github-keltia-archive: FTBFS: github.com/proglottis/gpgme: exec: "pkg-config": executable file not found in $PATH

Package: src:golang-github-keltia-archive Version: 0.9.1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules cl

Bug#1103186: commonmark-bkrs: FTBFS: help2man: can't get `--help' info from debian/adhoc/wrappers/python3/cmark-bkrs

Package: src:commonmark-bkrs Version: 0.5.4+ds-7.1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh c

Bug#1103184: cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg"

Package: src:cairosvg Version: 2.7.1-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --with

Bug#1103185: clj-yaml-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.yaml:snakeyaml:jar:1.x has not been downloaded from it before.

Package: src:clj-yaml-clojure Version: 0.7.2-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean

Processed: Bug#1101383 marked as pending in glib-d

Processing control commands: > tag -1 pending Bug #1101383 [src:glib-d] glib-d: Fails to build with glib 2.84 Added tag(s) pending. -- 1101383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1038747: gnome-software may overwrite debian-security with invalid entry

Hi everyone! This turned out to be trickier to fix, the problem may not even be in s-p but in some of the underlying libraries. With this bug active, it looks like we may have to release trixie without s-p, as it will miss the deadline today, and I need to spend energy on PackageKit to support deb

Bug#1102209: marked as done (matomo: flaky autopkgtest (mostly on i386):)

Your message dated Mon, 14 Apr 2025 23:49:42 + with message-id and subject line Bug#1102209: fixed in matomo 5.3.1+dfsg-1 has caused the Debian Bug report #1102209, regarding matomo: flaky autopkgtest (mostly on i386): to be marked as done. This means that you claim that the problem has been

Bug#1101383: marked as done (glib-d: Fails to build with glib 2.84)

Your message dated Mon, 14 Apr 2025 19:31:45 -0400 with message-id and subject line Re: glib-d: Fails to build with glib 2.84 has caused the Debian Bug report #1101383, regarding glib-d: Fails to build with glib 2.84 to be marked as done. This means that you claim that the problem has been dealt

Bug#1101383: marked as done (glib-d: Fails to build with glib 2.84)

Your message dated Mon, 14 Apr 2025 19:16:05 -0400 with message-id and subject line Re: glib-d: Fails to build with glib 2.84 has caused the Debian Bug report #1101383, regarding glib-d: Fails to build with glib 2.84 to be marked as done. This means that you claim that the problem has been dealt

Bug#1101383: marked as pending in glib-d

Control: tag -1 pending Hello, Bug #1101383 in glib-d 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/gnome-team/glib-d/-/commit/869769ab44f54f7e8a461a062555efa

Bug#1091520: marked as done (There will be no further releases in the 2.x series)

Your message dated Mon, 14 Apr 2025 20:41:05 + with message-id and subject line Bug#1091520: fixed in phing 3.0.1-1 has caused the Debian Bug report #1091520, regarding There will be no further releases in the 2.x series to be marked as done. This means that you claim that the problem has bee

Bug#1088285: marked as done (software-properties REMOVED from testing since October 23, 2024)

Your message dated Mon, 14 Apr 2025 23:06:09 + with message-id and subject line Bug#1088285: fixed in software-properties 0.111-1 has caused the Debian Bug report #1088285, regarding software-properties REMOVED from testing since October 23, 2024 to be marked as done. This means that you clai

Bug#1089720: marked as done (software-properties-qt just crashes on start)

Your message dated Mon, 14 Apr 2025 23:06:09 + with message-id and subject line Bug#1089720: fixed in software-properties 0.111-1 has caused the Debian Bug report #1089720, regarding software-properties-qt just crashes on start to be marked as done. This means that you claim that the problem

Bug#1092693: marked as done (software-properties-gtk: Does not start FileNotFoundError: '/usr/bin/apt-key')

Your message dated Mon, 14 Apr 2025 23:06:09 + with message-id and subject line Bug#1092693: fixed in software-properties 0.111-1 has caused the Debian Bug report #1092693, regarding software-properties-gtk: Does not start FileNotFoundError: '/usr/bin/apt-key' to be marked as done. This mean

Bug#1103178: libxmltok: get out of testing

Source: libxmltok Version: 1.2-4.2 Severity: serious #691755 requests libxmltok to be removed from unstable, lets get it out of testing first/too. It's an old predecessor of expat. Chris

Bug#1103044: mat2: unsatisfiable dependency on python2

On Mon, 14 Apr 2025 17:51:47 +0300, Otto Kekäläinen wrote: On a tanget to this bug: this package is maintained in Salsa, and the original build failure is visible when CI runs in https://salsa.debian.org/otto/mat2/-/pipelines/850962, and the fact that the new change fixed the first issue but re

Bug#1103137: marked as pending in pydicom

Control: tag -1 pending Hello, Bug #1103137 in pydicom 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/med-team/pydicom/-/commit/58b37a8e5ba19932f28cac12dbd12d9

Bug#1103137: marked as done (pydicom: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13)

 --- Source: pydicom Version: 2.4.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > mak

Bug#1103020: marked as done (nfs-ganesha: wrong use of Multi-Arch)

Your message dated Mon, 14 Apr 2025 21:51:15 + with message-id and subject line Bug#1103020: fixed in nfs-ganesha 6.5-4 has caused the Debian Bug report #1103020, regarding nfs-ganesha: wrong use of Multi-Arch to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Re: Bug#1103044: mat2: unsatisfiable dependency on python2

Processing control commands: > tags -1 + pending Bug #1103044 [mat2] mat2: unsatisfiable dependency on python2 Added tag(s) pending. -- 1103044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1103044: mat2: unsatisfiable dependency on python2

Control: tags -1 + pending Hi all, On Mon, Apr 14, 2025 at 04:42:00PM +0300, Dmitry Shachnev wrote: > Okay, I will NMU setuptools then, and then NMU mat2 with bumped dependency > on setuptools. After some discussion we decided that it's better to fix dh-python, not setuptools, and Stefano upload

Processed: Bug#1103137 marked as pending in pydicom

Processing control commands: > tag -1 pending Bug #1103137 [src:pydicom] pydicom: FTBFS in testing/i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13 Added tag(s) pending. -- 1103137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103137

Bug#1022034: marked as done (policyd-rate-limit: Uses deprecated yaml.load)

Your message dated Mon, 14 Apr 2025 21:17:09 + with message-id and subject line Bug#1022034: fixed in policyd-rate-limit 1.0.1.1-2.1+deb12u1 has caused the Debian Bug report #1022034, regarding policyd-rate-limit: Uses deprecated yaml.load to be marked as done. This means that you claim that

Bug#1094969: git linked with OpenSSL

On 2025-04-14 11:10, Russ Allbery wrote: I do find it fairly hard to understand the logic behind a position that somehow our git-remote-https binary as distributed is a derived work of OpenSSL and thus violates the GPLv2 license based on the nature of this specific dependency chain, but then I wa

Bug#1103102: marked as done (python-pyglfw: FTBFS in testing/i386: ImportError: Failed to load GLFW3 shared library.)

: 2.8.0+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > debian/rules binary > dh

Bug#1084550: qt6-webengine: removal of Python standard libraries in Python 3.13

Control: severity -1 important On Sunday, April 13, 2025 11:19:31 AM Mountain Standard Time Chris Hofstaedtler wrote: > Hi, > > On Mon, Oct 07, 2024 at 12:14:19PM -0400, Louis-Philippe Véronneau wrote: > > Source: qt6-webengine > > Severity: important > > User: debian-pyt...@lists.debian.org >

Bug#1103150: marked as done (python3-setuptools: Generates #!python shebangs, which dh_python3 considers as Python 2)

Your message dated Mon, 14 Apr 2025 21:04:48 + with message-id and subject line Bug#1103150: fixed in dh-python 6.20250414 has caused the Debian Bug report #1103150, regarding python3-setuptools: Generates #!python shebangs, which dh_python3 considers as Python 2 to be marked as done. This m

Processed: reassign 1100967 to golang-step-crypto-dev

Processing commands for cont...@bugs.debian.org: > reassign 1100967 golang-step-crypto-dev Bug #1100967 [golang-step-crypto-dev,golang-github-smallstep-crypto-dev] golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts Bug reassigned from package 'golang-st

Bug#1103152: Starts 2nd getty on hvc0, making console login (almost) impossible

On Mon, Apr 14, 2025 at 05:45:48PM +0100, Andrew Bower wrote: > On Mon, Apr 14, 2025 at 04:28:36PM +0200, Andras Korn wrote: > > During a dist-upgrade, the getty-run package was pulled in, and a(n > > IMO misleadingly named) getty-ttyS0 service enabled by default. > > IMO the system should not st

Bug#1092774: libfcgi: CVE-2025-23016

Control: tags -1 fixed-upstream Please note that Yadd's debdiff is based on a patch that was rejected. The final solution was just released with the new upstream version 2.4.5: https://github.com/FastCGI-Archives/fcgi2/commit/b0eabcaf4d4f371514891a52115c746815c2ff15

Processed: affects 1100967

Processing commands for cont...@bugs.debian.org: > affects 1100967 golang-github-smallstep-crypto-dev Bug #1100967 [golang-step-crypto-dev] golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts Added indication that 1100967 affects golang-github-smallstep-cr

Bug#1102893: marked as done (fltk1.3: fake RC bug to delay migration until fltk1.4 is ready)

Your message dated Mon, 14 Apr 2025 16:47:23 -0400 with message-id and subject line Lifting block has caused the Debian Bug report #1102893, regarding fltk1.3: fake RC bug to delay migration until fltk1.4 is ready to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1102251: marked as done (rust-sudo-rs: failing autopkgtests)

Your message dated Mon, 14 Apr 2025 20:45:38 + with message-id and subject line Bug#1102251: fixed in rust-sudo-rs 0.2.5-2 has caused the Debian Bug report #1102251, regarding rust-sudo-rs: failing autopkgtests to be marked as done. This means that you claim that the problem has been dealt wi

Processed: Bug#1103102 marked as pending in python-pyglfw

Processing control commands: > tag -1 pending Bug #1103102 [src:python-pyglfw] python-pyglfw: FTBFS in testing/i386: ImportError: Failed to load GLFW3 shared library. Added tag(s) pending. -- 1103102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103102 Debian Bug Tracking System Contact o

Bug#1103102: marked as pending in python-pyglfw

Control: tag -1 pending Hello, Bug #1103102 in python-pyglfw 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/python-team/packages/python-pyglfw/-/commit/1f65065

Processed: reassign 1103150 to dh-python

Processing commands for cont...@bugs.debian.org: > reassign 1103150 dh-python Bug #1103150 [python3-setuptools] python3-setuptools: Generates #!python shebangs, which dh_python3 considers as Python 2 Bug reassigned from package 'python3-setuptools' to 'dh-python'. No longer marked as found in ver

Bug#1102914:

On 4/14/25 8:58 PM, Salvatore Bonaccorso wrote: As asked in #1102889 as well, would it be possible to get a full kernel log as well please? I cannot share log from this machine, but I just went through this and in the moment libvirt failed there is nothing logged... I can see it only tried to

Bug#980148: mesa-vulkan-drivers: file content conflict in Multi-Arch:same package

Hi Simon, On Mon, Apr 14, 2025 at 05:23:01PM +0100, Simon McVittie wrote: > Loaders are expected to be able to recognise that a particular driver is not > for them, and gracefully not load it. In practice this works fine, because all > of our architectures can be distinguished by their ELF headers

Bug#1103152: Starts 2nd getty on hvc0, making console login (almost) impossible

On Mon, Apr 14, 2025 at 09:32:55PM +0200, Andras Korn wrote: > On Mon, Apr 14, 2025 at 05:45:48PM +0100, Andrew Bower wrote: > > > On Mon, Apr 14, 2025 at 04:28:36PM +0200, Andras Korn wrote: > > > During a dist-upgrade, the getty-run package was pulled in, and a(n > > > IMO misleadingly named) ge

Bug#1103103: pysodium: FTBFS in testing/i386: dh_auto_test: error: pybuild --test -i python{version} -p 3.13 returned exit code 13

Source: pysodium Version: 0.7.18-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250414 ftbfs-trixie Hi, During a rebuild of all packages in testing (trixie), your package failed to build on i386. Relevant part (hopefully): > deb

Bug#1057621: valgrind should not drop valgrind-dbg

Hi Chris, It's a bit moot as the bug is already solved On 13-04-2025 23:06, Chris Hofstaedtler wrote: > I think you are implying a finer detail that is lost on me. Let me try again. The other bug is about valgrind Recommends a package that doesn't exist. That's clearly RC, it can be fixed

Bug#1092774: Stable security: libfcgi: CVE-2025-23016

The upstream patch applies cleanly on (old)stable. Please find two debdiffs attached. diff -Nru libfcgi-2.4.2/debian/changelog libfcgi-2.4.2/debian/changelog --- libfcgi-2.4.2/debian/changelog 2020-01-01 00:00:01.0 + +++ libfcgi-2.4.2/debian/changelog 2025-04-14 18:53:11.0

Bug#1092774: marked as done (libfcgi: CVE-2025-23016)

Your message dated Mon, 14 Apr 2025 19:05:59 + with message-id and subject line Bug#1092774: fixed in libfcgi 2.4.5-0.1 has caused the Debian Bug report #1092774, regarding libfcgi: CVE-2025-23016 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1102914:

Hi, On Mon, Apr 14, 2025 at 02:01:07PM +0200, Milan Broz wrote: > Hi, > > we have the same issue with 6.1.133-1 (previous 6.1.129-1 works fine). > > We use passthrough of NVMe device, VM start now fails with > > qemu-system-x86_64: -device > {"driver":"vfio-pci","host":":03:00.0","id":"hos

Processed: severity of 1102914 is serious

Processing commands for cont...@bugs.debian.org: > severity 1102914 serious Bug #1102914 [src:linux] VMs don't start up when being passed through a PCI device Bug #1102889 [src:linux] linux-image-6.1.0-33-amd64: KVM GPU passthrough broken Bug #1103153 [src:linux] linux-image-6.1.0-33-amd64: kerne

Bug#1102276: [Pkg-rust-maintainers] Bug#1102276: Bug#1102276: fails to compile: the name `hkdf` is defined multiple times

On Mon, Apr 14, 2025, at 12:54 AM, Jonas Smedegaard wrote: > Quoting Fabian Grünbichler (2025-04-12 16:13:42) >> On Mon, Apr 7, 2025, at 9:37 AM, Jonas Smedegaard wrote: >> > Quoting Jonas Smedegaard (2025-04-07 09:29:04) >> > Possibly the cause of this issue is that the Debian packaging carries a

  1   2   3   >