Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild

Dear Paul, On Thu, 10 Aug 2023 21:44:23 +0200 Paul Gevers wrote: [...]¨ Your package src:utop has been trying to migrate for 37 days [2]. [...] > If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. One cur

Bug#1043439: lying in the changelog: Source-only upload

Package: src:r-bioc-saturn Version: 1.8.0+dfsg-2 Severity: serious Tags: sid trixie see http://launchpadlibrarian.net/680969404/r-bioc-saturn_1.8.0+dfsg-1_1.8.0+dfsg-2.diff.gz removing build dependencies, causing ftbfs

Bug#1039487: Resolving #1039487 - zsnapd (my package) removed from testing

Hi! Can't we just resolve this by patching #elif defined(__aarch64__) #include out of include/os/linux/kernel/linux/simd.h in the zfs modules source and thus forcing the use of: #else #define kfpu_allowed() 0 #define kfpu_begin()do {} while (0) #define kfpu_end()

Bug#1042162: marked as done (rust-erbium-core: FTBFS: unsatisfiable build-dependencies: librust-erbium-net-dev : Depends: librust-netlink-packet-core-0.4+default-dev but it is not installable)

Your message dated Fri, 11 Aug 2023 02:43:57 +0100 with message-id and subject line re: rust-erbium-core: FTBFS: unsatisfiable build-dependencies: librust-erbium-net-dev : Depends: librust-netlink-packet-core-0.4+default-dev but it is not installable has caused the Debian Bug report #1042162, re

Bug#1043421: marked as done (rust-rustls FTBFS: file not found error.)

Your message dated Fri, 11 Aug 2023 00:36:45 + with message-id and subject line Bug#1043421: fixed in rust-rustls 0.21.6-2 has caused the Debian Bug report #1043421, regarding rust-rustls FTBFS: file not found error. to be marked as done. This means that you claim that the problem has been de

Processed: re: netavark: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~)

Processing commands for cont...@bugs.debian.org: > tags 1042194 +patch Bug #1042194 [src:netavark] netavark: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) Added tag(s) patch. > thanks

Bug#1042194: netavark: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~)

tags 1042194 +patch thanks During a rebuild of all packages in sid, your package failed to build on amd64. The attached patch makes netavark build again (note: some of the packages it depends on have only just been accepted, so it may be a little time before binaries are available in sid).diff

Bug#1030322: marked as done (gnushogi: FTBFS with TeXInfo 7.0.x)

Your message dated Thu, 10 Aug 2023 23:39:58 + with message-id and subject line Bug#1030322: fixed in gnushogi 1.5~git20140725-2.1 has caused the Debian Bug report #1030322, regarding gnushogi: FTBFS with TeXInfo 7.0.x to be marked as done. This means that you claim that the problem has been

Bug#1030322: gnushogi: FTBFS with TeXInfo 7.0.x

I am uploading a NMU to move the experimental version to unstable in order to fix this. The debdiff is attached.diff -Nru gnushogi-1.5~git20140725/debian/changelog gnushogi-1.5~git20140725/debian/changelog --- gnushogi-1.5~git20140725/debian/changelog 2020-04-03 19:54:19.0 +0200 +++ gn

Bug#1043417: libwraster6: libwraster ABI breakage

Hi Andreas, On Thu 10 Aug 2023 06:14:44 PM +02, Andreas Metzler wrote: already communicated upstream, lets add a blocker bug. The new release bumped the symbol version of all symbols from LIBWRASTER6 to LIBWRASTER7, i.e. we have got total ABI breakage, none of the previously exported symbols ar

Bug#1037801: openexr: diff for NMU version 3.1.5-5.1

Control: tags 1037801 + patch Control: tags 1037801 + pending Dear maintainer, I've prepared an NMU for openexr (versioned as 3.1.5-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru openexr-3.1.5/debian/changelog openexr-3.1.5/debian/chang

Processed: openexr: diff for NMU version 3.1.5-5.1

Processing control commands: > tags 1037801 + patch Bug #1037801 [src:openexr] openexr: ftbfs with GCC-13 Added tag(s) patch. > tags 1037801 + pending Bug #1037801 [src:openexr] openexr: ftbfs with GCC-13 Added tag(s) pending. -- 1037801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037801

Bug#1043426: (no subject)

Pixel Saver was working properly with Debian 11 bullseye on both machines.

Bug#1042331: marked as done (rygel: FTBFS: ../meson.build:1:0: ERROR: Unexpected "[provides]" section, did you mean "[provide]"?)

Your message dated Thu, 10 Aug 2023 19:51:49 + with message-id and subject line Bug#1042331: fixed in rygel 0.42.4-1 has caused the Debian Bug report #1042331, regarding rygel: FTBFS: ../meson.build:1:0: ERROR: Unexpected "[provides]" section, did you mean "[provide]"? to be marked as done.

Bug#1040755: marked as done (ftbfs in rygel with meson 1.2.0 rc2)

Your message dated Thu, 10 Aug 2023 19:51:49 + with message-id and subject line Bug#1040755: fixed in rygel 0.42.4-1 has caused the Debian Bug report #1040755, regarding ftbfs in rygel with meson 1.2.0 rc2 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1043427: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild

Source: utop Version: 2.13.0-1 Severity: serious Control: close -1 2.13.1-2 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 havi

Processed: src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild

Processing control commands: > close -1 2.13.1-2 Bug #1043427 [src:utop] src:utop: fails to migrate to testing for too long: blocked by ocaml-logs rebuild Marked as fixed in versions utop/2.13.1-2. Bug #1043427 [src:utop] src:utop: fails to migrate to testing for too long: blocked by ocaml-logs

Bug#1043426: GNOME freezes when Pixel Saver is enabled

Package: gnome-shell-extension-pixelsaver Version: 1.30-1 Severity: critical Enabling the Pixel Saver GNOME Shell Extension freezes GNOME immediately. No mouse or keyboard input is accepted. Only Alt+SysRq+k gets me out of it. On subsequent sessions, i.e. with Pixel Saver previously enabled, GNOM

Bug#1030129: (no subject)

Are there any plans to backport this? Is the bug in a state that allows it to show up as an action item for the maintainers?

Bug#1037850: marked as done (rssguard: ftbfs with GCC-13)

Your message dated Thu, 10 Aug 2023 18:19:38 + with message-id and subject line Bug#1037850: fixed in rssguard 4.0.4+dfsg-1.1 has caused the Debian Bug report #1037850, regarding rssguard: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1038913: marked as done (libmsv: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023)

Your message dated Thu, 10 Aug 2023 18:14:07 + with message-id and subject line Bug#1038913: fixed in libmsv 1.1.1-4 has caused the Debian Bug report #1038913, regarding libmsv: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 to be marked as done. This means that

Bug#1042734: marked as done (binutils-mingw-w64 FTBFS: Patch debian/patches/specify-timestamp.patch does not apply)

Your message dated Thu, 10 Aug 2023 18:07:36 + with message-id and subject line Bug#1042734: fixed in binutils-mingw-w64 11+nmu1 has caused the Debian Bug report #1042734, regarding binutils-mingw-w64 FTBFS: Patch debian/patches/specify-timestamp.patch does not apply to be marked as done. Th

Processed: [bts-link] source package src:gnome-shell

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gnome-shell > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:rygel

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:rygel > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Bug#1043421: rust-rustls FTBFS: file not found error.

Package: rust-rustls Version: 0.21.6-1 Severity: serious rust-rustls fails to build from source. error: couldn't read rustls/build.rs: No such file or directory (os error 2) error: could not compile `rustls` due to previous error

Bug#1043418: rust-rustls-webpki - autopkgtest failure, file not found errors.

Package: rust-rustls-webpki Version: 0.101.2-2 Severity: serious The autopkgtest for rust-rustls-webpki is failing with a bunch of file not found errors. the first of which is pasted below. 199s error: couldn't read src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-s

Bug#1038912: marked as done (libreswan: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023)

Your message dated Thu, 10 Aug 2023 16:15:19 + with message-id and subject line Bug#1038912: fixed in libreswan 4.12-1 has caused the Debian Bug report #1038912, regarding libreswan: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 to be marked as done. This means

Bug#1043417: libwraster6: libwraster ABI breakage

Package: libwraster6 Version: 0.96.0-1 Severity: grave Tags: upstream Justification: Policy 8.6.2 Hello, already communicated upstream, lets add a blocker bug. The new release bumped the symbol version of all symbols from LIBWRASTER6 to LIBWRASTER7, i.e. we have got total ABI breakage, none of th

Bug#1042889: Debian PR #1042889

Hi. Kurt Hornik writes ("Debian PR #1042889"): > Have you seen > > ? No. > This points to a branch of VM at > > which apparently at some point in time passed native compilation (I > never

Bug#1042889: Debian PR #1042889

Ian/Dirk, Have you seen ? This points to a branch of VM at which apparently at some point in time passed native compilation (I never got a chance to try to far). I can try to follow u

Bug#1043381: marked as done (amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception)

Your message dated Thu, 10 Aug 2023 13:50:27 + with message-id and subject line Bug#1043381: fixed in amd64-microcode 3.20230808.1.1 has caused the Debian Bug report #1043381, regarding amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception to be marked

Bug#1043118: victoriametrics: FTBFS: test failure

On Thu, Aug 10, 2023 at 5:57 PM Guillem Jover wrote: > > Hi! > I cannot reproduce this one on my sid chroot, but another error > completely different in TestMarshalUnmarshalInt64Array. > This is a flaky test, I have reported it to upstream and it has been fixed. https://github.com/VictoriaMetrics

Bug#1043381: marked as done (amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception)

Your message dated Thu, 10 Aug 2023 13:19:09 + with message-id and subject line Bug#1043381: fixed in amd64-microcode 3.20230808.1 has caused the Debian Bug report #1043381, regarding amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception to be marked as

Bug#1043313: marked as done (libsuperlu-dev: Inconsistent declaration of double{C,M}alloc())

Your message dated Thu, 10 Aug 2023 12:22:14 + with message-id and subject line Bug#1043313: fixed in superlu 6.0.0+dfsg1-3 has caused the Debian Bug report #1043313, regarding libsuperlu-dev: Inconsistent declaration of double{C,M}alloc() to be marked as done. This means that you claim that

Processed: tagging 1036943

Processing commands for cont...@bugs.debian.org: > tags 1036943 + trixie-ignore Bug #1036943 {Done: Stefano Rivera } [dh-python] dh-python: please reinstate Breaks+Replaces: python2 (<< 2.7.18-2) Added tag(s) trixie-ignore. > thanks Stopping processing here. Please contact me if you need assista

Processed: tagging 1037887

Processing commands for cont...@bugs.debian.org: > tags 1037887 + experimental Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13 Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103

Bug#1042306: marked as done (keystone: FTBFS: AssertionError: len(context) = 22)

Your message dated Thu, 10 Aug 2023 11:50:54 + with message-id and subject line Bug#1042306: fixed in keystone 2:23.0.0-5 has caused the Debian Bug report #1042306, regarding keystone: FTBFS: AssertionError: len(context) = 22 to be marked as done. This means that you claim that the problem ha

Bug#1025545: marked as done (bleachbit: dependency on transitional policykit-1 package)

Your message dated Thu, 10 Aug 2023 11:49:08 + with message-id and subject line Bug#1025545: fixed in bleachbit 4.4.2-2 has caused the Debian Bug report #1025545, regarding bleachbit: dependency on transitional policykit-1 package to be marked as done. This means that you claim that the probl

Processed: Bug#1025545 marked as pending in bleachbit

Processing control commands: > tag -1 pending Bug #1025545 [bleachbit] bleachbit: dependency on transitional policykit-1 package Added tag(s) pending. -- 1025545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025545: marked as pending in bleachbit

Control: tag -1 pending Hello, Bug #1025545 in bleachbit 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/bleachbit/-/commit/2763dcfde068dfe

Processed: Bug#1042306 marked as pending in keystone

Processing control commands: > tag -1 pending Bug #1042306 [src:keystone] keystone: FTBFS: AssertionError: len(context) = 22 Added tag(s) pending. -- 1042306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1042306: marked as pending in keystone

Control: tag -1 pending Hello, Bug #1042306 in keystone 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/openstack-team/services/keystone/-/commit/9ecf4f9de01aa2

Bug#1042869: marked as done (sniffles: Please update to newer version without python3-pep517 requirement)

Your message dated Thu, 10 Aug 2023 11:04:13 + with message-id and subject line Bug#1042869: fixed in sniffles 2.2-1 has caused the Debian Bug report #1042869, regarding sniffles: Please update to newer version without python3-pep517 requirement to be marked as done. This means that you clai

Bug#1041127: marked as done (pbcopper FTBFS with gcc 13)

Your message dated Thu, 10 Aug 2023 11:00:12 + with message-id and subject line Bug#1041127: fixed in pbcopper 2.2.0+dfsg-1 has caused the Debian Bug report #1041127, regarding pbcopper FTBFS with gcc 13 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: update version information

Processing commands for cont...@bugs.debian.org: > found 1034988 meep/1.17.1-1 Bug #1034988 {Done: Thorsten Alteholz } [python3-meep] python3-meep: missing Breaks+Replaces in multiple situations when upgrading from bullseye Marked as found in versions meep/1.17.1-1. > thanks Stopping processing

Bug#1043313: libsuperlu-dev: Inconsistent declaration of double{C,M}alloc()

Source: superlu Followup-For: Bug #1043313 Upstream has just released a new version to fix it. Apparently it introduced other problems however. Let's see what upstream's response to that is.

Bug#1042045: marked as done (strace: FTBFS: ../../src/io_uring.c:568:28: error: ‘struct io_uring_buf_reg’ has no member named ‘pad’)

Your message dated Thu, 10 Aug 2023 10:28:37 + with message-id and subject line Bug#1042045: fixed in strace 6.4-0.1 has caused the Debian Bug report #1042045, regarding strace: FTBFS: ../../src/io_uring.c:568:28: error: ‘struct io_uring_buf_reg’ has no member named ‘pad’ to be marked as done

Bug#1041263: marked as done (fontconfig: depends on removed fonts-liberation2)

Your message dated Thu, 10 Aug 2023 10:27:29 + with message-id and subject line Bug#1041263: fixed in fontconfig 2.14.2-1 has caused the Debian Bug report #1041263, regarding fontconfig: depends on removed fonts-liberation2 to be marked as done. This means that you claim that the problem has

Processed: update metadata for dumat

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was hel...@subdivi.de). > usertags 1034995 + fileconflict There were no usertags set. Usertags are now: fileconflict. > affects 1034995 + python-dev-is-python2 Bug #103499

Bug#1036996: python3-notebook: Is Breaks: cadabra2 enough?

Hi Andreas, you fixed python3-notebook by adding versioned Breaks for cadabra2. Is this really enough? A Breaks condition allows concurrent unpack (but not concurrent configuration). An inconvenient unpack order could have bad results here, so I think this should be upgraded to versioned Conflict

Processed: update bug metadata

Processing commands for cont...@bugs.debian.org: > unarchive 1034988 Bug #1034988 {Done: Thorsten Alteholz } [python3-meep] python3-meep: missing Breaks+Replaces in multiple situations when upgrading from bullseye Unarchived Bug 1034988 > user debian...@lists.debian.org Setting user to debian...

Bug#1043118: victoriametrics: FTBFS: test failure

Hi! On Tue, 2023-08-08 at 14:59:45 +0300, Denys Holius wrote: > The latest version of VictoriaMetrics v1.92.0 > should be marked as > LTS but it has some backwards-incompatible changes. Meanwhile v1.87.6 >

Processed: Re: track correct binary package

Processing commands for cont...@bugs.debian.org: > found 1036996 jupyter-notebook/6.2.0-1, jupyter-notebook/6.4.12-2.1 Bug #1036996 [python3-notebook] cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror Marked as found in ver

Processed (with 2 errors): track correct binary package

Processing commands for cont...@bugs.debian.org: > reassign 1036996 python3-notebook Bug #1036996 [jupyter-notebook] cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror Bug reassigned from package 'jupyter-notebook' to 'pytho

Processed: tagging 1040043

Processing commands for cont...@bugs.debian.org: > tags 1040043 - a11y Bug #1040043 [rspamd] rspamd on aarch64 produces segfaults Removed tag(s) a11y. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104004

Bug#1041836: marked as done (libc6 2.36-9+deb12u1 stack smashing on some but not all amd64)

Your message dated Thu, 10 Aug 2023 10:06:38 +0200 with message-id and subject line Re: Bug#1041836: libc6 2.36-9+deb12u1 stack smashing on some but not all amd64 has caused the Debian Bug report #1041836, regarding libc6 2.36-9+deb12u1 stack smashing on some but not all amd64 to be marked as don

Bug#1041836: libc6 2.36-9+deb12u1 double free abort

Hi, On 2023-08-10 16:46, Paul Szabo wrote: > I now tried the idea whether the amount of memory in the machine has a > relevance to my "inetd: double free detected in tcache 2, abort" issue. > I tried "mem=8G" and similar as kernel boot parameter; that produced > more-or-less the expected results f

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1038909 serious Bug #1038909 [dd-opentracing-cpp] dd-opentracing-cpp: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 Severity set to 'serious' from 'important' > severity 1038910 serious Bug #1038910 [licens