Processed: version

Processing commands for cont...@bugs.debian.org: > # only trixie and sid > found 1084649 4.0.3-2 Bug #1084649 [src:buildbot] buildbot: removal of Python standard libraries in Python 3.13 Marked as found in versions buildbot/4.0.3-2. > thanks Stopping processing here. Please contact me if you nee

Bug#1085400: glab: FTBFS: src/gitlab.com/gitlab-org/cli/api/project.go:24:48: not enough arguments in call to client.Projects.DeleteProject

Package: src:glab Version: 1.47.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --builddirectory=_

Bug#1085399: exchange-calendars: FTBFS: failing tests (probably due to recent tzdata)

Package: src:exchange-calendars Version: 4.5.6-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --bui

Bug#1082165: marked as done (libcangjie3-data: Missing Breaks+Replaces: libcangjie2-data)

Your message dated Fri, 18 Oct 2024 21:19:01 + with message-id and subject line Bug#1082165: fixed in libcangjie 1.4.0.really.1.3-1 has caused the Debian Bug report #1082165, regarding libcangjie3-data: Missing Breaks+Replaces: libcangjie2-data to be marked as done. This means that you claim

Bug#1076387: marked as done (Cannot use agda-stdlib modules at all)

Your message dated Fri, 18 Oct 2024 21:49:54 + with message-id and subject line Bug#1076387: fixed in agda-stdlib 2.1-1 has caused the Debian Bug report #1076387, regarding Cannot use agda-stdlib modules at all to be marked as done. This means that you claim that the problem has been dealt wi

Processed: buildbot: removal of Python standard libraries in Python 3.13

Processing commands for cont...@bugs.debian.org: > tags 1084649 ftbfs Bug #1084649 [src:buildbot] buildbot: removal of Python standard libraries in Python 3.13 Added tag(s) ftbfs. > severity 1084649 serious Bug #1084649 [src:buildbot] buildbot: removal of Python standard libraries in Python 3.13

Bug#1085385: marked as done (0ad: FTBFS with Python 3.12)

Your message dated Fri, 18 Oct 2024 21:04:33 + with message-id and subject line Bug#1085385: fixed in 0ad 0.0.26-6 has caused the Debian Bug report #1085385, regarding 0ad: FTBFS with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1064726: marked as done (0ad: FTBFS: ImportError: cannot import name 'dist' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py))

Your message dated Fri, 18 Oct 2024 21:04:33 + with message-id and subject line Bug#1064726: fixed in 0ad 0.0.26-6 has caused the Debian Bug report #1064726, regarding 0ad: FTBFS: ImportError: cannot import name 'dist' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py) to be marked

Processed: closing 1084283

Processing commands for cont...@bugs.debian.org: > close 1084283 8.0.6+dfsg-1 Bug #1084283 [src:kicad] kicad: FTBFS: kicad/project_tree_pane.cpp:2253:31: error: invalid conversion from ‘git_commit* const*’ to ‘const git_commit**’ [-fpermissive] Marked as fixed in versions kicad/8.0.6+dfsg-1. Bug

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

Your message dated Fri, 18 Oct 2024 20:50:21 + with message-id and subject line Bug#1058432: fixed in glyphslib 6.4.0+ds1-1 has caused the Debian Bug report #1058432, regarding glyphslib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

On Fri, Oct 18, 2024 at 09:35:04PM +0200, Paul Gevers wrote: > Hi, > > On 18-10-2024 21:09, Noah Meyerhans wrote: > > That'll work, obviously, but I do think it should be considered > > system-wide on the debci lxc environment. On a common Debian > > installation, this isn't something a package m

Processed: catch2: diff for NMU version 3.7.1-0.3

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was sramac...@debian.org). > usertag 1085386 + bsp-2024-10-at-sbg There were no usertags set. Usertags are now: bsp-2024-10-at-sbg. > tags 1085386 + patch Bug #1

Bug#1080108: marked as done (flake8-quotes: FTBFS: FAIL: test_stdin (test.test_checks.TestFlake8Stdin.test_stdin))

Your message dated Fri, 18 Oct 2024 19:49:24 + with message-id and subject line Bug#1080108: fixed in flake8-quotes 3.4.0-2 has caused the Debian Bug report #1080108, regarding flake8-quotes: FTBFS: FAIL: test_stdin (test.test_checks.TestFlake8Stdin.test_stdin) to be marked as done. This mea

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Hi, On 18-10-2024 21:09, Noah Meyerhans wrote: That'll work, obviously, but I do think it should be considered system-wide on the debci lxc environment. On a common Debian installation, this isn't something a package maintainer or user should need to care about, as the defaults should result in

Bug#1085385: marked as pending in 0ad

Control: tag -1 pending Hello, Bug #1085385 in 0ad 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/games-team/0ad/-/commit/593ca909f7b3beab323686b99e3bcc2f42298

Bug#1064726: marked as pending in 0ad

Control: tag -1 pending Hello, Bug #1064726 in 0ad 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/games-team/0ad/-/commit/e0ac513cf119d44364543e39f23eb98412ec7

Processed: Bug#1064726 marked as pending in 0ad

Processing control commands: > tag -1 pending Bug #1064726 [src:0ad] 0ad: FTBFS: ImportError: cannot import name 'dist' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py) Added tag(s) pending. -- 1064726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064726 Debian Bug Tracking Sy

Processed: Bug#1085385 marked as pending in 0ad

Processing control commands: > tag -1 pending Bug #1085385 [0ad] 0ad: FTBFS with Python 3.12 Added tag(s) pending. -- 1085385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

On Fri, Oct 18, 2024 at 08:04:59PM +0200, Paul Gevers wrote: > > The sysctl is namespaced, so it should suffice to set it in the > > testbed container. > > So, this should be done by src:backuppc then. That'll work, obviously, but I do think it should be considered system-wide on the debci lxc en

Bug#1085386: marked as done (catch2 FTBFS on i386: 30 - ApprovalTests (Failed))

Your message dated Fri, 18 Oct 2024 19:04:09 + with message-id and subject line Bug#1085386: fixed in catch2 3.7.1-0.3 has caused the Debian Bug report #1085386, regarding catch2 FTBFS on i386: 30 - ApprovalTests (Failed) to be marked as done. This means that you claim that the problem has be

Bug#1085391: python3-google-api-python-client has an undeclared file conflict

Package: python3-google-api-python-client Version: 2.149.0-1.1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-googleapi python3-google-api-python-client has an undeclared file conflict. This may result in an unpack error from dpkg. The file

Processed: python3-google-api-python-client has an undeclared file conflict

Processing control commands: > affects -1 + python3-googleapi Bug #1085391 [python3-google-api-python-client] python3-google-api-python-client has an undeclared file conflict Added indication that 1085391 affects python3-googleapi -- 1085391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10

Processed: python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py

Processing control commands: > affects -1 + python3-pyvkfft Bug #1085389 [python3-pyvkfft-cuda] python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py Added indication that 1085389 affects python3-pyvkfft -- 1085389: https://bugs.debian.org/cgi-bi

Bug#1085389: python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py

Package: python3-pyvkfft-cuda Version: 2024.1.4+ds1-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + python3-pyvkfft python3-pyvkfft-cuda has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-

Bug#910920: Fixed #1064886

Fixed during BSP 2024 in Salzburg diff -Nru tinc-1.1~pre18/debian/changelog tinc-1.1~pre18/debian/changelog --- tinc-1.1~pre18/debian/changelog 2021-06-27 20:10:22.0 +0200 +++ tinc-1.1~pre18/debian/changelog 2024-10-18 19:59:48.0 +0200 @@ -1,3 +1,10 @@ +tinc (1.1~pre18-1.1) UNRELEAS

Bug#1085386: catch2: diff for NMU version 3.7.1-0.3

user debian-rele...@lists.debian.org usertag 1085386 + bsp-2024-10-at-sbg tags 1085386 + patch thanks Dear maintainer, I've prepared an NMU for catch2 (versioned as 3.7.1-0.3). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru catch2-3.7.1/debian/changelog catch2-3.7.

Bug#1085153: marked as done (rrdtool: FTBFS on armel and armhf: passing argument 2 of ‘_sql_fetchrow’ from incompatible pointer type)

Your message dated Fri, 18 Oct 2024 18:40:17 + with message-id and subject line Bug#1085153: fixed in rrdtool 1.7.2-4.2 has caused the Debian Bug report #1085153, regarding rrdtool: FTBFS on armel and armhf: passing argument 2 of ‘_sql_fetchrow’ from incompatible pointer type to be marked as

Bug#1085386: catch2 FTBFS on i386: 30 - ApprovalTests (Failed)

Source: catch2 Version: 3.7.1-0.2 Severity: serious Tags: ftbfs patch X-Debbugs-Cc: Sebastian Ramacher https://buildd.debian.org/status/fetch.php?pkg=catch2&arch=i386&ver=3.7.1-0.2&stamp=1729275595&raw=0 ... 71/71 Test #30: ApprovalTests ***Failed

Processed: forcibly merging 1084393 1085114

Processing commands for cont...@bugs.debian.org: > forcemerge 1084393 1085114 Bug #1084393 [src:clazy] clazy: FTBFS: error: 'void ClazyPreprocessorCallbacks::[...]' marked 'override', but does not override Bug #1085114 [src:clazy] clazy: Fails to build with llvm 19 Severity set to 'serious' from

Bug#1064726: follow-up bug filed

I filed bug #1085385 to track the FTBFS with Python 3.12.

Processed: rrdtool: diff for NMU version 1.7.2-4.2

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was sramac...@debian.org). > usertag 1085153 + bsp-2024-10-at-sbg There were no usertags set. Usertags are now: bsp-2024-10-at-sbg. > tags 1085153 + patch Bug #1

Bug#1085153: rrdtool: diff for NMU version 1.7.2-4.2

user debian-rele...@lists.debian.org usertag 1085153 + bsp-2024-10-at-sbg tags 1085153 + patch thanks Dear maintainer, I've prepared an NMU for rrdtool (versioned as 1.7.2-4.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru rrdtool-1.7.2/debian/changelog rrdtool-1

Processed: tagging 910920

Processing commands for cont...@bugs.debian.org: > tags 910920 + patch Bug #910920 [tinc] tinc: fails to install: tinc.postinst: cannot create /etc/tinc/nets.boot: Directory nonexistent Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 910920: h

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Control: reassign -1 src:backuppc 4.4.0-10 Control: affects -1 src:perl Hi, On 18-10-2024 20:00, Noah Meyerhans wrote: The sysctl is namespaced, so it should suffice to set it in the testbed container. So, this should be done by src:backuppc then. Paul OpenPGP_signature.asc Description: O

Bug#1085385: 0ad: FTBFS with Python 3.12

Package: 0ad Version: 0.0.26-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: oliv...@tilloy.net Dear Maintainer, This is a follow-up bug to #1064726. 0ad fails to build from source on testing and unstable. This is mostly

Processed: Re: Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Processing control commands: > reassign -1 src:backuppc 4.4.0-10 Bug #1085289 [debci] Please set net.ipv4.ping_group_range sysctl on debci test hosts Bug reassigned from package 'debci' to 'src:backuppc'. Ignoring request to alter found versions of bug #1085289 to the same values previously set

Bug#1085320: mysql-workbench: FTBFS (error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]).

Adding -Wno-error=template-id-cdtor is not sufficient to resolve the build failure, it then fails with: In file included from /build/mysql-workbench-8.0.32+dfsg/library/grt/src/python_context.h:28, from /build/mysql-workbench-8.0.32+dfsg/library/grt/src/python_context.cpp:24

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

On Fri, Oct 18, 2024 at 07:48:43PM +0200, Paul Gevers wrote: > Hi Noah, > > On 18-10-2024 19:43, Noah Meyerhans wrote: > > In bookworm and earlier, ping uses CAP_NET_RAW file capabilities in > > order to obtain permission to transmit ICMP. The version in trixie and > > later no longer sets file b

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Hi Noah, On 18-10-2024 19:43, Noah Meyerhans wrote: In bookworm and earlier, ping uses CAP_NET_RAW file capabilities in order to obtain permission to transmit ICMP. The version in trixie and later no longer sets file based capabilities, instead relying on the net.ipv4.ping_group_range sysctl.

Bug#1084909: marked as done (catch2: FTBFS on multiple architectures)

Your message dated Fri, 18 Oct 2024 17:49:01 + with message-id and subject line Bug#1084909: fixed in catch2 3.7.1-0.2 has caused the Debian Bug report #1084909, regarding catch2: FTBFS on multiple architectures to be marked as done. This means that you claim that the problem has been dealt w

Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Control: reassign -1 debci Control: retitle -1 Please set net.ipv4.ping_group_range sysctl on debci test hosts On Thu, Oct 17, 2024 at 10:06:06PM +0200, Paul Gevers wrote: > system /bin/ping6 -c 1 localhost > 57s CheckHostAlive: first ping (/bin/ping6 -c 1 localhost) failed (512, ) > 57s no pin

Processed: Re: Bug#1085289: perl breaks backuppc autopkgtest: no ping response from localhost

Processing control commands: > reassign -1 debci Bug #1085289 [src:iputils,src:backuppc] iputils breaks backuppc autopkgtest: no ping response Bug reassigned from package 'src:iputils,src:backuppc' to 'debci'. No longer marked as found in versions backuppc/4.4.0-10 and iputils/3:20240905-1. Igno

Bug#1084909: catch2: diff for NMU version 3.7.1-0.2

user debian-rele...@lists.debian.org usertag 1084909 + bsp-2024-10-at-sbg tags 1084909 + patch thank you Dear maintainer, I've prepared an NMU for catch2 (versioned as 3.7.1-0.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru catch2-3.7.1/debian/changelog catch2-3

Processed: catch2: diff for NMU version 3.7.1-0.2

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was sramac...@debian.org). > usertag 1084909 + bsp-2024-10-at-sbg There were no usertags set. Usertags are now: bsp-2024-10-at-sbg. > tags 1084909 + patch Bug #1

Processed: Re: speech-dispatcher: systemd .service file using Alias= and not symlink

Processing control commands: > tags -1 + patch Bug #1084827 [speech-dispatcher] speech-dispatcher: systemd .service file using Alias= and not symlink Added tag(s) patch. -- 1084827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084827 Debian Bug Tracking System Contact ow...@bugs.debian.or

Bug#1084827: speech-dispatcher: systemd .service file using Alias= and not symlink

Control: tags -1 + patch Hi Samuel, hi bigon! Am 18.10.24 um 17:01 schrieb Michael Biebl: On Wed, 09 Oct 2024 10:44:59 +0200 Laurent Bigonville wrote: Package: speech-dispatcher Version: 0.11.4-2 Severity: serious Tags: sid trixie Hello, The systemd .service file using Alias= and not symlin

Bug#1085354: mbedtls FTBFS on arm64 with gcc 14

Source: mbedtls Version: 3.6.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mbedtls&arch=arm64&ver=3.6.0-3&stamp=1729201458&raw=0 ... In file included from /<>/library/ctr_drbg.c:13: In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/l

Processed: closing 1057900

Processing commands for cont...@bugs.debian.org: > close 1057900 Bug #1057900 [apcupsd] apcupsd: move files from / to /usr Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1057900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057900 Debian

Processed: tagging 1085162

Processing commands for cont...@bugs.debian.org: > tags 1085162 + sid trixie Bug #1085162 [src:s390-tools] s390-tools: move aliased files from / to /usr (DEP17) Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1085162: https://bugs.deb

Bug#1084827: speech-dispatcher: systemd .service file using Alias= and not symlink

On Wed, 09 Oct 2024 10:44:59 +0200 Laurent Bigonville wrote: Package: speech-dispatcher Version: 0.11.4-2 Severity: serious Tags: sid trixie Hello, The systemd .service file using Alias= and not symlink but as service is not enabled, the symlink is not created. That means that the LSB script

Bug#1085294: marked as done (mysql-8.0: CVE-2024-21247 CVE-2024-21241 CVE-2024-21239 CVE-2024-21238 CVE-2024-21237 CVE-2024-21236 CVE-2024-21231 CVE-2024-21230 CVE-2024-21219 CVE-2024-21218 CVE-2024-2

Your message dated Fri, 18 Oct 2024 07:25:59 -0700 with message-id <59a5eb2efd2972a1ab5ddbb8b90cbba6f5d36fae.ca...@canonical.com> and subject line 1085294 fixed has caused the Debian Bug report #1085294, regarding mysql-8.0: CVE-2024-21247 CVE-2024-21241 CVE-2024-21239 CVE-2024-21238 CVE-2024-2123

Bug#1085258: #0185258: openmpi-common: binary-all package hardcodes amd64 paths

Ouch, So the cmake files need to be moved from openmpi-common to libopenmpi-dev. I will prepare an upload, regards Alastair -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 e: mckins...@debian.org, im: @alastair:mckinstry.ie https://mastodon.ie/@amckinstry

Bug#1064886: Fixed #1064886

Fixed during BSP 2024 in Salzburg diff -Nru sqlite-utils-3.30/debian/changelog sqlite-utils-3.30/debian/changelog --- sqlite-utils-3.30/debian/changelog 2024-10-18 14:32:50.0 +0200 +++ sqlite-utils-3.30/debian/changelog 2022-11-01 16:02:33.0 +0100 @@ -1,11 +1,3 @@ -sqlite-utils (3.3

Processed: tagging 1064886

Processing commands for cont...@bugs.debian.org: > tags 1064886 + patch Bug #1064886 [sqlite-utils] sqlite-utils: missing Depends: python3-click-default-group Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064886: https://bugs.debian.org/cgi

Bug#1085319: marked as done (transmageddon fails to launch)

Your message dated Fri, 18 Oct 2024 14:03:10 +0200 with message-id <20241018120310.s3jar3jzs4jpd...@jwilk.net> and subject line Re: Bug#1085319: transmageddon fails to launch has caused the Debian Bug report #1085319, regarding transmageddon fails to launch to be marked as done. This means that yo

Bug#1085319: transmageddon fails to launch

Package: transmageddon Version: 1.5-3 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to launch transmageddon, it fails: $ transmageddon /usr/share/transmageddon/transmageddon.py:31: PyGIWarning: Notify was imported without specifying a version first. Use g

Bug#1085310: marked as done (libmousex-getopt-perl: FTBFS with libgetopt-long-descriptive-perl: test failures)

Your message dated Fri, 18 Oct 2024 10:49:08 + with message-id and subject line Bug#1085310: fixed in libmousex-getopt-perl 0.38-3 has caused the Debian Bug report #1085310, regarding libmousex-getopt-perl: FTBFS with libgetopt-long-descriptive-perl: test failures to be marked as done. This

Bug#1085309: latex2html: autopkgtest regression with Perl 5.40: 318s Possible precedence issue with control flow operator

Control: tag -1 + confirmed Control: tag -1 + patch On Fri, 18 Oct 2024 08:55:27 +0300, Niko Tyni wrote: > This package fails its autopkgtest checks with Perl 5.40 (currently > in unstable.) > > It looks like pstoimg started warning and stderr output causes > a test failure. > > https://ci.de

Processed: Re: Bug#1085309: latex2html: autopkgtest regression with Perl 5.40: 318s Possible precedence issue with control flow operator

Processing control commands: > tag -1 + confirmed Bug #1085309 [latex2html] latex2html: autopkgtest regression with Perl 5.40: 318s Possible precedence issue with control flow operator Added tag(s) confirmed. > tag -1 + patch Bug #1085309 [latex2html] latex2html: autopkgtest regression with Perl

Processed: Re: Bug#1084506 closed by Debian FTP Masters (reply to Petter Reinholdtsen ) (Bug#1084506: fixed in suck 4.3.5-2)

Processing commands for cont...@bugs.debian.org: > severity 1084506 normal Bug #1084506 {Done: Petter Reinholdtsen } [src:suck] suck: FTBFS: dh: error: unable to load addon quilt Severity set to 'normal' from 'serious' > retitle 1084506 suck: does not really need to build-depend on quilt Bug #108

Bug#1084506: closed by Debian FTP Masters (reply to Petter Reinholdtsen ) (Bug#1084506: fixed in suck 4.3.5-2)

severity 1084506 normal retitle 1084506 suck: does not really need to build-depend on quilt reopen 1084506 thanks Hi. I think the way you fixed this was not optimal: El 18/10/24 a las 9:09, Debian Bug Tracking System escribió: * Don't specify --with=quilt, since package uses '3.0 (quilt)' s

Bug#1085288: marked as done (libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl)

Your message dated Fri, 18 Oct 2024 10:34:00 + with message-id and subject line Bug#1085288: fixed in libtest2-plugin-uuid-perl 0.002009-2 has caused the Debian Bug report #1085288, regarding libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl to be marked as done. Th

Bug#1085310: marked as pending in libmousex-getopt-perl

Control: tag -1 pending Hello, Bug #1085310 in libmousex-getopt-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/libmousex-getopt

Bug#1081117: (r-cran-)survey not migrating to testing autoremovals

Control: close -1 4.2-1-1 > Le Fri, Oct 11, 2024 at 08:52:11AM -0500, Dirk Eddelbuettel a écrit : > > > > Could you take a look at https://bugs.debian.org/1081117 ? It is about to > > remove my packages Rcmdr and effects from testing as a repercussion. Le Fri, Oct 18, 2024 at 04:14:48PM +0900, C

Processed: Bug#1085310 marked as pending in libmousex-getopt-perl

Processing control commands: > tag -1 pending Bug #1085310 [src:libmousex-getopt-perl] libmousex-getopt-perl: FTBFS with libgetopt-long-descriptive-perl: test failures Added tag(s) pending. -- 1085310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085310 Debian Bug Tracking System Contact

Bug#1052807: lmod: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Control: severity -1 important Control: retitle -1 lmod: FTBFS: testsuite fails if 'hostname -f' fails On Tue, 26 Sep 2023 15:19:12 +0200 Lucas Nussbaum wrote: Source: lmod Version: 8.6.19-1 During a rebuild of all packages in sid, your package failed to build on amd64. This is a testsuite fa

Processed: Re: lmod: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Processing control commands: > severity -1 important Bug #1052807 [src:lmod] lmod: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Severity set to 'important' from 'serious' > retitle -1 lmod: FTBFS: testsuite fails if 'hostname -f' fails Bu

Bug#1085288: marked as pending in libtest2-plugin-uuid-perl

Control: tag -1 pending Hello, Bug #1085288 in libtest2-plugin-uuid-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/libtest2-plu

Bug#1085288: libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl

On Fri, 18 Oct 2024 08:33:10 +0300, Niko Tyni wrote: > I do wonder if we're testing the right thing in the autopkgtest checks > at the moment. If a test doesn't pass with some permutation of the > alternative dependencies, either the test dependencies or the test > itself seem buggy to me. Hm …

Processed: Bug#1085288 marked as pending in libtest2-plugin-uuid-perl

Processing control commands: > tag -1 pending Bug #1085288 [src:libtest2-plugin-uuid-perl] libtest2-plugin-uuid-perl: autopkgtest needs update for new version of perl Added tag(s) pending. -- 1085288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085288 Debian Bug Tracking System Contact o

Processed: Re: (r-cran-)survey not migrating to testing autoremovals

Processing control commands: > close -1 4.2-1-1 Bug #1081117 {Done: Paul Gevers } [src:r-cran-survey] src:r-cran-survey: fails to migrate to testing for too long Marked as fixed in versions r-cran-survey/4.2-1-1. Bug #1081117 {Done: Paul Gevers } [src:r-cran-survey] src:r-cran-survey: fails to m

Processed: Re: Bug#1082683: marked as done (kxd: FTBFS: certificate is valid for *, not localhost)

Processing control commands: > fixed 1082683 0.17-1 Bug #1082683 {Done: Alberto Bertogli } [src:kxd] kxd: FTBFS: certificate is valid for *, not localhost Marked as fixed in versions kxd/0.17-1. -- 1082683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082683 Debian Bug Tracking System Con

Bug#1082683: marked as done (kxd: FTBFS: certificate is valid for *, not localhost)

Control: fixed 1082683 0.17-1

Bug#1085148: marked as done (pidgin FTBFS with gcc 14 due to the libxml2 revert)

Your message dated Fri, 18 Oct 2024 09:19:14 + with message-id and subject line Bug#1085148: fixed in pidgin 2.14.13-2 has caused the Debian Bug report #1085148, regarding pidgin FTBFS with gcc 14 due to the libxml2 revert to be marked as done. This means that you claim that the problem has b

Bug#1075058: marked as done (h2o: ftbfs with GCC-14)

Your message dated Fri, 18 Oct 2024 09:04:17 + with message-id and subject line Bug#1075058: fixed in h2o 2.2.5+dfsg2-9 has caused the Debian Bug report #1075058, regarding h2o: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1085295: marked as done (starlette: CVE-2024-47874)

Your message dated Fri, 18 Oct 2024 08:38:29 + with message-id and subject line Bug#1085295: fixed in starlette 0.41.0-1 has caused the Debian Bug report #1085295, regarding starlette: CVE-2024-47874 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Re: Bug#1085148: pidgin FTBFS with gcc 14 due to the libxml2 revert

Processing control commands: > tag -1 patch fixed-upstream Bug #1085148 [src:pidgin] pidgin FTBFS with gcc 14 due to the libxml2 revert Added tag(s) fixed-upstream and patch. -- 1085148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085148 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#1085148: pidgin FTBFS with gcc 14 due to the libxml2 revert

Control: tag -1 patch fixed-upstream On Tue, Oct 15, 2024 at 03:39:41PM +0300, Adrian Bunk wrote: > Source: pidgin > Version: 2.14.13-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=pidgin&ver=2.14.13-1%2Bb1 > > ... > ../../../../libpurple/protocols/bonjour/

Bug#1084506: marked as done (suck: FTBFS: dh: error: unable to load addon quilt)

Your message dated Fri, 18 Oct 2024 07:05:45 + with message-id and subject line Bug#1084506: fixed in suck 4.3.5-2 has caused the Debian Bug report #1084506, regarding suck: FTBFS: dh: error: unable to load addon quilt to be marked as done. This means that you claim that the problem has been