Processed: src:petsc: fails to migrate to testing for too long

Processing control commands: > close -1 3.21.6+dfsg1-2 Bug #1086890 [src:petsc] src:petsc: fails to migrate to testing for too long Marked as fixed in versions petsc/3.21.6+dfsg1-2. Bug #1086890 [src:petsc] src:petsc: fails to migrate to testing for too long Marked Bug as done -- 1086890: https:

Bug#1086891: src:rtpengine: fails to migrate to testing for too long

Source: rtpengine Version: 12.5.1.9-1 Severity: serious Control: close -1 12.5.1.15-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 da

Processed: src:rtpengine: fails to migrate to testing for too long

Processing control commands: > close -1 12.5.1.15-1 Bug #1086891 [src:rtpengine] src:rtpengine: fails to migrate to testing for too long Marked as fixed in versions rtpengine/12.5.1.15-1. Bug #1086891 [src:rtpengine] src:rtpengine: fails to migrate to testing for too long Marked Bug as done --

Bug#1086889: src:pcbasic: fails to migrate to testing for too long

Source: pcbasic Version: 2.0.7-3 Severity: serious Control: close -1 2.0.7-4 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 as hav

Bug#1086890: src:petsc: fails to migrate to testing for too long

Source: petsc Version: 3.20.6+dfsg1-3 Severity: serious Control: close -1 3.21.6+dfsg1-2 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

Processed: src:pcbasic: fails to migrate to testing for too long

Processing control commands: > close -1 2.0.7-4 Bug #1086889 [src:pcbasic] src:pcbasic: fails to migrate to testing for too long Marked as fixed in versions pcbasic/2.0.7-4. Bug #1086889 [src:pcbasic] src:pcbasic: fails to migrate to testing for too long Marked Bug as done -- 1086889: https://bu

Bug#1086888: src:lziprecover: fails to migrate to testing for too long

Source: lziprecover Version: 1.24-2 Severity: serious Control: close -1 1.25~pre1-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

Processed: src:lziprecover: fails to migrate to testing for too long

Processing control commands: > close -1 1.25~pre1-1 Bug #1086888 [src:lziprecover] src:lziprecover: fails to migrate to testing for too long Marked as fixed in versions lziprecover/1.25~pre1-1. Bug #1086888 [src:lziprecover] src:lziprecover: fails to migrate to testing for too long Marked Bug as

Bug#1075266: marked as done (mgetty: ftbfs with GCC-14)

Your message dated Thu, 07 Nov 2024 07:34:38 + with message-id and subject line Bug#1075266: fixed in mgetty 1.2.1-1.4 has caused the Debian Bug report #1075266, regarding mgetty: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1086887: src:python-adb-shell: unsatisfied build dependency in testing: python3-libusb1

Source: python-adb-shell Version: 0.4.4-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be re

Bug#1075266: mgetty: diff for NMU version 1.2.1-1.4

Control: tags 1075266 + patch Dear maintainer, to fix the issues with this package, I've prepared an NMU for mgetty (versioned as 1.2.1-1.4), debdiff below. An upload to DELAYED/1 will follow shortly. Please feel free to tell me if I should delay it longer. Regards, Christoph diff -Nru mge

Processed: mgetty: diff for NMU version 1.2.1-1.4

Processing control commands: > tags 1075266 + patch Bug #1075266 [src:mgetty] mgetty: ftbfs with GCC-14 Added tag(s) patch. -- 1075266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fixed 1081569 in 3.4.0-1

Processing commands for cont...@bugs.debian.org: > fixed 1081569 3.4.0-1 Bug #1081569 {Done: David Prévot } [src:php-doctrine-persistence] php-doctrine-persistence: Another source-only upload needed for testing migration Marked as fixed in versions php-doctrine-persistence/3.4.0-1. > thanks Stop

Bug#1086290: log4c: FTBFS: psnup: page width and height must be set

I suspect this is related to recent changes to the psutils package, specificly https://bugs.debian.org/695178 >. I am not sure how that patch could cause this issue. I tried changing the call to use 'psnup -Pa4 -2' instead, but it did not fix the issue. -- Happy hacking Petter Reinholdtsen

Processed: Re: Bug#1086353: apache-opennlp: FTBFS: autobuilder hangs

Processing control commands: > tags -1 + confirmed Bug #1086353 [src:apache-opennlp] apache-opennlp: FTBFS: autobuilder hangs Added tag(s) confirmed. -- 1086353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1086353: apache-opennlp: FTBFS: autobuilder hangs

Control: tags -1 + confirmed On 10/30/24 13:15, Santiago Vila wrote: [INFO] --- [INFO]  T E S T S [INFO] --- E: Build killed with signal TERM after 60 minutes of inactivity ---

Bug#1075979: molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

Control: tags -1 + patch Missing libopenmpi-dev build-dep. diff '--color=auto' -ru molds-0.3.1.orig/debian/control molds-0.3.1/debian/control --- molds-0.3.1.orig/debian/control 2014-10-26 20:08:12.0 +0100 +++ molds-0.3.1/debian/control 2024-11-07 01:52:07.607924186 +0100 @@ -3,7 +3,

Processed: Re: Bug#1075979: molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

Processing control commands: > tags -1 + patch Bug #1075979 [src:molds] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory Added tag(s) patch. -- 1075979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075979 Debian Bug Tracking Sy

Bug#1074879: marked as done (checkpw: ftbfs with GCC-14)

Your message dated Thu, 07 Nov 2024 00:33:59 + with message-id and subject line Bug#1074879: fixed in checkpw 1.02-5 has caused the Debian Bug report #1074879, regarding checkpw: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: Bug#1057784: ifplugd: RM from trixie

Processing control commands: > clone -1 -2 Bug #1057784 [src:ifplugd] ifplugd: RM for trixie Bug 1057784 cloned as bug 1086877 > reassign -2 ftp.debian.org Bug #1086877 [src:ifplugd] ifplugd: RM for trixie Bug reassigned from package 'src:ifplugd' to 'ftp.debian.org'. No longer marked as found in

Bug#1057784: ifplugd: RM from trixie

Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: ifplugd -- RoQA; rc-buggy; unmaintained Control: affects -2 src:ifplugd Dear ftpmasters, On Wed, Jun 12, 2024 at 10:20:57PM +0200, Chris Hofstaedtler wrote: > Raising severity now, as netctl does not need ifplugd. p

Bug#1086003: marked as done (slurm-wlm: CVE-2024-48936)

Your message dated Wed, 06 Nov 2024 23:19:59 + with message-id and subject line Bug#1086003: fixed in slurm-wlm 24.05.4-1 has caused the Debian Bug report #1086003, regarding slurm-wlm: CVE-2024-48936 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1086809: marked as done (perl-base: reinstate Getopt::Long::Parser)

Your message dated Wed, 06 Nov 2024 21:36:21 + with message-id and subject line Bug#1086809: fixed in perl 5.40.0-7 has caused the Debian Bug report #1086809, regarding perl-base: reinstate Getopt::Long::Parser to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1086249: xapian-core FTBFS on i386 with gcc 14

On Tue, Oct 29, 2024 at 10:43:25PM +0200, Adrian Bunk wrote: > On Tue, Oct 29, 2024 at 06:32:43PM +, Olly Betts wrote: > > On Tue, Oct 29, 2024 at 07:48:32PM +0200, Adrian Bunk wrote: > > > ../../tests/unittest.cc:962:49: warning: left shift count >= width of > > > type [-Wshift-count-overflow

Bug#1086434: marked as done (coreboot: FTBFS on arm64: ‘return’ with no value, in function returning non-void [-Wreturn-mismatch])

Your message dated Wed, 06 Nov 2024 21:05:52 + with message-id and subject line Bug#1086434: fixed in coreboot 4.15~dfsg-5 has caused the Debian Bug report #1086434, regarding coreboot: FTBFS on arm64: ‘return’ with no value, in function returning non-void [-Wreturn-mismatch] to be marked as

Processed: affects 1086809

Processing commands for cont...@bugs.debian.org: > affects 1086809 ucf Bug #1086809 [perl-base] perl-base: reinstate Getopt::Long::Parser Added indication that 1086809 affects ucf > thanks Stopping processing here. Please contact me if you need assistance. -- 1086809: https://bugs.debian.org/cgi

Processed: Re: Bug#1086809: ucfq has undeclared dependency on a full perl installation: Getopt/Long/Parser.pm not present in perl-base

Processing control commands: > reassign -1 perl-base 5.40.0-6 Bug #1086809 [ucf] ucfq has undeclared dependency on a full perl installation: Getopt/Long/Parser.pm not present in perl-base Bug reassigned from package 'ucf' to 'perl-base'. No longer marked as found in versions ucf/3.0043+nmu1. Igno

Processed: closing 1086186

Processing commands for cont...@bugs.debian.org: > close 1086186 Bug #1086186 {Done: Robin Gustafsson } [src:php-opis-closure] php-opis-closure: Useless in Debian Bug 1086186 is already marked as done; not doing anything. > thanks Stopping processing here. Please contact me if you need assistanc

Bug#1086809: ucfq has undeclared dependency on a full perl installation: Getopt/Long/Parser.pm not present in perl-base

Control: reassign -1 perl-base 5.40.0-6 Control: retitle -1 perl-base: reinstate Getopt::Long::Parser On Wed, Nov 06, 2024 at 11:17:27AM +, Mark Hindley wrote: > Package: ucf > Version: 3.0043+nmu1 > Severity: serious > Justification: Undeclared dependency, breaks unrelated packages > ucfq us

Processed: closing 1086186

Processing commands for cont...@bugs.debian.org: > close 1086186 Bug #1086186 [src:php-opis-closure] php-opis-closure: Useless in Debian Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1086186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1

Bug#1086186: closing 1086186

close 1086186 thanks

Bug#1086186: Needed by my package

Hi William, On 11/6/24 10:13, William Desportes wrote: Hi Robin, The package php-zumba-json-serializer needs it. Can you re-consider this request? -- William Desportes Certainly. Thanks for letting me know. Let's keep it then. I realize I only considered regular (reverse) dependencies, not

Bug#1077312: python-omegaconf: remove build-dependency on pydevd

On Sat, Sep 14, 2024 at 09:32:53PM +0100, Julian Gilbey wrote: > severity 1077312 serious > thanks I've just uploaded 2.3.0-1.1 to DELAYED/7-days to fix this RC bug. debdiff attached. Best wishes, Julian diff -Nru python-omegaconf-2.3.0/debian/changelog python-omegaconf-2.3.0/debian/changelog

Bug#1075291: [patch, pending] mpg321: ftbfs with GCC-14

Hi Andreas, Am Wed, Nov 06, 2024 at 06:40:41PM +0100 schrieb Andreas Metzler: > Are you really convinced we would not be better off dropping this > from Debian instead? mpg321 is stone-dead upstream (last commit about 12 > years ago), alternatives with active upstream exist and are packaged. Well

Bug#1082200: python-bytecode FTBFS with Python 3.13

On Wed, Nov 06, 2024 at 10:04:55PM +0500, Andrey Rakhmatullin wrote: > Control: severity -1 serious > Control: tags -1 + wontfix > > This was requested to be removed from Debian some months ago. Just waiting for a blocking bug in python-omegaconf to be fixed. When I've got a chance, I'll do an N

Bug#1081027: src:sssd: flaky autopkgtest: spawn id exp3 not open

Hi On 06-11-2024 07:43, Michael Prokop wrote: Paul, do you know what could be the best option to reproduce the behavior of https://ci.debian.net/ (locally)? Because the problem seems to be environment specific, no one seems to have been able to reproduce it on salsa so far. :-/ As reported, it

Processed: tagging 1086748

Processing commands for cont...@bugs.debian.org: > tags 1086748 + ftbfs Bug #1086748 [src:easyeffects] easyeffects: FTBFS on armel: error: static assertion failed: static_assert(std::atomic::is_always_lock_free) Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need

Processed: forcibly merging 1084230 1082985

Processing commands for cont...@bugs.debian.org: > forcemerge 1084230 1082985 Bug #1084230 [xvfb] xvfb: please consider disabling libunwind, at least on armhf Bug #1082985 [xvfb] chatty: fails to build on armhf Severity set to 'important' from 'serious' Added indication that 1082985 affects src:g

Processed: found 1082379 in 6.4.2-6

Processing commands for cont...@bugs.debian.org: > found 1082379 6.4.2-6 Bug #1082379 [src:puma] puma: CVE-2024-45614 Marked as found in versions puma/6.4.2-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 1082379: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1085354: marked as pending in mbedtls

Control: tag -1 pending Hello, Bug #1085354 in mbedtls 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/debian-iot-team/mbedtls/-/commit/183514cadb0d2602f98780ad

Processed: reassign 1082985 to xvfb

Processing commands for cont...@bugs.debian.org: > reassign 1082985 xvfb Bug #1082985 [src:chatty] chatty: fails to build on armhf Bug reassigned from package 'src:chatty' to 'xvfb'. No longer marked as found in versions chatty/0.8.5-1. Ignoring request to alter fixed versions of bug #1082985 to t

Bug#1075291: [patch, pending] mpg321: ftbfs with GCC-14

On 2024-11-06 Andreas Tille wrote: > Control: tags -1 patch > Control: tags -1 pending > Thanks > Hi, > this package came up as a candidate for the Bug of the Week[1]. > I've commited a patch[2] for this bug and will file an ITS bug > soon to get permission to maintain this package in Debian > M

Bug#1058364: python-etcd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Hi, thanks a lot. BTW, since the package is team maintained you can always feel free to do a team upload. Kind regards and thanks again for your very welcome help Andreas. -- https://fam-tille.de

Bug#1084828: marked as done (epics-base: FTBFS (requires network interfaces))

Your message dated Wed, 06 Nov 2024 17:19:15 + with message-id and subject line Bug#1084828: fixed in epics-base 7.0.8.1+dfsg1-3 has caused the Debian Bug report #1084828, regarding epics-base: FTBFS (requires network interfaces) to be marked as done. This means that you claim that the proble

Processed: Re: Bug#1082200: python-bytecode FTBFS with Python 3.13

Processing control commands: > severity -1 serious Bug #1082200 [src:python-bytecode] python-bytecode FTBFS with Python 3.13 Severity set to 'serious' from 'normal' > tags -1 + wontfix Bug #1082200 [src:python-bytecode] python-bytecode FTBFS with Python 3.13 Added tag(s) wontfix. -- 1082200: htt

Bug#1082985: [Debian-on-mobile-maintainers] Bug#1082985: Bug#1082985: chatty: fails to build on armhf

control: forcemerge 1084230 1082985 Hi Jeremy, On Wed, Nov 06, 2024 at 10:28:37AM -0500, Jeremy Bícha wrote: > Control: affects 1084230 src:chatty > > On Tue, Oct 8, 2024 at 9:25 AM Guido Günther wrote: > > The test fails with > > > > (process:1144): Gtk-WARNING **: 08:49:35.088: Failed to open

Processed (with 1 error): Re: [Debian-on-mobile-maintainers] Bug#1082985: Bug#1082985: chatty: fails to build on armhf

Processing control commands: > forcemerge 1084230 1082985 Bug #1084230 [xvfb] xvfb: please consider disabling libunwind, at least on armhf Unable to merge bugs because: package of #1082985 is 'src:chatty' not 'xvfb' Failed to forcibly merge 1084230: Did not alter merged bugs. -- 1082985: https:

Bug#1086552: marked as done (mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame)

Your message dated Wed, 06 Nov 2024 16:51:22 + with message-id and subject line Bug#1086552: fixed in mutter 47.1-4 has caused the Debian Bug report #1086552, regarding mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame to be marked as done. This means t

Processed: Re: Bug#1086807: live-build: weekly live testing images not generated

Processing control commands: > severity 1086807 normal Bug #1086807 [live-build] live-build: weekly live testing images not generated Severity set to 'normal' from 'serious' > retitle 1086807 Weekly images 2024-11-04 not generated Bug #1086807 [live-build] live-build: weekly live testing images no

Bug#1086834: elkcode: FTBFS on arm64: Nonexistent include directory ‘/usr/lib/x86_64-linux-gnu/openmpi/lib’

Source: elkcode Version: 9.6.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: debian-...@lists.debian.org Usertags: arm64 During a rebuild of all packages in sid, this package failed to build on arm64. On amd64 it builds correctly. It seems that the build uses /usr/lib/x86_

Processed: Bug#1085354 marked as pending in mbedtls

Processing control commands: > tag -1 pending Bug #1085354 [src:mbedtls] mbedtls FTBFS on arm64 with gcc 14 Added tag(s) pending. -- 1085354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1078531: python-mp-api: packaging for new upstream release

Hi Drew, Now that python3-maggma is available in unstable, I took the liberty of preparing python-mp-api for the new upstream release. I don't have write permissions on debichem-team, so I forked the project at https://salsa.debian.org/lolando/python-mp-api and updated the packaging according

Processed: Re: Bug#1086551: ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0)

Processing control commands: > tags 1086551 +fixed-upstream Bug #1086551 [ansible-core] ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0) Added tag(s) fixed-upstream. -- 1086551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086551 Debian Bug Tracking System Co

Bug#1086551: ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0)

Control: tags 1086551 +fixed-upstream 在 11/1/2024 6:06 AM, Simon McVittie 写道: Package: ansible-core Version: 2.17.5-4 Severity: grave Tags: upstream Justification: renders package unusable Forwarded: https://github.com/ansible/ansible/issues/84217 X-Debbugs-Cc: python-resolve...@packages.debian.

Bug#1082985: [Debian-on-mobile-maintainers] Bug#1082985: chatty: fails to build on armhf

Control: affects 1084230 src:chatty On Tue, Oct 8, 2024 at 9:25 AM Guido Günther wrote: > The test fails with > > (process:1144): Gtk-WARNING **: 08:49:35.088: Failed to open display > > and no other output. How is libspelling involved? This sounds like a duplicate of https://bugs.debian.org/108

Bug#1079398: fscacher: FTBFS: test_memoize_path_dir fails

Control: severity 1079398 important 在 8/23/2024 2:18 PM, Yaroslav Halchenko 写道: Hi Boyuan Thanks for the report! We had similar fails in the past upstream https://github.com/search?q=repo%3Acon%2Ffscacher+test_memoize_path_dir&type=issues but insofar it was flaky and we failed to reliably repr

Processed: Re: Bug#1079398: fscacher: FTBFS: test_memoize_path_dir fails

Processing control commands: > severity 1079398 important Bug #1079398 [src:fscacher] fscacher: FTBFS: test_memoize_path_dir fails Severity set to 'important' from 'grave' -- 1079398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079398 Debian Bug Tracking System Contact ow...@bugs.debian.o

Processed: burrow: FTBFS on riscv64: undefined: syscall.Dup2

Processing commands for cont...@bugs.debian.org: > owner 1086799 ! Bug #1086799 [src:burrow] burrow: FTBFS on riscv64: undefined: syscall.Dup2 Owner recorded as Santiago Vila . > thanks Stopping processing here. Please contact me if you need assistance. -- 1086799: https://bugs.debian.org/cgi-bi

Processed: Bug#1085450 marked as pending in sbuild

Processing control commands: > tag -1 pending Bug #1085450 [src:sbuild] mmdebootstrap: sbuild autopkgtest for unshare backend fails Added tag(s) pending. -- 1085450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1085354: closed by Debian FTP Masters (reply to Andrea Pappacoda ) (Bug#1085354: fixed in mbedtls 3.6.2-2)

Control: reopen -1 On Wed, Nov 06, 2024 at 12:21:04PM +, Debian Bug Tracking System wrote: >... > mbedtls (3.6.2-2) unstable; urgency=medium > . >* d/patches: fix builds with GCC 14. >... That didn't work: https://buildd.debian.org/status/package.php?p=mbedtls&suite=sid > Upstream migh

Bug#1080464: marked as done (Fix feature check for clang-19+)

Your message dated Wed, 06 Nov 2024 11:19:56 + with message-id and subject line Bug#1080464: fixed in xtensor 0.25.0-2 has caused the Debian Bug report #1080464, regarding Fix feature check for clang-19+ to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: affects 1086750

Processing commands for cont...@bugs.debian.org: > affects 1086750 grub-installer Bug #1086750 [src:grub] grub-installer still uses old grub-legacy Added indication that 1086750 affects grub-installer > thanks Stopping processing here. Please contact me if you need assistance. -- 1086750: https:

Processed: Re: Bug#1085354 closed by Debian FTP Masters (reply to Andrea Pappacoda ) (Bug#1085354: fixed in mbedtls 3.6.2-2)

Processing control commands: > reopen -1 Bug #1085354 {Done: Andrea Pappacoda } [src:mbedtls] mbedtls FTBFS on arm64 with gcc 14 '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 longer mar

Bug#1085354: closed by Debian FTP Masters (reply to Andrea Pappacoda ) (Bug#1085354: fixed in mbedtls 3.6.2-2)

On 06 nov. 2024 14:39, Adrian Bunk wrote: > Control: reopen -1 > > On Wed, Nov 06, 2024 at 12:21:04PM +, Debian Bug Tracking System wrote: >>... >> mbedtls (3.6.2-2) unstable; urgency=medium >> . >>* d/patches: fix builds with GCC 14. >>... > > That didn't work: > https://buildd.debian.

Bug#1085450: marked as pending in sbuild

Control: tag -1 pending Hello, Bug #1085450 in sbuild 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/debian/sbuild/-/commit/1a068dfa94038233ec9b85e066c645ad634

Bug#1086807: live-build: weekly live testing images not generated

Package: live-build Version: 2024.11.04 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: ldoct...@gmail.com Dear Maintainer, When opening https://cdimage.debian.org/images/weekly-live-builds/amd64/iso- hybrid/, instead of finding the weekly live images I find

Bug#1086807: live-build: weekly live testing images not generated

Control: severity 1086807 normal Control: retitle 1086807 Weekly images 2024-11-04 not generated Hello Leandro, On 06/11/2024 11:26, Leandro Doctors wrote: When opening https://cdimage.debian.org/images/weekly-live-builds/amd64/iso- hybrid/, instead of finding the weekly live images I find log

Bug#1086809: ucfq has undeclared dependency on a full perl installation: Getopt/Long/Parser.pm not present in perl-base

Package: ucf Version: 3.0043+nmu1 Severity: serious Justification: Undeclared dependency, breaks unrelated packages Dear Maintainer, ucfq uses the perl module Getopt/Long/Parser.pm[1]. In perl 5-40 (which bundled Getopt-Long 2.57) this module has been split to a separate file [2]. Relying on the

Bug#1085354: Upstream patch available

Hi Emilio, On Wed Nov 6, 2024 at 10:39 AM CET, Emilio Pozuelo Monfort wrote: On Wed, 23 Oct 2024 16:02:06 +0200 marillat wrote: Hi, Upstream patch: https://github.com/openwrt/openwrt/pull/15479/commits/a41747ac8e824b5cb9ed6874a688a4d5a578e10c This is blocking the mbedtls transition. Can yo

Bug#1086835: groonga: FTBFS: cannot stat './html/_static/webpack-macros.html': No such file or directory

Source: groonga Version: 14.0.5+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs During a rebuild of all packages in sid, groonga failed to build from source on both amd64 and arm64 with the following error message: /usr/bin/install: cannot stat './html/_static/webpack-macros.

Processed: remove grub-legacy support

Processing control commands: > block 1086750 by -1 Bug #1086750 [src:grub] grub-installer still uses old grub-legacy 1086750 was not blocked by any bugs. 1086750 was not blocking any bugs. Added blocking bug(s) of 1086750: 1086840 -- 1086750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108

Bug#1086840: remove grub-legacy support

Source: grub-installer Version: 1.203 Severity: serious Control: block 1086750 by -1 We finally want to get rid of grub-legacy in Debian. It's now (in sid) only a transistional package depending on grub-pc. There's MR!20 [0] by Pascal Homburg which completely removes the grub-legacy parts of it.

Bug#1085354: marked as done (mbedtls FTBFS on arm64 with gcc 14)

Your message dated Wed, 06 Nov 2024 12:19:33 + with message-id and subject line Bug#1085354: fixed in mbedtls 3.6.2-2 has caused the Debian Bug report #1085354, regarding mbedtls FTBFS on arm64 with gcc 14 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1084301: [Pkg-javascript-devel] Bug#1084301: moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1

Hi! On 05/11/2024 06:20, Jérémy Lal wrote: Le sam. 2 nov. 2024 à 21:09, Martina Ferrari > a écrit : I was planning to do that, but then I saw that Jérémy Lal from the js team had made big modifications to the package (to avoid this problem altogether I think,

Processed: tagging 1086836, tagging 1086754, tagging 1055447, tagging 1086645, tagging 1033761, tagging 1033528

Processing commands for cont...@bugs.debian.org: > tags 1086836 + sid trixie Bug #1086836 [src:rust-inflector] project is dead - successor seems to be cruet Added tag(s) trixie and sid. > tags 1086754 + sid trixie Bug #1086754 {Done: Emmanuel Bourg } [jameica-datasource] jameica-datasource - buil

Processed: bug 1086836 is forwarded to https://github.com/whatisinternet/Inflector/issues/83

Processing commands for cont...@bugs.debian.org: > forwarded 1086836 https://github.com/whatisinternet/Inflector/issues/83 Bug #1086836 [src:rust-inflector] project is dead - successor seems to be cruet Set Bug forwarded-to-address to 'https://github.com/whatisinternet/Inflector/issues/83'. > tha

Bug#1086799: marked as pending in burrow

Control: tag -1 pending Hello, Bug #1086799 in burrow 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/burrow/-/commit/8ffdd434bce4084251292b5e9

Processed: Bug#1086799 marked as pending in burrow

Processing control commands: > tag -1 pending Bug #1086799 [src:burrow] burrow: FTBFS on riscv64: undefined: syscall.Dup2 Added tag(s) pending. -- 1086799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1086799: marked as done (burrow: FTBFS on riscv64: undefined: syscall.Dup2)

Your message dated Wed, 06 Nov 2024 13:49:06 + with message-id and subject line Bug#1086799: fixed in burrow 1.2.1-4 has caused the Debian Bug report #1086799, regarding burrow: FTBFS on riscv64: undefined: syscall.Dup2 to be marked as done. This means that you claim that the problem has been

Bug#1085505: marked as done (petsc: Current Petsc packages incompatible with openmpi 5.x in sid)

Your message dated Wed, 6 Nov 2024 10:42:02 +0100 with message-id <1ca08008-51c2-49a3-8d3d-c36f9585a...@debian.org> and subject line Re: petsc: Current Petsc packages incompatible with openmpi 5.x in sid has caused the Debian Bug report #1085505, regarding petsc: Current Petsc packages incompatibl

Bug#1086766: kimap FTBFS with the nocheck build profile: missing files

On Tuesday, November 5, 2024 9:48:17 AM CET Helmut Grohne wrote: > kimap fails to build from source when enabling the nocheck build > > profile. A build ends as follows: > |dh_install > | > | dh_install: warning: Cannot find (any matches for) > | "usr/include/KF5/KIMAPTest/kimaptest/fakeserve

Bug#1086783: kxmlrpcclient FTBFS with nocheck build profile: missing symbols

On Tuesday, November 5, 2024 8:45:35 PM CET Helmut Grohne wrote: > Source: kxmlrpcclient > Version: 5.115.0-2 > Severity: serious > Justification: nocheck ftbfs is serious since trixie > Tags: ftbfs trixie sid > > Hi, > > kxmlrpcclient fails to build from source in unstable when enabling the > >

Bug#1085354: Upstream patch available

Hi Andrea, On Wed, 23 Oct 2024 16:02:06 +0200 marillat wrote: Hi, Upstream patch: https://github.com/openwrt/openwrt/pull/15479/commits/a41747ac8e824b5cb9ed6874a688a4d5a578e10c This is blocking the mbedtls transition. Can you take a look at the patch? Cheers, Emilio

Bug#1069486: marked as done (priv-wrapper: FTBFS on armhf: 1: [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure!)

Your message dated Wed, 06 Nov 2024 09:19:55 + with message-id and subject line Bug#1069486: fixed in priv-wrapper 1.0.1-4 has caused the Debian Bug report #1069486, regarding priv-wrapper: FTBFS on armhf: 1: [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure! to be marked as done.

Bug#1086186: Needed by my package

Hi Robin, The package php-zumba-json-serializer needs it. Can you re-consider this request? -- William Desportes

Bug#1058364: python-etcd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Hi Andreas Tille, On Thu, 8 Feb 2024 10:33:11 +0100 Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I've fixed the issue reported in the bug in Git. However, Salsa CI > shows another issue[1]: > > if _is_instance_mock(spec): > > raise InvalidSpecError(f'Cannot spec a Mock object. [obj