Bug#1066215: marked as done (soundmodem: FTBFS: kisspkt.c:762:9: error: implicit declaration of function ‘fchmod’ [-Werror=implicit-function-declaration])

Your message dated Mon, 25 Mar 2024 05:17:29 + with message-id and subject line Bug#1066215: fixed in soundmodem 0.20-7 has caused the Debian Bug report #1066215, regarding soundmodem: FTBFS: kisspkt.c:762:9: error: implicit declaration of function ‘fchmod’

Processed: Bug#1066215 marked as pending in soundmodem

Processing control commands: > tag -1 pending Bug #1066215 [src:soundmodem] soundmodem: FTBFS: kisspkt.c:762:9: error: implicit declaration of function ‘fchmod’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066215

Bug#1066215: marked as pending in soundmodem

Control: tag -1 pending Hello, Bug #1066215 in soundmodem 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:

Bug#1067630: fixed in emacs 1:29.3+1-1

On Mon, 25 Mar 2024 01:13:54 + Debian FTP Masters wrote: Source: emacs Source-Version: 1:29.3+1-1 Done: Rob Browning Should this issue be reopened or be cloned to backport fixes to Emacs-28 in Debian stable?

Processed: Re: emacs: release 29.3 fixes "several security vulnerabilities"

Processing control commands: > found -1 1:28.2+1-15 Bug #1067630 {Done: Rob Browning } [src:emacs] emacs: release 29.3 fixes "several security vulnerabilities" Marked as found in versions emacs/1:28.2+1-15. -- 1067630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067630 Debian Bug

Bug#1067630: emacs: release 29.3 fixes "several security vulnerabilities"

Control: found -1 1:28.2+1-15 On Sun, 24 Mar 2024 16:53:55 -0300 David Bremner wrote: ** Arbitrary Lisp code is no longer evaluated as part of turning on Org mode. This is for security reasons, to avoid evaluating malicious Lisp code. Emacs-28 in Debian 12 bookworm requires the fix as well.

Bug#1067630: marked as done (emacs: release 29.3 fixes "several security vulnerabilities")

Your message dated Mon, 25 Mar 2024 01:13:54 + with message-id and subject line Bug#1067630: fixed in emacs 1:29.3+1-1 has caused the Debian Bug report #1067630, regarding emacs: release 29.3 fixes "several security vulnerabilities" to be marked as done. This means that you claim that the

Bug#1067359: marked as done (rbldnsd: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1)

Your message dated Mon, 25 Mar 2024 01:55:52 + with message-id and subject line Bug#1067359: fixed in rbldnsd 1.0~20210120-3 has caused the Debian Bug report #1067359, regarding rbldnsd: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1 to be marked as done. This

Bug#1063971: marked as done (python-dateutil: autopkgtest regression with pytest 8)

Your message dated Sun, 24 Mar 2024 23:14:52 + with message-id and subject line Bug#1063971: fixed in python-dateutil 2.9.0-1 has caused the Debian Bug report #1063971, regarding python-dateutil: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the

Bug#1067604: marked as done (src:libcdk5: autopkgtest regression, tests the old version and more issues)

Your message dated Sun, 24 Mar 2024 22:47:35 + with message-id and subject line Bug#1067604: fixed in libcdk5 5.0.20230201-3 has caused the Debian Bug report #1067604, regarding src:libcdk5: autopkgtest regression, tests the old version and more issues to be marked as done. This means that

Bug#1067115: marked as done (gross: CVE-2023-52159)

Your message dated Mon, 25 Mar 2024 01:27:41 + with message-id and subject line Bug#1067115: fixed in gross 1.0.2-4.1 has caused the Debian Bug report #1067115, regarding gross: CVE-2023-52159 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1067491: time_t transition upgrade: failed systemctl call in preinst due to missing pre-dependencies

Thanks Wouter for reporting this and Michael for submitting a merge request for a potential fix! The libcrypto.so.3 is from the OpenSSL package. In your upgrade case it seems to be switching from libssl3 [i386] to libssl3t64 [i386]. Your MariaDB packages are amd64. This makes me wonder what is

Bug#1066983: monopd: Fails to start monopd.service

Sylvain Rochet wrote: > Actually, the main problem is /lib/systemd/system/monopd.socket which > set Accept=yes while monopd needs Accept=no (which is the default value). I wonder if monopd needs a systemd socket file at all and if we should disable the service after the installation. We have

Bug#1066198: marked as done (gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’ [-Werror=implicit-function-declaration])

Your message dated Mon, 25 Mar 2024 01:18:57 + with message-id and subject line Bug#1066198: fixed in gbatnav 1.0.4cvs20051004-7 has caused the Debian Bug report #1066198, regarding gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’

Processed: let these show up on buildd.d.o overview page

Processing commands for cont...@bugs.debian.org: > tags 883308 + ftbfs Bug #883308 [libseccomp2] libseccomp2 is missing support for ia64, alpha, sh4, sparc64, m68k Added tag(s) ftbfs. > tags 1067055 + ftbfs Bug #1067055 [src:openmpi] openmpi: error: implicit declaration of function

Bug#1066198: gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’ [-Werror=implicit-function-declaration]

Fixed. Patch as attachment. Description: Fix FTBFS due to -Werror=implicit-function-declaration Bug-Debian: https://bugs.debian.org/1066198 Author: Ying-Chun Liu (PaulLiu) Last-Update: 2024-03-25 Index: gbatnav-1.0.4cvs20051004/gbnserver/gbnserver.c

Processed: tagging 1067618, tagging 1067624, tagging 1067596, tagging 1067623, tagging 1067609, tagging 1067547 ...

Processing commands for cont...@bugs.debian.org: > tags 1067618 + sid trixie Bug #1067618 [src:whitedune] FTBFS: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration] Added tag(s) trixie and sid. > tags 1067624 + sid trixie Bug

Bug#1063969: marked as done (pytest-sugar: autopkgtest regression with pytest 8)

Your message dated Mon, 25 Mar 2024 00:15:35 +0100 with message-id and subject line Re: Accepted pytest-sugar 1.0.0-1 (source) into unstable has caused the Debian Bug report #1063969, regarding pytest-sugar: autopkgtest regression with pytest 8 to be marked as done. This means that you claim

Processed: Re: pytest-services: autopkgtest regression with pytest 8

Processing control commands: > reassign -1 python3-pytest 8.0.1-1 Bug #1063965 [pytest-services] pytest-services: autopkgtest regression with pytest 8 Bug reassigned from package 'pytest-services' to 'python3-pytest'. No longer marked as found in versions 2.2.1+ds-3. Ignoring request to alter

Bug#1063965: pytest-services: autopkgtest regression with pytest 8

Control: reassign -1 python3-pytest 8.0.1-1 Control: close -1 8.1.1-1 It looks like this issue was caused by a regression in pytest 8.0 and is fixed now. On Thu, 15 Feb 2024 11:36:07 +0100 roehl...@debian.org wrote: Package: pytest-services Version: 2.2.1+ds-3 Severity: important User:

Processed: Re: python-b2sdk: autopkgtest regression with pytest 8

Processing control commands: > reassign -1 python3-pytest 8.0.1-1 Bug #1063960 [python-b2sdk] python-b2sdk: autopkgtest regression with pytest 8 Bug reassigned from package 'python-b2sdk' to 'python3-pytest'. No longer marked as found in versions 1.17.3-2. Ignoring request to alter fixed versions

Bug#1063960: python-b2sdk: autopkgtest regression with pytest 8

Control: reassign -1 python3-pytest 8.0.1-1 Control: close -1 8.1.1-1 As it turns out, there was a regression in pytest 8.0 which has been fixed in pytest 8.1 Cheers Timo On Thu, 15 Feb 2024 11:36:15 +0100 roehl...@debian.org wrote: Package: python-b2sdk Version: 1.17.3-2 Severity:

Bug#1067115: gross: diff for NMU version 1.0.2-4.1

On Sun, Mar 24, 2024 at 11:05:54PM +0100, Antonio Radici wrote: > On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote: > > Control: tags 1067115 + patch > > Control: tags 1067115 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for gross (versioned as 1.0.2-4.1) and

Processed: Re: Bug#1063951: fixed in barectf 3.1.2-2

Processing control commands: > reopen -1 Bug #1063951 {Done: Michael Jeanson } [barectf] barectf: autopkgtest regression with pytest 8 '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

Bug#1063951: fixed in barectf 3.1.2-2

Control: reopen -1 Control: notfixed -1 3.1.2-2 On Fri, 15 Mar 2024 21:44:05 + Debian FTP Masters wrote: * [2375fb4] Disable pytest8 deprecation warnings (Closes: #1063951) - Also (Closes: #1066742) built with pytest8 Unfortunately, this was not a permanent solution, because

Processed: forcibly merging 1065799 1066613

Processing commands for cont...@bugs.debian.org: > forcemerge 1065799 1066613 Bug #1065799 [src:ncrack] ncrack: FTBFS on arm{el,hf}: configure: error: *** compiler cannot create working executables, check config.log *** Bug #1065799 [src:ncrack] ncrack: FTBFS on arm{el,hf}: configure: error: ***

Bug#1067115: gross: diff for NMU version 1.0.2-4.1

On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote: > Control: tags 1067115 + patch > Control: tags 1067115 + pending > > Dear maintainer, > > I've prepared an NMU for gross (versioned as 1.0.2-4.1) and uploaded > it to DELAYED/2. Please feel free to tell me if I should cancel it. >

Processed: Bug#1063971 marked as pending in python-dateutil

Processing control commands: > tag -1 pending Bug #1063971 [python-dateutil] python-dateutil: autopkgtest regression with pytest 8 Added tag(s) pending. -- 1063971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1063971: marked as pending in python-dateutil

Control: tag -1 pending Hello, Bug #1063971 in python-dateutil 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:

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

Your message dated Sun, 24 Mar 2024 21:19:43 + with message-id and subject line Bug#1067358: fixed in python-flexmock 0.12.0-1 has caused the Debian Bug report #1067358, regarding anymarkup-core: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1067358: marked as done (python-flexmock: FTBFS: AttributeError: module '_pytest.runner' has no attribute 'call_runtest_hook')

Your message dated Sun, 24 Mar 2024 21:19:43 + with message-id and subject line Bug#1067358: fixed in python-flexmock 0.12.0-1 has caused the Debian Bug report #1067358, regarding python-flexmock: FTBFS: AttributeError: module '_pytest.runner' has no attribute 'call_runtest_hook' to be

Bug#1067624: marked as done (FTBFS: error: ‘struct input_event’ has no member named ‘time’)

Your message dated Sun, 24 Mar 2024 20:49:56 + with message-id and subject line Bug#1067624: fixed in antimicro 3.1.4-2 has caused the Debian Bug report #1067624, regarding FTBFS: error: ‘struct input_event’ has no member named ‘time’ to be marked as done. This means that you claim that the

Bug#1050336: marked as done (libnet-xmpp-perl: unable to StartTLS, without any feedback)

Your message dated Sun, 24 Mar 2024 20:44:29 + with message-id and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1 has caused the Debian Bug report #1064058, regarding libnet-xmpp-perl: unable to StartTLS, without any feedback to be marked as done. This means that you

Bug#1064058: marked as done (libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when hostname verification is enabled)

Your message dated Sun, 24 Mar 2024 20:44:29 + with message-id and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1 has caused the Debian Bug report #1064058, regarding libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when hostname verification is enabled to

Bug#1032868: marked as done (sendxmpp: Stopped working with version of prosody that's in bullseye)

Your message dated Sun, 24 Mar 2024 20:44:29 + with message-id and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1 has caused the Debian Bug report #1064058, regarding sendxmpp: Stopped working with version of prosody that's in bullseye to be marked as done. This means

Bug#986971: marked as done (sendxmpp: Sendxmpp doesn't work with current XMPP servers)

Your message dated Sun, 24 Mar 2024 20:44:29 + with message-id and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1 has caused the Debian Bug report #1064058, regarding sendxmpp: Sendxmpp doesn't work with current XMPP servers to be marked as done. This means that you

Bug#1067630: emacs: release 29.3 fixes "several security vulnerabilities"

Source: emacs Version: 29.2+1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team , debian-emac...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 According to the 29.3 release notes * Changes in Emacs 29.3 Emacs 29.3

Bug#1067628: FTBFS: Error: symbol `open64' is already define

Source: cctools Version: 9.9-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cctools=armel=9.9-4%2Bb2=1711271394=0 /tmp/ccxWFvuU.s: Assembler messages: /tmp/ccxWFvuU.s:1927: Error: symbol `open64' is already defined -- System Information: Debian Release:

Processed: tagging 1066866

Processing commands for cont...@bugs.debian.org: > tags 1066866 + ftbfs Bug #1066866 [railway-gtk] railway-gtk: FTBFS on i386 "type annotations needed" Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066866:

Bug#1067627: FTBFS: error: comparison of integer expressions of different signedness: ‘long unsigned int’ and ‘long int’

Source: xpra Version: 3.1.5+dfsg1-0.2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=xpra=i386=3.1.5%2Bdfsg1-0.2%2Bb3=1710056306=0 xpra/x11/bindings/keyboard_bindings.c: In function ‘__Pyx_PyInt_AndObjC’: xpra/x11/bindings/keyboard_bindings.c:30158:36: error:

Bug#1067626: FTBFS: fopen_fails test failed

Source: pacemaker Version: 2.1.6-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pacemaker=armel=2.1.6-5=1711156223=0 PASS: pcmk__output_new_test 1 - empty_formatters PASS: pcmk__output_new_test 2 - invalid_params PASS: pcmk__output_new_test 3 - no_such_format

Bug#1067625: FTBFS on armel: undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'

Source: transmission Version: 4.0.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=transmission=armel=4.0.5-1%2Bb1=1711181507=0 /usr/bin/ld: ../../libtransmission/libtransmission.a(web.cc.o): undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'

Bug#1067624: FTBFS: error: ‘struct input_event’ has no member named ‘time’

Source: antimicro Version: 3.1.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=antimicro=armel=3.1.4-1%2Bb1=1711183999=0 /<>/src/eventhandlers/uinputeventhandler.cpp: In member function ‘void UInputEventHandler::write_uinput_event(int, int, int, int, bool)’:

Bug#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

Source: acm Version: 6.0+20200416-1.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=acm=armel=6.0%2B20200416-1.1%2Bb2=1711183805=0 disscope.c: In function ‘main’: disscope.c:242:45: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type

Processed: severity of 1066765 is important, user release.debian....@packages.debian.org, usertagging 1066765

Processing commands for cont...@bugs.debian.org: > severity 1066765 important Bug #1066765 {Done: Antonio Valentino } [src:pygac] pygac: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Severity set to 'important' from 'serious' >

Bug#1067616: FTBFS: error: ‘struct input_event’ has no member named ‘time’

On Sun, 24 Mar 2024 at 23:06:18 +0500, Andrey Rakhmatullin wrote: > GLX/input_device_linuxevent.cpp: In member function ‘virtual void > CL_InputDevice_LinuxEvent::keep_alive()’: > GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no > member named ‘time’ > 269 | >

Bug#1067622: FTBFS: error: missing initializer for member ‘input_event::value’

Source: projecteur Version: 0.10-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=projecteur=armel=0.10-2%2Bb2=1711185228=0 /<>/src/deviceinput.cc: In member function ‘void InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:

Bug#1067344: marked as done (pyspectral: FTBFS: dh_missing: error: missing files, aborting)

Your message dated Sun, 24 Mar 2024 18:21:01 + with message-id and subject line Bug#1067344: fixed in pyspectral 0.13.0+ds-2 has caused the Debian Bug report #1067344, regarding pyspectral: FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim that

Bug#1067621: FTBFS on 32-bit time64 architectures: error: implicit declaration of function ‘gzopen64’

Source: berkeley-abc Version: 1.01+20230625git01b1bd1+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=berkeley- abc=armel=1.01%2B20230625git01b1bd1%2Bdfsg-3%2Bb2=1711273244=0 In file included from src/base/io/ioReadBlifMv.c:21: src/base/io/ioReadBlifMv.c: In

Bug#1067619: FTBFS: tests segfault

Source: falcosecurity-libs Version: 0.14.1-5.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=falcosecurity- libs=i386=0.14.1-5.1=1709205669=0 [ RUN ] sinsp_with_test_input.spawn_process Segmentation fault gmake[9]: *** [libsinsp/test/CMakeFiles/run-unit-test-

Bug#1067618: FTBFS: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]

Source: whitedune Version: 0.30.10-2.2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=whitedune=armel=0.30.10-2.2%2Bb1=1711185326=0 y.tab.c: In function 'yyparse': y.tab.c:2666:7: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'?

Bug#1067616: FTBFS: error: ‘struct input_event’ has no member named ‘time’

Source: clanlib Version: 1.0~svn3827-11.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=clanlib=armel=1.0%7Esvn3827-11.1=1711185366=0 GLX/input_device_linuxevent.cpp: In member function ‘virtual void CL_InputDevice_LinuxEvent::keep_alive()’:

Bug#1064139: marked as done (ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’)

Your message dated Sun, 24 Mar 2024 18:00:13 + with message-id and subject line Bug#1064139: fixed in ogre-1.12 1.12.10+dfsg2-4 has caused the Debian Bug report #1064139, regarding ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’ to be marked as done. This means

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

Alberto Bertogli wrote: > I'll try to get a debian install to boot for armhf, but it'll take me a > bit because it's not straightforward (to put it mildly :). Oh, yeah. :/ Perhaps qemu might be better option here. There might even be pre-built disk images flying around. > How urgent/important

Bug#1067615: FTBFS: error: size of array ‘dummyinfo_does_not_fit’ is negative

Source: osmo-pcu Version: 1.1.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=osmo- pcu=armel=1.1.0-3%2Bb2=1711272169=0 /bin/bash ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"osmo-pcu\" -DPACKAGE_TARNAME=\"osmo-pcu\" -DPACKAGE_VERSION=\"1.1.0\"

Processed: Re: Bug#1066465 closed by Debian FTP Masters (reply to Filip Hroch ) (Bug#1066465: fixed in dcraw 9.28-4)

Processing control commands: > found -1 dcraw/9.28-4 Bug #1066465 {Done: Filip Hroch } [src:dcraw] dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration] The source dcraw and version 9.28-4 do not appear to match any binary

Bug#1066465: closed by Debian FTP Masters (reply to Filip Hroch ) (Bug#1066465: fixed in dcraw 9.28-4)

Control: found -1 dcraw/9.28-4 On Sun, Mar 24, 2024 at 05:21:05PM +, Debian Bug Tracking System wrote: > dcraw (9.28-4) unstable; urgency=low > . >* Added missing headers. Closes: #1066465 Unfortunately, by overwriting the 9.28-3.1 changes you removed the fix, not added it, as your

Processed: Re: Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

Processing commands for cont...@bugs.debian.org: > reopen 1067486 Bug #1067486 {Done: Julian Andres Klode } [grub-efi-amd64-signed] Depends: grub-common (= 2.12-1) but it is not going to be installed 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

Control: tags -1 patch On 2024-03-24 Andrey Rakhmatullin wrote: > On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote: > > > ./config.h:2540:11: fatal error: trio.h: No such file or directory > > > 2540 | # include "trio.h" > > > | ^~~~ > (this suggests that using

Processed: Re: Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

Processing control commands: > tags -1 patch Bug #1066396 [src:lftp] lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory Added tag(s) patch. -- 1066396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066396 Debian Bug Tracking System Contact

Bug#1067499: marked as done (libconsensuscore-dev: ships /usr/include/meson.build)

Your message dated Sun, 24 Mar 2024 18:24:23 +0100 with message-id <1bc9d224-1c9a-4692-bbb6-8c71fd589...@debian.org> and subject line Re: libconsensuscore-dev: ships /usr/include/meson.build has caused the Debian Bug report #1067499, regarding libconsensuscore-dev: ships /usr/include/meson.build

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

reopen 1067486 reassign 1067486 apt severity 1067486 normal thanks Am Fri, Mar 22, 2024 at 11:46:02PM +0100 schrieb Julian Andres Klode: > > Please upload a new version so grub-efi-amd64-signed can be installable. > > Thanks! > > I'm getting a bit tired of this. This is normal, the packages are

Bug#1066465: marked as done (dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration])

Your message dated Sun, 24 Mar 2024 17:19:42 + with message-id and subject line Bug#1066465: fixed in dcraw 9.28-4 has caused the Debian Bug report #1066465, regarding dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration] to

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

On Fri, 22 Mar 2024 23:46:02 +0100 Julian Andres Klode wrote: > Version: 1+2.12+1+b1 > > (this should be the right version when it gets accepted) > > On Fri, Mar 22, 2024 at 06:23:06PM +0800, Tianyu Chen wrote: > > Package: grub-efi-amd64-signed > > Version: 1+2.12+1 > > Severity: serious > >

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

On Fri, 22 Mar 2024 23:46:02 +0100 Julian Andres Klode wrote: > Version: 1+2.12+1+b1 > > (this should be the right version when it gets accepted) > > On Fri, Mar 22, 2024 at 06:23:06PM +0800, Tianyu Chen wrote: > > Package: grub-efi-amd64-signed > > Version: 1+2.12+1 > > Severity: serious > >

Bug#1066500: marked as done (vorbisgain: FTBFS: misc.c:268:9: error: implicit declaration of function ‘isatty’ [-Werror=implicit-function-declaration])

Your message dated Sun, 24 Mar 2024 17:10:47 + with message-id and subject line Bug#1066500: fixed in vorbisgain 0.37-2.1 has caused the Debian Bug report #1066500, regarding vorbisgain: FTBFS: misc.c:268:9: error: implicit declaration of function ‘isatty’

Bug#1066324: marked as done (lucy: FTBFS: poly.c:22:9: error: implicit declaration of function ‘abi_code’ [-Werror=implicit-function-declaration])

Your message dated Sun, 24 Mar 2024 17:09:25 + with message-id and subject line Bug#1066324: fixed in lucy 1.20-4 has caused the Debian Bug report #1066324, regarding lucy: FTBFS: poly.c:22:9: error: implicit declaration of function ‘abi_code’ [-Werror=implicit-function-declaration] to be

Bug#1067175: marked as done (exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)

Your message dated Sun, 24 Mar 2024 16:49:59 + with message-id and subject line Bug#1067175: fixed in exaile 4.1.3+dfsg-3 has caused the Debian Bug report #1067175, regarding exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf to be marked as done. This

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

Your message dated Sun, 24 Mar 2024 16:49:16 + with message-id and subject line Bug#1067257: fixed in astroml 1.0.2-4 has caused the Debian Bug report #1067257, regarding astroml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1067136: marked as done (astroml: numpy.testing.run_module_suite no longer exists)

Your message dated Sun, 24 Mar 2024 16:49:15 + with message-id and subject line Bug#1067136: fixed in astroml 1.0.2-4 has caused the Debian Bug report #1067136, regarding astroml: numpy.testing.run_module_suite no longer exists to be marked as done. This means that you claim that the problem

Bug#1067465: yosys-plugin-ghdl builds on x86 only, but built on other architectures before

Hi Matthias, On Thu, Mar 21, 2024 at 11:16:56PM +0100, Matthias Klose wrote: > Package: src:yosys-plugin-ghdl > * Use ghdl-mcode instead of ghdl-gcc as it's more portable > > but ghdl-mcode is only available on amd64 and i386. With this choice you're > making things worse. My bad, I was under

Bug#1067609: marked as done (gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev)

Your message dated Sun, 24 Mar 2024 16:21:11 + with message-id and subject line Bug#1067609: fixed in gbrainy 1:2.4.6-2 has caused the Debian Bug report #1067609, regarding gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev to be marked as done. This means

Bug#1067609: gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev

Package: gbrainy Version: 1:2.4.6-1 Severity: serious Tags: patch X-Debbugs-Cc: juli...@ubuntu.com User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch *** /tmp/tmpxuguf7sd/bug_body In Ubuntu, the attached patch was applied to achieve the following: * Replace

Bug#1066983: monopd: Fails to start monopd.service

Hi, On Sat, Mar 23, 2024 at 09:35:38PM +0100, Sylvain Rochet wrote: > > That might be related to the latest change "Add a service template for > compatibility reasons with monopd.socket.". Actually, the main problem is /lib/systemd/system/monopd.socket which set Accept=yes while monopd needs

Bug#1066113: guix: CVE-2024-27297

On 2024-03-16, Vagrant Cascadian wrote: > For anyone with Guix or Nix installed, if I understand correctly, it > basically allows arbitrarily replacing the source code for anything that > you might build using Guix or Nix. Yes, for multi-user systems and people running untrusted code in “guix

Bug#1066375: canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

On 2024-03-13 Lucas Nussbaum wrote: > Source: canna > Version: 3.7p3-20 > Severity: serious [...] > During a rebuild of all packages in sid, your package failed to build > on amd64. > This is most likely caused by a change in dpkg 1.22.6, that enabled > -Werror=implicit-function-declaration. For

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

On Mon, Mar 18, 2024 at 12:29:40PM +, Chris Lamb wrote: Dear Alberto, Hi! Hope this finds you well. Any quick/immediate ideas on what might be behind this build failure? Note that this is on ARM architectures rather than amd64 — I often misread and conflate them at speed. :) Oh, and I

Bug#1067604: src:libcdk5: autopkgtest regression, tests the old version and more issues

Source: libcdk5 Version: 5.0.20230201-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this

Bug#1066543: marked as done (ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror])

Your message dated Sun, 24 Mar 2024 12:21:02 + with message-id and subject line Bug#1066543: fixed in ucx 1.16.0+ds-5 has caused the Debian Bug report #1066543, regarding ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] to

Bug#1067208: marked as done (umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64")

Your message dated Sun, 24 Mar 2024 11:54:55 + with message-id and subject line Bug#1067208: fixed in umockdev 0.18.1-1 has caused the Debian Bug report #1067208, regarding umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" to be marked as done. This means that you

Bug#1066433: marked as done (uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type)

Your message dated Sun, 24 Mar 2024 10:51:33 + with message-id and subject line Bug#1066433: fixed in uim 1:1.8.8-9.3 has caused the Debian Bug report #1066433, regarding uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type to be marked as done. This means that

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote: > > ./config.h:2540:11: fatal error: trio.h: No such file or directory > > 2540 | # include "trio.h" > > | ^~~~ (this suggests that using trio is not actually supported but that's irrelevant) This is caused by the

Processed: Re: Bug#1067208: umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

Processing control commands: > forwarded -1 https://github.com/martinpitt/umockdev/issues/216 Bug #1067208 [src:umockdev] umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" Set Bug forwarded-to-address to 'https://github.com/martinpitt/umockdev/issues/216'. > tag -1

Bug#1067208: umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216 Control: tag -1 upstream pending Hello all, Thorsten Glaser [2024-03-20 3:05 +]: > /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed > only with _FILE_OFFSET_BITS=64" >26 | # error

Processed: bug 1067545 is forwarded to https://github.com/klatexformula/klatexformula/pull/75, tagging 1067545

Processing commands for cont...@bugs.debian.org: > forwarded 1067545 https://github.com/klatexformula/klatexformula/pull/75 Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’} Set Bug forwarded-to-address to

Bug#1067596: FTBFS: error: ‘const struct input_event’ has no member named ‘time’

Source: xf86-input-multitouch Version: 1.0~rc3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=xf86-input- multitouch=armel=1.0%7Erc3-2%2Bb2=1711272573=0 src/hwstate.c: In function ‘finish_packet’: src/hwstate.c:43:24: error: ‘const struct input_event’ has no

Bug#1066433: uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type

Control: tags -1 patch On 2024-03-13 Lucas Nussbaum wrote: > Source: uim > Version: 1:1.8.8-9.2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie > Hi, > During a rebuild of all packages in sid, your package

Processed: Re: Bug#1066433: uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type

Processing control commands: > tags -1 patch Bug #1066433 [src:uim] uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type Added tag(s) patch. -- 1066433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066433 Debian Bug Tracking System Contact

Processed: tagging 1067567, tagging 1067545, tagging 1067560, tagging 1067428, tagging 1067546, tagging 1052841 ...

Processing commands for cont...@bugs.debian.org: > tags 1067567 + sid trixie Bug #1067567 [dhcp-probe] dhcp-probe: [time_t] Remove hardcoded dependencies on libpcap0.8, libnet, shlibs takes care of them Added tag(s) sid and trixie. > tags 1067545 + sid trixie Bug #1067545 [src:klatexformula]

Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst

On Thu, 21 Mar 2024 18:39:00 +0100 Jochen Sprickerhof wrote: dpkg -S configuration.rst bugwarrior: /usr/share/doc/bugwarrior/html/_sources/common_configuration.rst.txt bugwarrior: /usr/share/doc/bugwarrior/html/_sources/configuration.rst.txt The second one is the same file. I will push new

Processed: ITP: golang-github-skeema-knownhosts -- Go SSH known_hosts wrapper with host key lookup

Processing control commands: > block 1060701 by -1 Bug #1060701 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: CVE-2023-49568 CVE-2023-49569 1060701 was blocked by: 1067593 1060701 was not blocking any bugs. Added blocking bug(s) of 1060701: 1067594 -- 1060701:

Processed: ITP: golang-github-pjbgf-sha1cd -- SHA1 implementation with collision detection

Processing control commands: > block 1060701 by -1 Bug #1060701 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: CVE-2023-49568 CVE-2023-49569 1060701 was not blocked by any bugs. 1060701 was not blocking any bugs. Added blocking bug(s) of 1060701: 1067593 -- 1060701:

Bug#1066500: vorbisgain: diff for NMU version 0.37-2.1

Control: tags 1066500 + patch Control: tags 1066500 + pending Dear maintainer, I've prepared an NMU for vorbisgain (versioned as 0.37-2.1). The diff is attached to this message. I require a sponsor to have it uploaded. Regards. -- Håvarddiff -Nru vorbisgain-0.37/debian/changelog

Processed: vorbisgain: diff for NMU version 0.37-2.1

Processing control commands: > tags 1066500 + patch Bug #1066500 [src:vorbisgain] vorbisgain: FTBFS: misc.c:268:9: error: implicit declaration of function ‘isatty’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066500 + pending Bug #1066500 [src:vorbisgain] vorbisgain:

Processed: tagging 1056893

Processing commands for cont...@bugs.debian.org: > tags 1056893 + ftbfs Bug #1056893 [src:uvloop] uvloop: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056893:

Bug#1064423: bug 1064423: src:gnome-keyring: FTBFS on s390x

Hi all, [s390x porters in CC, maybe they can help?] On Wed, 21 Feb 2024 22:22:54 +0100 Paul Gevers wrote: Source: gnome-keyring The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your

Processed: Bug#1066261 marked as pending in lintian

Processing control commands: > tag -1 pending Bug #1066261 [src:lintian] lintian: FTBFS: hello.c:9:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration] Bug #1065431 [src:lintian] lintian: autopkgtests fail due to implicit definition of memcpy Added tag(s)

Bug#1066261: marked as pending in lintian

Control: tag -1 pending Hello, Bug #1066261 in lintian 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: