Bug#1067916: FTBFS: tests failed

Thank you very much to Arnd Bergmann and Wookey for the assistance off-list. Arnd's explanation of the root cause and the patch required is reproduced below. I suspect others will also find it helpful. On Sun, Apr 14, 2024 at 5:33 AM Arnd Bergmann wrote: > This is the same problem that any

Processed: unblock 1068942 by 1069098

Processing control commands: > unblock 1068942 by 1069098 Bug #1068942 [src:oscar4] src:oscar4: unsatisfied build dependency in testing: emboss-data 1068942 was blocked by: 1069098 1068942 was not blocking any bugs. Removed blocking bug(s) of 1068942: 1069098 -- 1068942:

Bug#1068942: unblock 1068942 by 1069098

control: unblock 1068942 by 1069098 Hello, emboss no longer builds on s390x and its binaries have been RMed from s390x, unblocking emboss migration to testing. This in principle should resolve the current bug. Andrius

Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)

Your message dated Fri, 19 Apr 2024 05:20:35 + with message-id and subject line Bug#1069191: fixed in glibc 2.37-18 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence to be marked

Processed: Bug#1069191 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Added tag(s) pending. -- 1069191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069191 Debian Bug Tracking

Bug#1069191: marked as pending in glibc

Control: tag -1 pending Hello, Bug #1069191 in glibc 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#1064928: marked as done (FTBFS everywhere)

Your message dated Fri, 19 Apr 2024 04:50:04 + with message-id and subject line Bug#1064928: fixed in openturns 1.21.1-5 has caused the Debian Bug report #1064928, regarding FTBFS everywhere to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: Reducing severity to important

Processing commands for cont...@bugs.debian.org: > severity 1068133 important Bug #1068133 {Done: Mattias Ellert } [src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64 library Severity set to 'important' from 'serious' > severity 1068134 important Bug #1068134 {Done:

Bug#1069270: rendering failure with gtk 4

Package: librnd Severity: serious Version: 4.2.0-1 There appears to be a bug in this version of librnd that prevents successful rendering with the default gtk 4 hid. In the short term, users can work around the problem by installing librnd4-hid-lesstif and invoking the various ringdove tools

Bug#1063085: marked as done (uhd: NMU diff for 64-bit time_t transition)

Your message dated Fri, 19 Apr 2024 04:05:07 + with message-id and subject line Bug#1063085: fixed in uhd 4.6.0.0+ds1-6 has caused the Debian Bug report #1063085, regarding uhd: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been

Bug#1063324: marked as done (libuhd4.6.0-dpdk has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libuhd.so.4.6.0)

Your message dated Fri, 19 Apr 2024 04:05:07 + with message-id and subject line Bug#1063324: fixed in uhd 4.6.0.0+ds1-6 has caused the Debian Bug report #1063324, regarding libuhd4.6.0-dpdk has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libuhd.so.4.6.0 to be marked as done.

Processed: closing 1066231

Processing commands for cont...@bugs.debian.org: > close 1066231 7.0.2+repack-1~exp1 Bug #1066231 [src:code-saturne] code-saturne: FTBFS: src/mei/mei_parser.c:1310:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration] Marked as fixed in versions

Processed: found 1050407 in 1.6.0-2, tagging 1050407, found 1064516 in 0.9.1-1, block 1062029 with 1037597 ...

Processing commands for cont...@bugs.debian.org: > found 1050407 1.6.0-2 Bug #1050407 [src:tycho] tycho: build-depends on obsolete libeclipse-osgi-util-java Marked as found in versions tycho/1.6.0-2. > tags 1050407 + sid trixie experimental Bug #1050407 [src:tycho] tycho: build-depends on

Bug#1066305: marked as done (3dchess: FTBFS: init.c:140:21: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])

Your message dated Fri, 19 Apr 2024 01:49:16 + with message-id and subject line Bug#1066305: fixed in 3dchess 0.8.1-22 has caused the Debian Bug report #1066305, regarding 3dchess: FTBFS: init.c:140:21: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration] to

Processed: Re: Bug#1069202 closed by Debian FTP Masters (reply to Holger Levsen ) (Bug#1069202: fixed in rust-sequoia-chameleon-gnupg 0.8.0-3)

Processing control commands: > reopen 1069202 Bug #1069202 {Done: Holger Levsen } [gpg-from-sq] gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink pointing to gpg-sq 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and

Bug#1069202: closed by Debian FTP Masters (reply to Holger Levsen ) (Bug#1069202: fixed in rust-sequoia-chameleon-gnupg 0.8.0-3)

Control: reopen 1069202 Control: found 1069202 0.8.0-3 The symlinks in the gpg-from-sq and gpgv-from-sq packages appear to point in the wrong direction. That is, gpg-from-sq installs a symlink at /usr/bin/gpg-sq, which refers to gpg. Instead, gpg-from-sq should install a symlink at

Processed: retitle 1069265 to tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1 corrupts zoneinfo files

Processing commands for cont...@bugs.debian.org: > retitle 1069265 tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1 corrupts > zoneinfo files Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Changed Bug title to 'tzdata: Upgrade from 2023c-2 to 2024a-0+deb10u1

Processed: tagging 1069265

Processing commands for cont...@bugs.debian.org: > tags 1069265 - upstream Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Removed tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265:

Processed: tagging 1069265

Processing commands for cont...@bugs.debian.org: > tags 1069265 - d-i Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files Removed tag(s) d-i. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069265:

Bug#1064692: marked as done (yotta: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_test] Error 1)

Your message dated Fri, 19 Apr 2024 00:49:20 + with message-id and subject line Bug#1064692: fixed in yotta 0.20.5-6 has caused the Debian Bug report #1064692, regarding yotta: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_test] Error 1 to be marked as done. This means that you

Processed: found 1069265 in tzdata/2024a-0+deb10u1

Processing commands for cont...@bugs.debian.org: > found 1069265 tzdata/2024a-0+deb10u1 Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files The source tzdata and version 2024a-0+deb10u1 do not appear to match any binary packages Marked as found in versions

Processed: notfound 1069265 in tzdata/2023c-2

Processing commands for cont...@bugs.debian.org: > notfound 1069265 tzdata/2023c-2 Bug #1069265 [tzdata] tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files No longer marked as found in versions tzdata/2023c-2. > thanks Stopping processing here. Please contact me if you need

Bug#1065993: xwiimote: FTBFS on arm{el,hf}:

Followup-For: Bug #1065993 Control: tag -1 patch pending Hi, I've pushed a fix for this issue and some more t64 cleanup to the GIT repository. If you want, I can go ahead with an NMU. Andreas

Processed: Update bug ownership

Processing commands for cont...@bugs.debian.org: > owner 1064706 Nick Morrott Bug #1064706 {Done: Nick Morrott } [src:python-mbed-host-tests] python-mbed-host-tests: FTBFS: AttributeError: 'called_once' is not a valid assertion. Use a spec for the mock if 'called_once' is meant to be an

Processed: Re: xwiimote: FTBFS on arm{el,hf}:

Processing control commands: > tag -1 patch pending Bug #1065993 [src:xwiimote] xwiimote: FTBFS on arm{el,hf}: Added tag(s) pending and patch. -- 1065993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1069265: tzdata: Upgrade from 2023c-2 to 2024 corrupts zoneinfo files

Package: tzdata Version: 2023c-2 Severity: grave Tags: d-i upstream Justification: renders package unusable Dear Maintainer, On 2024-04-17 several of my servers running Debian 10 received an update for the tzdata package via Debian unattended-upgrade. However, this update resulted in corruption

Bug#1067561: FTBFS: Error: symbol `open64' is already defined

On 14/04/2024 20:21, Yves-Alexis Perez wrote: On Sat, 2024-04-13 at 16:11 +0100, Peter Green wrote: >> Hi, thanks for the patch. It looks a bit strong though, undefining stuff >> like >> that unconditionally. Do you have pointers to the Ubuntu bug or something? >> I've looked at upstream commits

Bug#1064706: marked as done (python-mbed-host-tests: FTBFS: AttributeError: 'called_once' is not a valid assertion. Use a spec for the mock if 'called_once' is meant to be an attribute.)

Your message dated Thu, 18 Apr 2024 22:49:31 + with message-id and subject line Bug#1064706: fixed in python-mbed-host-tests 1.4.4-10 has caused the Debian Bug report #1064706, regarding python-mbed-host-tests: FTBFS: AttributeError: 'called_once' is not a valid assertion. Use a spec for the

Bug#1066684: marked as done (xpat2: FTBFS: loadsave.c:279:24: error: implicit declaration of function ‘cuserid’ [-Werror=implicit-function-declaration])

Your message dated Thu, 18 Apr 2024 22:13:13 + with message-id and subject line Bug#1066684: fixed in xpat2 1.07-20+nmu1 has caused the Debian Bug report #1066684, regarding xpat2: FTBFS: loadsave.c:279:24: error: implicit declaration of function ‘cuserid’

Bug#1069261: cwlformat: fails with newer ruamel.yaml

Package: cwlformat Version: 2022.02.18-2 Severity: serious Tags: patch I've uploaded ruamel.yaml version 0.18.6 and it has unfortunately broken the test suite of cwlformat. There is a simple patch, applied upstream, to fix this: it just updates the expected output of the test. It is here:

Processed: severity of 1068938 is grave, severity of 1064293 is grave

Processing commands for cont...@bugs.debian.org: > severity 1068938 grave Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in paths Severity set to 'grave' from 'important' > severity 1064293 grave Bug #1064293 [src:less] less: CVE-2022-48624 Severity set to 'grave' from

Bug#1066684: xpat2: FTBFS: loadsave.c:279:24: error: implicit declaration of function ‘cuserid’ [-Werror=implicit-function-declaration]

Here's an NMU diff that fixes the FTBFS. In incoming right now. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross diff -Nru

Processed: severity of 1069191 is grave

Processing commands for cont...@bugs.debian.org: > # make it RC with https://www.openwall.com/lists/oss-security/2024/04/18/4 > severity 1069191 grave Bug #1069191 [src:glibc] glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence Severity

Bug#1068147: marked as done (FTBFS: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’})

Your message dated Thu, 18 Apr 2024 21:11:58 + with message-id and subject line Bug#1068147: fixed in pesign 116-7 has caused the Debian Bug report #1068147, regarding FTBFS: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’} to be

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

Your message dated Thu, 18 Apr 2024 21:09:59 + with message-id and subject line Bug#1067255: fixed in mplcursors 0.5.3-1 has caused the Debian Bug report #1067255, regarding mplcursors: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1063979: marked as done (mplcursors: autopkgtest regression with pytest 8)

Your message dated Thu, 18 Apr 2024 21:09:59 + with message-id and subject line Bug#1063979: fixed in mplcursors 0.5.3-1 has caused the Debian Bug report #1063979, regarding mplcursors: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the problem has

Bug#1069197: marked as done (udisks: FTBFS on s390x: ./doc/udisks2-scan.c:204:(.text.startup.main+0x216): undefined reference to `udisks_linux_drive_lsm_get_type')

Your message dated Thu, 18 Apr 2024 23:03:37 +0200 with message-id <01a7e2d2-5db6-4aa3-9315-77ad89210...@debian.org> and subject line Re: udisks: FTBFS on s390x: ./doc/udisks2-scan.c:204:(.text.startup.main+0x216): undefined reference to `udisks_linux_drive_lsm_get_type' has caused the Debian

Bug#1069259: haskell-termonad: FTBFS on armhf: callStackDoc, called at compiler/GHC/Utils/Panic.hs:182:37 in ghc:GHC.Utils.Panic

Source: haskell-termonad Version: 4.5.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=haskell-termonad=armhf=4.5.0.0-1%2Bb4=1713092640=0 : error:

Bug#1069258: ruby-curb: FTBFS: 178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 notifications

Source: ruby-curb Version: 1.0.5-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ruby-curb=amd64=1.0.5-1%2Bb3=1712538836=0

Bug#1069257: cython: FTBFS on !all: Could not import extension sphinx_issues (exception: No module named 'sphinx_issues')

Source: cython Version: 3.0.10+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cython=amd64=3.0.10%2Bdfsg-2=1713455643=0 debian/rules

Processed: found 1066788 in 2.0.2-1.1

Processing commands for cont...@bugs.debian.org: > # version in testing FTBFS with the same error > found 1066788 2.0.2-1 Bug #1066788 [src:gyoto] gyoto: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 check-lorene returned exit code 2 Marked as found in

Bug#1067547: wmweather+: diff for NMU version 2.19~alpha+ds-1.1

Control: tags 1067547 + patch Control: tags 1067547 + pending Dear maintainer, I've prepared an NMU for wmweather+ (versioned as 2.19~alpha+ds-1.1) and am going to upload it to DELAYED/2. Please feel free to tell me if I should delay it longer. J. diff -Nru

Processed: wmweather+: diff for NMU version 2.19~alpha+ds-1.1

Processing control commands: > tags 1067547 + patch Bug #1067547 [src:wmweather+] FTBFS: "vsnprintf is so broken we can't compensate. Sorry." Added tag(s) patch. > tags 1067547 + pending Bug #1067547 [src:wmweather+] FTBFS: "vsnprintf is so broken we can't compensate. Sorry." Added tag(s)

Bug#1069254: nwipe: FTBFS: configure: error: libconfig library not found

Source: nwipe Version: 0.36-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nwipe=arm64=0.36-1=1713296007=0 checking for libconfig... no checking for

Bug#1064729: marked as done (quilt: FTBFS: make[1]: *** [debian/rules:27: override_dh_auto_build] Error 1)

Your message dated Thu, 18 Apr 2024 19:50:29 + with message-id and subject line Bug#1064729: fixed in quilt 0.68-1 has caused the Debian Bug report #1064729, regarding quilt: FTBFS: make[1]: *** [debian/rules:27: override_dh_auto_build] Error 1 to be marked as done. This means that you

Bug#1069247: libconfig-model-dpkg-perl: test failures

Source: libconfig-model-dpkg-perl Version: 3.004 Severity: serious Tags: ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on https://ci.debian.net/packages/libc/libconfig-model-dpkg-perl/unstable/amd64/45274399/ libconfig-model-dpkg-perl has

Bug#1069246: dh-make-perl: test failure in t/AptContents.t

Source: dh-make-perl Version: 0.124 Severity: serious Tags: ftbfs help Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As noticed on ci.debian.net, dh-make-perl has a test failure in t/AptContents.t:

Bug#1066438: marked as done (backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’)

Your message dated Thu, 18 Apr 2024 16:49:16 + with message-id and subject line Bug#1066438: fixed in backuppc-rsync 3.1.3.0-4 has caused the Debian Bug report #1066438, regarding backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’ to be marked as

Bug#1069202: marked as done (gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink pointing to gpg-sq)

Your message dated Thu, 18 Apr 2024 16:36:28 + with message-id and subject line Bug#1069202: fixed in rust-sequoia-chameleon-gnupg 0.8.0-3 has caused the Debian Bug report #1069202, regarding gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink pointing to gpg-sq to be marked

Processed: tagging 1066438

Processing commands for cont...@bugs.debian.org: > tags 1066438 + pending Bug #1066438 [src:backuppc-rsync] backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#1069201: marked as done (src:rust-sequoia-chameleon-gnupg: gpg-sq and gpgv-sq from 0.8.0 conflict with sequoia-chameleon-gnupg 0.5.1)

Your message dated Thu, 18 Apr 2024 15:24:22 + with message-id and subject line Bug#1069201: fixed in rust-sequoia-chameleon-gnupg 0.8.0-2 has caused the Debian Bug report #1069201, regarding src:rust-sequoia-chameleon-gnupg: gpg-sq and gpgv-sq from 0.8.0 conflict with

Bug#1065775: marked as done (juman: iotool.c:154:6: error: implicit declaration of function ‘getcwd’; did you mean ‘getw’? [-Werror=implicit-function-declaration])

Your message dated Thu, 18 Apr 2024 15:20:29 + with message-id and subject line Bug#1065775: fixed in juman 7.0-3.7 has caused the Debian Bug report #1065775, regarding juman: iotool.c:154:6: error: implicit declaration of function ‘getcwd’; did you mean ‘getw’?

Bug#1066222: marked as done (gtk-chtheme: FTBFS: theme_sel.c:113:5: error: implicit declaration of function ‘gtk_timeout_add’; did you mean ‘g_timeout_add’? [-Werror=implicit-function-declaration])

Your message dated Thu, 18 Apr 2024 15:20:16 + with message-id and subject line Bug#1066222: fixed in gtk-chtheme 0.3.1-6.2 has caused the Debian Bug report #1066222, regarding gtk-chtheme: FTBFS: theme_sel.c:113:5: error: implicit declaration of function ‘gtk_timeout_add’; did you mean

Bug#1058290: marked as done (python-kafka: FTBFS: E ModuleNotFoundError: No module named 'kafka.vendor.six.moves')

Your message dated Thu, 18 Apr 2024 16:06:21 +0200 with message-id <1eb6ee77-c932-4826-aef3-14cd4a15d...@debian.org> and subject line Fixed has caused the Debian Bug report #1058290, regarding python-kafka: FTBFS: E ModuleNotFoundError: No module named 'kafka.vendor.six.moves' to be marked as

Processed: severity 1069097 important

Processing commands for cont...@bugs.debian.org: > severity 1069097 important Bug #1069097 [openstack-dashboard] openstack-dashboard: postinst error makes designate-dashboard to FTBFS randomly Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact

Processed: Re: Bug#1069244: nfs: Have not changed nfs version, but reboot of server says nfs versions do not match

Processing commands for cont...@bugs.debian.org: > severity 1069244 important Bug #1069244 [klibc-utils] nfs: Have not changed nfs version, but reboot of server says nfs versions do not match Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you

Bug#1065797: marked as done (st: FTBFS on arm{el,hf}: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’? [-Werror=implicit-function-declaration])

Your message dated Thu, 18 Apr 2024 13:50:13 + with message-id and subject line Bug#1065797: fixed in st 1.9-3.4 has caused the Debian Bug report #1065797, regarding st: FTBFS on arm{el,hf}: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’?

Bug#1068431: marked as done (rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures.)

Your message dated Thu, 18 Apr 2024 13:49:22 + with message-id and subject line Bug#1068431: fixed in rakarrack 0.6.1-9 has caused the Debian Bug report #1068431, regarding rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim

Bug#1066287: marked as done (st: FTBFS: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’? [-Werror=implicit-function-declaration])

Your message dated Thu, 18 Apr 2024 13:50:13 + with message-id and subject line Bug#1066287: fixed in st 1.9-3.4 has caused the Debian Bug report #1066287, regarding st: FTBFS: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’?

Bug#1068431: marked as pending in rakarrack

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

Processed: Bug#1068431 marked as pending in rakarrack

Processing control commands: > tag -1 pending Bug #1068431 [rakarrack] rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) pending. -- 1068431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068431 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1069244: nfs: Have not changed nfs version, but reboot of server says nfs versions do not match

Package: klibc-utils Version: 2.0.6-1+deb10u1 Severity: critical File: nfs Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Bug#1069192: marked as done (Autopkgtest failure: missing dependency on python3-pytz)

Your message dated Thu, 18 Apr 2024 13:19:21 + with message-id and subject line Bug#1069192: fixed in lektor 3.3.7-2.1 has caused the Debian Bug report #1069192, regarding Autopkgtest failure: missing dependency on python3-pytz to be marked as done. This means that you claim that the problem

Bug#1068647: marked as done (python-pot: autopkgtest regression on i386 with NumPy 1.26.4)

Your message dated Thu, 18 Apr 2024 13:05:11 + with message-id and subject line Bug#1068647: fixed in python-pot 0.9.3+dfsg-2 has caused the Debian Bug report #1068647, regarding python-pot: autopkgtest regression on i386 with NumPy 1.26.4 to be marked as done. This means that you claim that

Bug#1014539: squirrel3: CVE-2022-30292

On Thu, 7 Jul 2022 17:55:11 +0200 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote: > Source: squirrel3 > X-Debbugs-CC: t...@security.debian.org > Severity: grave > Tags: security > > Hi, > > The following vulnerability was published for squirrel3. > > CVE-2022-30292[0]: > | Heap-based buffer overflow

Bug#1069192: Autopkgtest failure: missing dependency on python3-pytz

Hi Nilesh, Le 2024-04-18 à 06 h 24, Nilesh Patra a écrit : I will NMU this in a week or so if I see no activity. This package has been going through in-attention for a while. Please, you may upload the fix whenever you wish, it's fine with me. -- Jérôme

Bug#1069196: marked as done (eulisp: FTBFS on arm{el,hf}: unixcall.c:90:15: error: conflicting types for ‘timezone’; have ‘time_t’ {aka ‘long long int’})

Your message dated Thu, 18 Apr 2024 12:04:51 + with message-id and subject line Bug#1069196: fixed in euslisp 9.30+dfsg-1 has caused the Debian Bug report #1069196, regarding eulisp: FTBFS on arm{el,hf}: unixcall.c:90:15: error: conflicting types for ‘timezone’; have ‘time_t’ {aka ‘long long

Processed: tagging 1046274, fixed 1062998 in 4.19.0-1.1~exp1, tagging 1062998, tagging 1062072 ...

Processing commands for cont...@bugs.debian.org: > tags 1046274 - sid trixie Bug #1046274 {Done: Roland Mas } [src:hkl] hkl: Fails to build source after successful build Removed tag(s) sid and trixie. > fixed 1062998 4.19.0-1.1~exp1 Bug #1062998 {Done: Steve Langasek } [src:tumbler] tumbler:

Bug#1052085: marked as done (golang-github-traefik-yaegi: FTBFS: test failures)

Your message dated Thu, 18 Apr 2024 11:04:40 + with message-id and subject line Bug#1052085: fixed in golang-github-traefik-yaegi 0.16.1-1 has caused the Debian Bug report #1052085, regarding golang-github-traefik-yaegi: FTBFS: test failures to be marked as done. This means that you claim

Bug#975138: marked as done (simulavr: FTBFS: collect2: error: ld returned 1 exit status)

Your message dated Thu, 18 Apr 2024 10:34:44 + with message-id and subject line Bug#975138: fixed in simulavr 1.0.0+git20160221.e53413b-3 has caused the Debian Bug report #975138, regarding simulavr: FTBFS: collect2: error: ld returned 1 exit status to be marked as done. This means that you

Bug#1069192: Autopkgtest failure: missing dependency on python3-pytz

I will NMU this in a week or so if I see no activity. This package has been going through in-attention for a while. Best, Nilesh signature.asc Description: PGP signature

Processed: Re: Bug#1066438: backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’

Processing control commands: > tag -1 + patch Bug #1066438 [src:backuppc-rsync] backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’ Added tag(s) patch. -- 1066438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066438 Debian Bug Tracking System

Bug#1066438: backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’

Control: tag -1 + patch Hi Andreas, Andreas Hasenack wrote: > This fixes the build: > > --- a/configure.ac > +++ b/configure.ac > @@ -852,6 +852,7 @@ fi > > AC_CACHE_CHECK([if gettimeofday takes tz > argument],rsync_cv_HAVE_GETTIMEOFDAY_TZ,[ > AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include >

Processed: Re: Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

Processing control commands: > tags -1 + patch Bug #1068665 [src:cfengine3] cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed Added tag(s) patch. -- 1068665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

Control: tags -1 + patch Hi, On 2024-04-08 11:17, Sebastian Ramacher wrote: > 1 != 3 > ERROR: connection_management_test.c:39 Failure! > 1 != 2 > ERROR: connection_management_test.c:69 Failure! > 1 != 2 > ERROR: connection_management_test.c:99 Failure! > 1 != 2 > ERROR:

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

Your message dated Thu, 18 Apr 2024 09:23:38 + with message-id and subject line Bug#1067258: fixed in xphyle 4.4.4-3 has caused the Debian Bug report #1067258, regarding xphyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1067318: autorm ping

ping to prevent autoremoval from testing, while time_t-64bit migration is unfinished.

Bug#1069055: marked as done (chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition)

Your message dated Thu, 18 Apr 2024 07:49:20 + with message-id and subject line Bug#1069055: fixed in chr 0.1.78-1 has caused the Debian Bug report #1069055, regarding chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition to be marked as done. This means

Processed: Re: Bug#1069055: chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition

Processing control commands: > tag -1 patch Bug #1069055 [src:chr] chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition Added tag(s) patch. > block -1 by 1069198 Bug #1069055 [src:chr] chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks

Bug#1069055: chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition

Control: tag -1 patch Control: block -1 by 1069198 On Mon, Apr 15, 2024 at 12:47:39PM -0400, Boyuan Yang wrote: > Your package builds-depends on library package libqt5concurrent5, > which does not exist in Debian Sid after Debian 64-bit time_t transition > since the library package was renamed. >

Bug#1069226: tomogui: FTBFS: RuntimeError: Sphinx is required to build or test the documentation

Source: tomogui Version: 0.3.1-2 Severity: serious Tags: ftbfs Hello, tomogui FTBFS in sid on amd64: running build_doc Traceback (most recent call last): File "/home/merkys/tomogui-0.3.1/setup.py", line 804, in setup_package() File "/home/merkys/tomogui-0.3.1/setup.py", line 801, in

Bug#1069225: freesas: FTBFS: fatal error: numpy/arrayobject.h: No such file or directory

Source: freesas Version: 0.9.0-6 Severity: serious Tags: ftbfs Hello, freesas FTBFS in sid on amd64: INFO:root:x86_64-linux-gnu-gcc -Wsign-compare -fwrapv -O2 -Wall -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security

Bug#1069224: nabu: FTBFS: AssertionError: OpenclUnsharpMask: max error is too high with method

Source: nabu Version: 2023.1.1-3 Severity: serious Tags: ftbfs Hello, nabu FTBFS in sid on amd64: FAILURES

Bug#1069222: purple-xmpp-carbons: debian/shlibs.local hardcodes dependency on libpurple0

Package: purple-xmpp-carbons Version: 0.2.3-1 Severity: serious Tags: trixie sid debian/shlibs.local hardcodes a dependency on libpurple0, which makes the package uninstallable on armel/armhf due to the 64-bit time_t rename to libpurple0t64.