Bug#1072366: libndp: CVE-2024-5564

2024-06-10 Thread Florian Ernst
Hello Moritz, On Mon, Jun 10, 2024 at 01:56:16PM +0200, Moritz Muehlenhoff wrote: > It would be great if you could prepare updates for bullseye-security and > bookworm-security [1]. Please use 1.6-1+deb11u1 and 1.8-1+deb12u1 as the > respective version numbers. security.debian.org also has autopkg

Bug#1072963: jpeg-xl: Failing autopkgtests on non-amd64

2024-06-10 Thread Mathieu Malaterre
Julian, On Tue, Jun 11, 2024 at 1:06 AM Jeremy Bícha wrote: > > Source: jpeg-xl > Version: 0.9.2-6 > Severity: serious > Tags: experimental > > jpeg-xl in experimental has autopkgtests that are failing on all > architectures except for amd64. > > Specifically, the problem is that debian/libjxl-gd

Bug#1072969: pytorch: CVE-2024-5480

2024-06-10 Thread Salvatore Bonaccorso
Source: pytorch Version: 2.1.2+dfsg-4 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 pytorch. CVE-2024-5480[0]: | A vulnerability in the PyTorch's torch.distributed

Bug#1072824: marked as done (odin FTBFS with VTK 9.3.0)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 05:04:09 + with message-id and subject line Bug#1072824: fixed in odin 2.0.5-6 has caused the Debian Bug report #1072824, regarding odin FTBFS with VTK 9.3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Processed: Bug#1072824 marked as pending in odin

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072824 [src:odin] odin FTBFS with VTK 9.3.0 Added tag(s) pending. -- 1072824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072824: marked as pending in odin

2024-06-10 Thread Anton Gladky
Control: tag -1 pending Hello, Bug #1072824 in odin 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/odin/-/commit/65d4b30820cd234ad26e1b753162352e38a2f

Bug#1070411: containerd fails to build as a normal user due to sysctl

2024-06-10 Thread Reinhard Tartler
Jochen Sprickerhof writes: > containerd uses sysctl during the build which fails as a normal user: > > === RUN TestLinuxSandboxContainerSpec > sandbox_run_linux_test.go:241: TestCase "spec should reflect original > config" > sandbox_run_linux_test.go:71: Check PodSandbox annotations

Bug#1060474: marked as done (pulseaudio: Please switch Build-Depends to systemd-dev)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 23:34:05 + with message-id and subject line Bug#1060474: fixed in pulseaudio 16.1+dfsg1-5.1 has caused the Debian Bug report #1060474, regarding pulseaudio: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the

Bug#1072766: rust-alacritty: FTBFS: unsatisfiable build-dependencies

2024-06-10 Thread James McCoy
On Fri, Jun 07, 2024 at 05:23:32PM GMT, Santiago Vila wrote: > > [...] > Install main build dependencies (apt-based resolver) > > > Installing build dependencies >

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

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 23:20:16 + with message-id and subject line Bug#1063647: fixed in sysconfig 0.0.14+nmu1 has caused the Debian Bug report #1063647, regarding sysconfig: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means tha

Bug#1060474: Bug#1072960: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

2024-06-10 Thread Jeremy Bícha
On Mon, Jun 10, 2024 at 6:24 PM Chris Hofstaedtler wrote: > I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and > uploaded it to DELAYED/7. Please feel free to tell me if I > should delay it longer. Feel free to upload now without delay. Thank you, Jeremy Bícha

Bug#1072963: jpeg-xl: Failing autopkgtests on non-amd64

2024-06-10 Thread Jeremy Bícha
Source: jpeg-xl Version: 0.9.2-6 Severity: serious Tags: experimental jpeg-xl in experimental has autopkgtests that are failing on all architectures except for amd64. Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64 a

Bug#1071295: apt-cacher-ng: diff for NMU version 3.7.4-1.1

2024-06-10 Thread Chris Hofstaedtler
Control: tags -1 + patch pending Dear maintainer, I've prepared an NMU for apt-cacher-ng (versioned as 3.7.4-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru apt-cacher-ng-3.7.4/debian/changelog apt-cacher-ng-3.7.4/debian/changelog -

Processed: apt-cacher-ng: diff for NMU version 3.7.4-1.1

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch pending Bug #1071295 [src:apt-cacher-ng] apt-cacher-ng: FTBFS: src/meta.h:326:44: error: operator '!' has no right operand Added tag(s) patch and pending. -- 1071295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071295 Debian Bug Tracking Sys

Bug#1060474: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

2024-06-10 Thread Chris Hofstaedtler
Control: tags -1 + patch pending Dear maintainer, I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru pulseaudio-16.1+dfsg1/debian/changelog pulseaudio-16.1+dfsg1/debian/chan

Processed: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch pending Bug #1060474 [src:pulseaudio] pulseaudio: Please switch Build-Depends to systemd-dev Added tag(s) patch and pending. -- 1060474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060474 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1057576: marked as done (mako: FTBFS: dh_sphinxdoc: error: debian/python-mako-doc/usr/share/doc/python-mako-doc/html/search.html top-level node does not have data-content_root attribute)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 23:57:00 +0200 with message-id <20240610215700.rvxouigrondw6...@piotr.cc> and subject line fixed in zzzeeksphinx has caused the Debian Bug report #1057576, regarding mako: FTBFS: dh_sphinxdoc: error: debian/python-mako-doc/usr/share/doc/python-mako-doc/html/sear

Processed: closing 1063190

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1063190 Bug #1063190 [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1063190: https://bugs.debian.org/cgi-bin/

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

2024-06-10 Thread Chris Hofstaedtler
* Sam Hartman [240610 23:13]: > control: tags -1 +help > > > Chris> Filing with severity: serious as the buildd network has > Chris> started switching to sbuild with unshare backend, and > Chris> multiple people have reproduced this problem. > > I'm not running sbuild these days; I'

Bug#1071007:

2024-06-10 Thread Paul Pfeister
When building the rpm, I named the (rpm) package sherlock-project to have parity with PyPI, due to the same conflicting package. The importable module is still simply sherlock, however, which is _less than ideal_, and should probably be addressed. With this discussion now being had on the deb side

Bug#1072159: marked as done (rust-pango-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/Pango-1.0.gir': No such file or directory)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 21:21:11 + with message-id and subject line Bug#1072159: fixed in rust-pango-sys 0.19.5-3 has caused the Debian Bug report #1072159, regarding rust-pango-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/Pango-1.0.gir': No such file

Processed: your mail

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1071892 by 1060848 Bug #1071892 [src:rust-transmission-client] rust-transmission-client: FTBFS: unsatisfiable build-dependencies 1071892 was not blocked by any bugs. 1071892 was not blocking any bugs. Added blocking bug(s) of 1071892: 10608

Processed: Re: Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +help Bug #1072952 [src:krb5] krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity Added tag(s) help. -- 1072952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072952 Debian Bug Tracking System Cont

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

2024-06-10 Thread Sam Hartman
control: tags -1 +help Chris> Filing with severity: serious as the buildd network has Chris> started switching to sbuild with unshare backend, and Chris> multiple people have reproduced this problem. I'm not running sbuild these days; I'm mostly moving toward containerized builds fo

Processed: remove webext-noscript

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 922396 -1 Bug #922396 [webext-noscript] webext-noscript: version out of date -- does not work with current Firefox Bug 922396 cloned as bug 1072956 > reassign -1 ftp.debian.org Bug #1072956 [webext-noscript] webext-noscript: version out of

Processed: remove tinyjsd

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 971774 -1 Bug #971774 [tinyjsd] Doesn't support Thunderbird 68 / 78 Bug 971774 cloned as bug 1072955 > reassign -1 ftp.debian.org Bug #1072955 [tinyjsd] Doesn't support Thunderbird 68 / 78 Bug reassigned from package 'tinyjsd' to 'ftp.debian

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

2024-06-10 Thread Chris Hofstaedtler
Source: krb5 Version: 1.20.1-6 Severity: serious Tags: ftbfs X-Debbugs-CC: jspri...@debian.org Filing with severity: serious as the buildd network has started switching to sbuild with unshare backend, and multiple people have reproduced this problem. When building krb5 with sbuild, configured to

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

2024-06-10 Thread Samuel Henrique
Hello Thomas, On Mon, 10 Jun 2024 at 12:03, Thomas Goirand wrote: > > On 6/9/24 18:47, Samuel Henrique wrote: > > Zigo, > >> I just saw that sherlock (the social networks package) moved its python > >> files to /usr/share, instead of /usr/lib/python3/dist-packages > >> . This was > >> the sensibl

Processed: tagging 1056834

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1056834 + upstream fixed-upstream Bug #1056834 {Done: Nicholas D Steeves } [src:pyfuse3] pyfuse3: ftbfs with cython 3.0.x Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1072857: Proposed fix for #1072857

2024-06-10 Thread Aurélien COUDERC
Hi, being hit by this too, I’ve sumbitted an MR at [1]. You’ll also find in attachment the same fix on top of the version of dput currently in the archive which is slightly different from the one in the salsa repo. You can put it in /usr/share/dput/dput/dput.py as a short-term workaround. [1]

Bug#1056834: marked as done (pyfuse3: ftbfs with cython 3.0.x)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 15:50:36 -0400 with message-id <877cewtw4z@digitalmercury.freeddns.org> and subject line Re: Bug#1056834: pyfuse3: ftbfs with cython 3.0.x has caused the Debian Bug report #1056834, regarding pyfuse3: ftbfs with cython 3.0.x to be marked as done. This means

Bug#1061743: marked as done (gramps ftbfs with Python 3.12 as default)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:35:34 + with message-id and subject line Bug#1061743: fixed in gramps 5.2.2+dfsg-0.1 has caused the Debian Bug report #1061743, regarding gramps ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem has been d

Bug#969885: marked as done (megadown: [python] is required and it's not installed)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:20:10 + with message-id and subject line Bug#1072945: Removed package(s) from unstable has caused the Debian Bug report #969885, regarding megadown: [python] is required and it's not installed to be marked as done. This means that you claim that the prob

Bug#1007941: marked as done (megadown: Should we remove this package?)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:20:10 + with message-id and subject line Bug#1072945: Removed package(s) from unstable has caused the Debian Bug report #1007941, regarding megadown: Should we remove this package? to be marked as done. This means that you claim that the problem has been

Bug#991003: marked as done (kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:19:20 + with message-id and subject line Bug#1072932: Removed package(s) from unstable has caused the Debian Bug report #991003, regarding kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel to

Bug#983648: marked as done (kpatch-dkms: fails to build module for Linux 5.10: uses unknown struct stack_trace)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:19:20 + with message-id and subject line Bug#1072932: Removed package(s) from unstable has caused the Debian Bug report #983648, regarding kpatch-dkms: fails to build module for Linux 5.10: uses unknown struct stack_trace to be marked as done. This mean

Bug#1061743: Gramps in Debian

2024-06-10 Thread Dr. Tobias Quathamer
Am 03.06.24 um 06:55 schrieb Ross Gammon: I will try and take a look this week. But if I fail, either of you are welcome to lose patience, merge it to master, and upload it for me. :-) Hi Ross, I've decided to lose patience. :-) No, seriously, I've built Gramps locally and did some test runs

Bug#1029189: marked as done (kpatch: FTBFS with shellcheck 0.9.0)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:19:20 + with message-id and subject line Bug#1072932: Removed package(s) from unstable has caused the Debian Bug report #1029189, regarding kpatch: FTBFS with shellcheck 0.9.0 to be marked as done. This means that you claim that the problem has been deal

Bug#1027889: marked as done (kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms))

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 19:19:20 + with message-id and subject line Bug#1072932: Removed package(s) from unstable has caused the Debian Bug report #1027889, regarding kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms) to be marked as done. This means that you claim

Bug#1072947: dropbear: autopkgtest remote-unlocking is flaky

2024-06-10 Thread Luca Boccassi
Source: dropbear 2024.85-2 Severity: serious Justification: flaky debci is RC as per RT User: debian...@lists.debian.org Usertags: flaky Dear Maintainer(s), The remote-unlocking autopkgtest is flaky, and often requires a retry to pass, with no other changes. As per RT, this is RC. Example: https

Processed: Re: Bug#1039883: The issue impacts SSD disks as well (updating found version)

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1039883 6.5.8-1 Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Marked as found in versions linux/6.5.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039883: https://bugs.debian.org/cgi-b

Processed: found 1039883 in 5.10.103-1, found 1039883 in 5.16.3-1~exp1, found 1039883 in 5.17~rc3-1~exp1

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # According to bisection in 5.10.94 5.15.17 5.16.3 and 5.17-rc1 > found 1039883 5.10.103-1 Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Marked as found in versions linux/5.10.103-1. > found 1039883 5.16.3-1~exp1 Bug #1039883 [src:

Bug#1070327: marked as done (libauparse0t64 fails piuparts: missing postrm for /usr-move mitigation)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 18:04:23 + with message-id and subject line Bug#1070327: fixed in audit 1:3.1.2-3 has caused the Debian Bug report #1070327, regarding libauparse0t64 fails piuparts: missing postrm for /usr-move mitigation to be marked as done. This means that you claim tha

Processed: severity of 1067699 is serious

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1067699 serious Bug #1067699 [libllvm18] libllvm18:i386 contains files, also in libllvm18:amd64 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067699: https://

Processed: unblock bug now that more specific bug was filed

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 1071982 by 1052028 Bug #1071982 [src:jupyterhub] FTBFS: help2man fails 1071982 was blocked by: 1052028 1071982 was not blocking any bugs. Removed blocking bug(s) of 1071982: 1052028 > End of message, stopping processing here. Please conta

Bug#1072941: marked as done (libgl1-mesa-dri: not multi-arch coinstallable)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 17:22:28 + with message-id and subject line Bug#1072941: fixed in mesa 24.1.1-2 has caused the Debian Bug report #1072941, regarding libgl1-mesa-dri: not multi-arch coinstallable to be marked as done. This means that you claim that the problem has been deal

Processed: Fixed

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1052200 4.3.4+dfsg1-1+deb12u1 Bug #1052200 {Done: Soren Stoutner } [electrum] electrum: Lightning security bug in bookworm 4.3.4+dfsg1-1 Marked as fixed in versions electrum/4.3.4+dfsg1-1+deb12u1. > -- Stopping processing here. Please cont

Processed: libgl1-mesa-dri: not multi-arch coinstallable

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1067699 Bug #1072941 [libgl1-mesa-dri] libgl1-mesa-dri: not multi-arch coinstallable 1072941 was not blocked by any bugs. 1072941 was not blocking any bugs. Added blocking bug(s) of 1072941: 1067699 -- 1072941: https://bugs.debian.org/cgi-bin/bugreport.

Bug#1072941: libgl1-mesa-dri: not multi-arch coinstallable

2024-06-10 Thread Sven Joachim
Package: libgl1-mesa-dri Version: 24.1.1-1 Severity: serious Control: block -1 by 1067699 I just had to downgrade a bunch of packages from src:mesa to version 24.1.0-2, because the installation of libllvm18:i386 failed due to a file conflict that has been present for a few months, see #1067699. P

Processed (with 5 errors): Re: Bug#1039883: The issue impacts SSD disks as well (updating found version)

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1039883 6.1.90-1 Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Marked as found in versions linux/6.1.90-1. > On Thursday, 30 May 2024 14:39:16 CEST Emanuele Rocca wrote: Unknown command or malformed arguments to command. > >

Bug#1039883: linux: ext4 corruption with symlinks

2024-06-10 Thread Ben Hutchings
On Sun, 5 Nov 2023 16:12:41 + Hervé Werner wrote: > Hello > > I'm sorry for the delay. > > > Are you able to reliably preoeduce the issue and can bisect it to > > the introducing commit? > I faced this issue on real data but I struggled to find a reliable > scenario to reproduce it. Here is

Processed: unblock bug now that more specific bug was filed

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 1052028 by 1071982 Bug #1052028 [src:pydantic] please update to pydantic 2.x 1052028 was not blocked by any bugs. 1052028 was blocking: 1061609 1071982 1072938 Removed blocking bug(s) of 1052028: 1071982 > End of message, stopping processi

Processed (with 1 error): jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2)

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1052028 Bug #1072938 [src:jupyterhub] jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2) 1072938 was not blocked by any bugs. 1072938 was not blocking any bugs. Added blocking bug(s) of 1072938: 1052028 > unblock 107192 by 1052028 Failed to

Bug#1072938: jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2)

2024-06-10 Thread Jeremy Bícha
Source: jupyterhub Version: 5.0.0+ds1-1 Severity: serious Tags: ftbfs Control: block -1 by 1052028 Control: unblock 107192 by 1052028 X-Debbugs-CC: lola...@debian.org jupyterhub is unable to build from source because it has Build-Depends: python3-pydantic >=2 but the latest version of python3-pyda

Bug#1072934: shadowsocks-libev: Consider removing the package

2024-06-10 Thread Boyuan Yang
Source: shadowsocks-libev Version: 3.3.5+ds-10 Severity: serious X-Debbugs-CC: r...@debian.org rogershim...@gmail.com Tags: sid Hi, Following the previous communication in March, I am considering to take action and remove related packages in the ss-libev ecosystem. Package shadowsocks-libev will

Bug#1072935: simple-obfs: Consider removing the package

2024-06-10 Thread Boyuan Yang
Source: simple-obfs Version: 0.0.5-6 Severity: serious X-Debbugs-CC: r...@debian.org rogershim...@gmail.com Tags: sid Hi, Following the previous communication in March, I am considering to take action and remove related packages in the ss-libev ecosystem. The first targeted package would be simp

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-06-10 Thread Chris Hofstaedtler
On Mon, Jun 10, 2024 at 11:59:34AM +0200, Chris Hofstaedtler wrote: > Hi, > > On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote: > > > "Simon" == Simon McVittie writes: [..] > > Simon> However, even with both of those, if the krb5 test suite (or > > Simon> protocol) is resol

Bug#1072597: marked as done (node-chownr: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 13:49:18 + with message-id and subject line Bug#1072597: fixed in node-chownr 2.0.0-3 has caused the Debian Bug report #1072597, regarding node-chownr: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with

Bug#1072604: marked as done (node-stream-shift: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 13:49:28 + with message-id and subject line Bug#1072604: fixed in node-stream-shift 1.0.3+~1.0.2-1 has caused the Debian Bug report #1072604, regarding node-stream-shift: FTBFS: failing tests to be marked as done. This means that you claim that the problem

Bug#1068918: marked as done (node-zx: FTBFS test suite failure)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 17:32:34 +0400 with message-id and subject line Fixed elsewhere has caused the Debian Bug report #1068918, regarding node-zx: FTBFS test suite failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: notfound 1068918 in node-zx/7.1.1+~cs6.7.23-2, notfound 1068918 in node-zx/7.1.1+~cs6.7.23-3

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1068918 node-zx/7.1.1+~cs6.7.23-2 Bug #1068918 [src:node-zx] node-zx: FTBFS test suite failure No longer marked as found in versions node-zx/7.1.1+~cs6.7.23-2. > notfound 1068918 node-zx/7.1.1+~cs6.7.23-3 Bug #1068918 [src:node-zx] node-z

Bug#1072603: marked as done (node-read-package-json: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 12:19:44 + with message-id and subject line Bug#1072603: fixed in node-read-package-json 5.0.2+~2.0.0-2 has caused the Debian Bug report #1072603, regarding node-read-package-json: FTBFS: failing tests to be marked as done. This means that you claim that th

Bug#1072602: marked as done (node-parse-json: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 12:19:37 + with message-id and subject line Bug#1072602: fixed in node-parse-json 5.2.0+~cs5.1.7-2 has caused the Debian Bug report #1072602, regarding node-parse-json: FTBFS: failing tests to be marked as done. This means that you claim that the problem ha

Bug#1072598: marked as done (node-decompress-response: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 12:19:26 + with message-id and subject line Bug#1072598: fixed in node-decompress-response 6.0.0-3 has caused the Debian Bug report #1072598, regarding node-decompress-response: FTBFS: failing tests to be marked as done. This means that you claim that the p

Bug#1072600: marked as done (node-json-parse-better-errors: FTBFS: failing tests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 12:05:54 + with message-id and subject line Bug#1072600: fixed in node-json-parse-better-errors 1.0.2+~cs3.3.1-3 has caused the Debian Bug report #1072600, regarding node-json-parse-better-errors: FTBFS: failing tests to be marked as done. This means that

Processed: Bug#1072602 marked as pending in node-parse-json

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072602 [src:node-parse-json] node-parse-json: FTBFS: failing tests Added tag(s) pending. -- 1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072602: marked as pending in node-parse-json

2024-06-10 Thread Yadd
Control: tag -1 pending Hello, Bug #1072602 in node-parse-json 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/js-team/node-parse-json/-/commit/e81f2de8b3677dbe

Bug#1072306: marked as done (src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 12:06:30 + with message-id and subject line Bug#1072306: fixed in r-cran-rcppparallel 5.1.7+dfsg-5 has caused the Debian Bug report #1072306, regarding src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression to be marked as

Bug#1072603: marked as pending in node-read-package-json

2024-06-10 Thread Yadd
Control: tag -1 pending Hello, Bug #1072603 in node-read-package-json 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/js-team/node-read-package-json/-/commit/72

Processed: Bug#1072603 marked as pending in node-read-package-json

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072603 [src:node-read-package-json] node-read-package-json: FTBFS: failing tests Added tag(s) pending. -- 1072603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072598: marked as pending in node-decompress-response

2024-06-10 Thread Yadd
Control: tag -1 pending Hello, Bug #1072598 in node-decompress-response 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/js-team/node-decompress-response/-/commi

Bug#1072366: libndp: CVE-2024-5564

2024-06-10 Thread Moritz Muehlenhoff
Hi Florian, On Mon, Jun 10, 2024 at 08:41:27AM +0200, Florian Ernst wrote: > Dear Security Team, > > On Sat, Jun 01, 2024 at 04:57:53PM +0200, Salvatore Bonaccorso wrote: > > [...] > > [0] https://security-tracker.debian.org/tracker/CVE-2024-5564 > > https://www.cve.org/CVERecord?id=CVE-2024-

Processed: Bug#1072598 marked as pending in node-decompress-response

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072598 [src:node-decompress-response] node-decompress-response: FTBFS: failing tests Added tag(s) pending. -- 1072598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072598 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1072600: marked as pending in node-json-parse-better-errors

2024-06-10 Thread Yadd
Control: tag -1 pending Hello, Bug #1072600 in node-json-parse-better-errors 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/js-team/node-json-parse-better-err

Processed: Bug#1072600 marked as pending in node-json-parse-better-errors

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072600 [src:node-json-parse-better-errors] node-json-parse-better-errors: FTBFS: failing tests Added tag(s) pending. -- 1072600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072600 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1071160: Fix in stable

2024-06-10 Thread tic
Hello guys, Thanks for the quick upload to sid guys ! Do you know what is the plan for stable ? I see no activity to backport the fixes since the 2.45.1 release [0]. Thanks in advance Tic [0] : https://repo.or.cz/git/debian.git/shortlog/8d1426afa25b0a66ed65d9b56b8c11df5e35d973 publickey - tic

Bug#1063645: Aw: Re: markdown: missing required debian/rules targets build-arch and/or build-indep

2024-06-10 Thread Johannes Schauer Marin Rodrigues
Quoting Bastian Germann (2024-06-10 09:30:20) > "Johannes Schauer Marin Rodrigues": > > Do you have recommendations? I just need a drop-in replacement for markdown > > into stdin, html on stdout. Nothing fancy. > I would suggest discount or python3-markdown. Brilliant! That tip was gold! All I did

Bug#1071007: Bug#1072733: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

2024-06-10 Thread Thomas Goirand
On 6/9/24 18:47, Samuel Henrique wrote: Zigo, I just saw that sherlock (the social networks package) moved its python files to /usr/share, instead of /usr/lib/python3/dist-packages . This was the sensible thing to do, as it doesn't really need to expose itself as Python module. Not really, tha

Bug#1072835: marked as done (jpeg-xl: Failing autopkgtests)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 10:49:14 + with message-id and subject line Bug#1072835: fixed in jpeg-xl 0.9.2-6 has caused the Debian Bug report #1072835, regarding jpeg-xl: Failing autopkgtests to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-06-10 Thread Chris Hofstaedtler
Hi, On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote: > > "Simon" == Simon McVittie writes: [..] > Simon> I am unsure whether there is consensus that "the result of > Simon> gethostname() resolves to some address of the local machine" > Simon> is also a reasonable thing

Processed: mythtv-status: diff for NMU version 1.1.0-1.1

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tags 1052282 + patch Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile Added tag(s) patch. > tags 1052282 + pending Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile Added tag(s) pending. -- 1052282: https://bugs.debi

Bug#1052282: mythtv-status: diff for NMU version 1.1.0-1.1

2024-06-10 Thread Chris Hofstaedtler
Control: tags 1052282 + patch Control: tags 1052282 + pending Dear maintainer, I've prepared an NMU for mythtv-status (versioned as 1.1.0-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. The patch also moves the systemd units into /usr. Regards. diff

Bug#1072760: ikiwiki: FTBFS: Parse errors: No plan found in TAP output

2024-06-10 Thread Jonathan Dowland
On Fri, Jun 07, 2024 at 05:22:32PM +0200, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: … > t/po.t (Wstat: 65280 (exited 255) Tests: 38 Failed: 0) > Non-zero exit status: 255 > Parse errors: No plan found in TAP output

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

2024-06-10 Thread Jonas Smedegaard
Quoting Jeremy Bícha (2024-04-21 19:47:08) > Simple patch attached. I am not convinced that this issue should be ignored: Might be revealing the upstream bugs recently tracked upstream, which might in Debian be affected by relaxed dependencies e.g. on concurrent-queue. - Jonas -- * Jonas Smed

Bug#1072913: libnss-pgsql: remove from Debian?

2024-06-10 Thread Chris Hofstaedtler
Source: libnss-pgsql Version: 1.4.0debian-8 Severity: serious libnss-pgsql's last upload was in 2014. This was a maintainer upload. The last upstream release apparently happened in 2007. This is about 17 years ago at the time of writing. libnss-pgsql currently has an open FTBFS bug, pointing to o

Processed: irker: diff for NMU version 2.23+dfsg-1.1

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tags 1060467 + patch Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Added tag(s) patch. > tags 1060467 + pending Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Added tag(s) pending. -- 1060467: https://bugs.de

Processed (with 1 error): file loss caused by systemd-dev missing

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1060467 1072082 Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev Unable to merge bugs because: package of #1072082 is 'irker' not 'src:irker' Failed to forcibly merge 1060467: Did not alter merged bugs. > than

Bug#1060467: irker: diff for NMU version 2.23+dfsg-1.1

2024-06-10 Thread Chris Hofstaedtler
Control: tags 1060467 + patch Control: tags 1060467 + pending Dear maintainer, I've prepared an NMU for irker (versioned as 2.23+dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru irker-2.23+dfsg/debian/changelog irker-2.23+dfsg/

Bug#1069575: FTBFS in experimental

2024-06-10 Thread Jonas Smedegaard
Quoting Matthias Geiger (2024-05-26 11:20:09) > On Sat, 25 May 2024 20:27:28 +0200 Jonas Smedegaard wrote: > > Control: block -1 by 1071900 > > > > Quoting Jonas Smedegaard (2024-05-25 20:13:12) > > > Ahh, you are talking about *async-channel* v2.3.0. Please consider in > > > future to mentio

Bug#1072912: supermin: /lib64: No such file or directory

2024-06-10 Thread Chris Hofstaedtler
Source: libguestfs Version: 1:1.52.0-6.1 Severity: serious User: helm...@debian.org Usertags: dep17 X-Debbugs-CC: helm...@debian.org The debootstrap set was uploaded, including a new glibc and base-files. The owner and exact management of /lib64 has changed. libguestfs tests now fail, possibly in

Bug#1072798: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 08:49:49 + with message-id and subject line Bug#1072798: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1 has caused the Debian Bug report #1072798, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092 to be marked as done. This

Bug#1064720: marked as done (ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 08:36:03 + with message-id and subject line Bug#1064720: fixed in ruby-capybara 3.40.0+ds-1 has caused the Debian Bug report #1064720, regarding ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: to be marked as done. This means that you cla

Bug#1071309: closing 1071309

2024-06-10 Thread Martin
close 1071309 1.8.4-4 thanks

Processed: closing 1071309

2024-06-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1071309 1.8.4-4 Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails Marked as fixed in versions gajim/1.8.4-4. Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails Marked Bug as done > thanks Stopping process

Bug#1071400: marked as done (src:specutils: unsatisfied build dependency in testing: python3-spectral-cube)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 09:48:15 +0200 with message-id and subject line Closing outdated bug has caused the Debian Bug report #1071400, regarding src:specutils: unsatisfied build dependency in testing: python3-spectral-cube to be marked as done. This means that you claim that the pro

Processed: Bug#1064720 marked as pending in ruby-capybara

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Ignoring request to alter tags of bug #1064720 to the same tags previously set -- 1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720

Bug#1064720: marked as pending in ruby-capybara

2024-06-10 Thread Utkarsh Gupta
Control: tag -1 pending Hello, Bug #1064720 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/dd48272e5a4623078b

Processed: Bug#1064720 marked as pending in ruby-capybara

2024-06-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Ignoring request to alter tags of bug #1064720 to the same tags previously set -- 1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720

Bug#1064720: marked as pending in ruby-capybara

2024-06-10 Thread Utkarsh Gupta
Control: tag -1 pending Hello, Bug #1064720 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/2d5be37dfa3e7a2433

Bug#1063645: Aw: Re: markdown: missing required debian/rules targets build-arch and/or build-indep

2024-06-10 Thread Bastian Germann
"Johannes Schauer Marin Rodrigues": > Do you have recommendations? I just need a drop-in replacement for markdown > into stdin, html on stdout. Nothing fancy. I would suggest discount or python3-markdown.

  1   2   >