Processed: Re: Bug#1074591: /etc/cron.monthly/acct uses `last` which has been removed from util-linux

Processing control commands: > retitle -1 acct: cron job needs wtmpdb last and points it to wtmp file Bug #1074591 [acct] /etc/cron.monthly/acct points 'wtmpdb last' at a wtmp format file Changed Bug title to 'acct: cron job needs wtmpdb last and points it to wtmp file' from '/etc/cron.monthly/a

Bug#1074591: /etc/cron.monthly/acct uses `last` which has been removed from util-linux

Control: retitle -1 acct: cron job needs wtmpdb last and points it to wtmp file On Thu, Jun 05, 2025 at 10:23:37PM +0100, Andrew Bower wrote: > On Sun, Jun 01, 2025 at 12:12:42PM +, internet2poi...@aim.com wrote: > > acct currently does not have any relationship with the new wtmpdb package, >

Bug#1107347: papi:FTBFS:build failed(#error Need to define rmb for this architecture!)

Source: papi Version: 7.1.0-5 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 Dear papi maintainer, The package papi build failed on riscv64.The crucial buildd log below: ``` cc -DPAPI_NO_MEMORY_MANAGEMENT -DSTATIC_PAPI_EVENTS_TABLE -DUSE_PERFEVENT_RDP

Bug#1104656: marked as done (tao-json-dev: new version breaks src:tao-config and src:xenium)

Your message dated Thu, 05 Jun 2025 22:24:13 + with message-id and subject line Bug#1104658: fixed in tao-json 1.0.0~beta14+really0.0+git20200604.f357d72-1 has caused the Debian Bug report #1104658, regarding tao-json-dev: new version breaks src:tao-config and src:xenium to be marked as done.

Bug#1104658: marked as done (tao-json-dev: new version breaks src:tao-config and src:xenium)

Your message dated Thu, 05 Jun 2025 22:24:13 + with message-id and subject line Bug#1104656: fixed in tao-json 1.0.0~beta14+really0.0+git20200604.f357d72-1 has caused the Debian Bug report #1104656, regarding tao-json-dev: new version breaks src:tao-config and src:xenium to be marked as done.

Bug#1104658: marked as done (tao-json-dev: new version breaks src:tao-config and src:xenium)

Your message dated Thu, 05 Jun 2025 22:24:13 + with message-id and subject line Bug#1104658: fixed in tao-json 1.0.0~beta14+really0.0+git20200604.f357d72-1 has caused the Debian Bug report #1104658, regarding tao-json-dev: new version breaks src:tao-config and src:xenium to be marked as done.

Bug#1104656: marked as done (tao-json-dev: new version breaks src:tao-config and src:xenium)

Your message dated Thu, 05 Jun 2025 22:24:13 + with message-id and subject line Bug#1104656: fixed in tao-json 1.0.0~beta14+really0.0+git20200604.f357d72-1 has caused the Debian Bug report #1104656, regarding tao-json-dev: new version breaks src:tao-config and src:xenium to be marked as done.

Processed: retitle acct cron job bug

Processing commands for cont...@bugs.debian.org: > retitle 1074591 /etc/cron.monthly/acct points 'wtmpdb last' at a wtmp format > file Bug #1074591 [acct] /etc/cron.monthly/acct uses `last` which has been removed from util-linux Changed Bug title to '/etc/cron.monthly/acct points 'wtmpdb last' a

Bug#1107304: python3.13 left out of toolchain packages list

Release Team, I noticed today while reading https://bugs.debian.org/1107304 that python3.13 was not included in the toolchain packages list [1]. My reading of the list is that it was intended to be there. If it had been on the list, the last version that would have been allowed into Testing withou

Bug#1107304: pdfarranger: Fails to start: RuntimeError: context has already been set

On Thu, Jun 05, 2025 at 10:05:51AM +0200, intrigeri wrote: on my sid system, pdfarranger fails to start: $ pdfarranger Traceback (most recent call last): File "/bin/pdfarranger", line 33, in sys.exit(load_entry_point('pdfarranger==1.11.1', 'console_scripts', 'pdfarranger')())

Bug#1074591: /etc/cron.monthly/acct uses `last` which has been removed from util-linux

On Sun, Jun 01, 2025 at 12:12:42PM +, internet2poi...@aim.com wrote: > acct currently does not have any relationship with the new wtmpdb package, > though, so the cronjob as shipped will never work and will send an error > message every month. > > acct should have a Depends or at least a Recom

Bug#1103802: closed by Debian FTP Masters (reply to Colin Watson ) (Bug#1103802: fixed in austin 3.7.0-1)

On Fri, May 30, 2025 at 12:32:25AM +0100, Colin Watson wrote: On Tue, May 20, 2025 at 05:42:57PM +0100, Colin Watson wrote: I'm just pinging this bug to avoid autoremoval kicking in before follow-up versions have time to migrate to testing: And again: And one more bump. https://tracker.debi

Processed: tags 1075693 + patch

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

Bug#1106281: broken by ansible 12

Hi Marco (2025.05.22_14:13:21_+0200) Please check if this is still reproducible with 0.3.25~a1-1? Upstream *thinks* this is compatible: https://github.com/mitogen-hq/mitogen/issues/1258#issuecomment-2941886559 Now's the time to report issues to them. Stefano -- Stefano Rivera http://tumblewe

Bug#1075693: Fixing xzoom build

Hi there, I have worked to fix this bug! Now with gcc 14, it's necessary has all functions declared. The code are building without the -DTIMER flag, this flag switch in include or not the libs that define the functions that report the -Wdeprecated-declarations error: 43 │ #ifdef TIMER

Bug#1104656: [Debian-med-packaging] Bug#1104656: tao-json-dev: new version breaks src:tao-config and src:xenium

Hi Santiago, Santiago Vila, on 2025-06-05: > retitle 1104656 tao-json-dev: new version breaks src:tao-config and src:xenium > affects 1104656 src:tao-config src:xenium > thanks > > Note: Those affects are for the benefit of anybody doing archive rebuilds for > unstable, > but this bug would only

Processed: Re: Bug#1107288: qemu-system-ppc - kvm configured incorrectly for debian: Can't support 64 kiB guest pages with 4 kiB host pages

Processing control commands: > severity -1 serious Bug #1107288 [qemu-system-ppc] qemu-system-ppc - kvm configured incorrectly for debian: Can't support 64 kiB guest pages with 4 kiB host pages Severity set to 'serious' from 'important' -- 1107288: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Processed: Re: janus: autopkgtest failure

Processing control commands: > tags -1 patch Bug #1102692 [janus] janus: autopkgtest failure Added tag(s) patch. -- 1102692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1102692: janus: autopkgtest failure

Control: tags -1 patch -- Hi, On Sat, Apr 12, 2025 at 11:12:44AM +0300, Adrian Bunk wrote: > Source: buildd=janus > Version: 1.1.2-2 > Severity: serious > X-Debbugs-Cc: Guillem Jover > > https://tracker.debian.org/pkg/janus > > Issues preventing migration: > ∙ ∙ autopkgtest for janus/1.1.2-2:

Bug#1053602: removed link to mannual

On Fri, Apr 25, 2025 at 11:43:31PM +0200, Thomas Lange wrote: > I've removed the link to this manual on > https://www.debian.org/security/ > and updated the status on www.d.o/doc. > But I think we may should the manual also from /doc. Assuming the current maintainer does not object, I hope to spen

Processed: Bug#1107311 marked as pending in libfile-find-rule-perl

Processing control commands: > tag -1 pending Bug #1107311 [src:libfile-find-rule-perl] libfile-find-rule-perl: CVE-2011-10007 Added tag(s) pending. -- 1107311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107311: marked as done (libfile-find-rule-perl: CVE-2011-10007)

Your message dated Thu, 05 Jun 2025 12:33:56 + with message-id and subject line Bug#1107311: fixed in libfile-find-rule-perl 0.34-4 has caused the Debian Bug report #1107311, regarding libfile-find-rule-perl: CVE-2011-10007 to be marked as done. This means that you claim that the problem has

Bug#1107311: marked as pending in libfile-find-rule-perl

Control: tag -1 pending Hello, Bug #1107311 in libfile-find-rule-perl 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/perl-team/modules/packages/libfile-find-ru

Bug#1107311: libfile-find-rule-perl: CVE-2011-10007

Source: libfile-find-rule-perl Version: 0.34-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/richardc/perl-file-find-rule/pull/4 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libfi

Bug#1106799: e2fsck-static: statically linked against glibc without a Built-Using: field

On Wed, Jun 04, 2025 at 10:21:32PM +0200, Aurelien Jarno wrote: > > they need to install dh-builtusing. It's also helpful for users who > > are confused why dpkg-buildpackage doesn't work. > > That's indeed can be confusing at a first glance. That said both apt > install and apt satisfy are able

Bug#1106428: Additional insights on the failing QUERY method test

Le jeu. 5 juin 2025 à 11:53, Santiago Vila a écrit : > Good news from the github issue: > > "I'm gonna include 65c8380 in the v20 release" > > https://github.com/nodejs/node/issues/51562#issuecomment-2943090159 I'm waiting a few hours to see if someone steps up, and will upload a patched nodejs

Processed: Re: Additional insights on the failing QUERY method test

Processing commands for cont...@bugs.debian.org: > reassign 1106428 nodejs Bug #1106428 [src:node-body-parser] node-body-parser: FTBFS: Error: expected 201 "Created", got 405 "Method Not Allowed" Bug reassigned from package 'src:node-body-parser' to 'nodejs'. No longer marked as found in versions

Processed: wsdd: Obsolete conffile /etc/default/wsdd

Processing commands for cont...@bugs.debian.org: > tags 1100767 + patch Bug #1100767 [wsdd] wsdd: Obsolete conffile /etc/default/wsdd Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1100767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=110

Bug#1106428: Additional insights on the failing QUERY method test

Good news from the github issue: "I'm gonna include 65c8380 in the v20 release" https://github.com/nodejs/node/issues/51562#issuecomment-2943090159 Thanks.

Bug#1107280: pymatgen: FTBFS: Tries to access Internet during build

Hi. I found a different mode of failure today: === FAILURES === __ TestVaspDoc.test_print_help[ISYM] ___ self = , tag = 'ISYM' @pytest.mark.parametrize("tag", ["ISYM"]) def test_print

Bug#1106428: Additional insights on the failing QUERY method test

El 5/6/25 a las 9:11, Jérémy Lal escribió: The best fix would be in the embedded copy of llhttp in nodejs 20.19.2 - remove the HTTP QUERY support that was added in https://github.com/nodejs/node/commit/eb25047b1b08180ed68dcefe2299682fbc7966ab

Bug#1106428: Additional insights on the failing QUERY method test

reassign 1106428 nodejs found 1106428 20.19.2+dfsg-1 affects 1106428 src:node-body-parser forwarded 1106428 https://github.com/nodejs/node/issues/51562#issuecomment-2943008360 thanks El 5/6/25 a las 11:21, Jérémy Lal escribió: Le jeu. 5 juin 2025 à 11:20, Santiago Vila mailto:sanv...@debian.org

Bug#1100767: wsdd: Obsolete conffile /etc/default/wsdd

tags 1100767 + patch thanks The attached patch add a .maintscript calling mv_conffile which should handle the /etc/default/wsdd -> /etc/wsdd-server/defaults conffile move without loosing the system configuration. Unsure if that is enough to properly handle the upgrade path and the fact that ea

Bug#1106428: Additional insights on the failing QUERY method test

Le jeu. 5 juin 2025 à 11:20, Santiago Vila a écrit : > El 5/6/25 a las 9:11, Jérémy Lal escribió: > > The best fix would be in the embedded copy of llhttp in nodejs 20.19.2 - > remove the HTTP QUERY support that was > > added in > https://github.com/nodejs/node/commit/eb25047b1b08180ed68dcefe2299

Bug#1106428: Additional insights on the failing QUERY method test

Le jeu. 5 juin 2025 à 03:17, Santiago Vila a écrit : > Note: Beware: The package has autopkgtests, so maybe it's not as simple > as disabling some tests. What can happen with the tests in testing > if they run again now? Could they fail? > I believe this case is supported by the transition-to-te

Bug#1107304: pdfarranger: Fails to start: RuntimeError: context has already been set

Package: pdfarranger Version: 1.11.1-2 Severity: grave Hi, on my sid system, pdfarranger fails to start: $ pdfarranger Traceback (most recent call last): File "/bin/pdfarranger", line 33, in sys.exit(load_entry_point('pdfarranger==1.11.1', 'console_scripts', 'pdfarranger')())

Bug#1106428: Additional insights on the failing QUERY method test

Le jeu. 5 juin 2025 à 02:28, Santiago Vila a écrit : > Thanks a lot for the investigation! > > So, it seems the logical thing to do here is to disable those failing > tests, > as they were not really intended to be run with nodejs 20. > > Is there any team preference about how to do that? > > I c