Bug#1072425: k3b: FTBFS with ffmpeg 7.0: k3bf fmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’ xt’ {aka ‘struct AVCodecContext’} has n o m

Le 1 août 2024 00:39:05 GMT+02:00, Diederik de Haas a écrit : >On dinsdag 23 juli 2024 17:56:34 CEST you wrote: >> > during a rebuild of the reverse dependencies for the transition to >> > ffmpeg 7.0, your package failed to build >> >> In the upstream git repo there are 2 commits on 2024-04-1

Bug#1076487: marked as done (src:php-deepcopy: fails to migrate to testing for too long: uploader built arch:all binary)

Your message dated Thu, 01 Aug 2024 06:19:49 + with message-id and subject line Bug#1076487: fixed in php-deepcopy 1.12.0-1.1 has caused the Debian Bug report #1076487, regarding src:php-deepcopy: fails to migrate to testing for too long: uploader built arch:all binary to be marked as done.

Bug#1077186: marked as done (FTBFS: Could not find a package configuration file provided by "lxqt-build-tools")

Your message dated Thu, 01 Aug 2024 06:04:24 + with message-id and subject line Bug#1077186: fixed in lxqt-build-tools 2.0.0+really0.13.0-1 has caused the Debian Bug report #1077186, regarding FTBFS: Could not find a package configuration file provided by "lxqt-build-tools" to be marked as do

Bug#1077715: gcc-13-cross-ports ftbfs building the loong64 cross compilers

Package: src:gcc-13-cross-ports Version: 16 Severity: serious Tags: sid trixie X-Debbugs-CC: debian-loonga...@lists.debian.org gcc-13-cross-ports ftbfs building the loong64 cross compilers: [...] collect2: error: ld returned 1 exit status make[7]: *** [Makefile:998: libgcc_s.so] Error 1 make[7]:

Bug#1057780: marked as done (gdb-minimal provides gdb, without providing all the features in gdb)

Your message dated Thu, 01 Aug 2024 05:50:35 + with message-id and subject line Bug#1057780: fixed in gdb 15.1-1 has caused the Debian Bug report #1057780, regarding gdb-minimal provides gdb, without providing all the features in gdb to be marked as done. This means that you claim that the pr

Bug#1075356: marked as done (pacparser: ftbfs with GCC-14)

Your message dated Thu, 01 Aug 2024 05:35:21 + with message-id and subject line Bug#1075356: fixed in pacparser 1.4.5-2 has caused the Debian Bug report #1075356, regarding pacparser: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1068782: Bug#1071322: News on those issues?

Hi Jeremy, On Sun, Jun 30, 2024 at 02:47:41PM +0200, Salvatore Bonaccorso wrote: > Hi Jeremy, > > On Mon, Jun 17, 2024 at 04:31:04PM -0400, Jeremy T. Bouse wrote: > > Upstream had been MIA for years; its last release was in 2010. It appears > > he has finally returned, but I haven't had time to d

Bug#1058191: marked as done (pprofile: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

Your message dated Thu, 01 Aug 2024 03:20:22 + with message-id and subject line Bug#1058191: fixed in pprofile 2.1.0-2 has caused the Debian Bug report #1058191, regarding pprofile: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParse

Bug#1076426: marked as done (boost1.83: autopkgtest regression with CMake 3.30+)

Your message dated Thu, 01 Aug 2024 02:40:25 + with message-id and subject line Bug#1076426: fixed in boost1.83 1.83.0-3.1 has caused the Debian Bug report #1076426, regarding boost1.83: autopkgtest regression with CMake 3.30+ to be marked as done. This means that you claim that the problem h

Bug#1056100: marked as done (boost1.83: Boost.Signals2 causes FTBFS)

Your message dated Thu, 01 Aug 2024 02:40:25 + with message-id and subject line Bug#1056100: fixed in boost1.83 1.83.0-3.1 has caused the Debian Bug report #1056100, regarding boost1.83: Boost.Signals2 causes FTBFS to be marked as done. This means that you claim that the problem has been deal

Processed: raising severity, python3-distutils is removed

Processing commands for cont...@bugs.debian.org: > severity 1062657 serious Bug #1062657 [faiss] Faiss needs to be migrated away from using distutils Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062657: https://bugs.debi

Processed: block 1076692 with 1056100, tagging 1056100, tagging 1076426

Processing commands for cont...@bugs.debian.org: > block 1076692 with 1056100 Bug #1076692 [src:swift-im] swift-im: FTBFS with miniupnpc 2.2.8 1076692 was blocked by: 1056100 1076692 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1076692 to the same blocks previously s

Processed: tagging 1076692

Processing commands for cont...@bugs.debian.org: > tags 1076692 + pending Bug #1076692 [src:swift-im] swift-im: FTBFS with miniupnpc 2.2.8 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076692: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Bug#1077454: [Debian-med-packaging] Bug#1077454: bioperl-run: t/SABlastPlus.t failure

Le Tue, Jul 30, 2024 at 10:19:32PM +0200, Étienne Mollier a écrit : > Control: forwarded -1 https://github.com/bioperl/bioperl-run/issues/62 > The test includes several calls to the makeblastdb command, > through various "factories" (in the sense of design patterns). > My impression is that the t

Processed: pyroma: Source code depends on removed python3-distutils

Processing control commands: > forwarded -1 https://github.com/regebro/pyroma/issues/104 Bug #1077701 [src:pyroma] pyroma: Source code depends on removed python3-distutils Set Bug forwarded-to-address to 'https://github.com/regebro/pyroma/issues/104'. -- 1077701: https://bugs.debian.org/cgi-bin

Bug#1077701: pyroma: Source code depends on removed python3-distutils

Source: pyroma Version: 4.2-2 Severity: grave Control: forwarded -1 https://github.com/regebro/pyroma/issues/104 Dear Debian pyroma package maintainer, This project still depends on the distutuils module, which has been removed from Python 3.12. An upstream issue is available at https://github.co

Bug#1075246: marked as done (mactelnet: ftbfs with GCC-14)

Your message dated Thu, 01 Aug 2024 00:24:55 + with message-id and subject line Bug#1075246: fixed in mactelnet 0.5.2-1 has caused the Debian Bug report #1075246, regarding mactelnet: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1077690: marked as done (gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386)

Your message dated Wed, 31 Jul 2024 23:35:17 + with message-id and subject line Bug#1077690: fixed in gtk4 4.14.4+ds-7 has caused the Debian Bug report #1077690, regarding gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386 to be marked as done. This means

Bug#1075143: marked as done (libappimage: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 23:35:27 + with message-id and subject line Bug#1075143: fixed in libappimage 1.0.4-5-4 has caused the Debian Bug report #1075143, regarding libappimage: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1077690: gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386

On Thu, 01 Aug 2024 at 01:47:57 +0300, Adrian Bunk wrote: > Sorry, I got that backwards. > > LDFLAGS were missing with dpkg 1.22.9 in gtk4 4.14.4+ds-4 but are now back. OK, that's consistent with the log I was looking at. None of gtk4's extra LDFLAGS are actually critical to the build, so it isn'

Bug#1077690: gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386

On Wed, Jul 31, 2024 at 11:21:51PM +0100, Simon McVittie wrote: > On Wed, 31 Jul 2024 at 23:02:31 +0100, Simon McVittie wrote: > > On Thu, 01 Aug 2024 at 00:19:45 +0300, Adrian Bunk wrote: > > > Comparing build logs the "-Wl,-z,defs -Wl,-O1" is also gone > > > (not only on i386) > > Are you sure t

Bug#1072425: k3b: FTBFS with ffmpeg 7.0: k3bf fmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’ xt’ {aka ‘struct AVCodecContext’} has n o m

On dinsdag 23 juli 2024 17:56:34 CEST you wrote: > > during a rebuild of the reverse dependencies for the transition to > > ffmpeg 7.0, your package failed to build > > In the upstream git repo there are 2 commits on 2024-04-13 which probably do > fix the FTBFS issue, but don't make it compatible

Bug#1077690: marked as pending in gtk4

Control: tag -1 pending Hello, Bug #1077690 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/1a46546210d73c0c523ed32070c6d3e3b4a

Processed: Bug#1077690 marked as pending in gtk4

Processing control commands: > tag -1 pending Bug #1077690 [src:gtk4] gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386 Added tag(s) pending. -- 1077690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077690 Debian Bug Tracking System Contact ow...@bugs

Bug#1077552: marked as done (debsigs: Tries to access Internet during build)

Your message dated Wed, 31 Jul 2024 22:19:12 + with message-id and subject line Bug#1077552: fixed in debsigs 0.2.1-1 has caused the Debian Bug report #1077552, regarding debsigs: Tries to access Internet during build to be marked as done. This means that you claim that the problem has been d

Bug#1077690: gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386

On Wed, 31 Jul 2024 at 23:02:31 +0100, Simon McVittie wrote: > On Thu, 01 Aug 2024 at 00:19:45 +0300, Adrian Bunk wrote: > > Comparing build logs the "-Wl,-z,defs -Wl,-O1" is also gone > > (not only on i386) Are you sure those LDFLAGS are missing? I can see the -Wl,-O1 showing up in the build log

Bug#1077690: gtk4: intended CFLAGS/LDFLAGS no longer set, leading to test failures and FTBFS on i386

Source: gtk4 Version: 4.14.4-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Adrian Bunk (Redirecting from a reply to #1077675 since this is a different bug) On Thu, 01 Aug 2024 at 00:19:45 +0300, Adrian Bunk wrote: > O

Processed: Re: Bug#1072625: nvidia-cuda-toolkit: switch to llvm 17

Processing control commands: > severity -1 important Bug #1072625 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: switch to llvm 17 Severity set to 'important' from 'serious' -- 1072625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072625 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1072625: nvidia-cuda-toolkit: switch to llvm 17

Control: severity -1 important On 30/07/2024 11.56, Emilio Pozuelo Monfort wrote: On Wed, 05 Jun 2024 12:32:03 +0200 Emilio Pozuelo Monfort wrote: nvidia-cuda-toolkit currently uses llvm 15, but that version is going to be removed as we also have 16, 17 and 18 in sid. Please switch to a newe

Bug#1077439: Fwd: Bug#1077439: latex-cjk-japanese-wadalab: FTBFS: wftodm.c:57:1: error: return type defaults to ‘int’ [-Wimplicit-int]

Control: tags -1 + help On 31.07.2024 10:48, Danai SAE-HAN (韓達耐) wrote: Hi Danai, When compiling wftodm.c from the latex-cjk-japanese-wadalab package, I get a bunch of warnings with GCC 13 (see also below Lucas' output). To me, these seems just fairly benign warnings based on deprecated C89 c

Processed: Re: Fwd: Bug#1077439: latex-cjk-japanese-wadalab: FTBFS: wftodm.c:57:1: error: return type defaults to ‘int’ [-Wimplicit-int]

Processing control commands: > tags -1 + help Bug #1077439 [src:latex-cjk-japanese-wadalab] latex-cjk-japanese-wadalab: FTBFS: wftodm.c:57:1: error: return type defaults to ‘int’ [-Wimplicit-int] Added tag(s) help. -- 1077439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077439 Debian Bug

Bug#1077675: gtk4: FTBFS: gtk / notify test fails: gtk_calendar_set_month: assertion 'date != NULL' failed

On Wed, Jul 31, 2024 at 08:56:55PM +0100, Simon McVittie wrote: >,,, > The good news is that this seems to be the only test failure, on all the > architectures that have been attempted so far. The bad news is that this is not true on i386, apparently the -ffloat-store is gone there. Comparing bui

Processed: linuxcnc: FTBFS: Fontconfig error: No writable cache directories

Processing commands for cont...@bugs.debian.org: > # tidying up > reassign 1076893 texlive-lang-french Bug #1076893 {Done: Petter Reinholdtsen } [src:linuxcnc] linuxcnc: FTBFS: Fontconfig error: No writable cache directories Bug reassigned from package 'src:linuxcnc' to 'texlive-lang-french'. No

Processed: found 1074430 in 4.8.1-1

Processing commands for cont...@bugs.debian.org: > found 1074430 4.8.1-1 Bug #1074430 {Done: Alexandre Rossi } [src:adminer] adminer: CVE-2023-45196 CVE-2023-45195 Marked as found in versions adminer/4.8.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 107443

Bug#1075383: marked as done (phast: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 20:43:50 + with message-id and subject line Bug#1075383: fixed in phast 1.6+dfsg-6 has caused the Debian Bug report #1075383, regarding phast: 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#1075237: marked as done (lpr: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 20:42:30 + with message-id and subject line Bug#1075237: fixed in lpr 1:2008.05.17.3+nmu3 has caused the Debian Bug report #1075237, regarding lpr: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1077672: marked as done (libgtk-3-0t64: Cannot install due conflict with libgtk-3-0:arm64 1:3.24.38-2~deb12u1+rpt6+rpi1)

Your message dated Wed, 31 Jul 2024 16:38:03 -0400 with message-id and subject line Re: Bug#1077672: libgtk-3-0t64: Cannot install due conflict with libgtk-3-0:arm64 1:3.24.38-2~deb12u1+rpt6+rpi1 has caused the Debian Bug report #1077672, regarding libgtk-3-0t64: Cannot install due conflict with

Processed: Bug#1075383 marked as pending in phast

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

Bug#1075383: marked as pending in phast

Control: tag -1 pending Hello, Bug #1075383 in phast 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/med-team/phast/-/commit/e910cab1b768e97311b92f2cc30b1675fd9

Bug#1077675: marked as done (gtk4: FTBFS: gtk / notify test fails: gtk_calendar_set_month: assertion 'date != NULL' failed)

Your message dated Wed, 31 Jul 2024 16:24:17 -0400 with message-id and subject line Re: Bug#1077675: gtk4: FTBFS: gtk / notify test fails: gtk_calendar_set_month: assertion 'date != NULL' failed has caused the Debian Bug report #1077675, regarding gtk4: FTBFS: gtk / notify test fails: gtk_calend

Bug#1076893: marked as done (linuxcnc: FTBFS: Fontconfig error: No writable cache directories)

Your message dated Wed, 31 Jul 2024 22:21:57 +0200 with message-id and subject line Re: linuxcnc: FTBFS: Fontconfig error: No writable cache directories has caused the Debian Bug report #1076893, regarding linuxcnc: FTBFS: Fontconfig error: No writable cache directories to be marked as done. Thi

Bug#1077675: gtk4: FTBFS: gtk / notify test fails: gtk_calendar_set_month: assertion 'date != NULL' failed

Source: gtk4 Version: 4.14.4-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The new version of gtk4 in unstable failed to build on all architectures so far: > == 140/668 ===

Bug#1077672: libgtk-3-0t64: Cannot install due conflict with libgtk-3-0:arm64 1:3.24.38-2~deb12u1+rpt6+rpi1

Package: libgtk-3-0t64 Version: /var/cache/apt/archives/libgtk-3-0t64_3.24.43-1_arm64.deb Severity: critical Justification: breaks the whole system X-Debbugs-Cc: mikegreen10...@gmail.com, mikegreen10...@gmail.com After trying to install xfce4-screenshooter which claims to depend on this package,

Bug#1060469: marked as done (intel-hdcp: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 19:20:14 + with message-id and subject line Bug#1060469: fixed in intel-hdcp 20.3.0-1.1 has caused the Debian Bug report #1060469, regarding intel-hdcp: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the prob

Bug#1052643: marked as done (intel-hdcp FTBFS when systemd.pc changes systemdsystemunitdir)

Your message dated Wed, 31 Jul 2024 19:20:14 + with message-id and subject line Bug#1052643: fixed in intel-hdcp 20.3.0-1.1 has caused the Debian Bug report #1052643, regarding intel-hdcp FTBFS when systemd.pc changes systemdsystemunitdir to be marked as done. This means that you claim that t

Processed: Re: Bug#1077075: mutter: Monitors not detected on Wayland after upgrade on Debian 13/testing

Processing commands for cont...@bugs.debian.org: > forwarded 1077075 https://gitlab.gnome.org/GNOME/mutter/-/issues/3605 Bug #1077075 [mutter-common] mutter: Monitors not detected on Wayland after upgrade on Debian 13/testing Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/mutter

Bug#1039883: linux: ext4 corruption with symlinks

On Tue, 2024-07-09 at 19:32 +0200, Ben Hutchings wrote: > Control: tag -1 patch fixed-upstream > > A fix was applied to the ext4 "dev" branch earlier today: > > > I would sti

Bug#1077287: marked as done (libgtk-4-1 v4.14: missing dependency on libgles2 (maybe there are alternatives) on at least i386)

Your message dated Wed, 31 Jul 2024 18:50:09 + with message-id and subject line Bug#1077287: fixed in gtk4 4.14.4+ds-5 has caused the Debian Bug report #1077287, regarding libgtk-4-1 v4.14: missing dependency on libgles2 (maybe there are alternatives) on at least i386 to be marked as done. T

Bug#1077192: marked as done (gtk4: Test regression in 4.14 on s390x: assertion failure in 3 gsk tests)

Your message dated Wed, 31 Jul 2024 18:50:09 + with message-id and subject line Bug#1077192: fixed in gtk4 4.14.4+ds-5 has caused the Debian Bug report #1077192, regarding gtk4: Test regression in 4.14 on s390x: assertion failure in 3 gsk tests to be marked as done. This means that you claim

Bug#1077181: marked as done (gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault)

Your message dated Wed, 31 Jul 2024 18:50:09 + with message-id and subject line Bug#1077181: fixed in gtk4 4.14.4+ds-5 has caused the Debian Bug report #1077181, regarding gtk4: FTBFS on riscv64: a11y/text, a11y/textview tests segfault to be marked as done. This means that you claim that the

Processed: Re: snakemake: FTBFS failing tests

Processing control commands: > retitle -1 pytools.persistent_dict fails in multithread Bug #1076925 [src:snakemake] snakemake: FTBFS: failing tests Changed Bug title to 'pytools.persistent_dict fails in multithread' from 'snakemake: FTBFS: failing tests'. > reassign -1 python3-pytools Bug #107692

Bug#1060469: marked as done (intel-hdcp: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 18:49:18 + with message-id and subject line Bug#1060469: fixed in freeipa 4.11.1-2.1 has caused the Debian Bug report #1060469, regarding intel-hdcp: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem

Bug#1076925: snakemake: FTBFS failing tests

Control: retitle -1 pytools.persistent_dict fails in multithread Control: reassign -1 python3-pytools Control: affects -1 snakemake Control: tags -1 fixed-upstream Control: severity -1 normal (for pytools - it's still RC for snakemake) This was probably introduced when pytools.persistent_dict sta

Bug#1063754: fat-modules: SD corruption upon opening file on Linux desktop

On Tue, 2024-06-04 at 06:51 -0400, Bud Heal wrote: > I filled up the (micro)SDs, including the current one I have been scanning > into, the one that I set aside as probably defective and the pair I bought > for testing. I will append the bash script. I appreciate that you've scripted this, but you

Bug#1077075: mutter: Monitors not detected on Wayland after upgrade on Debian 13/testing

Done, here is the upstream bug report: https://gitlab.gnome.org/GNOME/mutter/-/issues/3605 Thanks On Sat, Jul 27, 2024 at 9:06 AM Jeremy Bícha wrote: > On Thu, Jul 25, 2024 at 3:39 PM Fabrice Quenneville > wrote: > > Package: mutter-common > > Version: 46.3.1-2 > > Severity: critical > > Justi

Bug#1060560: marked as done (spice-vdagent: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 18:19:51 + with message-id and subject line Bug#1060560: fixed in spice-vdagent 0.22.1-4.1 has caused the Debian Bug report #1060560, regarding spice-vdagent: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that th

Bug#1074991: marked as done (gf2x: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 17:49:38 + with message-id and subject line Bug#1074991: fixed in gf2x 1.3.0-3 has caused the Debian Bug report #1074991, regarding gf2x: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1075453: marked as done (ruamel.yaml.clib: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 17:35:16 + with message-id and subject line Bug#1075453: fixed in ruamel.yaml.clib 0.2.8+ds-2 has caused the Debian Bug report #1075453, regarding ruamel.yaml.clib: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been

Bug#1075453: marked as pending in ruamel.yaml.clib

Control: tag -1 pending Hello, Bug #1075453 in ruamel.yaml.clib 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/ruamel.yaml.clib/-/commit/0

Processed: Bug#1075453 marked as pending in ruamel.yaml.clib

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

Bug#1071640: mitmproxy: Error prevents the program to starts

Hello, > starting the program leads to an unrecoverable error, a backtrace is > printed on the console and the error is: > > "ModuleNotFoundError: No module named 'blinker._saferef'" I can confirm this problem. -- Regards/Mit freundlichen Grüßen Christian Weiske -=≡ Geeking around in the nam

Bug#1071640: mitmproxy blinker problem

Using blinker 1.7.0 seems to help (but Debian testing+unstable ships 1.8.2): https://github.com/UnMars/Prolific-Joiner/issues/22 Upstream removed blinker from their dependencies: https://github.com/mitmproxy/mitmproxy/pull/5528 https://github.com/mitmproxy/mitmproxy/commit/f4dc2f2cfdb40e04022e4deb

Bug#1070254: marked as done (ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)')

Your message dated Wed, 31 Jul 2024 19:04:04 +0200 with message-id <3312651.44csPzL39Z@grummly> and subject line Re: Bug#1070254: ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)' has caused the Debian Bug report #1070254, regarding

Bug#1070254: ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)'

Hi, Le jeudi 2 mai 2024, 21:34:24 CEST Patrick Franz a écrit : > Hej, > > Am Donnerstag, 2. Mai 2024, 15:24:07 CEST schrieb Helmut Grohne: > > Source: ktp-text-ui > > Version: 22.12.3-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source (but built successfully in

Bug#1075704: marked as done (yorick-yeti: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 16:51:49 + with message-id and subject line Bug#1075704: fixed in yorick-yeti 6.4.0-2 has caused the Debian Bug report #1075704, regarding yorick-yeti: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1000061: cfengine3: depends on obsolete pcre3 library

> Am 18.12.23 um 15:14 schrieb Bastian Germann: > > On Fri, 18 Aug 2023 12:01:17 +0200 Bastian Germann wrote: > > > cfengine3 is a key package and requires pcre, so this has to be fixed. > > > > Upstream claims that this is fixed with 3.24.0. On Tue, Mar 12, 2024 at 03:58:12PM +0100, Christoph M

Bug#1067266: marked as done (python-bonsai: FTBFS: dh_missing: error: missing files, aborting)

Your message dated Wed, 31 Jul 2024 16:36:39 + with message-id and subject line Bug#1067266: fixed in python-bonsai 1.5.3+ds-1 has caused the Debian Bug report #1067266, regarding python-bonsai: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim

Bug#1067912: marked as done (Update Build-Depends for the time64 library renames)

Your message dated Wed, 31 Jul 2024 16:19:46 + with message-id and subject line Bug#1067912: fixed in nitrokey-app 1.4.2-1.1 has caused the Debian Bug report #1067912, regarding Update Build-Depends for the time64 library renames to be marked as done. This means that you claim that the proble

Bug#1060573: marked as done (nitrokey-app: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 16:19:46 + with message-id and subject line Bug#1060573: fixed in nitrokey-app 1.4.2-1.1 has caused the Debian Bug report #1060573, regarding nitrokey-app: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the p

Bug#1065386: marked as done (anytun: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 16:04:33 + with message-id and subject line Bug#1065386: fixed in golang-github-containers-toolbox 0.0.99.3+git20230118+446d7bfdef6a-2.1 has caused the Debian Bug report #1065386, regarding anytun: Please switch Build-Depends to systemd-dev to be marked as

Bug#1035782: nuitka: Nuitka should hard-depend on an earlier python version and thus be uninstallable

Hello Stuart, Nuitka supports 3.12 for a while now, and will support 3.13 at release time. We will be able to keep it this way. I think I messed up with my sponsor such that currently the stable package didn't make it through my automatic checks, but I think it should be good to go I will check t

Bug#1077426: fp16: FTBFS: bitcasts.cc:14:60: error: ‘setfill’ is not a member of ‘std’

Control: tags -1 + patch I believe the following patch will solve the issue. As far as I can tell, gcc 14 is a bit more picky and these include lines will solve it. diff --git a/debian/patches/ftbfs-gcc-14.patch b/debian/patches/ftbfs-gcc-14.patch new file mode 100644 index 000..877b161 ---

Processed: Re: fp16: FTBFS: bitcasts.cc:14:60: error: ‘setfill’ is not a member of ‘std’

Processing control commands: > tags -1 + patch Bug #1077426 [src:fp16] fp16: FTBFS: bitcasts.cc:14:60: error: ‘setfill’ is not a member of ‘std’ Added tag(s) patch. -- 1077426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077426 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1077666: Build-Depends: libllvmlibc--dev is missing

Source: iwyu Version: 8.22-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: a...@kernel.org Dear Maintainer, I've tried building iwyu from source after installing the all the build dependencies of the package, and failed.

Bug#1065386: marked as done (anytun: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 31 Jul 2024 14:35:37 + with message-id and subject line Bug#1065386: fixed in anytun 0.3.8-1.1 has caused the Debian Bug report #1065386, regarding anytun: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem has b

Bug#1067266: marked as pending in python-bonsai

Control: tag -1 pending Hello, Bug #1067266 in python-bonsai reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-bonsai/-/commit/5398988

Processed: Bug#1067266 marked as pending in python-bonsai

Processing control commands: > tag -1 pending Bug #1067266 [src:python-bonsai] python-bonsai: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. -- 1067266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067266 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#1072425: marked as pending in k3b

Control: tag -1 pending Hello, Bug #1072425 in k3b 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/qt-kde-team/kde/k3b/-/commit/da2e99075a65fc290b4fc06f8f20f643

Processed: Bug#1072425 marked as pending in k3b

Processing control commands: > tag -1 pending Bug #1072425 {Done: Aurélien COUDERC } [src:k3b] k3b: FTBFS with ffmpeg 7.0: k3bffmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’ Added tag(s) pending. -- 1072425: https://bugs.debian.org

Bug#1072425: marked as done (k3b: FTBFS with ffmpeg 7.0: k3bffmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’)

Your message dated Wed, 31 Jul 2024 13:52:16 + with message-id and subject line Bug#1072425: fixed in k3b 24.05.2-1 has caused the Debian Bug report #1072425, regarding k3b: FTBFS with ffmpeg 7.0: k3bffmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member

Bug#1077650: Binary build patching insanity

Hey Samuel! On Wed, Jul 31, 2024 at 07:55:32PM +0900, Samuel Henrique wrote: > >> Severity: serious > >Could you please clarify why you think this severity is appropriate? >I'm tempted to lower it. It's *very* different from normal packaging practice, just about the opposite of the "principle of

Bug#1073450: ncbi-acc-download: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

On Sun, 16 Jun 2024 15:22:57 +0200 Lucas Nussbaum wrote: > Source: ncbi-acc-download > Version: 0.2.8-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240615 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your p

Bug#1075429: marked as done (qt6-webengine: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 12:36:51 + with message-id and subject line Bug#1075429: fixed in qt6-webengine 6.6.2+dfsg-5 has caused the Debian Bug report #1075429, regarding qt6-webengine: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been deal

Bug#1035782: nuitka: Nuitka should hard-depend on an earlier python version and thus be uninstallable

Hi Kay I see that an updated nuitka has still not made it to Debian and so nuitka has not been available in testing (or working in unstable) for over 15 months. Do you have a firm plan for a nuitka upload? Would it make sense for nuitka to be team maintained so that others can work on the p

Bug#1076818: marked as done (mayavi2: FTBFS: NameError: name 'build_src' is not defined)

Your message dated Wed, 31 Jul 2024 11:50:00 + with message-id and subject line Bug#1076818: fixed in mayavi2 4.8.2-1 has caused the Debian Bug report #1076818, regarding mayavi2: FTBFS: NameError: name 'build_src' is not defined to be marked as done. This means that you claim that the proble

Bug#1075260: marked as done (mayavi2: ftbfs with GCC-14)

Your message dated Wed, 31 Jul 2024 11:50:00 + with message-id and subject line Bug#1075260: fixed in mayavi2 4.8.2-1 has caused the Debian Bug report #1075260, regarding mayavi2: 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#1074586: marked as done (mayavi2:FTBFS:build failure（UnicodeDecodeError）)

Your message dated Wed, 31 Jul 2024 11:50:00 + with message-id and subject line Bug#1074586: fixed in mayavi2 4.8.2-1 has caused the Debian Bug report #1074586, regarding mayavi2:FTBFS:build failure（UnicodeDecodeError） to be marked as done. This means that you claim that the problem has been

Bug#1074586: marked as pending in mayavi2

Control: tag -1 pending Hello, Bug #1074586 in mayavi2 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/mayavi2/-/commit/350f0de1efe2fda59fa

Bug#1076818: marked as pending in mayavi2

Control: tag -1 pending Hello, Bug #1076818 in mayavi2 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/mayavi2/-/commit/350f0de1efe2fda59fa

Processed: Bug#1076818 marked as pending in mayavi2

Processing control commands: > tag -1 pending Bug #1076818 [src:mayavi2] mayavi2: FTBFS: NameError: name 'build_src' is not defined Added tag(s) pending. -- 1076818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1074586 marked as pending in mayavi2

Processing control commands: > tag -1 pending Bug #1074586 [src:mayavi2] mayavi2:FTBFS:build failure（UnicodeDecodeError） Added tag(s) pending. -- 1074586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1074669: marked as done (python3-simpletal: FTBFS: ModuleNotFoundError: No module named 'imp')

Your message dated Wed, 31 Jul 2024 11:34:50 + with message-id and subject line Bug#1074669: fixed in python3-simpletal 5.2-4 has caused the Debian Bug report #1074669, regarding python3-simpletal: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you cla

Bug#1074669: marked as pending in python3-simpletal

Control: tag -1 pending Hello, Bug #1074669 in python3-simpletal 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/python3-simpletal/-/commit

Processed: Bug#1074669 marked as pending in python3-simpletal

Processing control commands: > tag -1 pending Bug #1074669 [src:python3-simpletal] python3-simpletal: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1074669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074669 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#1077650: Binary build patching insanity

Hello Steve, > Severity: serious Could you please clarify why you think this severity is appropriate? I'm tempted to lower it. > I'm maintaining a distro derived from Debian, and we've just tripped > over issues in building the curl package with more patches applied. I take it this happened bec

Bug#1077650: Binary build patching insanity

Source: curl Version: 7.88.1-10+deb12u5 Severity: serious Hi, I'm maintaining a distro derived from Debian, and we've just tripped over issues in building the curl package with more patches applied. I've just found the code in debian/rules that calls quilt at build time to mess around with the so

Bug#1077303: marked as done (crowdsec FTBFS fixup for docker transition)

Your message dated Wed, 31 Jul 2024 10:19:23 + with message-id and subject line Bug#1077303: fixed in crowdsec 1.4.6-9 has caused the Debian Bug report #1077303, regarding crowdsec FTBFS fixup for docker transition to be marked as done. This means that you claim that the problem has been deal

Processed: closing 1073396

Processing commands for cont...@bugs.debian.org: > close 1073396 Bug #1073396 [src:python-urllib3] python-urllib3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you nee

Bug#1076973: marked as done (rust-pkcs8: FTBFS: dh-rust-built-using returned exit code 1)

Your message dated Wed, 31 Jul 2024 11:30:07 +0200 with message-id <172241820747.1714821.3565296761034611...@cairon.jones.dk> and subject line Re: Bug#1076972: rust-ed25519: FTBFS: dh-rust-built-using returned exit code 1 has caused the Debian Bug report #1076972, regarding rust-pkcs8: FTBFS: dh-r

Bug#1076972: marked as done (rust-ed25519: FTBFS: dh-rust-built-using returned exit code 1)

Your message dated Wed, 31 Jul 2024 11:30:07 +0200 with message-id <172241820747.1714821.3565296761034611...@cairon.jones.dk> and subject line Re: Bug#1076972: rust-ed25519: FTBFS: dh-rust-built-using returned exit code 1 has caused the Debian Bug report #1076972, regarding rust-ed25519: FTBFS: dh

  1   2   >