Processed: severity of 1064992 is serious

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1064992 serious Bug #1064992 [sigil] sigil <= 2.1.0 plugin support broken by Python 3.12 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1064992: https://bugs.debia

Processed: notfound 1067289 in node-xterm/5.3.0-2

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1067289 node-xterm/5.3.0-2 Bug #1067289 [src:node-xterm] node-xterm: FTBFS: dh_auto_test: error: /bin/sh -ex debian/nodejs/test returned exit code 134 No longer marked as found in versions node-xterm/5.3.0-2. > thanks Stopping processing

Processed: Bug#1061012 marked as pending in node-eslint-plugin-node

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061012 [src:node-eslint-plugin-node] node-eslint-plugin-node: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_test] Error 202 Added tag(s) pending. -- 1061012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061012 Debian Bug Trackin

Bug#1061012: marked as pending in node-eslint-plugin-node

2024-06-11 Thread Yadd
Control: tag -1 pending Hello, Bug #1061012 in node-eslint-plugin-node 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-eslint-plugin-node/-/commit/

Processed: severity of 1071179 is serious

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1071179 serious Bug #1071179 [src:nose-el] RM: elpa-nose : obsolete Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071179: https://bugs.debian.org/cgi-bin/bugrepo

Processed (with 1 error): dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split'

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #1072857 [dput] dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer: Bug 1072857 cloned as bug 1073040 > retitle -2 dput: Fails when processing ssh_config_options value: > AttributeError: 'list' object has no a

Bug#1072857: dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split'

2024-06-11 Thread Ben Finney
Control: clone -1 -2 Control: retitle -2 dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split' Control: tags -2 + confirmed Control: severity -2 severe On 11-Jun-2024, Christoph Berg wrote: > Uploading to ssh-upload [DELAYED/0-day] (via scp

Bug#1073014: dhcpcd: flaky autopkgtest: Obtaining network configuration for veth1 via dhcp... timed out

2024-06-11 Thread Martin-Éric Racine
ti 11. kesäk. 2024 klo 23.21 Paul Gevers (elb...@debian.org) kirjoitti: > > Source: dhcpcd > Version: 1:10.0.8-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest of your package because it > was tested fo

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

2024-06-11 Thread Guillem Jover
Package: po4a Version: 0.70 Severity: serious Hi! When building dpkg, it now fails with something like this: ,--- Making check in man make[1]: Entering directory '/dpkg/man' /usr/bin/po4a --previous --srcdir . --destdir . --no-backups --porefs file --msgmerge-opt=--add-location=file --p

Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

2024-06-11 Thread Ben Finney
Control: tags -1 + patch On 09-Jun-2024, Martin-Éric Racine wrote: > Incorrect delayed argument: ValueError: delayed days value must be a decimal > integer: At https://salsa.debian.org/debian/dput/-/merge_requests/14> is a merge request proposing to fix this bug. Can you try the resulting Dput

Processed: Re: Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1072857 [dput] dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer: Added tag(s) patch. -- 1072857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072857 Debian Bug Tracking System Contact ow...@bugs.

Processed: severity of 1073033 is grave

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1073033 grave Bug #1073033 [neomutt] neomutt removes gpg.rc and smime.rc breaking cryptographic functions for users relying on them Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need a

Bug#1072643: Upstream po4a now hints about a possible fix to this issue

2024-06-11 Thread Martin Quinson
Hello, I just commited an improved error message in https://github.com/mquinson/po4a/commit/0717616bce2a281a3b7a2348f0d1d9abc9f1b892 I hope that it's enough to fix this issue. Bye, Mt signature.asc Description: This is a digitally signed message part

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

2024-06-11 Thread Martin Quinson
Le lundi 10 juin 2024 à 10:21 +0100, Jonathan Dowland a écrit : > 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) >

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

2024-06-11 Thread Martin Quinson
Le lundi 10 juin 2024 à 10:21 +0100, Jonathan Dowland a écrit : > 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) >

Processed: Re: Bug#1072977: apt-listbugs 0.1.42 is broken

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + unreproducible moreinfo Bug #1072977 [apt-listbugs] apt-listbugs 0.1.42 is broken Added tag(s) unreproducible and moreinfo. -- 1072977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072977 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1072977: apt-listbugs 0.1.42 is broken

2024-06-11 Thread Francesco Poli
Control: tags -1 + unreproducible moreinfo On Tue, 11 Jun 2024 10:27:33 +0200 Karine Crèvecœur wrote: > Package: apt-listbugs > Version: 0.1.42 > Severity: grave > > > Hi, Hello Karine, thanks for caring about apt-listbugs! > > Since the upgrade to version 0.1.42, apt-listbugs doesn't work

Processed: The package is only unusable in stable (bookworm)

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1039898 - sid trixie Bug #1039898 [libapache2-mod-qos] mod-qos can not be enabled correctly for apache2 in Debian 12 Removed tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039898: ht

Bug#1039898: The package is only unusable in stable (bookworm)

2024-06-11 Thread Marcelo Jorge Vieira
tags 1039898 - sid trixie thanks Hi, The package is only unusable in stable (bookworm). But, you can use bookworm-backports [0] to install the same testing/unstable version. It was fixed in testing/unstable by #172 [1]. So, I'm removing sid and trixie tags from this bug report. Cheers,

Processed (with 1 error): reassign 1072748 to src:upower, reassign 1072947 to src:dropbear ..., tagging 1072532 ...

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1072748 src:upower 1.90.3-1 Bug #1072748 [src:upower 1.90.3-1] upower: autopkgtest installed-tests is flaky Warning: Unknown package '1.90.3-1' Bug reassigned from package 'src:upower 1.90.3-1' to 'src:upower'. Ignoring request to alter f

Processed (with 1 error): 1072979 sev

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1072979 normal Bug #1072979 [ftp.debian.org] RM: beast-mmc [i386] -- RoM ; dependency not available anymore Severity set to 'normal' from 'serious' > affects 1072979 beast-mcmc Bug #1072979 [ftp.debian.org] RM: beast-mmc [i386] -- RoM ;

Processed: reassign

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1072765 sphinx-bootstrap-theme 0.8.1-4 Bug #1072765 [src:python-skbio] python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js is missing Bug reassigned from package

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

2024-06-11 Thread Sam Hartman
control: tags -1 -help +confirmed I reproduced the problem with a podman container with no network. Apparently t_iprop.py hangs if the only network interface is loopback. I'm fairly sure it would work fine only talking to itself if there was a non-127.0.0.1 address for it to use. If I can fix t

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

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 -help +confirmed Bug #1072952 [src:krb5] krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity Removed tag(s) help. Bug #1072952 [src:krb5] krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with si

Bug#1072765: python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js is missing

2024-06-11 Thread Sergio Durigan Junior
Control: reassign -1 sphinx-bootstrap-theme/0.8.1-4 On Friday, June 07 2024, Santiago Vila wrote: > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > [...] > dh_sphinxdoc --package=python-skbio-doc > dh_sphinxdoc: error: > debian/python-skbio-doc/

Processed: kglobalacceld has an undeclared file conflict on /usr/lib/systemd/user/plasma-kglobalaccel.service

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libkf5globalaccel-bin Bug #1073030 [kglobalacceld] kglobalacceld has an undeclared file conflict on /usr/lib/systemd/user/plasma-kglobalaccel.service Added indication that 1073030 affects libkf5globalaccel-bin -- 1073030: https://bugs.debian.org/cgi-b

Bug#1073030: kglobalacceld has an undeclared file conflict on /usr/lib/systemd/user/plasma-kglobalaccel.service

2024-06-11 Thread Helmut Grohne
Package: kglobalacceld Version: 6.0.90-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libkf5globalaccel-bin kglobalacceld has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/systemd/user/plasma-kglobal

Bug#1069575: FTBFS in experimental

2024-06-11 Thread Matthias Geiger
On Mon, 10 Jun 2024 11:02:23 +0200 Jonas Smedegaard wrote: > > > > I will look into updating concurrent-queue to 2.5.0 then. > > Any news on updating concurrent-queue to 2.5.0? > > - Jonas Just uploaded to exp along with async-io 2.3.3. best, werdahias

Bug#1060528: marked as done (libu2f-host: Please switch Build-Depends to systemd-dev)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 20:40:07 + with message-id and subject line Bug#1060528: fixed in libu2f-host 1.1.10-3.1 has caused the Debian Bug report #1060528, regarding libu2f-host: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the pr

Bug#1073023: ocaml-luv: autopkgtest regression: Version 3.15 of the dune language is not supported

2024-06-11 Thread Paul Gevers
Source: ocaml-luv Version: 0.5.12-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail in testing. Can you please investigate the situation and fix it? I copied some of

Bug#1073014: dhcpcd: flaky autopkgtest: Obtaining network configuration for veth1 via dhcp... timed out

2024-06-11 Thread Paul Gevers
Source: dhcpcd Version: 1:10.0.8-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package because it was tested for glibc. I noticed that it regularly fails. Because the unstable-to-testing migration so

Bug#1073013: [Pkg-javascript-devel] Bug#1073013: nodejs: Testsuite fails with OpenSSL 3.2.2

2024-06-11 Thread Jérémy Lal
Le mar. 11 juin 2024 à 22:00, Sebastian Andrzej Siewior < sebast...@breakpoint.cc> a écrit : > Package: nodejs > Version: 20.14.0+dfsg-1 > Severity: serious > Tags: patch > > OpenSSL 3.2.2 introduced an error code a behaviour Node was testing and > now "test/parallel/test-http2-https-fallback.js"

Bug#1073013: nodejs: Testsuite fails with OpenSSL 3.2.2

2024-06-11 Thread Sebastian Andrzej Siewior
Package: nodejs Version: 20.14.0+dfsg-1 Severity: serious Tags: patch OpenSSL 3.2.2 introduced an error code a behaviour Node was testing and now "test/parallel/test-http2-https-fallback.js" is unhappy. The OpenSSL change is was introduced in https://github.com/openssl/openssl/pull/24338. I don't

Bug#1060528: libu2f-host: Please switch Build-Depends to systemd-dev

2024-06-11 Thread Philipp Kern
On Thu, Jan 11, 2024 at 11:36:52PM +0100, bi...@debian.org wrote: > your package libu2f-host declares a Build-Depends on systemd and/or > udev. > > In most cases, this build dependency is added to get the paths that > are defined in udev.pc or systemd.pc (via pkgconfig). It turns out the package

Bug#1073009: doesn't work with SQLAlchemy 2.X

2024-06-11 Thread Piotr Ożarowski
Source: openstack-trove Version: 1:21.0.1-2 Severity: serious Tags: ftbfs Hi, I uploaded SQLAlchemy 2.X to unstable and openstack-trove currently FTBFS due to failing tests (tries to import sqlalchemy.databases which is no longer available) so the code is definitely not ready for SA 2.X. I gues

Bug#1071075: marked as done (python-easydev accesses the internet during the build)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 18:19:18 + with message-id and subject line Bug#1071075: fixed in python-easydev 0.13.2+dfsg1-2 has caused the Debian Bug report #1071075, regarding python-easydev accesses the internet during the build to be marked as done. This means that you claim that t

Bug#1071075: marked as pending in python-easydev

2024-06-11 Thread Sergio Durigan Junior
Control: tag -1 pending Hello, Bug #1071075 in python-easydev 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/python-easydev/-/commit/21e41

Processed: Bug#1071075 marked as pending in python-easydev

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1071075 [src:python-easydev] python-easydev accesses the internet during the build Added tag(s) pending. -- 1071075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#1058130: closed by Debian FTP Masters (reply to Ulises Vitulli ) (Bug#1058130: fixed in python-nmea2 1.19.0-1)

2024-06-11 Thread Sergio Durigan Junior
Control: tags -1 + patch On Tuesday, May 14 2024, Adrian Bunk wrote: > Control: reopen -1 > > On Mon, Feb 12, 2024 at 10:57:03PM +, Debian Bug Tracking System wrote: >>... >> python-nmea2 (1.19.0-1) unstable; urgency=medium >> . >>* New upstream release (Closes: #1058130). >>... >> Rele

Processed: Re: Bug#1058130: closed by Debian FTP Masters (reply to Ulises Vitulli ) (Bug#1058130: fixed in python-nmea2 1.19.0-1)

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1058130 [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) patch. -- 1058130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058130 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1066608: dvbstreamer: diff for NMU version 2.1.0-5.7

2024-06-11 Thread Francisco Vilmar Cardoso Ruviaro
Control: tags 1066608 + patch Control: tags 1066608 + pending Dear maintainer, I've prepared an NMU for dvbstreamer (versioned as 2.1.0-5.7) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru dvbstreamer-2.1.0/debian/chan

Processed: dvbstreamer: diff for NMU version 2.1.0-5.7

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags 1066608 + patch Bug #1066608 [src:dvbstreamer] dvbstreamer: FTBFS: standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function ‘UTF8_nextchar’ [-Werror=implicit-function-declaration] Ignoring request to alter tags of bug #1066608 to the same ta

Processed: found 1069677 in 0.21.10-1

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069677 0.21.10-1 Bug #1069677 {Done: Jonas Smedegaard } [src:rust-rustls] rust-rustls: CVE-2024-32650 Marked as found in versions rust-rustls/0.21.10-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069

Bug#1073001: buildbot FTBFS: python3-sqlalchemy (<< 1.5) no longer satisfiable

2024-06-11 Thread Helmut Grohne
Source: buildbot Version: 3.10.1-2 Severity: serious Tags: ftbfs trixie sid buildbot can no longer be built in unstable as the python3-sqlalchemy package is too new to satisfy buildbot's build dependencies. It likely needs an upload that establishes compatibility with newer sqlalchemy. Helmut

Bug#1070815: marked as done (libdrm-intel1 should be compiled for arm64)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 15:49:31 + with message-id and subject line Bug#1070815: fixed in libdrm 2.4.121-2 has caused the Debian Bug report #1070815, regarding libdrm-intel1 should be compiled for arm64 to be marked as done. This means that you claim that the problem has been deal

Bug#1069904: marked as done (Autopkgtests failed)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 15:19:01 + with message-id and subject line Bug#1069904: fixed in python-gnupg 0.5.2-2 has caused the Debian Bug report #1069904, regarding Autopkgtests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: libdrm-intel1 should be compiled for arm64

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1070815 {Done: Timo Aaltonen } [libdrm-intel1] libdrm-intel1 should be compiled for arm64 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No lon

Bug#1072183: fenics-dolfinx: FTBFS with nanobind 2.0

2024-06-11 Thread Timo Röhling
Hi, * Francesco Ballarin [2024-06-11 09:53]: Hopefully there won't be future ABI breaks that aren't aligned with a fenics-basix/fenics-dolfinx release, but if there will be we will look forward to any suggestion from you on how to come up with a more elegant solution. I gave it a bit of thought

Processed: Bug#1069904 marked as pending in python-gnupg

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069904 [python3-gnupg] Autopkgtests failed Ignoring request to alter tags of bug #1069904 to the same tags previously set -- 1069904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069904 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1069904: marked as pending in python-gnupg

2024-06-11 Thread Elena Grandi
Control: tag -1 pending Hello, Bug #1069904 in python-gnupg 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/python-gnupg/-/commit/ed1d9477c

Bug#1069677: marked as done (rust-rustls: CVE-2024-32650)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 13:49:15 + with message-id and subject line Bug#1069677: fixed in rust-rustls 0.21.12-1 has caused the Debian Bug report #1069677, regarding rust-rustls: CVE-2024-32650 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1072977: bembo.debian.org TLS certificate is not signed by a well-known authority

2024-06-11 Thread Antoine Le Gonidec
While the update to apt-listbugs 0.1.42 does indeed trigger the reported problem, its cause is not in apt-listbugs code itself. This update uses https by default, but one of the servers answering to bugs.debian.org (bembo.debian.org) uses a TLS certificate that is not signed by a well-known author

Bug#1072977: bembo.debian.org TLS certificate is not signed by a well-known authority

2024-06-11 Thread Antoine Le Gonidec
> This update uses https by default, but one of the servers answering to > bugs.debian.org (bembo.debian.org) uses a TLS certificate that is not > signed by a well-known authority, leading to the certificate > verification failure. You can probably forget about that, further investigation seems to

Processed: Re: pycryptodome: FTBFS: cannot find -lasan and -lubsan on loong64, sparc64 and other architectures

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > Severity -1 normal Bug #1072992 [src:pycryptodome] pycryptodome: FTBFS: cannot find -lasan and -lubsan on loong64, sparc64 and other architectures Severity set to 'normal' from 'serious' -- 1072992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072992 Debian

Bug#1072992: pycryptodome: FTBFS: cannot find -lasan and -lubsan on loong64, sparc64 and other architectures

2024-06-11 Thread zhangdandan
Control: Severity -1 normal

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

2024-06-11 Thread Julian Wollrath
Am Di, 11 Jun 2024 13:22:29 +0100 schrieb Simon McVittie : > On Tue, 11 Jun 2024 at 13:28:52 +0200, Chris Hofstaedtler wrote: > > Maybe smcv can chime in here. > > [...] > > I think there is a better way than running a > > postinst script in each individual package (triggers?). > > Yes, there is a

Bug#1072992: pycryptodome: FTBFS: cannot find -lasan and -lubsan on loong64, sparc64 and other architectures

2024-06-11 Thread zhangdandan
Source: pycryptodome Version: 3.20.0+dfsg-1 Severity: serious Tags: ftbfs User: debian-loonga...@lists.debian.org Usertags: loong64 Compiling the pycryptodome failed for loong64 and others architectures in the Debian Package Auto-Building environment. ... [  3%] Building C object CMakeFiles/tes

Bug#1070411: marked as done (containerd fails to build as a normal user due to sysctl)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 12:34:13 + with message-id and subject line Bug#1070411: fixed in containerd 1.6.24~ds1-2 has caused the Debian Bug report #1070411, regarding containerd fails to build as a normal user due to sysctl to be marked as done. This means that you claim that the

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

2024-06-11 Thread Simon McVittie
On Tue, 11 Jun 2024 at 13:28:52 +0200, Chris Hofstaedtler wrote: > Maybe smcv can chime in here. (I am not a maintainer of gdk-pixbuf and I do not intend to be any sort of single point of failure for Debian's use of gdk-pixbuf; I have sometimes done team uploads of it as part of the GNOME team, bu

Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

2024-06-11 Thread John Paul Adrian Glaubitz
Hi Guillem, On Tue, 2024-06-11 at 13:42 +0200, Guillem Jover wrote: > > I had a look at this, and it seems like this package has never really > > worked on ARM systems at all? And this was hidden due to the missing > > declarations not being an error. > > > > AFAIK, only x86 (i386 and amd64), ia6

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

2024-06-11 Thread Julian Wollrath
Am Di, 11 Jun 2024 13:28:52 +0200 schrieb Chris Hofstaedtler : > On Tue, Jun 11, 2024 at 01:04:06PM +0200, Julian Wollrath wrote: > > > > Specifically, the problem is that > > > > debian/libjxl-gdk-pixbuf.postinst and > > > > debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64 > > > > archite

Bug#1072981: marked as done (tinyows: FTBFS in sid: error: implicit declaration of function 'atoi')

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 12:04:45 + with message-id and subject line Bug#1072981: fixed in tinyows 1.2.1-2 has caused the Debian Bug report #1072981, regarding tinyows: FTBFS in sid: error: implicit declaration of function 'atoi' to be marked as done. This means that you claim that

Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

2024-06-11 Thread Guillem Jover
Control: tag -1 patch [ CCing debian-arm list to loop them into the porting issue. ] Hi! On Fri, 2024-06-07 at 14:42:18 +0200, Guillem Jover wrote: > On Sat, 2024-04-20 at 14:56:40 +0200, Lucas Nussbaum wrote: > > Source: libx86emu > > Version: 3.5-1 > > Severity: serious > > Justification: FTBF

Processed: Re: Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1069498 [src:libx86emu] libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1069498: https://bugs.debian.org/cgi-bin/bugreport

Bug#1072980: marked as done (guestfs-tools - build-depends unsatisfiable on armel)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 11:34:11 + with message-id and subject line Bug#1072980: fixed in guestfs-tools 1.52.0-3 has caused the Debian Bug report #1072980, regarding guestfs-tools - build-depends unsatisfiable on armel to be marked as done. This means that you claim that the probl

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

2024-06-11 Thread Chris Hofstaedtler
On Tue, Jun 11, 2024 at 01:04:06PM +0200, Julian Wollrath wrote: > > > Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst > > > and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64 > > > architecture which means that libjxl-gdk-pixbuf is uninstallable on > > > architectures

Processed: Re: Bug#1069426: nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1069426 [src:nocache] nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined Added tag(s) patch. -- 1069426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069426 Debian Bug Tracking System Contact ow...@bugs.deb

Bug#1069426: nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined

2024-06-11 Thread Guillem Jover
Control: tag -1 patch Hi! On Sat, 2024-04-20 at 15:01:27 +0200, Lucas Nussbaum wrote: > Source: nocache > Version: 1.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf > During a rebuild of all

Processed: Re: [Debian-med-packaging] Bug#1072979: beast-mcmc - build-dependencies unsatisfiable on i386.

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 RM: beast-mmc [i386] -- RoM ; dependency not available anymore Bug #1072979 [beast-mcmc] beast-mcmc - build-dependencies unsatisfiable on i386. Changed Bug title to 'RM: beast-mmc [i386] -- RoM ; dependency not available anymore' from 'beast-mcmc - build-

Bug#1072979: [Debian-med-packaging] Bug#1072979: beast-mcmc - build-dependencies unsatisfiable on i386.

2024-06-11 Thread Charles Plessy
Control: retitle -1 RM: beast-mmc [i386] -- RoM ; dependency not available anymore Control: reassign -1 ftp.debian.org Hi all, > On 11 June 2024 at 10:05, Peter Green wrote: > | > | beast-mcmc build-depends on r-cran-rjava, which is no longer available > | on i386. It appears that the package f

Bug#1061008: marked as done (aiohttp-jinja2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 11:19:03 + with message-id and subject line Bug#1061008: fixed in aiohttp-jinja2 1.6-1 has caused the Debian Bug report #1061008, regarding aiohttp-jinja2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned e

Bug#1070411: marked as pending in containerd

2024-06-11 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #1070411 in containerd 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/go-team/packages/containerd/-/commit/5b620db2446fc1a0d

Processed: Bug#1070411 marked as pending in containerd

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070411 [src:containerd] containerd fails to build as a normal user due to sysctl Added tag(s) pending. -- 1070411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

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

2024-06-11 Thread Julian Wollrath
Hi, Am Di, 11 Jun 2024 08:19:54 +0200 schrieb 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 al

Bug#1052660: gst-plugins-bad1.0: Fails to build: netsim build test failing

2024-06-11 Thread Emilio Pozuelo Monfort
Control: severity -1 important On Mon, 25 Sep 2023 15:52:57 -0400 Jeremy Bicha wrote: Source: gst-plugins-bad1.0 Version: 1.22.4-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3000 gst-plugins-bad1.0's elements_netsim build te

Processed: Re: gst-plugins-bad1.0: Fails to build: netsim build test failing

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1052660 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: Fails to build: netsim build test failing Severity set to 'important' from 'serious' -- 1052660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052660 Debian Bug Tracking System Co

Bug#1072979: beast-mcmc - build-dependencies unsatisfiable on i386.

2024-06-11 Thread Dirk Eddelbuettel
On 11 June 2024 at 10:05, Peter Green wrote: | Package: beast-mcmc | Version: 1.10.4+dfsg-5 | Severity: serious | x-debbugs-cc: r-cran-rj...@packages.debian.org | | beast-mcmc build-depends on r-cran-rjava, which is no longer available | on i386. It appears that the package failed to build, and

Processed: block 1072938 with 1052028

2024-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1072938 with 1052028 Bug #1072938 [src:jupyterhub] jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2) 1072938 was blocked by: 1052028 1072938 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1072938 to

Bug#1068119: marked as done (s390-tools: FTBFS: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [-Werror=array-bounds=])

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 10:04:38 + with message-id and subject line Bug#1068119: fixed in s390-tools 2.16.0-2.1 has caused the Debian Bug report #1068119, regarding s390-tools: FTBFS: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [

Bug#1068119: Solution for 1068119 - compile error for s390-tools 2.16.0-2

2024-06-11 Thread Johannes Schauer Marin Rodrigues
Control: affects -1 + mmdebstrap Hi, On Mon, 27 May 2024 12:07:11 +0200 Steffen Eiden wrote: > this issue is already fixed upstream since v2.22.0. > > Do one of: > - apply the upstream fix [1,2] > - update your package to at least v2.22.0 > > > The upstream fix disables the warning similar to

Processed: Re: Solution for 1068119 - compile error for s390-tools 2.16.0-2

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + mmdebstrap Bug #1068119 [src:s390-tools] s390-tools: FTBFS: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [-Werror=array-bounds=] Added indication that 1068119 affects mmdebstrap -- 1068119: https://b

Bug#1072183: fenics-dolfinx: FTBFS with nanobind 2.0

2024-06-11 Thread Francesco Ballarin
Source: fenics-dolfinx Followup-For: Bug #1072183 X-Debbugs-Cc: francesco.balla...@unicatt.it, roehl...@debian.org, dpars...@debian.org Thanks Timo. I confirm that nanobind, fenics-basix and fenics-dolfinx migrated yesterday to testing. Hopefully there won't be future ABI breaks that aren't align

Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

2024-06-11 Thread Christoph Berg
Re: Martin-Éric Racine > Incorrect delayed argument: ValueError: delayed days value must be a decimal > integer: `dput -e 0` works around that part of the problem. I then ran into another problem though: Uploading to ssh-upload [DELAYED/0-day] (via scp to ssh.upload.debian.org): Traceback (most

Bug#1072982: lime - build-depends on package that is not in testing.

2024-06-11 Thread Peter Green
Package: lime Version: 5.2.0+dfsg-3 Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable lime build-depends on boost1.74, which is no longer in testing. It seems that lime was removed from t

Bug#1072979: beast-mcmc - build-dependencies unsatisfiable on i386.

2024-06-11 Thread Peter Green
Package: beast-mcmc Version: 1.10.4+dfsg-5 Severity: serious x-debbugs-cc: r-cran-rj...@packages.debian.org beast-mcmc build-depends on r-cran-rjava, which is no longer available on i386. It appears that the package failed to build, and the old binaries were then removed.

Bug#1072981: tinyows: FTBFS in sid: error: implicit declaration of function 'atoi'

2024-06-11 Thread Andreas Beckmann
Source: tinyows Version: 1.2.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, tinyows FTBFS in a minimal sid pbuilder chroot: dh_auto_build make -j3 make[1]: Entering directory '/build/tinyows-1.2.1' gcc -g -O2 -Werror=implicit-function-declaration -ffi

Bug#1072980: guestfs-tools - build-depends unsatisfiable on armel

2024-06-11 Thread Peter Green
Package: guestfs-tools Version: 1.52.0-2 Severity: serious User: debian...@lists.debian.org Usertags: edos-uninstallable guestfs-tools on armel build-depends on linux-image-marvell:armel | linux-image-versatile:armel neither of which is available anymore. It looks like the only kernel now avail

Bug#1067545: marked as done (FTBFS on 32-bit time64 arches: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’})

2024-06-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jun 2024 08:35:46 + with message-id and subject line Bug#1067545: fixed in klatexformula 4.1.0-1.1 has caused the Debian Bug report #1067545, regarding FTBFS on 32-bit time64 arches: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’} to be marked as done

Bug#1072977: apt-listbugs 0.1.42 is broken

2024-06-11 Thread Karine Crèvecœur
Package: apt-listbugs Version: 0.1.42 Severity: grave Hi, Since the upgrade to version 0.1.42, apt-listbugs doesn't work anymore. As examplen the command apt-listbugs list apt-lisbugs gave the error: Retrieving bug reports... 0% Fail Error retrieving bug reports from the server with the fo

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

2024-06-11 Thread Sebastian Ramacher
Hi On 2024-06-11 10:18:14 +0200, Jochen Sprickerhof wrote: > Hi Reinhard, > > * Reinhard Tartler [2024-06-10 22:26]: > > Are you sure that the test is actually executing a sysctl(2) command? > > Looking at the code, it seems to me that this is code is assembling a > > runtime spec that the CRI i

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

2024-06-11 Thread Jochen Sprickerhof
Hi Reinhard, * Reinhard Tartler [2024-06-10 22:26]: Are you sure that the test is actually executing a sysctl(2) command? Looking at the code, it seems to me that this is code is assembling a runtime spec that the CRI implementation will then carry out. Forthermore, the output above indicates t

Processed: prewikka: diff for NMU version 5.2.0-2.1

2024-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags 1060985 + pending Bug #1060985 [src:prewikka] prewikka: FTBFS: ModuleNotFoundError: No module named 'six' Added tag(s) pending. -- 1060985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060985 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1060985: prewikka: diff for NMU version 5.2.0-2.1

2024-06-11 Thread Chris Hofstaedtler
Control: tags 1060985 + pending Dear maintainer, I've prepared an NMU for prewikka (versioned as 5.2.0-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru prewikka-5.2.0/debian/changelog prewikka-5.2.0/debian/changelog --- prewikka-5.2

Bug#1072971: kuserfeedback: FTBFS on s390x: OpenGLInfoSourceTest::testOpenGLInfoSource() '!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE

2024-06-11 Thread Emilio Pozuelo Monfort
Source: kuserfeedback Version: 1.3.0-3 Severity: serious Hi, During a rebuild for the Qt6 transition, your package failed to build on s390x: * Start testing of OpenGLInfoSourceTest * Config: Using QtTest library 5.15.13, Qt 5.15.13 (s390x-big_endian-lp64 shared (dynamic)