Bug#1066959: sysdig: wrong runtime dependency on old falcosecurity binary
Package: sysdig
Version: 0.35.0+repack-1
Severity: Serious
Hello, for some reasons sysdig has an hardcoded runtime dependency on
libfalcosecurity0, now renamed in libfalcosecurity0t64.
You can remove it and let debhelper create it via shlibs:Depends automatically
*** /tmp/tmpmxvw_b1d/sysdig_0.35.0+repack-1ubuntu1.debdiff
diff -Nru sysdig-0.35.0+repack/debian/control
sysdig-0.35.0+repack/debian/control
--- sysdig-0.35.0+repack/debian/control 2024-01-26 07:25:50.0 +0100
+++ sysdig-0.35.0+repack/debian/control 2024-03-16 06:50:27.0 +0100
@@ -27,8 +27,7 @@
Package: sysdig
Architecture: any
-Depends: libfalcosecurity0 (>= 0.11.3),
- ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
Recommends: falcosecurity-scap-dkms
Description: system-level exploration and troubleshooting tool
Sysdig instruments your physical and virtual machines at the OS level
G.
Processed: fix bug metadata
Processing commands for cont...@bugs.debian.org: > # reassign from source to binary > reassign 1066895 python3-reactivex Bug #1066895 [src:python-reactivex] python-reactivex: duplicate of src:python-rx Bug reassigned from package 'src:python-reactivex' to 'python3-reactivex'. No longer marked as found in versions python-reactivex/4.0.4-1. Ignoring request to alter fixed versions of bug #1066895 to the same values previously set > # restore found after reassign > found 1066895 python-reactivex/4.0.4-1 Bug #1066895 [python3-reactivex] python-reactivex: duplicate of src:python-rx Marked as found in versions python-reactivex/4.0.4-1. > # reaffect from source to binary > affects 1066895 - src:python-rx Bug #1066895 [python3-reactivex] python-reactivex: duplicate of src:python-rx Removed indication that 1066895 affects src:python-rx > affects 1066895 + python3-rx Bug #1066895 [python3-reactivex] python-reactivex: duplicate of src:python-rx Added indication that 1066895 affects python3-rx > thanks Stopping processing here. Please contact me if you need assistance. -- 1066895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066622: marked as done (radlib: FTBFS: ../src/radevents.c:185:29: error: implicit declaration of function ‘radProcessGetNotifyFD’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 04:58:00 + with message-id and subject line Bug#1066622: fixed in radlib 2.12.0-7 has caused the Debian Bug report #1066622, regarding radlib: FTBFS: ../src/radevents.c:185:29: error: implicit declaration of function ‘radProcessGetNotifyFD’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: radlib Version: 2.12.0-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I../h -I/usr/include -D_GNU_SOURCE -I/usr/include -I/usr/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radmsgRouter.lo -MD -MP -MF .deps/radmsgRouter.Tpo -c -o radmsgRouter.lo > `test -f '../src/radmsgRouter.c' || echo './'`../src/radmsgRouter.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radevents.lo -MD -MP -MF .deps/radevents.Tpo -c ../src/radevents.c -fPIC > -DPIC -o .libs/radevents.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radconffile.lo -MD -MP -MF .deps/radconffile.Tpo -c ../src/radconffile.c > -fPIC -DPIC -o .libs/radconffile.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > raddebug.lo -MD -MP -MF .deps/raddebug.Tpo -c ../src/raddebug.c -fPIC -DPIC > -o .libs/raddebug.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radbuffers.lo -MD -MP -MF .deps/radbuffers.Tpo -c ../src/radbuffers.c -fPIC > -DPIC -o .libs/radbuffers.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radmsgRouter.lo -MD -MP -MF .deps/radmsgRouter.Tpo -c ../src/radmsgRouter.c > -fPIC -DPIC -o .libs/radmsgRouter.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radlist.lo -MD -MP -MF .deps/radlist.Tpo -c ../src/radlist.c -fPIC -DPIC -o > .libs/radlist.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../h -I/usr/include > -D_GNU_SOURCE -I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT > radcrc.lo -MD -MP -MF .deps/radcrc.Tpo -c ../src/radcrc.c -fPIC -DPIC -o
Bug#1066302: marked as done (liburjtag: FTBFS: svf.c:1286:19: error: implicit declaration of function ‘urj_tap_detect’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 04:27:06 + with message-id and subject line Bug#1066302: fixed in liburjtag 0.0~git20231222.310e99b-1 has caused the Debian Bug report #1066302, regarding liburjtag: FTBFS: svf.c:1286:19: error: implicit declaration of function ‘urj_tap_detect’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liburjtag Version: 0.0~git20230703.491077f-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -I../../include/urjtag -I../.. -I../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/libusb-1.0 -Wall -Wmissing-prototypes > -Wstrict-prototypes -Wpointer-arith -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o svf_flex.lo svf_flex.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include/urjtag > -I../.. -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libusb-1.0 -Wall -Wmissing-prototypes -Wstrict-prototypes > -Wpointer-arith -g -O2 -Werror=implicit-function-declaration > "-ffile-prefix-map=/<>=." -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > svf_bison.c -fPIC -DPIC -o .libs/svf_bison.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include/urjtag > -I../.. -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libusb-1.0 -Wall -Wmissing-prototypes -Wstrict-prototypes > -Wpointer-arith -g -O2 -Werror=implicit-function-declaration > "-ffile-prefix-map=/<>=." -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > svf_flex.c -fPIC -DPIC -o .libs/svf_flex.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include/urjtag > -I../.. -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libusb-1.0 -Wall -Wmissing-prototypes -Wstrict-prototypes > -Wpointer-arith -g -O2 -Werror=implicit-function-declaration > "-ffile-prefix-map=/<>=." -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > svf.c -fPIC -DPIC -o .libs/svf.o > svf.c:1273:5: warning: no previous prototype for ‘program_jtag’ > [-Wmissing-prototypes] > 1273 | int program_jtag(int32_t fd, const char *drivername, const char > *bsdl_path, int64_t frequency) > | ^~~~ > svf.c: In function ‘program_jtag’: > svf.c:1286:19: error: implicit declaration of function ‘urj_tap_detect’ > [-Werror=implicit-function-declaration] > 1286 | int32_t err = urj_tap_detect(chain, 0); > | ^~ > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include/urjtag > -I../.. -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/libusb-1.0 -Wall -Wmissing-prototypes -Wstrict-prototypes > -Wpointer-arith -g -O2 -Werror=implicit-function-declaration > "-ffile-prefix-map=/<>=." -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > svf_bison.c -o svf_bison.o >/dev/null 2>&1 > cc1: some warnings being treated as errors > make[4]: *** [Makefile:520: svf.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/liburjtag_0.0~git20230703.491077f-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail
Bug#1065207: marked as done (gcl27: recent libc6-dev change causes XDR support to be dropped)
Your message dated Sat, 16 Mar 2024 03:42:12 + with message-id and subject line Bug#1065207: fixed in gcl27 2.7.0-21 has caused the Debian Bug report #1065207, regarding gcl27: recent libc6-dev change causes XDR support to be dropped to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcl27 Version: 2.7.0-20 Severity: serious User: debian-gl...@lists.debian.org Usertags: libtirpc-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev, which depends on libtirpc-dev, has been added to the libc6-dev package. The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1 NMU, as part of the 64-bit time_t transition. This causes gcl27 to disable the XDR support. Not fully sure what are the consequences. Therefore please either: - Add libnsl-dev as build dependency - Disable XDR support explicitly with --disable-xdr so that this feature does not depend on the packages installed on the system. The glibc change will likely be reverted in the short term, but given its a change we want to do for Trixie, this will only lower the severity of the bug. Regards Aurelien --- End Message --- --- Begin Message --- Source: gcl27 Source-Version: 2.7.0-21 Done: Camm Maguire We believe that the bug you reported is fixed in the latest version of gcl27, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Camm Maguire (supplier of updated gcl27 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Mar 2024 20:00:19 -0400 Source: gcl27 Architecture: source Version: 2.7.0-21 Distribution: unstable Urgency: high Maintainer: Camm Maguire Changed-By: Camm Maguire Closes: 1065207 Changes: gcl27 (2.7.0-21) unstable; urgency=high . * Version_2_7_0pre24 * Bug fix: "recent libc6-dev change causes XDR support to be dropped", thanks to Aurelien Jarno (Closes: #1065207). Checksums-Sha1: cdbd726fbece6a2731fe05ebf890e454955944fe 2302 gcl27_2.7.0-21.dsc a7e247948d22a2d9975a08a2e0b09eec9140d8d7 1091968 gcl27_2.7.0-21.debian.tar.xz c52302ac1b4214b5be35829c84c5658bbbc79c4e 8979 gcl27_2.7.0-21_source.buildinfo Checksums-Sha256: ecc58e5cf2ea189b919c4e86c683cf20bc0788002b4f831ae7c60243c30bceab 2302 gcl27_2.7.0-21.dsc bce6a5113d15098290f09283eca6f21bb9e4f81a2198abef78519cfb18e64dbe 1091968 gcl27_2.7.0-21.debian.tar.xz c4c23ccf175183ac08db1261c456bbd4320fc98e4a72477624b465bd5beb8bb5 8979 gcl27_2.7.0-21_source.buildinfo Files: 4501ba5f130c53539750b330c34bfa4c 2302 lisp optional gcl27_2.7.0-21.dsc 5601a613515db7f274afc8b25bc85123 1091968 lisp optional gcl27_2.7.0-21.debian.tar.xz 728b11c33ae42c636698dd822a55f9a5 8979 lisp optional gcl27_2.7.0-21_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmX049kACgkQuEXOUQ+b cU21EQ//V6Mgf/KCvDQgA8hqw28yJLb+quUpVDG1aw5PkDdS7STjXqZliL7v4mzc lIKPIA/o9Yhy2Rfe2pk1ttKP58ZRGgOGBe/x5wb5/QfT2luGoQ2qM7JqF2Om7/aG TV+EL91ypoa/l32EEiGHT3+CV6c4RqFOhm6+duWe76MASh+DNVJqbv5/41FvGF5I eMZyIt78Ek7AlbvzcuD+WMS6QsWDLyv34t4y02xfZ6eiEn/5OVArB9y9JPhQVzZs ajtcz74Le5+VXE/smKlT1SwmYk0LhdAHDSedNBf0SYVX02L3b9N6X1aVZmaqYvP6 4NP+EQhPAaF8mTDfmg1Mk43YthbK/xTMqu81pT87Sv22vitUKYUukJU6IBtsrQjK er2YTeA/KTf7IziVgEJKrZNpmrEKHa7DrR5N4Cq8WKnwR04sB1Os0j9UoLauQJI0 2KsVbTUaZxk1EFJWJqa2/579z713XivnXE1iHk9xVhfe/RFUAaUxk50ULJhwEJuM U8ZWAYkj7h0oMDIFFhQnU0JI/FKlpBuNJidJsspMRVPMY6xUk9FC8N7/lkVMb9f6 dfLQgwAHh3W5OSTFrUQOQQGEdOOpjrjOaATe6apJMyx8MzdUkECgDvCHTB0bXUWW fmbmwPb0pH3GoKJzp5x/39wiG59StI3O0CwPn6XeeeCBdlxVxI8= =p/sz -END PGP SIGNATURE- pgpVP4FqF9Diz.pgp Description: PGP signature --- End Message ---
Processed: closing 1042314
Processing commands for cont...@bugs.debian.org: > close 1042314 8.4.0-1 Bug #1042314 [src:puppetserver] puppetserver: FTBFS: actual: org.jruby.exceptions.NoMethodError: (NoMethodError) undefined method `load_defaults' for Gem::Specification:Class Marked as fixed in versions puppetserver/8.4.0-1. Bug #1042314 [src:puppetserver] puppetserver: FTBFS: actual: org.jruby.exceptions.NoMethodError: (NoMethodError) undefined method `load_defaults' for Gem::Specification:Class Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1042314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042314: closing 1042314
close 1042314 8.4.0-1 thanks I believe this bug is now fixed in the latest version of jruby and puppetserver uploaded to sid. Thanks, -- Jérôme
Bug#1066952: Defaulting to -Werror=implicit-function-declaration might not be a good idea
Hi! On Sat, 2024-03-16 at 02:18:22 +0200, Adrian Bunk wrote: > Package: dpkg-dev > Version: 1.22.6 > Severity: serious > X-Debbugs-Cc: Steve Langasek > 3. Code that does still compile with -Werror=implicit-function-declaration >but behaves differently, e.g. due to failing autoconf tests silently >disabling features > Debian has automation listing implicit-function-declaration warnings > in all packages already running for several years: > https://qa.debian.org/bls/bytag/W-implicit-declaration.html > My main worry is point 3, issues like #1066394. > > #1066394 was found due to causing a FTBFS in a different package, > but the more common case is likely that a program has some > feature/plugin disabled and this won't be spotted until much later. > > "Much later" might be after the release of trixie a user upgrading > to bookworm who uses this feature. > > Or it might result in a program silently using an insecure legacy codepath, > e.g. after a test for getentropy() failed. Not enabling this -Werror might imply ABI breakage for the time64 transition, which seems pretty terrible too. The way I see it, and given the timing, effort and preparation necessary for this transition, both options (enabling or not enabling the fatal warning) are potentially bad in their own way. But given that these are clearly bugs, that not enabling them can imply ABI breakage, that if things go according to plan (AFAIK) this will be made the default anyway with gcc-14, that we can track those down, and people have already been doing that for the Modern-C effort, see: https://fedoraproject.org/wiki/Changes/PortingToModernC https://wiki.gentoo.org/wiki/Modern_C_porting I think we might as well just cope with this anyway right away. > A large part of the packages in unstable might not get recompiled > between now and the release of trixie, creating the additional > issue that any such problem might occur only after a security update > or point release update if this is the next rebuild of the package > in trixie. AFAIUI (and I'd expect) the whole distribution needs to be rebuilt anyway as part of the time64 transition, otherwise the 32-bit ports that are affected by it, will not benefit from it. So I don't think this should be a concern. So I'm inclined to close this, and consider the current state, the less bad one. :/ Thanks, Guillem
Bug#1066956: blimps: FTBFS with -Werror=implicit-function-declaration
Source: blimps Version: 3.9+ds-1 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, blimps FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration /usr/bin/gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/blimps-3.9+ds=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wuninitialized -O2 -I../include -fpic -Wdate-time -D_FORTI FY_SOURCE=2 -c -o biassed_blocks_finder.o biassed_blocks_finder.c biassed_blocks_finder.c: In function 'parse': biassed_blocks_finder.c:101:6: error: implicit declaration of function 'plustospace' [-Werror=implicit-function-declaration] 101 | plustospace(entries[i].val); | ^~~ biassed_blocks_finder.c:102:6: error: implicit declaration of function 'unescape_url' [-Werror=implicit-function-declaration] 102 | unescape_url(entries[i].val); | ^~~~ biassed_blocks_finder.c: In function 'clean_temp_files': biassed_blocks_finder.c:120:3: warning: ignoring return value of 'system' declared with attribute 'warn_unused_result' [-Wunused-result] 120 | system(buf); | ^~~ ... Andreas
Bug#1066955: metis-edf: FTBFS with -Werror=implicit-function-declaration
Source: metis-edf Version: 4.1-2-4 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, metis-edf FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/metis-edf-4.1-2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -DPIC -I. -c initpart.c In file included from ./metis.h:35, from initpart.c:16: initpart.c: In function '__GrowBisection': ./rename.h:380:42: error: implicit declaration of function '__GKfree'; did you mean 'GKfree'? [-Werror=implicit-function-declaration] 380 | #define GKfree __GKfree | ^~~~ initpart.c:199:4: note: in expansion of macro 'GKfree' 199 |GKfree(, , , LTERM); |^~ cc1: some warnings being treated as errors make[3]: *** [Makefile:23: initpart.o] Error 1 Andreas
Bug#1066954: xtrs: FTBFS with html2test 2.x: Unrecognized command line option "-style"
Source: xtrs Version: 4.9d-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) Hi, xtrs FTBFS with the new html2test version in sid: html2text -nobs -style pretty cpmutil.html >cpmutil.txt Unrecognized command line option "-style", try "-help". make[1]: *** [Makefile:184: cpmutil.txt] Error 1 Andreas
Bug#1066953: pvpgn: FTBFS with -Werror=implicit-function-declaration
Source: pvpgn Version: 1.8.5-3 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) Hi, pvpgn FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/pvpgn-1.8.5=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DHAVE_CONFIG_H -DWITH_SQL_MYSQL -DWITH_SQL_PGSQL -DWITH_SQL_SQLITE 3 -DBNETD_DEFAULT_CONF_FILE=\"/etc/pvpgn/bnetd.conf\" -DD2CS_DEFAULT_CONF_FILE=\"/etc/pvpgn/d2cs.conf\" -DD2DBS_DEFAULT_CONF_FILE=\"/etc/pvpgn/d2dbs.conf\" -I"." -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include - fno-strict-aliasing -c bnetd/handle_irc.c -o bnetd/handle_irc.o bnetd/handle_irc.c: In function '_handle_whereto_command': bnetd/handle_irc.c:1391:8: error: implicit declaration of function 'trans_net' [-Werror=implicit-function-declaration] 1391 |trans_net(conn_get_addr(conn), , ); |^ bnetd/handle_irc.c: In function '_handle_join_command.part.0.isra': bnetd/handle_irc.c:1026:75: warning: '%s' directive writing up to 508 bytes into a region of size between 2 and 510 [-Wformat-overflow=] 1026 | sprintf(temp,"%s :%s",ircname,topic); | ^~ In file included from /usr/include/stdio.h:906, from ./common/util.h:26, from bnetd/handle_irc.c:23: In function 'sprintf', inlined from '_handle_join_command.part.0.isra' at bnetd/handle_irc.c:1026:8: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: '__builtin___sprintf_chk' output between 3 and 1019 bytes into a destination of size 512 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ Dependency check: bniutils bnetd/handle_irc.c: In function '_handle_joingame_command': bnetd/handle_irc.c:1683:75: warning: '%s' directive writing up to 508 bytes into a region of size between 2 and 510 [-Wformat-overflow=] 1683 | sprintf(temp,"%s :%s",ircname,topic); | ^~ In function 'sprintf', inlined from '_handle_joingame_command' at bnetd/handle_irc.c:1683:8: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: '__builtin___sprintf_chk' output between 3 and 1019 bytes into a destination of size 512 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ cc1: some warnings being treated as errors make[1]: *** [Makefile:740: bnetd/handle_irc.o] Error 1 Andreas
Bug#1066507: marked as done (kannel: FTBFS: configure: error: Either get a multithread-enabled SSL or configure with --disable-ssl)
Your message dated Sat, 16 Mar 2024 01:08:33 + with message-id and subject line Bug#1066507: fixed in kannel 1.4.5-14 has caused the Debian Bug report #1066507, regarding kannel: FTBFS: configure: error: Either get a multithread-enabled SSL or configure with --disable-ssl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kannel Version: 1.4.5-13 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 failed to build on amd64. Relevant part (hopefully): > checking for openssl/pem.h... yes > checking for openssl/ssl.h... yes > checking for openssl/err.h... yes > checking for openssl/hmac.h... yes > checking whether the OpenSSL library is multithread-enabled... no > configure: error: Either get a multithread-enabled SSL or configure with > --disable-ssl > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/kannel_1.4.5-13_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: kannel Source-Version: 1.4.5-14 Done: Guillem Jover We believe that the bug you reported is fixed in the latest version of kannel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated kannel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 23:52:28 +0100 Source: kannel Architecture: source Version: 1.4.5-14 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Guillem Jover Closes: 1045568 1049339 1066507 Changes: kannel (1.4.5-14) unstable; urgency=medium . * Adopt package as part of the Debian VoIP Team. (Closes: #1049339) * Run wrap-and-sort -sat. * Remove obsolete lsb-base dependency. * Add a debian/.gitignore file. * Fix FTBFS due to -Werror=implicit-function-declaration in OpenSSL configure check. (Closes: #1066507) * Fix FTBFS when building twice in a row. (Closes: #1045568) * Switch from pkg-config to pkgconf in build dependencies. * Update copyright file and remove old generation scaffolding. * Use spaces around Makefile variable assignments. * Conditionally append nocheck to DEB_BUILD_MAINT_OPTIONS instead of DEB_BUILD_OPTIONS which is a user controlled variable. * Switch to debhelper-compat level 13. * Update lintian-overrides. * Stop using pristine-tar, and rename git branches. Checksums-Sha1: c71ebf7d331952dab1c410ff3b4b534a3fdf79fc 2356 kannel_1.4.5-14.dsc c1b695d11dd37159fdf450aa4bc46b09191b0600 22840 kannel_1.4.5-14.debian.tar.xz d926e9f4264bfb1f07b91bddcc7157700dda5b9c 12550 kannel_1.4.5-14_amd64.buildinfo Checksums-Sha256: d3feb26c507a8f26b6374e771e19c8e0c5a03d9d9c0ec1804f1db1c38a952602 2356 kannel_1.4.5-14.dsc ba10e399140b8bac4c431cf58a334abbf8aca1e2f5bbbfc55967c63dc39ff533 22840 kannel_1.4.5-14.debian.tar.xz 5583cbdb2ca13a6c2f0d53e3db5b5e77963d361c79b79f8520c1840bb5c76ac8 12550 kannel_1.4.5-14_amd64.buildinfo Files: ce6ecbd87f1f3ccc9d74441487622940 2356 net optional kannel_1.4.5-14.dsc 202753998703b294a103bb2b029abf3e 22840 net optional kannel_1.4.5-14.debian.tar.xz 1952fcf1c3471517d2a5462755f2a7ba 12550 net
Bug#1066388: marked as done (dvbstream: FTBFS: mpegtools/ringbuffy.c:62:17: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 00:42:34 + with message-id and subject line Bug#1066388: fixed in dvbstream 0.6+cvs20090621-4 has caused the Debian Bug report #1066388, regarding dvbstream: FTBFS: mpegtools/ringbuffy.c:62:17: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvbstream Version: 0.6+cvs20090621-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -I ../DVB/include -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g > -Wall -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -o ts_filter > ts_filter.c > mpegtools/ringbuffy.c: In function ‘ring_write’: > mpegtools/ringbuffy.c:62:17: error: implicit declaration of function ‘memcpy’ > [-Werror=implicit-function-declaration] >62 | memcpy (rbuf->buffy+pos, data, rest); > | ^~ > mpegtools/ringbuffy.c:22:1: note: include ‘’ or provide a > declaration of ‘memcpy’ >21 | #include "ringbuffy.h" > +++ |+#include >22 | > mpegtools/ringbuffy.c:62:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] >62 | memcpy (rbuf->buffy+pos, data, rest); > | ^~ > mpegtools/ringbuffy.c:62:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c:67:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] >67 | memcpy (rbuf->buffy+pos, data, count); > | ^~ > mpegtools/ringbuffy.c:67:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c: In function ‘ring_peek’: > mpegtools/ringbuffy.c:92:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] >92 | memcpy(data, rbuf->buffy+pos, count); > | ^~ > mpegtools/ringbuffy.c:92:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c:94:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] >94 | memcpy(data, rbuf->buffy+pos, rest); > | ^~ > mpegtools/ringbuffy.c:94:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c: In function ‘ring_read’: > mpegtools/ringbuffy.c:117:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] > 117 | memcpy(data, rbuf->buffy+pos, count); > | ^~ > mpegtools/ringbuffy.c:117:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c:120:17: warning: incompatible implicit declaration of > built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch] > 120 | memcpy(data, rbuf->buffy+pos, rest); > | ^~ > mpegtools/ringbuffy.c:120:17: note: include ‘’ or provide a > declaration of ‘memcpy’ > mpegtools/ringbuffy.c: In function ‘ring_rest’: > mpegtools/ringbuffy.c:193:30: warning: variable ‘rest’ set but not used > [-Wunused-but-set-variable] > 193 | int diff, free, pos, rest; > | ^~~~ > ts_filter.c: In function ‘main’: > ts_filter.c:37:7: warning: statement with no effect [-Wunused-value] >37 | exit; > | ^~~~ > ts_filter.c:52:9: warning: statement with no effect [-Wunused-value] >52 | exit; > | ^~~~ > mpegtools/remux.c: In function ‘write_video_pes’: > mpegtools/remux.c:748:18: warning: variable ‘dts’ set but not used > [-Wunused-but-set-variable] > 748 | uint32_t dts = 0; > |
Bug#1063333: marked as done (cardpeek: Built version of cardpeek in Sid use lua5.3 and breaks lua's scripts. Need lua5.2 only.)
Your message dated Sat, 16 Mar 2024 00:28:56 + with message-id and subject line Bug#106: fixed in cardpeek 0.8.4-1.3 has caused the Debian Bug report #106, regarding cardpeek: Built version of cardpeek in Sid use lua5.3 and breaks lua's scripts. Need lua5.2 only. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cardpeek Version: 0.8.4-pacstall2 Severity: grave Tags: newcomer Justification: renders package unusable X-Debbugs-Cc: xdav...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed cardpeek from sid, try to use tachograph.lua script, give error line 335 * What exactly did you do (or not do) that was effective (or ineffective)? use apt-rdepend and see that cardpeek is built with lua5.3 on debian Sid Here, this is my newly built package. Built with lua5.2 works This package is very important for truck driver and need to work (there is no alternative on linux) Here my pacstall script if it can help : https://raw.githubusercontent.com/Xdavius/vortex-linux/main/vortex-repository/pacscript/packages/cardpeek/cardpeek.pacscript Regards (Sorry for my bad english) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.3-tkg-eevdf (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cardpeek depends on: ii curl 8.6.0-1 ii libgtk-3-dev 3.24.41-1 ii liblua5.2-0 5.2.4-3 ii libpcsclite-dev 2.0.1-1 cardpeek recommends no packages. cardpeek suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: cardpeek Source-Version: 0.8.4-1.3 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of cardpeek, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated cardpeek package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 23:31:12 + Source: cardpeek Architecture: source Version: 0.8.4-1.3 Distribution: unstable Urgency: medium Maintainer: Richard Ulrich Changed-By: Bastian Germann Closes: 106 Changes: cardpeek (0.8.4-1.3) unstable; urgency=medium . * Non-maintainer upload. * Revert back to lua 5.2. (Closes: #106) Checksums-Sha1: be96502d2b85a601a93145484106313e700ad11e 1756 cardpeek_0.8.4-1.3.dsc 84358b7db48ddab59ffcbed83575e25c08f1db7a 7316 cardpeek_0.8.4-1.3.debian.tar.xz ee5169d208454ec90e27d0d990316548fcc52ab0 15321 cardpeek_0.8.4-1.3_source.buildinfo Checksums-Sha256: 0ffa4a6310ad6766762f062a78e795729d23dea98ed05a1737314cfd5b4b4caf 1756 cardpeek_0.8.4-1.3.dsc 1259725d7f3b038078e7f8e5a8e5b711102652ff2cea5480ff242e9bfb304d4c 7316 cardpeek_0.8.4-1.3.debian.tar.xz 1dcdba7f0585bdd1fab37a27792cc3244890565ee8649e82f13285b8a75ebe10 15321 cardpeek_0.8.4-1.3_source.buildinfo Files: d347805fe6b582983ccce5b7542e382f 1756 utils optional cardpeek_0.8.4-1.3.dsc d9c413539a2762b1f85b274dfb555c84 7316 utils optional cardpeek_0.8.4-1.3.debian.tar.xz dfed15a4563809614c0c6c7d1979b074 15321 utils optional cardpeek_0.8.4-1.3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmX035IQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFHCkC/92VhGQRfxDW5vQu6LY1tPSfWBNboFhFPXl kQWLsbFduQR4SlIRJYCKCbRy2YLfNu6+BfI9XNlnL15IlWkmZxWGAzKWfU2zBBm9 zGxLQn3sFcCUYdPO6tJE36yYRL1sQHhfIRH2RX9+g56lxSt9OrmmSN+EDYMQDUjo Ir6giWr1O6mPgOvNgq7D5JfCiCAgKNOVrD7u92tHKcTrm5ho1dH9YSaGwA3tX9U/ EIVbTJg/RWdc4tE/Uz7ZbZdmofyN/i4qr09HOlTBgZa7vVmAo0iHnYDFm4q174rH
Bug#1066952: Defaulting to -Werror=implicit-function-declaration might not be a good idea
Package: dpkg-dev Version: 1.22.6 Severity: serious X-Debbugs-Cc: Steve Langasek There are at least 3 different ways how -Werror=implicit-function-declaration breaks packages: 1. Code that did emit implicit-function-declaration warnings during compilation before and does FTBFS now 2. Code that does FTBFS now due to other breakage caused by -Werror=implicit-function-declaration, e.g. in autoconf tests 3. Code that does still compile with -Werror=implicit-function-declaration but behaves differently, e.g. due to failing autoconf tests silently disabling features Cases from point 1 were always(?) bugs and it is good that they get fixed. The real-world effect of these bugs can be everywhere from "completely harmless" to "that was always broken". Debian has automation listing implicit-function-declaration warnings in all packages already running for several years: https://qa.debian.org/bls/bytag/W-implicit-declaration.html My main worry is point 3, issues like #1066394. #1066394 was found due to causing a FTBFS in a different package, but the more common case is likely that a program has some feature/plugin disabled and this won't be spotted until much later. "Much later" might be after the release of trixie a user upgrading to bookworm who uses this feature. Or it might result in a program silently using an insecure legacy codepath, e.g. after a test for getentropy() failed. A large part of the packages in unstable might not get recompiled between now and the release of trixie, creating the additional issue that any such problem might occur only after a security update or point release update if this is the next rebuild of the package in trixie.
Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.
On Wed, Mar 13, 2024 at 10:48:45AM -0100, Graham Inggs wrote: >... > Ubuntu is further along in the time_t transition, so further > investigation is needed as to which package causes the change in buld > behaviour of db5.3. >... It's dpkg, Ubuntu disabled -Werror=implicit-function-declaration cu Adrian
Bug#1063333: cardpeek: Built version of cardpeek in Sid use lua5.3 and breaks lua's scripts. Need lua5.2 only.
I am NMUing once again because I have caused this issue. The debdiff is attached.diff -Nru cardpeek-0.8.4/debian/changelog cardpeek-0.8.4/debian/changelog --- cardpeek-0.8.4/debian/changelog 2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/changelog 2024-03-15 23:31:12.0 + @@ -1,3 +1,10 @@ +cardpeek (0.8.4-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Revert back to lua 5.2. (Closes: #106) + + -- Bastian Germann Fri, 15 Mar 2024 23:31:12 + + cardpeek (0.8.4-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru cardpeek-0.8.4/debian/control cardpeek-0.8.4/debian/control --- cardpeek-0.8.4/debian/control 2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/control 2024-03-15 23:31:12.0 + @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Richard Ulrich -Build-Depends: debhelper-compat (= 10), libluabind-dev, libpcsclite-dev, libgtk-3-dev, libglib2.0-dev, doc-base, libssl-dev, liblua5.3-dev, libcurl4-openssl-dev +Build-Depends: debhelper-compat (= 10), libluabind-dev, libpcsclite-dev, libgtk-3-dev, libglib2.0-dev, doc-base, libssl-dev, liblua5.2-dev, libcurl4-openssl-dev Standards-Version: 3.9.6 Homepage: http://pannetrat.com/Cardpeek/ diff -Nru cardpeek-0.8.4/debian/patches/series cardpeek-0.8.4/debian/patches/series --- cardpeek-0.8.4/debian/patches/series2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/patches/series2024-03-15 23:31:12.0 + @@ -1,4 +1,2 @@ lintian_warnings lintian2 -lua5.3.patch -lua5.3-pkgconf.patch
Bug#1066944: marked as done (FTBFS on 32-bit arches with 64-bit time_t)
Your message dated Fri, 15 Mar 2024 23:49:02 +
with message-id
and subject line Bug#1066944: fixed in ulfius 2.7.15-2.2
has caused the Debian Bug report #1066944,
regarding FTBFS on 32-bit arches with 64-bit time_t
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ulfius
Version: 2.7.15-2.1
Severity: serious
Tags: ftbfs patch upstream fixed-upstream
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=ulfius=armel=2.7.15-2.1=1709168616=0
/<>/src/u_websocket.c: In function ‘ulfius_websocket_wait_close’:
/<>/src/u_websocket.c:2316:28: error: conversion from ‘long long
int’ to ‘long int’ may change value [-Werror=conversion]
2316 | abstime.tv_nsec += (((time_t)timeout%1000) * 100);
|^
>From 9457809a5321ca4a87f19fdc3f7f4af68e72afa8 Mon Sep 17 00:00:00 2001
From: Nicolas Mora
Date: Wed, 28 Feb 2024 20:36:03 -0500
Subject: [PATCH] Fix timespec.tv_nsec value conversion
---
src/u_websocket.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/u_websocket.c b/src/u_websocket.c
index efca309..771f872 100644
--- a/src/u_websocket.c
+++ b/src/u_websocket.c
@@ -2322,7 +2322,7 @@ int ulfius_websocket_wait_close(struct _websocket_manager * websocket_manager, u
if (timeout) {
clock_gettime(CLOCK_REALTIME, );
abstime.tv_sec += ((time_t)timeout / 1000);
-abstime.tv_nsec += (((time_t)timeout%1000) * 100);
+abstime.tv_nsec += long int)timeout)%1000) * 100);
if (abstime.tv_nsec > 9) {
abstime.tv_nsec %= 10;
abstime.tv_sec ++;
--
2.43.0
--- End Message ---
--- Begin Message ---
Source: ulfius
Source-Version: 2.7.15-2.2
Done: Amin Bandali
We believe that the bug you reported is fixed in the latest version of
ulfius, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Amin Bandali (supplier of updated ulfius package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 15 Mar 2024 16:10:29 -0400
Source: ulfius
Architecture: source
Version: 2.7.15-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian IoT Maintainers
Changed-By: Amin Bandali
Closes: 1066944
Changes:
ulfius (2.7.15-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/patches/fix-ftbfs-32bit-arches-64bit-time_t.patch: Add
upstream patch to fix FTBFS on 32-bit arches with 64-bit time_t.
(Closes: #1066944)
Checksums-Sha1:
de62b43e8e9962af18760df12869dbcb80b6dbd9 2423 ulfius_2.7.15-2.2.dsc
f89232e1c719e9b1b9dab5cccd8f9a8f6b1e2015 453596 ulfius_2.7.15.orig.tar.gz
127cd868b7cd368ebec998ddbc14cbd1be5518b9 9452 ulfius_2.7.15-2.2.debian.tar.xz
893a1282a8cce8cc8c9e168942408502da06462b 7100
ulfius_2.7.15-2.2_source.buildinfo
Checksums-Sha256:
49cec76d9d5e0befa69b8884019f94c23cc03f5bea8e38b971e29fab1ba42ec8 2423
ulfius_2.7.15-2.2.dsc
19cf789b2af1919b69f77c7701237bfc318a9781ec657b68fd4b6ffa9d53f111 453596
ulfius_2.7.15.orig.tar.gz
21919cc261fbcf0238c9f321353f41fea09ebebcf93ca23fc9122d9b1af78c54 9452
ulfius_2.7.15-2.2.debian.tar.xz
e299a3f066068c307be4d746431826c336cfd2b8ca8a88661fc268e15d3e4308 7100
ulfius_2.7.15-2.2_source.buildinfo
Files:
acc462d2f78855a37032795dcf067286 2423 devel optional ulfius_2.7.15-2.2.dsc
72101c6b274ea373ae48f8c29a5f7dcb 453596 devel optional
ulfius_2.7.15.orig.tar.gz
5f65aa0780414505a5bcedd52c1390ce 9452 devel optional
ulfius_2.7.15-2.2.debian.tar.xz
1e18d166c77fa1977a83a0f46fe7dee1 7100 devel optional
ulfius_2.7.15-2.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEObM8jZRIDS3cwqSYi0Sgzce5VvIFAmX0q1oACgkQi0Sgzce5
VvLwCw/9Elw1AIxqdrPrh9YZOhQRRxr74HZsCQi8/PnVOC5oooO3baGyef8eeixu
rBvcaxlSlMuWBYdpO9bD1pd3JAIu1L772VzXGwkVjbKjVzZMqlQch33uWshSBaRJ
HnWRg09XXb4OixXsk6cAPBlk2NPaUA/+Tmv2Pkipd27Wy1BrhkuVy43G0qhBfGO8
Bug#1065395: marked as done (spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space)
Your message dated Fri, 15 Mar 2024 23:44:17 + with message-id and subject line Bug#1065395: fixed in spirv-llvm-translator-16 16.0.0-7 has caused the Debian Bug report #1065395, regarding spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spirv-llvm-translator-14 Version: 14.0.0-10 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: issue Dear maintainers, Since a couple of days, our workers on s390x are dying because some test is filling up all disk space. Several days ago, I wrongly suspected src:fenics-dolfinx (bug #1064995) and added it to our reject-list. It didn't solve the issue, so today I spend more time on finding the culprit. Basically every spike above 40% in the graph [1] is a moment that we see issues like: Feb 28 05:38:18 ci-worker-s390x-01 debci[1738391]: gzip: /tmp/debci-worker-43383540-cNnbLE372K/autopkgtest-incoming/testing/s390x/f/fenics-dolfinx/43383540/log.gz: No space left on device Feb 28 05:38:18 ci-worker-s390x-01 debci[1424101]: E: Test for package fenics-dolfinx produced no exit code, aborting One of the suspects started to be spirv-llvm-translator-14, so I ran its autopkgtest manually, while logging disk use every 10 seconds (I started slightly delayed because I monitored the wrong partition first). As you can see below, during the test it grows from 17 GB (at the end) to its peak at 179 GB. That's not acceptable on our infrastructure. One file I happened to spot on the way was build/test/test_output/DebugInfo/Generic/Output/two-cus-from-same-file.ll.tmp: -rw-r--r-- 1 root root 41G Mar 3 19:18 two-cus-from-same-file.ll.tmp I have added spirv-llvm-translator-14 to our reject-list on s390x. As this seems to be a rather new issue, I'm wondering if it's due to: * Add build-needed autopkgtest for spirv-headers compat check. Or maybe something in the toolchain that broke on s390x? Paul [1] https://ci.debian.net/munin/ci-worker-s390x-01/ci-worker-s390x-01/df.html /dev/mapper/3600507630affd250004a 196G 40G 146G 22% /scratch /dev/mapper/3600507630affd250004a 196G 49G 138G 27% /scratch /dev/mapper/3600507630affd250004a 196G 57G 130G 31% /scratch /dev/mapper/3600507630affd250004a 196G 65G 122G 35% /scratch /dev/mapper/3600507630affd250004a 196G 66G 121G 36% /scratch /dev/mapper/3600507630affd250004a 196G 67G 120G 36% /scratch /dev/mapper/3600507630affd250004a 196G 70G 117G 38% /scratch /dev/mapper/3600507630affd250004a 196G 73G 114G 40% /scratch /dev/mapper/3600507630affd250004a 196G 76G 111G 41% /scratch /dev/mapper/3600507630affd250004a 196G 79G 108G 43% /scratch /dev/mapper/3600507630affd250004a 196G 83G 104G 45% /scratch /dev/mapper/3600507630affd250004a 196G 85G 101G 46% /scratch /dev/mapper/3600507630affd250004a 196G 88G 98G 48% /scratch /dev/mapper/3600507630affd250004a 196G 92G 95G 50% /scratch /dev/mapper/3600507630affd250004a 196G 95G 92G 51% /scratch /dev/mapper/3600507630affd250004a 196G 98G 89G 53% /scratch /dev/mapper/3600507630affd250004a 196G 101G 86G 54% /scratch /dev/mapper/3600507630affd250004a 196G 104G 83G 56% /scratch /dev/mapper/3600507630affd250004a 196G 107G 80G 58% /scratch /dev/mapper/3600507630affd250004a 196G 65G 122G 35% /scratch /dev/mapper/3600507630affd250004a 196G 65G 122G 35% /scratch /dev/mapper/3600507630affd250004a 196G 66G 121G 36% /scratch /dev/mapper/3600507630affd250004a 196G 68G 118G 37% /scratch /dev/mapper/3600507630affd250004a 196G 72G 115G 39% /scratch /dev/mapper/3600507630affd250004a 196G 75G 112G 41% /scratch /dev/mapper/3600507630affd250004a 196G 78G 109G 42% /scratch /dev/mapper/3600507630affd250004a 196G 81G 106G 44% /scratch /dev/mapper/3600507630affd250004a 196G 85G 102G 46% /scratch /dev/mapper/3600507630affd250004a 196G 87G 99G 47% /scratch /dev/mapper/3600507630affd250004a 196G 90G 96G 49%
Processed: Re: mozjs102: Fails to build with Python 3.12
Processing control commands: > forwarded -1 > https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide Bug #1066872 [src:mozjs102] mozjs102: Fails to build with Python 3.12 Set Bug forwarded-to-address to 'https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide'. -- 1066872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066872: mozjs102: Fails to build with Python 3.12
Control: forwarded -1 https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide Fedora has included two patches to fix this.
Bug#1066234: marked as done (php8.2: FTBFS: credits.c:130:9: error: implicit declaration of function ‘php_print_packaging_credits’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 23:18:12 +
with message-id
and subject line Bug#1066234: fixed in php8.2 8.2.16-2.1
has caused the Debian Bug report #1066234,
regarding php8.2: FTBFS: credits.c:130:9: error: implicit declaration of
function ‘php_print_packaging_credits’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php8.2
Version: 8.2.16-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
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 more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -Iext/standard/ -I/<>/ext/standard/
> -I/<>/ext-build/include -I/<>/ext-build/main
> -I/<> -I/<>/ext-build/ext/date/lib
> -I/<>/ext/date/lib -I/usr/include/libxml2
> -I/usr/include/x86_64-linux-gnu -I/usr/include/enchant-2
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/webp
> -I/usr/include/c-client -I/<>/ext/mbstring/libmbfl
> -I/<>/ext-build/ext/mbstring/libmbfl
> -I/<>/ext/mbstring/libmbfl/mbfl
> -I/<>/ext-build/ext/mbstring/libmbfl/mbfl
> -I/usr/include/postgresql -I/usr/include/pspell -I/usr/include/editline
> -I/usr/include/tidy -I/<>/ext-build/TSRM
> -I/<>/ext-build/Zend -I/<>/main
> -I/<>/Zend -I/<>/TSRM -I/<>/ext-build/
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/c-client
> -fno-common -Wstrict-prototypes -Wformat-truncation -Wlogical-op
> -Wduplicated-cond -Wno-clobbered -Wall -Wextra -Wno-strict-aliasing
> -Wno-unused-parameter -Wno-sign-compare -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -O2 -Wall -pedantic -fsigned-char
> -fno-strict-aliasing -DOPENSSL_SUPPRESS_DEPRECATED -g -fvisibility=hidden
> -Wimplicit-fallthrough=1 -DZEND_SIGNALS -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1
> -c /<>/ext/standard/ftp_fopen_wrapper.c -MMD -MF
> ext/standard/ftp_fopen_wrapper.dep -MT ext/standard/ftp_fopen_wrapper.lo
> -fPIC -DPIC -o ext/standard/ftp_fopen_wrapper.o >/dev/null 2>&1
> /<>/ext/standard/credits.c: In function ‘php_print_credits’:
> /<>/ext/standard/credits.c:130:9: error: implicit declaration of
> function ‘php_print_packaging_credits’ [-Werror=implicit-function-declaration]
> 130 | php_print_packaging_credits(flag, 0);
> | ^~~
> /<>/ext/standard/credits.c: At top level:
> /<>/ext/standard/credits.c:138:13: warning: conflicting types
> for ‘php_print_packaging_credits’; have ‘void(int, int)’
> 138 | PHPAPI void php_print_packaging_credits(int flag, int top) /* {{{ */
> | ^~~
> /<>/ext/standard/credits.c:130:9: note: previous implicit
> declaration of ‘php_print_packaging_credits’ with type ‘void(int, int)’
> 130 | php_print_packaging_credits(flag, 0);
> | ^~~
> /<>/ext/standard/credits.c: In function
> ‘php_print_packaging_credits’:
> /<>/ext/standard/credits.c:140:18: warning: logical ‘and’
> applied to non-boolean constant [-Wlogical-op]
> 140 | if (flag && PHP_CREDITS_PACKAGING) {
> | ^~
> x86_64-linux-gnu-gcc -Iext/standard/ -I/<>/ext/standard/
> -I/<>/ext-build/include -I/<>/ext-build/main
> -I/<> -I/<>/ext-build/ext/date/lib
> -I/<>/ext/date/lib -I/usr/include/libxml2
> -I/usr/include/x86_64-linux-gnu -I/usr/include/enchant-2
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/webp
> -I/usr/include/c-client -I/<>/ext/mbstring/libmbfl
> -I/<>/ext-build/ext/mbstring/libmbfl
> -I/<>/ext/mbstring/libmbfl/mbfl
> -I/<>/ext-build/ext/mbstring/libmbfl/mbfl
> -I/usr/include/postgresql -I/usr/include/pspell -I/usr/include/editline
> -I/usr/include/tidy -I/<>/ext-build/TSRM
> -I/<>/ext-build/Zend -I/<>/main
> -I/<>/Zend -I/<>/TSRM -I/<>/ext-build/
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/c-client
> -fno-common
Bug#1066850: Depends extraction not robust
now you're relying on the fact that the first dependency is the libmagic1XX one. That's not robust.
Bug#1065977: marked as done (libsearpc: FTBFS on arm{el,hf}: searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’; did you mean ‘writen’? [-Werror=implicit-function-declaration]
Your message dated Fri, 15 Mar 2024 22:59:35 +
with message-id
and subject line Bug#1066367: fixed in libsearpc
3.3.0+really3.3+git20230527.783141f-3.2
has caused the Debian Bug report #1066367,
regarding libsearpc: FTBFS on arm{el,hf}: searpc-demo-packet.h:40:34: error:
implicit declaration of function ‘write’; did you mean ‘writen’?
[-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsearpc
Version: 3.3.0+really3.3+git20230527.783141f-3.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=libsearpc=armhf=3.3.0%2Breally3.3%2Bgit20230527.783141f-3.1=1709152397=0
gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I../lib -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -Wall -pedantic -c -o demo-async-client.o
demo-async-client.c
test-object.c:3:55: warning: ISO C does not allow extra ‘;’ outside of a
function [-Wpedantic]
3 | G_DEFINE_TYPE (TestObject, test_object, G_TYPE_OBJECT);
| ^
In file included from searpc-demo-client.c:13:
searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
[-Wpedantic]
22 | char data[0];
| ^~~~
searpc-demo-packet.h: In function ‘writen’:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
| ^
| writen
searpc-demo-packet.h: In function ‘readn’:
searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’; did
you mean ‘readn’? [-Werror=implicit-function-declaration]
65 | if ( (nread = read(fd, buf, nleft)) < 0) {
| ^~~~
| readn
searpc-demo-client.c: In function ‘transport_callback’:
searpc-demo-client.c:34:13: warning: unused variable ‘ret’ [-Wunused-variable]
34 | int fd, ret;
| ^~~
searpc-demo-client.c: In function ‘rpc_string_test’:
searpc-demo-client.c:124:5: error: implicit declaration of function ‘close’;
did you mean ‘pclose’? [-Werror=implicit-function-declaration]
124 | close(sockfd);
| ^
| pclose
In file included from demo-async-client.c:10:
searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
[-Wpedantic]
22 | char data[0];
| ^~~~
searpc-demo-packet.h: In function ‘writen’:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
| ^
| writen
In file included from searpc-demo-client.c:14:
searpc-demo-client.c: In function ‘rpc_glist_test’:
test-object.h:7:38: error: implicit declaration of function
‘test_object_get_type’; did you mean ‘g_object_get_type’?
[-Werror=implicit-function-declaration]
7 | #define TEST_OBJECT_TYPE(test_object_get_type())
| ^~~~
searpc-demo-client.c:133:44: note: in expansion of macro ‘TEST_OBJECT_TYPE’
133 |TEST_OBJECT_TYPE, , 3,
|^~~~
searpc-demo-packet.h: In function ‘readn’:
searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’; did
you mean ‘readn’? [-Werror=implicit-function-declaration]
65 | if ( (nread = read(fd, buf, nleft)) < 0) {
| ^~~~
| readn
demo-async-client.c: In function ‘transport_send’:
searpc-demo-client.c: In function ‘main’:
demo-async-client.c:39:19: warning: unused variable ‘pac_ret’
[-Wunused-variable]
39 | packet *pac, *pac_ret;
| ^~~
Bug#1066367: marked as done (libsearpc: FTBFS: searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’; did you mean ‘writen’? [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 22:59:35 +
with message-id
and subject line Bug#1066367: fixed in libsearpc
3.3.0+really3.3+git20230527.783141f-3.2
has caused the Debian Bug report #1066367,
regarding libsearpc: FTBFS: searpc-demo-packet.h:40:34: error: implicit
declaration of function ‘write’; did you mean ‘writen’?
[-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsearpc
Version: 3.3.0+really3.3+git20230527.783141f-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
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 more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../lib
> -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wall -pedantic -c -o demo-async-client.o demo-async-client.c
> test-object.c:3:55: warning: ISO C does not allow extra ‘;’ outside of a
> function [-Wpedantic]
> 3 | G_DEFINE_TYPE (TestObject, test_object, G_TYPE_OBJECT);
> | ^
> In file included from demo-async-client.c:10:
> searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
> [-Wpedantic]
>22 | char data[0];
> | ^~~~
> searpc-demo-packet.h: In function ‘writen’:
> searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
> did you mean ‘writen’? [-Werror=implicit-function-declaration]
>40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
> | ^
> | writen
> searpc-demo-packet.h: In function ‘readn’:
> searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’;
> did you mean ‘readn’? [-Werror=implicit-function-declaration]
>65 | if ( (nread = read(fd, buf, nleft)) < 0) {
> | ^~~~
> | readn
> demo-async-client.c: In function ‘transport_send’:
> demo-async-client.c:39:19: warning: unused variable ‘pac_ret’
> [-Wunused-variable]
>39 | packet *pac, *pac_ret;
> | ^~~
> demo-async-client.c:37:13: warning: unused variable ‘ret’ [-Wunused-variable]
>37 | int fd, ret;
> | ^~~
> demo-async-client.c:37:9: warning: unused variable ‘fd’ [-Wunused-variable]
>37 | int fd, ret;
> | ^~
> demo-async-client.c: In function ‘main’:
> demo-async-client.c:149:5: error: implicit declaration of function ‘close’;
> did you mean ‘pclose’? [-Werror=implicit-function-declaration]
> 149 | close(sockfd);
> | ^
> | pclose
> demo-async-client.c:92:11: warning: unused variable ‘ret_str’
> [-Wunused-variable]
>92 | char *ret_str;
> | ^~~
> In file included from searpc-demo-client.c:13:
> searpc-demo-packet.h:22:10: warning: ISO C forbids zero-size array ‘data’
> [-Wpedantic]
>22 | char data[0];
> | ^~~~
> searpc-demo-packet.h: In function ‘writen’:
> searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
> did you mean ‘writen’? [-Werror=implicit-function-declaration]
>40 | if ( (nwritten = write(fd, ptr, nleft)) <= 0) {
> | ^
> | writen
> searpc-demo-packet.h: In function ‘readn’:
> searpc-demo-packet.h:65:31: error: implicit declaration of function ‘read’;
> did you mean ‘readn’? [-Werror=implicit-function-declaration]
>65 | if ( (nread = read(fd, buf, nleft)) < 0) {
> | ^~~~
> | readn
> searpc-demo-client.c: In function ‘transport_callback’:
> searpc-demo-client.c:34:13: warning: unused variable ‘ret’ [-Wunused-variable]
>34 | int fd, ret;
> |
Bug#1060407: Multiple security issues
On Wed, Jan 10, 2024 at 08:36:38PM +0100, Moritz Muehlenhoff wrote: > Source: gtkwave > Version: 3.3.116-1 > Severity: grave > Tags: security > X-Debbugs-Cc: Debian Security Team > > A very thorough security audit of gtkwave unveiled a total of 82 security > issues in gtkwave, all fixed in 3.3.118: > > CVE-2023-32650 CVE-2023-34087 CVE-2023-34436 CVE-2023-35004 > CVE-2023-35057 CVE-2023-35128 CVE-2023-35702 CVE-2023-35703 > CVE-2023-35704 CVE-2023-35955 CVE-2023-35956 CVE-2023-35957 > CVE-2023-35958 CVE-2023-35959 CVE-2023-35960 CVE-2023-35961 > CVE-2023-35962 CVE-2023-35963 CVE-2023-35964 CVE-2023-35969 > CVE-2023-35970 CVE-2023-35989 CVE-2023-35992 CVE-2023-35994 > CVE-2023-35995 CVE-2023-35996 CVE-2023-35997 CVE-2023-36746 > CVE-2023-36747 CVE-2023-36861 CVE-2023-36864 CVE-2023-36915 > CVE-2023-36916 CVE-2023-37282 CVE-2023-37416 CVE-2023-37417 > CVE-2023-37418 CVE-2023-37419 CVE-2023-37420 CVE-2023-37442 > CVE-2023-37443 CVE-2023-37444 CVE-2023-37445 CVE-2023-37446 > CVE-2023-37447 CVE-2023-37573 CVE-2023-37574 CVE-2023-37575 > CVE-2023-37576 CVE-2023-37577 CVE-2023-37578 CVE-2023-37921 > CVE-2023-37922 CVE-2023-37923 CVE-2023-38583 CVE-2023-38618 > CVE-2023-38619 CVE-2023-38620 CVE-2023-38621 CVE-2023-38622 > CVE-2023-38623 CVE-2023-38648 CVE-2023-38649 CVE-2023-38650 > CVE-2023-38651 CVE-2023-38652 CVE-2023-38653 CVE-2023-38657 > CVE-2023-39234 CVE-2023-39235 CVE-2023-39270 CVE-2023-39271 > CVE-2023-39272 CVE-2023-39273 CVE-2023-39274 CVE-2023-39275 > CVE-2023-39316 CVE-2023-39317 CVE-2023-39413 CVE-2023-39414 > CVE-2023-39443 CVE-2023-39444 > > Let's first fix unstable and then we can simple build 3.3.118 > for stable-security and oldstable-security as well. >... I looked at it for LTS, and there are at least two issues to consider: 1. GTK 2 versus GTK 3 Between bullseye and bookworm the UI switched from GTK 2 to GTK 3. The good news is that in buster both versions of 3.3.118 work with a small testcase. The bad news is that upstream has different tarballs for GTK 2 and GTK 3. 2. ghwdump moved to ghdl-tools The ghwdump tool (and manpage) was dropped in 3.3.110 from the upstream sources, and is now in ghdl-tools. My suggestion would be that I do: sid: 3.3.118-0.1 (or 3.3.118-1 if done by a maintainer) bookworm: 3.3.118-0.1~deb12u1 bullseye: 3.3.104+really3.3.118-0.1 (GTK 2 and with ghwdump re-added) buster: 3.3.104+really3.3.118-0.1~deb10u1 (or 3.3.98+really3.3.118-0.1) Any comments? Especially maintainer feedback would be appreciated. > Cheers, > Moritz cu Adrian
Bug#1066900: marked as done (g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes)
Your message dated Fri, 15 Mar 2024 22:24:56 + with message-id and subject line Bug#1066900: fixed in gobject-introspection 1.80.0-1 has caused the Debian Bug report #1066900, regarding g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gobject-introspection Version: 1.78.1-16 Severity: serious Justification: results in misbuilt packages X-Debbugs-Cc: debian-cr...@lists.debian.org When it converts GIR XML to binary typelib files, g-ir-compiler replaces abstract types such as int and gsize (size_t) with concrete types such as gint32 (int32_t) and guint64 (uint32_t). The way in which it does this depends on the type sizes discovered at configure time when compiling g-ir-compiler. This means that cross-compiling for an arm64 or riscv64 host on an amd64 build machine should be OK, but cross-compiling for armhf or i386 on amd64 will produce invalid typelibs. I am sorry that I didn't notice this sooner. A crude solution to this would be to revert gobject-introspection and gobject-introspection-bin to be Multi-Arch: no, so that building typelibs is no longer possible in cross-builds. [1] A more refined version of that would be to change the relationship between gobject-introspection and gobject-introspection-bin so that instead of the current arrangement where the dependency is on a virtual package gobject-introspection-linux-little-endian, it would be on a virtual package that also reflects the word size in use: gobject-introspection-linux-lp64-little-endian or similar. This would preserve the ability to cross-compile in only those situations where it would be correct. [2] A workaround to enable cross-compiling between word sizes would be to use the host architecture g-ir-compiler, and run it via qemu-user. Unfortunately this will greatly increase the amount of host-architecture code that needs to be run via emulation. In the short term, I'm going to do [1] or [2] as a matter of urgency, to ensure that Ubuntu 24.04 doesn't ship with faulty cross-tools that claim to work but actually do not. Any further improvement can be in-scope for #1030223 "gobject-introspection: make cross-compilation possible". If we do [2] then we will have to be extra-careful to distinguish between dissimilar ILP32 ABIs, because gobject-introspection currently hard-codes that it thinks time_t is long and off_t is size_t, both of which happen to be correct on LP64 and on i386, but neither of which is correct on an ILP32 architecture that has transitioned to large file support and 64-bit time_t (such as armel and armhf in 2024) or an ILP32 architecture that always had 64-bit off_t and time_t (such as x32). I apologise for having been insufficiently careful when enabling this feature. smcv --- End Message --- --- Begin Message --- Source: gobject-introspection Source-Version: 1.80.0-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gobject-introspection, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gobject-introspection package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Mar 2024 15:32:45 + Source: gobject-introspection Architecture: source Version: 1.80.0-1 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1065332 1066900 Changes: gobject-introspection (1.80.0-1) experimental; urgency=medium . * New upstream stable release * Merge packaging changes from unstable - dh_girepository: Avoid generating a dependency on libgirepository1.0-dev (Closes: #1065332) - Use host g-ir-compiler (possibly wrapped with qemu-user) when cross-compiling, since the build architecture g-ir-compiler has built-in knowledge of type sizes which is not necessarily correct
Bug#1066138: marked as done (gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration)
Your message dated Fri, 15 Mar 2024 22:23:49 +
with message-id
and subject line Bug#1066138: fixed in gnupg1 1.4.23-2
has caused the Debian Bug report #1066138,
regarding gnupg1: fails to build gpgkeys_ldap, probably due to
-Werror=implicit-function-declaration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg2
Version: 2.2.40-1.1
Severity: serious
Justification: ftbfs
X-Debbugs-Cc: t...@mirbsd.de
Trying to binNMU gnupg2 to make it installable during t64 transition,
I notice the following configury output:
[…]
checking for library containing dn_skipname... none required
checking whether the resolver is usable... yes
checking whether LDAP via "-lldap" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lwldap32" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking for ber_free in -llber... yes
configure: WARNING:
***
*** Building without LDAP support.
*** No CRL access or X.509 certificate search available.
***
checking for sendmail... no
[…]
This matches the following failure mode at the end of the build:
19:50⎜ I can't build gnugpg2:
19:50⎜dh_install -a -O--builddirectory=build
19:50⎜ dh_install: warning: Cannot find (any matches for)
⎜"debian/tmp/usr/lib/gnupg/dirmngr_ldap" (tried in ., debian/tmp)
19:50⎜ dh_install: warning: dirmngr missing files:
⎜debian/tmp/usr/lib/gnupg/dirmngr_ldap
19:50⎜ dh_install: error: missing files, aborting
The cause in config.log:
configure:11580: checking whether LDAP via "-lldap" is present and sane
configure:11600: gcc -o conftest -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/tmp/buildd/gnupg2-2.2.40=.
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now conftest.c -lldap
>&5
conftest.c: In function 'main':
conftest.c:96:1: error: implicit declaration of function 'ldap_open'; did you
mean 'ldap_turn'? [-Werror=implicit-function-declaration]
96 | ldap_open("foobar",1234);
| ^
| ldap_turn
cc1: some warnings being treated as errors
configure:11600: $? = 1
configure: failed program was:
[…]
| /* end confdefs.h. */
|
| #ifdef _WIN32
| #include
| #include
| #else
| #include
| #endif
|
| int
| main (void)
| {
| ldap_open("foobar",1234);
| ;
| return 0;
| }
configure:11608: result: no
Prototypes are now mandatory, both for C23 and because the t64 transition
can only work if prototypes are properly used.
bye,
//mirabilos
--- End Message ---
--- Begin Message ---
Source: gnupg1
Source-Version: 1.4.23-2
Done: Andreas Metzler
We believe that the bug you reported is fixed in the latest version of
gnupg1, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler (supplier of updated gnupg1 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 15 Mar 2024 19:48:08 +0100
Source: gnupg1
Architecture: source
Version: 1.4.23-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG-Maintainers
Changed-By: Andreas Metzler
Closes: 1066138
Changes:
gnupg1 (1.4.23-2) unstable; urgency=medium
.
* Team upload.
* 0007-build-Use-LDAP_DEPRECATED-to-detect-ldap-library.patch Fix FTBFS with
-Werror=implicit-function-declaration. Closes: #1066138
* Includes multi-arch hints by Debian janitor.
Checksums-Sha1:
26da2c41929f329568954224af7ef736237ef488 2237 gnupg1_1.4.23-2.dsc
856182204279e38f8953fd1cbd771f0b7b5d36d1 34020
Bug#1065599: marked as done (gcc-14-offload-nvptx: openmp offload compile fails due to missing libgomp.spec)
Your message dated Fri, 15 Mar 2024 22:14:37 + with message-id and subject line Bug#1065599: fixed in gcc-14 14-20240315-1 has caused the Debian Bug report #1065599, regarding gcc-14-offload-nvptx: openmp offload compile fails due to missing libgomp.spec to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-14-offload-nvptx Version: 14-20240303-1 Severity: grave Justification: renders package unusable Dear Maintainer, due to a different organisation in file installation with respect to gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the following: x86_64-linux-gnu-accel-nvptx-none-gcc-14: fatal error: cannot read spec file 'libgomp.spec': No such file or directory compilation terminated. nvptx mkoffload: fatal error: x86_64-linux-gnu-accel-nvptx-none-gcc-14 returned 1 exit status compilation terminated. lto-wrapper: fatal error: /usr/libexec/gcc/x86_64-linux-gnu/14//accel/nvptx-none/mkoffload returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed While gcc-12-offload-nvptx installed executables, includes, and libs under /usr/lib/gcc/x86_64-linux-gnu/12/accel/nvptx-none, and found them, gcc-14-offload-nvptx does not appear to install them anywhere, nor to depend on any other separate package that does. This effectively renders the package unusable. Thanks in advance, best regards Giacomo Mulas *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.7-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gcc-14-offload-nvptx depends on: ii gcc-14 14-20240303-1 ii gcc-14-base14-20240303-1 ii libc6 2.37-15.1 ii libc6-dev 2.37-15.1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii libgomp-plugin-nvptx1 14-20240303-1 ii libmpc31.3.1-1+b2 ii libmpfr6 4.2.1-1+b1 ii libzstd1 1.5.5+dfsg2-2 ii nvptx-tools0.20230904-1 ii zlib1g 1:1.3.dfsg-3.1 gcc-14-offload-nvptx recommends no packages. gcc-14-offload-nvptx suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gcc-14 Source-Version: 14-20240315-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-14, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-14 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 20:35:12 +0100 Source: gcc-14 Architecture: source Version: 14-20240315-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1061371 1065458 1065599 1066932 Changes: gcc-14 (14-20240315-1) unstable; urgency=medium . * Snapshot, taken from the trunk 20240315. . * Fix installation of the amdgcn offload compiler. Closes: #1065458. * Fix installation of the nvptx offload compiler. Closes: #1065599. * Add loong64 bits for the gcc-multilib-multiarch patch. Closes: #1061371. * Enable Modula-2 on the Hurd (Samuel Thibault). Closes: #1066932. Checksums-Sha1: 77b5e95b03d53d08e6f347a79b2127193fcd1f09
Bug#1064967: fontforge DSA (was: Re: Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1)
On Wed, Mar 13, 2024 at 08:39:47PM +0100, Salvatore Bonaccorso wrote:
> Hi Adrian,
Hi Salvatore,
> On Fri, Mar 08, 2024 at 02:03:55AM +0200, Adrian Bunk wrote:
> > Control: tags 1064967 + patch
> > Control: tags 1064967 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.
> >
> > @Security team:
> > If wanted, I could afterwards also prepare (pu or DSA) updates for
> > bookworm and bullseye.
>
> We came to the conclusion that it warrants a DSA. Could you prepare
> debdiffs for bookworm-security and bulseye-security?
the debdiffs are attached.
Tested on both releases with the PoCs from [1] and that opening a normal
compressed font still works.
> Regards,
> Salvatore
cu
Adrian
[1]
https://www.canva.dev/blog/engineering/fonts-are-still-a-helvetica-of-a-problem/
diffstat for fontforge-20201107~dfsg fontforge-20201107~dfsg
changelog | 10
patches/0001-fix-splinefont-shell-command-injection-5367.patch | 181
++
patches/series |1
3 files changed, 192 insertions(+)
diff -Nru fontforge-20201107~dfsg/debian/changelog
fontforge-20201107~dfsg/debian/changelog
--- fontforge-20201107~dfsg/debian/changelog2021-01-15 17:55:46.0
+0200
+++ fontforge-20201107~dfsg/debian/changelog2024-03-15 22:56:38.0
+0200
@@ -1,3 +1,13 @@
+fontforge (1:20201107~dfsg-4+deb11u1) bullseye-security; urgency=medium
+
+ * Non-maintainer upload.
+ * CVE-2024-25081: Spline Font command injection via crafted filenames
+ * CVE-2024-25082: Spline Font command injection via crafted archives
+or compressed files
+ * Closes: #1064967
+
+ -- Adrian Bunk Fri, 15 Mar 2024 22:56:38 +0200
+
fontforge (1:20201107~dfsg-4) unstable; urgency=medium
* Rename extended to extendeddbl to avoid FTBFS on Hurd.
diff -Nru
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
---
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
1970-01-01 02:00:00.0 +0200
+++
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
2024-03-15 22:48:11.0 +0200
@@ -0,0 +1,181 @@
+From 216eb14b558df344b206bf82e2bdaf03a1f2f429 Mon Sep 17 00:00:00 2001
+From: Peter Kydas
+Date: Tue, 6 Feb 2024 20:03:04 +1100
+Subject: fix splinefont shell command injection (#5367)
+
+---
+ fontforge/splinefont.c | 125 +
+ 1 file changed, 90 insertions(+), 35 deletions(-)
+
+diff --git a/fontforge/splinefont.c b/fontforge/splinefont.c
+index 239fdc035..647daee10 100644
+--- a/fontforge/splinefont.c
b/fontforge/splinefont.c
+@@ -788,11 +788,14 @@ return( name );
+
+ char *Unarchive(char *name, char **_archivedir) {
+ char *dir = getenv("TMPDIR");
+-char *pt, *archivedir, *listfile, *listcommand, *unarchivecmd,
*desiredfile;
++char *pt, *archivedir, *listfile, *desiredfile;
+ char *finalfile;
+ int i;
+ int doall=false;
+ static int cnt=0;
++gchar *command[5];
++gchar *stdoutresponse = NULL;
++gchar *stderrresponse = NULL;
+
+ *_archivedir = NULL;
+
+@@ -827,18 +830,30 @@ return( NULL );
+ listfile = malloc(strlen(archivedir)+strlen("/" TOC_NAME)+1);
+ sprintf( listfile, "%s/" TOC_NAME, archivedir );
+
+-listcommand = malloc( strlen(archivers[i].unarchive) + 1 +
+- strlen( archivers[i].listargs) + 1 +
+- strlen( name ) + 3 +
+- strlen( listfile ) +4 );
+-sprintf( listcommand, "%s %s %s > %s", archivers[i].unarchive,
+- archivers[i].listargs, name, listfile );
+-if ( system(listcommand)!=0 ) {
+- free(listcommand); free(listfile);
+- ArchiveCleanup(archivedir);
+-return( NULL );
+-}
+-free(listcommand);
++command[0] = archivers[i].unarchive;
++command[1] = archivers[i].listargs;
++command[2] = name;
++command[3] = NULL; // command args need to be NULL-terminated
++
++if ( g_spawn_sync(
++ NULL,
++ command,
++ NULL,
++ G_SPAWN_SEARCH_PATH,
++ NULL,
++ NULL,
++ ,
++ ,
++ NULL,
++ NULL
++ ) == FALSE) { // did not successfully execute
++ ArchiveCleanup(archivedir);
++ return( NULL );
++}
++// Write out the listfile to be read in later
++FILE *fp = fopen(listfile, "wb");
++fwrite(stdoutresponse, strlen(stdoutresponse), 1, fp);
++fclose(fp);
+
+ desiredfile =
Bug#1066742: marked as done (barectf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 15 Mar 2024 21:44:05 +
with message-id
and subject line Bug#1066742: fixed in barectf 3.1.2-2
has caused the Debian Bug report #1066742,
regarding barectf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barectf
Version: 3.1.2-1
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 failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_barectf
> * Building wheel...
> Successfully built barectf-3.1.2-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build"
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_barectf
> * Building wheel...
> Successfully built barectf-3.1.2-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_barectf/build; python3.12 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.12.2, pytest-8.0.2, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_barectf/build
> plugins: xdist-3.4.0
> collected 1 item / 32 errors
>
> ERRORS
>
> ___ ERROR collecting tests/config/yaml/2/configs/fail/clock
>
> /usr/lib/python3/dist-packages/_pytest/nodes.py:153: in _create
> return super().__call__(*k, **kw)
> E TypeError: _YamlFile.__init__() got an unexpected keyword argument 'path'
>
> During handling of the above exception, another exception occurred:
> /usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__
> return self._hookexec(self.name, self._hookimpls.copy(), kwargs,
> firstresult)
> /usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
> return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
> tests/config/yaml/conftest.py:64: in pytest_collect_file
> return _YamlFileFail.from_parent(parent, fspath=path, name=name)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:660: in from_parent
> return super().from_parent(parent=parent, fspath=fspath, path=path, **kw)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:276: in from_parent
> return cls._create(parent=parent, **kw)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:168: in _create
> return super().__call__(*k, **known_kw)
> tests/config/yaml/conftest.py:102: in __init__
> super().__init__(parent=parent, fspath=fspath)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:615: in __init__
> path = _imply_path(type(self), path, fspath=fspath)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:109: in _imply_path
> warnings.warn(
> E pytest.PytestRemovedIn8Warning: The (fspath: py.path.local) argument to
> _YamlFileFail is deprecated. Please use the (path: pathlib.Path) argument
> instead.
> E See
> https://docs.pytest.org/en/latest/deprecations.html#fspath-argument-for-node-constructors-replaced-with-pathlib-path
> ___ ERROR collecting tests/config/yaml/2/configs/fail/config
> ___
> /usr/lib/python3/dist-packages/_pytest/nodes.py:153: in _create
> return super().__call__(*k, **kw)
> E TypeError: _YamlFile.__init__() got an unexpected keyword argument 'path'
>
> During handling of the above exception, another exception occurred:
> /usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__
> return self._hookexec(self.name, self._hookimpls.copy(), kwargs,
> firstresult)
>
Bug#1066763: marked as done (liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Fri, 15 Mar 2024 22:42:34 +0100
with message-id
and subject line Re: Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8
test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
has caused the Debian Bug report #1066763,
regarding liferea: FTBFS: dh_auto_test: error: make -j8 test
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liferea
Version: 1.15.4-1
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 failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/src/tests'
> make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> rule.
> echo parse_html favicon parse_date parse_rss parse_xml social |\
> sed "s/^/.\//;s/ / \&\& .\//g" |\
> xargs -I{} sh -c "{}"
> TAP version 13
> # random seed: R02S6f4f289a9f9f0f104f9d56655caaa00a
> 1..23
> # Start of html tests
> ok 1 /html/auto_discover_link_xml
> ok 2 /html/auto_discover_link_xml_base_url
> ok 3 /html/auto_discover_link_rss
> ok 4 /html/auto_discover_link_rdf
> ok 5 /html/auto_discover_link_atom
> ok 6 /html/auto_discover_link_atom2
> ok 7 /html/auto_discover_link_broken_tag
> ok 8 /html/auto_discover_link_garbage
> ok 9 /html/auto_discover_link_xml_atom
> ok 10 /html/auto_discover_link_xml_atom2
> ok 11 /html/auto_discover_link_xml_atom3
> ok 12 /html/auto_discover_link_xml_rce
> ok 13 /html/html5_extract_article
> ok 14 /html/html5_extract_article_main
> ok 15 /html/html5_extract_article_main2
> ok 16 /html/html5_extract_article_micro_format
> ok 17 /html/html5_extract_article_cms_content_id
> ok 18 /html/html5_extract_article_missing
> ok 19 /html/html5_extract_article_empty_tags
> ok 20 /html/html5_extract_article_empty_tags_nested
> ok 21 /html/html5_extract_article_self_closed_tags
> ok 22 /html/html5_extract_article_self_closed_tags_nested
> ok 23 /html/html5_extract_article_strip_inline_code
> # End of html tests
> TAP version 13
> # random seed: R02Sc17ce5d075f8e71d410497e1f12f6030
> 1..6
> # Start of favicon tests
> ok 1 /favicon/tc1
> ok 2 /favicon/tc2
> ok 3 /favicon/tc3
> ok 4 /favicon/tc4
> ok 5 /favicon/tc5
> ok 6 /favicon/tc6
> # End of favicon tests
> TAP version 13
> # random seed: R02S8bfaa9583c8d2c81eff3aa8e51ee7110
> 1..18
> # Start of parse_date tests
> # Start of rfc822 tests
> ok 1 /parse_date/rfc822/empty
> ok 2 /parse_date/rfc822/nonsense
> ok 3 /parse_date/rfc822/full
> ok 4 /parse_date/rfc822/day
> ok 5 /parse_date/rfc822/time
> ok 6 /parse_date/rfc822/min
> ok 7 /parse_date/rfc822/timezone
> ok 8 /parse_date/rfc822/year2_1
> ok 9 /parse_date/rfc822/year2_2
> ok 10 /parse_date/rfc822/year2_3
> ok 11 /parse_date/rfc822/wrong
> # End of rfc822 tests
> # Start of iso8601 tests
> ok 12 /parse_date/iso8601/empty
> ok 13 /parse_date/iso8601/nonsense
> ok 14 /parse_date/iso8601/full
> ok 15 /parse_date/iso8601/day
> ok 16 /parse_date/iso8601/Z
> ok 17 /parse_date/iso8601/wrong
> ok 18 /parse_date/iso8601/notz
> # End of iso8601 tests
> # End of parse_date tests
> TAP version 13
> # random seed: R02S7e7ce3b2870e6446dbb36d78ec11c8da
> 1..2
> # Start of rss tests
> ok 1 /rss/feed1
> ok 2 /rss/feed2_rce
> # End of rss tests
> TAP version 13
> # random seed: R02S536f22548cffbfb87e9cbab9897a5edf
> 1..10
> # Start of parse_xml tests
> ok 1 /parse_xml/xpath_find_empty_doc
> ok 2 /parse_xml/xpath_find_empty_doc2
> ok 3 /parse_xml/xpath_find_real_doc
> ok 4 /parse_xml/xpath_find_atom_feed
> # End of parse_xml tests
> # Start of xhtml_strip tests
> ok 5 /xhtml_strip/onload
> ok 6 /xhtml_strip/meta
> ok 7 /xhtml_strip/wbr
> ok 8 /xhtml_strip/extra_body
> ok 9 /xhtml_strip/script
> ok 10 /xhtml_strip/iframe
> # End of xhtml_strip tests
> TAP version 13
> # random seed: R02S03d33d3be1eba1f96e3466469276211a
> 1..4
> # Start of social tests
> ok 1 /social/url
> ok 2 /social/url2
> ok 3 /social/title1
> ok 4 /social/title2
> # End of social tests
> ./test_a11y.sh
> ../../glade/auth.ui: WARNING: 'GtkLabel' 'prompt' does not specify what it
> labels within 'GtkDialog' 'auth'
> ../../glade/enclosure_handler.ui: WARNING: 'GtkLabel' 'label204' does not
> specify what it labels within 'GtkDialog' 'enclosure_handler'
> ../../glade/enclosure_handler.ui: WARNING: 'GtkLabel' 'enc_type_label' does
> not specify what it labels within
Bug#1063951: marked as done (barectf: autopkgtest regression with pytest 8)
Your message dated Fri, 15 Mar 2024 21:44:05 + with message-id and subject line Bug#1063951: fixed in barectf 3.1.2-2 has caused the Debian Bug report #1063951, regarding barectf: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: barectf Version: 3.1.2-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: pytest-8 Dear maintainer, your package has a autopkgtest regression with pytest 8. Typically, packages will start failing if they - have deprecation warnings of type PytestRemovedIn8Warning, or - assume a particular pytest stdout/stderr output which might have changed, or - rely on implementation details of the pytest test collector, in particular the pytest.Package class, which has been redesigned for pytest 8. Please refer to the upstream changelog [1] for a complete list of breaking changes and the pytest (pseudo-)excuses [2] related to your package for details of the regression. It is possible that the autopkgtest regression is not directly caused by barectf, but by one of its dependencies. In that case, feel free to reassign the bug and mark your package as affected, but do not close the bug until the autopkgtest passes. Cheers Timo [1] https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023- 12-30 [2] https://qa.debian.org/excuses.php?experimental=1=pytest --- End Message --- --- Begin Message --- Source: barectf Source-Version: 3.1.2-2 Done: Michael Jeanson We believe that the bug you reported is fixed in the latest version of barectf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated barectf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 15:55:53 -0400 Source: barectf Architecture: source Version: 3.1.2-2 Distribution: unstable Urgency: medium Maintainer: Michael Jeanson Changed-By: Michael Jeanson Closes: 1063951 1066742 Changes: barectf (3.1.2-2) unstable; urgency=medium . * [2375fb4] Disable pytest8 deprecation warnings (Closes: #1063951) - Also (Closes: #1066742) built with pytest8 * [06b29a2] Bump standard to 4.6.2, no changes necessary Checksums-Sha1: 95aee9716fe5afc3a99d12c1e919a99f9b85037e 2254 barectf_3.1.2-2.dsc 53eacc31cc2432c9f79b84e7c1e658509c8035da 267773 barectf_3.1.2.orig.tar.gz 6e99d31bebb43d3d1586fe3d25e8b872048b5c0d 4208 barectf_3.1.2-2.debian.tar.xz 764e8523c7b4e355099bfdb220e27cf2177b3431 8476 barectf_3.1.2-2_source.buildinfo Checksums-Sha256: 606bab128b2adf0693fe963bf0f0ffc5f17b1b6419080b4d7b268fc7d4e35846 2254 barectf_3.1.2-2.dsc bad30bee4370408a101e6cca7af325cf9875e1a1a0fd712219603f44ac2e7ec8 267773 barectf_3.1.2.orig.tar.gz 631bf39a97269241836cb498237e8ad2b5221de16223f42745149cb1eeb9a805 4208 barectf_3.1.2-2.debian.tar.xz 46aa3ada85ca85a6186ea35b245b5e0b8f4e9a0331a6164a3b150a54b6ba4b60 8476 barectf_3.1.2-2_source.buildinfo Files: ee47e292257f30d75d85063145131b7d 2254 python optional barectf_3.1.2-2.dsc 6d2b2e24ecac4c1081685fd802552105 267773 python optional barectf_3.1.2.orig.tar.gz 58c37ef5b5b78acbd3346ed9c07ee284 4208 python optional barectf_3.1.2-2.debian.tar.xz 820ba25dd9064de368681ea2b404953f 8476 python optional barectf_3.1.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAmX0qZcUHG1qZWFuc29u QGRlYmlhbi5vcmcACgkQhlYfRSGA/P4exA//YzcpE/yvJIvTaovwp12oOsnfLxez vfrljwrkNszTc1a0YclZy9Gn98yugksx1sXZ8dX+IIz/WU5K2Y4Iba0UpTR6T9/Y TnZCtKsJ5Q6QZJl94L4M5K3+Zv/VRZdPZCOM1PdK/CTv3yBpsoU+Iho2vH1ZoQdO jJLSuu7MOy2BwHLCrr/lSmlP6ejDS9r+n1kDba8Tj9a/bcbTrdQW/ORbn2YOtFEZ TZ53kVoowk2FcWdxfFw5YxPXsHb2M0pBe2UktDB5YVxpGiC0R/wRpH2J2JpxIfn+ zrGvqSDyFixJrOPu2ans5QwGHc1xVJlTA2hXgzyu79p127ruDIIEF8B7FIZhm7fB +P/ts51NhS0jFRWOm9BVN5VCx1K1Ttmze5Y48MvmWwzj0wgBku2VZRqY/zm6S3ie ZF2R1rjpaJk+2jX+XC0ubKiZxGSdhFh7SNNd1oDpEiWQ6x78M9jYj8R+bu1V8msU
Bug#1066382: marked as done (xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-f
Your message dated Fri, 15 Mar 2024 20:22:20 + with message-id and subject line Bug#1066382: fixed in xserver-xorg-video-nouveau 1:1.0.17-3 has caused the Debian Bug report #1066382, regarding xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xserver-xorg-video-nouveau Version: 1:1.0.17-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri > -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau > -I/usr/include/libdrm -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c -o > nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c > ../../src/nv_driver.c: In function ‘NVScreenInit’: > ../../src/nv_driver.c:1451:23: error: implicit declaration of function > ‘wfbScreenInit’; did you mean ‘fbScreenInit’? > [-Werror=implicit-function-declaration] > 1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX, > | ^ > | fbScreenInit > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm > -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c > ../../src/nv04_exa.c -fPIC -DPIC -o .libs/nv04_exa.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm > -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c > ../../src/nv04_xv_ovl.c -fPIC -DPIC -o .libs/nv04_xv_ovl.o > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri > -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau > -I/usr/include/libdrm -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c -o > nv04_xv_blit.lo ../../src/nv04_xv_blit.c > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri > -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau > -I/usr/include/libdrm -g -O2
Bug#1066944: FTBFS on 32-bit arches with 64-bit time_t
Source: ulfius
Version: 2.7.15-2.1
Severity: serious
Tags: ftbfs patch upstream fixed-upstream
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=ulfius=armel=2.7.15-2.1=1709168616=0
/<>/src/u_websocket.c: In function ‘ulfius_websocket_wait_close’:
/<>/src/u_websocket.c:2316:28: error: conversion from ‘long long
int’ to ‘long int’ may change value [-Werror=conversion]
2316 | abstime.tv_nsec += (((time_t)timeout%1000) * 100);
|^
>From 9457809a5321ca4a87f19fdc3f7f4af68e72afa8 Mon Sep 17 00:00:00 2001
From: Nicolas Mora
Date: Wed, 28 Feb 2024 20:36:03 -0500
Subject: [PATCH] Fix timespec.tv_nsec value conversion
---
src/u_websocket.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/u_websocket.c b/src/u_websocket.c
index efca309..771f872 100644
--- a/src/u_websocket.c
+++ b/src/u_websocket.c
@@ -2322,7 +2322,7 @@ int ulfius_websocket_wait_close(struct _websocket_manager * websocket_manager, u
if (timeout) {
clock_gettime(CLOCK_REALTIME, );
abstime.tv_sec += ((time_t)timeout / 1000);
-abstime.tv_nsec += (((time_t)timeout%1000) * 100);
+abstime.tv_nsec += long int)timeout)%1000) * 100);
if (abstime.tv_nsec > 9) {
abstime.tv_nsec %= 10;
abstime.tv_sec ++;
--
2.43.0
Bug#1066220: marked as done (mono: FTBFS: gc_dlopen.c:52:30: error: implicit declaration of function ‘GC_collection_in_progress’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 19:47:44 +
with message-id
and subject line Bug#1066220: fixed in mono 6.8.0.105+dfsg-3.6
has caused the Debian Bug report #1066220,
regarding mono: FTBFS: gc_dlopen.c:52:30: error: implicit declaration of
function ‘GC_collection_in_progress’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono
Version: 6.8.0.105+dfsg-3.5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
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 more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> make[2]: Entering directory '/<>/libgc'
> CC allchblk.lo
> CC alloc.lo
> CC checksums.lo
> CC dbg_mlc.lo
> CC blacklst.lo
> CC dyn_load.lo
> CC finalize.lo
> CC gc_dlopen.lo
> CC gcj_mlc.lo
> gc_dlopen.c: In function ‘disable_gc_for_dlopen’:
> gc_dlopen.c:52:30: error: implicit declaration of function
> ‘GC_collection_in_progress’ [-Werror=implicit-function-declaration]
>52 | while (GC_incremental && GC_collection_in_progress()) {
> | ^
> alloc.c:85:2: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>85 | {"Copyright 1988,1989 Hans-J. Boehm and Alan J. Demers ",
> | ^~~
> alloc.c:86:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>86 | "Copyright (c) 1991-1995 by Xerox Corporation. All rights reserved.
> ",
> | ^~
> alloc.c:87:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>87 | "Copyright (c) 1996-1998 by Silicon Graphics. All rights reserved. ",
> | ^
> alloc.c:88:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>88 | "Copyright (c) 1999-2001 by Hewlett-Packard Company. All rights
> reserved. ",
> |
> ^~~~
> alloc.c:89:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>89 | "THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY",
> | ^~
> alloc.c:90:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>90 | " EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK.",
> | ^~
> alloc.c:91:1: warning: initialization discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
>91 | "See source code for details." };
> | ^~
> alloc.c:130:7: warning: no previous declaration for ‘GC_timeout_stop_func’
> [-Wmissing-declarations]
> 130 | int GC_timeout_stop_func GC_PROTO((void))
> | ^~~~
> alloc.c:186:6: warning: no previous declaration for ‘GC_adj_words_allocd’
> [-Wmissing-declarations]
> 186 | word GC_adj_words_allocd()
> | ^~~
> alloc.c:231:6: warning: no previous declaration for ‘GC_clear_a_few_frames’
> [-Wmissing-declarations]
> 231 | void GC_clear_a_few_frames()
> | ^
> alloc.c: In function ‘GC_clear_a_few_frames’:
> alloc.c:234:10: warning: variable ‘frames’ set but not used
> [-Wunused-but-set-variable]
> 234 | word frames[NWORDS];
> | ^~
> alloc.c: At top level:
> alloc.c:254:6: warning: no previous declaration for ‘GC_notify_full_gc’
> [-Wmissing-declarations]
> 254 | void GC_notify_full_gc()
> | ^
> alloc.c:269:6: warning: no previous declaration for ‘GC_maybe_gc’
> [-Wmissing-declarations]
> 269 | void GC_maybe_gc()
> | ^~~
> dbg_mlc.c:311:7:
Bug#1066903: libgnt: please drop runtime dependencies
This sounds reasonable to. It looks like you beat me to this with an
NMU. Thanks!
On 2024-03-15 04:08, Gianfranco Costamagna wrote:
Package: libgnt
Version: 2.14.4-1.1
Severity: serious
Tags: patch
Hello, I found some runtime dependencies, such as removed libglib2.0-0
breaking every 32bit build except i386 due to
time64_t transition.
Please update, remove them, let debhelper evaluate them via shlibs:Depends.
Also I added libxml2-dev build-dependency, looks like the support was
not enabled.
before:
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency libxml-2.0 found: NO (tried pkgconfig and cmake)
Now:
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Run-time dependency libxml-2.0 found: YES 2.9.14
Also dpkg shows correct dependencies now:
Package: libgnt0t64
[...]
Depends: libc6 (>= 2.38), libglib2.0-0t64 (>= 2.75.3), libncursesw6 (>=
6), libtinfo6 (>= 6), libxml2 (>= 2.7.4)
Breaks: finch (<< 2.14.1), libgnt0 (<< 2.14.4-1.2)
Replaces: finch (<< 2.14.1), libgnt0
Provides: libgnt0 (= 2.14.4-1.2)
[...]
Thanks for considering the patch.
*** /tmp/tmpkfjro47y/libgnt_2.14.4-1.1ubuntu1.debdiff
diff -Nru libgnt-2.14.4/debian/control libgnt-2.14.4/debian/control
--- libgnt-2.14.4/debian/control 2024-03-08 06:22:50.0 +0100
+++ libgnt-2.14.4/debian/control 2024-03-15 09:59:05.0 +0100
@@ -1,6 +1,7 @@
libglib2.0-dev,
libglib2.0-doc,
libncurses-dev,
+ libxml2-dev,
meson,
Build-Depends-Indep: gtk-doc-tools,
Homepage: https://keep.imfreedom.org/libgnt/libgnt
@@ -18,10 +18,7 @@
Package: libgnt0t64
Provides: ${t64:Provides}
Architecture: any
-Depends: libglib2.0-0,
- libncursesw6,
- libxml2,
- ${misc:Depends},
+Depends: ${misc:Depends},
${shlibs:Depends},
Breaks: libgnt0 (<< ${source:Version}), finch (<< 2.14.1),
Replaces: libgnt0, finch (<< 2.14.1),
--
Richard
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: Re: Bug#1066444: nacl: FTBFS: ld: cannot find -lnsl: No such file or directory
Processing control commands: > retitle -1 nacl: FTBFS due to -Werror=implicit-function-declaration Bug #1066444 [src:nacl] nacl: FTBFS: ld: cannot find -lnsl: No such file or directory Changed Bug title to 'nacl: FTBFS due to -Werror=implicit-function-declaration' from 'nacl: FTBFS: ld: cannot find -lnsl: No such file or directory'. -- 1066444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066444: nacl: FTBFS: ld: cannot find -lnsl: No such file or directory
control: retitle -1 nacl: FTBFS due to -Werror=implicit-function-declaration Hi, On 2024-03-13 13:03, Lucas Nussbaum wrote: > Source: nacl > Version: 20110221-13 > 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 failed to build > on amd64. > > > Relevant part (hopefully): [ snip] > > === Tue Mar 12 20:30:43 UTC 2024 === checking -lnsl > > /usr/bin/ld: cannot find -lnsl: No such file or directory > > collect2: error: ld returned 1 exit status The build system of nacl is totally nonstandard and difficult to understand, but it appears that this error is harmless. The real issue behind this FTBFS is the -Werror=implicit-function-declaration introduced by dpkg 1.22.6. Retitling the bug accordingly. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Processed: libsearpc: diff for NMU version 3.3.0+really3.3+git20230527.783141f-3.2
Processing control commands:
> tags 1066367 + patch
Bug #1066367 [src:libsearpc] libsearpc: FTBFS: searpc-demo-packet.h:40:34:
error: implicit declaration of function ‘write’; did you mean ‘writen’?
[-Werror=implicit-function-declaration]
Bug #1065977 [src:libsearpc] libsearpc: FTBFS on arm{el,hf}:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
Added tag(s) patch.
Added tag(s) patch.
> tags 1066367 + pending
Bug #1066367 [src:libsearpc] libsearpc: FTBFS: searpc-demo-packet.h:40:34:
error: implicit declaration of function ‘write’; did you mean ‘writen’?
[-Werror=implicit-function-declaration]
Bug #1065977 [src:libsearpc] libsearpc: FTBFS on arm{el,hf}:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
Added tag(s) pending.
Added tag(s) pending.
--
1065977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065977
1066367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066367: libsearpc: diff for NMU version 3.3.0+really3.3+git20230527.783141f-3.2
Control: tags 1066367 + patch Control: tags 1066367 + pending Dear maintainer, I've prepared an NMU for libsearpc (versioned as 3.3.0+really3.3+git20230527.783141f-3.2) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog 2024-02-28 23:11:14.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog 2024-03-16 00:36:38.0 +0500 @@ -1,3 +1,10 @@ +libsearpc (3.3.0+really3.3+git20230527.783141f-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066367). + + -- Andrey Rakhmatullin Sat, 16 Mar 2024 00:36:38 +0500 + libsearpc (3.3.0+really3.3+git20230527.783141f-3.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch 2024-03-16 00:35:16.0 +0500 @@ -0,0 +1,36 @@ +From d78aede0e4c559fa3dbce0e64ffc943da47fe76c Mon Sep 17 00:00:00 2001 +From: orbea +Date: Sat, 8 Apr 2023 17:13:55 -0700 +Subject: [PATCH] Fix -Werror=implicit-function-declaration + +unistd.h is needed for write, close and read +--- + demo/searpc-demo-packet.h | 1 + + demo/test-object.h| 2 ++ + 2 files changed, 3 insertions(+) + +diff --git a/demo/searpc-demo-packet.h b/demo/searpc-demo-packet.h +index 926f36b..6552396 100644 +--- a/demo/searpc-demo-packet.h b/demo/searpc-demo-packet.h +@@ -4,6 +4,7 @@ + + #include + #include ++#include + #include + + #ifdef WIN32 +diff --git a/demo/test-object.h b/demo/test-object.h +index f3f7589..a6d8b5d 100644 +--- a/demo/test-object.h b/demo/test-object.h +@@ -4,6 +4,8 @@ + #include + #include + ++GType test_object_get_type (void); ++ + #define TEST_OBJECT_TYPE(test_object_get_type()) + #define TEST_OBJECT(obj)(G_TYPE_CHECK_INSTANCE_CAST ((obj), TEST_OBJECT_TYPE, TestObject)) + #define IS_TEST_OBJCET(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), TEST_OBJCET_TYPE)) diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series 2023-06-30 15:18:13.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series 2024-03-16 00:35:49.0 +0500 @@ -3,3 +3,4 @@ 0003-Use-argparse-in-searpc-codegen-for-basic-help.patch 0004-Use-g_realloc-in-named_pipe_client_handler.patch #0005-Fix-memory-leak.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066903: marked as done (libgnt: please drop runtime dependencies)
Your message dated Fri, 15 Mar 2024 19:25:24 +
with message-id
and subject line Bug#1066903: fixed in libgnt 2.14.4-1.2
has caused the Debian Bug report #1066903,
regarding libgnt: please drop runtime dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnt
Version: 2.14.4-1.1
Severity: serious
Tags: patch
Hello, I found some runtime dependencies, such as removed libglib2.0-0 breaking
every 32bit build except i386 due to
time64_t transition.
Please update, remove them, let debhelper evaluate them via shlibs:Depends.
Also I added libxml2-dev build-dependency, looks like the support was not
enabled.
before:
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency libxml-2.0 found: NO (tried pkgconfig and cmake)
Now:
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Run-time dependency libxml-2.0 found: YES 2.9.14
Also dpkg shows correct dependencies now:
Package: libgnt0t64
[...]
Depends: libc6 (>= 2.38), libglib2.0-0t64 (>= 2.75.3), libncursesw6 (>= 6), libtinfo6
(>= 6), libxml2 (>= 2.7.4)
Breaks: finch (<< 2.14.1), libgnt0 (<< 2.14.4-1.2)
Replaces: finch (<< 2.14.1), libgnt0
Provides: libgnt0 (= 2.14.4-1.2)
[...]
Thanks for considering the patch.
*** /tmp/tmpkfjro47y/libgnt_2.14.4-1.1ubuntu1.debdiff
diff -Nru libgnt-2.14.4/debian/control libgnt-2.14.4/debian/control
--- libgnt-2.14.4/debian/control2024-03-08 06:22:50.0 +0100
+++ libgnt-2.14.4/debian/control2024-03-15 09:59:05.0 +0100
@@ -1,6 +1,7 @@
libglib2.0-dev,
libglib2.0-doc,
libncurses-dev,
+ libxml2-dev,
meson,
Build-Depends-Indep: gtk-doc-tools,
Homepage: https://keep.imfreedom.org/libgnt/libgnt
@@ -18,10 +18,7 @@
Package: libgnt0t64
Provides: ${t64:Provides}
Architecture: any
-Depends: libglib2.0-0,
- libncursesw6,
- libxml2,
- ${misc:Depends},
+Depends: ${misc:Depends},
${shlibs:Depends},
Breaks: libgnt0 (<< ${source:Version}), finch (<< 2.14.1),
Replaces: libgnt0, finch (<< 2.14.1),
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libgnt
Source-Version: 2.14.4-1.2
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
libgnt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gianfranco Costamagna (supplier of updated libgnt
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Mar 2024 09:59:05 +0100
Source: libgnt
Built-For-Profiles: noudeb
Architecture: source
Version: 2.14.4-1.2
Distribution: unstable
Urgency: medium
Maintainer: Richard Laager
Changed-By: Gianfranco Costamagna
Closes: 1066903
Changes:
libgnt (2.14.4-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Drop runtime dependencies (Closes: #1066903)
Checksums-Sha1:
afa166269e8e975e185e61a74f6fabb7d06ba397 2308 libgnt_2.14.4-1.2.dsc
3057e5601b4e6b8964b426e3f7d421a8b7cd62a2 9536 libgnt_2.14.4-1.2.debian.tar.xz
16f52e63ad7b896cf05ba3e7361040cf297425b7 9364
libgnt_2.14.4-1.2_source.buildinfo
Checksums-Sha256:
bc4ba1d6e368bf0e22397520efae11f40d2376cd6150f875e184873bbf8e8902 2308
libgnt_2.14.4-1.2.dsc
98ced1441ca503771df37a727027a00bce56934729f66b3934fe8b87331a7cd6 9536
libgnt_2.14.4-1.2.debian.tar.xz
d43c528c16642802ac88498fa8686abac15c871541d8d39c2f5f05aa47d3fb47 9364
libgnt_2.14.4-1.2_source.buildinfo
Files:
633b36754ea5b96334546e0e0aa564b8 2308 libs optional libgnt_2.14.4-1.2.dsc
4faee1e21cd9838aa8d85d64c5e1a29f 9536 libs optional
libgnt_2.14.4-1.2.debian.tar.xz
Processed: forcibly merging 1066367 1065977
Processing commands for cont...@bugs.debian.org:
> forcemerge 1066367 1065977
Bug #1066367 [src:libsearpc] libsearpc: FTBFS: searpc-demo-packet.h:40:34:
error: implicit declaration of function ‘write’; did you mean ‘writen’?
[-Werror=implicit-function-declaration]
Bug #1065977 [src:libsearpc] libsearpc: FTBFS on arm{el,hf}:
searpc-demo-packet.h:40:34: error: implicit declaration of function ‘write’;
did you mean ‘writen’? [-Werror=implicit-function-declaration]
Merged 1065977 1066367
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065977
1066367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066457: marked as done (node-websocket: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-websocket: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-websocket Version: 1.0.34+~cs10.0.25-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 failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/utf-8-validate/build' > CC(target) Release/obj.target/validation/src/validation.o > SOLINK_MODULE(target) Release/obj.target/validation.node > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-websocket_1.0.34+~cs10.0.25-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096 libnode109_18.19.1+dfsg-5_amd64.deb 299c2e39fd4fa3e0ec6a0bf00172ba0b52eb8365 3569504 nodejs-doc_18.19.1+dfsg-5_all.deb e4c7dbfa5850a45f3bc5ef617e08af8a49ab08b5 10959 nodejs_18.19.1+dfsg-5_amd64.buildinfo 880b1df5cef1d2bc1da4e105a07c11b48fe3e498 317764 nodejs_18.19.1+dfsg-5_amd64.deb Checksums-Sha256: 4b4bc90d856e3912024fa236f6c65d44bb477cf4e9d941120f96164b553a628a 4359 nodejs_18.19.1+dfsg-5.dsc 9c1b72df4a601ad27f23c3391cf3b1c78e4a7645596da5491b7d308c6fca99dc 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz a3606562b561dca6b3b6b2def4414c73479eb2fdfa80a1dae9738f8bab84bf24 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb d5443f5988ca86708246635fe9da2154692d83013bb59e5ee5db86bee44f2ea2 10491096 libnode109_18.19.1+dfsg-5_amd64.deb
Bug#1066445: marked as done (node-node-sass: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-node-sass: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-node-sass Version: 7.0.3+git20221109.ee13eb9+dfsg-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 failed to build on amd64. Relevant part (hopefully): > g++ -o Release/obj.target/binding.node -shared -pthread -rdynamic -m64 > -Wl,-z,relro -Wl,-z,now -Wl,-soname=binding.node -Wl,--start-group > Release/obj.target/binding/src/binding.o > Release/obj.target/binding/src/create_string.o > Release/obj.target/binding/src/custom_function_bridge.o > Release/obj.target/binding/src/custom_importer_bridge.o > Release/obj.target/binding/src/sass_context_wrapper.o > Release/obj.target/binding/src/sass_types/boolean.o > Release/obj.target/binding/src/sass_types/color.o > Release/obj.target/binding/src/sass_types/error.o > Release/obj.target/binding/src/sass_types/factory.o > Release/obj.target/binding/src/sass_types/list.o > Release/obj.target/binding/src/sass_types/map.o > Release/obj.target/binding/src/sass_types/null.o > Release/obj.target/binding/src/sass_types/number.o > Release/obj.target/binding/src/sass_types/string.o -Wl,--end-group -lnode > -lsass > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb
Bug#1066446: marked as done (node-iconv: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-iconv: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-iconv Version: 3.0.1+~3.0.0-1 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 failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > CC(target) Release/obj.target/iconv/binding.o > SOLINK_MODULE(target) Release/obj.target/iconv.node > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-iconv_3.0.1+~3.0.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096 libnode109_18.19.1+dfsg-5_amd64.deb 299c2e39fd4fa3e0ec6a0bf00172ba0b52eb8365 3569504 nodejs-doc_18.19.1+dfsg-5_all.deb e4c7dbfa5850a45f3bc5ef617e08af8a49ab08b5 10959 nodejs_18.19.1+dfsg-5_amd64.buildinfo 880b1df5cef1d2bc1da4e105a07c11b48fe3e498 317764 nodejs_18.19.1+dfsg-5_amd64.deb Checksums-Sha256: 4b4bc90d856e3912024fa236f6c65d44bb477cf4e9d941120f96164b553a628a 4359 nodejs_18.19.1+dfsg-5.dsc 9c1b72df4a601ad27f23c3391cf3b1c78e4a7645596da5491b7d308c6fca99dc 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz a3606562b561dca6b3b6b2def4414c73479eb2fdfa80a1dae9738f8bab84bf24 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb d5443f5988ca86708246635fe9da2154692d83013bb59e5ee5db86bee44f2ea2 10491096 libnode109_18.19.1+dfsg-5_amd64.deb
Bug#1066428: marked as done (node-leveldown: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-leveldown: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-leveldown Version: 5.6.0+dfsg-4 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 failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > CXX(target) Release/obj.target/leveldown/binding.o > SOLINK_MODULE(target) Release/obj.target/leveldown.node > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-leveldown_5.6.0+dfsg-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096 libnode109_18.19.1+dfsg-5_amd64.deb 299c2e39fd4fa3e0ec6a0bf00172ba0b52eb8365 3569504 nodejs-doc_18.19.1+dfsg-5_all.deb e4c7dbfa5850a45f3bc5ef617e08af8a49ab08b5 10959 nodejs_18.19.1+dfsg-5_amd64.buildinfo 880b1df5cef1d2bc1da4e105a07c11b48fe3e498 317764 nodejs_18.19.1+dfsg-5_amd64.deb Checksums-Sha256: 4b4bc90d856e3912024fa236f6c65d44bb477cf4e9d941120f96164b553a628a 4359 nodejs_18.19.1+dfsg-5.dsc 9c1b72df4a601ad27f23c3391cf3b1c78e4a7645596da5491b7d308c6fca99dc 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz a3606562b561dca6b3b6b2def4414c73479eb2fdfa80a1dae9738f8bab84bf24 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb d5443f5988ca86708246635fe9da2154692d83013bb59e5ee5db86bee44f2ea2 10491096 libnode109_18.19.1+dfsg-5_amd64.deb
Bug#1066407: marked as done (node-opencv: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 +
with message-id
and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5
has caused the Debian Bug report #1066399,
regarding node-opencv: FTBFS: ld: cannot find -lnode: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-opencv
Version: 7.0.0+git20200316.f0a03a4b-1
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 failed to build
on amd64.
Relevant part (hopefully):
> cc1plus: note: source object is likely at address zero
> CXX(target) Release/obj.target/opencv/src/FaceRecognizer.o
> ../src/FaceRecognizer.cc: In static member function ‘static void
> FaceRecognizerWrap::Init(v8::Local)’:
> ../src/FaceRecognizer.cc:84:14: warning: ignoring return value of
> ‘v8::Maybe v8::Object::Set(v8::Local,
> v8::Local, v8::Local)’, declared with attribute
> ‘warn_unused_result’ [-Wunused-result]
>84 | target->Set(Nan::GetCurrentContext(),
> Nan::New("FaceRecognizer").ToLocalChecked(), ctor->GetFunction(
> Nan::GetCurrentContext() ).ToLocalChecked());
> |
> ~~~^~~
> In file included from
> /usr/include/nodejs/deps/v8/include/v8-array-buffer.h:13,
> from /usr/include/nodejs/deps/v8/include/v8.h:24,
> from ../src/OpenCV.h:18,
> from ../src/FaceRecognizer.cc:1:
> /usr/include/nodejs/deps/v8/include/v8-object.h:244:37: note: declared here
> 244 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
> | ^~~
> ../src/FaceRecognizer.cc: In static member function ‘static
> Nan::NAN_METHOD_RETURN_TYPE
> FaceRecognizerWrap::PredictSync(Nan::NAN_METHOD_ARGS_TYPE)’:
> ../src/FaceRecognizer.cc:335:11: warning: ignoring return value of
> ‘v8::Maybe v8::Object::Set(v8::Local,
> v8::Local, v8::Local)’, declared with attribute
> ‘warn_unused_result’ [-Wunused-result]
> 335 | res->Set(Nan::GetCurrentContext(), Nan::New("id").ToLocalChecked(),
> Nan::New(predictedLabel));
> |
> ^
> /usr/include/nodejs/deps/v8/include/v8-object.h:244:37: note: declared here
> 244 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
> | ^~~
> ../src/FaceRecognizer.cc:336:11: warning: ignoring return value of
> ‘v8::Maybe v8::Object::Set(v8::Local,
> v8::Local, v8::Local)’, declared with attribute
> ‘warn_unused_result’ [-Wunused-result]
> 336 | res->Set(Nan::GetCurrentContext(),
> Nan::New("confidence").ToLocalChecked(), Nan::New(confidence));
> |
> ^
> /usr/include/nodejs/deps/v8/include/v8-object.h:244:37: note: declared here
> 244 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
> | ^~~
> ../src/FaceRecognizer.cc: In member function ‘virtual void
> PredictASyncWorker::HandleOKCallback()’:
> ../src/FaceRecognizer.cc:375:13: warning: ignoring return value of
> ‘v8::Maybe v8::Object::Set(v8::Local,
> v8::Local, v8::Local)’, declared with attribute
> ‘warn_unused_result’ [-Wunused-result]
> 375 | res->Set(Nan::GetCurrentContext(),
> Nan::New("id").ToLocalChecked(), Nan::New(predictedLabel));
> |
> ^
> /usr/include/nodejs/deps/v8/include/v8-object.h:244:37: note: declared here
> 244 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
> | ^~~
> ../src/FaceRecognizer.cc:376:13: warning: ignoring return value of
> ‘v8::Maybe v8::Object::Set(v8::Local,
> v8::Local, v8::Local)’, declared with attribute
> ‘warn_unused_result’ [-Wunused-result]
> 376 | res->Set(Nan::GetCurrentContext(),
> Nan::New("confidence").ToLocalChecked(), Nan::New(confidence));
> |
> ^
> /usr/include/nodejs/deps/v8/include/v8-object.h:244:37: note: declared here
> 244 |
Bug#1066425: marked as done (node-libpq: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 +
with message-id
and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5
has caused the Debian Bug report #1066399,
regarding node-libpq: FTBFS: ld: cannot find -lnode: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-libpq
Version: 1.8.12+~1.8.10-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 failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> CXX(target) Release/obj.target/addon/src/connection.o
> CXX(target) Release/obj.target/addon/src/connect-async-worker.o
> CXX(target) Release/obj.target/addon/src/addon.o
> In file included from ../../../../usr/share/nodejs/nan/nan.h:62,
> from ../src/addon.h:4,
> from ../src/addon.cc:1:
> /usr/include/nodejs/src/node.h:1014:7: warning: cast between incompatible
> function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka
> ‘void (*)(v8::Local)’} to ‘node::addon_register_func’ {aka ‘void
> (*)(v8::Local, v8::Local, void*)’}
> [-Wcast-function-type]
> 1014 | (node::addon_register_func) (regfunc),
> \
> | ^
> /usr/include/nodejs/src/node.h:1048:3: note: in expansion of macro
> ‘NODE_MODULE_X’
> 1048 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT
> (readability/null_usage)
> | ^
> ../src/addon.cc:76:1: note: in expansion of macro ‘NODE_MODULE’
>76 | NODE_MODULE(addon, InitAddon)
> | ^~~
> SOLINK_MODULE(target) Release/obj.target/addon.node
> /usr/bin/ld: cannot find -lnode: No such file or directory
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/node-libpq_1.8.12+~1.8.10-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.1+dfsg-5
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Mar 2024 23:51:57 +0100
Source: nodejs
Binary: libnode-dev libnode109 nodejs nodejs-doc
Architecture: source amd64 all
Version: 18.19.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Description:
libnode-dev - evented I/O for V8 javascript (development files)
libnode109 - evented I/O for V8 javascript - runtime library
nodejs - evented I/O for V8 javascript - runtime executable
nodejs-doc - API documentation for Node.js, the javascript platform
Closes: 1065909 1066399
Changes:
nodejs (18.19.1+dfsg-5) unstable; urgency=medium
.
* Drop distutils dep. Closes: #1065909
* Facilitate t64 transition by just bumping
NODE_MODULE ABI to 109. Closes: #1066399
* test_ci.patch: skip hanging or EAI_AGAIN failing tests
Checksums-Sha1:
31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359
Bug#1066419: marked as done (node-node-pty: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 +
with message-id
and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5
has caused the Debian Bug report #1066399,
regarding node-node-pty: FTBFS: ld: cannot find -lnode: No such file or
directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-node-pty
Version: 1.0.0+ds1+~6.3.0-1
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 failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> CXX(target) Release/obj.target/pty/src/unix/pty.o
> ../src/unix/pty.cc: In function ‘void pty_after_waitpid(uv_async_t*)’:
> ../src/unix/pty.cc:609:9: warning: ‘void* memset(void*, int, size_t)’ writing
> to an object of type ‘class Nan::Persistent’ with no trivial
> copy-assignment [-Wclass-memaccess]
> 609 | memset(>cb, -1, sizeof(baton->cb));
> | ~~^~~
> In file included from ../../../../usr/share/nodejs/nan/nan.h:411,
> from ../src/unix/pty.cc:20:
> /usr/include/nan_persistent_12_inl.h:12:40: note: ‘class
> Nan::Persistent’ declared here
>12 | template class Persistent :
> |^~
> In file included from ../../../../usr/share/nodejs/nan/nan.h:62:
> ../src/unix/pty.cc: At global scope:
> /usr/include/nodejs/src/node.h:1014:7: warning: cast between incompatible
> function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka
> ‘void (*)(v8::Local)’} to ‘node::addon_register_func’ {aka ‘void
> (*)(v8::Local, v8::Local, void*)’}
> [-Wcast-function-type]
> 1014 | (node::addon_register_func) (regfunc),
> \
> | ^
> /usr/include/nodejs/src/node.h:1048:3: note: in expansion of macro
> ‘NODE_MODULE_X’
> 1048 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT
> (readability/null_usage)
> | ^
> ../src/unix/pty.cc:826:1: note: in expansion of macro ‘NODE_MODULE’
> 826 | NODE_MODULE(pty, init)
> | ^~~
> SOLINK_MODULE(target) Release/obj.target/pty.node
> /usr/bin/ld: cannot find -lnode: No such file or directory
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/node-node-pty_1.0.0+ds1+~6.3.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.1+dfsg-5
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Mar 2024 23:51:57 +0100
Source: nodejs
Binary: libnode-dev libnode109 nodejs nodejs-doc
Architecture: source amd64 all
Version: 18.19.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Description:
libnode-dev - evented I/O for V8 javascript (development files)
libnode109 - evented I/O for V8
Bug#1066415: marked as done (node-sqlite3: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-sqlite3: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-sqlite3 Version: 5.1.5+ds1-1 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 failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > CXX(target) Release/obj.target/node_sqlite3/src/backup.o > gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] > ../src/backup.cc: In static member function ‘static void > node_sqlite3::Backup::Work_BeginInitialize(node_sqlite3::Database::Baton*)’: > ../src/backup.cc:182:9: warning: unused variable ‘status’ [-Wunused-variable] > 182 | int status = napi_create_async_work( > | ^~ > In file included from ../src/backup.cc:4: > ../src/backup.cc: In static member function ‘static void > node_sqlite3::Backup::Work_BeginStep(Baton*)’: > ../src/macros.h:185:9: warning: unused variable ‘status’ [-Wunused-variable] > 185 | int status = napi_create_async_work( > \ > | ^~ > ../src/backup.cc:255:5: note: in expansion of macro ‘BACKUP_BEGIN’ > 255 | BACKUP_BEGIN(Step); > | ^~~~ > ../src/backup.cc: In static member function ‘static void > node_sqlite3::Backup::Work_BeginFinish(Baton*)’: > ../src/macros.h:185:9: warning: unused variable ‘status’ [-Wunused-variable] > 185 | int status = napi_create_async_work( > \ > | ^~ > ../src/backup.cc:322:5: note: in expansion of macro ‘BACKUP_BEGIN’ > 322 | BACKUP_BEGIN(Finish); > | ^~~~ > CXX(target) Release/obj.target/node_sqlite3/src/database.o > ../src/database.cc: In static member function ‘static void > node_sqlite3::Database::Work_BeginOpen(Baton*)’: > ../src/database.cc:155:9: warning: unused variable ‘status’ > [-Wunused-variable] > 155 | int status = napi_create_async_work( > | ^~ > ../src/database.cc: In static member function ‘static void > node_sqlite3::Database::Work_BeginClose(Baton*)’: > ../src/database.cc:249:9: warning: unused variable ‘status’ > [-Wunused-variable] > 249 | int status = napi_create_async_work( > | ^~ > ../src/database.cc: In static member function ‘static void > node_sqlite3::Database::Work_BeginExec(Baton*)’: > ../src/database.cc:593:9: warning: unused variable ‘status’ > [-Wunused-variable] > 593 | int status = napi_create_async_work( > | ^~ > ../src/database.cc: In static member function ‘static void > node_sqlite3::Database::Work_BeginLoadExtension(Baton*)’: > ../src/database.cc:702:9: warning: unused variable ‘status’ > [-Wunused-variable] > 702 | int status = napi_create_async_work( > | ^~ > CXX(target) Release/obj.target/node_sqlite3/src/node_sqlite3.o > CXX(target) Release/obj.target/node_sqlite3/src/statement.o > ../src/statement.cc: In static member function ‘static void > node_sqlite3::Statement::Work_BeginPrepare(node_sqlite3::Database::Baton*)’: > ../src/statement.cc:125:9: warning: unused variable ‘status’ > [-Wunused-variable] > 125 | int status = napi_create_async_work( > | ^~ > In file included from ../src/statement.cc:5: > ../src/statement.cc: In static member function ‘static void > node_sqlite3::Statement::Work_BeginBind(Baton*)’: > ../src/macros.h:149:9: warning: unused variable ‘status’ [-Wunused-variable] > 149 | int status = napi_create_async_work( > \ > | ^~ > ../src/statement.cc:353:5: note: in expansion of macro ‘STATEMENT_BEGIN’ > 353 | STATEMENT_BEGIN(Bind); > | ^~~ > ../src/statement.cc: In static member function ‘static void > node_sqlite3::Statement::Work_BeginGet(Baton*)’: > ../src/macros.h:149:9: warning: unused variable ‘status’ [-Wunused-variable] > 149 | int status = napi_create_async_work( > \ > | ^~ > ../src/statement.cc:405:5: note: in expansion of macro ‘STATEMENT_BEGIN’
Bug#1066409: marked as done (r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-v8 Version: 4.4.1+dfsg-1 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 failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem R >dh_update_autotools_config -O--buildsystem=R >dh_autoreconf -O--buildsystem=R >dh_auto_configure -O--buildsystem=R >dh_auto_build -O--buildsystem=R >dh_auto_test -O--buildsystem=R >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=R >dh_prep -O--buildsystem=R >dh_auto_install --destdir=debian/r-cran-v8/ -O--buildsystem=R > I: R packages needed for DEP8: testthat, knitr, rmarkdown > I: R Package: V8 Version: 4.4.1 > I: Building using R version 4.3.3-2 > I: R API version: r-api-4.0 > I: Using built-time from d/changelog: Fri, 22 Dec 2023 10:12:23 +0100 > mkdir -p > /<>/r-cran-v8-4.4.1\+dfsg/debian/r-cran-v8/usr/lib/R/site-library > R CMD INSTALL -l > /<>/r-cran-v8-4.4.1\+dfsg/debian/r-cran-v8/usr/lib/R/site-library > --clean . "--built-timestamp='Fri, 22 Dec 2023 10:12:23 +0100'" > * installing *source* package ‘V8’ ... > files ‘inst/doc/npm.html’, ‘inst/doc/v8_intro.html’, ‘inst/js/underscore.js’, > ‘inst/js/wasm-feature-detect.js’ are missing > ** using staged installation > Found C++17 compiler: g++ > Using CXXCPP=g++ -std=gnu++17 -E > Using PKG_CFLAGS=-I/usr/include/v8 -I/usr/include/v8-3.14 > Using PKG_LIBS=-lv8 -lv8_libplatform > Running feature test for pointer compression... > /usr/bin/ld: cannot find -lv8: No such file or directory > /usr/bin/ld: cannot find -lv8_libplatform: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/r-cran-v8_4.4.1+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64
Bug#1066405: marked as done (node-modern-syslog: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 +
with message-id
and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5
has caused the Debian Bug report #1066399,
regarding node-modern-syslog: FTBFS: ld: cannot find -lnode: No such file or
directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-modern-syslog
Version: 1.2.0-4
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 failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> CXX(target) Release/obj.target/core/core.o
> In file included from ../core.cc:1:
> /usr/include/nodejs/src/node.h:1014:7: warning: cast between incompatible
> function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka
> ‘void (*)(v8::Local)’} to ‘node::addon_register_func’ {aka ‘void
> (*)(v8::Local, v8::Local, void*)’}
> [-Wcast-function-type]
> 1014 | (node::addon_register_func) (regfunc),
> \
> | ^
> /usr/include/nodejs/src/node.h:1048:3: note: in expansion of macro
> ‘NODE_MODULE_X’
> 1048 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT
> (readability/null_usage)
> | ^
> ../core.cc:190:1: note: in expansion of macro ‘NODE_MODULE’
> 190 | NODE_MODULE(core, Init);
> | ^~~
> SOLINK_MODULE(target) Release/obj.target/core.node
> /usr/bin/ld: cannot find -lnode: No such file or directory
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/node-modern-syslog_1.2.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.19.1+dfsg-5
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Mar 2024 23:51:57 +0100
Source: nodejs
Binary: libnode-dev libnode109 nodejs nodejs-doc
Architecture: source amd64 all
Version: 18.19.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Description:
libnode-dev - evented I/O for V8 javascript (development files)
libnode109 - evented I/O for V8 javascript - runtime library
nodejs - evented I/O for V8 javascript - runtime executable
nodejs-doc - API documentation for Node.js, the javascript platform
Closes: 1065909 1066399
Changes:
nodejs (18.19.1+dfsg-5) unstable; urgency=medium
.
* Drop distutils dep. Closes: #1065909
* Facilitate t64 transition by just bumping
NODE_MODULE ABI to 109. Closes: #1066399
* test_ci.patch: skip hanging or EAI_AGAIN failing tests
Checksums-Sha1:
31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc
f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936
nodejs_18.19.1+dfsg-5.debian.tar.xz
b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312
libnode-dev_18.19.1+dfsg-5_amd64.deb
ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096
Bug#1066402: marked as done (node-re2: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-re2: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-re2 Version: 1.19.2+~cs2.13.13-1 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 failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > CXX(target) Release/obj.target/re2/lib/addon.o > CXX(target) Release/obj.target/re2/lib/new.o > CXX(target) Release/obj.target/re2/lib/exec.o > CXX(target) Release/obj.target/re2/lib/test.o > CXX(target) Release/obj.target/re2/lib/match.o > CXX(target) Release/obj.target/re2/lib/replace.o > CXX(target) Release/obj.target/re2/lib/search.o > CXX(target) Release/obj.target/re2/lib/split.o > CXX(target) Release/obj.target/re2/lib/to_string.o > CXX(target) Release/obj.target/re2/lib/accessors.o > CXX(target) Release/obj.target/re2/lib/util.o > SOLINK_MODULE(target) Release/obj.target/re2.node > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-re2_1.19.2+~cs2.13.13-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096 libnode109_18.19.1+dfsg-5_amd64.deb 299c2e39fd4fa3e0ec6a0bf00172ba0b52eb8365 3569504 nodejs-doc_18.19.1+dfsg-5_all.deb e4c7dbfa5850a45f3bc5ef617e08af8a49ab08b5 10959 nodejs_18.19.1+dfsg-5_amd64.buildinfo 880b1df5cef1d2bc1da4e105a07c11b48fe3e498 317764
Bug#1066399: marked as done (node-nan: FTBFS: ld: cannot find -lnode: No such file or directory)
Your message dated Fri, 15 Mar 2024 19:10:10 + with message-id and subject line Bug#1066399: fixed in nodejs 18.19.1+dfsg-5 has caused the Debian Bug report #1066399, regarding node-nan: FTBFS: ld: cannot find -lnode: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-nan Version: 2.18.0-1 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 failed to build on amd64. Relevant part (hopefully): > g++ -o Release/obj.target/addon.node -shared -pthread -rdynamic -m64 > -Wl,-z,relro -Wl,-soname=addon.node -Wl,--start-group > Release/obj.target/addon/addon.o Release/obj.target/addon/pi_est.o > Release/obj.target/addon/sync.o Release/obj.target/addon/async.o > -Wl,--end-group -lnode > /usr/bin/ld: cannot find -lnode: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/node-nan_2.18.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.19.1+dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2024 23:51:57 +0100 Source: nodejs Binary: libnode-dev libnode109 nodejs nodejs-doc Architecture: source amd64 all Version: 18.19.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode109 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 1065909 1066399 Changes: nodejs (18.19.1+dfsg-5) unstable; urgency=medium . * Drop distutils dep. Closes: #1065909 * Facilitate t64 transition by just bumping NODE_MODULE ABI to 109. Closes: #1066399 * test_ci.patch: skip hanging or EAI_AGAIN failing tests Checksums-Sha1: 31143da5fc1cd14ede54a834f8fddbf63df6dc20 4359 nodejs_18.19.1+dfsg-5.dsc f34b1441ae69e538784b8f564dc7b47fcb3e2f2d 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz b7bcaa14758db27c625ec1e1da5639d5556b0f57 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb ab9ad0262b18be91a9efe831e6a11dc708db0653 10491096 libnode109_18.19.1+dfsg-5_amd64.deb 299c2e39fd4fa3e0ec6a0bf00172ba0b52eb8365 3569504 nodejs-doc_18.19.1+dfsg-5_all.deb e4c7dbfa5850a45f3bc5ef617e08af8a49ab08b5 10959 nodejs_18.19.1+dfsg-5_amd64.buildinfo 880b1df5cef1d2bc1da4e105a07c11b48fe3e498 317764 nodejs_18.19.1+dfsg-5_amd64.deb Checksums-Sha256: 4b4bc90d856e3912024fa236f6c65d44bb477cf4e9d941120f96164b553a628a 4359 nodejs_18.19.1+dfsg-5.dsc 9c1b72df4a601ad27f23c3391cf3b1c78e4a7645596da5491b7d308c6fca99dc 163936 nodejs_18.19.1+dfsg-5.debian.tar.xz a3606562b561dca6b3b6b2def4414c73479eb2fdfa80a1dae9738f8bab84bf24 509312 libnode-dev_18.19.1+dfsg-5_amd64.deb
Bug#1066327: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:48:27PM +0100, Lucas Nussbaum wrote: > > chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ > > [-Werror=implicit-function-declaration] > > chm_http.c:179:9: error: implicit declaration of function ‘close’; did you > > mean ‘pclose’? [-Werror=implicit-function-declaration] These are fixed by including and but then there is an undefined pread64() in chm_lib.c, not sure what is the correct way to fix that. Gentoo fixed that by adding #define _LARGEFILE64_SOURCE to the file, but I hesitate to do that as I don't understand the implications of doing that on different architectures. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1066943: ntirpc: FTBFS: missing dependency on libnsl-dev
Source: ntirpc Version: 4.3-3.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=ntirpc=armel=4.3-3.1=1710521344=0 -- Looking for epoll_create -- Looking for epoll_create - found -- Found EPOLL: 1 -- Could NOT find NSL (missing: NSL_LIBRARY) -- -- --- -- TIRPC_EPOLL = TRUE -- USE_RPC_RDMA = OFF -- USE_GSS = ON -- USE_PROFILE = OFF -- USE_LTTNG_NTIRPC = OFF -- Configuring done (5.2s) CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: NSL_LIBRARY (ADVANCED) linked by target "ntirpc" in directory /<>/src -- Generating done (0.1s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_RUNSTATEDIR CMAKE_INSTALL_SYSCONFDIR FETCHCONTENT_FULLY_DISCONNECTED CMake Generate step failed. Build files cannot be regenerated correctly. Cheers> -- Sebastian Ramacher
Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’
Source: xmrig Version: 6.21.1+dfsg-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=xmrig=armhf=6.21.1%2Bdfsg-1%2Bb1=1710494247=0 cd /<>/obj-arm-linux-gnueabihf/src/3rdparty/argon2 && /usr/bin/cc -DCL_TARGET_OPENCL_VERSION=200 -DCL_USE_DEPRECATED_OPENCL_1_2_APIS -DHAVE_BUILTIN_CLEAR_CACHE -DHAVE_ROTR -DHAVE_SYSLOG_H -DUNICODE -DXMRIG_ALGO_ARGON2 -DXMRIG_ALGO_RANDOMX -DXMRIG_FEATURE_ADL -DXMRIG_FEATURE_API -DXMRIG_FEATURE_BENCHMARK -DXMRIG_FEATURE_CUDA -DXMRIG_FEATURE_ENV -DXMRIG_FEATURE_HTTP -DXMRIG_FEATURE_HWLOC -DXMRIG_FEATURE_NVML -DXMRIG_FEATURE_OPENCL -DXMRIG_JSON_SINGLE_LINE_ARRAY -DXMRIG_MINER_PROJECT -DXMRIG_OS_LINUX -DXMRIG_OS_UNIX -DXMRIG_STRICT_OPENCL_CACHE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__STDC_FORMAT_MACROS -I/<>/src/3rdparty/argon2/../.. -I/<>/src/3rdparty/argon2/lib -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-strict-aliasing -maes -std=gnu99 -MD -MT src/3rdparty/argon2/CMakeFiles/argon2.dir/lib/impl-select.c.o -MF CMakeFiles/argon2.dir/lib/impl-select.c.o.d -o CMakeFiles/argon2.dir/lib/impl-select.c.o -c /<>/src/3rdparty/argon2/lib/impl-select.c cc: error: unrecognized command-line option ‘-maes’ Cheers -- Sebastian Ramacher
Processed: Re: Bug#1066531: policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration]
Processing control commands: > tags -1 - patch Bug #1066531 [src:policykit-1] policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] Removed tag(s) patch. -- 1066531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066531: policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration]
Control: tags -1 - patch On Wed, 13 Mar 2024 13:01:49 + Mark Hindley wrote: Control: tags -1 patch I also bumped into this whilst rebuilding src:policykit-1 yesterday. There is an upstream patch[1], but it doesn't fix the build for me; I think it is patching the wrong files.The problem appears to be multiple copies of mocklibc. AFAICS ./test/mocklibc is not used in favour of a meson subproject. The pkla-compat tarball also has mocklibc, but that is also patched already. Getting the multiple layers of quilt and meson patches to work was unpleasant. So the attached patch may save you some time. HTH Mark [1] https://github.com/polkit-org/polkit/commit/0d78d1e4bf5ab3ce11678005b220aac0cfc5bee5 Thanks for the patch Unfortunately it fails to apply to the src:policykit-1 package as shipped in Debian sid. Thus marking the bug report accordingly. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066941: coz-profiler: FTBFS: what(): unknown compilation unit version 5
Source: coz-profiler
Version: 0.2.2-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=coz-profiler=amd64=0.2.2-2%2Bb1=1710517462=0
printf "int main(int argc, char *argv[])\n{\nreturn (0);\n}\n" > x.c
gcc -g -o x x.c || ( rm -f x x.c ; exit 1)
../coz run --- ./x
␛[34m[libcoz.cpp:100] ␛[01;34mbootstrapping coz␛[0m
␛[34m[libcoz.cpp:128] ␛[01;34mIncluding MAIN, which is
/<>/libcoz/x␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/<>/libcoz/libcoz.so is not in
scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libdwarf++.so.0 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
is not in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 is
not in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libelf++.so.0 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libgcc_s.so.1 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libc.so.6 is not in
scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libm.so.6 is not in
scope␛[0m
terminate called after throwing an instance of 'dwarf::format_error'
what(): unknown compilation unit version 5
make[3]: *** [Makefile:12: check] Error 250
Cheers
--
Sebastian Ramacher
Bug#1066939: xboxdrv: FTBFS on arm{el,hf}: src/linux_uinput.cpp:294:20: error: ‘struct input_event’ has no member named ‘time’
Source: xboxdrv
Version: 0.8.8-3
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=xboxdrv=armhf=0.8.8-3%2Bb1=1710520170=0
g++ -o src/linux_uinput.o -c -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-isystem/usr/include/dbus-1.0
-isystem/usr/lib/arm-linux-gnueabihf/dbus-1.0/include
-isystem/usr/include/glib-2.0
-isystem/usr/lib/arm-linux-gnueabihf/glib-2.0/include -pthread
-isystem/usr/include/libusb-1.0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -Wall -ansi -pedantic
-DPACKAGE_VERSION='"0.8.8"' -Isrc src/linux_uinput.cpp
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’
is not valid for C++
In file included from /usr/include/boost/function/detail/requires_cxx11.hpp:9,
from /usr/include/boost/function/detail/prologue.hpp:12,
from /usr/include/boost/function.hpp:30,
from src/linux_uinput.hpp:22,
from src/linux_uinput.cpp:19:
/usr/include/boost/function/detail/requires_cxx11.hpp:18:1: note: ‘#pragma
message: C++03 support was deprecated in Boost.Function 1.82 and will be
removed in Boost.Function 1.84. Please open an issue in
https://github.com/boostorg/function if you want it retained.’
18 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.Function
1.82 and will be removed in Boost.Function 1.84. Please open an issue in
https://github.com/boostorg/function if you want it retained.")
| ^~~~
/usr/include/boost/bind/detail/requires_cxx11.hpp:18:1: note: ‘#pragma message:
C++03 support was deprecated in Boost.Bind 1.82 and will be removed in
Boost.Bind 1.84. Please open an issue in https://github.com/boostorg/bind if
you want it retained.’
18 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.Bind 1.82
and will be removed in Boost.Bind 1.84. Please open an issue in
https://github.com/boostorg/bind if you want it retained.")
| ^~~~
/usr/include/boost/smart_ptr/detail/requires_cxx11.hpp:19:1: note: ‘#pragma
message: C++03 support was deprecated in Boost.SmartPtr 1.82 and will be
removed in Boost.SmartPtr 1.84. Please open an issue in
https://github.com/boostorg/smart_ptr if you want it retained.’
19 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.SmartPtr
1.82 and will be removed in Boost.SmartPtr 1.84. Please open an issue in
https://github.com/boostorg/smart_ptr if you want it retained.")
| ^~~~
/usr/include/boost/lexical_cast.hpp:40:1: note: ‘#pragma message: C++03 support
is deprecated in Boost.LexicalCast 1.82 and will be removed in
Boost.LexicalCast 1.84.’
40 | BOOST_PRAGMA_MESSAGE("C++03 support is deprecated in Boost.LexicalCast
1.82 and will be removed in Boost.LexicalCast 1.84.")
| ^~~~
src/linux_uinput.cpp: In member function ‘void LinuxUinput::send(uint16_t,
uint16_t, int32_t)’:
src/linux_uinput.cpp:294:20: error: ‘struct input_event’ has no member named
‘time’
294 | gettimeofday(, NULL);
|^~~~
scons: *** [src/linux_uinput.o] Error 1
scons: building terminated because of errors.
Cheers
--
Sebastian Ramacher
Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined
Source: libfiu Version: 1.2-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=libfiu=armhf=1.2-2=1710292712=0 cc -D_XOPEN_SOURCE=600 -fPIC -DFIU_ENABLE=1 -D_LARGEFILE64_SOURCE=1 -I. -I../../libfiu/ -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -D_GNU_SOURCE -c codegen.c -o codegen.o /tmp/cc54dEva.s: Assembler messages: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined /tmp/cchEoHpC.s: Assembler messages: /tmp/cchEoHpC.s:474: Error: symbol `mmap64' is already defined make[4]: *** [Makefile:67: modules/posix.mm.mod.o] Error 1 make[4]: *** Waiting for unfinished jobs make[4]: *** [Makefile:67: modules/posix.custom.o] Error 1 /tmp/cct4HXD3.s: Assembler messages: /tmp/cct4HXD3.s:1810: Error: symbol `pread64' is already defined /tmp/cct4HXD3.s:3995: Error: symbol `pwrite64' is already defined /tmp/cct4HXD3.s:5803: Error: symbol `truncate64' is already defined /tmp/cct4HXD3.s:6480: Error: symbol `ftruncate64' is already defined /tmp/ccInAMjZ.s: Assembler messages: /tmp/ccInAMjZ.s:437: Error: symbol `fopen64' is already defined make[4]: *** [Makefile:67: modules/posix.io.mod.o] Error 1 /tmp/ccInAMjZ.s:1099: Error: symbol `freopen64' is already defined /tmp/ccInAMjZ.s:3393: Error: symbol `tmpfile64' is already defined /tmp/ccInAMjZ.s:5973: Error: symbol `ftello64' is already defined /tmp/ccInAMjZ.s:7007: Error: symbol `fseeko64' is already defined /tmp/ccInAMjZ.s:7699: Error: symbol `fsetpos64' is already defined make[4]: *** [Makefile:67: modules/posix.stdio.mod.o] Error 1 Cheers -- Sebastian Ramacher
Processed: pmount: diff for NMU version 0.9.23-7.1
Processing control commands: > tags 1066515 + patch Bug #1066515 [src:pmount] pmount: FTBFS: luks.c:147:7: error: implicit declaration of function ‘creat’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066515 + pending Bug #1066515 [src:pmount] pmount: FTBFS: luks.c:147:7: error: implicit declaration of function ‘creat’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066515: pmount: diff for NMU version 0.9.23-7.1
Control: tags 1066515 + patch Control: tags 1066515 + pending Dear maintainer, I've prepared an NMU for pmount (versioned as 0.9.23-7.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru pmount-0.9.23/debian/changelog pmount-0.9.23/debian/changelog --- pmount-0.9.23/debian/changelog 2023-09-14 12:58:36.0 +0500 +++ pmount-0.9.23/debian/changelog 2024-03-15 23:43:49.0 +0500 @@ -1,3 +1,10 @@ +pmount (0.9.23-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066515). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:43:49 +0500 + pmount (0.9.23-7) unstable; urgency=medium * New maintainer. Closes: #689854 diff -Nru pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch --- pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 23:43:49.0 +0500 @@ -0,0 +1,18 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066515 +Last-Update: 2024-03-15 + +Index: pmount-0.9.23/src/luks.c +=== +--- pmount-0.9.23.orig/src/luks.c pmount-0.9.23/src/luks.c +@@ -16,6 +16,8 @@ + #include + #include + #include ++#include ++#include + + + /* If CRYPTSETUP_RUID is set, we run cryptsetup with ruid = euid = 0. diff -Nru pmount-0.9.23/debian/patches/series pmount-0.9.23/debian/patches/series --- pmount-0.9.23/debian/patches/series 2023-09-14 12:58:36.0 +0500 +++ pmount-0.9.23/debian/patches/series 2024-03-15 23:43:32.0 +0500 @@ -1,3 +1,4 @@ 01-man-plugdev.diff 10_fix-spelling-binary-errors.patch 20_fix-spelling-manpage-error.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066465: dcraw: diff for NMU version 9.28-3.1
Control: tags 1066465 + patch Control: tags 1066465 + pending Dear maintainer, I've prepared an NMU for dcraw (versioned as 9.28-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru dcraw-9.28/debian/changelog dcraw-9.28/debian/changelog --- dcraw-9.28/debian/changelog 2021-11-22 03:15:39.0 +0500 +++ dcraw-9.28/debian/changelog 2024-03-15 23:31:51.0 +0500 @@ -1,3 +1,10 @@ +dcraw (9.28-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066465). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:31:51 +0500 + dcraw (9.28-3) unstable; urgency=medium * Written wrappers of fread(),fwrite(),fseek() library functions which diff -Nru dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch --- dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 23:31:51.0 +0500 @@ -0,0 +1,41 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066465 +Last-Update: 2024-03-15 + +Index: dcraw-9.28/fujiturn.c +=== +--- dcraw-9.28.orig/fujiturn.c dcraw-9.28/fujiturn.c +@@ -15,6 +15,7 @@ + #include + #include + #include ++#include + + #ifdef _16BIT + typedef unsigned short value; +Index: dcraw-9.28/fuji_green.c +=== +--- dcraw-9.28.orig/fuji_green.c dcraw-9.28/fuji_green.c +@@ -11,6 +11,8 @@ + #include + #include + #include ++#include ++#include + + #define ushort UshORt + typedef unsigned char uchar; +Index: dcraw-9.28/Makefile.am +=== +--- dcraw-9.28.orig/Makefile.am dcraw-9.28/Makefile.am +@@ -14,5 +14,6 @@ dcfujiturn16_SOURCES = fujiturn.c + dcfujiturn16_CFLAGS = -D_16BIT + + dcfujigreen_SOURCES = fuji_green.c ++dcfujigreen_CFLAGS = -D_XOPEN_SOURCE + + dccleancrw_SOURCES = clean_crw.c diff -Nru dcraw-9.28/debian/patches/series dcraw-9.28/debian/patches/series --- dcraw-9.28/debian/patches/series 2021-11-22 03:15:39.0 +0500 +++ dcraw-9.28/debian/patches/series 2024-03-15 23:31:51.0 +0500 @@ -6,3 +6,4 @@ 906529.patch 906530.patch iowrap.diff +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Processed: dcraw: diff for NMU version 9.28-3.1
Processing control commands: > tags 1066465 + patch Bug #1066465 [src:dcraw] dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066465 + pending Bug #1066465 [src:dcraw] dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: php8.2: diff for NMU version 8.2.16-2.1
Processing control commands: > tags 1066234 + patch Bug #1066234 [src:php8.2] php8.2: FTBFS: credits.c:130:9: error: implicit declaration of function ‘php_print_packaging_credits’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066234 + pending Bug #1066234 [src:php8.2] php8.2: FTBFS: credits.c:130:9: error: implicit declaration of function ‘php_print_packaging_credits’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066234: php8.2: diff for NMU version 8.2.16-2.1
Control: tags 1066234 + patch Control: tags 1066234 + pending Dear maintainer, I've prepared an NMU for php8.2 (versioned as 8.2.16-2.1) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru php8.2-8.2.16/debian/changelog php8.2-8.2.16/debian/changelog --- php8.2-8.2.16/debian/changelog 2024-02-18 12:09:07.0 +0500 +++ php8.2-8.2.16/debian/changelog 2024-03-15 23:36:01.0 +0500 @@ -1,3 +1,10 @@ +php8.2 (8.2.16-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066234). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:36:01 +0500 + php8.2 (8.2.16-2) unstable; urgency=medium * Regenerate d/tests for correct PHP version (Closes: #1064174) diff -Nru php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch --- php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 22:28:43.0 +0500 @@ -0,0 +1,15 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066234 +Last-Update: 2024-03-15 + +--- php8.2-8.2.16.orig/ext/standard/credits.c php8.2-8.2.16/ext/standard/credits.c +@@ -24,6 +24,7 @@ + #include "php.h" + #include "info.h" + #include "SAPI.h" ++#include "credits.h" + + #define CREDIT_LINE(module, authors) php_info_print_table_row(2, module, authors) + diff -Nru php8.2-8.2.16/debian/patches/series php8.2-8.2.16/debian/patches/series --- php8.2-8.2.16/debian/patches/series 2024-02-18 12:09:07.0 +0500 +++ php8.2-8.2.16/debian/patches/series 2024-03-15 22:28:28.0 +0500 @@ -45,3 +45,4 @@ 0045-scripts-php-.in-Explicitly-define-the-path-to-sed.patch 0046-Remove-timestamps-from-phar.patch 0047-Disable-garbage-collection-routine.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066325: marked as done (calculix-ccx: FTBFS: elemChecker.c:29:7: error: implicit declaration of function ‘v_result’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 23:47:54 +0530 with message-id <20240315181754.6ejcfcbaxehzc...@office.mailbox.org> and subject line Fixed in latest upload has caused the Debian Bug report #1066325, regarding calculix-ccx: FTBFS: elemChecker.c:29:7: error: implicit declaration of function ‘v_result’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calculix-ccx Version: 2.20-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -Wall -I/usr/include/spooles -DARCH=Linux -DSPOOLES -DARPACK > -DMATRIXSTORAGE -DUSE_MT=1 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -c elementcpuload.c > elemChecker.c: In function ‘elemChecker’: > elemChecker.c:29:7: error: implicit declaration of function ‘v_result’ > [-Werror=implicit-function-declaration] >29 | v_result( [elem[i].nod[0]].nx, [elem[i].nod[1]].nx, > v12); > | ^~~~ > elemChecker.c:32:7: error: implicit declaration of function ‘v_prod’ > [-Werror=implicit-function-declaration] >32 | v_prod(v12,v13,vn); > | ^~ > elemChecker.c:34:11: error: implicit declaration of function ‘v_betrag’ > [-Werror=implicit-function-declaration] >34 | bvn=v_betrag(vn); > | ^~~~ > cc -Wall -I/usr/include/spooles -DARCH=Linux -DSPOOLES -DARPACK > -DMATRIXSTORAGE -DUSE_MT=1 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -c expand.c > cc1: some warnings being treated as errors > make[2]: *** [Makefile:9: elemChecker.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/calculix-ccx_2.20-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 2.21-1 Best, Nilesh signature.asc Description: PGP signature --- End Message ---
Processed: mono: diff for NMU version 6.8.0.105+dfsg-3.6
Processing control commands: > tags 1066220 + patch Bug #1066220 [src:mono] mono: FTBFS: gc_dlopen.c:52:30: error: implicit declaration of function ‘GC_collection_in_progress’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066220 + pending Bug #1066220 [src:mono] mono: FTBFS: gc_dlopen.c:52:30: error: implicit declaration of function ‘GC_collection_in_progress’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066220: mono: diff for NMU version 6.8.0.105+dfsg-3.6
Control: tags 1066220 + patch Control: tags 1066220 + pending Dear maintainer, I've prepared an NMU for mono (versioned as 6.8.0.105+dfsg-3.6) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru mono-6.8.0.105+dfsg/debian/changelog mono-6.8.0.105+dfsg/debian/changelog --- mono-6.8.0.105+dfsg/debian/changelog 2023-09-06 17:03:58.0 +0500 +++ mono-6.8.0.105+dfsg/debian/changelog 2024-03-15 22:02:36.0 +0500 @@ -1,3 +1,10 @@ +mono (6.8.0.105+dfsg-3.6) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066220). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 22:02:36 +0500 + mono (6.8.0.105+dfsg-3.5) unstable; urgency=medium * Non-maintainer upload. diff -Nru mono-6.8.0.105+dfsg/debian/patches/debian-changes mono-6.8.0.105+dfsg/debian/patches/debian-changes --- mono-6.8.0.105+dfsg/debian/patches/debian-changes 2023-09-06 17:03:58.0 +0500 +++ mono-6.8.0.105+dfsg/debian/patches/debian-changes 2024-03-15 22:02:36.0 +0500 @@ -24,6 +24,108 @@ Reviewed-By: Last-Update: 2021-06-29 +Index: mono-6.8.0.105+dfsg/Makefile.am +=== +Index: mono-6.8.0.105+dfsg/configure.ac +=== +Index: mono-6.8.0.105+dfsg/data/mono-cairo.pc.in +=== +Index: mono-6.8.0.105+dfsg/data/mono.pc.in +=== +Index: mono-6.8.0.105+dfsg/docs/docs.make +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/DocUtils.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/DocumentationEnumerator.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/CppFormatters/CppFullMemberFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/FSharpFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/JsFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/JsMemberFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/build/monodroid/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/build/monotouch/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/mono/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v2.0/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v3.5/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.0/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7/Makefile
Bug#1066314: regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]
> 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 more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
>
> Relevant part (hopefully):
> > cc -DNDEBUG -g -O2 -Werror=implicit-function-declaration
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security
+-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
-DREGINA_SHARE_DIRECTORY=\"//usr/share/regina-rexx\" -funsigned-char
-DREGINA_VERSION_DATE=\""31 Dec 2011"\" -DREGINA_VERSION_MAJOR=\"3\"
+-DREGINA_VERSION_MINOR=\"6\" -DREGINA_VERSION_SUPP=\"\"
-DHAVE_CONFIG_H-I. -I. -I./contrib-o rexxext.o -c ./rexxext.c
> > ./rexxext.c: In function ‘__regina_rex_getcallstack’:
> > ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’;
> > did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]
> >95 | getcallstack( TSD, parms->value );
> > | ^~~~
> > | popcallstack
> > cc1: some warnings being treated as errors
> > make[1]: *** [Makefile:427: rexxext.o] Error 1
Hi, Lucas and Alen.
While it is easy to fix this particular error (see attached patch,
from upstream repo), other similar error happens afterwards in my
tests. The problem is that this package is way behind upstream and I
think priority is to upgrade to a recent upstream version and then fix
whatever is left.
Not tagging 'patch' since this change alone does not fix build.
Regards,
--- regina-rexx.orig/rexxext.c
+++ regina-rexx/rexxext.c
@@ -55,6 +55,8 @@
# endif
#endif
+extern void getcallstack( tsd_t *TSD, streng *stem );
+
streng *rex_userid( tsd_t *TSD, cparamboxptr parms )
{
#if defined(WIN32)
Bug#1066366: marked as done (libstb: FTBFS: stb_dxt.c:608:7: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 17:56:23 + with message-id and subject line Bug#1065764: fixed in libstb 0.0~git20230129.5736b15+ds-1.2 has caused the Debian Bug report #1065764, regarding libstb: FTBFS: stb_dxt.c:608:7: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstb Version: 0.0~git20230129.5736b15+ds-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, 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 more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -Wdate-time -D_FORTIFY_SOURCE=2 -DSTB_DEFINE -DSTB_PERFECT_HASH > -DSTB_HERRINGBONE_WANG_TILE_IMPLEMENTATION -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -fwrapv -fPIC -o > stb_herringbone_wang_tile.o -c stb_herringbone_wang_tile.c > stb_c_lexer.c:323:20: warning: ‘stb__strchr’ defined but not used > [-Wunused-function] > 323 | static const char *stb__strchr(const char *str, int ch) > |^~~ > stb_herringbone_wang_tile.c:369:41: warning: ‘struct stbhw__process’ declared > inside parameter list will not be visible outside of this definition or > declaration > 369 | typedef void stbhw__process_rect(struct stbhw__process *p, int xpos, > int ypos, > | ^~ > stb_herringbone_wang_tile.c: In function ‘stbhw__process_h_row’: > stb_herringbone_wang_tile.c:401:43: warning: passing argument 1 of > ‘p->process_h_rect’ from incompatible pointer type > [-Wincompatible-pointer-types] > 401 | p->process_h_rect(p, xpos, ypos, a,b,c,d,e,f); > | ^ > | | > | stbhw__process * > stb_herringbone_wang_tile.c:401:43: note: expected ‘struct stbhw__process *’ > but argument is of type ‘stbhw__process *’ > stb_herringbone_wang_tile.c: In function ‘stbhw__process_v_row’: > stb_herringbone_wang_tile.c:425:43: warning: passing argument 1 of > ‘p->process_v_rect’ from incompatible pointer type > [-Wincompatible-pointer-types] > 425 | p->process_v_rect(p, xpos, ypos, a,b,c,d,e,f); > | ^ > | | > | stbhw__process * > stb_herringbone_wang_tile.c:425:43: note: expected ‘struct stbhw__process *’ > but argument is of type ‘stbhw__process *’ > stb_herringbone_wang_tile.c: In function ‘stbhw_build_tileset_from_image’: > stb_herringbone_wang_tile.c:929:21: warning: assignment to ‘void (*)(struct > stbhw__process *, int, int, int, int, int, int, int, int)’ from > incompatible pointer type ‘void (*)(stbhw__process *, int, int, int, int, > int, int, int, int)’ [-Wincompatible-pointer-types] > 929 |p.process_h_rect = stbhw__parse_h_rect; > | ^ > stb_herringbone_wang_tile.c:930:21: warning: assignment to ‘void (*)(struct > stbhw__process *, int, int, int, int, int, int, int, int)’ from > incompatible pointer type ‘void (*)(stbhw__process *, int, int, int, int, > int, int, int, int)’ [-Wincompatible-pointer-types] > 930 |p.process_v_rect = stbhw__parse_v_rect; > | ^ > deprecated/stb.c: In function ‘stb_float_eq’: > deprecated/stb.c:1428:13: warning: dereferencing type-punned pointer will > break strict-aliasing rules [-Wstrict-aliasing] > 1428 |if (abs(*(int *) - *(int *)) <= max_ulps) return 1; > | ^ > stb_dxt.c: In function ‘stb_compress_dxt_block’: > deprecated/stb.c:1428:26: warning: dereferencing type-punned pointer will > break strict-aliasing rules [-Wstrict-aliasing] > 1428 |if (abs(*(int *) - *(int *)) <= max_ulps) return 1; > | ^ > stb_dxt.c:608:7: error:
Bug#1065764: marked as done (libstb: FTBFS on arm{el,hf}: stb_dxt.c:608:7: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 17:56:23 +
with message-id
and subject line Bug#1065764: fixed in libstb 0.0~git20230129.5736b15+ds-1.2
has caused the Debian Bug report #1065764,
regarding libstb: FTBFS on arm{el,hf}: stb_dxt.c:608:7: error: implicit
declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstb
Version: 0.0~git20230129.5736b15+ds-1.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=libstb=armel=0.0%7Egit20230129.5736b15%2Bds-1.1=1709545364=0
stb_dxt.c: In function ‘stb_compress_dxt_block’:
stb_dxt.c:608:7: error: implicit declaration of function ‘memcpy’
[-Werror=implicit-function-declaration]
608 | memcpy(data, src, 4*16);
| ^~
stb_dxt.c:89:1: note: include ‘’ or provide a declaration of ‘memcpy’
88 | #include
+++ |+#include
89 | #endif
stb_dxt.c:608:7: warning: incompatible implicit declaration of built-in
function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
608 | memcpy(data, src, 4*16);
| ^~
stb_dxt.c:608:7: note: include ‘’ or provide a declaration of ‘memcpy’
https://buildd.debian.org/status/fetch.php?pkg=libstb=armel=0.0%7Egit20230129.5736b15%2Bds-1.1=1709545364=0
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libstb
Source-Version: 0.0~git20230129.5736b15+ds-1.2
Done: Andrey Rakhmatullin
We believe that the bug you reported is fixed in the latest version of
libstb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrey Rakhmatullin (supplier of updated libstb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Mar 2024 21:40:23 +0500
Source: libstb
Architecture: source
Version: 0.0~git20230129.5736b15+ds-1.2
Distribution: unstable
Urgency: medium
Maintainer: Yangfl
Changed-By: Andrey Rakhmatullin
Closes: 1065764
Changes:
libstb (0.0~git20230129.5736b15+ds-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1065764).
Checksums-Sha1:
0947b4f8d9f819cc8252c3d21e50bf07e80cc194 2097
libstb_0.0~git20230129.5736b15+ds-1.2.dsc
b37d0e1701fe713290f28554dee7dc8259c5245a 12060
libstb_0.0~git20230129.5736b15+ds-1.2.debian.tar.xz
4de91985cc96d464e85a2d438c78b1491fcac419 6892
libstb_0.0~git20230129.5736b15+ds-1.2_amd64.buildinfo
Checksums-Sha256:
186a7118362188c410b903fda13c48e6039b5ef1cb80c3b7313c2d5c9ffa01e6 2097
libstb_0.0~git20230129.5736b15+ds-1.2.dsc
8d0e9dcc962aea2e5e2c4290d822ed6fcb2e60b6288e6cf6bff01e4efd42f28d 12060
libstb_0.0~git20230129.5736b15+ds-1.2.debian.tar.xz
e27d658ba58583a40efbe6e0db362acb761448aa7e7fa0125503424f73419bd8 6892
libstb_0.0~git20230129.5736b15+ds-1.2_amd64.buildinfo
Files:
5afdd080b583646afc4cea5b5803bc5a 2097 libs optional
libstb_0.0~git20230129.5736b15+ds-1.2.dsc
b8aa6e84edb4a96615a8f71f245e2150 12060 libs optional
libstb_0.0~git20230129.5736b15+ds-1.2.debian.tar.xz
ac5e991ac0d4e70e1dfd824af71d748a 6892 libs optional
libstb_0.0~git20230129.5736b15+ds-1.2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmXwiFUACgkQM2L3AxpJ
kuEooQ//Un53Wv4cU7J0Rlqy8cluEW8oVsS6+FpakplRkxNWQwPrS9je+QGgOCO1
IjphlMoHYa0uOT754LH+OE2qWQYIzK6WvOMe2xCqD/4W+k2wd0brB1gMlkWoYgAR
wdro72ZQxrB0tM6yKURPwUHJPGEV77e+I6CESCah/B6jB0RwuWvVDp8YUPR7hWns
/GHzXcO2BPDcW6CB0i1IO/hrlgy8yAznW/uJe16vwgoGicQDfgp3fZTFd4T7qsGy
DZWU6Ze2anerkTvJMt5Te89AK4gfYruTzgtmhumVdYyWQfQQvV7E08Ixc2m5YxOd
47K7fomMNKPX1ZJGaxOJXYWcgnAUgyk0JSzaHmg+VenT8Yv2Ul7M2y3B3UCftK6J
NUyfuxJjyOrO2DxP7HD/X5i/opi5TThHezsUWwKsILXk/eXeAnMfckZI/AlLe/Bi
slcZK4Co2Wc81Ml/wMqpMDwPUZrRbMolIqQ8PfTVhtMbcEgMdCFrt3mIKpkxzDpR
l7EtqenBzYfVuaXLI7rKgPjFBqwy0/K0Xz1Rr1z67O6bdMa9hH13semDMhuBN6XX
Bug#1066904: marked as done (gi-compile-repository: generates incorrect typelib when cross-compiling with different type sizes)
Your message dated Fri, 15 Mar 2024 17:42:47 + with message-id and subject line Bug#1066904: fixed in glib2.0 2.80.0-2 has caused the Debian Bug report #1066904, regarding gi-compile-repository: generates incorrect typelib when cross-compiling with different type sizes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gobject-introspection Version: 1.78.1-16 Severity: serious Justification: results in misbuilt packages X-Debbugs-Cc: debian-cr...@lists.debian.org When it converts GIR XML to binary typelib files, g-ir-compiler replaces abstract types such as int and gsize (size_t) with concrete types such as gint32 (int32_t) and guint64 (uint32_t). The way in which it does this depends on the type sizes discovered at configure time when compiling g-ir-compiler. This means that cross-compiling for an arm64 or riscv64 host on an amd64 build machine should be OK, but cross-compiling for armhf or i386 on amd64 will produce invalid typelibs. I am sorry that I didn't notice this sooner. A crude solution to this would be to revert gobject-introspection and gobject-introspection-bin to be Multi-Arch: no, so that building typelibs is no longer possible in cross-builds. [1] A more refined version of that would be to change the relationship between gobject-introspection and gobject-introspection-bin so that instead of the current arrangement where the dependency is on a virtual package gobject-introspection-linux-little-endian, it would be on a virtual package that also reflects the word size in use: gobject-introspection-linux-lp64-little-endian or similar. This would preserve the ability to cross-compile in only those situations where it would be correct. [2] A workaround to enable cross-compiling between word sizes would be to use the host architecture g-ir-compiler, and run it via qemu-user. Unfortunately this will greatly increase the amount of host-architecture code that needs to be run via emulation. In the short term, I'm going to do [1] or [2] as a matter of urgency, to ensure that Ubuntu 24.04 doesn't ship with faulty cross-tools that claim to work but actually do not. Any further improvement can be in-scope for #1030223 "gobject-introspection: make cross-compilation possible". If we do [2] then we will have to be extra-careful to distinguish between dissimilar ILP32 ABIs, because gobject-introspection currently hard-codes that it thinks time_t is long and off_t is size_t, both of which happen to be correct on LP64 and on i386, but neither of which is correct on an ILP32 architecture that has transitioned to large file support and 64-bit time_t (such as armel and armhf in 2024) or an ILP32 architecture that always had 64-bit off_t and time_t (such as x32). I apologise for having been insufficiently careful when enabling this feature. smcv --- End Message --- --- Begin Message --- Source: glib2.0 Source-Version: 2.80.0-2 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of glib2.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated glib2.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Mar 2024 15:11:52 + Source: glib2.0 Architecture: source Version: 2.80.0-2 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1066904 Changes: glib2.0 (2.80.0-2) experimental; urgency=medium . * Use host-architecture gi-compile-repository, etc. when cross-compiling. When setting up the cross wrappers for gi-compile-repository, etc. I had assumed that gi-compile-repository was a simple transformation from GIR XML into binary, which varied only by its endianness. Unfortunately, it is not: it also transforms abstract types such as size_t into equivalent fixed-size types such as guint64, which requires knowledge of the size of each type.
Bug#1065598: marked as done (gcc-13-offload-nvptx: openmp offload compile fails due to missing libgomp.spec)
Your message dated Fri, 15 Mar 2024 17:40:37 + with message-id and subject line Bug#1065598: fixed in gcc-13 13.2.0-19 has caused the Debian Bug report #1065598, regarding gcc-13-offload-nvptx: openmp offload compile fails due to missing libgomp.spec to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-13-offload-nvptx Version: 13.2.0-18 Severity: grave Justification: renders package unusable Dear Maintainer, due to a different organisation in file installation with respect to gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the following: x86_64-linux-gnu-accel-nvptx-none-gcc-13: fatal error: cannot read spec file 'libgomp.spec': No such file or directory compilation terminated. nvptx mkoffload: fatal error: x86_64-linux-gnu-accel-nvptx-none-gcc-13 returned 1 exit status compilation terminated. lto-wrapper: fatal error: /usr/libexec/gcc/x86_64-linux-gnu/13//accel/nvptx-none/mkoffload returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed While gcc-12-offload-nvptx installed executables, includes, and libs under /usr/lib/gcc/x86_64-linux-gnu/12/accel/nvptx-none, and found them, gcc-13-offload-nvptx does not appear to install them anywhere, nor to depend on any other separate package that does. This effectively renders the package unusable. While the gcc-12 offload still works, gcc-13 is now the default compiler on sid, meaning that trying to compile openmp to offload to nvptx with the default compiler fails. Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.7-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gcc-13-offload-nvptx depends on: ii gcc-13 13.2.0-18 ii gcc-13-base13.2.0-18 ii libc6 2.37-15.1 ii libc6-dev 2.37-15.1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii libgomp-plugin-nvptx1 14-20240303-1 ii libmpc31.3.1-1+b2 ii libmpfr6 4.2.1-1+b1 ii libzstd1 1.5.5+dfsg2-2 ii nvptx-tools0.20230904-1 ii zlib1g 1:1.3.dfsg-3.1 gcc-13-offload-nvptx recommends no packages. gcc-13-offload-nvptx suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gcc-13 Source-Version: 13.2.0-19 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-13, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-13 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 17:33:18 +0100 Source: gcc-13 Architecture: source Version: 13.2.0-19 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1065598 Changes: gcc-13 (13.2.0-19) unstable; urgency=medium . * Update to git 20240315 from the gcc-13 branch. - Fix PR middle-end/95351, PR driver/114314, PR target/101737 (SH), PR ada/113979, PR d/112285, PR d/112290, PR d/114171, PR fortran/114012, PR fortran/114024, PR libfortran/105437, PR libfortran/114304, PR libfortran/105473, PR libstdc++/110167. * Fix installation of the amdgcn offload compiler. * Fix installation of the nvptx offload compiler. Closes: #1065598. * ASan: move allocator base to avoid conflict with high-entropy ASLR for x86-64 Linux. Patch taken from LLVM. LP: #2048768. Checksums-Sha1
Processed: Re: Bug#1066910: chromium: downloads non-free component libchromescreenai.so without asking
Processing control commands: > tags -1 bookworm trixie sid Bug #1066910 [chromium] chromium: downloads non-free component libchromescreenai.so without asking Added tag(s) trixie, bookworm, and sid. -- 1066910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066910: chromium: downloads non-free component libchromescreenai.so without asking
Control: tags -1 bookworm trixie sid On 3/15/24 06:57, Helmut Grohne wrote: Package: chromium Version: 122.0.6261.128-1 Severity: serious In recent versions, chromium started downloading a file ~/.config/chromium/screen_ai/*/libchromescreenai.so. Evidently, the source of this shared object is not in the chromium source package. I think the chromium package - being in main - should not download a shared object and run it without user confirmation. Helmut Thanks for reporting this! It looks like this is controlled with the enable_screen_ai_service, I'll test that & fix it in the next series of upload. OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066543: ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
On Wed, Mar 13, 2024 at 12:57:48PM +0100, Lucas Nussbaum wrote: > > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= > > -I/<>/src -I/<> -I/<>/src > > -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables > > -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label > > -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar > > -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 > > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > > -fstack-protector-strong -fstack-clash-protection -Wformat > > -Werror=format-security -fcf-protection -nostdlib -std=c++11 -c > > ucp_tests.cc -fPIC -DPIC -o .libs/libucxperf_la-ucp_tests.o > > cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > > is not valid for C++ [-Werror] > > cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > > is not valid for C++ [-Werror] Two notes here after a local sbuild build. First, these are warnings, not errors. Not sure what's the difference, it also has -Werror passed and gcc is also 13.2.0-18, but I don't see the "all warnings being treated as errors" text. The command: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= -I/<>/src -I/<> -I/<>/src -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -nostdlib -std=c++11 -c ucp_tests.cc -fPIC -DPIC -o .libs/libucxperf_la-ucp_tests.o Second, the build also failed, and also in the same directory, but for a totally different cause: libtool: link: gcc -O3 -g -Wall -Werror -funwind-tables -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch -Wno-pointer-sign -Werror-implicit-function-declaration -Wno-format-zero-length -Wnested-externs -Wshadow -Werror=declaration-after-statement -fopenmp -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-dynamic-list-data -Wl,-z -Wl,relro -o .libs/ucx_perftest ucx_perftest-perftest.o ucx_perftest-perftest_run.o ucx_perftest-perftest_params.o ucx_perftest-perftest_mad.o -libmad -libumad lib/.libs/libucxperf.a /<>/src/ucp/.libs/libucp.so /<>/src/uct/.libs/libuct.so /<>/src/ucs/.libs/libucs.so -lm /<>/src/ucm/.libs/libucm.so -ldl -lrt -fopenmp /usr/bin/ld: lib/.libs/libucxperf.a(libucxperf_la-uct_tests.o):(.data.rel.local.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0' -- WBR, wRAR signature.asc Description: PGP signature
Processed: Bug#1066904 marked as pending in glib2.0
Processing control commands: > tag -1 pending Bug #1066904 [libglib2.0-dev] gi-compile-repository: generates incorrect typelib when cross-compiling with different type sizes Added tag(s) pending. -- 1066904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066904: marked as pending in glib2.0
Control: tag -1 pending
Hello,
Bug #1066904 in glib2.0 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/glib/-/commit/22ad69bf8f1470d36b4fd99442470cc1dfd3c74f
Use host-architecture gi-compile-repository, etc. when cross-compiling
When setting up the cross wrappers for gi-compile-repository, etc. I had
assumed that gi-compile-repository was a simple transformation from
GIR XML into binary, which varied only by its endianness. Unfortunately,
it is not: it also transforms abstract types such as size_t into
equivalent fixed-size types such as guint64, which requires knowledge
of the size of each type.
Instead of running the build architecture gi-compile-repository and
telling it to use the host architecture search path, install upstream's
gi-compile-repository etc. into ${pkglibdir}, and set up cross wrappers
that will automatically detect whether we can run them directly or
whether we must use qemu-user. This is not "pure" cross-compilation,
but it's the best we can do.
This means that the build and host OS must match, but it does have the
side benefit that we no longer require the build and host endianness to
be the same, because everything that interacts the typelib is now a
host binary (possibly running under qemu).
Closes: #1066904
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1066904
Bug#1065715: marked as done (xgks: FTBFS on arm{el,hf}: ERROR: The following variables need values)
Your message dated Fri, 15 Mar 2024 16:38:59 +
with message-id
and subject line Bug#1065715: fixed in xgks 2.6.1+dfsg.2-15
has caused the Debian Bug report #1065715,
regarding xgks: FTBFS on arm{el,hf}: ERROR: The following variables need values
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xgks
Version: 2.6.1+dfsg.2-14.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=xgks=armel=2.6.1%2Bdfsg.2-14.1=1709543440=0
checking for X11 library...
checking for XNoOp(0) in default library(s)... no
checking for XNoOp(0) in -lX11... no
checking for XNoOp(0) in -L/usr/lib -lX11... no
checking for XNoOp(0) in -L/usr/lib/X11 -lX11... no
checking for XNoOp(0) in -L/usr/X11/lib -lX11... no
checking for XNoOp(0) in -L/usr/lib/X11R5 -lX11... no
checking for XNoOp(0) in -L/usr/local/lib -lX11... no
checking for XNoOp(0) in -L/usr/local/lib/X11 -lX11... no
checking for XNoOp(0) in -L/usr/local/lib/X11R5 -lX11... no
checking for package version... 2.6
../src/configure: ERROR: The following variables need values:
VARIABLE DESCRIPTIONEXAMPLE
------
LD_X11 X11 library-L/usr/lib/X11 -lX11
The above variables may be set in the environment or in the file
CUSTOMIZE. Variables referring to executable programs needn't be set
if the relevant directory is added to PATH. In any case, ./configure
should probably be rerun. See file INSTALL for details.
make[1]: *** [debian/rules:36: override_dh_auto_configure] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: xgks
Source-Version: 2.6.1+dfsg.2-15
Done: Alastair McKinstry
We believe that the bug you reported is fixed in the latest version of
xgks, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated xgks package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Mar 2024 15:57:15 +
Source: xgks
Architecture: source
Version: 2.6.1+dfsg.2-15
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry
Changed-By: Alastair McKinstry
Closes: 1065715
Changes:
xgks (2.6.1+dfsg.2-15) unstable; urgency=medium
.
* Fixes for implicit-function-declaration errors. Closes: #1065715
* Replace recommends: pkg-config -> pkgconf
Checksums-Sha1:
7fbfa3831d9ce53e64d7446bbe08ac5e57f9a6b9 2112 xgks_2.6.1+dfsg.2-15.dsc
9b52c322e566630f3f13f27438d873c6708c1440 106908
xgks_2.6.1+dfsg.2-15.debian.tar.xz
Checksums-Sha256:
c94fe854787cfdf2cfb3c4ed3424faf8cf597723119ea0020d27974916828ab1 2112
xgks_2.6.1+dfsg.2-15.dsc
a041daef20f60553ed81523d6ac38f48dfbc2ca9d3ef5981fdb608a2d4797a04 106908
xgks_2.6.1+dfsg.2-15.debian.tar.xz
Files:
df51c1ba24aa676a6825f75d1c5536cd 2112 utils optional xgks_2.6.1+dfsg.2-15.dsc
7c4591e261b633f85b10dc61355e777e 106908 utils optional
xgks_2.6.1+dfsg.2-15.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmX0cGAACgkQy+a7Tl2a
06VVHQ/9HvWLsOBGJSA4Fq99Y1ejPr03QpLx5zeRls2vVIpuU36t5yg3kUo28S/U
NC+lS7On+5RQQjDyf8tvGBTw9yNHtlTKRs68yeBmHgng6rboHvuAi9h4MbliEtPO
w/Q6ZRNiPONazrTvPsv9vdHNCHLhFIb0NlzjdsfBjD98CSv6XACzG1Ua7bmhopnc
2/GBnsScb79GRqpeGcSzsU4j95fFgX10M4FC0Gwxt88BH/4qxO531TJJQ8GtH82O
jvl0vjo4O0oW0GwHwslT3+swtP0wsEIYTpRnrOSjwEKQhinkFnP0uFdUjSfqdeNr
4DLrsd0J214H8j0Gvkqg/je9APH6u5nciVE57gDfKB+e7DSFI4KBAheWUIX2+/ky
hKi6bAIMS+ie81qoxsjcYiIhfQhGBPAYBtuja/r9ugyH3WjyJiQDvdjhLX4ofDSv
5Qlyg0otGxVFaB3xNG2wO7D4KCliHMqoWTWMb5t496/YLuqcyTMxWPJNoqUtJh92
YCx9mbo7C/Yu7h1TguYcryE49w80YXMOyM4Wm17X3QYqhYqsKI1W1jmvz7AVM4Pi
SujS4iGBpPR3vgQ/OClPogt2zeHWOj7iSrUERr/AfJwrbRJ1tYxi0E28d9pixoBf
cQ2BY/CfWfgflw701FdDeZgv7ztiRgoCImwPovc2kdva93+1I1g=
=XiFy
-END PGP SIGNATURE-
pgphA9SPYBLHy.pgp
Description: PGP signature
--- End Message ---
Bug#1066900: marked as done (g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes)
Your message dated Fri, 15 Mar 2024 16:00:43 + with message-id and subject line Bug#1066900: fixed in gobject-introspection 1.78.1-17 has caused the Debian Bug report #1066900, regarding g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gobject-introspection Version: 1.78.1-16 Severity: serious Justification: results in misbuilt packages X-Debbugs-Cc: debian-cr...@lists.debian.org When it converts GIR XML to binary typelib files, g-ir-compiler replaces abstract types such as int and gsize (size_t) with concrete types such as gint32 (int32_t) and guint64 (uint32_t). The way in which it does this depends on the type sizes discovered at configure time when compiling g-ir-compiler. This means that cross-compiling for an arm64 or riscv64 host on an amd64 build machine should be OK, but cross-compiling for armhf or i386 on amd64 will produce invalid typelibs. I am sorry that I didn't notice this sooner. A crude solution to this would be to revert gobject-introspection and gobject-introspection-bin to be Multi-Arch: no, so that building typelibs is no longer possible in cross-builds. [1] A more refined version of that would be to change the relationship between gobject-introspection and gobject-introspection-bin so that instead of the current arrangement where the dependency is on a virtual package gobject-introspection-linux-little-endian, it would be on a virtual package that also reflects the word size in use: gobject-introspection-linux-lp64-little-endian or similar. This would preserve the ability to cross-compile in only those situations where it would be correct. [2] A workaround to enable cross-compiling between word sizes would be to use the host architecture g-ir-compiler, and run it via qemu-user. Unfortunately this will greatly increase the amount of host-architecture code that needs to be run via emulation. In the short term, I'm going to do [1] or [2] as a matter of urgency, to ensure that Ubuntu 24.04 doesn't ship with faulty cross-tools that claim to work but actually do not. Any further improvement can be in-scope for #1030223 "gobject-introspection: make cross-compilation possible". If we do [2] then we will have to be extra-careful to distinguish between dissimilar ILP32 ABIs, because gobject-introspection currently hard-codes that it thinks time_t is long and off_t is size_t, both of which happen to be correct on LP64 and on i386, but neither of which is correct on an ILP32 architecture that has transitioned to large file support and 64-bit time_t (such as armel and armhf in 2024) or an ILP32 architecture that always had 64-bit off_t and time_t (such as x32). I apologise for having been insufficiently careful when enabling this feature. smcv --- End Message --- --- Begin Message --- Source: gobject-introspection Source-Version: 1.78.1-17 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gobject-introspection, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gobject-introspection package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Mar 2024 13:14:58 + Source: gobject-introspection Architecture: source Version: 1.78.1-17 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1066900 Changes: gobject-introspection (1.78.1-17) unstable; urgency=medium . [ Simon McVittie, Jeremy Bícha ] * Add a nogir build profile . [ Simon McVittie ] * d/control: Correct a misleading comment. It's g-ir-scanner, not g-ir-compiler, that runs the dumper executable. * Use host-architecture g-ir-compiler, etc. when cross-compiling. When setting up the cross wrappers for g-ir-compiler, etc. I had assumed that g-ir-compiler was a simple
Processed: notfound 1010445 in 6.12.0.122-0xamarin1+ubuntu2004b1, found 1010445 in 6.8.0.105+dfsg-3.3
Processing commands for cont...@bugs.debian.org: > notfound 1010445 6.12.0.122-0xamarin1+ubuntu2004b1 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) There is no source info for the package 'mono-complete' at version '6.12.0.122-0xamarin1+ubuntu2004b1' with architecture '' Unable to make a source version for version '6.12.0.122-0xamarin1+ubuntu2004b1' No longer marked as found in versions 6.12.0.122-0xamarin1+ubuntu2004b1. > found 1010445 6.8.0.105+dfsg-3.3 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) Marked as found in versions mono/6.8.0.105+dfsg-3.3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to kannel, tagging 1066507
Processing commands for cont...@bugs.debian.org: > limit source kannel Limiting to bugs with field 'source' containing at least one of 'kannel' Limit currently set to 'source':'kannel' > tags 1066507 + pending Bug #1066507 [src:kannel] kannel: FTBFS: configure: error: Either get a multithread-enabled SSL or configure with --disable-ssl Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1065767 1066319
Processing commands for cont...@bugs.debian.org:
> forcemerge 1065767 1066319
Bug #1065767 [src:libopendbx] libopendbx: FTBFS on arm{el,hf}:
mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’
[-Werror=implicit-function-declaration]
Bug #1066319 [src:libopendbx] libopendbx: FTBFS: mssql_basic.c:324:21: error:
implicit declaration of function ‘dbpoll’
[-Werror=implicit-function-declaration]
Merged 1065767 1066319
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065767
1066319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066900: marked as pending in gobject-introspection
Control: tag -1 pending
Hello,
Bug #1066900 in gobject-introspection 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/gobject-introspection/-/commit/8c7f723a539331a8203f86bc6b89d2473dd916ce
Use host-architecture g-ir-compiler, etc. when cross-compiling
When setting up the cross wrappers for g-ir-compiler, etc. I had
assumed that g-ir-compiler was a simple transformation from
GIR XML into binary, which varied only by its endianness. Unfortunately,
it is not: it also transforms abstract types such as size_t into
equivalent fixed-size types such as guint64, which requires knowledge
of the size of each type.
Instead of running the build architecture g-ir-compiler and
telling it to use the host architecture search path, install upstream's
g-ir-compiler etc. into ${pkglibdir}, and set up cross wrappers
that will automatically detect whether we can run them directly or
whether we must use qemu-user. We already had logic for this for the
dumper executable that is run by g-ir-scanner, which is always a
host-architecture binary.
This involves running qemu more often, but does have the side benefit
that we no longer require the build and host endianness to be the same,
because everything that interacts the typelib is now a host binary
(possibly running under emulation).
Closes: #1066900
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1066900
Processed: Bug#1066900 marked as pending in gobject-introspection
Processing control commands: > tag -1 pending Bug #1066900 [gobject-introspection] g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes Ignoring request to alter tags of bug #1066900 to the same tags previously set -- 1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066929: Package outdated, crippled, unfit for release
Source: bcachefs-tools Version: 24+really1.3.4-2 Severity: serious I don't think bcachefs-tools in its current state is fit for release. * The package is severely behind: Debian is currently at 1.3.4. Upstream is at 1.6.4. * Chronologically speaking, 1.3.4 was released in November 2023, so in theory, it's not that old. In practice, however, bcachefs is a fast-moving project, and in particular the past few months have been critical both in terms of pace, and in terms of stabilization: bcachefs was merged in the upstream Linux kernel, starting with v6.7, released in January 2024. Linux 6.8 was released this week as well, with even more fixes, including the ability to use the in-kernel fsck. * Linux v6.7 entered unstable this week, which opens up the user base for this package quite a bit. Especially with the recent hype, others may be inclined to try it, and be surprised by back-and-forth metadata migrations between kernel and userspace, as a concrete example of a problem. * Moreover, even the outdated version that we have in Debian is crippled, because large parts of its functionality are missing: all the Rust functionality included in this software, which is ever increasing (up to being required, in newer upstream releases). This has been reported previously as #1060256. * I'd also argue that the package lacks attentive maintainership, and would recommend to orphan and/or find one or more comaintainers: - There are various packaging issues: wrong version number, branches not pushed into git etc. etc. (most reported as #1054620) - There hasn't been any coordination/two-way street with upstream; I contributed a bunch of PRs to help with the Rust integration bits in Debian, and I know Steinar was in touch with them as well, but none of this was done by the package maintainer or in coordination with them. - No serious effort was made to package the Rust bits before. I worked on it and made it happen with only a few hours of work, as documented in that bug report above. - There hasn't been any coordinated system integration effort with other Debian packages like grub/initramfs-tools/etc. #1061525 describes issues that are across projects and up for us, the distributor, to really triage and coordinate fixes for. - Finally, while a bunch of work happened by others, like myself paving the road for the Rust bits to be enabled, and by Steinar to prepare fixed packages (and even an NMU), there hasn't been an appropriate level of response to our contributions IMHO, that would have included in an upload that includes all of these fixes. We are basically blocked. Now, I realize that the maintainer may be quite busy with other tasks, including what I can only image is a busy Debian workload due to some other, erm, duties (for which I'm thankful!). In an effort to be more collegial, I've even reached out in private, twice. But, I think we are at the point where weeks pass while the state of this package is simply not OK, a disservice to our users, and unfit for release, hence this RC bug. This is a filesystem we're talking about, so outdated/buggy software can even mean broader system-wide issues including data corruption. In terms of a path forward: I would recommend to upload the package as prepared by Steinar ASAP, and/or submit an RFH/O for the long-term maintainership of the package. Best, Faidon
Bug#1062896: shishi: NMU diff for 64-bit time_t transition
reopen 1062896
thanks
Benjamin Drung writes:
> Source: shishi
> Dear maintainer,
>
> Please find attached a final version of this patch for the time_t
> transition. This patch is being uploaded to unstable.
>
> Note that this adds a versioned build-dependency on dpkg-dev, to guard
> against accidental backports with a wrong ABI.
Thanks for working on this.
I noticed that autopkgtest for 1.0.3-2.1 fails on i386:
https://ci.debian.net/packages/s/shishi/testing/i386/43439759/
It is time related:
100s PASS: gcc tests/gztime.c
100s Segmentation fault
Debugging this (with help from #debian-devel) led me down several chains
of discoveries. I believe that this package has enabled and assumes
64-bit time_t on all 32-bit platforms for a long time, including i386.
Look at how the old version before your changes behave:
jas@kaka:~$ podman run --arch=386 -it --rm debian:testing
root@78d65bc11b9f:/# cat /etc/apt/sources.list.d/debian.sources | sed 's,:
deb,: deb-src,' > /etc/apt/sources.list.d/src.sources
root@78d65bc11b9f:/# apt update
root@78d65bc11b9f:~# apt install libshishi-dev build-essential
Get:76 http://deb.debian.org/debian testing/main i386 libshishi-dev i386
1.0.3-2 [217 kB]
root@78d65bc11b9f:~# apt source shishi
root@78d65bc11b9f:~# cd shishi-1.0.3/
root@78d65bc11b9f:~/shishi-1.0.3# touch config.h
root@78d65bc11b9f:~/shishi-1.0.3# WORKDIR=.
root@78d65bc11b9f:~/shishi-1.0.3# gcc -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-I$WORKDIR -Ilib/gl -D_GL_ATTRIBUTE_CONST= -DPACKAGE='"shishi"' -o $WORKDIR/foo
tests/gztime.c `pkg-config --cflags --libs shishi`
root@78d65bc11b9f:~/shishi-1.0.3# ./foo
root@78d65bc11b9f:~/shishi-1.0.3# gcc -I$WORKDIR -Ilib/gl
-D_GL_ATTRIBUTE_CONST= -DPACKAGE='"shishi"' -o $WORKDIR/foo tests/gztime.c
`pkg-config --cflags --libs shishi`
root@78d65bc11b9f:~/shishi-1.0.3# ./foo
Segmentation fault (core dumped)
root@78d65bc11b9f:~/shishi-1.0.3#
This suggests passing 32-bit time_t to this library break before your
change, and it breaks after your changes too. See earlier debci failure
for 1.0.3-2 without your t64 changes here that confirms this hypothesis:
https://ci.debian.net/packages/s/shishi/testing/i386/43917754/
So the library is 64-bit only even on 32-bit architectures, or at least
i386, I briefly compared build logs on armhf too.
You can re-run the snippet above on unstable instead, and you will see
it behaves the same for 1.0.3-2.1. So the t64 patches did not modify
any ABI at all.
As far as I understand, this means this package does not need any
t64-migration at all, and your NMU should be reverted. Do you agree?
Arguable the package header .h file should not use the time_t type since
the shared library ABI will only work if the application uses 64-bit
time_t, but on i386 the normal approach is to have 32-bit time_t. This
would be an upstream wishlist, it was suggested to replace time_t with
int64_t so that callers that pass 32-bit time_t would get automatically
extended, which is one solution.
/Simon
> Thanks!
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: unable to detect
>
> diff -Nru shishi-1.0.3/debian/changelog shishi-1.0.3/debian/changelog
> --- shishi-1.0.3/debian/changelog 2024-01-30 16:09:13.0 +
> +++ shishi-1.0.3/debian/changelog 2024-02-29 15:52:14.0 +
> @@ -1,3 +1,10 @@
> +shishi (1.0.3-2.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Rename libraries for 64-bit time_t transition. Closes: #1062896
> +
> + -- Benjamin Drung Thu, 29 Feb 2024 15:52:14 +
> +
> shishi (1.0.3-2) unstable; urgency=medium
>
>[ Simon Josefsson ]
> diff -Nru shishi-1.0.3/debian/control shishi-1.0.3/debian/control
> --- shishi-1.0.3/debian/control 2024-01-30 15:57:25.0 +
> +++ shishi-1.0.3/debian/control 2024-02-29 15:52:14.0 +
> @@ -5,7 +5,7 @@
> Uploaders:
> Simon Josefsson ,
> Russ Allbery ,
> -Build-Depends:
> +Build-Depends: dpkg-dev (>= 1.22.5),
> debhelper-compat (= 13),
> libgcrypt-dev,
> libgnutls28-dev,
> @@ -25,7 +25,10 @@
> Homepage: https://www.gnu.org/software/shishi/
> Rules-Requires-Root: no
>
> -Package: libshishi0
> +Package: libshishi0t64
> +Provides: ${t64:Provides}
> +Replaces: libshishi0
> +Breaks: libshishi0 (<< ${source:Version})
> Section: libs
> Architecture: any
> Multi-Arch: same
> @@ -63,7 +66,7 @@
> Architecture: any
> Multi-Arch: same
> Depends:
> - libshisa0 (= ${binary:Version}),
> + libshisa0t64 (= ${binary:Version}),
> libshishi-dev (= ${binary:Version}),
> ${misc:Depends},
> Description: Development files for the
Processed: Re: Bug#1062896: shishi: NMU diff for 64-bit time_t transition
Processing commands for cont...@bugs.debian.org:
> reopen 1062896
Bug #1062896 {Done: Benjamin Drung } [src:shishi] shishi:
NMU diff for 64-bit time_t transition
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions shishi/1.0.3-2.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1062896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066578: marked as done (xsunpinyin: FTBFS: ic.c:323:5: error: implicit declaration of function ‘ui_tray_init’ [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 13:39:04 +
with message-id
and subject line Bug#1066578: fixed in xsunpinyin 2.0.3-9
has caused the Debian Bug report #1066578,
regarding xsunpinyin: FTBFS: ic.c:323:5: error: implicit declaration of
function ‘ui_tray_init’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xsunpinyin
Version: 2.0.3-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
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 more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -o ic.o -c -O2 -g -pipe
> -DSUNPINYIN_XIM_ICON_DIR=\"/usr/share/xsunpinyin/icons/\"
> -DSUNPINYIN_XIM_SETTING_DIR=\"/usr/share/xsunpinyin/\"
> -Werror=implicit-function-declaration -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -pthread -I. -IIMdkit -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0
> -I/usr/include/sunpinyin-2.0 -I/usr/include/sunpinyin-2.0/ime-core
> -I/usr/include/sunpinyin-2.0/lexicon -I/usr/include/sunpinyin-2.0/pinyin
> -I/usr/include/sunpinyin-2.0/slm -I/usr/include/sunpinyin-2.0/slm/getwordfreq
> -I/usr/include/sunpinyin-2.0/slm/ids2ngram
> -I/usr/include/sunpinyin-2.0/slm/mmseg
> -I/usr/include/sunpinyin-2.0/slm/slmbuild
> -I/usr/include/sunpinyin-2.0/slm/slminfo
> -I/usr/include/sunpinyin-2.0/slm/slmpack
> -I/usr/include/sunpinyin-2.0/slm/slmprune
> -I/usr/include/sunpinyin-2.0/slm/slmseg
> -I/usr/include/sunpinyin-2.0/slm/thread
> -I/usr/include/sunpinyin-2.0/slm/tools
> -I/usr/include/sunpinyin-2.0/slm/tslmendian
> -I/usr/include/sunpinyin-2.0/slm/tslminfo ic.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
> from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
> from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
> from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
> from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
> from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
> from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:33,
> from ic.h:39,
> from ic.c:48:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
> deprecated [-Wdeprecated-declarations]
> 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
> | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
> from /usr/include/glib-2.0/gobject/gbinding.h:31,
> from /usr/include/glib-2.0/glib-object.h:24,
> from /usr/include/glib-2.0/gio/gioenums.h:30,
> from /usr/include/glib-2.0/gio/giotypes.h:30,
> from /usr/include/glib-2.0/gio/gio.h:28,
> from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
> from /usr/include/gtk-2.0/gdk/gdk.h:32,
> from /usr/include/gtk-2.0/gtk/gtk.h:32:
> /usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
> 723 | {
> | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
> from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
> from /usr/include/gtk-2.0/gtk/gtk.h:126:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
>73 | GTimeVal last_popdown;
> | ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:34,
> from
Bug#1066571: marked as done (sane-frontends: FTBFS: sanei_init_debug.c:103:17: error: implicit declaration of function ‘isfdtype’; did you mean ‘isctype’? [-Werror=implicit-function-declaration])
Your message dated Fri, 15 Mar 2024 13:21:17 +
with message-id
and subject line Bug#1066571: fixed in sane-frontends 1.0.14-18
has caused the Debian Bug report #1066571,
regarding sane-frontends: FTBFS: sanei_init_debug.c:103:17: error: implicit
declaration of function ‘isfdtype’; did you mean ‘isctype’?
[-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sane-frontends
Version: 1.0.14-17
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
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 more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -Wdate-time
> -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE
> -DPATH_SANE_DATA_DIR=/usr/share/sane-DV_MAJOR=1 -DV_MINOR=0 -DV_BUILD=14
> -DSANE_V_MAJOR=1 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wall sanei_load_values.c
> sanei_wire.c: In function ‘sanei_w_array’:
> sanei_wire.c:213:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 4 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 213 | DBG (0, "sanei_w_array: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~
> 214 |"exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> 215 |MAX_MEM, len * element_size, MAX_MEM + len *
> element_size);
> | ~~
> | |
> | size_t {aka long unsigned int}
> sanei_wire.c:214:59: note: format string is defined here
> 214 |"exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> | unsigned int
> | %lu
> sanei_wire.c:213:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 213 | DBG (0, "sanei_w_array: DECODE: maximum amount of
> allocated memory "
> |
> ^~~~
> sanei_wire.c:214:70: note: format string is defined here
> 214 |"exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> |
> unsigned int
> |
> %lu
> sanei_wire.c: In function ‘sanei_w_ptr’:
> sanei_wire.c:291:23: warning: format ‘%u’ expects argument of type ‘unsigned
> int’, but argument 4 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 291 | DBG (0, "sanei_w_ptr: DECODE: maximum amount of
> allocated memory "
> |
> ^~
> 292 |"exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> 293 |MAX_MEM, value_size, (w->allocated_memory +
> value_size));
> | ~~
> | |
> | size_t {aka long unsigned int}
> sanei_wire.c:292:59: note: format string is defined here
> 292 |"exceeded (limit: %u, new allocation: %u, total:
> %u bytes)\n",
> | ~^
> | |
> |
Processed: tagging 1066900
Processing commands for cont...@bugs.debian.org: > tags 1066900 + pending Bug #1066900 [gobject-introspection] g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061752: marked as done (python-django-tagging ftbfs with Python 3.12 as default)
Your message dated Fri, 15 Mar 2024 12:22:34 +
with message-id
and subject line Bug#1061752: fixed in python-django-tagging 1:0.5.0-5.1
has caused the Debian Bug report #1061752,
regarding python-django-tagging ftbfs with Python 3.12 as default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-django-tagging
Version: 1:0.5.0-5
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails to build:
[...]
==
ERROR: test_tag_get_from_model
(tagging.tests.tests.TestTagFieldInForms.test_tag_get_from_model)
--
Traceback (most recent call last):
File "/<>/tagging/tests/tests.py", line 1142, in
test_tag_get_from_model
self.assertEquals(FormTest.tags, 'test1 test2 test3 titi toto')
^
AttributeError: 'TestTagFieldInForms' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
==
ERROR: test_view_404
(tagging.tests.tests.TestTaggedObjectList.test_view_404)
--
Traceback (most recent call last):
File "/<>/tagging/tests/tests.py", line 1227, in
test_view_404
self.get_view('/unavailable/', code=404)
File "/<>/tagging/tests/tests.py", line 1197, in get_view
self.assertEquals(response.status_code, code)
^
AttributeError: 'TestTaggedObjectList' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
==
ERROR: test_view_dynamic
(tagging.tests.tests.TestTaggedObjectList.test_view_dynamic)
--
Traceback (most recent call last):
File "/<>/tagging/tests/tests.py", line 1212, in
test_view_dynamic
self.get_view('/tag/', expected_items=1)
File "/<>/tagging/tests/tests.py", line 1197, in get_view
self.assertEquals(response.status_code, code)
^
AttributeError: 'TestTaggedObjectList' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
==
ERROR: test_view_related
(tagging.tests.tests.TestTaggedObjectList.test_view_related)
--
Traceback (most recent call last):
File "/<>/tagging/tests/tests.py", line 1215, in
test_view_related
response = self.get_view('/static/related/',
^
File "/<>/tagging/tests/tests.py", line 1197, in get_view
self.assertEquals(response.status_code, code)
^
AttributeError: 'TestTaggedObjectList' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
==
ERROR: test_view_static
(tagging.tests.tests.TestTaggedObjectList.test_view_static)
--
Traceback (most recent call last):
File "/<>/tagging/tests/tests.py", line 1209, in
test_view_static
self.get_view('/static/', expected_items=2)
File "/<>/tagging/tests/tests.py", line 1197, in get_view
self.assertEquals(response.status_code, code)
^
AttributeError: 'TestTaggedObjectList' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
--
Ran 75 tests in 0.534s
FAILED (errors=5)
--- End Message ---
--- Begin Message ---
Source: python-django-tagging
Source-Version: 1:0.5.0-5.1
Done: Christoph Martin
We believe that the bug you reported is fixed in the latest version of
python-django-tagging, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Martin (supplier of updated
python-django-tagging package)
(This message was generated automatically at
Bug#1065654: marked as done (mesa ftbfs with time_t64)
Your message dated Fri, 15 Mar 2024 11:57:55 + with message-id and subject line Bug#1065654: fixed in mesa 24.0.3-1 has caused the Debian Bug report #1065654, regarding mesa ftbfs with time_t64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mesa Version: 24.0.2-1 Severity: serious Tags: sid trixie patch mesa ftbfs with time_t64, patch attached. I didn't check if the _TIMET_BITS are used in the affected files. There's also a bug in the profile support. WINE cannot be built without LLVM, and therefore should be disabled.reverted: --- mesa-24.0.2/.pc/.quilt_patches +++ mesa-24.0.2.orig/.pc/.quilt_patches @@ -1 +0,0 @@ -patches reverted: --- mesa-24.0.2/.pc/.quilt_series +++ mesa-24.0.2.orig/.pc/.quilt_series @@ -1 +0,0 @@ -series reverted: --- mesa-24.0.2/.pc/.version +++ mesa-24.0.2.orig/.pc/.version @@ -1 +0,0 @@ -2 reverted: --- mesa-24.0.2/.pc/applied-patches +++ mesa-24.0.2.orig/.pc/applied-patches @@ -1 +0,0 @@ -time64.diff reverted: --- mesa-24.0.2/.pc/time64.diff/src/drm-shim/drm_shim.c +++ mesa-24.0.2.orig/.pc/time64.diff/src/drm-shim/drm_shim.c @@ -1,836 +0,0 @@ -/* - * Copyright © 2018 Broadcom - * - * Permission is hereby granted, free of charge, to any person obtaining a - * copy of this software and associated documentation files (the "Software"), - * to deal in the Software without restriction, including without limitation - * the rights to use, copy, modify, merge, publish, distribute, sublicense, - * and/or sell copies of the Software, and to permit persons to whom the - * Software is furnished to do so, subject to the following conditions: - * - * The above copyright notice and this permission notice (including the next - * paragraph) shall be included in all copies or substantial portions of the - * Software. - * - * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR - * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, - * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL - * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER - * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING - * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER - * DEALINGS IN THE SOFTWARE. - */ - -/** - * @file - * - * Implements wrappers of libc functions to fake having a DRM device that - * isn't actually present in the kernel. - */ - -/* Prevent glibc from defining open64 when we want to alias it. */ -#undef _FILE_OFFSET_BITS -#define _LARGEFILE64_SOURCE - -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include - -#include "util/anon_file.h" -#include "util/set.h" -#include "util/simple_mtx.h" -#include "util/u_debug.h" -#include "drm_shim.h" - -#define REAL_FUNCTION_POINTER(x) __typeof__(x) *real_##x - -static simple_mtx_t shim_lock = SIMPLE_MTX_INITIALIZER; -struct set *opendir_set; -bool drm_shim_debug; - -/* If /dev/dri doesn't exist, we'll need an arbitrary pointer that wouldn't be - * returned by any other opendir() call so we can return just our fake node. - */ -DIR *fake_dev_dri = (void *)_set; - -REAL_FUNCTION_POINTER(close); -REAL_FUNCTION_POINTER(closedir); -REAL_FUNCTION_POINTER(dup); -REAL_FUNCTION_POINTER(fcntl); -REAL_FUNCTION_POINTER(fopen); -REAL_FUNCTION_POINTER(ioctl); -REAL_FUNCTION_POINTER(mmap); -REAL_FUNCTION_POINTER(mmap64); -REAL_FUNCTION_POINTER(open); -REAL_FUNCTION_POINTER(opendir); -REAL_FUNCTION_POINTER(readdir); -REAL_FUNCTION_POINTER(readdir64); -REAL_FUNCTION_POINTER(readlink); -REAL_FUNCTION_POINTER(realpath); - -#define HAS_XSTAT __GLIBC__ == 2 && __GLIBC_MINOR__ < 33 - -#if HAS_XSTAT -REAL_FUNCTION_POINTER(__xstat); -REAL_FUNCTION_POINTER(__xstat64); -REAL_FUNCTION_POINTER(__fxstat); -REAL_FUNCTION_POINTER(__fxstat64); -#else -REAL_FUNCTION_POINTER(stat); -REAL_FUNCTION_POINTER(stat64); -REAL_FUNCTION_POINTER(fstat); -REAL_FUNCTION_POINTER(fstat64); -#endif - -static char render_node_dir[] = "/dev/dri/"; -/* Full path of /dev/dri/renderD* */ -static char *render_node_path; -/* renderD* */ -static char *render_node_dirent_name; -/* /sys/dev/char/major: */ -static int drm_device_path_len; -static char *drm_device_path; -/* /sys/dev/char/major:minor/device */ -static int device_path_len; -static char *device_path; -/* /sys/dev/char/major:minor/device/subsystem */ -static char
Bug#1064123: marked as done (libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard)
Your message dated Fri, 15 Mar 2024 11:57:55 + with message-id and subject line Bug#1064123: fixed in mesa 24.0.3-1 has caused the Debian Bug report #1064123, regarding libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgl1-mesa-dri Version: 24.0.1-1 Severity: important Dear Maintainer, after the latest upgrade it's impossible for me to run a display manager or startx any window manager; after at most a few seconds / keypresses / mouse movements the screen freezes, completely unresponsive to anything other than the power button; the log below suggests a null pointer. Running "sleep 30; killall -u lorenzo" as root before startx returns me to a tty. Reverting to the previous version everything works. I'm running this on a debian derivative, devuan; afaik it shouldn't make a difference, as the package is unmodified from debian - I don't know how to verify that other than by installing debian in some partition, can one start some window manager from a debian chroot/whatever? If it's ok in debian or you need any more info please do let me know. -- Package-specific info: glxinfo: DISPLAY is not set. /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] [1002:6611] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.6.15-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-13) 13.2.0, GNU ld (GNU Binutils for Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) Xorg X server log files on system: -- -rw-r--r-- 1 lorenzo lorenzo 48300 Sep 19 15:56 /home/lorenzo/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 rootroot39672 Feb 16 20:09 /var/log/Xorg.0.log -rw-r--r-- 1 lorenzo lorenzo 45226 Feb 17 12:58 /home/lorenzo/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/lorenzo/.local/share/xorg/Xorg.0.log): [ 2392.994] X.Org X Server 1.21.1.10 X Protocol Version 11, Revision 0 [ 2392.996] Current Operating System: Linux dudu 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) x86_64 [ 2392.996] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6.15-amd64 root=/dev/mapper/dev1-root ro quiet [ 2392.997] xorg-server 2:21.1.10-1devuan1 (https://www.devuan.org/os/community) [ 2392.998] Current version of pixman: 0.42.2 [ 2392.999] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2392.999] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2393.002] (==) Log file: "/home/lorenzo/.local/share/xorg/Xorg.0.log", Time: Sat Feb 17 12:58:09 2024 [ 2393.003] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2393.003] (==) No Layout section. Using the first Screen section. [ 2393.003] (==) No screen section available. Using defaults. [ 2393.003] (**) |-->Screen "Default Screen Section" (0) [ 2393.003] (**) | |-->Monitor "" [ 2393.003] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 2393.003] (==) Automatically adding devices [ 2393.003] (==) Automatically enabling devices [ 2393.003] (==) Automatically adding GPU devices [ 2393.003] (==) Automatically binding GPU devices [ 2393.003] (==) Max clients allowed: 256, resource mask: 0x1f [ 2393.003] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 2393.003] Entry deleted from font path. [ 2393.003] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 2393.003] Entry deleted from font path. [ 2393.003] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 2393.003] Entry deleted from font path. [ 2393.003] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 2393.003] Entry
Processed: Bug#1061752 marked as pending in python-django-tagging
Processing control commands: > tag -1 pending Bug #1061752 [src:python-django-tagging] python-django-tagging ftbfs with Python 3.12 as default Added tag(s) pending. -- 1061752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
