Processed: limit source to linux, tagging 1040901, tagging 1053503, tagging 1055069, tagging 1051365 ...

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1040901 + pending Bug #1040901 [src:linux] linux modules must not be signed with CA key, bump ABI every

Processed: tagging 1056902, found 1056764 in 2.12~rc1-12, notfound 1056764 in 2.06-13, found 1056348 in 1.11.0-2 ...

Processing commands for cont...@bugs.debian.org: > tags 1056902 + sid trixie Bug #1056902 [libbytelist-java] libbytelist-java: Package is obsolete and should be removed before trixie release Added tag(s) trixie and sid. > found 1056764 2.12~rc1-12 Bug #1056764 [grub-efi-amd64] grub-efi-amd64:

Processed: severity of 1057067 is wishlist

Processing commands for cont...@bugs.debian.org: > severity 1057067 wishlist Bug #1057067 [src:rclone] new upstream release (1.65) Severity set to 'wishlist' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1057067:

Bug#1057067: new upstream release (1.65)

Source: rclone Severity: critical Debian is somewhat lagging behind upstream. Unstable currently has 1.60.1 (2022-11-17, uploaded to unstable on 2022-12-13) while upstream is at 1.65.0 (released 2022-11-26). It looks like upstream does a release roughly every two months, is there a plan to

Bug#1055678: marked as done (librnd4-lib-gtk has an undeclared file conflict)

Your message dated Tue, 28 Nov 2023 20:17:12 -0700 (MST) with message-id <20231129031712.a58266060...@rover.gag.com> and subject line fixed in 4.1.0-3 has caused the Debian Bug report #1055678, regarding librnd4-lib-gtk has an undeclared file conflict to be marked as done. This means that you

Bug#1054975: marked as done (haskell-copilot: FTBFS: unsatisfiable build-dependencies)

Your message dated Tue, 28 Nov 2023 20:36:30 -0500 (EST) with message-id <5dd23ee7-3ce2-f748-5cef-d0581142...@techie.net> and subject line Fixed has caused the Debian Bug report #1054975, regarding haskell-copilot: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you

Bug#1054928: marked as done (haskell-copilot-libraries: FTBFS: unsatisfiable build-dependencies)

Your message dated Tue, 28 Nov 2023 20:35:42 -0500 (EST) with message-id and subject line Fixed has caused the Debian Bug report #1054928, regarding haskell-copilot-libraries: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you claim that the problem has been dealt

Bug#1053259: marked as done (gst-plugins-bad1.0: CVE-2023-40476)

Your message dated Wed, 29 Nov 2023 00:49:23 + with message-id and subject line Bug#1053259: fixed in gst-plugins-bad1.0 1.22.7-1 has caused the Debian Bug report #1053259, regarding gst-plugins-bad1.0: CVE-2023-40476 to be marked as done. This means that you claim that the problem has been

Bug#1056102: marked as done (gst-plugins-bad1.0: CVE-2023-44429: AV1 codec parser buffer overflow)

Your message dated Wed, 29 Nov 2023 00:49:23 + with message-id and subject line Bug#1056102: fixed in gst-plugins-bad1.0 1.22.7-1 has caused the Debian Bug report #1056102, regarding gst-plugins-bad1.0: CVE-2023-44429: AV1 codec parser buffer overflow to be marked as done. This means that

Bug#1056101: marked as done (gst-plugins-bad1.0: CVE-2023-44446: MXF demuxer use-after-free)

Your message dated Wed, 29 Nov 2023 00:49:23 + with message-id and subject line Bug#1056101: fixed in gst-plugins-bad1.0 1.22.7-1 has caused the Debian Bug report #1056101, regarding gst-plugins-bad1.0: CVE-2023-6: MXF demuxer use-after-free to be marked as done. This means that you

Bug#1053261: marked as done (gst-plugins-bad1.0: CVE-2023-40474)

Your message dated Wed, 29 Nov 2023 00:49:23 + with message-id and subject line Bug#1053261: fixed in gst-plugins-bad1.0 1.22.7-1 has caused the Debian Bug report #1053261, regarding gst-plugins-bad1.0: CVE-2023-40474 to be marked as done. This means that you claim that the problem has been

Bug#1053260: marked as done (gst-plugins-bad1.0: CVE-2023-40475)

Your message dated Wed, 29 Nov 2023 00:49:23 + with message-id and subject line Bug#1053260: fixed in gst-plugins-bad1.0 1.22.7-1 has caused the Debian Bug report #1053260, regarding gst-plugins-bad1.0: CVE-2023-40475 to be marked as done. This means that you claim that the problem has been

Bug#1054952: marked as done (haskell-copilot-language: FTBFS: unsatisfiable build-dependencies)

Your message dated Wed, 29 Nov 2023 00:34:04 + with message-id and subject line Bug#1054952: fixed in haskell-copilot-language 3.17-2 has caused the Debian Bug report #1054952, regarding haskell-copilot-language: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that

Bug#1054819: marked as done (ezdxf: FTBFS: make[2]: *** [Makefile:44: html] Error 2)

Your message dated Sat, 25 Nov 2023 16:13:05 -0700 (MST) with message-id <20231125231305.cd3eb6060...@rover.gag.com> and subject line fixed in 1.1.3-1 has caused the Debian Bug report #1054819, regarding ezdxf: FTBFS: make[2]: *** [Makefile:44: html] Error 2 to be marked as done. This means that

Bug#1057058: liquidsoap-doc: missing Breaks+Replaces: liquidsoap (<< 2.2.2)

Package: liquidsoap-doc Version: 2.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#1057056: rust-comrak: Unsatisfiable dependency on rust-emojis

Source: rust-comrak Version: 0.18.0-1 Severity: serious X-Debbugs-CC: sylves...@debian.org, aferra...@debian.org librust-comrak-dev depends on librust-emojis-0.5+default-dev but that is not packaged in Debian. Thank you, Jeremy Bícha

Bug#1054831: marked as done (haskell-hashable-time: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)

Your message dated Tue, 28 Nov 2023 19:07:12 + with message-id and subject line Bug#1054369: Removed package(s) from unstable has caused the Debian Bug report #1054831, regarding haskell-hashable-time: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25

Bug#1054970: marked as done (haskell-drbg: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-cereal-dev-0.5.8.3-8b478, libghc-crypt

Your message dated Tue, 28 Nov 2023 19:06:18 + with message-id and subject line Bug#1054365: Removed package(s) from unstable has caused the Debian Bug report #1054970, regarding haskell-drbg: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406,

Bug#1054858: marked as done (haskell-monadcryptorandom: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)

Your message dated Tue, 28 Nov 2023 19:07:39 + with message-id and subject line Bug#1054370: Removed package(s) from unstable has caused the Debian Bug report #1054858, regarding haskell-monadcryptorandom: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error

Bug#1054864: marked as done (haskell-cipher-aes128: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:149: debian/hlibrary.setup] Error 25)

Your message dated Tue, 28 Nov 2023 19:06:45 + with message-id and subject line Bug#1054366: Removed package(s) from unstable has caused the Debian Bug report #1054864, regarding haskell-cipher-aes128: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:149: debian/hlibrary.setup] Error 25

Bug#1054850: marked as done (haskell-template: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)

Your message dated Tue, 28 Nov 2023 19:05:35 + with message-id and subject line Bug#1054352: Removed package(s) from unstable has caused the Debian Bug report #1054850, regarding haskell-template: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25 to be

Bug#1012221: marked as done (rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.)

Your message dated Tue, 28 Nov 2023 18:56:14 + with message-id and subject line Bug#1053614: Removed package(s) from unstable has caused the Debian Bug report #1012221, regarding rust-stdweb-internal-macros (build-)depends on old version of rust-sha1. to be marked as done. This means that

Bug#1051109: marked as done (gtkpod: Intent to request removal from Debian)

Your message dated Tue, 28 Nov 2023 18:50:46 + with message-id and subject line Bug#1018855: Removed package(s) from unstable has caused the Debian Bug report #1051109, regarding gtkpod: Intent to request removal from Debian to be marked as done. This means that you claim that the problem

Bug#1051108: marked as done (anjuta: FTBFS: 1 failed unexpectedly)

Your message dated Tue, 28 Nov 2023 18:51:37 + with message-id and subject line Bug#1018726: Removed package(s) from unstable has caused the Debian Bug report #1051108, regarding anjuta: FTBFS: 1 failed unexpectedly to be marked as done. This means that you claim that the problem has been

Bug#1019305: marked as done (anjuta: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev)

Your message dated Tue, 28 Nov 2023 18:51:37 + with message-id and subject line Bug#1018726: Removed package(s) from unstable has caused the Debian Bug report #1019305, regarding anjuta: Please build-depend on libgdk-pixbuf-2.0-dev instead of libgdk-pixbuf2.0-dev to be marked as done. This

Bug#1055778: marked as done (libamtk-5-dev: Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be installed)

Your message dated Tue, 28 Nov 2023 18:47:52 + with message-id and subject line Bug#1056584: Removed package(s) from unstable has caused the Debian Bug report #1055778, regarding libamtk-5-dev: Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be installed to be marked as done. This

Bug#1054746: marked as done (ruby-factory-bot-rails: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1477:in `rescue in block in activate_dependencies': Could

Your message dated Tue, 28 Nov 2023 16:34:28 + with message-id and subject line Bug#1054746: fixed in ruby-factory-bot-rails 6.4.2-1 has caused the Debian Bug report #1054746, regarding ruby-factory-bot-rails: FTBFS: ERROR: Test "ruby3.1" failed:

Processed: block bugs

Processing commands for cont...@bugs.debian.org: > block 1053953 by 1055092 Bug #1053953 [src:rust-indexmap] rust-indexmap: please upgrade to v2 1053953 was not blocked by any bugs. 1053953 was not blocking any bugs. Added blocking bug(s) of 1053953: 1055092 > block 1055092 by 1050086 Bug

Bug#1056348: FTBFS: tests fail in clean environment

Hey Nicolas! On Fri, Nov 24, 2023 at 11:26:25AM -0500, Nicolas Mora wrote: >Hello, > >I've forwarded the bug upstream [1] and they made a patch [2]. > >Can you test their patch on your package, to check if the problem is fixed on >your CI? > >Also, if this works, I suggest to apply their patch

Bug#929165: marked as done (ubuntu-keyring removes configuration files without checking)

Your message dated Tue, 28 Nov 2023 15:35:20 + with message-id and subject line Bug#929165: fixed in ubuntu-keyring 2023.11.28.1-0.2 has caused the Debian Bug report #929165, regarding ubuntu-keyring removes configuration files without checking to be marked as done. This means that you claim

Bug#1057035: marked as done (Missing Breaks/Replaces / file conflict with ubuntu-cloud-keyring)

Your message dated Tue, 28 Nov 2023 15:35:21 + with message-id and subject line Bug#1057035: fixed in ubuntu-keyring 2023.11.28.1-0.2 has caused the Debian Bug report #1057035, regarding Missing Breaks/Replaces / file conflict with ubuntu-cloud-keyring to be marked as done. This means that

Bug#1054998: marked as done (strace: FTBFS: ../../src/io_uring.c:48:16: error: ‘const struct io_sqring_offsets’ has no member named ‘resv2’; did you mean ‘resv1’?)

Your message dated Tue, 28 Nov 2023 22:50:26 +0800 with message-id and subject line close 1054998 has caused the Debian Bug report #1054998, regarding strace: FTBFS: ../../src/io_uring.c:48:16: error: ‘const struct io_sqring_offsets’ has no member named ‘resv2’; did you mean ‘resv1’? to be

Processed (with 1 error): Merge #1053420 #1054722 for rust-matchers

Processing commands for cont...@bugs.debian.org: > merge 1053420 1054722 Bug #1053420 [rust-matchers] rust-matchers - incompatible with mew regex-automata Unable to merge bugs because: package of #1054722 is 'src:rust-matchers' not 'rust-matchers' Failed to merge 1053420: Did not alter merged

Bug#1054294: marked as done (mlpack: binary-all FTBFS)

Your message dated Tue, 28 Nov 2023 12:34:11 + with message-id and subject line Bug#1054294: fixed in mlpack 4.3.0-1 has caused the Debian Bug report #1054294, regarding mlpack: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1057035: Missing Breaks/Replaces / file conflict with ubuntu-cloud-keyring

Package: ubuntu-keyring Version: 2023.11.28.1-0.1 Severity: serious Preparing to unpack .../ubuntu-keyring_2023.11.28.1-0.1_all.deb ... Unpacking ubuntu-keyring (2023.11.28.1-0.1) over (2020.06.17.1-1) ... dpkg: error processing archive

Bug#1057032: wims: An updated package of wims closing all bugs exists.

Source: wims Version: 2:4.22~dfsg1-2 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Hello, I use an updated package for wims 4.27a closing all actual bugs of version: 2:4.22~dfsg1-2 : wims (2:4.27a~dfsg1-1) UNRELEASED;

Bug#1042099: marked as done (liquidsoap FTBFS: Error: This expression has type ... but an expression was expected of type)

Your message dated Tue, 28 Nov 2023 10:22:37 + with message-id and subject line Bug#1042099: fixed in liquidsoap 2.2.2-1 has caused the Debian Bug report #1042099, regarding liquidsoap FTBFS: Error: This expression has type ... but an expression was expected of type to be marked as done.