Processed: severity of 460232 is normal

Processing commands for cont...@bugs.debian.org: > severity 460232 normal Bug #460232 [pam] Please clarify license Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 460232:

Bug#1023442: marked as done (systemd FTBFS: python3-pyparsing:native no longer satisfiable)

Your message dated Mon, 07 Nov 2022 00:34:22 + with message-id and subject line Bug#1023442: fixed in systemd 252-3 has caused the Debian Bug report #1023442, regarding systemd FTBFS: python3-pyparsing:native no longer satisfiable to be marked as done. This means that you claim that the

Bug#1019829: marked as done (pgn2web: Please transition to wxwidgets3.2)

Your message dated Mon, 07 Nov 2022 00:28:43 + with message-id and subject line Bug#1019829: fixed in pgn2web 0.4-3.1 has caused the Debian Bug report #1019829, regarding pgn2web: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been

Processed: pgn2web: diff for NMU version 0.4-3.1

Processing control commands: > tags 1019829 + patch Bug #1019829 [src:pgn2web] pgn2web: Please transition to wxwidgets3.2 Added tag(s) patch. -- 1019829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1019829: pgn2web: diff for NMU version 0.4-3.1

Control: tags 1019829 + patch Dear maintainer, I've prepared an NMU for pgn2web (versioned as 0.4-3.1) and uploaded it to unstable as per the NMU guidelines in the devref: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines Cheers, Olly diff -Nru

Bug#1021032: vlc: playing videos results in a black screen

Hi, On Sat, 08 Oct 2022 14:30:43 +0300 =?ISO-8859-1?Q?R=E9mi?= Denis-Courmont wrote: Le lauantaina 8. lokakuuta 2022, 12.40.56 EEST KeyofBlueS a écrit : > Hi all. Let's continue here from #1021140 > > > It seems this issue it's not

Bug#1023579: lomiri-clock-app: autopkgtest depends on non-existing packages

Source: lomiri-clock-app Version: 3.13~git20221027.60c85a4-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/l/lomiri-clock-app/27859719/log.gz ... E: Unable to locate package autopilot-touch E: Unable to locate package libautopilot-qt E: Unable to locate package

Bug#1011924: marked as done (capsule-nextflow: FTBFS with OpenJDK 17 due to pack200 removal and ambiguous reference to FileSystems.newFileSystem())

Your message dated Sun, 06 Nov 2022 22:19:10 + with message-id and subject line Bug#1011924: fixed in capsule-nextflow 1.1.1+dfsg-1 has caused the Debian Bug report #1011924, regarding capsule-nextflow: FTBFS with OpenJDK 17 due to pack200 removal and ambiguous reference to

Bug#991358: marked as done (guile-2.2 should not be in bookworm)

Your message dated Sun, 06 Nov 2022 22:11:22 + with message-id and subject line Bug#1023560: Removed package(s) from unstable has caused the Debian Bug report #991358, regarding guile-2.2 should not be in bookworm to be marked as done. This means that you claim that the problem has been

Bug#1017222: marked as done (nifti2dicom: FTBFS: build-dependency not installable: libinsighttoolkit4-dev)

Your message dated Sun, 06 Nov 2022 22:09:14 + with message-id and subject line Bug#1023390: Removed package(s) from unstable has caused the Debian Bug report #1017222, regarding nifti2dicom: FTBFS: build-dependency not installable: libinsighttoolkit4-dev to be marked as done. This means

Bug#1013157: marked as done (nifti2dicom: vtk[6,7] removal)

Your message dated Sun, 06 Nov 2022 22:09:14 + with message-id and subject line Bug#1023390: Removed package(s) from unstable has caused the Debian Bug report #1013157, regarding nifti2dicom: vtk[6,7] removal to be marked as done. This means that you claim that the problem has been dealt

Bug#949355: marked as done (simpleitk FTBFS: test failures)

Your message dated Sun, 06 Nov 2022 22:08:46 + with message-id and subject line Bug#1023389: Removed package(s) from unstable has caused the Debian Bug report #949355, regarding simpleitk FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt

Processed: raku-json-class: trying to overwrite '/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-json

Processing control commands: > affects -1 src:raku-license-spdx Bug #1023576 [raku-json-class] raku-json-class: trying to overwrite '/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-json-marshal

Bug#1023576: raku-json-class: trying to overwrite '/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-js

Package: raku-json-class Version: 0.0.19-1 Severity: serious Tags: ftbfs Control: affects -1 src:raku-license-spdx https://piuparts.debian.org/sid/fail/raku-json-class_0.0.19-1.log ... Unpacking raku-json-class (0.0.19-1) ... dpkg: error processing archive

Processed: retitle 1023569 to librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1

Processing commands for cont...@bugs.debian.org: > retitle 1023569 librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1 Bug #1023569 [librte-net-af-xdp22] librte-net-af-xdp22 is empty after rebuild with 1.0.1 Changed Bug title to 'librte-net-af-xdp22 is empty after rebuild with libbpf

Bug#1023574: wolfssl: CVE-2022-42961

Source: wolfssl Version: 5.2.0-2 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 wolfssl. CVE-2022-42961[0]: | An issue was discovered in wolfSSL before 5.5.0. A

Processed: src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on package that can't migrate

Processing control commands: > close -1 4.1.0-2 Bug #1023572 [src:ruby-liquid-c] src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on package that can't migrate Marked as fixed in versions ruby-liquid-c/4.1.0-2. Bug #1023572 [src:ruby-liquid-c] src:ruby-liquid-c: fails

Bug#1023572: src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on package that can't migrate

Source: ruby-liquid-c Version: 4.0.0-2 Severity: serious Control: close -1 4.1.0-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1023534 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1023571: php-cas: CVE-2022-39369: Service Hostname Discovery Exploitation

Source: php-cas Version: 1.3.8-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.3.6-1 Hi, The following vulnerability was published for php-cas. CVE-2022-39369[0]: | phpCAS is an authentication

Processed: php-cas: CVE-2022-39369: Service Hostname Discovery Exploitation

Processing control commands: > found -1 1.3.6-1 Bug #1023571 [src:php-cas] php-cas: CVE-2022-39369: Service Hostname Discovery Exploitation Marked as found in versions php-cas/1.3.6-1. -- 1023571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023571 Debian Bug Tracking System Contact

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sun, 6 Nov 2022 11:44:43 -0800 > Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name, > 58...@debbugs.gnu.org, 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-06 11:32, Eli Zaretskii wrote: > > My question was whether in this scenario, since the parent Emacs > >

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

On 2022-11-06 11:32, Eli Zaretskii wrote: My question was whether in this scenario, since the parent Emacs exits, the child Emacs can get SIGHUP, simply because its parent exited and the read end of the PTY no longer exists. Yes, my sense from the few experiments I tried, is that it's a

Bug#1023569: librte-net-af-xdp22 is empty after rebuild with 1.0.1

Package: librte-net-af-xdp22 Version: 21.11-5 Severity: serious $ dpkg -L librte-net-af-xdp22 /. /usr /usr/share /usr/share/doc /usr/share/doc/librte-net-af-xdp22 /usr/share/doc/librte-net-af-xdp22/changelog.Debian.amd64.gz /usr/share/doc/librte-net-af-xdp22/changelog.Debian.gz

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

> Date: Sun, 6 Nov 2022 11:18:03 -0800 > Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name, > 58...@debbugs.gnu.org, 1017...@bugs.debian.org > From: Paul Eggert > > On 2022-11-05 22:51, Eli Zaretskii wrote: > > > But is it possible for a program like Emacs to get SIGHUP in such a

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

On 2022-11-05 22:51, Eli Zaretskii wrote: But is it possible for a program like Emacs to get SIGHUP in such a situation, or is that highly improbable? We have standard streams of the inferior Emacs process connected via PTYs to the parent process, I believe -- does that deliver SIGHUP or

Bug#937049: mini-buildd: Python2 removal in sid/bullseye

Hi Moritz, On Fri, 2022-10-28 at 00:12 +0200, Moritz Mühlenhoff wrote: > Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose: > > Package: src:mini-buildd > > Version: 1.0.41 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal

Bug#1022343: marked as done (view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by view3dscene)

Your message dated Sun, 06 Nov 2022 18:58:53 + with message-id and subject line Bug#1022343: fixed in view3dscene 4.2.0-1 has caused the Debian Bug report #1022343, regarding view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by view3dscene to be marked as

Bug#1022451: marked as done (qcat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

Your message dated Sun, 06 Nov 2022 18:54:35 + with message-id and subject line Bug#1022451: fixed in qcat 1.1.0-5 has caused the Debian Bug report #1022451, regarding qcat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 to be marked

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

On Sun, Nov 6, 2022 at 3:51 PM Sebastian Ramacher wrote: > > Source: fastnetmon > Version: 1.2.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com > >

Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

On Fri, Oct 07, 2022 at 02:16:35PM -0300, Antonio Terceiro wrote: >... > But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so > this is a bit weird. >... $ cat /usr/share/rubygems-integration/all/gems/actionmailer-6.1.7/lib/action_mailer/mail_with_error_handling.rb #

Bug#999017: marked as done (xfractint: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 17:43:55 + with message-id and subject line Bug#999017: fixed in xfractint 20.4.10-3 has caused the Debian Bug report #999017, regarding xfractint: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#999035: marked as done (gerstensaft: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 17:36:27 + with message-id and subject line Bug#999035: fixed in gerstensaft 0.3-5 has caused the Debian Bug report #999035, regarding gerstensaft: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#999183: marked as done (dhcpdump: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 17:05:52 + with message-id and subject line Bug#999183: fixed in dhcpdump 1.8-3 has caused the Debian Bug report #999183, regarding dhcpdump: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#999124: marked as done (dhis-server: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 17:05:59 + with message-id and subject line Bug#999124: fixed in dhis-server 5.3-3 has caused the Debian Bug report #999124, regarding dhis-server: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#999096: marked as done (cpufreqd: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 17:04:54 + with message-id and subject line Bug#999096: fixed in cpufreqd 2.4.2-3 has caused the Debian Bug report #999096, regarding cpufreqd: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Processed: tagging 1016279

Processing commands for cont...@bugs.debian.org: > tags 1016279 + fixed Bug #1016279 {Done: Adrian Bunk } [src:libzypp] libzypp: FTBFS: Random.cc:21:27: error: ‘time’ was not declared in this scope Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#999296: tagcloud: diff for NMU version 1.4-1.3

Control: tags 999296 + patch Control: tags 999296 + pending Dear maintainer, I've prepared an NMU for tagcloud (versioned as 1.4-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u tagcloud-1.4/debian/changelog

Processed: tagcloud: diff for NMU version 1.4-1.3

Processing control commands: > tags 999296 + patch Bug #999296 [src:tagcloud] tagcloud: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999296 + pending Bug #999296 [src:tagcloud] tagcloud: missing required debian/rules targets build-arch and/or

Bug#1020525: marked as done (ddskk: fails to install with emacs 1.28)

Your message dated Sun, 06 Nov 2022 16:34:32 + with message-id and subject line Bug#1020525: fixed in ddskk 17.1-9 has caused the Debian Bug report #1020525, regarding ddskk: fails to install with emacs 1.28 to be marked as done. This means that you claim that the problem has been dealt

Processed: spew: diff for NMU version 1.0.8-1.1

Processing control commands: > tags 998965 + patch Bug #998965 [src:spew] spew: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998965 + pending Bug #998965 [src:spew] spew: missing required debian/rules targets build-arch and/or build-indep Added

Bug#1020258: Bug#1020525: ddskk: fails to install with emacs 1.28

On 2022-09-22 at 19:23 +0200, Andreas Beckmann wrote: > (This could be another instance of #1020258, but there is no output > from the actual error available in the log.) As you say, it seems affected by #1020258. ``` emacsen-common: Handling install of emacsen flavor emacs Install ddskk for

Bug#998965: spew: diff for NMU version 1.0.8-1.1

Control: tags 998965 + patch Control: tags 998965 + pending Dear maintainer, I've prepared an NMU for spew (versioned as 1.0.8-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u spew-1.0.8/debian/rules spew-1.0.8/debian/rules ---

Processed: libgcr410: diff for NMU version 2.4.0-9.3

Processing control commands: > tags 999332 + patch Bug #999332 [src:libgcr410] libgcr410: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999332 + pending Bug #999332 [src:libgcr410] libgcr410: missing required debian/rules targets build-arch

Bug#999332: libgcr410: diff for NMU version 2.4.0-9.3

Control: tags 999332 + patch Control: tags 999332 + pending Dear maintainer, I've prepared an NMU for libgcr410 (versioned as 2.4.0-9.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u libgcr410-2.4.0/debian/changelog

Bug#1023531: utox: autopkgtest regression on s390x: test_chrono fails

On 2022-11-06 08:12, Paul Gevers wrote: > Source: utox > Version: 0.18.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > Your package has an autopkgtest, great. With a recent upload of glibc it > started to fail on s390x. Looking at the

Processed: fix version

Processing commands for cont...@bugs.debian.org: > notfixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3 Bug #1022893 {Done: Nilesh Patra } [src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any FTBFS No longer marked as fixed in versions

Processed: xplot: diff for NMU version 1.19-9.1

Processing control commands: > tags 999308 + patch Bug #999308 [src:xplot] xplot: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999308 + pending Bug #999308 [src:xplot] xplot: missing required debian/rules targets build-arch and/or build-indep

Bug#999308: xplot: diff for NMU version 1.19-9.1

Control: tags 999308 + patch Control: tags 999308 + pending Dear maintainer, I've prepared an NMU for xplot (versioned as 1.19-9.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru xplot-1.19/debian/changelog xplot-1.19/debian/changelog

Processed: fixed

Processing commands for cont...@bugs.debian.org: > fixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3 Bug #1022893 [src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any FTBFS Marked as fixed in versions golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-3. > close

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

Source: fastnetmon Version: 1.2.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com https://buildd.debian.org/status/fetch.php?pkg=fastnetmon=amd64=1.2.3-1%2Bb1=1667748889=0

Processed: severity of 1018906 is serious

Processing commands for cont...@bugs.debian.org: > severity 1018906 serious Bug #1018906 {Done: Domenico Andreoli } [dwarves] dwarves: FTBFS with libbpf 1.0.0 Ignoring request to change severity of Bug 1018906 to the same value. > thanks Stopping processing here. Please contact me if you need

Processed: severity of 1018906 is serious

Processing commands for cont...@bugs.debian.org: > severity 1018906 serious Bug #1018906 {Done: Domenico Andreoli } [dwarves] dwarves: FTBFS with libbpf 1.0.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1018906:

Processed: Re: autopkgtest fails with sqlalchemy 1.4.23+ds1

Processing control commands: > tags 995779 + patch Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1 Added tag(s) patch. -- 995779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#995779: autopkgtest fails with sqlalchemy 1.4.23+ds1

Control: tags 995779 + patch This is the upstream merged fix for sqlalchemy 1.4: https://gitlab.com/mailman/mailman/-/commit/c926e3d54680d4fac0648cde036368c699976038

Bug#999137: marked as done (sredird: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 14:49:28 + with message-id and subject line Bug#999137: fixed in sredird 2.2.1-2.1 has caused the Debian Bug report #999137, regarding sredird: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#998950: marked as done (mailsync: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sun, 06 Nov 2022 14:49:17 + with message-id and subject line Bug#998950: fixed in mailsync 5.2.7-3.1 has caused the Debian Bug report #998950, regarding mailsync: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Processed: pyopengl: migrate to libglut3.12

Processing control commands: > block 1023419 by -1 Bug #1023419 [release.debian.org] transition: freeglut 1023419 was not blocked by any bugs. 1023419 was not blocking any bugs. Added blocking bug(s) of 1023419: 1023548 -- 1023419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023419

Bug#1023548: pyopengl: migrate to libglut3.12

Source: pyopengl Version: 3.1.5+dfsg-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 1023419 by -1 pyopengl hardcodes the dependency on freeglut3. As the transition from freeglut3 to libglut3.12 is currently ongoing, pyopengl needs to be fixed. Cheers -- Sebastian Ramacher

Processed: Re: Update bug

Processing commands for cont...@bugs.debian.org: > severity 1023373 important Bug #1023373 [src:bibledit] bibledit: non-source Google Analytics file Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1023373:

Bug#1023373: Further bug discussion

Hi Bastian, Thank you for the extra clarification about what this bug is about, and for the extra details. > We can play a word game but "missing sources" is exactly about > "non-source files". If a file is contained in a package that is not a > source file then its sources are missing.

Bug#1023229: marked as done (f3d: autopkgtest regression on s390x: Compare with ref failed)

Your message dated Sun, 06 Nov 2022 13:34:13 + with message-id and subject line Bug#1023229: fixed in f3d 1.3.1+dfsg-5 has caused the Debian Bug report #1023229, regarding f3d: autopkgtest regression on s390x: Compare with ref failed to be marked as done. This means that you claim that the

Bug#1022339: marked as done (virt-manager: FTBFS: dh_install: error: missing files, aborting)

Your message dated Sun, 06 Nov 2022 12:35:40 + with message-id and subject line Bug#1022339: fixed in virt-manager 1:4.1.0-2 has caused the Debian Bug report #1022339, regarding virt-manager: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim

Processed: Bug#1022339 marked as pending in virt-manager

Processing control commands: > tag -1 pending Bug #1022339 [src:virt-manager] virt-manager: FTBFS: dh_install: error: missing files, aborting Ignoring request to alter tags of bug #1022339 to the same tags previously set -- 1022339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022339

Bug#1022339: marked as pending in virt-manager

Control: tag -1 pending Hello, Bug #1022339 in virt-manager reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1022313: marked as done (gnupg-pkcs11-scd: FTBFS: conftest.c:49:10: fatal error: minix/config.h: No such file or directory)

Your message dated Sun, 06 Nov 2022 10:49:03 + with message-id and subject line Bug#1022313: fixed in gnupg-pkcs11-scd 0.10.0-2 has caused the Debian Bug report #1022313, regarding gnupg-pkcs11-scd: FTBFS: conftest.c:49:10: fatal error: minix/config.h: No such file or directory to be marked

Bug#999145: cappuccino: diff for NMU version 0.5.1-10.1

On Wed, Nov 02, 2022 at 05:45:26PM -0300, Marcos Talau wrote: > Control: tags 999145 + patch > Control: tags 999145 + pending > > > Dear maintainer, > > I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay

Bug#1023178: marked as done (microprofile: Contains non-free source)

Your message dated Sun, 06 Nov 2022 10:00:10 + with message-id and subject line Bug#1023178: fixed in microprofile 4.0+dfsg-1 has caused the Debian Bug report #1023178, regarding microprofile: Contains non-free source to be marked as done. This means that you claim that the problem has been

Bug#1023501: marked as done (busybox-static: version 1:1.35.0-3 breaks boot)

Your message dated Sun, 06 Nov 2022 08:49:16 + with message-id and subject line Bug#1023501: fixed in busybox 1:1.35.0-4 has caused the Debian Bug report #1023501, regarding busybox-static: version 1:1.35.0-3 breaks boot to be marked as done. This means that you claim that the problem has

Bug#1023427: marked as done (pixman: CVE-2022-44638)

Your message dated Sun, 06 Nov 2022 08:35:44 + with message-id and subject line Bug#1023427: fixed in pixman 0.40.0-1.1 has caused the Debian Bug report #1023427, regarding pixman: CVE-2022-44638 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1020079: netplan.io: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

Dear Maintainer, After switching from deprecated nose to pytest, I was able to build your package in a sid chroot environment. I've just applied this PR [1] and updated B-D as suggested in [2] Kind regards [1] https://github.com/canonical/netplan/pull/289 [2]

Processed: Re: busybox-static: version 1:1.35.0-3 breaks boot on hppa

Processing control commands: > tag -1 + confirmed Bug #1023501 [busybox-static] busybox-static: version 1:1.35.0-3 breaks boot Added tag(s) confirmed. -- 1023501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1023501: busybox-static: version 1:1.35.0-3 breaks boot on hppa

Control: tag -1 + confirmed On Sat, 5 Nov 2022 21:18:58 +0100 Robert Luberda wrote: severity 1023501 grave retitle 1023501 busybox-static: version 1:1.35.0-3 breaks boot on hppa and amd64 found 1023501 1:1.35.0-3 notfound 1023501 1:1.35.0-2 On Sat, 05 Nov 2022 13:31:51 + John David

Processed: retitle 1023501 to busybox-static: version 1:1.35.0-3 breaks boot

Processing commands for cont...@bugs.debian.org: > retitle 1023501 busybox-static: version 1:1.35.0-3 breaks boot Bug #1023501 [busybox-static] busybox-static: version 1:1.35.0-3 breaks boot on hppa Changed Bug title to 'busybox-static: version 1:1.35.0-3 breaks boot' from 'busybox-static:

Processed: src:ruby-liquid: fails to migrate to testing for too long: new BD not available in testing

Processing control commands: > close -1 5.4.0-2 Bug #1023534 [src:ruby-liquid] src:ruby-liquid: fails to migrate to testing for too long: new BD not available in testing Marked as fixed in versions ruby-liquid/5.4.0-2. Bug #1023534 [src:ruby-liquid] src:ruby-liquid: fails to migrate to testing

Bug#1023534: src:ruby-liquid: fails to migrate to testing for too long: new BD not available in testing

Source: ruby-liquid Version: 4.0.3-3 Severity: serious Control: close -1 5.4.0-2 Tags: sid bookworm 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 60 days

Bug#1023531: utox: autopkgtest regression on s390x: test_chrono fails

Source: utox Version: 0.18.1-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. With a recent upload of glibc it started to fail on s390x. Looking at the history [1], I noticed that apparently the test can flip

Bug#1022295: marked as done (llvm-toolchain-13: FTBFS: build-dependency not installable: llvm-spirv)

Your message dated Sun, 06 Nov 2022 07:00:37 + with message-id and subject line Bug#1022295: fixed in llvm-toolchain-13 1:13.0.1-9 has caused the Debian Bug report #1022295, regarding llvm-toolchain-13: FTBFS: build-dependency not installable: llvm-spirv to be marked as done. This means that

Bug#1023466: marked as done (llvm-toolchain-13: FTBFS with swig 4.1: interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined)

Your message dated Sun, 06 Nov 2022 07:00:37 + with message-id and subject line Bug#1023466: fixed in llvm-toolchain-13 1:13.0.1-9 has caused the Debian Bug report #1023466, regarding llvm-toolchain-13: FTBFS with swig 4.1: interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined to

Bug#1023530: nut: flaky autopkgtest: varying failures

Source: nut Version: 2.8.0-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails (after the fix for bug #1019221). Because the unstable-to-testing migration