Processed: severity of 1064310 is grave

2024-02-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1064310 grave Bug #1064310 [src:dav1d] dav1d: CVE-2024-1580 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1064310:

Processed: tagging 1064275, tagging 1064308, tagging 1064295, tagging 1058102

2024-02-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1064275 + sid trixie Bug #1064275 [src:asdf-standard] autopkgtest failure with python-jsonschema 4.19.2 Added tag(s) trixie and sid. > tags 1064308 + sid trixie Bug #1064308 [src:libricohcamerasdk] libricohcamerasdk: identified for time_t

Bug#1056354: marked as done (python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Feb 2024 13:29:43 +0900 with message-id <20240220132943.221a@jet> and subject line has caused the Debian Bug report #1056354, regarding python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0 to be marked as done. This means that you claim that the problem has been

Processed: Re: python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.4.0-1 Bug #1056354 [python3-hinawa-utils] python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0 Marked as fixed in versions hinawa-utils/0.4.0-1. -- 1056354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056354 Debian Bug Tracking System Contact

Bug#1056354: python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0

2024-02-19 Thread Kentaro HAYASHI
Control: fixed -1 0.4.0-1 This bug was fixed in hinawa-utils 0.4.0-1. On Tue, 21 Nov 2023 17:09:35 +0200 Adrian Bunk wrote: > Package: python3-hinawa-utils > Version: 0.3.0-3 > Severity: serious > > src:libhinawa now builds gir1.2-hinawa-4.0 instead of > gir1.2-hinawa-3.0 > >

Bug#1063302: libsingular4-dev: libsingular renders sagemath unusable

2024-02-19 Thread Alexandre Lymberopoulos
Thanks, Doug! Hope this is fixed soon. My first guess is to call the installed version of singular and then see what happens. Sage team: if I can help in some way, just tell me. Best, Alexandre Em 19/02/2024 08:50, Torrance, Douglas escreveu: Control: reassign -1 sagemath 9.5-6 Control:

Bug#1052051: sagemath: Confirm this on my installation

2024-02-19 Thread Alexandre Lymberopoulos
Package: sagemath Version: 9.5-6 Followup-For: Bug #1052051 Dear Maintainer, sagemath can't be run here. After many messages, the last one is: ImportError: libsingular-Singular-4.3.1.so: cannot open shared object file: No such file or directory Maybe it can be fixed by invoking the currently

Bug#1064243: marked as done (rust-ahash: Fails to build, requires rustc 1.72)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Feb 2024 01:02:03 + with message-id and subject line Bug#1064243: fixed in rust-ahash 0.8.8-2 has caused the Debian Bug report #1064243, regarding rust-ahash: Fails to build, requires rustc 1.72 to be marked as done. This means that you claim that the problem has

Bug#1064302: marked as done (enforcing time64 on 32-bit architectures is wrong for i386)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Feb 2024 01:23:07 +0100 with message-id and subject line Re: Bug#1064302: enforcing time64 on 32-bit architectures is wrong for i386 has caused the Debian Bug report #1064302, regarding enforcing time64 on 32-bit architectures is wrong for i386 to be marked as done.

Bug#1064328: snort: identified for time_t transition but no ABI in shlibs

2024-02-19 Thread Steve Langasek
Source: snort Version: 2.9.15.1-6 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Dear maintainers, Analysis of the archive for the 64-bit time_t transition[0][1] identifies snort as an affected package, on the basis that the headers could not be compiled and analyzed out of

Bug#1063462: marked as done (pycurl: FTBFS during tests: GnuTLS recv error (-110): The TLS connection was non-properly terminated)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 23:04:34 + with message-id and subject line Bug#1063462: fixed in curl 8.6.0-3 has caused the Debian Bug report #1063462, regarding pycurl: FTBFS during tests: GnuTLS recv error (-110): The TLS connection was non-properly terminated to be marked as done.

Bug#1064324: libnvme ftbfs on most release architectures

2024-02-19 Thread Matthias Klose
Package: src:libnvme Version: 1.8-1 Severity: serious Tags: sid trixie ftbfs libnvme ftbfs on most release architectures, timeouts in the tests: [...] === 24/24 test: sysfs start time: 11:13:43 duration: 30.05s

Bug#1064302: enforcing time64 on 32-bit architectures is wrong for i386

2024-02-19 Thread Matthias Klumpp
Am Mo., 19. Feb. 2024 um 21:45 Uhr schrieb Matthias Klose : > > Package: src:ldc > Version: 1:1.36.0-1 > Severity: serious > Tags: sid trixie > > Just reading the changelog: > > * LDC should already work fine with 64-bit time on 32-bit > architectures, just to be on the safe side though,

Bug#1063274: pydevd: autopkgtest-failing warning with pandas 2.1

2024-02-19 Thread Rebecca N. Palmer
Thank you for caring about not breaking other packages, and yes, that's a good reason to not upload that new upstream for now. Does just the patch (not the new upstream) also break debugpy? (It shouldn't be able to, since it only touches test code.)

Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard

2024-02-19 Thread Xavier G.
Dear Maintainer, I confirm this issue. I experienced it with an AMD R7 240 graphics card[1] on a regular Debian Sid host running kernel 6.6.15. Booting with the previous kernel (6.6.13) did not change the situation but I confirm "Accel" "no", as suggested by Grégory, is a suitable workaround.

Bug#1057548: cloud-init: FTBFS: failing tests

2024-02-19 Thread Ross Vandegrift
On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: I started updating to the latest upstream release, which fixes this FTBFS. But I'm reluctant to push to the team repo, due to an issue with the network

Bug#1064308: libricohcamerasdk: identified for time_t transition but no ABI in shlibs

2024-02-19 Thread Steve Langasek
Source: libricohcamerasdk Version: 1.1.0-4 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Hi Thorsten, Analysis of the archive for the 64-bit time_t transition[0][1] identifies libricohcamerasdk as an affected package, on the basis that the ABI of the library references the

Processed: src:python-pamqp: fails to migrate to testing for too long: autopkgtest failures on 32 bit

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.3.0-1 Bug #1064309 [src:python-pamqp] src:python-pamqp: fails to migrate to testing for too long: autopkgtest failures on 32 bit Marked as fixed in versions python-pamqp/3.3.0-1. Bug #1064309 [src:python-pamqp] src:python-pamqp: fails to migrate to

Bug#1064309: src:python-pamqp: fails to migrate to testing for too long: autopkgtest failures on 32 bit

2024-02-19 Thread Paul Gevers
Source: python-pamqp Version: 3.2.1-1 Severity: serious Control: close -1 3.3.0-1 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

Bug#1064306: nodejs: FTBFS on mips64el: failed tests

2024-02-19 Thread Sebastian Ramacher
Source: nodejs Version: 18.19.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=18.19.1%2Bdfsg-1=1708294535=0 not ok 270

Processed: Re: libdemeter-perl: ships perl modules already packaged separately as libxray-scattering-perl, libxray-absorption-perl

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.9.27+ds6-2 Bug #1064067 {Done: Roland Mas } [libdemeter-perl] libdemeter-perl: ships perl modules already packaged separately as libxray-scattering-perl, libxray-absorption-perl Marked as found in versions libdemeter-perl/0.9.27+ds6-2; no longer marked

Bug#1064067: libdemeter-perl: ships perl modules already packaged separately as libxray-scattering-perl, libxray-absorption-perl

2024-02-19 Thread Andreas Beckmann
Followup-For: Bug #1064067 Control: found -1 0.9.27+ds6-2 Control: retitle -1 libdemeter-perl: ships perl modules already packaged separately as libxray-scattering-perl, libxray-absorption-perl, libifeffit-perl, libchemistry-formula-perl Hi, there is another file conflict with

Bug#1064302: enforcing time64 on 32-bit architectures is wrong for i386

2024-02-19 Thread Matthias Klose
Package: src:ldc Version: 1:1.36.0-1 Severity: serious Tags: sid trixie Just reading the changelog: * LDC should already work fine with 64-bit time on 32-bit architectures, just to be on the safe side though, enforce time64,lfs on 32-bit architectures for C code as well (Closes:

Bug#1064295: puppet-agent: ununsatisfiable dependencies: depends on ruby-concurrent (< 1.2.0)

2024-02-19 Thread Jérôme Charaoui
Hello, On Mon, 19 Feb 2024 20:38:19 +0100 Aurelien Jarno wrote: puppet-agent in unstable is not installable anymore as it depends on ruby-concurrent (< 1.2.0), while the version in unstable is now 1.2.3-2. Yes, I'm aware. puppet-agent 8.4.0, which works with ruby-concurrent >= 1.2.0, is

Bug#1064298: libhamlib4t64: ineffective replaces due to /usr-move

2024-02-19 Thread Helmut Grohne
Package: libhamlib4t64 Version: 4.5.5-3.1~exp1 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17p1 Control: affects -1 + libhamlib4 X-Debbugs-Cc: vor...@debian.org, mwhud...@debian.org libhamlib4t64 introduced Replaces for libhamlib4 to take over its files and in that process

Processed: libhamlib4t64: ineffective replaces due to /usr-move

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libhamlib4 Bug #1064298 [libhamlib4t64] libhamlib4t64: ineffective replaces due to /usr-move Added indication that 1064298 affects libhamlib4 -- 1064298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064298 Debian Bug Tracking System Contact

Bug#1064266: marked as done (python-lsp-black: FTBFS with black 24.2.0-1)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 19:51:43 + with message-id and subject line Bug#1064266: fixed in python-lsp-black 2.0.0-2 has caused the Debian Bug report #1064266, regarding python-lsp-black: FTBFS with black 24.2.0-1 to be marked as done. This means that you claim that the problem has

Bug#1064295: puppet-agent: ununsatisfiable dependencies: depends on ruby-concurrent (< 1.2.0)

2024-02-19 Thread Aurelien Jarno
Package: puppet-agent Version: 7.23.0-1 Severity: serious X-Debbugs-Cc: d...@debian.org Dear maintainer, puppet-agent in unstable is not installable anymore as it depends on ruby-concurrent (< 1.2.0), while the version in unstable is now 1.2.3-2. Regards Aurelien

Bug#1064294: bind-dyndb-ldap: FTBFS: error: Install BIND9 development files

2024-02-19 Thread Aurelien Jarno
Source: bind-dyndb-ldap Version: 11.10-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, bind-dyndb-ldap fails to build from source, from my build log on amd64: | checking for -fvisibility=hidden compiler flag... yes

Processed: Bug#1064266 marked as pending in python-lsp-black

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1064266 [src:python-lsp-black] python-lsp-black: FTBFS with black 24.2.0-1 Added tag(s) pending. -- 1064266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1064266: marked as pending in python-lsp-black

2024-02-19 Thread Johannes Schauer Marin Rodrigues
Control: tag -1 pending Hello, Bug #1064266 in python-lsp-black 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#1063746: Upload request for golang-github-katalix-go-l2tp 0.1.7-1

2024-02-19 Thread Tom Parkin
Hi folks, Would someone mind please reviewing and uploading golang-github-katalix-go-l2tp 0.1.7-1? https://salsa.debian.org/go-team/packages/golang-github-katalix-go-l2tp The package is updated to remove the L2TPIP6 transport test, which is failing due to the backport of an upstream kernel

Bug#1060898: apfs-dkms: fails to build module: super.c:17:10: fatal error: version.h: No such file or directory

2024-02-19 Thread Gürkan Myczko
Hi Andreas, attached you can find an overhaul of the package installation that also fixes the missing version.h Having the Debian revision included in the dkms module version is very unusual, now this only uses the upstream version. Looks good except it didn't install/build for me, maybe I

Bug#1063746: (no subject)

2024-02-19 Thread Tom Parkin
I believe the root cause of this issue is this backported kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/l2tp/l2tp_ip6.c?h=linux-6.1.y=f6a7182179c0ed788e3755ee2ed18c888ddcc33f The commit is present from Linux v6.6 onwards and has been backported to at

Bug#1061307: marked as done (rpds-py FTBFS with pyo3 0.20)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 16:21:30 + with message-id and subject line Bug#1061307: fixed in rpds-py 0.12.0-3 has caused the Debian Bug report #1061307, regarding rpds-py FTBFS with pyo3 0.20 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1061917: marked as done (virtualbox-dkms: Does not build)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 16:06:35 + with message-id and subject line Bug#1061917: fixed in virtualbox 7.0.14-dfsg-2 has caused the Debian Bug report #1061917, regarding virtualbox-dkms: Does not build to be marked as done. This means that you claim that the problem has been dealt

Bug#1063717: NVIDIA packages in stable-updates fix module compilation for linux 6.1.76-1

2024-02-19 Thread matte . mb2006 . 9990
On Mon, 19 Feb 2024 00:18:29 +0100 Andreas Beckmann wrote: > On 18/02/2024 17.06, matte.mb2006.9...@gmail.com wrote: > >> https://lists.debian.org/debian-stable-announce/2024/02/msg2.html > > > The update is not yet available on my PC. I live in Italy. > > Do you have bookworm-updates (or

Bug#1064023: marked as done (cddlib: FTBFS on armhf: ! Text line contains an invalid character.)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 13:29:14 + with message-id <87y1bgbn15@piedmont.edu> and subject line Re: Bug#1064023: cddlib: FTBFS on armhf: ! Text line contains an invalid character. has caused the Debian Bug report #1064023, regarding cddlib: FTBFS on armhf: ! Text line contains

Bug#1064023: cddlib: FTBFS on armhf: ! Text line contains an invalid character.

2024-02-19 Thread Torrance, Douglas
On Thu 15 Feb 2024 03:51:43 PM -05, Sebastian Ramacher wrote: Source: cddlib Version: 094m-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org

Bug#1064275: autopkgtest failure with python-jsonschema 4.19.2

2024-02-19 Thread Thomas Goirand
Source: asdf-standard Version: 1.0.3-1 Severity: serious Hi, as per this: https://qa.debian.org/excuses.php?experimental=1=python-jsonschema your package has autopkgtest regressions. Since python-jsonschema was staged in Experimental for so long, I'm uploading it to unstable, making this bug

Processed: bug 1064266 is forwarded to https://github.com/python-lsp/python-lsp-black/issues/55

2024-02-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1064266 https://github.com/python-lsp/python-lsp-black/issues/55 Bug #1064266 [src:python-lsp-black] python-lsp-black: FTBFS with black 24.2.0-1 Set Bug forwarded-to-address to

Processed: reopening 1037914

2024-02-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1037914 Bug #1037914 {Done: Matthew Grant } [cloud-initramfs-growroot] cloud-initramfs-growroot: missing dependencies in initramfs 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Processed: Re: Bug#1063302: libsingular4-dev: libsingular renders sagemath unusable

2024-02-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 sagemath 9.5-6 Bug #1063302 [libsingular4-dev] libsingular4-dev: libsingular renders sagemath unusable Bug reassigned from package 'libsingular4-dev' to 'sagemath'. No longer marked as found in versions singular/1:4.3.2-p10+ds-1. Ignoring request to

Bug#1063302: libsingular4-dev: libsingular renders sagemath unusable

2024-02-19 Thread Torrance, Douglas
Control: reassign -1 sagemath 9.5-6 Control: severity 1052051 grave Control: merge -1 1052051 On Tue 06 Feb 2024 12:18:06 AM -03, Alexandre Lymberopoulos wrote: Package: libsingular4-dev Version: 1:4.3.2-p10+ds-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, It

Bug#1053405: darktable: FTBFS on arm64 (gcc bug?)

2024-02-19 Thread Tino Mettler
Version: 4.4.2-1.1 Hi, OPENMP support was disabled for arm64 in the 4.4.2-1.1 package, so this bug can be closed. I also stumbled again over this FTBFS bug after accidently enabling OPENMP yesterday for the darktable 4.6.1-1 package, so it looks like this workaround is still needed. Regards,

Bug#1064224: marked as done (python-hmmlearn: fails variational gaussian tests with sklearn 1.4)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 10:04:26 + with message-id and subject line Bug#1064224: fixed in python-hmmlearn 0.3.0-4 has caused the Debian Bug report #1064224, regarding python-hmmlearn: fails variational gaussian tests with sklearn 1.4 to be marked as done. This means that you

Bug#1064266: python-lsp-black: FTBFS with black 24.2.0-1

2024-02-19 Thread Johannes Schauer Marin Rodrigues
Source: python-lsp-black Version: 2.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sylves...@debian.org Hi, python-lsp-black currently FTBFS in unstable. To track down the reason, I ran debbisect: DEBIAN_BISECT_SRCPKG=python-lsp-black debbisect

Bug#1044060: marked as done (q2-quality-control: test failure with pandas 2.0)

2024-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2024 09:35:35 + with message-id and subject line Bug#1044060: fixed in q2-quality-control 2024.2.0-2 has caused the Debian Bug report #1044060, regarding q2-quality-control: test failure with pandas 2.0 to be marked as done. This means that you claim that the

Bug#1063274: pydevd: autopkgtest-failing warning with pandas 2.1

2024-02-19 Thread Julian Gilbey
On Mon, Feb 19, 2024 at 08:03:34AM +, Rebecca N. Palmer wrote: > This has been merged but not uploaded - is there a reason it shouldn't be, > or have you just not had time? Hi Rebecca, Yes; I've upgraded to the latest version in my local repo, which includes this patch upstream, but it's now

Bug#1044060: q2-quality-control: test failure with pandas 2.0

2024-02-19 Thread s3v
Hi, According to [1]:     Empty DataFrames/Series will now default to have a ``RangeIndex``     ^     Before, constructing an empty (where ``data`` is ``None`` or an empty list-like argument) :class:`Series` or :class:`DataFrame`

Bug#1063274: pydevd: autopkgtest-failing warning with pandas 2.1

2024-02-19 Thread Rebecca N. Palmer
This has been merged but not uploaded - is there a reason it shouldn't be, or have you just not had time?