Bug#1064232: marked as done (rust-axum: Failing autopkgtests)

Your message dated Sat, 27 Jul 2024 08:36:05 +0200 with message-id <172206216583.818760.6567404842564833...@cairon.jones.dk> and subject line Re: Bug#1064232: autopkgtest now pass has caused the Debian Bug report #1064232, regarding rust-axum: Failing autopkgtests to be marked as done. This means

Processed: Accepted curl 8.9.0-2 (source) into unstable

Processing commands for cont...@bugs.debian.org: > reopen 1077197 Bug #1077197 [libcurl4-openssl-dev] libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements Bug 1077197 is not marked as done; doing nothing. > reopen 1077190 Bug #1077190 [src:curl] curl: pkgconf --cflags libcurl

Processed: Accepted curl 8.9.0-2 (source) into unstable

Processing commands for cont...@bugs.debian.org: > reopen 1077197 Bug #1077197 {Done: Carlos Henrique Lima Melara } [libcurl4-openssl-dev] libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements 'reopen' may be inappropriate when a bug has been closed with a version; all fixed v

Bug#1077190: Accepted curl 8.9.0-2 (source) into unstable

Hi, Am 27.07.24 um 08:00 schrieb Rene Engelhard: b) even more, pbuilder disables the install of recommends. That means builds inside pbuilder still will fail. This doesn't even work in sbuild (and thus the buildds). After I gave back libreoffice I got https://buildd.debian.org/status/fetch

Bug#1077190: Accepted curl 8.9.0-2 (source) into unstable

Hi, Am 27.07.24 um 08:00 schrieb Rene Engelhard: a) Is this needed for anything using liburls .pc. A pure --cflags now needs those. Even when not doing static linking. Recommends here is wrong. This needs to be a Depends. b) even more, pbuilder disables the install of recommends. That means

Bug#1077190: Accepted curl 8.9.0-2 (source) into unstable

reopen 1077197 reopen 1077190 thanks Hi, Am 27.07.24 um 06:34 schrieb Debian FTP Masters:    * debian/control: make libcurl*-dev packages Recommends -dev packages. (Closes: #1077197, #1077190) This is not  going to work. a) Is this needed for anything using liburls .pc. A pure --cf

Bug#1077227: libcwiid1: Unintentionally libcwiid1t64 --> libcwiid1 changes ?

Package: libcwiid1 Version: 0.6.91-8 Severity: serious Dear Maintainer, Would be nice why the libcwiid1t64 has been renamed to libcwiid1 whithouht a soname change. Do you have forgot to include changes done for the time_t transition ? , | cwiid (0.6.91-7.1) unstable; urgency=medium | | *

Bug#1077224: python3-utidylib - depends on cruft package

Package: python-utidylib Version: 0.10-1 Severity: serious python3-utidylib depends on libtidy5deb0 which is no longer built by the tidy-html5 source package. It appears to have been replaced by libtidy58. Since this is an arch all package, and a hard-coded depdency this cannot be fixed by a bin

Bug#1076904: [Pkg-javascript-devel] Bug#1076904: pkg-js-tools: FTBFS: help2man: can't get `--version' info from ./tools/debcheck-node-repo

On 7/27/24 07:15, Guillem Jover wrote: Control: reopen -1 Control: notfixed -1 dpkg/1.22.9 Control: affect -1 = src:pkg-js-tools Control: retitle -1 dpkg-dev: Make fragments lack internal dpkg_lazy_eval macros Control: tags -1 = On Fri, 2024-07-26 at 15:21:16 +0200, Santiago Vila wrote: unmerge

Bug#1077223: python3-tidylib - depends on cruft package

Package: python-tidylib Version: 0.3.3~dfsg-7 Severity: serious python3-tidylib depends on libtidy5deb0 which is no longer built by the tidy-html5 source package. It appears to have been replaced by libtidy58. Since this is an arch all package, and a hard-coded depdency this cannot be fixed by a

Bug#1077197: marked as done (libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements)

Your message dated Sat, 27 Jul 2024 04:34:20 + with message-id and subject line Bug#1077197: fixed in curl 8.9.0-2 has caused the Debian Bug report #1077197, regarding libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements to be marked as done. This means that you claim tha

Bug#1077190: marked as done (curl: pkgconf --cflags libcurl failing due to missing deps)

Your message dated Sat, 27 Jul 2024 04:34:20 + with message-id and subject line Bug#1077190: fixed in curl 8.9.0-2 has caused the Debian Bug report #1077190, regarding curl: pkgconf --cflags libcurl failing due to missing deps to be marked as done. This means that you claim that the problem h

Bug#1076904: marked as done (dpkg-dev: Make fragments lack internal dpkg_lazy_eval macros)

Your message dated Sat, 27 Jul 2024 04:19:13 + with message-id and subject line Bug#1076904: fixed in dpkg 1.22.10 has caused the Debian Bug report #1076904, regarding dpkg-dev: Make fragments lack internal dpkg_lazy_eval macros to be marked as done. This means that you claim that the problem

Bug#1077197: marked as pending in curl

Control: tag -1 pending Hello, Bug #1077197 in curl 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/curl/-/commit/29e7a9b8a0375be8ad28b5e3b52fa68a6e0b085

Processed: Bug#1077190 marked as pending in curl

Processing control commands: > tag -1 pending Bug #1077190 [src:curl] curl: pkgconf --cflags libcurl failing due to missing deps Added tag(s) pending. -- 1077190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1077197 marked as pending in curl

Processing control commands: > tag -1 pending Bug #1077197 [libcurl4-openssl-dev] libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements Added tag(s) pending. -- 1077197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077197 Debian Bug Tracking System Contact ow...@bugs.de

Bug#1077190: marked as pending in curl

Control: tag -1 pending Hello, Bug #1077190 in curl 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/curl/-/commit/29e7a9b8a0375be8ad28b5e3b52fa68a6e0b085

Bug#1074378: bind9: Bind9 SEGFAULT when enable DLZ with samba

Thanks, I've now uploaded the fixed package to both unstable and bookworm-security. The bookworm-security package needs to be processed by the security team, so it might take a little bit longer than the version in unstable which should be building or already built. Ondrej -- Ondřej Surý (He/Hi

Bug#1074378: marked as done (bind9: Bind9 SEGFAULT when enable DLZ with samba)

Your message dated Sat, 27 Jul 2024 03:19:26 + with message-id and subject line Bug#1074378: fixed in bind9 1:9.20.0-2 has caused the Debian Bug report #1074378, regarding bind9: Bind9 SEGFAULT when enable DLZ with samba to be marked as done. This means that you claim that the problem has bee

Processed: Re: Bug#1076904: [Pkg-javascript-devel] Bug#1076904: pkg-js-tools: FTBFS: help2man: can't get `--version' info from ./tools/debcheck-node-repo

Processing control commands: > reopen -1 Bug #1076904 {Done: Santiago Vila } [dpkg-dev] pkg-js-tools: FTBFS: help2man: can't get `--version' info from ./tools/debcheck-node-repo 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you m

Bug#1076904: [Pkg-javascript-devel] Bug#1076904: pkg-js-tools: FTBFS: help2man: can't get `--version' info from ./tools/debcheck-node-repo

Control: reopen -1 Control: notfixed -1 dpkg/1.22.9 Control: affect -1 = src:pkg-js-tools Control: retitle -1 dpkg-dev: Make fragments lack internal dpkg_lazy_eval macros Control: tags -1 = On Fri, 2024-07-26 at 15:21:16 +0200, Santiago Vila wrote: > unmerge 1076904 > thanks > Hi. I can indeed re

Bug#1074378: bind9: Bind9 SEGFAULT when enable DLZ with samba

On Fri, 26 Jul 2024 14:28:12 +0200 Bernhard Schmidt wrote: ... > > Can anyone confirm the workaround from the Samba BZ setting > LDB_MODULES_DISABLE_DEEPBIND=true ? > > yes, the workaround has enabled my system to work again after the upgrade to 1:9.18.28-1~deb12u1

Bug#1074985: marked as done (genders: ftbfs with GCC-14)

Your message dated Sat, 27 Jul 2024 03:05:10 + with message-id and subject line Bug#1074985: fixed in genders 1.27-3-2 has caused the Debian Bug report #1074985, regarding genders: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1074378: bind9: Bind9 SEGFAULT when enable DLZ with samba

Ok, here's the patch: From 6b2ffa8216bcf65f3b20b14171d9732d9583e6f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Sat, 27 Jul 2024 04:57:36 +0200 Subject: [PATCH] Disable RTLD_DEEPBIND in Samba DLZ module When RTLD_DEEPBIND is enabled in the LDB modules inside the Samb

Bug#1077209: marked as done (python-orjson: CVE-2024-27454)

Your message dated Sat, 27 Jul 2024 02:44:56 + with message-id and subject line Bug#1077209: fixed in python-orjson 3.9.15-1 has caused the Debian Bug report #1077209, regarding python-orjson: CVE-2024-27454 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1077123: marked as done (srv-el: needs rebuild against dh-elpa >=2.1.5)

Your message dated Sat, 27 Jul 2024 11:28:29 +0900 with message-id <87ttgblgaa@melete.silentflame.com> and subject line done has caused the Debian Bug report #1077123, regarding srv-el: needs rebuild against dh-elpa >=2.1.5 to be marked as done. This means that you claim that the problem has b

Bug#1077131: marked as done (xcscope-el: needs rebuild against dh-elpa >=2.1.5)

Your message dated Sat, 27 Jul 2024 11:28:48 +0900 with message-id <87plqzlg9r@melete.silentflame.com> and subject line done has caused the Debian Bug report #1077131, regarding xcscope-el: needs rebuild against dh-elpa >=2.1.5 to be marked as done. This means that you claim that the problem h

Bug#1075481: marked as done (ruby-tokyocabinet: ftbfs with GCC-14)

Your message dated Sat, 27 Jul 2024 01:51:48 + with message-id and subject line Bug#1075481: fixed in ruby-tokyocabinet 1.31-7 has caused the Debian Bug report #1075481, regarding ruby-tokyocabinet: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been de

Bug#1074798: a56: diff for NMU version 1.3+dfsg-10.2

Control: tags 1074798 + patch Control: tags 1074798 + pending Dear maintainer, I've prepared an NMU for a56 (versioned as 1.3+dfsg-10.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. These changes are also available on the "build-clean" branch of

Processed: a56: diff for NMU version 1.3+dfsg-10.2

Processing control commands: > tags 1074798 + patch Bug #1074798 [src:a56] a56: ftbfs with GCC-14 Added tag(s) patch. > tags 1074798 + pending Bug #1074798 [src:a56] a56: ftbfs with GCC-14 Added tag(s) pending. -- 1074798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074798 Debian Bug Trac

Processed: Re: Bug#1077181: gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault

Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/6490 Bug #1077181 [src:gtk4] gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gtk/-/issues/6490'. > tags -1 + pending Bug #107718

Bug#1077181: gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault

Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/6490 Control: tags -1 + pending On Fri, 26 Jul 2024 at 15:55:15 +0100, Simon McVittie wrote: > This might be related to https://gitlab.gnome.org/GNOME/gtk/-/issues/6490 > which reported that these same tests were segfaulting on Ubun

Bug#1076372: Re.: linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels

Hi Salvatore, Am 26.07.24 um 23:09 schrieb Salvatore Bonaccorso: Now that you were able to pinpoint two versions which are very close together, would you be able to bisect the changes between 6.3.5 and 6.3.7 to find the breaking commit upstream in that 6.3.y series? not without spending more t

Bug#1077181: marked as pending in gtk4

Control: tag -1 pending Hello, Bug #1077181 in gtk4 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/gnome-team/gtk4/-/commit/490bcaee93502a95afb54d503d543ea8e06

Processed: Bug#1077181 marked as pending in gtk4

Processing control commands: > tag -1 pending Bug #1077181 [src:gtk4] gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault Added tag(s) pending. -- 1077181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#1074898: marked as done (cwiid: ftbfs with GCC-14)

Your message dated Sat, 27 Jul 2024 00:00:16 + with message-id and subject line Bug#1074898: fixed in cwiid 0.6.91-8 has caused the Debian Bug report #1074898, regarding cwiid: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1074963: marked as done (foma: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 23:48:59 + with message-id and subject line Bug#1074963: fixed in foma 1:0.10.0+s311.20240712-1 has caused the Debian Bug report #1074963, regarding foma: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with

Processed: update bug

Processing commands for cont...@bugs.debian.org: > forwarded 1075177 https://github.com/ueno/libkkc/issues/47 Bug #1075177 [src:libkkc] libkkc: ftbfs with GCC-14 Changed Bug forwarded-to-address to 'https://github.com/ueno/libkkc/issues/47' from 'https://github.com/ueno/libkkc/issues/47 thanks'.

Bug#1075301: mutt: ftbfs with GCC-14

On 2024-07-03 12:37:27 +, Matthias Klose wrote: > gcc -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc\" > -DBINDIR=\"/usr/bin\" -DMUTTLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H=1 > -I. -I../.. -I. -I../.. -I../../imap-Wdate-time -D_FORTIFY_SOURCE=2 > -isystem /usr/include/mit-

Bug#1076259: marked as done (progress-linux-gnome-desktop: Depends on extensions that aren't compatible with GNOME Shell 46)

Your message dated Fri, 26 Jul 2024 23:05:01 + with message-id and subject line Bug#1076259: fixed in progress-linux-metapackages 20221002-15 has caused the Debian Bug report #1076259, regarding progress-linux-gnome-desktop: Depends on extensions that aren't compatible with GNOME Shell 46 to

Bug#1052556: marked as done (bfh-gnome-desktop: Depends on extensions that aren't compatible with GNOME Shell 46)

Your message dated Fri, 26 Jul 2024 22:49:00 + with message-id and subject line Bug#1052556: fixed in bfh-metapackages 20211009-26 has caused the Debian Bug report #1052556, regarding bfh-gnome-desktop: Depends on extensions that aren't compatible with GNOME Shell 46 to be marked as done. Th

Bug#1077197: libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements

On Fri, 26 Jul 2024 19:03:58 +0300 Adrian Bunk wrote: Package: libcurl4-openssl-dev Version: 8.9.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Rene Engelhard Control: affects -1 libcurl4-gnutls-dev src:libreoffice $ pkgconf --cflags libcurl Package libidn2 was not found in the pkg-config sea

Processed: affects 1077197

Processing commands for cont...@bugs.debian.org: > affects 1077197 + src:network-manager Bug #1077197 [libcurl4-openssl-dev] libcurl4-openssl-dev: Insufficient dependencies for pkgconf requirements Added indication that 1077197 affects src:network-manager > thanks Stopping processing here. Pleas

Bug#1077073: marked as done (texlive-bin FTBFS on 32-bit with gcc 14)

Your message dated Fri, 26 Jul 2024 22:06:30 + with message-id and subject line Bug#1077073: fixed in texlive-bin 2024.20240313.70630+ds-4 has caused the Debian Bug report #1077073, regarding texlive-bin FTBFS on 32-bit with gcc 14 to be marked as done. This means that you claim that the prob

Bug#1076313: marked as done (scikit-build's autopkg tests fail with setuptools 70)

Your message dated Fri, 26 Jul 2024 22:05:43 + with message-id and subject line Bug#1076313: fixed in scikit-build 0.18.0-1 has caused the Debian Bug report #1076313, regarding scikit-build's autopkg tests fail with setuptools 70 to be marked as done. This means that you claim that the proble

Processed: Bug#1076313 marked as pending in scikit-build

Processing control commands: > tag -1 pending Bug #1076313 [src:scikit-build] scikit-build's autopkg tests fail with setuptools 70 Ignoring request to alter tags of bug #1076313 to the same tags previously set -- 1076313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076313 Debian Bug Trac

Bug#1076313: marked as pending in scikit-build

Control: tag -1 pending Hello, Bug #1076313 in scikit-build 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/scikit-build/-/commit/f4f165375

Bug#1075377: marked as done (perl-tk: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 21:35:13 + with message-id and subject line Bug#1075377: fixed in perl-tk 1:804.036+dfsg1-3 has caused the Debian Bug report #1075377, regarding perl-tk: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#1076372: Re.: linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels

Processing control commands: > tags -1 + moreinfo Bug #1076372 [src:linux] linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels Added tag(s) moreinfo. -- 1076372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076372 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1076372: Re.: linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels

Control: tags -1 + moreinfo Hi Stefan, On Fri, Jul 26, 2024 at 10:49:00AM +0200, Stefan wrote: > The complete sentence is: > > oldest non-working kernel is 6.3.7 (package linux-image-6.3.0-1-amd64), > 6.3.5 (latest version of package package linux-image-6.3.0-0-amd64) works. Now that you were a

Processed: found 1076372 in 6.3.7-1

Processing commands for cont...@bugs.debian.org: > found 1076372 6.3.7-1 Bug #1076372 [src:linux] linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels Ignoring request to alter found versions of bug #1076372 to the same values previously set > thanks Stopping processing her

Bug#1077209: python-orjson: CVE-2024-27454

Source: python-orjson Version: 3.9.14-3 Severity: grave Tags: security upstream Forwarded: https://github.com/ijl/orjson/issues/458 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for python-orjson. CVE-2024-27454[0]: | orjson.loads in orjson

Processed: affects 1074378

Processing commands for cont...@bugs.debian.org: > affects 1074378 + release.debian.org,security.debian.org Bug #1074378 [bind9] bind9: Bind9 SEGFAULT when enable DLZ with samba Added indication that 1074378 affects release.debian.org and security.debian.org > thanks Stopping processing here. Ple

Processed: libauthen-sasl-xs-perl: ftbfs with GCC-14; patch ready

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

Bug#1075146: libauthen-sasl-xs-perl: ftbfs with GCC-14; patch ready

Control: tags -1 + patch Hi, I pushed a patch[1] to salsa to proceed to targeted changes to the libauthen-sasl-xs-perl, but I'm not entirely confident touching a library that seems security sensitive. I'm notably feeling a bit bugged by the initial type discrepancy of a variable passed to an IV.

Processed: Bug#1075146 marked as pending in libauthen-sasl-xs-perl

Processing control commands: > tag -1 pending Bug #1075146 [src:libauthen-sasl-xs-perl] libauthen-sasl-xs-perl: ftbfs with GCC-14 Added tag(s) pending. -- 1075146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1075146: marked as pending in libauthen-sasl-xs-perl

Control: tag -1 pending Hello, Bug #1075146 in libauthen-sasl-xs-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/libauthen-sasl-

Bug#1076879: marked as pending in epcr

Hi Santiago, Santiago Vila, on 2024-07-25: > I see that you fixed this very quickly. Thanks! > > I just wanted to point out that this was really a bug in dpkg-dev: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076863 > > so in case you would like to continue to use some of > those vari

Bug#1077181: gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault

On Fri, 26 Jul 2024 at 15:55:17 +0100, Simon McVittie wrote: > On Fri, 26 Jul 2024 at 14:48:36 +0100, Simon McVittie wrote: > > On Fri, 26 Jul 2024 at 14:53:03 +0200, Matthias Geiger wrote: > > > The a11y tests just seem to segfault: > > > > > > 478/668 gtk:a11y / text

Processed: triage cython related bug

Processing commands for cont...@bugs.debian.org: > block 1075607 by 1077205 Bug #1075607 [src:unifrac] unifrac: ftbfs with GCC-14 1075607 was not blocked by any bugs. 1075607 was not blocking any bugs. Added blocking bug(s) of 1075607: 1077205 > thank you Stopping processing here. Please contact

Bug#1075158: marked as done (libcli: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 19:18:59 + with message-id and subject line Bug#1075158: fixed in libcli 1.10.7-2 has caused the Debian Bug report #1075158, regarding libcli: 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#1071778: marked as done (python-django-ca: FTBFS: failing tests)

Your message dated Fri, 26 Jul 2024 19:06:56 + with message-id and subject line Bug#1076654: Removed package(s) from unstable has caused the Debian Bug report #1071778, regarding python-django-ca: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been d

Bug#1066789: marked as done (pycoast: 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, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1066785: marked as done (python-pytest-lazy-fixture: 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, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding python-pytest-lazy-fixture: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3

Bug#1066784: marked as done (python-marshmallow-sqlalchemy: 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, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding python-marshmallow-sqlalchemy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.1

Bug#1066757: marked as done (prettytable: 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, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding prettytable: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned e

Bug#1063973: marked as done (python-marshmallow-sqlalchemy: autopkgtest regression with pytest 8)

Your message dated Fri, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding python-marshmallow-sqlalchemy: autopkgtest regression with pytest 8 to be marked as done. This means that you clai

Bug#1063957: marked as done (python-pytest-lazy-fixture: autopkgtest regression with pytest 8)

Your message dated Fri, 26 Jul 2024 19:05:45 + with message-id and subject line Bug#1076459: Removed package(s) from unstable has caused the Debian Bug report #1063957, regarding python-pytest-lazy-fixture: autopkgtest regression with pytest 8 to be marked as done. This means that you claim t

Bug#998940: marked as done (python-ooolib: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Fri, 26 Jul 2024 18:59:17 + with message-id and subject line Bug#1076014: Removed package(s) from unstable has caused the Debian Bug report #998940, regarding python-ooolib: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This mean

Bug#965794: marked as done (python-ooolib: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Fri, 26 Jul 2024 18:59:17 + with message-id and subject line Bug#1076014: Removed package(s) from unstable has caused the Debian Bug report #965794, regarding python-ooolib: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you

Bug#1052507: marked as done (azure-cosmos-python: upstream has moved to another repository)

Your message dated Fri, 26 Jul 2024 18:59:48 + with message-id and subject line Bug#1076059: Removed package(s) from unstable has caused the Debian Bug report #1052507, regarding azure-cosmos-python: upstream has moved to another repository to be marked as done. This means that you claim that

Bug#1024722: marked as done (davs2: Keep out of testing until it is used)

Your message dated Fri, 26 Jul 2024 18:58:38 + with message-id and subject line Bug#1075984: Removed package(s) from unstable has caused the Debian Bug report #1024722, regarding davs2: Keep out of testing until it is used to be marked as done. This means that you claim that the problem has b

Bug#1071817: marked as done (xavs2: FTBFS: source/common/vec/intrinsic_intra-pred.c:775:13: error: implicit declaration of function ‘memcpy’)

Your message dated Fri, 26 Jul 2024 18:57:49 + with message-id and subject line Bug#1075983: Removed package(s) from unstable has caused the Debian Bug report #1071817, regarding xavs2: FTBFS: source/common/vec/intrinsic_intra-pred.c:775:13: error: implicit declaration of function ‘memcpy’ to

Bug#1024723: marked as done (xavs2: do not release with bookworm)

Your message dated Fri, 26 Jul 2024 18:57:49 + with message-id and subject line Bug#1075983: Removed package(s) from unstable has caused the Debian Bug report #1024723, regarding xavs2: do not release with bookworm to be marked as done. This means that you claim that the problem has been deal

Bug#1075832: marked as done (tk-html3: Completely remove hv3 (and tk-html3), for good reasons)

Your message dated Fri, 26 Jul 2024 18:55:09 + with message-id and subject line Bug#1075846: Removed package(s) from unstable has caused the Debian Bug report #1075832, regarding tk-html3: Completely remove hv3 (and tk-html3), for good reasons to be marked as done. This means that you claim t

Bug#1058260: marked as done (python-ck: FTBFS: ModuleNotFoundError: No module named 'imp')

Your message dated Fri, 26 Jul 2024 18:56:13 + with message-id and subject line Bug#1075936: Removed package(s) from unstable has caused the Debian Bug report #1058260, regarding python-ck: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that

Bug#1035552: marked as done (sassphp: needs conversion to dh-php >= 4)

Your message dated Fri, 26 Jul 2024 18:52:39 + with message-id and subject line Bug#1075764: Removed package(s) from unstable has caused the Debian Bug report #1035552, regarding sassphp: needs conversion to dh-php >= 4 to be marked as done. This means that you claim that the problem has been

Bug#1020977: marked as done (FTBFS: *** DH_PHP_VERSIONS cannot be empty. Stop.)

Your message dated Fri, 26 Jul 2024 18:52:03 + with message-id and subject line Bug#1075763: Removed package(s) from unstable has caused the Debian Bug report #1020977, regarding FTBFS: *** DH_PHP_VERSIONS cannot be empty. Stop. to be marked as done. This means that you claim that the proble

Bug#1054736: marked as done (versiontools: FTBFS: make: *** [debian/rules:7: clean] Error 25)

Your message dated Fri, 26 Jul 2024 18:43:38 + with message-id and subject line Bug#1074527: Removed package(s) from unstable has caused the Debian Bug report #1054736, regarding versiontools: FTBFS: make: *** [debian/rules:7: clean] Error 25 to be marked as done. This means that you claim th

Bug#1067683: marked as done (FTBFS: error: implicit declaration of function ‘getmode’)

Your message dated Fri, 26 Jul 2024 18:42:08 + with message-id and subject line Bug#1072228: Removed package(s) from unstable has caused the Debian Bug report #1067683, regarding FTBFS: error: implicit declaration of function ‘getmode’ to be marked as done. This means that you claim that the

Bug#1065998: marked as done (versiontools: Please drop dependencies on python3-distutils)

Your message dated Fri, 26 Jul 2024 18:43:38 + with message-id and subject line Bug#1074527: Removed package(s) from unstable has caused the Debian Bug report #1065998, regarding versiontools: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that t

Bug#1056537: marked as done (versiontools autopkg tests fail with Python 3.12)

Your message dated Fri, 26 Jul 2024 18:43:38 + with message-id and subject line Bug#1074527: Removed package(s) from unstable has caused the Debian Bug report #1056537, regarding versiontools autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem

Bug#1074998: marked as done (gimp: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 18:35:33 + with message-id and subject line Bug#1074998: fixed in gimp 2.10.38-2 has caused the Debian Bug report #1074998, regarding gimp: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1073299: marked as done (debian package version 2.4.2 does not work in stable, and was not updated to 2.4.90 in testing and unstable.)

Your message dated Fri, 26 Jul 2024 18:34:01 + with message-id and subject line Bug#1070701: Removed package(s) from unstable has caused the Debian Bug report #1073299, regarding debian package version 2.4.2 does not work in stable, and was not updated to 2.4.90 in testing and unstable. to be

Bug#1019303: marked as done (librm0: library mismatch between roger-router and librm0)

Your message dated Fri, 26 Jul 2024 18:34:01 + with message-id and subject line Bug#1070701: Removed package(s) from unstable has caused the Debian Bug report #1019303, regarding librm0: library mismatch between roger-router and librm0 to be marked as done. This means that you claim that the

Processed: reassign 1077005 to dpkg-dev, reassign 1076932 to dpkg-dev, forcibly merging 1077005 1076932

Processing commands for cont...@bugs.debian.org: > reassign 1077005 dpkg-dev 1.22.8 Bug #1077005 [1076932] CFLAGS+=foo etc stopped working Warning: Unknown package '1076932' Bug reassigned from package '1076932' to 'dpkg-dev'. No longer marked as found in versions dpkg-dev. Ignoring request to alt

Processed (with 2 errors): Re: Bug#1077005: CFLAGS+=foo etc stopped working

Processing control commands: > reassign -1 1076932 dpkg-dev Bug #1077005 [dpkg-dev] CFLAGS+=foo etc stopped working Bug reassigned from package 'dpkg-dev' to '1076932'. Warning: Unknown package '1076932' Warning: Unknown package '1076932' No longer marked as found in versions dpkg/1.22.8. Warning:

Processed: Re: Bug#1076872: debian-reference: FTBFS: dh_install: warning: Cannot find (any matches for) "build/debian-reference.fr.pdf"

Processing commands for cont...@bugs.debian.org: > reassign 1076872 texlive-lang-french Bug #1076872 [src:debian-reference] debian-reference: FTBFS: dh_install: warning: Cannot find (any matches for) "build/debian-reference.fr.pdf" Bug reassigned from package 'src:debian-reference' to 'texlive-la

Bug#1076872: debian-reference: FTBFS: dh_install: warning: Cannot find (any matches for) "build/debian-reference.fr.pdf"

reassign 1076872 texlive-lang-french affects 1076872 + src:debian-reference found 1076872 2024.20240706-1 close 1076872 2024.20240706-2 thanks Hi. If I'm not mistaken, this was a bug in texlive-lang-french. If you build the package today in unstable, it would probably work. Thanks.

Bug#1075236: marked as done (lp-solve: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 18:08:50 + with message-id and subject line Bug#1075236: fixed in lp-solve 5.5.2.5-3 has caused the Debian Bug report #1075236, regarding lp-solve: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1076932: webdis: FTBFS: src/client.h:6:10: fatal error: http_parser.h: No such file or directory

El 26/7/24 a las 19:48, James McCoy escribió: CFLAGS += $(CPPFLAGS) export CFLAGS += -Isrc -Isrc/http-parser Maybe this package is trying to use the dpkg-provided build flags incorrectly, but I've seen this pattern in a number of places. Looks like #1077005. Please reassign + affects

Bug#1077203: ucspi-tcp: FTBFS with unshare

Package: src:ucspi-tcp Version: 1:0.88-10 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update

Processed: 1076986 affects qbs

Processing commands for cont...@bugs.debian.org: > affects 1076986 + src:qbs Bug #1076986 [qt6-base-dev] error: SSE register return with SSE2 disabled Added indication that 1076986 affects src:qbs > thanks Stopping processing here. Please contact me if you need assistance. -- 1076986: https://bu

Bug#1076932: webdis: FTBFS: src/client.h:6:10: fatal error: http_parser.h: No such file or directory

On Wed, Jul 24, 2024 at 12:50:20PM GMT, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: > > > [...] > debian/rules binary > dh binary >dh_update_autotools_config

Bug#1077190: curl: pkgconf --cflags libcurl failing due to missing deps

Source: curl Followup-For: Bug #1077190 X-Debbugs-Cc: tj.iam...@proton.me This is a result of upstream commit f057de5a1a which results in libcurl.pc having: Name: libcurl URL: https://curl.se/ Description: Library to transfer files with ftp, http, etc. Version: 8.9.0 Requires: Requires.private:

Processed: notfound 1072938 in 5.0.0+ds1-1

Processing commands for cont...@bugs.debian.org: > notfound 1072938 5.0.0+ds1-1 Bug #1072938 {Done: Alexandre Detiste } [src:jupyterhub] jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2) No longer marked as found in versions jupyterhub/5.0.0+ds1-1. > thanks Stopping processing here.

Processed: BTS housekeeping

Processing commands for cont...@bugs.debian.org: > forwarded 1075522 https://github.com/snapcore/snapd/pull/13959 Bug #1075522 [src:snapd] snapd: ftbfs with GCC-14 Set Bug forwarded-to-address to 'https://github.com/snapcore/snapd/pull/13959'. > tags 1075522 patch Bug #1075522 [src:snapd] snapd: f

Bug#1075455: marked as done (ruby-augeas: ftbfs with GCC-14)

Your message dated Fri, 26 Jul 2024 17:10:14 + with message-id and subject line Bug#1075455: fixed in ruby-augeas 1:0.5.0+gem-2 has caused the Debian Bug report #1075455, regarding ruby-augeas: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1076970: Debian bug #1076970 (napari FTBFS)

I had a look at this bug report. It seems the error comes from pydantic (pydantic code called by other parts of pydantic); it still occurs with the recent upload of pydantic 2.4.2. I tried doing a package for the newer upstream release (2.8.2) with a simple gbp import-orig --uscan (and refre

Bug#1077186: FTBFS: Could not find a package configuration file provided by "lxqt-build-tools"

Hi, On Fri, Jul 26, 2024 at 02:19:49PM +0100, Aurelien Jarno wrote: Source: lxqt-session Version: 1.4.0-1 Severity: serious Tags: ftbfs | ... | Could not find a package configuration file provided by "lxqt-build-tools" | (requested version 0.13.0) with any of the following names: | | l

  1   2   3   >