Bug#974486: marked as done (gramofile: autopkgtest must be marked superficial)
Your message dated Sat, 27 Apr 2024 08:38:24 + with message-id and subject line Bug#974486: fixed in gramofile 1.6-13 has caused the Debian Bug report #974486, regarding gramofile: autopkgtest must be marked superficial 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.) -- 974486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gramofile X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in gramofile is running a trivial command that does not provide significant test coverage: - xvfb-run -a gramofile & Executing that command is considered to be a trivial test, which does not provide significant coverage for a package as a whole. But these tests are a useful way to detect regressions in dependencies and prevent them from breaking your package. However, it is important that we are realistic about the level of test coverage provided by these commands: most regressions cannot be detected in this way. So it is not appropriate for packages with only superficial tests to have the reduced migration time to migrate from unstable to testing as that means less opportunity for testing by users compared to the package with no tests. To support this, the keyword "Restrictions: superficial" has been defined [1]. Packages where all tests are marked with this keyword are not considered for the reduced migration age from unstable to testing, and will not be allowed to migrate automatically in later stages of the freeze [2]. Its always better to have more extensive testing than having superficial testing, which again is better than having no test. Please consider i) Adding a non-trivial test, and/or ii) Mark the trivial test with "Restrictions: superficial", similar to [3] or [4]. The Release Team has listed this issue in the list of Release Critical Issues for bullseye [5] and has mentioned that the test must be marked superficial if it is not testing one of its own installed binary packages in some way. As a result, the severity of this bug report might be increased to serious in future. [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions [2] https://release.debian.org/bullseye/freeze_policy.html [3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468 [4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3 [5] https://release.debian.org/bullseye/rc_policy.txt -- Regards Sudip --- End Message --- --- Begin Message --- Source: gramofile Source-Version: 1.6-13 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of gramofile, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated gramofile 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: Sat, 27 Apr 2024 09:55:01 +0200 Source: gramofile Architecture: source Version: 1.6-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 974486 1066587 Changes: gramofile (1.6-13) unstable; urgency=medium . * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066587) * Switch B-D to libncurses-dev. * Mark smoketest as superficial. (Closes: #974486) * Run smoketest in foreground. Checksums-Sha1: 6a4e262a74230b4897f92822430f78497e107cbd 1969 gramofile_1.6-13.dsc d8e026592c661d73cfe206a56e0d973ea79e6793 23912 gramofile_1.6-13.debian.tar.xz 835440f9ec81a6af3c8ef1745a3a844b976a0995 7067 gramofile_1.6-13_source.buildinfo Checksums-Sha256: 49c91f80de90b80c245b91375810a777a25aea6f0b5b70a4039a83ff7cf38a11 1969 gramofile_1.6-13.dsc 618f8430beb7831f1e1683a669dbb4a091656b4867dd780a4ffd2f54def98ffd 23912 gramofile_1.6-13.debian.tar.xz a5e2de96fdc7b585f6adcb80276b04d9b53f58c11ce8623efadf25e6d9826691 7067 gramofile
Bug#1066587: marked as done (gramofile: FTBFS: gramofile.c:42:3: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])
Your message dated Sat, 27 Apr 2024 08:38:24 + with message-id and subject line Bug#1066587: fixed in gramofile 1.6-13 has caused the Debian Bug report #1066587, regarding gramofile: FTBFS: gramofile.c:42:3: error: implicit declaration of function ‘exit’ [-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.) -- 1066587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gramofile Version: 1.6-12 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 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -O2 -funroll-loops -DTURBO_MEDIAN -DTURBO_BUFFER -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o reclp_main.o reclp_main.c > gramofile.c: In function ‘finishmenu’: > gramofile.c:42:3: error: implicit declaration of function ‘exit’ > [-Werror=implicit-function-declaration] >42 | exit (0); > | ^~~~ > gramofile.c:17:1: note: include ‘’ or provide a declaration of > ‘exit’ >16 | #include > +++ |+#include >17 | #else > gramofile.c:42:3: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] >42 | exit (0); > | ^~~~ > gramofile.c:42:3: note: include ‘’ or provide a declaration of > ‘exit’ > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -O2 -funroll-loops -DTURBO_MEDIAN -DTURBO_BUFFER -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o scrollmenu.o scrollmenu.c > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -O2 -funroll-loops -DTURBO_MEDIAN -DTURBO_BUFFER -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o stringinput.o stringinput.c > cc1: some warnings being treated as errors > make[1]: *** [: gramofile.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/gramofile_1.6-12_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: gramofile Source-Version: 1.6-13 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of gramofile, 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 Beckmann (supplier of updated gramofile 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: Sat, 27 Apr 2024 09:55:01 +0200 Source: gramofile Architecture: source Version: 1.6-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 974486 106
Processed: bullseye-pu: package cpu/1.4.3-14~deb11u1
Processing control commands:
> block 1067439 with -1
Bug #1067439 {Done: Andreas Beckmann } [cpu] cpu: undefined
symbol globalLdap in libcpu_ldap.so on Debian 12
1067439 was not blocked by any bugs.
1067439 was not blocking any bugs.
Added blocking bug(s) of 1067439: 1069880
> affects -1 + src:cpu
Bug #1069880 [release.debian.org] bullseye-pu: package cpu/1.4.3-14~deb11u1
Added indication that 1069880 affects src:cpu
--
1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439
1069880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:singleapplication
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:singleapplication > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1050520 (http://bugs.debian.org/1050520) > # Bug title: singleapplication: Non-dfsg-free license in future v3.4.0 version > # * https://github.com/itay-grudev/SingleApplication/issues/171 > # * remote status changed: open -> closed > # * closed upstream > tags 1050520 + fixed-upstream Bug #1050520 [src:singleapplication] singleapplication: Non-dfsg-free license in future v3.4.0 version Added tag(s) fixed-upstream. > usertags 1050520 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1050520 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:gpac
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gpac > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1060696 (http://bugs.debian.org/1060696) > # Bug title: gpac: CVE-2023-50120 > # * https://github.com/gpac/gpac/issues/2698 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1060696 + fixed-upstream Bug #1060696 [src:gpac] gpac: CVE-2023-50120 Added tag(s) fixed-upstream. > usertags 1060696 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #1065861 (http://bugs.debian.org/1065861) > # Bug title: gpac: CVE-2024-22749 > # * https://github.com/gpac/gpac/issues/2713 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1065861 + fixed-upstream Bug #1065861 [src:gpac] gpac: CVE-2024-22749 Added tag(s) fixed-upstream. > usertags 1065861 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060696 1065861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020806: marked as done (perl-byacc: reproducible-builds: differing buildid in in /usr/bin/pbyacc)
Your message dated Thu, 25 Apr 2024 15:02:58 +0200 with message-id and subject line [Debian FTP Masters] Accepted perl-byacc 2.0-9 (source) into unstable has caused the Debian Bug report #1020806, regarding perl-byacc: reproducible-builds: differing buildid in in /usr/bin/pbyacc 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.) -- 1020806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl-byacc Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The buildid differs in /usr/bin/pbyacc when built with a different build path: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/perl-byacc.html The attached patch fixes this in the upstream Makefile by adding -ffile-prefix-map to CFLAGS. According to my local tests, with this patch applied perl-byacc should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining perl-byacc! live well, vagrant From 1002dd61fdf333b0266ce59cd3053e6812905727 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 26 Sep 2022 23:55:37 + Subject: [PATCH] Makefile: Add -ffile-prefix-map to CFLAGS to avoid embedding build path. https://reproducible-builds.org/docs/build-path/ --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 077e9ea..1dd3c07 100644 --- a/Makefile +++ b/Makefile @@ -26,7 +26,7 @@ SIG_TYPE = void CPPFLAGS = $(RINDEX) -DPROGRAM=\"$(PROGRAM)\" -DSIG_TYPE=$(SIG_TYPE) -CFLAGS = -O2 -g $(CPPFLAGS) +CFLAGS = -O2 -g -ffile-prefix-map=$(CURDIR)=. $(CPPFLAGS) CC = gcc -Wall CPP = /lib/cpp -- 2.37.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 2.0-9 I forgot to close this bug in d/changelog. Start of forwarded message From: Debian FTP Masters To: debian-devel-chan...@lists.debian.org Subject: Accepted perl-byacc 2.0-9 (source) into unstable Date: Thu, 25 Apr 2024 09:06:37 + -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Apr 2024 19:14:14 +0200 Source: perl-byacc Architecture: source Version: 2.0-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Changes: perl-byacc (2.0-9) unstable; urgency=medium . * QA upload. . * Updated vcs in d/control to Salsa. * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.8 to 4.7.0. * Moved to debhelper compat level 13 and enabled hardening and reproducible build. Checksums-Sha1: a34413b43fad9194c8badca1aa6865d11b403937 1792 perl-byacc_2.0-9.dsc 9312e49e3929820c3e41d651563da242d7259530 84540 perl-byacc_2.0.orig.tar.gz 23cef06d2409b67d0e5f9f15ca12eb7b5a3cc0e4 13912 perl-byacc_2.0-9.debian.tar.xz 003b3378b4b3b2b54afb70da58855f45dc995756 6361 perl-byacc_2.0-9_source.buildinfo Checksums-Sha256: 467e253c37476f5002ca7cd59ad4beba140acfbb4894b44ae6893a0be4f570c7 1792 perl-byacc_2.0-9.dsc ce370945ca19299bb65c8223d8e7370f3edfe5e32322d21fb41d19325a72cbef 84540 perl-byacc_2.0.orig.tar.gz ca3f5f9d599e4ca3d1e7a0ebc48a6efe806d9b52a77942d69da17b29b2414d8d 13912 perl-byacc_2.0-9.debian.tar.xz d4504424b32fc7f4a4f492faa7e8725c37b603ee6d0099e86d6d3cecaded6362 6361 perl-byacc_2.0-9_source.buildinfo Files: bff7bb9d01bc8f17e92e62c152b6acd8 1792 devel optional perl-byacc_2.0-9.dsc 4c206de09d6af335e9376f78659ed4f2 84540 devel optional perl-byacc_2.0.orig.tar.gz 37f52ef24a92af5ec8be16467c76 13912 devel optional perl-byacc_2.0-9.debian.tar.xz f9dd1c403088e7e01579f33bc8affdcd 6361 devel optional perl-byacc_2.0-9_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYqGAUACgkQgSgKoIe6 +w5rGA//Z0b9vdPG+ou4AO+4p0Vv377EcMyY61L+F+SvuxloP4AY++6KYEKqv3Y7 XQvrtW55NChsCObYfU+tPrf1nKIrM4cVYNci5JJQhjK9V4Aw6a8izS26sv0T80sh kQhLzFNMT4zoc+PmLSTHEetMIRfPylBsn6KvO0UTwCt44Jpex8qTGWDOt04tQa4b QxYfH3idg9JvA5DaCL3x39YzAR/j20iknfIDcy/Gb3oOG2xu90QKCSSnaNUhdTQR yuV8oy/HZtb3QFXHCnRe8BBMGpQ0J0C3lM9IwHGrUdKnuaBj+IASGcIu3J3HbM9U Ekf101eHmo9hi30rCAch6Qt+2cgWyazCjXevbryo23mqSFqpwiJQT2Fk4jifrVMH IXg+uKyWE9JeOn3cueezHZDE5pNgozwPRe+/YtNkZA3SwlH/d9gP/0BWijmITJRP 91oUWHy0TYHuS4cYHzTBUCqil3Ep/euVFko7rZf5iEFM6IPJoywhz7GChFgwZS7W rnWmnvIXc0f7wE7XKnaqCUWcNcqg9WBdCj9ZN8ImZuovJ6blYytAb9XG/pBZ5lSf tllC7gykGKtObjlkOBQW9HuvHW09ExDMJI3BEQUd6m7R
Processed: Re: [Mayhem] Bug report on perl-byacc: pbyacc crashes with exit status 139
Processing control commands: > tags -1 + patch Bug #716290 [perl-byacc] [Mayhem] Bug report on perl-byacc: pbyacc crashes with exit status 139 Added tag(s) patch. -- 716290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036334: marked as done (bugz.1: Missing SEE ALSO)
Your message dated Wed, 24 Apr 2024 18:04:15 + with message-id and subject line Bug#1036334: fixed in bugz 0.14-1 has caused the Debian Bug report #1036334, regarding bugz.1: Missing SEE ALSO 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.) -- 1036334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bugz Version: 0.13-3 Severity: normal Tags: upstream X-Debbugs-Cc: Alastair Tse , Markus Meier , Dylan Baker , William Hubbs , a...@kernel.org Hi! The manual page doesn't have a SEE ALSO section, so it's hard to find the documentation for the config file. I see that the master branch has this issue fixed, but there hasn't been a release since then (2017). Is the upstream project still maintained? Cheers, Alex -- System Information: Debian Release: 12.0 merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages bugz depends on: ii python3 3.11.2-1+b1 bugz recommends no packages. bugz suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: bugz Source-Version: 0.14-1 Done: Akash Doppalapudi We believe that the bug you reported is fixed in the latest version of bugz, 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 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Akash Doppalapudi (supplier of updated bugz 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, 23 Apr 2024 14:01:23 + Source: bugz Architecture: source Version: 0.14-1 Distribution: unstable Urgency: medium Maintainer: Akash Doppalapudi Changed-By: Akash Doppalapudi Closes: 900234 1036334 Changes: bugz (0.14-1) unstable; urgency=medium . * New upstream version 0.14 (Closes: #1036334) * New Maintainer (Closes: #900234) * d/control: - Update Maintainer name - Bump Standards-Version to 4.7.0 - Add new Build-Depends 'flit' & 'pybuild-plugin-pyproject' as build backend - Remove dh-exec from Build-Depends as it's not needed anymore * d/copyright: - Change 'man/*' to 'data/share/man/*' copyright stanza as per upstream - Update packaging copyright information - Update Upstream-Contact with upstream maintainer's details * Remove d/install since it's not needed anymore Checksums-Sha1: 59a8dfc382312d29c562a6903298a1848b61473b 1729 bugz_0.14-1.dsc ac0bd8ab255ce7eb81fa599654b7106080c722fd 26589 bugz_0.14.orig.tar.gz b5b68e2b545b248c27cbea57ff07acf3254249ce 4464 bugz_0.14-1.debian.tar.xz 0390af1230148b3cd4bff18d6e3c3dc9e727a7e6 6685 bugz_0.14-1_source.buildinfo Checksums-Sha256: d13b2541de31acc34905d51bed0ef8002bb41b2ace01249f0a826d112a835605 1729 bugz_0.14-1.dsc 351556c68c17a88a27e98629dc74d9cd1a6c2eae49ed05e1a69da1db93efe266 26589 bugz_0.14.orig.tar.gz 3b72a89809a1372e37b475570334f6f070fb70d9af166ed11593dcd46535e060 4464 bugz_0.14-1.debian.tar.xz 1b34d96e5c812ea86346a8c2efa38d08d54d8422afcbdd7c47e2db38a5f164c7 6685 bugz_0.14-1_source.buildinfo Files: 635056c85c88e819181017c54945da0c 1729 misc optional bugz_0.14-1.dsc 996cfdc6673a211c384ceafa77c20fbd 26589 misc optional bugz_0.14.orig.tar.gz 9e25990c4084760367e49f49574e5b93 4464 misc optional bugz_0.14-1.debian.tar.xz 44b19bcb85cc048eb69034ffb4371938 6685 misc optional bugz_0.14-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYpRXcQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFK/IC/9mgjzB9dqJjTGOmkZutbad2o8hWc3YvaWf ZvfdvH4KvTiKPog2StU4l8hsJIJCInpiOR8A5PiENFXQ+1L52H8Kg82y0dcpLSvD tBlLRSMdjC6vmo6vR5FYPu4pHmIj+iGswGebK9KZDSJn9qvA8x6ta78RQ9vSh2Of t5ULyOUstoKmRFCnQ9CsfrGji4zhBpQANrSYBzejoCBId5fPs+djL+VRVR2x8/Cw dIRa1xfrl3OpP7GlyZOV8+hubTlIo/WyfaR9PrvbOz8B0eUP1jyuo3X7YwcskeET HaInnkP6KyvNJgfPAu+SnJkBWFI9qyaHAYBrb2NztuUSe4J2M+dnyQS6AjbH6U4N KrCOgn2RKH5nnnNDOpvz5bXSOiJaqBp+eYbtc1jNpMVcASqMuR0e3XduCMOa
Bug#1025655: marked as done (hovercraft: requires python3-setuptools)
Your message dated Wed, 24 Apr 2024 18:02:34 +
with message-id
and subject line Bug#1025655: fixed in hovercraft 2.7-2+deb11u1
has caused the Debian Bug report #1025655,
regarding hovercraft: requires python3-setuptools
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.)
--
1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hovercraft
Version: 2.7-2
Severity: important
X-Debbugs-Cc: bms.deb...@barwap.com
Dear Maintainer,
fresh install, running hovercraft
$ hovercraft planning_presentation.rst html
Traceback (most recent call last):
File "/usr/bin/hovercraft", line 33, in
sys.exit(load_entry_point('hovercraft==2.7', 'console_scripts',
'console_script')())
File "/usr/bin/hovercraft", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/share/hovercraft/hovercraft/__init__.py", line 6, in
import pkg_resources
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3243,
in
def _initialize_master_working_set():
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3226,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3255,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools' distribution was not found
and is required by hovercraft
* What outcome did you expect instead?
$ hovercraft planning_presentation.rst html
(No errors - what did happen after apt-get install python3-setuptools)
-- System Information:
Debian Release: 11.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-19-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages hovercraft depends on:
ii libjs-impress 1.0.0-1
ii libjs-sphinxdoc3.4.3-2
ii python33.9.2-3
ii python3-docutils 0.16+dfsg-4
ii python3-lxml 4.6.3+dfsg-0.1+deb11u1
ii python3-pkg-resources 52.0.0-4
ii python3-pygments 2.7.1+dfsg-2.1
ii python3-svg.path 3.0-2
ii python3-watchdog 1.0.2-2
hovercraft recommends no packages.
hovercraft suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hovercraft
Source-Version: 2.7-2+deb11u1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
hovercraft, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated hovercraft 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: Wed, 24 Apr 2024 06:11:30 +0200
Source: hovercraf
Bug#264500: marked as done (fmtools: fmscan patch to allow choice of threshold signal strength (attached))
Your message dated Wed, 24 Apr 2024 09:17:43 +0200
with message-id
and subject line Re: fmtools: fmscan patch to allow choice of threshold signal
strength (attached)
has caused the Debian Bug report #264500,
regarding fmtools: fmscan patch to allow choice of threshold signal strength
(attached)
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.)
--
264500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fmtools
Version: 0.99.1-1
Severity: normal
The fmscan utility is not nearly as useful as it could be without
this patch. this adds the -t command line option to allow control of
the threshold signal strength that fmscan uses to decide if a station
can be received. please apply to future debian packages of this tool
and submit to the upstream maintainer.
thanks & enjoy,
Greg
Only in fmtools-0.99.1: build-stamp
Only in fmtools-0.99.1/debian: files
Only in fmtools-0.99.1/debian: fmtools
Only in fmtools-0.99.1/debian: fmtools.substvars
Only in fmtools-0.99.1: fm
Only in fmtools-0.99.1: fmscan
diff -ru orig/fmtools-0.99.1/fmscan.1 fmtools-0.99.1/fmscan.1
--- orig/fmtools-0.99.1/fmscan.12003-12-06 20:47:36.0 -0800
+++ fmtools-0.99.1/fmscan.1 2004-08-08 22:41:56.0 -0700
@@ -44,6 +44,9 @@
.TP
\fB\-i \fIfreq
Increment between scanned channels, in MHz. Default: 0.2.
+.TP
+\fB\-t \fIpercent
+Signal strength threshold to consider a channel. Default: 50%.
.SH BUGS
This program may not do much if your radio card's driver doesn't support
fine tuning in 1/16000 MHz offsets. By default, v4l assumes 1/16 MHz
diff -ru orig/fmtools-0.99.1/fmscan.c fmtools-0.99.1/fmscan.c
--- orig/fmtools-0.99.1/fmscan.c2003-12-06 22:40:25.0 -0800
+++ fmtools-0.99.1/fmscan.c 2004-08-08 22:44:48.0 -0700
@@ -37,7 +37,7 @@
void help(char *prog)
{
printf("fmtools fmscan version %s\n\n", FMT_VERSION);
- printf("usage: %s [-h] [-d ] [-s ] [-e ] [-i
]\n\n", prog);
+ printf("usage: %s [-h] [-d ] [-s ] [-e ] [-i ]
[-t <%%>]\n\n", prog);
printf("Auxiliary program to scan a frequency band for radio
stations.\n\n");
@@ -46,6 +46,7 @@
printf(" -s - set start of scanning range to \n");
printf(" -e - set end of scanning range to \n");
printf(" -i - set increment value between channels to
\n");
+ printf(" -t <%%>- set signal strength percentage to lock onto
<%%>\n");
printf(" - a value in the format nnn.nn (MHz)\n");
exit(0);
@@ -55,7 +56,7 @@
{
int fd, ret, i, tries = TRIES;
struct video_tuner vt;
- float perc, begval, incval, endval;
+ float perc, begval, incval, endval, threshold;
longlowf, highf, freq, totsig, incr, fact;
char*progname, *dev = NULL;
@@ -66,7 +67,9 @@
incval = 0.20; /* increment 0.2 MHz */
endval = 107.9; /* stop at 107.9 MHz */
- while ((i = getopt(argc, argv, "+e:hi:s:d:")) != EOF) {
+threshold = THRESHOLD;
+
+ while ((i = getopt(argc, argv, "+e:hi:s:d:t:")) != EOF) {
switch (i) {
case 'd':
dev = strdup(optarg);
@@ -80,6 +83,9 @@
case 's':
begval = atof(optarg);
break;
+case 't':
+threshold = atoi(optarg)/100.;
+break;
case 'h':
default:
help(progname);
@@ -152,7 +158,7 @@
perc = (totsig / (65535.0 * tries));
- if (perc > THRESHOLD)
+ if (perc > threshold)
printf("%2.1f: %3.1f%% \n",
(freq / (double) fact), perc * 100.0);
}
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: alpha
Kernel: Linux 2.4.23-rc5-grsec-nfs12
Locale: LANG=C, LC_CTYPE=C
Versions of packages fmtools depends on:
ii libc6.1 2.3.2.ds1-13 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.8
[Ben Pfaff]
> I incorporated
Processed: Re: fmtools: fmscan patch to allow choice of threshold signal strength (attached)
Processing control commands: > tags -1 + patch Bug #264500 [fmtools] fmtools: fmscan patch to allow choice of threshold signal strength (attached) Added tag(s) patch. -- 264500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934046: marked as done (mrename: Homepage field arrives to Linkedin)
Your message dated Mon, 22 Apr 2024 06:49:32 + with message-id and subject line Bug#934046: fixed in mrename 1.2-17 has caused the Debian Bug report #934046, regarding mrename: Homepage field arrives to Linkedin 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.) -- 934046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mrename Version: 1.2-14 Severity: normal The Homepage field points to http://alfalinux.sourceforge.net/mrename.php3. This URL redirects to a Linkedin personal page. Eriberto --- End Message --- --- Begin Message --- Source: mrename Source-Version: 1.2-17 Done: David da Silva Polverari We believe that the bug you reported is fixed in the latest version of mrename, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David da Silva Polverari (supplier of updated mrename 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: Mon, 22 Apr 2024 06:32:43 + Source: mrename Architecture: source Version: 1.2-17 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: David da Silva Polverari Closes: 934046 Changes: mrename (1.2-17) unstable; urgency=medium . * QA upload. * debian/control: - Bumped Standards-Version to 4.7.0. - Flagged mrename as 'Multi-Arch: foreign'. - Pointed Homepage field to Internet Archive snapshot. (Closes: #934046) * debian/copyright: update packaging copyright information. * debian/gbp.conf: created to make git repository compliant with DEP-14 layout recommendations and enforce the use of pristine-tar. * debian/salsa-ci.yml: created to provide CI tests for Salsa. * debian/upstream/metadata: created. Checksums-Sha1: b3386b369b280b19801f6fc6a88b41d3166eb56d 1856 mrename_1.2-17.dsc 5df86a9684e3d1faf540f2c6e897dfe5008a3e2c 5484 mrename_1.2-17.debian.tar.xz 47fb6a41921250e1be19ac6aa15d1f17bd4ed0f4 5528 mrename_1.2-17_source.buildinfo Checksums-Sha256: 17c12573ddc055ec99204fad1e2ff8843499ae0f42a82f56a9ee4a22beb88735 1856 mrename_1.2-17.dsc a52305ae0a43dad48ca75bde061ced382d30f38e302377e54dd2195efee1bc2a 5484 mrename_1.2-17.debian.tar.xz e2ce67aed940cdaec205d8c88554545a79b812b1e8ae88d5a259e23ac9c8146a 5528 mrename_1.2-17_source.buildinfo Files: 330314e166db332c75efaf4a41bf6865 1856 utils optional mrename_1.2-17.dsc c5fffcfbac8e1a2187fe37e10fe62e84 5484 utils optional mrename_1.2-17.debian.tar.xz f0a53e52e96eaf385670e95bfccd72c1 5528 utils optional mrename_1.2-17_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEDTUunGhzKyZWj9leHIjoaIRpgN4FAmYmBUcACgkQHIjoaIRp gN53exAAyMXYwfXV0iIwPwa2piN5r3JhTeC+uZdmbCF4Ol+snPh80Qhc2l4qD+uR DIwhRcPoRIHpXh1GIaOAQAMH3DNmQ9GfuiCo7/Jkb3xolmZlAEPYbEUYgZs+Vh/T AEBjrmUjknqs8/fN2nhw9DkPxJ9/QPn5yUB6SGa00ApuWBA56gI9C8JGpviQqAwm WxQeV1jLiut/o6Fi0BjSLlRG54EASBQVtwKNfBKLhSB7/lWjhY1QOdKwpubXHaq+ HKkcD+Z2loOFYFOdOjGsneN36WtBgCA8hvuD/jZ3RssNSOIcp9AExjbhjmhrjhJ7 fy4iTe0OlBgbh8B9YpgqErsmWg3Ut+V4i8vZOVz6i67UQ2wM68Sx/evdUjnEeUU6 qAKvTtGq9NIAXwEeBa4v4bb5SHgEdK7wJ6Avk77FoVChSywTKYIgbDR6xFhc+SJD ConME6sRi2l05AocBewCvhzd0BU5V8XC2l/WVppsU/uu6wwx94TmPySZ4+Ykj3A7 a5aNGWKY5+zWC4LZQkX+9/8Fofi7wJXxc2fmz45ALbqcHYFviRwCXzxrMwLSluEN 6oHxS+PCy/VlYhKj9hcNsRAQ8msd6dnKf8UpLjafJ2Y9KVM/5+s/TEbV0IrPVdDL OLf60v7WvW7ycwfg5Fu3PRyxEswwLL5B+exDktUxDbHb7pOKJJc= =m9Wo -END PGP SIGNATURE- pgpdZizbNW8Mz.pgp Description: PGP signature --- End Message ---
Bug#1066601: marked as done (gnunet-gtk: FTBFS: plugin_gtk_namestore_tlsa.c:617:12: error: implicit declaration of function ‘memmem’; did you mean ‘memset’? [-Werror=implicit-function-declaration])
Your message dated Mon, 22 Apr 2024 00:50:21 + with message-id and subject line Bug#1066601: fixed in gnunet-gtk 0.20.0-4 has caused the Debian Bug report #1066601, regarding gnunet-gtk: FTBFS: plugin_gtk_namestore_tlsa.c:617:12: error: implicit declaration of function ‘memmem’; did you mean ‘memset’? [-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.) -- 1066601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnunet-gtk Version: 0.20.0-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): > /bin/bash ../../libtool --tag=CC --mode=link gcc -I/usr/include/gtk-3.0 > -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/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread > -I/usr/include/libgladeui-2.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 > -I/usr/include/pango-1.0 -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/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -fno-strict-aliasing > -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -I/usr/include/gtk-3.0 -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/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -export-dynamic > -avoid-version -module -no-undefined -Wl,-z,relro -o > libgnunet_plugin_gtk_namestore_a.la -rpath /usr/lib/x86_64-linux-gnu/gnunet > libgnunet_plugin_gtk_namestore_a_la-plugin_gtk_namestore_a.lo -lgnunetutil > -lgnunetutil -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz > -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 > -lglib-2.0 > plugin_gtk_namestore_tlsa.c: In function ‘import_x509_certificate’: > plugin_gtk_namestore_tlsa.c:617:12: error: implicit declaration of function > ‘memmem’; did you mean ‘memset’? [-Werror=implicit-function-declaration] > 617 | cn = memmem (str.data, str.size, ",CN=", 4); > |^~ > |memset > plugin_gtk_namestore_tlsa.c:617:10: warning: assignment to ‘const char *’ > from ‘int’ makes pointer from integer without a cast [-Wint-conversion] > 617 | cn = memmem (str.data, str.size, ",CN=", 4); > | ^ > /bin/bash ../../libtool --tag=CC --mode=link gcc -I/usr/include/gtk-3.0 > -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/h
Bug#1044290: marked as done (dmucs: Fails to build source after successful build)
Your message dated Mon, 22 Apr 2024 00:49:21 + with message-id and subject line Bug#1044290: fixed in dmucs 0.6.1+dfsg-1 has caused the Debian Bug report #1044290, regarding dmucs: Fails to build source after successful build 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.) -- 1044290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dmucs Version: 0.6.1-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package dmucs > dpkg-buildpackage: info: source version 0.6.1-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by David da Silva Polverari > > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_auto_clean > dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > make -j1 distclean > make[1]: Entering directory '/<>' > Making distclean in COSMIC > make[2]: Entering directory '/<>/COSMIC' > (cd EXE; make clean ) > make[3]: Entering directory '/<>/COSMIC/EXE' > /bin/rm -f *.o *.bak *.err Spm sktdbg spmchk spmtable srmsrvr > make[3]: Leaving directory '/<>/COSMIC/EXE' > (cd EXAMPLES ; make clean ) > make[3]: Entering directory '/<>/COSMIC/EXAMPLES' > /bin/rm -f *.o *.bak *.err smsrvr smclient multiskt sktpoll talksrvr > talkclient sktsig oobrecv oobsend > make[3]: Leaving directory '/<>/COSMIC/EXAMPLES' > All object files, the simpleskts library, and executables are now gone > make[2]: Leaving directory '/<>/COSMIC' > Making distclean in . > make[2]: Entering directory '/<>' > test -z "gethost loadavg monitor remhost" || rm -f gethost loadavg monitor > remhost > test -z "dmucs" || rm -f dmucs > rm -f *.o > rm -f *.tab.c > rm -f > rm -f config.h stamp-h1 > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > make[2]: Leaving directory '/<>' > rm -f config.status config.cache config.log configure.lineno > configure.status.lineno > rm -rf ./.deps > rm -f Makefile > make[1]: Leaving directory '/<>' >debian/rules override_dh_clean > make[1]: Entering directory '/<>' > dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in > use) > rm -f addhost config.log > make[1]: Leaving directory '/<>' > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building dmucs using existing ./dmucs_0.6.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory autom4te.cache > dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/output.1, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.1, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use > --include-removal to override > dpkg-source: error: cannot represent change to test: binary file contents > changed > dpkg-source: error: add test in debian/source/inclu
Bug#1069481: marked as done (freecdb: FTBFS on armhf: dh_auto_test: error: make -j4 check returned exit code 2)
Your message dated Mon, 22 Apr 2024 00:19:14 + with message-id and subject line Bug#1069481: fixed in freecdb 0.77 has caused the Debian Bug report #1069481, regarding freecdb: FTBFS on armhf: dh_auto_test: error: make -j4 check 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.) -- 1069481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freecdb Version: 0.76 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./check-local cdbmake cdbdump cdbget cdbstats > Checking cdbmake... > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create loop: symbolic link loop > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake: fatal: unable to create tmp: invalid argument > 111 > cdbmake failed. > make[1]: *** [Makefile:25: check] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 check returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/04/20/freecdb_0.76_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: freecdb Source-Version: 0.77 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of freecdb, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated freecdb 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: Mon, 22 Apr 2024 01:55:29 +0200 Source: freecdb Architecture: source Version: 0.77 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1011493 1069481 Changes: freecdb (0.77) unstable; urgency=medium . * QA upload. * Explicitly pass CFLAGS to the build. (Closes: #1011493, #1069481) * Fix building with -Werror=implicit-function-declaration. * Declare Rules-Requires-Root: no. Checksums-Sha1: 585b79d52820daba1389e4535a0160ec52eafec8 1531 freecdb_0.77.dsc ee987a46da1db0ba45cea13e0cd7362399309cb7 218108 freecdb_0.77.tar.xz b8f1b39c2725c21dfea4d333ab847059ce06dc55 5613 freecdb_0.77_source.buildinfo Checksums-Sha256: 26b7bea273740144f4b93be3bfa71d61c491a2438c5f557802f68bdaba7cfdfa 1531 freecdb_0.77.dsc 8a8805a521ccc49f54b28abd9ab4ff0ceebdc14267bc72b946ccf3efd35aed95 218108 freecdb_0.77.tar.xz 2ccc40d887ac4cb22b4db1f64bfd9f2edfc260248213d1d7bedb00cb31b4cb7a 5613 freecdb_0.77_source.buildinfo Files: d8f2435204bc3e531946b7c4c129429d 1531 utils optional freecdb_0.77.dsc 145be443c590812b2df3d7d3c6eb4b6c 218108 utils optional freecdb_0.77.tar.xz 6e8fd572ce43b2c469bb41d1d8d811a3 5613 utils optional freecdb_0.77_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYl
Bug#1011493: marked as done (freecdb: reproducible-builds: embedded build paths in various binaries)
Your message dated Mon, 22 Apr 2024 00:19:14 + with message-id and subject line Bug#1011493: fixed in freecdb 0.77 has caused the Debian Bug report #1011493, regarding freecdb: reproducible-builds: embedded build paths in various binaries 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.) -- 1011493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freecdb Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The build path is embedded in various binaries in /usr/bin: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/freecdb.html /usr/bin/cdbdump /build/1st/freecdb-0.76/cdbdump.c:45 vs. /build/2/freecdb-0.76/2nd/cdbdump.c:45 The attached patch fixes this by explicitly passing CFLAGS to a dh_auto_build override in debian/rules, which includes the -ffile-prefix-map argument used to avoid embedding build paths. With this patch applied, freecdb should build reproducibly on tests.reproducible-builds.org! live well, vagrant From 614861c71f34eea174ed917d3a03b23f771008f3 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 23 May 2022 22:28:57 + Subject: [PATCH] debian/rules: Explicitly pass CFLAGS to dh_auto_build. --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index 2d33f6a..ae015cc 100755 --- a/debian/rules +++ b/debian/rules @@ -2,3 +2,6 @@ %: dh $@ + +override_dh_auto_build: + dh_auto_build -- CFLAGS="$(CFLAGS)" -- 2.36.1 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: freecdb Source-Version: 0.77 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of freecdb, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated freecdb 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: Mon, 22 Apr 2024 01:55:29 +0200 Source: freecdb Architecture: source Version: 0.77 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1011493 1069481 Changes: freecdb (0.77) unstable; urgency=medium . * QA upload. * Explicitly pass CFLAGS to the build. (Closes: #1011493, #1069481) * Fix building with -Werror=implicit-function-declaration. * Declare Rules-Requires-Root: no. Checksums-Sha1: 585b79d52820daba1389e4535a0160ec52eafec8 1531 freecdb_0.77.dsc ee987a46da1db0ba45cea13e0cd7362399309cb7 218108 freecdb_0.77.tar.xz b8f1b39c2725c21dfea4d333ab847059ce06dc55 5613 freecdb_0.77_source.buildinfo Checksums-Sha256: 26b7bea273740144f4b93be3bfa71d61c491a2438c5f557802f68bdaba7cfdfa 1531 freecdb_0.77.dsc 8a8805a521ccc49f54b28abd9ab4ff0ceebdc14267bc72b946ccf3efd35aed95 218108 freecdb_0.77.tar.xz 2ccc40d887ac4cb22b4db1f64bfd9f2edfc260248213d1d7bedb00cb31b4cb7a 5613 freecdb_0.77_source.buildinfo Files: d8f2435204bc3e531946b7c4c129429d 1531 utils optional freecdb_0.77.dsc 145be443c590812b2df3d7d3c6eb4b6c 218108 utils optional freecdb_0.77.tar.xz 6e8fd572ce43b2c469bb41d1d8d811a3 5613 utils optional freecdb_0.77_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlqBIQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCK+oD/0QoBsB4d0XzP3hs+EkfW5bxLF53TE3htU5 2qSVB89Vzo5ZatDP1AKZJvZvrFbtQQRzx+dZWiywjYqNijwvAoXdbE7waZ/lvzla BMMuxr32dCV6XN6xBwIzTBT0YMI3VHSSUwXo+mSma09ZMUYV4AAUIiExZgF5zAeg cXPPfUxQidWaMyY5G3muDkYOrLGRh4+bDY+s4qgqJP2nuhlCUfWWBettIsODqjHE yl7H60+F1bul/f9PNwxXl7cwzY+GU39q+DV7Pz4KjdjHakZ/+QzzwZznQM5+g+CV +Nbi5ogMSy6yREDMdqco2Fb1GYh0AfuL3NZhbwr9+yi8Zvpz29DpE18MJDXIbtO1 hWDVVSjTRyFxVoqky/lrBr2RVUuZl3axHx1BUtaJyuJNgo/cAw/UUi7ktofQStd/ eLJK3bxlLZ8fvZTWfYOdZGZm6Y7vhhKsLcvrOZkije2P7a2EeJKSr2tZx095+QgK eYRVco8lxd8rJtk2tZASZhWfRIhQ8c6CHnZwd+zP+NUUY6xYpNIzwd957Zx0fw9A gN7JBkgjSq199iw1i9SGaO/96HEjnzlNmRqGN25vFYbUa5fudHVs69mNVb4JTVtY 8hFzcDos+7Ggm6ocVRSPCXmzV85
Bug#1024283: marked as done (ipsvd: reproducible-builds: buildid differences in various binaries)
Your message dated Sun, 21 Apr 2024 17:49:55 + with message-id and subject line Bug#1024283: fixed in ipsvd 1.0.0-6 has caused the Debian Bug report #1024283, regarding ipsvd: reproducible-builds: buildid differences in various binaries 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.) -- 1024283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipsvd Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The buildid differs when built from a different path for various binaries in /usr/bin: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/ipsvd.html The attached patch to debian/rules fixes this by adding -ffile-prefix-map to CFLAGS. Switching to dh and a recent debhelper compat level might also solve this problem. According to my local tests, with this patch applied, ipsvd should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining ipsvd! live well, vagrant From 7310c68df7db93c4b837e18e70cebfde1a60f9ae Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Wed, 16 Nov 2022 23:30:03 + Subject: [PATCH] debian/rules: Add -ffile-prefix-map to CFLAGS to avoid embedding build paths. https://reproducible-builds.org/docs/build-path/ --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index f3d69a5..97ec522 100755 --- a/debian/rules +++ b/debian/rules @@ -5,7 +5,7 @@ ifneq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) STRIP =: nostrip endif -CFLAGS =-g -O2 -Wall +CFLAGS =-g -O2 -Wall -ffile-prefix-map=$(CURDIR)=. LDFLAGS =-Os CC =gcc ifneq (,$(findstring diet,$(DEB_BUILD_OPTIONS))) -- 2.38.1 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ipsvd Source-Version: 1.0.0-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of ipsvd, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated ipsvd 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: Sun, 21 Apr 2024 19:32:53 +0200 Source: ipsvd Architecture: source Version: 1.0.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1024283 1069448 Changes: ipsvd (1.0.0-6) unstable; urgency=medium . * QA upload. * Re-import package history into GIT. * Make the build verbose. * Do not omit the hardening flags. (Closes: #1024283, #1069448) * Fix building with -Werror=implicit-function-declaration. Checksums-Sha1: 9d2c2fccbdde0538130c422ce455d88d0672de2a 1734 ipsvd_1.0.0-6.dsc bff9a3f77d92c787f8e79d36bc2907752827b4ff 6108 ipsvd_1.0.0-6.debian.tar.xz 91712c6e472ca9e91779dfa650c3d63bfe09e30f 4717 ipsvd_1.0.0-6_source.buildinfo Checksums-Sha256: f31abc6d7790260120fe69753ae709474920ef0c8ebd1881fbbfd9fc8d5a946b 1734 ipsvd_1.0.0-6.dsc d16f38bbaad1066ea29ed5b7ce8955f72104954e8bfddbdd8cc953b4eb6f3c2c 6108 ipsvd_1.0.0-6.debian.tar.xz 09de445abaa3efa1fa974bd82bd1bb0c2c777beb1fc3cbf3f080aadb7dbfaf82 4717 ipsvd_1.0.0-6_source.buildinfo Files: 2f924aadfea9d5e807fa4c17101ec56e 1734 net optional ipsvd_1.0.0-6.dsc 628f662a5c4b036407a1030fe0ac6810 6108 net optional ipsvd_1.0.0-6.debian.tar.xz eef4ffe496704e271b5b374ed2025477 4717 net optional ipsvd_1.0.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlTlMQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCNhnD/9TCIp3CNC6Yl5pyGdd3Ac3TpZJtFccaS1C Q/rSblhea7dNF/laiggtbD9zNtN+/saRUvn5U1XR/byXJPeiFh+9nfmxjv4FsMFL yRD0TVk5Su0N9iTB9HB2vZ4uUgTRDa4HHmlETctiOzDJa0XHKQnuGuiyLRdkvgvA AVuM9C9dxdQFbtZk8ONRyu6+/jxcY/bHoCfmx85jCPstcTpvk48xkm+76alhCgF+ 3cAPM1xtRwuq/p0NdeTOKMrF1Vlo9X5H0b+1QsFVa9exT8DZCqUlEDcYfXiJyH2w P17DqGNDfizfXGYKzDVCGRdkG/l165ghjGxEbRdxuaEuH2S/cTJnz0ax6GNIk97z MetjqXZiVxLUHscPvQgua0YLN0DhbrxNh8BausONuuO+xLSjTqGLyEq3YHOvkyiB
Bug#1069448: marked as done (ipsvd: FTBFS on armhf: make[1]: *** [Makefile:7: check] Error 1)
Your message dated Sun, 21 Apr 2024 17:49:55 + with message-id and subject line Bug#1069448: fixed in ipsvd 1.0.0-6 has caused the Debian Bug report #1069448, regarding ipsvd: FTBFS on armhf: make[1]: *** [Makefile:7: check] Error 1 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.) -- 1069448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipsvd Version: 1.0.0-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<>/ipsvd-1.0.0/compile' > ./compile check-tcpsvd.c > ./load check-tcpsvd unix.a byte.a `cat socket.lib` > ./compile check-udpsvd.c > ./load check-udpsvd unix.a byte.a `cat socket.lib` > ./compile check-ipsvd-cdb.c > ./load check-ipsvd-cdb uint32_unpack.o unix.a byte.a > ./check-local tcpsvd udpsvd ipsvd-cdb `grep -v nossl Checking tcpsvd... > Checking udpsvd... > Checking ipsvd-cdb... > usage: ipsvd-cdb cdb cdb.tmp dir > > 111 > ipsvd-cdb: fatal: unable to create: > /<>/ipsvd/compile/check-tmp.cdb.tmp: invalid argument > 111 > /<>/ipsvd/compile/ipsvd-cdb.check: 24: cannot open > /<>/ipsvd/compile/check-tmp.cdb: No such file > 0 > ipsvd-cdb failed. > make[1]: *** [Makefile:7: check] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/ipsvd_1.0.0-5_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: ipsvd Source-Version: 1.0.0-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of ipsvd, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated ipsvd 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: Sun, 21 Apr 2024 19:32:53 +0200 Source: ipsvd Architecture: source Version: 1.0.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1024283 1069448 Changes: ipsvd (1.0.0-6) unstable; urgency=medium . * QA upload. * Re-import package history into GIT. * Make the build verbose. * Do not omit the hardening flags. (Closes: #1024283, #1069448) * Fix building with -Werror=implicit-function-declaration. Checksums-Sha1: 9d2c2fccbdde0538130c422ce455d88d0672de2a 1734 ipsvd_1.0.0-6.dsc bff9a3f77d92c787f8e79d36bc2907752827b4ff 6108 ipsvd_1.0.0-6.debian.tar.xz 91712c6e472ca9e91779dfa650c3d63bfe09e30f 4717 ipsvd_1.0.0-6_source.buildinfo Checksums-Sha256: f31abc6d7790260120fe69753ae709474920ef0c8ebd1881fbbfd9fc8d5a946b 1734 ipsvd_1.0.0-6.dsc d16f38bbaad1066ea29ed5b7ce8955f72104954e8bfddbdd8cc953b4eb6f3c2c 6108 ipsvd_1.0.0-6.debian.tar.xz 09de445abaa3efa1fa974bd82bd1bb0c2c777beb1fc3cbf3f080aadb7dbfaf82 4717 ipsvd_1.0.0-6_source.buildinfo Files: 2f924aadfea9d5e807fa4c17101ec56e 1734 net optional ipsvd_1.0.0-6.dsc 628f662a5c4b036407a1030fe0ac6810 6108 net optional ipsvd_1.0.0-6.debian.tar.xz eef4ffe496704e271b5b374ed2025477 4717 net optional ipsvd_1.0.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlTlMQHGFuYmVAZGVi aWFuL
Bug#1069463: marked as done (blobwars: FTBFS on armhf: src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’})
Your message dated Sun, 21 Apr 2024 17:34:10 +
with message-id
and subject line Bug#1069463: fixed in blobwars 2.00-4
has caused the Debian Bug report #1069463,
regarding blobwars: FTBFS on armhf: src/CReplayData.cpp:41:34: error: cannot
convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
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.)
--
1069463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blobwars
Version: 2.00-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security `pkg-config
> --cflags sdl2 SDL2_mixer SDL2_image SDL2_ttf SDL2_net` -DVERSION=2.00
> -DRELEASE=1 -DUSEPAK=0 -DPAKNAME=\"blobwars.pak\"
> -DPAKLOCATION=\"/usr/share/games/blobwars/\" -DUNIX
> -DGAMEPLAYMANUAL=\"/usr/share/doc/blobwars/index.html\" -Wall
> -DLOCALEDIR=\"/usr/share/locale/\"
> -DMEDAL_SERVER_HOST=\"www.parallelrealities.co.uk\" -DMEDAL_SERVER_PORT=80 -g
> -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -O2 -g -flto -c
> src/CSwitch.cpp
> cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’
> is not valid for C++
> src/CReplayData.cpp: In member function ‘void
> ReplayData::printReplayInformation()’:
> src/CReplayData.cpp:41:34: error: cannot convert ‘long int*’ to ‘const
> time_t*’ {aka ‘const long long int*’}
>41 | tm *timeinfo = localtime();
> | ^~
> | |
> | long int*
> In file included from /usr/include/features.h:490,
> from /usr/include/errno.h:25,
> from src/headers.h:22,
> from src/CReplayData.cpp:1:
> /usr/include/time.h:141:19: note: initializing argument 1 of ‘tm*
> localtime(const time_t*)’
> 141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
> | ^~
> make[1]: *** [Makefile:83: CReplayData.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/blobwars_2.00-3_unstable-armhf.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: blobwars
Source-Version: 2.00-4
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
blobwars, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated blobwars 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: Sun, 21 Apr 2024 19:08:57 +0200
Source: blobwars
Architecture: source
Version: 2.00-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1069463
Changes:
blobwars (2.00-4) unstable; urgency=medium
.
* QA uplo
Bug#445823: marked as done (freecdb: FTBFS with parallel build)
Your message dated Sun, 21 Apr 2024 19:31:13 +0200 with message-id and subject line Re: Patch for freecdb parallel build has caused the Debian Bug report #445823, regarding freecdb: FTBFS with parallel build 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.) -- 445823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freecdb Version: 0.75 Severity: wishlist Usertags: ftbfs-parallel From my pbuilder build log, using dpkg-buildpackage -j3 ... fakeroot debian/rules binary : implicit + : directory debian/freecdb missing : debian/freecdb/usr/share/doc/freecdb/ make: *** [freecdb.deb-checkdir] Error 1 make: *** Waiting for unfinished jobs + install -m0644 debian/README.Debian.diet debian/freecdb/usr/share/doc/freecdb/ + install -m0644 debian/copyright debian/freecdb/usr/share/doc/freecdb/ + install -m0644 debian/changelog debian/freecdb/usr/share/doc/freecdb/changelog.Debian + mv debian/freecdb/usr/share/doc/freecdb/changelog.Debian debian/freecdb/usr/share/doc/freecdb/changelog dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- Version: 0.76 On Mon, 8 Oct 2007 10:09:57 -0400 Daniel Schepler wrote: Here's a patch to add proper dependencies to debian/implicit. That is gone with the switch to dh. Andreas--- End Message ---
Bug#746999: marked as done (Conflicting parameter types of function G311_multiSequenceFunc)
Your message dated Sun, 21 Apr 2024 16:19:08 + with message-id and subject line Bug#746999: fixed in canna 3.7p3-21 has caused the Debian Bug report #746999, regarding Conflicting parameter types of function G311_multiSequenceFunc 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.) -- 746999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: canna Version: 3.7p3-12 Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] gcc -o ./libcanna.so.1.2~ -shared -Wl,-z,relro -Wl,-soname,libcanna.so.1 jrbind.o ebind.o lisp.o defaultmap.o bushu.o chikuji.o commondata.o empty.o henkan.o hex.o ichiran.o jishu.o kctrl.o keydef.o kigo.o mode.o multi.o onoff.o parse.o romaji.o uiutil.o uldefine.o uldelete.o ulhinshi.o ulkigo.o ulmount.o ulserver.o util.o yesno.o bunsetsu.o engine.o RKroma.o RKkana.o obind.o rkc.o convert.o wconvert.o wutil.o conf.o cfuncs.o file.o strops.o -lc error: conflicting function declarations "G311_multiSequenceFunc" old definition in module keydef file keydef.c line 40 signed int (struct _uiContext *, struct _kanjiMode *, signed int, signed int, signed int) new definition in module multi file multi.c line 248 signed int (struct _uiContext *d, struct _kanjiMode *mode, signed int whattodo, unsigned int key, signed int fnum) Observe that the fourth argument (key) differs in signedness, which may cause problems for negative/large unsigned values. Best, Michael pgpkqrQIZUv96.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: canna Source-Version: 3.7p3-21 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of canna, 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 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated canna 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: Sun, 21 Apr 2024 17:43:26 +0200 Source: canna Architecture: source Version: 3.7p3-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 746999 1035504 1043711 1066375 Changes: canna (3.7p3-21) unstable; urgency=medium . * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066375, #746999) * Properly override dh_auto_install. (Closes: #1043711) * Clean more generated files. * Updated Turkish (tr) debconf translations, thanks to Atila KOÇ. (Closes: #1035504) * Update Lintian overrides. Checksums-Sha1: dd8c975461ddcb1d2c54fb326b7667833ce57a36 2058 canna_3.7p3-21.dsc 5bf486a707cdf4f5768301e686ec67d85eb0bafd 57152 canna_3.7p3-21.debian.tar.xz 8362bf7d776690b9a48a53dfed23a8cc2a9b763f 7938 canna_3.7p3-21_source.buildinfo Checksums-Sha256: 3ef153b4815b56a4a03cc354471a5fdbca49cb2b86f1931497eb9ebebc65c947 2058 canna_3.7p3-21.dsc 10cc022e6f2b557919d7553416fce9cd2f9ab5f6af2fd6460197b66cf9fb9e46 57152 canna_3.7p3-21.debian.tar.xz 52d9cf3b600269efc424f0a504643e1f9fb12c7e14c0e651c5679f10c06fd605 7938 canna_3.7p3-21_source.buildinfo Files: a75efef6943e28f771bba67f3de5cc04 2058 utils optional canna_3.7p3-21.dsc 9c93b5b8bd5020a9af9c8d9270b666d4 57152 utils optional canna_3.7p3-21.debian.tar.xz 739f87949dbe1168bc92e211ff8186c5 7938 utils optional canna_3.7p3-21_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlNgMQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCLW4EACjO6PIrdvXI37CQSw3aQcXvcrEjAS/HVGq V3OuZ+JZvoK8UU1r/SCOYOUsLAqg7LVfuZQq+3dpIGUEecfWlJh4KvJ/Dw4ufpfX LqE0JinFbnRgSbuS9XTiyq2leu1+GcEJ7BTRnL/Rs1jOgof3eEiEuCVg6vpDYjX0 f4gbe0o8UceDfWp6gEhQsqbbVSWZ6y6nNf8oHe6PeOjm8dOmKhwOim40wWEWgE5D othZvwKzGLb0qMAQokHznn34DCzEnNCY13pmY3H5mSQsMXftTFKxq1in7tSWIfdX YgkraMjFbsg9emmiJRUGpInBU1+FL+gcNFbUINI4P8tVMt2kw/Ee9I
Bug#1043711: marked as done (canna: Fails to build source after successful build)
Your message dated Sun, 21 Apr 2024 16:19:08 + with message-id and subject line Bug#1043711: fixed in canna 3.7p3-21 has caused the Debian Bug report #1043711, regarding canna: Fails to build source after successful build 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.) -- 1043711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: canna Version: 3.7p3-20 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package canna > dpkg-buildpackage: info: source version 3.7p3-20 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Helge Kreutzmann > > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > rm -f accanna.h config.log config.cache config.status pubconf.h cwenv.sh > rm -f -r include cannaconf.h > rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS > make.log MakeOut "#"* > cleaning in ./lib... > make[2]: Entering directory '/<>' > make[2]: warning: -j8 forced in submake: resetting jobserver mode. > rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS > make.log MakeOut "#"* > cleaning in lib/RKindep... > make[3]: Entering directory '/<>/lib' > make[3]: warning: -j8 forced in submake: resetting jobserver mode. > Makefile:1147: warning: ignoring prerequisites on suffix rule definition > rm -f cfuncs.sub file.sub cksum.sub ecfuncs.sub strops.sub > rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS > make.log MakeOut "#"* > rm -f Makefile Makefile.dep > make[3]: Leaving directory '/<>/lib/RKindep' > cleaning in lib/RK... > make[3]: Entering directory '/<>/lib' > make[3]: warning: -j8 forced in submake: resetting jobserver mode. > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkBgnBun.tmp RkBgnBun.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkDefine.tmp RkDefine.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkDelete.tmp RkDelete.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkEndBun.tmp RkEndBun.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkEnlarg.tmp RkEnlarg.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkFinali.tmp RkFinali.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGetDic.tmp RkGetDic.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGetKan.tmp RkGetKan.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGetLex.tmp RkGetLex.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGetSta.tmp RkGetSta.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGetYom.tmp RkGetYom.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkGoto.tmp RkGoto.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkInitia.tmp RkInitia.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkIntro.tmp RkIntro.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed > rm -f RkLeft.tmp RkLeft.jtmp > rm -f ../../misc/manual.sed > rm -f ../../misc/manual.sed >
Bug#1035504: marked as done (canna: [INTL:tr] turkish translation of debconf messages)
Your message dated Sun, 21 Apr 2024 16:19:08 + with message-id and subject line Bug#1035504: fixed in canna 3.7p3-21 has caused the Debian Bug report #1035504, regarding canna: [INTL:tr] turkish translation of debconf messages 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.) -- 1035504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: canna Severity: wishlist Tags: l10n patch Hello, Find attached the updated Turkish translation of the canna debconf messages. It has been submitted for review to the debian-l10n-turkish mailing list. Please include it in your next upload. Regards, Atila KOÇ --- YASAL UYARI --- # Turkish debconf translation of canna # This file is distributed under the same license as the canna package. # Mert Dirik , 2008. # Atila KOÇ , 2023. # msgid "" msgstr "" "Project-Id-Version: canna\n" "Report-Msgid-Bugs-To: ca...@packages.debian.org\n" "POT-Creation-Date: 2009-05-03 07:53+0200\n" "PO-Revision-Date: 2023-04-17 21:49+0300\n" "Last-Translator: Atila KOÇ \n" "Language-Team: Debian L10n Turkish \n" "Language: tr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" "X-Generator: Poedit 2.4.2\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Should the Canna server run automatically?" msgstr "Canna sunucusu otomatikman çalışsın mı?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "This package contains the Canna server and server-related utilities. If you " "are only interested in these utilities, you can disable the Canna server now." msgstr "" "Bu paket Canna sunucusunu ve sunucuyla ilgili araçları içerir. Eğer yalnızca " "bu araçlarla ilgileniyorsanız, Canna sunucusunu şimdi " "etkisizleştirebilirsiniz." #. Type: boolean #. Description #: ../templates:3001 msgid "Should the Canna server run in network mode?" msgstr "Canna sunucusu ağ kipinde mi çalışmalı?" #. Type: boolean #. Description #: ../templates:3001 msgid "" "By default the Canna server will run without support for network " "connections, and will only accept connections on UNIX domain sockets, from " "clients running on the same host." msgstr "" "Öntanımlı olarak Canna sunucusu ağ bağlantılarına destek vermeden çalışır ve " "yalnızca aynı makinede çalışan istemcilerden gelen UNIX etki alanı soketi " "bağlantılarını kabul eder." #. Type: boolean #. Description #: ../templates:3001 msgid "" "If you choose this option, network support will be activated, and the Canna " "server will accept connections on TCP sockets from clients that may be on " "remote hosts. Some clients (such as egg and yc-el) require this mode even if " "they run on the local host." msgstr "" "Eğer bu seçeneği seçerseniz, ağ desteği etkinleştirilecek ve Canna sunucusu " "uzak makinelerde çalışan istemcilerden gelen TCP soketi bağlantılarını da " "kabul edecektir. egg ve yc-el gibi bazı istemciler, aynı makinede çalışsalar " "bile bu kipi gerektirebilirler." #. Type: boolean #. Description #: ../templates:4001 msgid "Manage /etc/hosts.canna automatically?" msgstr "/etc/hosts.canna otomatikman yönetilsin mi?" #. Type: boolean #. Description #: ../templates:4001 msgid "" "The /etc/hosts.canna file lists hosts allowed to connect to the Canna server." msgstr "" "/etc/hosts.canna dosyası Canna sunucusuna bağlanabilecek makineleri listeler." #. Type: boolean #. Description #: ../templates:4001 msgid "" "You should not accept this option if you prefer managing the file's contents " "manually." msgstr "Dosyanın içeriğini elle yönetecekseniz, bu seçeneği seçmemelisiniz." #. Type: string #. Description #: ../templates:5001 msgid "Hosts allowed to connect to this Canna server:" msgstr "Bu Canna sunucusuna bağlanma izni verilen makineler:" #. Type: string #. Description #: ../templates:5001 msgid "" "Please enter the names of the hosts allowed to connect to this Canna server, " &quo
Bug#1066375: marked as done (canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration])
Your message dated Sun, 21 Apr 2024 16:19:08 + with message-id and subject line Bug#1066375: fixed in canna 3.7p3-21 has caused the Debian Bug report #1066375, regarding canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-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.) -- 1066375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: canna Version: 3.7p3-20 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 -g -Wall -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 -I../../include -Dlinux -D__amd64__ > -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE > -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE >-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -DFUNCPROTO=15 > -DNARROWPROTO context.c > In file included from /usr/include/inttypes.h:25, > from ../../include/canna/sysdep.h:30, > from ../../include/canna/RK.h:44, > from RKintern.h:58, > from context.c:28: > /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > context.c: In function ‘_RkInitialize’: > context.c:105:13: error: implicit declaration of function ‘mkdir’ > [-Werror=implicit-function-declaration] > 105 | if (mkdir(path, MKDIR_MODE) < 0 && > | ^ > context.c: At top level: > context.c:24:13: warning: ‘rcsid’ defined but not used [-Wunused-variable] >24 | static char rcsid[]="$Id: context.c,v 1.5 2003/09/17 08:50:52 aida_s > Exp $"; > | ^ > cc1: some warnings being treated as errors > make[5]: *** [Makefile:1123: context.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/canna_3.7p3-20_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: canna Source-Version: 3.7p3-21 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of canna, 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 Beckmann (supplier of updated canna 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: Sun, 21 Apr 2024 17:43:26 +0200 Source: canna Architecture: source Version: 3.7p3-21 Distribution: unstable Urgency:
Bug#1069440: marked as done (olpc-kbdshim: FTBFS on armhf: common.c:342:24: error: ‘struct input_event’ has no member named ‘time’)
Your message dated Sun, 21 Apr 2024 14:51:43 + with message-id and subject line Bug#1069440: fixed in olpc-kbdshim 27-3 has caused the Debian Bug report #1069440, regarding olpc-kbdshim: FTBFS on armhf: common.c:342:24: error: ‘struct input_event’ has no member named ‘time’ 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.) -- 1069440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olpc-kbdshim Version: 27-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -Wall -O2 -g > -DVERSION=27 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o olpc-kbdshim-udev.o olpc-kbdshim-udev.c > common.c: In function ‘inject_uinput_event’: > common.c:342:24: error: ‘struct input_event’ has no member named ‘time’ > 342 | gettimeofday(, NULL); > |^ > make[1]: *** [: common.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/olpc-kbdshim_27-2_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: olpc-kbdshim Source-Version: 27-3 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of olpc-kbdshim, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated olpc-kbdshim 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: Sun, 21 Apr 2024 16:05:16 +0200 Source: olpc-kbdshim Architecture: source Version: 27-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1069440 Changes: olpc-kbdshim (27-3) unstable; urgency=medium . * QA upload. * Import package history into GIT. * Tune (Pre-)Depends. * Do not omit hardening flags. * Update Lintian overrides. * Add upstream metadata, Homepage and watch file. * Work around struct input_event.time kernel api change. (Closes: #1069440) Checksums-Sha1: cae724493ba030f5a98dd0a9afdcce9c7e7ab605 1904 olpc-kbdshim_27-3.dsc 2de22160aa93ca7d2a0127c2174c5fa46c765265 3644 olpc-kbdshim_27-3.debian.tar.xz 6eb40048a37db9dbd68e7c45cd4f4fa7f8222d97 5665 olpc-kbdshim_27-3_source.buildinfo Checksums-Sha256: 49b3e68d9ea7f467d27b1666517bbfaf2861863df661ad93b4242a8192a15d37 1904 olpc-kbdshim_27-3.dsc a98a53fbbf40ab61190f84d21040e08de5638e89da1b25d7028959d80f9fab09 3644 olpc-kbdshim_27-3.debian.tar.xz 5e6b98191e67a8ebcf7631c6b41bdb51c8edf3b340bb8b7087d3c5816378cd8c 5665 olpc-kbdshim_27-3_source.buildinfo Files: f78ef5ef4d019b9cbeaa42304c389a48 1904 admin optional olpc-kbdshim_27-3.dsc 03fe53787467c9e6773f7fbb67d993d6 3644 admin optional olpc-kbdshim_27-3.debian.tar.xz a2e92314eeca38e3242b8af8d36bf149 5665 admin optional olpc-kbdshim_27-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYlHY0QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCJXv
Bug#1069435: marked as done (olpc-powerd: FTBFS on armhf: olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’)
Your message dated Sun, 21 Apr 2024 11:51:41 + with message-id and subject line Bug#1069435: fixed in olpc-powerd 23-5 has caused the Debian Bug report #1069435, regarding olpc-powerd: FTBFS on armhf: olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’ 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.) -- 1069435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olpc-powerd Version: 23-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > cc -Wall -O2 -g -DVERSION=23 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro pnmto565fb.c > -o pnmto565fb > pnmto565fb.c: In function ‘showimage’: > pnmto565fb.c:374:5: warning: implicit declaration of function ‘readahead’ > [-Wimplicit-function-declaration] > 374 | readahead(fd, 0, sb.st_size); > | ^ > olpc-switchd.c: In function ‘round_secs’: > olpc-switchd.c:311:14: error: ‘struct input_event’ has no member named ‘time’ > 311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0); > | ^~ > olpc-switchd.c:311:34: error: ‘struct input_event’ has no member named ‘time’ > 311 | return ev->time.tv_sec + ((ev->time.tv_usec > 50) ? 1 : 0); > | ^~ > olpc-switchd.c: In function ‘power_button_event’: > olpc-switchd.c:323:11: error: ‘struct input_event’ has no member named ‘time’ > 323 | ev->time.tv_sec, ev->time.tv_usec, > | ^~ > olpc-switchd.c:323:28: error: ‘struct input_event’ has no member named ‘time’ > 323 | ev->time.tv_sec, ev->time.tv_usec, > |^~ > pnmto565fb.c:312:25: warning: variable ‘rightfillcols’ set but not used > [-Wunused-but-set-variable] > 312 | int bottomfillrows, rightfillcols; > | ^ > olpc-switchd.c: In function ‘lid_event’: > olpc-switchd.c:339:11: error: ‘struct input_event’ has no member named ‘time’ > 339 | ev->time.tv_sec, ev->time.tv_usec, > | ^~ > olpc-switchd.c:339:28: error: ‘struct input_event’ has no member named ‘time’ > 339 | ev->time.tv_sec, ev->time.tv_usec, > |^~ > olpc-switchd.c: In function ‘ebook_event’: > olpc-switchd.c:359:11: error: ‘struct input_event’ has no member named ‘time’ > 359 | ev->time.tv_sec, ev->time.tv_usec, > | ^~ > olpc-switchd.c:359:28: error: ‘struct input_event’ has no member named ‘time’ > 359 | ev->time.tv_sec, ev->time.tv_usec, > |^~ > olpc-switchd.c: In function ‘acpwr_event’: > olpc-switchd.c:379:11: error: ‘struct input_event’ has no member named ‘time’ > 379 | ev->time.tv_sec, ev->time.tv_usec, > | ^~ > olpc-switchd.c:379:28: error: ‘struct input_event’ has no member named ‘time’ > 379 | ev->time.tv_sec, ev->time.tv_usec, > |^~ > olpc-switchd.c: In function ‘round_secs’: > olpc-switchd.c:312:1: warning: control reaches end of non-void function > [-Wreturn-type] > 312 | } > | ^ > make[1]: *** [: olpc-switchd] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/olpc-powerd_23-4_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: olpc-p
Bug#641204: marked as done (olpc-powerd: should list the "dialog" package (at least) as a suggested package)
Your message dated Sun, 21 Apr 2024 11:51:41 + with message-id and subject line Bug#641204: fixed in olpc-powerd 23-5 has caused the Debian Bug report #641204, regarding olpc-powerd: should list the "dialog" package (at least) as a suggested package 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.) -- 641204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: olpc-powerd Version: 23-2 Severity: important 1) "sudo powerd-config" yields: [sudo] password for nerd: powerd-config: the 'dialog' program isn't available, quitting. Use a text editor to edit profiles under /etc/olpc-powerd, and (re)activate them with: 'powerd-config profilename' (Or use 'sudo yum install dialog' to install the package.) 2) The suggestion to use 'sudo yum install dialog' could do with a patch as well... -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages olpc-powerd depends on: ii ethtool 1:2.6.34-3 display or change Ethernet device ii libc6 2.13-10Embedded GNU C Library: Shared lib Versions of packages olpc-powerd recommends: ii iptables 1.4.8-3administration tools for packet fi olpc-powerd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: olpc-powerd Source-Version: 23-5 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of olpc-powerd, 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 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated olpc-powerd 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: Sun, 21 Apr 2024 13:23:18 +0200 Source: olpc-powerd Architecture: source Version: 23-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 641204 1021457 1069435 Changes: olpc-powerd (23-5) unstable; urgency=medium . * QA upload. * Import package history into GIT. * Generate and cleanup debian/powerd.conf during package build. * Do not overwrite hardening flags. (Closes: #1021457) * Fix building with -Werror=implicit-function-declaration. * Tune (Pre-)Depends. * Add Recommends: dialog. (Closes: #641204) * Work around struct input_event.time kernel api change. (Closes: #1069435) * Add upstream metadata, Homepage and watch file. Checksums-Sha1: 5caa13a4a18a66ac83ec4949e05719b6a21cd1db 1875 olpc-powerd_23-5.dsc 8d57dad3a8215691405e998ea9079a747f25cae8 4132 olpc-powerd_23-5.debian.tar.xz db898663109e1582c824ba951d65551f6b0027dd 5631 olpc-powerd_23-5_source.buildinfo Checksums-Sha256: ef0d74243ee379ee6622696bdea40f71558c207aacdc0e757dd6e7efce447855 1875 olpc-powerd_23-5.dsc a8ceaf9cd258581037b85399d511d4dc61e1acf68f59e857391264d13ce6060d 4132 olpc-powerd_23-5.debian.tar.xz 70a07b16aa23ed2f872e79ea87bf7f2f348594b5b5441661e8da0a1831a87b34 5631 olpc-powerd_23-5_source.buildinfo Files: a89f291936dc20eee8d9b521e788a47e 1875 admin optional olpc-powerd_23-5.dsc 30dab7ea7ff172370c21c88652173991 4132 admin optional olpc-powerd_23-5.debian.tar.xz eaec2f851ee2d3258401be0d28ce1b63 5631 admin optional olpc-powerd_23-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYk94gQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCDx5D/0eCq+F57uZ2HVcFC9FPVBn6ZRIthX1Tthc YD306jIvO+P6nSLiBN9zgShRALEyDKD/jW1w5yHwGVMD95c/dPtWOgUbCO0mnTW3 P1cQg0+2YTw5pXclc9wVqGhkhMR+w6oH8jHri7uQWU0BepEx98oNZ3UoAi9sqcWq wiHB/tPssYgVXue6BiyEPOcpGH4Zh8ThUSePxlaHejnyWGLiOv+N2Fhi7pwbiHSb Zs5sWkQP8S3JNYrLfShUgD2I52P5Jpy0XHUAPhcYQkBbOoNHF+aIIed7kHCPWDAj 8bSPlstjsSyJOIPWopMV+eJEajCFbImxYq6f1ktRhO6tWSw78Lu3yqApnD5A77KD J6m4F6OsFawWz2zRVAmYuYbLcpmig0/xSml/xC2OgzqXhzGGDQjayUiMBk
Bug#1021457: marked as done (olpc-powerd: reproducible-builds: build path embedded in debugging symbols)
Your message dated Sun, 21 Apr 2024 11:51:41 + with message-id and subject line Bug#1021457: fixed in olpc-powerd 23-5 has caused the Debian Bug report #1021457, regarding olpc-powerd: reproducible-builds: build path embedded in debugging symbols 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.) -- 1021457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olpc-powerd Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The build path is embedded in /usr/lib/debug/.dwz/x86_64-linux-gnu/olpc-powerd.debug: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/olpc-powerd.html /build/1st/olpc-powerd-23 vs. /build/2/olpc-powerd-23/2nd The attached patch to the upstream Makefile fixes this by appending to CFLAGS instead of overriding them, allowing the default CFLAGS to be passed. According to my local tests, with this patch applied, olpc-powerd should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining olpc-powerd! live well, vagrant From 28c1a60abd0c8dd1c41cfe0d30f755441c941cff Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 2 May 2022 16:18:08 + Subject: [PATCH] Makefile: Append to CFLAGS. This allows passing the default flags from dpkg-buildflags. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 5c0315a..bc1f3c7 100644 --- a/Makefile +++ b/Makefile @@ -35,7 +35,7 @@ OPT_FLAGS ?= -O2 -g PROGS = olpc-switchd pnmto565fb -CFLAGS = -Wall $(OPT_FLAGS) -DVERSION=$(VERSION) +CFLAGS += -Wall $(OPT_FLAGS) -DVERSION=$(VERSION) # -- 2.37.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: olpc-powerd Source-Version: 23-5 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of olpc-powerd, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated olpc-powerd 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: Sun, 21 Apr 2024 13:23:18 +0200 Source: olpc-powerd Architecture: source Version: 23-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 641204 1021457 1069435 Changes: olpc-powerd (23-5) unstable; urgency=medium . * QA upload. * Import package history into GIT. * Generate and cleanup debian/powerd.conf during package build. * Do not overwrite hardening flags. (Closes: #1021457) * Fix building with -Werror=implicit-function-declaration. * Tune (Pre-)Depends. * Add Recommends: dialog. (Closes: #641204) * Work around struct input_event.time kernel api change. (Closes: #1069435) * Add upstream metadata, Homepage and watch file. Checksums-Sha1: 5caa13a4a18a66ac83ec4949e05719b6a21cd1db 1875 olpc-powerd_23-5.dsc 8d57dad3a8215691405e998ea9079a747f25cae8 4132 olpc-powerd_23-5.debian.tar.xz db898663109e1582c824ba951d65551f6b0027dd 5631 olpc-powerd_23-5_source.buildinfo Checksums-Sha256: ef0d74243ee379ee6622696bdea40f71558c207aacdc0e757dd6e7efce447855 1875 olpc-powerd_23-5.dsc a8ceaf9cd258581037b85399d511d4dc61e1acf68f59e857391264d13ce6060d 4132 olpc-powerd_23-5.debian.tar.xz 70a07b16aa23ed2f872e79ea87bf7f2f348594b5b5441661e8da0a1831a87b34 5631 olpc-powerd_23-5_source.buildinfo Files: a89f291936dc20eee8d9b521e788a47e 1875 admin optional olpc-powerd_23-5.dsc 30dab7ea7ff172370c21c88652173991 4132 admin optional olpc-powerd_23-5.debian.tar.xz eaec2f851ee2d3258401be0d28ce1b63 5631 admin optional olpc-powerd_23-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYk94gQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCDx5D/0eCq+F57uZ2HVcFC9FPVBn6ZRIthX1Tthc YD306jIvO+P6nSLiBN9zgShRALEyDKD/jW1w5yHwGVMD95c/dPtWOgUbCO0mnTW3 P1cQg0+2YTw5pXclc9wVqGhkhMR+w6oH8jHri7uQWU0BepEx98oNZ3UoAi9sqcWq wiHB
Bug#1069453: marked as done (tcmu: FTBFS on armhf: build-dependency not installable: librados-dev)
Your message dated Sun, 21 Apr 2024 11:14:36 + with message-id and subject line Bug#1069453: fixed in tcmu 1.5.4-8 has caused the Debian Bug report #1069453, regarding tcmu: FTBFS on armhf: build-dependency not installable: librados-dev 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.) -- 1069453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcmu Version: 1.5.4-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, > libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, > zlib1g-dev, build-essential, fakeroot > Filtered Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, > libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, > zlib1g-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [794 B] > Get:5 copy:/<>/apt_archive ./ Packages [757 B] > Fetched 2160 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librados-dev but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/04/20/tcmu_1.5.4-6_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: tcmu Source-Version: 1.5.4-8 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of tcmu, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated tcmu 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: Sun, 21 Apr 2024 12:46:27 +0200 Source: tcmu Architecture: source Version: 1.5.4-8 Distribution: unstable Urgency: medium Maintain
Processed: reopening 1069453
Processing commands for cont...@bugs.debian.org:
> reopen 1069453
Bug #1069453 {Done: Andreas Beckmann } [src:tcmu] tcmu: FTBFS
on armhf: build-dependency not installable: librados-dev
'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 tcmu/1.5.4-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069453: marked as done (tcmu: FTBFS on armhf: build-dependency not installable: librados-dev)
Your message dated Sun, 21 Apr 2024 08:37:42 + with message-id and subject line Bug#1069453: fixed in tcmu 1.5.4-7 has caused the Debian Bug report #1069453, regarding tcmu: FTBFS on armhf: build-dependency not installable: librados-dev 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.) -- 1069453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcmu Version: 1.5.4-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, > libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, > zlib1g-dev, build-essential, fakeroot > Filtered Build-Depends: cmake, debhelper-compat (= 13), kmod, libglib2.0-dev, > libkmod-dev, libnl-genl-3-dev, librados-dev, pkgconf, systemd-dev, > zlib1g-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [794 B] > Get:5 copy:/<>/apt_archive ./ Packages [757 B] > Fetched 2160 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librados-dev but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/04/20/tcmu_1.5.4-6_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: tcmu Source-Version: 1.5.4-7 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of tcmu, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated tcmu 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: Sun, 21 Apr 2024 10:20:23 +0200 Source: tcmu Architecture: source Version: 1.5.4-7 Distribution: unstable Urgency: medium Maintainer: Debian
Bug#1069309: marked as done (xfractint FTBFS: error: implicit declaration of function)
Your message dated Fri, 19 Apr 2024 23:50:55 + with message-id and subject line Bug#1069309: fixed in xfractint 20.4.10-5 has caused the Debian Bug report #1069309, regarding xfractint FTBFS: error: implicit declaration of function 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.) -- 1069309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfractint Version: 20.4.10-4 Severity: serious Tags: ftbfs X-Debbugs-Cc: Petter Reinholdtsen https://buildd.debian.org/status/logs.php?pkg=xfractint=20.4.10-4 ... /usr/bin/gcc -I../headers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I./headers -DXFRACT -DNOBSTRING -g -DBIG_ANSI_C -DLINUX -fno-builtin -fcommon -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o 3d.o 3d.c 3d.c: In function ‘longvmultpersp’: 3d.c:290:20: error: implicit declaration of function ‘multiply’ [-Werror=implicit-function-declaration] 290 | tmp[j] += multiply(s[i],m[i][j],bitshift); |^~~~ 3d.c:318:20: error: implicit declaration of function ‘divide’ [-Werror=implicit-function-declaration] 318 | tmpview[0] = divide(lview[0],denom,bitshift); |^~ cc1: some warnings being treated as errors make[3]: *** [: 3d.o] Error 1 --- End Message --- --- Begin Message --- Source: xfractint Source-Version: 20.4.10-5 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of xfractint, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated xfractint 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: Sat, 20 Apr 2024 01:16:21 +0200 Source: xfractint Architecture: source Version: 20.4.10-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1069309 Changes: xfractint (20.4.10-5) unstable; urgency=medium . * QA upload. . * Added 1030-no-implicit-declaration.patch to fix build problem (Closes: #1069309). Checksums-Sha1: 9ea5d0559462e62f70d74e6ef19ab086543b5f65 1901 xfractint_20.4.10-5.dsc d1c642a50b7b7384b4610d00f4a4d97ef56b38e2 8312 xfractint_20.4.10-5.debian.tar.xz 83089127b415877ac18b822465765092bd8d0605 6861 xfractint_20.4.10-5_source.buildinfo Checksums-Sha256: 01a4ea7dae2b788f6b9efdd6d23cae744734dd0ae3da7591275feb626e363f5e 1901 xfractint_20.4.10-5.dsc 856f398da106ba975b849e6053f7e08a5b123144ad680554f71630553e761530 8312 xfractint_20.4.10-5.debian.tar.xz 6a0ef1208d1fe4a49553635953e3e36145e7f1548974acc5cd0f234bdc98ed8d 6861 xfractint_20.4.10-5_source.buildinfo Files: a33e1344877e50e5f56b2344914f26e4 1901 non-free/graphics optional xfractint_20.4.10-5.dsc 7572ab1b79b7849d95efa0bdd70006c5 8312 non-free/graphics optional xfractint_20.4.10-5.debian.tar.xz 736e5e708eabd41452203a0f0e40a256 6861 non-free/graphics optional xfractint_20.4.10-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYi/AoACgkQgSgKoIe6 +w4LcA/+JVzulbP6dWP5uDBcatN1GeK4eZC2qllpY8CacloFfMMHiKq+jVCPGZzr Ez+BHuIpMEhxK/NRqU7KrNcoO8DqvIvsADn8L+EItbrkcMaThoErMksabmf14lX5 L8t4fLu6kXsmAHbSRlx0RhJ+meI+xW9j5gwAjVjg1Rzz6vlUmDINoq+mhwZOZAwz S6wWP6jhFPo5UZ0Fb4Mdf+V8OqT+nIMeVLEn6nU/knbNXr4xZ9/nGXM/bc+lPTCa BaEe7qJAnqAqSv/plAIhbmarCm/BXXIFVud+DwKWuleeq2AOwX3N22W7+l8EQS7I e/uRdBq52UK9iuWdb5rxuY3BbvQg1x0T4Rzd0RJpeo8CrLrXnUqLYCPZYWcvLa2C 18W29Hw0u1bNqqNGkhKd7CZxlESclZ8d6d1/8qcaxQ9FlILnjKgznb8Bs31YeQQl Oc6ToftiNRQ3qnL3WAx+1eN5Qicnx4JA0RFHrkS99MvpDZrlXhEaFA63fPxMjNwK 0QjJrMPwTN9X0bmmx0jZT/LJB/H2mkLd9vNnXRDal5QSdezipeZ0FajmwAh1ULuM JN8CH2cahB2zcXTYPW3UdAHuygDMy6PBjYRFwsYubOBHTmGsHZAJPYlIXcXHJLdh x4+6v+WQvAnu8P7+qBX1g++hubqlxHBCnFW4y5cf/YHOGg4MG5Y= =0j4s -END PGP SIGNATURE- pgpiMYU8sCXxJ.pgp Description: PGP signature --- End Message ---
Bug#789586: marked as done (unar: Fails to extract files from a RAR archive embedded into an .exe)
Your message dated Fri, 19 Apr 2024 23:54:47 +0200 with message-id <552ecb67-4d5b-425b-930a-a786d7d2a...@debian.org> and subject line Re: Bug#789586: unar: Fails to extract files from a RAR archive embedded into an .exe has caused the Debian Bug report #789586, regarding unar: Fails to extract files from a RAR archive embedded into an .exe 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.) -- 789586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.8.1-4 Severity: normal Hi there, unar fails to extract the .cab files from the Arx Fatalis demo archive, which is provided as a RAR archive embedded into an .exe file. Please see here for the archive and download instructions: http://ds.nordicgames.at/arxfatalis/arx_demo_english.exe http://wiki.arx-libertatis.org/Getting_the_game_data This became apparent while preparing to package the game data during game-data-packager development, hence the CC. Cheers, Fabian -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unar depends on: ii dpkg 1.18.1 ii gnustep-base-runtime 1.24.7-1 ii libbz2-1.01.0.6-8 ii libc6 2.19-18 ii libgcc1 1:5.1.1-9 ii libgnustep-base1.24 1.24.7-1 ii libicu52 52.1-9 ii libobjc4 5.1.1-9 ii libstdc++65.1.1-9 ii libwavpack1 4.75.0-1 ii zlib1g1:1.2.8.dfsg-2+b1 unar recommends no packages. unar suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.10.8+ds1-1--- End Message ---
Processed: for
Processing commands for cont...@bugs.debian.org: > forwarded 789591 https://github.com/MacPaw/XADMaster/issues/50 Bug #789591 [unar] unar: Fails to extract files from a LHA archive embedded into an .exe Set Bug forwarded-to-address to 'https://github.com/MacPaw/XADMaster/issues/50'. > forwarded 789586 https://github.com/MacPaw/XADMaster/issues/51 Bug #789586 [unar] unar: Fails to extract files from a RAR archive embedded into an .exe Set Bug forwarded-to-address to 'https://github.com/MacPaw/XADMaster/issues/51'. > End of message, stopping processing here. Please contact me if you need assistance. -- 789586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789586 789591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#790367: marked as done (unar: lsar -L doesn't show timestamp, only format string)
Your message dated Fri, 19 Apr 2024 23:17:15 +0200 with message-id <7859a039-bb57-4ebd-8ecc-d3d6419f9...@debian.org> and subject line Re: unar: lsar -L doesn't show timestamp, only format string has caused the Debian Bug report #790367, regarding unar: lsar -L doesn't show timestamp, only format string 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.) -- 790367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.8.1-4 Severity: minor Dear Maintainer, When I run `lsar -L` it doesn't display a timestamp for "Last modified" of the various files. Instead, it shows a format string: Last modified:MMdd hh:mm a Looks like `lsar -l` is able to pick up and display the correct timestamps though. Tested with a random .zip-file. Presumably the case for all files. (See also https://bugs.launchpad.net/ubuntu/+source/unar/+bug/1393322) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unar depends on: ii dpkg 1.18.1 ii gnustep-base-runtime 1.24.7-1 ii libbz2-1.01.0.6-8 ii libc6 2.19-18 ii libgcc1 1:5.1.1-12 ii libgnustep-base1.24 1.24.7-1 ii libicu52 52.1-9 ii libobjc4 5.1.1-12 ii libstdc++65.1.1-12 ii libwavpack1 4.75.0-1 ii zlib1g1:1.2.8.dfsg-2+b1 unar recommends no packages. unar suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org --- End Message --- --- Begin Message --- Version: 1.10.8+ds1-1--- End Message ---
Bug#1013221: marked as done (sendfile: /etc/cron.weekly job complains about deprecated tempfile)
Your message dated Fri, 19 Apr 2024 00:16:37 +0200
with message-id
and subject line Re: sendfile: /etc/cron.weekly job complains about deprecated
tempfile
has caused the Debian Bug report #1013221,
regarding sendfile: /etc/cron.weekly job complains about deprecated tempfile
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.)
--
1013221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendfile
Version: 2.1b.20080616-8
Severity: normal
I'm getting an email weekly:
/etc/cron.weekly/sendfile:
WARNING: tempfile is deprecated; consider using mktemp instead.
Replacing the recommended action seems to fix the issue.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages sendfile depends on:
ii libc6 2.31-13+deb11u3
ii libdpkg-perl 1.20.10
ii libreadline8 8.1-1
ii openbsd-inetd [inet-superserver] 0.20160825-5
ii perl 5.32.1-4+deb11u2
ii update-inetd 4.51
sendfile recommends no packages.
Versions of packages sendfile suggests:
pn pgp-i
-- Configuration Files:
/etc/cron.weekly/sendfile changed:
test -f /etc/sendfile.cf || exit 0
test -x /usr/bin/sendfile || exit 0
spooldir=$(sendfile -qW=spool)
cd $spooldir || exit 0
export LANG=C
maxage=$(grep '^deljunk' /etc/sendfile.cf)
test -n "$maxage" || exit 0
maxage=${maxage##*=}
maxage=${maxage//}
maxage=${maxage/ /}
pivot=$spooldir/pivot
touch -d now-${maxage}days $pivot
touch -d now-1day $pivot.yesterday
tmp=$(mktemp)
trap "rm -f $tmp $pivot $pivot.yesterday" INT EXIT
for i in *
do
if [ -z "$(getent passwd "$i")" ]
then
continue
fi
echo -n > $tmp
if [ -d "$i" ]
then
(
cd "$i"
for f in $(find -maxdepth 1 -name '*.h')
do
b=${f#./}
b=${b%.h}
FILE=
SIZE=
while read line
do
case $line in
FILE*) FILE=${line#FILE }
;;
SIZE*) SIZE=${line#SIZE }
SIZE=${SIZE#* }
;;
esac
done < $f
size=$(stat $b.d|grep Size)
size=${size#*Size: }
size=${size%% *}
if [ $SIZE -gt $size ]
then
if [ $b.d -ot $pivot ]
then
logger -i -p daemon.info -t sendfile "sf_cleanup: Expired
partial file $b for user $i"
rm -f ${b}.{dh}
else
if [ $b.d -ot $pivot.yesterday ]
then
echo "Partial file $b will expire after $maxage days"
>> $tmp
fi
fi
fi
done
)
if [ -s $tmp ]
then
(
echo "Subject: Weekly SAFT Report"
echo "From: SAFT Server "
echo
echo "The following incompletely received files have been found
in the SAFT"
echo "spool directory $spooldir:"
echo
cat $tmp
) | /usr/sbin/sendmail $i
fi
fi
done
/etc/logrotate.d/sendfile changed:
/var/spool/sendfile/*/log {
weekly
compress
rotate 7
missingok
nocreate
sharedscripts
}
/etc/profile.d/sendfile [Errno 2] No such file or directory:
'/etc/profile.d/sendfile'
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.1b.20080616-9
Hi. I don't use or maintain sendfile myself, but according to the changelog:
* debian/sf_cleanup: Replace missing tempfile(1) call with mktemp(1).
(Closes: #969409)
this was fixed in the version above.
Thanks.--- End Message ---
Bug#975138: marked as done (simulavr: FTBFS: collect2: error: ld returned 1 exit status)
Your message dated Thu, 18 Apr 2024 10:34:44 + with message-id and subject line Bug#975138: fixed in simulavr 1.0.0+git20160221.e53413b-3 has caused the Debian Bug report #975138, regarding simulavr: FTBFS: collect2: error: ld returned 1 exit status to be marked as done. This means that you 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.) -- 975138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simulavr Version: 1.0.0+git20160221.e53413b-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/gcc/avr/5.4.0/../../../avr/bin/ld: abort_at90s4433.elf section > `.data' will not fit in region `data' > /usr/lib/gcc/avr/5.4.0/../../../avr/bin/ld: region `data' overflowed by 8 > bytes > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/11/19/simulavr_1.0.0+git20160221.e53413b-2_unstable.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: simulavr Source-Version: 1.0.0+git20160221.e53413b-3 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of simulavr, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated simulavr 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, 18 Apr 2024 12:09:05 +0200 Source: simulavr Architecture: source Version: 1.0.0+git20160221.e53413b-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 975138 Changes: simulavr (1.0.0+git20160221.e53413b-3) unstable; urgency=medium . * QA upload. * Import package history into GIT. * Limit to -std=c++14. * Shorten strings to avoid "region `data' overflowed by 8 bytes" on some targets. (Closes: #975138) * Declare Rules-Requires-Root: no. * Add -fdebug-prefix-map=... to AVR_CFLAGS for reproducible builds. * CI: Exclude avr-gcc from blhc checks. Checksums-Sha1: 487218a027d98527503736fc6891363cdfe1be9d 2068 simulavr_1.0.0+git20160221.e53413b-3.dsc d325366c44acb349d2d4212e63a9bf63f96b5c47 30752 simulavr_1.0.0+git20160221.e53413b-3.debian.tar.xz 34950cad2822f90409e826a07df3fa912b7f8dca 6658 simulavr_1.0.0+git20160221.e53413b-3_source.buildinfo Checksums-Sha256: 115b47ddfc878db5b9b58aaaf1e3e8791627151f423c15753b1d6a89527b2c24 2068 simulavr_1.0.0+git20160221.e53413b-3.dsc 40a18749f064e60503aa46e0161ce00f6f2647d974fced58a393e575d4c8c881 30752 simulavr_1.0.0+git20160221.e53413b-3.debian.tar.xz 98778be1d61a31a70aa9497469a15b6ae8a8280c13c58923d5aee83cdce24a30 6658 simulavr_1.0.0+git20160221.e53413b-3_source.buildinfo Files: da27b85450b1e03f5a345f307c4167aa 2068 electronics optional simulavr_1.0.0+git20160221.e53413b-3.dsc 034807e34c000d3e8e6f3a10ebc6827a 30752 electronics optional simulavr_1.0.0+git20160221.e53413b-3.debian.tar.xz 644192b0db24f0dc02beebe630c05744 6658 electronics optional simulavr_1.0.0+git20160221.e53413b-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYg8bsQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCP2KD/9vjsTJb0Qbv/xEW50vKbcZ/ZZ1GBQP/Nqx ihe4mUDKQpOXrbjPmioqWqNa8hA9bYFA5XpizQUG0CYa6/8YxETfvkljSREBMcSD 6CGjEw1wDd5xM3ObiJuBN7eKYt7wHYKu3SlwHymclp4YRfAkY5MgYE6yNHzVDZ+t lbaMlG5zI4OVXhta8P5QZtEhrutMQI6IGAVGf2DMsSh7g8zPT6olL+/WxYt7gv// 6pf6sJacnCuvhTRyc79Nod98cXLkpXTlhQjaGA4uWTvatYYjGGE7zI3UeqaE7oZU LFC6KTtB2vQzaD1RSaJT/oZtyVvSZZReQziBYoxVaZhv3QUuRjjI4i67smbPHgdy LCRPfrb75w8njEHmcOkDzHIkGIEvvUtM0X/dGNt
Bug#992887: marked as done (xball new upstream release)
Your message dated Wed, 17 Apr 2024 22:56:57 + with message-id and subject line Bug#992887: fixed in xball 3.0.1+dfsg-2 has caused the Debian Bug report #992887, regarding xball new upstream release 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.) -- 992887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xball Version: 3.0.1 New upstream release of orphaned Debian Package xball v3.0.1 located here: https://github.com/JoesCat/xball/releases/tag/v3.1.0 git repo located here: https://github.com/JoesCat/xball/ Note: lacking prior git or SVN history, this git repo is approximate, but not historically correct (as was) - the best I was able to do based on the existing Debian xball install files. More information here: https://lists.debian.org/debian-devel-games/2021/08/msg5.html Thanks, Joe --- End Message --- --- Begin Message --- Source: xball Source-Version: 3.0.1+dfsg-2 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of xball, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated xball 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, 18 Apr 2024 00:38:22 +0200 Source: xball Architecture: source Version: 3.0.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 992887 Changes: xball (3.0.1+dfsg-2) unstable; urgency=medium . * QA upload. . * Updated vcs in d/control to Salsa. * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 4.6.2 to 4.7.0. * Switched to new upstream project https://github.com/JoesCat/xball/. (Closes: #992887) * Flagged that source can build without root access in d/control. * Switched to debhelper compat level 13 and enabled hardening. Checksums-Sha1: 724fce8269f71d4555805329b6f3da1310b63a19 1879 xball_3.0.1+dfsg-2.dsc 43f17b7387cd6596e82304d053228a0d49863072 8812 xball_3.0.1+dfsg-2.debian.tar.xz d9c3a20ff2fb6ac68f19e152902ad5ffcc026ebd 8426 xball_3.0.1+dfsg-2_source.buildinfo Checksums-Sha256: 3071f67758168b2fd7283eca50b743afbfa6b4074e8739657d849a6a0e2ed44c 1879 xball_3.0.1+dfsg-2.dsc dc5722dc442ef002ac10beb2a76b9b48a39a43558f92ecc32365ce7f432bb811 8812 xball_3.0.1+dfsg-2.debian.tar.xz b1208ead431a2742ba2dc277f7aefbfd260797a81fe4a1f17fee1afebc4c3820 8426 xball_3.0.1+dfsg-2_source.buildinfo Files: d8dc173d84cf1145e2ab96f24d96f17b 1879 games optional xball_3.0.1+dfsg-2.dsc 2babb147cf41b7ed0840867e937c202e 8812 games optional xball_3.0.1+dfsg-2.debian.tar.xz f13c6ac02cd986bd16b643a52e1dea1e 8426 games optional xball_3.0.1+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYgT6AACgkQgSgKoIe6 +w4v2hAAtKdsQODj4+6DIcH8llz7Mal6B936kUrsMIKPdlswOWWqxFmNzzLDOVrm 4Jfm4mku5HnuFcgow0s8sCJY+UUYum8kRAl7lvml/hamVFQADO27ZADBk3JmPdEF +nU65/sFw9mwt7vZe/yHeh24YNdYnwqPVMjUlXginkUvnE8KiM1xAtlWGq1m9002 ZJQImma2/YHzYMIJin/iV6pTjWwcuPfuDf1+joP7PsceOMM34Oi5UzKxbgtSonGY bzcOElEHQ5aZHD7ZXnUUy2A58PpTovt77BGT1mIkdcxqw/grA9Ggo6fJ4hBWViy3 jV1if8lqBbQrEqPGyhwtaL5cKj9UtJ5VU0xwloGM6fGPKGxh05+uKgiXcufBDI3F FQsmdBDdklgZEVowhMNPQ2I80mt6vOpxdi502eIND006A3JMl5W/UVkwBGjdvAi0 dAqcLmF1owkQbu0aKdse35t6Bo3H/yh3cm5enajNnvo+zNCgMiT/Bj4mzRl1eSjc 0DFYtoYmdN1ToysNZTPAWnvAFtm1tVexsV1LQpkH54moB8tM21rbh9JTh6TPy62x RQkVI/Y4CsUnmbxQXJQyw5Tmz/HPd1soGia5j6tKHHUyxPklejVgZci9airDWWEa WUEQG9w2b8khCGdMHrhETOpIVqOzajnnopMGe2vbgoh2vgZv5gM= =hugp -END PGP SIGNATURE- pgpgRhUxQ_Ltj.pgp Description: PGP signature --- End Message ---
Processed: reopen
tps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890518 890638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890638 892136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892136 893961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893961 895427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895427 896967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896967 898959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898959 899013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899013 908513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908513 910785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910785 911859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911859 911897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911897 911962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911962 914619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914619 917242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917242 921387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921387 922925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922925 927426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927426 928953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928953 929942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929942 933271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933271 935182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 941743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941743 942052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942052 944354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944354 946545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946545 946592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946592 947612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947612 95: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95 956586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956586 959399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959399 964945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964945 965236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965236 968698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968698 969299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969299 969977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969977 971874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971874 974220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974220 974650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974650 975068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975068 977463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977463 977857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977857 977977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977977 983945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983945 986981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986981 987626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987626 993206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993206 997089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen bugs closed by dak
Processing commands for cont...@bugs.debian.org:
> reopen 640462
Bug #640462 {Done: Debian FTP Masters }
[libreoffice] libreoffice: default window appears partly off-screen
'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 4:24.2.3~rc1-1+rm.
> reopen 661818
Bug #661818 {Done: Debian FTP Masters }
[libreoffice] libreoffice: some menu icons are missing in KDE menu (but appear
in editor)
'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 4:24.2.3~rc1-1+rm.
> reopen 669064
Bug #669064 {Done: Debian FTP Masters }
[libreoffice-calc] libreoffice-calc: LibreOffice Calc is not shown in top
context menu of xlsx files like for xls files
'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 4:24.2.3~rc1-1+rm.
> reopen 708533
Bug #708533 {Done: Debian FTP Masters }
[libreoffice] libreoffice: connects to the print server (CUPS) when opening
some document
'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 4:24.2.3~rc1-1+rm.
> reopen 729936
Bug #729936 {Done: Debian FTP Masters }
[libreoffice-writer] libreoffice-writer: autotext and menu inserted fields
gives different values
'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 4:24.2.3~rc1-1+rm.
> reopen 754333
Bug #754333 {Done: Debian FTP Masters }
[libreoffice-common] libreoffice-common: junk output on rmdir in
libreoffice-common.postrm.in
Bug #883443 {Done: Debian FTP Masters }
[libreoffice-common] rmdir: failed to remove
'/var/lib/libreoffice/share/prereg/': No such file or directory
'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 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 772097
Bug #772097 {Done: Debian FTP Masters }
[libreoffice] libreoffice: LibreOffice sees only "Generic Printer"
'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 4:24.2.3~rc1-1+rm.
> reopen 776950
Bug #776950 {Done: Debian FTP Masters }
[libreoffice] libreoffice: Open LibreOffice Basic crash LibreOffice
'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 4:24.2.3~rc1-1+rm.
> reopen 804174
Bug #804174 {Done: Debian FTP Masters }
[libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work
Bug #812081 {Done: Debian FTP Masters }
[libreoffice] Keyboard shortcuts (Ctrl-Q etc.) do not work
'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 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 808754
Bug #808754 {Done: Debian FTP Masters }
[libreoffice] libreoffice: lightproof-en settings revert after each update
'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 4:24.2.3~rc1-1+rm.
> reopen 819577
Bug #819577 {Done: Debian FTP Masters }
[libreoffice-calc] libreoffice-calc: Crash after runtime error in LibreOffice
Basic after changing Code
'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 4:24.2.3~rc1-1+rm.
> reopen 820350
Bug #820350 {Done: Debian FTP Masters }
[libreoffice] libreoffice: Packaging LibreOfice Still for stable branch of the
Debian
Bug #914619 {Done: Debian FTP Masters }
[libreoffice] "LibreOffice Still" should be used by the stable distribution
'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 4:24.2.3~rc1-1+rm.
No longer marked as fixed in versions 4:24.2.3~rc1-1+rm.
> reopen 821401
Bug #821401 {Done: Debian FTP Masters }
[libreoffice-gtk3] libreoffice-gtk3: First [Ctrl+Scroll Down] after changing
focus to LO makes LO
Bug#1013601: marked as done (python-sshoot: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found)
Your message dated Wed, 17 Apr 2024 12:49:23 + with message-id and subject line Bug#1013601: fixed in python-sshoot 1.4.2-3 has caused the Debian Bug report #1013601, regarding python-sshoot: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found 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.) -- 1013601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-sshoot Version: 1.4.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > I: pybuild base:239: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/i18n.py -> /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/listing.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/manager.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/autocomplete.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/profile.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/main.py -> /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/config.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > copying sshoot/conftest.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot > creating /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/__init__.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_manager.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_config.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_listing.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_autocomplete.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > copying sshoot/tests/test_profile.py -> > /<>/.pybuild/cpython3_3.10/build/sshoot/tests > running egg_info > creating sshoot.egg-info > writing sshoot.egg-info/PKG-INFO > writing dependency_links to sshoot.egg-info/dependency_links.txt > writing entry points to sshoot.egg-info/entry_points.txt > writing requirements to sshoot.egg-info/requires.txt > writing top-level names to sshoot.egg-info/top_level.txt > writing manifest file 'sshoot.egg-info/SOURCES.txt' > reading manifest file 'sshoot.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE.txt' > writing manifest file 'sshoot.egg-info/SOURCES.txt' > creating /<>/.pybuild/cpython3_3.10/build/sshoot/locale > copying sshoot/locale/argparse.pot -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale > copying sshoot/locale/sshoot.pot -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale > creating /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT > creating > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/argparse.mo -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/argparse.po -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/sshoot.mo -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > copying sshoot/locale/it_IT/LC_MESSAGES/sshoot.po -> > /<>/.pybuild/cpython3_3.10/build/sshoot/locale/it_IT/LC_MESSAGES > register-python-argcomplete3 --shell bash sshoot \ > > debian/bash-completion > /bin/sh: 1: register-python-argcomplete3: not found > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 127 The full build log is available from: http://qa-logs.debian.net/2022/06/24/python-sshoot_1.4.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;user
Bug#908513: marked as done (libreoffice - missing gallery when Dmaths is installed)
Your message dated Wed, 17 Apr 2024 11:53:46 + with message-id and subject line Bug#1069123: Removed package(s) from experimental has caused the Debian Bug report #867591, regarding libreoffice - missing gallery when Dmaths is installed 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.) -- 867591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:6.1.1~rc1-2 Severity: normal Dear Maintainer, I think there is a litttle issue with the gallery in libreoffice. If the libreoffice-dmaths package is installed, then I can gent no access to the libreoffice-gallery. (Clicking on the "Gallery"-icon showes me the dmaths gallery). When libreoffice-dmaths is uninstralled, then the gallery (all pictures and so on) are appearng again. I looked into the settings of libreoffice and searched at Google and others, but could not find a solution, how to set the gallery-path to the "normal" gallery withj installed dmaths. I believe, this is a bug. If I am wrong, please point me to the right settings. Thanks for reading this and your help. Best regards Hans -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.17.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-avmedia-backend-gstreamer 1:6.1.1~rc1-2 ii libreoffice-avmedia-backend-vlc1:6.1.1~rc1-2 ii libreoffice-base 1:6.1.1~rc1-2 ii libreoffice-calc 1:6.1.1~rc1-2 ii libreoffice-core 1:6.1.1~rc1-2 ii libreoffice-draw 1:6.1.1~rc1-2 ii libreoffice-impress1:6.1.1~rc1-2 ii libreoffice-math 1:6.1.1~rc1-2 ii libreoffice-report-builder-bin 1:6.1.1~rc1-2 ii libreoffice-writer 1:6.1.1~rc1-2 ii python3-uno1:6.1.1~rc1-2 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu2.37-1 ii fonts-liberation1:1.07.4-7 ii fonts-liberation2 2.00.1-7 pn fonts-linuxlibertine ii fonts-noto-hinted 20171026-2 ii fonts-noto-mono 20171026-2 ii fonts-sil-gentium-basic 1.102-1 ii libreoffice-java-common 1:6.1.1~rc1-2 ii libreoffice-librelogo 1:6.1.1~rc1-2 ii libreoffice-nlpsolver 0.9+LibO6.1.1~rc1-2 ii libreoffice-ogltrans1:6.1.1~rc1-2 ii libreoffice-report-builder 1:6.1.1~rc1-2 ii libreoffice-script-provider-bsh 1:6.1.1~rc1-2 pn libreoffice-script-provider-js ii libreoffice-script-provider-python 1:6.1.1~rc1-2 ii libreoffice-sdbc-postgresql 1:6.1.1~rc1-2 ii libreoffice-wiki-publisher 1.2.0+LibO6.1.1~rc1-2 Versions of packages libreoffice suggests: ii cups-bsd 2.2.8-5 ii firefox-esr 60.2.0esr-1~deb9u2 ii ghostscript 9.22~dfsg-2.1 ii gnupg2.2.10-1 pn gpa ii gstreamer1.0-libav 1.15.0.1+git20180723+db823502-1 ii gstreamer1.0-plugins-bad 1.14.2-1 ii gstreamer1.0-plugins-base1.14.2-1 ii gstreamer1.0-plugins-good1.14.2-1 ii gstreamer1.0-plugins-ugly1.14.2-1 ii hunspell-de-at [hunspell-dictionary] 20161207-5 ii hunspell-de-ch [hunspell-dictionary] 20161207-5 ii hunspell-de-de [hunspell-dictionary] 20161207-5 ii hyphen-de [hyphen-hyphenation-patterns] 1:6.1.0~rc2-2 ii imagemagick 8:6.9.10.8+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.8+dfsg-1 pn libgl1 pn libreoffice-grammarcheck pn libreoffice-help ii libreoffice-kde5 1:6.1.1~rc1-2 pn libreoffice-l10n pn libreoffice-officebean pn libsane1
Bug#867591: marked as done (libreoffice-writer: bug or no bug? Libreoffice-dmath inhibits to open gallery in libreoffice-writer)
Your message dated Wed, 17 Apr 2024 11:53:46 + with message-id and subject line Bug#1069123: Removed package(s) from experimental has caused the Debian Bug report #867591, regarding libreoffice-writer: bug or no bug? Libreoffice-dmath inhibits to open gallery in libreoffice-writer 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.) -- 867591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-writer Version: 1:5.2.7-1 Severity: normal Dear Maintainer, don't know, if this is a bug or a user-mistake, but since the installation of libreoffice-dmath I can not open the normal gallery (with pictures). When I click on the "gallery" icon, then I get only mathematical symbols from dmath. Of course, I can deinstall libreoffice-dmath, but isn't there another way? I searched and searched and found none, to recall the piuctures in the gallery. I believe, this is a bug or maybe a missing option (switching between dmath and libreoffice) or I have something missed. It would be nice, if you could take a look at it, and if the error is on my side, please drop me a note and just close this bugreport. In case of my error: Sorry for the noise, in case of a bug, I would be happy if it can be fixed. Thank you very much for all the work, libreoffice is great! Best regards Hans -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-writer depends on: ii dpkg 1.18.24 ii libabw-0.1-1 0.1.1-4 ii libc6 2.24-12 ii libe-book-0.1-10.1.2-4 ii libetonyek-0.1-1 0.1.6-5 ii libgcc11:7.1.0-7 ii libicu57 57.1-6 ii libmwaw-0.3-3 0.3.11-3 ii libodfgen-0.1-10.1.6-2 ii libreoffice-base-core 1:5.2.7-1 ii libreoffice-core 1:5.2.7-1 ii librevenge-0.0-0 0.0.4-6 ii libstdc++6 7.1.0-7 ii libwpd-0.10-10 0.10.1-5 ii libwpg-0.3-3 0.3.1-3 ii libwps-0.4-4 0.4.6-2 ii libxml22.9.4+dfsg1-2.2+b1 ii uno-libs3 5.2.7-1 ii ure5.2.7-1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages libreoffice-writer recommends: ii libreoffice-math 1:5.2.7-1 Versions of packages libreoffice-writer suggests: ii default-jre [java5-runtime] 2:1.8-59 ii fonts-crosextra-caladea 20130214-1 ii fonts-crosextra-carlito 20130920-1 ii libreoffice-base 1:5.2.7-1 pn libreoffice-gcj ii libreoffice-java-common 1:5.2.7-1 ii openjdk-8-jre [java5-runtime] 8u131-b11-2 ii oracle-java8-jre [java5-runtime] 8u101 Versions of packages libreoffice-core depends on: ii fontconfig2.12.3-0.1 ii fonts-opensymbol 2:102.7+LibO5.2.7-1 ii libboost-date-time1.62.0 1.62.0+dfsg-4+b1 ii libc6 2.24-12 ii libcairo2 1.14.10-1 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.1+git20160603-3+b1 ii libcups2 2.2.3-2 ii libcurl3-gnutls 7.52.1-5 ii libdbus-1-3 1.10.20-1 ii libdbus-glib-1-2 0.108-2 ii libdconf1 0.26.0-2+b1 ii libeot0 0.01-4+b1 ii libexpat1 2.2.1-2 ii libexttextcat-2.0-0 3.4.4-2+b1 ii libfontconfig12.12.3-0.1 ii libfreetype6 2.8-0.2 ii libgcc1 1:7.1.0-7 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglew2.02.0.0-4 ii libglib2.0-0 2.52.3-1 ii libgltf-0.0-0v5 0.0.2-5 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgraphite2-31.3.10-2 ii libharfbuzz-icu0 1.4.2-1 ii libharfbuzz0b 1.4.2-1 ii libhunspell-1.4-0 1.4.1-2+b2 ii libhyphen02.8.8-5 ii libice6 2:1.0.9-2 ii libicu57 57.1-6 ii libjpeg62-turbo 1:1.5.1-2 ii liblangtag1 0.6.2-1 ii liblcms2-22.8-4 ii libldap-2.4-2 2.4.44+dfsg-7 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0
Bug#1066462: marked as done (dot-forward: FTBFS: control.c:65:41: error: implicit declaration of function ‘close’ [-Werror=implicit-function-declaration])
Your message dated Wed, 17 Apr 2024 09:49:19 +
with message-id
and subject line Bug#1066462: fixed in dot-forward 1:0.71-7
has caused the Debian Bug report #1066462,
regarding dot-forward: FTBFS: control.c:65:41: error: implicit declaration of
function ‘close’ [-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.)
--
1066462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dot-forward
Version: 1:0.71-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):
> make[1]: Entering directory '/<>'
> ( cat warn-auto.sh; \
> echo CC=\'`head -1 conf-cc`\'; \
> echo LD=\'`head -1 conf-ld`\' \
> ) > auto-ccld.sh
> nroff -man dot-forward.1 > dot-forward.0
> cat auto-ccld.sh make-load.sh > make-load
> cat auto-ccld.sh find-systype.sh > find-systype
> cat auto-ccld.sh make-compile.sh > make-compile
> cat auto-ccld.sh make-makelib.sh > make-makelib
> chmod 755 make-load
> chmod 755 find-systype
> chmod 755 make-compile
> chmod 755 make-makelib
> ./find-systype > systype
> ( cat warn-auto.sh; ./make-load "`cat systype`" ) > load
> ( cat warn-auto.sh; ./make-compile "`cat systype`" ) > \
> compile
> ( cat warn-auto.sh; ./make-makelib "`cat systype`" ) > \
> makelib
> chmod 755 load
> chmod 755 makelib
> chmod 755 compile
> ./compile dot-forward.c
> ./compile control.c
> ( ( ./compile tryvfork.c && ./load tryvfork ) >/dev/null \
> 2>&1 \
> && cat fork.h2 || cat fork.h1 ) > fork.h
> ./compile auto-str.c
> ./compile substdio.c
> ./compile substdi.c
> ./compile substdo.c
> ./compile subfderr.c
> control.c: In function ‘control_readline’:
> control.c:65:41: error: implicit declaration of function ‘close’
> [-Werror=implicit-function-declaration]
>65 | if (getln(,sa,,'\n') == -1) { close(fd); return -1; }
> | ^
> dot-forward.c: In function ‘run’:
> dot-forward.c:78:7: error: implicit declaration of function ‘pipe’
> [-Werror=implicit-function-declaration]
>78 | if (pipe(pi) == -1)
> | ^~~~
> dot-forward.c:81:19: error: implicit declaration of function ‘fork’
> [-Werror=implicit-function-declaration]
>81 | switch (child = fork()) {
> | ^~~~
> dot-forward.c:85:7: error: implicit declaration of function ‘close’
> [-Werror=implicit-function-declaration]
>85 | close(pi[1]);
> | ^
> dot-forward.c:86:11: error: implicit declaration of function ‘fd_move’
> [-Werror=implicit-function-declaration]
>86 | if (fd_move(0,pi[0]) == -1)
> | ^~~
> dot-forward.c:89:7: error: implicit declaration of function ‘sig_pipedefault’
> [-Werror=implicit-function-declaration]
>89 | sig_pipedefault();
> | ^~~
> dot-forward.c:90:7: error: implicit declaration of function ‘execv’
> [-Werror=implicit-function-declaration]
>90 | execv(*args,args);
> | ^
> auto-str.c:8:6: warning: conflicting types for built-in function ‘puts’;
> expected ‘int(const char *)’ [-Wbuiltin-declaration-mismatch]
> 8 | void puts(s)
> | ^~~~
> auto-str.c:4:1: note: ‘puts’ is declared in header ‘’
> 3 | #include "exit.h"
> +++ |+#include
> 4 |
> dot-forward.c: In function ‘readcontrols’:
> dot-forward.c:141:7: error: implicit declaration of function ‘chdir’
> [-Werror=implicit-function-declaration]
> 141 | if (chdir(auto_qmail) == -1)
> | ^
> dot-forward.c:160:7: error: implicit declaration of function ‘fchdir’
> [-Werror=implicit-function-declaration]
> 160 | if (fchdir(fddir) == -1)
> | ^~
> dot-forward.c: In function ‘gotaddr’:
> dot-forward.c:189:12: error: implicit declaratio
Bug#738086: marked as done (xvier: please provide a desktop file and icons)
Your message dated Tue, 16 Apr 2024 20:45:15 + with message-id and subject line Bug#738086: fixed in xvier 1.0-10 has caused the Debian Bug report #738086, regarding xvier: please provide a desktop file and icons 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.) -- 738086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xvier Version: 1.0-7.5 Severity: wishlist User: pkg-games-de...@lists.alioth.debian.org Usertags: desktop-integration goals not-gamesteam Dear maintainer, currently xvier does not supply a desktop file and no desktop and menu icons. Hence the game is not well integrated into the user's desktop environment. Please consider helping to improve the desktop integration of games in Debian. https://wiki.debian.org/Games/JessieReleaseGoal Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: xvier Source-Version: 1.0-10 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of xvier, 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 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated xvier 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: Tue, 16 Apr 2024 22:01:35 +0200 Source: xvier Architecture: source Version: 1.0-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 275470 738086 Changes: xvier (1.0-10) unstable; urgency=medium . * QA upload. . * Acknowledge NMU (Closes: #275470). * Updated vcs in d/control to Salsa. * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.8.3 to 4.7.0. * Removed useless postinst and postrm scripts. * Added XDG desktop menu entry (Closes: #738086). Checksums-Sha1: e1a7eb7b9844c97bd05db158cfe4ba5ece779827 1750 xvier_1.0-10.dsc a1e228079f100677d7dfbe1d847b9127c86572f9 3808 xvier_1.0-10.debian.tar.xz 23f63e9c76247ea40d8f992d727d6cba63ca7a4a 5544 xvier_1.0-10_source.buildinfo Checksums-Sha256: 29b8b341fdd5e6721570941847b37a701335af9b2be8d91e507ae3523bec0f3b 1750 xvier_1.0-10.dsc edf4f56621a06fb90b456e95ad9340cb5669a952f44d6e1af77534d11757bbef 3808 xvier_1.0-10.debian.tar.xz 840a0e4d4c26b01dc2f7802392f18e46a34a105f933eafc3c6ee3b9c7f71935e 5544 xvier_1.0-10_source.buildinfo Files: 6ea519b32f7227b9cbc0c56f8480c5ac 1750 games optional xvier_1.0-10.dsc a14a9bfea32ed1970dd2356aa2c7133d 3808 games optional xvier_1.0-10.debian.tar.xz e1d61187ca7722ea57cb1429fd830e9e 5544 games optional xvier_1.0-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYe2Z8ACgkQgSgKoIe6 +w6hPg/8CuUS2vzyCvz8jc2nk5+3H8wxoPlv/d5kvZdu8LX6q1F3jnokDX5SfuiW Lnn8P0a6JkUcYSvQiG3k44HvpaPEfNsWD7zB1LTjWaHCapGFUR+Od/dMLLW/VcYE PoANuSqBmxdqGOR2lPMKdsq9ZUTXJn27U0uqOWYP360m5AD/kGscAcMS20BFVZEF gl/k5SKVYfEFZd2+TcF04ME6tg/G5F84nHdZnsD9Qy/pmmTO3ULjI4kMkg9DySdD HKueLwA2rBPRBE2qpsC/HozpBKA62dHFrGM5WaYD4vmtqlS13ai91QaoSOxkirfQ vHtDDkJ3z+qqH+9Bug9aO69BTRyA4kSQL/ttFFnXBTDiDQBCv7QC3cFTdKe7FBXi ZzHFnqg5bpeFLQEeG8sgM5832FF96xT2SRdndBMaRkJOIUKxtvXm91+xndc+h+E/ lElTBjUx6wsVfn5pDCaDr6rNf5eNIwHuJT8x0Qg4uOtAKZwfeoSPEV7Ixu1L9YYg VaThRWxBvhwdT40h1JqoMsJ3Z6vyQK3C33JIJmnZDm2CwWHaBj39JFKV4LoPf+Wi 4aGqgECziDM6kgyx9H/yklRihPVvG0aD/VxJwQRxeQoW9L3BcfLrnqfwBHP03gjO Q4l9GqJ+9LNkM5Ck86+LtEtB8LSr3HZtBhng5acQDXxijQxup/o= =192z -END PGP SIGNATURE- pgpvkchSKDPcK.pgp Description: PGP signature --- End Message ---
Bug#275470: marked as done (NMU diff for 1.0-7.1)
Your message dated Tue, 16 Apr 2024 20:45:15 + with message-id and subject line Bug#275470: fixed in xvier 1.0-10 has caused the Debian Bug report #275470, regarding NMU diff for 1.0-7.1 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.) -- 275470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xvier Tags: patch The NMU diff for the 1.0-7.1 NMU is available on http://err.no/patches/xvier_1.0-7.1.NMU.diff -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- --- End Message --- --- Begin Message --- Source: xvier Source-Version: 1.0-10 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of xvier, 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 275...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated xvier 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: Tue, 16 Apr 2024 22:01:35 +0200 Source: xvier Architecture: source Version: 1.0-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 275470 738086 Changes: xvier (1.0-10) unstable; urgency=medium . * QA upload. . * Acknowledge NMU (Closes: #275470). * Updated vcs in d/control to Salsa. * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.8.3 to 4.7.0. * Removed useless postinst and postrm scripts. * Added XDG desktop menu entry (Closes: #738086). Checksums-Sha1: e1a7eb7b9844c97bd05db158cfe4ba5ece779827 1750 xvier_1.0-10.dsc a1e228079f100677d7dfbe1d847b9127c86572f9 3808 xvier_1.0-10.debian.tar.xz 23f63e9c76247ea40d8f992d727d6cba63ca7a4a 5544 xvier_1.0-10_source.buildinfo Checksums-Sha256: 29b8b341fdd5e6721570941847b37a701335af9b2be8d91e507ae3523bec0f3b 1750 xvier_1.0-10.dsc edf4f56621a06fb90b456e95ad9340cb5669a952f44d6e1af77534d11757bbef 3808 xvier_1.0-10.debian.tar.xz 840a0e4d4c26b01dc2f7802392f18e46a34a105f933eafc3c6ee3b9c7f71935e 5544 xvier_1.0-10_source.buildinfo Files: 6ea519b32f7227b9cbc0c56f8480c5ac 1750 games optional xvier_1.0-10.dsc a14a9bfea32ed1970dd2356aa2c7133d 3808 games optional xvier_1.0-10.debian.tar.xz e1d61187ca7722ea57cb1429fd830e9e 5544 games optional xvier_1.0-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYe2Z8ACgkQgSgKoIe6 +w6hPg/8CuUS2vzyCvz8jc2nk5+3H8wxoPlv/d5kvZdu8LX6q1F3jnokDX5SfuiW Lnn8P0a6JkUcYSvQiG3k44HvpaPEfNsWD7zB1LTjWaHCapGFUR+Od/dMLLW/VcYE PoANuSqBmxdqGOR2lPMKdsq9ZUTXJn27U0uqOWYP360m5AD/kGscAcMS20BFVZEF gl/k5SKVYfEFZd2+TcF04ME6tg/G5F84nHdZnsD9Qy/pmmTO3ULjI4kMkg9DySdD HKueLwA2rBPRBE2qpsC/HozpBKA62dHFrGM5WaYD4vmtqlS13ai91QaoSOxkirfQ vHtDDkJ3z+qqH+9Bug9aO69BTRyA4kSQL/ttFFnXBTDiDQBCv7QC3cFTdKe7FBXi ZzHFnqg5bpeFLQEeG8sgM5832FF96xT2SRdndBMaRkJOIUKxtvXm91+xndc+h+E/ lElTBjUx6wsVfn5pDCaDr6rNf5eNIwHuJT8x0Qg4uOtAKZwfeoSPEV7Ixu1L9YYg VaThRWxBvhwdT40h1JqoMsJ3Z6vyQK3C33JIJmnZDm2CwWHaBj39JFKV4LoPf+Wi 4aGqgECziDM6kgyx9H/yklRihPVvG0aD/VxJwQRxeQoW9L3BcfLrnqfwBHP03gjO Q4l9GqJ+9LNkM5Ck86+LtEtB8LSr3HZtBhng5acQDXxijQxup/o= =192z -END PGP SIGNATURE- pgp3BPKwsnhqZ.pgp Description: PGP signature --- End Message ---
Bug#1047646: marked as done (pam-ssh-agent-auth: Fails to build source after successful build)
Your message dated Tue, 16 Apr 2024 21:42:13 +0200 with message-id and subject line [Debian FTP Masters] Accepted pam-ssh-agent-auth 0.10.3-8 (source) into unstable has caused the Debian Bug report #1047646, regarding pam-ssh-agent-auth: Fails to build source after successful build 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.) -- 1047646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pam-ssh-agent-auth Version: 0.10.3-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > > > dpkg-buildpackage: info: source package pam-ssh-agent-auth > dpkg-buildpackage: info: source version 0.10.3-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Marcos Talau > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_auto_clean > dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > make -j1 distclean > make[1]: Entering directory '/<>' > if [ -f regress/Makefile ] && [ -r regress/Makefile ]; then \ > (cd regress && make clean) \ > fi > rm -f *.o *.a pam_ssh_agent_auth.so logintest config.cache config.log > rm -f *.out core > rm -f Makefile config.h config.status > rm -f openbsd-compat/regress/Makefile *~ > rm -rf autom4te.cache > rm -f pam_ssh_agent_auth.8 > (cd openbsd-compat && make distclean) > make[2]: Entering directory '/<>/openbsd-compat' > rm -f *.o *.a core > rm -f Makefile *~ > make[2]: Leaving directory '/<>/openbsd-compat' > if test -d pkg ; then \ > rm -fr pkg ; \ > fi > make[1]: Leaving directory '/<>' >dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in > use) > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pam-ssh-agent-auth using existing > ./pam-ssh-agent-auth_0.10.3.orig.tar.bz2 > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: error: cannot represent change to ed25519-donna/ed25519.o: > binary file contents changed > dpkg-source: error: add ed25519-donna/ed25519.o in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/pam-ssh-agent-auth_0.10.3-4_unstable.log 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: 0.10.3-8 This issue was fixed with the latest upload, but I forgot to close the bug. Start of forwarded message From: Debian FTP Masters To: debian-devel-chan...@lists.debian.org Subject: Accepted pam-ssh-agent-auth 0.10.3-8 (source) into unstable Date: Tue, 16 Apr 2024 18:52:14 + -BEGIN PGP SIGNED MESSAGE- Ha
Processed: tagging 1061212
Processing commands for cont...@bugs.debian.org: > tags 1061212 + upstream fixed-upstream Bug #1061212 [src:emscripten] Please upgrade to llvm-toolchain-17 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958135: marked as done (dvi2dvi FTCBFS: strips with the build architecture strip)
Your message dated Tue, 16 Apr 2024 19:04:22 +
with message-id
and subject line Bug#958135: fixed in dvi2dvi 2.0alpha-11
has caused the Debian Bug report #958135,
regarding dvi2dvi FTCBFS: strips with the build architecture strip
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.)
--
958135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvi2dvi
Version: 2.0alpha-10
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
dvi2dvi fails to cross build from source, because the upstream Makefile
strips during make install using the build architecture strip via
install -s. Beyond breaking cross compilation, doing so breaks
DEB_BUILD_OPTIONS=nostrip as well as generation of -dbgsym packages.
Please consider applying the attached patch to skip such stripping and
defer it to dh_strip.
Helmut
diff --minimal -Nru dvi2dvi-2.0alpha/debian/changelog
dvi2dvi-2.0alpha/debian/changelog
--- dvi2dvi-2.0alpha/debian/changelog 2017-01-14 09:35:54.0 +0100
+++ dvi2dvi-2.0alpha/debian/changelog 2020-04-18 21:42:07.0 +0200
@@ -1,3 +1,9 @@
+dvi2dvi (2.0alpha-11) UNRELEASED; urgency=medium
+
+ * Fix FTCBFS: Defer stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne Sat, 18 Apr 2020 21:42:07 +0200
+
dvi2dvi (2.0alpha-10) unstable; urgency=medium
* QA upload
diff --minimal -Nru dvi2dvi-2.0alpha/debian/patches/cross.patch
dvi2dvi-2.0alpha/debian/patches/cross.patch
--- dvi2dvi-2.0alpha/debian/patches/cross.patch 1970-01-01 01:00:00.0
+0100
+++ dvi2dvi-2.0alpha/debian/patches/cross.patch 2020-04-18 21:41:36.0
+0200
@@ -0,0 +1,11 @@
+--- dvi2dvi-2.0alpha.orig/Makefile
dvi2dvi-2.0alpha/Makefile
+@@ -81,7 +81,7 @@
+ install: install-dvi2dvi
+
+ install-dvi2dvi: dvi2dvi
+- install -s -m 755 dvi2dvi ${BINAREA}/dvi2dvi
++ $(INSTALL) -s -m 755 dvi2dvi ${BINAREA}/dvi2dvi
+
+ install-lib:
+ -mkdir ${DVI2LIB}
diff --minimal -Nru dvi2dvi-2.0alpha/debian/patches/series
dvi2dvi-2.0alpha/debian/patches/series
--- dvi2dvi-2.0alpha/debian/patches/series 2017-01-14 09:35:54.0
+0100
+++ dvi2dvi-2.0alpha/debian/patches/series 2020-04-18 21:41:22.0
+0200
@@ -8,3 +8,4 @@
pass-flags-hardening-build.patch
dont-overwrite-prototypes.patch
fix-printf-usage.patch
+cross.patch
diff --minimal -Nru dvi2dvi-2.0alpha/debian/rules dvi2dvi-2.0alpha/debian/rules
--- dvi2dvi-2.0alpha/debian/rules 2017-01-14 09:35:54.0 +0100
+++ dvi2dvi-2.0alpha/debian/rules 2020-04-18 21:42:02.0 +0200
@@ -13,5 +13,5 @@
override_dh_auto_install:
- dh_auto_install
+ dh_auto_install -- INSTALL='install --strip-program=true'
$(MAKE) install-lib DESTDIR=$(CURDIR)/debian/dvi2dvi
--- End Message ---
--- Begin Message ---
Source: dvi2dvi
Source-Version: 2.0alpha-11
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
dvi2dvi, 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 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated dvi2dvi 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: Tue, 16 Apr 2024 20:50:15 +0200
Source: dvi2dvi
Architecture: source
Version: 2.0alpha-11
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 958135 1066297
Changes:
dvi2dvi (2.0alpha-11) unstable; urgency=medium
.
[ Andreas Beckmann ]
* QA upload.
* Import package history into GIT.
* Fix building with -Werror=implicit-function-declaration.
(Closes: #1066297)
* Declare Rules-Requires-Root: no.
.
[ Helmut Grohne ]
* Fix FTCBFS: Defer stripping to dh_strip. (Closes: #958135)
Checksums-Sha1:
709b11fb451f04a006ee9b458ba77d1fea0547bd 1898 dvi2dvi_2.0alpha-11.dsc
644bb443448734f918a61b4310f3d75af4e360bc 12340
dvi2dvi_2.0alpha-11.debian.tar.xz
0723d66076dc48d5606ee5cea1396a3725b3910f 5734
dvi2dvi_2.0alpha-11_source.buildinfo
Checksums-Sha256:
a9a58fa8fa6e3786c3e22269380710ce6fc0945e1c7b29be39e0b311c550c7f9
Bug#1066297: marked as done (dvi2dvi: FTBFS: fontcom.c:45:9: error: implicit declaration of function ‘replfont’ [-Werror=implicit-function-declaration])
Your message dated Tue, 16 Apr 2024 19:04:22 +
with message-id
and subject line Bug#1066297: fixed in dvi2dvi 2.0alpha-11
has caused the Debian Bug report #1066297,
regarding dvi2dvi: FTBFS: fontcom.c:45:9: error: implicit declaration of
function ‘replfont’ [-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.)
--
1066297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvi2dvi
Version: 2.0alpha-10
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 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g
> -DPOSIX -DANSI -I/usr/include -DKPATHSEA -Wdate-time -D_FORTIFY_SOURCE=2 -c
> -o dconv.o dconv.c
> fontcom.c: In function ‘get_font_entry’:
> fontcom.c:45:9: error: implicit declaration of function ‘replfont’
> [-Werror=implicit-function-declaration]
>45 | if (replfont(n, s, rn, , )) {
> | ^~~~
> fontcom.c: At top level:
> fontcom.c:100:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 100 | first_markchar(fe, c)
> | ^~
> fontcom.c:150:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 150 | null_markchar(fe, c)
> | ^
> fontcom.c:178:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 178 | null_setchar(c)
> | ^~~~
> dfdcom.c:41:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>41 | dfd_dirkeep()
> | ^~~
> fontcom.c:185:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 185 | null_setstring(s, len)
> | ^~
> dfdcom.c: In function ‘dfd_movedown’:
> dfdcom.c:139:5: error: implicit declaration of function ‘dev_move’
> [-Werror=implicit-function-declaration]
> 139 | dev_move(a, n, command-n);
> | ^~~~
> dvi2.c:104:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 104 | main(argc, argv)
> | ^~~~
> dvi2.c: In function ‘main’:
> dvi2.c:119:21: error: implicit declaration of function ‘getenv’
> [-Werror=implicit-function-declaration]
> 119 | if ((dvi2path = getenv(DVI2PATHENV)) == NULL)
> | ^~
> dvi2.c:8:1: note: ‘getenv’ is defined in header ‘’; did you forget
> to ‘#include ’?
> 7 | #include
> +++ |+#include
> 8 | #endif
> dvi2.c:119:19: warning: assignment to ‘char *’ from ‘int’ makes pointer from
> integer without a cast [-Wint-conversion]
> 119 | if ((dvi2path = getenv(DVI2PATHENV)) == NULL)
> | ^
> dvi2.c:124:18: warning: assignment to ‘char *’ from ‘int’ makes pointer from
> integer without a cast [-Wint-conversion]
> 124 | if ((dvi2lib = getenv(DVI2LIBENV)) == NULL)
> | ^
> dvi2.c:129:23: warning: assignment to ‘char *’ from ‘int’ makes pointer from
> integer without a cast [-Wint-conversion]
> 129 | if ((fontdescfile = getenv(FONTDESCENV)) == NULL)
> | ^
> dfdcom.c: In function ‘dfd_movedown_v’:
> dfdcom.c:149:5: error: implicit declaration of function ‘dev_makemove’
> [-Werror=implicit-function-declaration]
> 149 | dev_makemove(-l, RIGHT1-1);
> | ^~~~
> dfdcom.c: In function ‘dfd_setrule’:
> dfdcom.c:175:5: error: implicit declaration of function ‘dev_setrule’; did
> you mean ‘dfd_setrule’? [-Werror=implicit-function-declaration]
> 175 | dev_setrule(makeint(a, 4), makeint(b, 4), command);
> | ^~~
> | dfd_setrule
> dvi2.c:134:5: error: implicit declaration of function ‘init_default’
> [-Werror=implicit-function-declaration]
> 134 | init_default(KPSENAME);
> | ^~~~
> dfdcom.c: In function ‘d_setrule_v’:
> dfdcom.c:188:13: error: implicit declaration of
Bug#1065069: marked as done (apt-move rebuilt with the wrong ABI on 32-bit architectures)
Your message dated Tue, 16 Apr 2024 21:02:22 +0200 with message-id and subject line Re: apt-move rebuilt with the wrong ABI on 32-bit architectures has caused the Debian Bug report #1065069, regarding apt-move rebuilt with the wrong ABI on 32-bit architectures 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.) -- 1065069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apt-move Version: 4.2.27-6+b1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org apt-move has been binNMUed for the time64_t transition. However due to the lack of extra-depends and the impossibility to recreate chroots on the buildd, it has been built with pre time64_t version of dpkg and gcc-13, probably leading to the wrong ABI. See for instance: https://buildd.debian.org/status/fetch.php?pkg=apt-move=armel=4.2.27-6%2Bb1=1709156067=0 --- End Message --- --- Begin Message --- On Thu, 29 Feb 2024 12:15:53 +0100 Aurelien Jarno wrote: apt-move has been binNMUed for the time64_t transition. However due to the lack of extra-depends and the impossibility to recreate chroots on the buildd, it has been built with pre time64_t version of dpkg and gcc-13, probably leading to the wrong ABI. See for instance: https://buildd.debian.org/status/fetch.php?pkg=apt-move=armel=4.2.27-6%2Bb1=1709156067=0 binNMUed again. Andreas--- End Message ---
Bug#1008675: marked as done (pam-ssh-agent-auth: Replace MD5 key fingerprints with SHA256 fingerprints as printed by ssh-keygen -l)
Your message dated Tue, 16 Apr 2024 18:52:14 +
with message-id
and subject line Bug#1008675: fixed in pam-ssh-agent-auth 0.10.3-8
has caused the Debian Bug report #1008675,
regarding pam-ssh-agent-auth: Replace MD5 key fingerprints with SHA256
fingerprints as printed by ssh-keygen -l
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.)
--
1008675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pam-ssh-agent-auth
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/fingerprint_sha256.patch: Use SHA256 with base64
encoding for key fingerprints. MD5 fingerprints are deprecated,
OpenSSH has switched to SHA256 since OpenSSH 6.8.
This will make the fingerprints compatible with ssh-keygen -l and allow
the package to work in FIPS mode. (LP: #1964486)
Thanks for considering the patch.
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy
APT policy: (1001, 'jammy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-23-generic (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
diff -Nru pam-ssh-agent-auth-0.10.3/debian/patches/fingerprint_sha256.patch
pam-ssh-agent-auth-0.10.3/debian/patches/fingerprint_sha256.patch
--- pam-ssh-agent-auth-0.10.3/debian/patches/fingerprint_sha256.patch
1970-01-01 01:00:00.0 +0100
+++ pam-ssh-agent-auth-0.10.3/debian/patches/fingerprint_sha256.patch
2022-03-17 15:31:12.0 +0100
@@ -0,0 +1,116 @@
+Description: Switch key fingerprint hash algorithm from MD5 to SHA256.
+ Use the newer base64 encoding format introduced in OpenSSH 6.8 to produce
+ fingerprints compatible with ssh-keygen -l.
+Forwarded: yes
+Bug: https://github.com/jbeverly/pam_ssh_agent_auth/pull/37
+Bug-Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486
+Author: Tobias Heider
+
+Index: pam-ssh-agent-auth-0.10.3/key.c
+===
+--- pam-ssh-agent-auth-0.10.3.orig/key.c
pam-ssh-agent-auth-0.10.3/key.c
+@@ -281,11 +281,8 @@ pamsshagentauth_key_fingerprint_raw(cons
+ *dgst_raw_length = 0;
+
+ switch (dgst_type) {
+- case SSH_FP_MD5:
+- md = EVP_md5();
+- break;
+- case SSH_FP_SHA1:
+- md = EVP_sha1();
++ case SSH_FP_SHA256:
++ md = EVP_sha256();
+ break;
+ default:
+ pamsshagentauth_fatal("key_fingerprint_raw: bad digest type %d",
+@@ -338,6 +335,31 @@ pamsshagentauth_key_fingerprint_raw(cons
+ }
+
+ static char *
++key_fingerprint_b64(const char *alg, u_char *dgst_raw, size_t dgst_raw_len)
++{
++ char *ret;
++ size_t plen = strlen(alg) + 1;
++ size_t rlen = ((dgst_raw_len + 2) / 3) * 4 + plen + 1;
++ int r;
++
++ if (dgst_raw_len > 65536 || (ret = calloc(1, rlen)) == NULL)
++ return NULL;
++ pamsshagentauth_strlcpy(ret, alg, rlen);
++ pamsshagentauth_strlcat(ret, ":", rlen);
++ if (dgst_raw_len == 0)
++ return ret;
++ if ((r = pamsshagentauth___b64_ntop(dgst_raw, dgst_raw_len,
++ ret + plen, rlen - plen)) == -1) {
++ explicit_bzero(ret, rlen);
++ free(ret);
++ return NULL;
++ }
++ /* Trim padding characters from end */
++ ret[strcspn(ret, "=")] = '\0';
++ return ret;
++}
++
++static char *
+ key_fingerprint_hex(u_char *dgst_raw, u_int dgst_raw_len)
+ {
+ char *retval;
+@@ -405,6 +427,7 @@ key_fingerprint_bubblebabble(u_char *dgs
+ char *
+ pamsshagentauth_key_fingerprint(const Key *k, enum fp_type dgst_type, enum
fp_rep dgst_rep)
+ {
++ const char *dgst_name;
+ char *retval = NULL;
+ u_char *dgst_raw;
+ u_int dgst_raw_len;
+@@ -416,6 +439,16 @@ pamsshagentauth_key_fingerprint(const Ke
+ case SSH_FP_HEX:
+ retval = key_fingerprint_hex(dgst_raw, dgst_raw_len);
+ break;
++ case SSH_FP_BASE64:
++ switch (dgst_type) {
++ case SSH_FP_SHA256:
++ dgst_name = "SHA256";
++ break;
++
Bug#1054828: marked as done (propellor: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)
Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id
and subject line Bug#1054828: fixed in propellor 5.17-1
has caused the Debian Bug report #1054828,
regarding propellor: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153:
configure-ghc-stamp] Error 25
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.)
--
1054828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-propellor-doc.substvars
> dh_installdirs -plibghc-propellor-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/0XPnzc0se_ -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-propellor-dev
> libghc-propellor-doc
> libghc-propellor-prof
> propellor
> Running dh_listpackages
> libghc-propellor-dev
> libghc-propellor-doc
> libghc-propellor-prof
> propellor
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/propellor-5.13/ --datasubdir=propellor
> --htmldir=/usr/share/doc/libghc-propellor-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring propellor-5.13...
> Flags chosen: withtypeerrors=True
> CallStack (from HasCallStack):
> withMetadata, called at
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Duplicate modules in library: Utility.Scheduled
>
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/propellor_5.13-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=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
Bug#1054640: marked as done (propellor: FTBFS with ghc 9.4: Not in scope: type constructor or class `UserEntry')
Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id
and subject line Bug#1054640: fixed in propellor 5.17-1
has caused the Debian Bug report #1054640,
regarding propellor: FTBFS with ghc 9.4: Not in scope: type constructor or
class `UserEntry'
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.)
--
1054640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
propellor FTBFS with ghc 9.4 (it still builds fine with 9.0 in testing):
https://salsa.debian.org/debian/propellor/-/jobs/4840519
[139 of 180] Compiling Utility.UserInfo ( src/Utility/UserInfo.hs,
dist-ghc/build/Utility/UserInfo.o, dist-ghc/build/Utility/UserInfo.dyn_o )
src/Utility/UserInfo.hs:57:23: error:
Not in scope: type constructor or class `UserEntry'
|
57 | myVal :: [String] -> (UserEntry -> String) -> IO (Either String String)
| ^
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 880.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build
--builddir=dist-ghc returned exit"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 610
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 473
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build",
"--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: propellor
Source-Version: 5.17-1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
propellor, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated propellor 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: Tue, 16 Apr 2024 19:17:26 +0200
Source: propellor
Architecture: source
Version: 5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1045437 1049841 1053981 1054640 1054828
Changes:
propellor (5.17-1) unstable; urgency=medium
.
* QA upload.
* New upstream release. (Closes: #1054640, #1053981, #1054828)
* Clean more build artefacts. (Closes: #1045437, #1049841)
Checksums-Sha1:
92a0775bcb34c479323628f90a690fde2d970e6c 3094 propellor_5.17-1.dsc
be0ceea30e7f191116fa6c77b7e32462b07703b4 738024 propellor_5.17.orig.tar.xz
b4100815057fc23ea29552df6790f43f9f17e76e 31624 propellor_5.17-1.debian.tar.xz
b64211982b6779f77c8d6bbc2f71af4ad5022557 9447 propellor_5.17-1_source.buildinfo
Checksums-Sha256:
05a91a2363c5d7b1e4f3da4321df87a7e0b01090a724b72707cdb558382e07b5 3094
propellor_5.17-1.dsc
96464166ff001bfaee15d5b61ef8632f1d99d41aefb456235c79b2a1e9750c21 738024
propellor_5.17.orig.tar.xz
ea519b43a535f37fd0785ea37343f14fa80d2f38e004f7f14c04a31fb8ce43b8 31624
propellor_5.17-1.debian.tar.xz
93a23f9df334eed7b74e7dfeba5fb667d3b8a1d776ae70f864ebc0bfbfbc0e9e 9447
propellor_5.17-1_source.buildinfo
Files:
bead5eeada71c5c0cc332fe0019df022 3094 admin optional propellor_5.17-1.dsc
dfc06b5a7c3b26cc7ea652e4e39aa6fc 738024 admin optional
propellor_5.17.orig.tar.xz
9c9fc0b925adca76ee45b112eb0490a8 31624 admin optional
propellor_5.17-1.debian.tar.xz
6b70f9989ace95892ec7f98fb0771785 9447 admin optional
propellor_5.17-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYes1gQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCI3IEACxajhlAJfJSVowmKk9Sys8pGOuX+dZ1Cxv
OvOOkF5wVVEk2GkVE85K64zb9k
Bug#1053981: marked as done (propellor: Needs a sourceful upload to support haddock interface 41)
Your message dated Tue, 16 Apr 2024 17:35:28 + with message-id and subject line Bug#1053981: fixed in propellor 5.17-1 has caused the Debian Bug report #1053981, regarding propellor: Needs a sourceful upload to support haddock interface 41 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.) -- 1053981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: propellor Version: 5.13-3 Severity: serious This package needs a sourceful upload to rebuild libghc-propellor-doc against interface 41. -- Ilias --- End Message --- --- Begin Message --- Source: propellor Source-Version: 5.17-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of propellor, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated propellor 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: Tue, 16 Apr 2024 19:17:26 +0200 Source: propellor Architecture: source Version: 5.17-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1045437 1049841 1053981 1054640 1054828 Changes: propellor (5.17-1) unstable; urgency=medium . * QA upload. * New upstream release. (Closes: #1054640, #1053981, #1054828) * Clean more build artefacts. (Closes: #1045437, #1049841) Checksums-Sha1: 92a0775bcb34c479323628f90a690fde2d970e6c 3094 propellor_5.17-1.dsc be0ceea30e7f191116fa6c77b7e32462b07703b4 738024 propellor_5.17.orig.tar.xz b4100815057fc23ea29552df6790f43f9f17e76e 31624 propellor_5.17-1.debian.tar.xz b64211982b6779f77c8d6bbc2f71af4ad5022557 9447 propellor_5.17-1_source.buildinfo Checksums-Sha256: 05a91a2363c5d7b1e4f3da4321df87a7e0b01090a724b72707cdb558382e07b5 3094 propellor_5.17-1.dsc 96464166ff001bfaee15d5b61ef8632f1d99d41aefb456235c79b2a1e9750c21 738024 propellor_5.17.orig.tar.xz ea519b43a535f37fd0785ea37343f14fa80d2f38e004f7f14c04a31fb8ce43b8 31624 propellor_5.17-1.debian.tar.xz 93a23f9df334eed7b74e7dfeba5fb667d3b8a1d776ae70f864ebc0bfbfbc0e9e 9447 propellor_5.17-1_source.buildinfo Files: bead5eeada71c5c0cc332fe0019df022 3094 admin optional propellor_5.17-1.dsc dfc06b5a7c3b26cc7ea652e4e39aa6fc 738024 admin optional propellor_5.17.orig.tar.xz 9c9fc0b925adca76ee45b112eb0490a8 31624 admin optional propellor_5.17-1.debian.tar.xz 6b70f9989ace95892ec7f98fb0771785 9447 admin optional propellor_5.17-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYes1gQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCI3IEACxajhlAJfJSVowmKk9Sys8pGOuX+dZ1Cxv OvOOkF5wVVEk2GkVE85K64zb9kUIf+71pgMPQSt64K7dgu5CkZtBTkUCNEX/jk7x 4ItUmcIdYaTEvlYDx2TB/C2FqsJlizbdhiPZpvJUijhFJwBmi5LNvfHXR1AYNO6X n2pA47Nc1gsLq2jraN2JUCu4c+9e8AXcZ3cSmMtQO0JwjakOOLSuSqTFQOt5kqmr gRVFZqsl3KgaIMYA+FJkVXqW1uV5k46dN5WnCnIxn7OuRGqV0KBVoFddoSBZT+XO zfc1WJUtoTOxhCZbUlnzI0L5Ic1niUiLOWEG2HYK3n08jJv+XJJ18/rNepzjygJn JzQ//iH56F58Ocoi+Tjj/JkBnbw1wvgCVik2HeXcnYJphwLKVG61nSAGdTSP7Shv EYxbV4k+JlF3o/FMaO/NuKwCXhx/Tgxtl09Lu4cKYyjUdVr/kubJsNksPFcLUDUL YWZibk3x3bEj1udHfJmv9Cnr7P6ruaN8LtFr1cWnvE8eLUb5zGJ9AtUD2tHm11gL tepnDnVVURjjT1npIQx7EHkUH4q7JGspEM0Dzeya1pMjWp/kRSOWJS9lyoQf/MH7 hHtqW99AeJ9PpgSiHb8yHV6+dG15jPTceqR5Y6K2s2Ce8yOw0AGlrKCNdJ1QJarI TQGSnt+61A== =VoPC -END PGP SIGNATURE- pgpWf6KL0OSX1.pgp Description: PGP signature --- End Message ---
Bug#1049841: marked as done (propellor: Fails to build binary packages again after successful build)
Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id
and subject line Bug#1049841: fixed in propellor 5.17-1
has caused the Debian Bug report #1049841,
regarding propellor: Fails to build binary packages again after successful build
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.)
--
1049841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild
Hi,
This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild
Relevant part of the build log:
> dpkg-gencontrol: warning: Conflicts field of package libghc-propellor-doc:
> substitution variable ${haskell:Conflicts} used, but is not defined
> dpkg-gencontrol: warning: package libghc-propellor-doc: substitution variable
> ${haskell:Recommends} unused, but is defined
> dpkg-gencontrol: warning: package libghc-propellor-doc: substitution variable
> ${haskell:ghc-version} unused, but is defined
> # only call dh_scour for packages in main
> if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then
> dh_scour -plibghc-propellor-doc ; fi
> dh_md5sums -plibghc-propellor-doc
> dh_builddeb -plibghc-propellor-doc
> dpkg-deb: building package 'libghc-propellor-doc' in
> '../libghc-propellor-doc_5.13-3_all.deb'.
> /usr/bin/make build
> make[1]: Entering directory '/<>'
> ./Setup build
> Run the 'configure' command first.
> make[1]: *** [Makefile:5: build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:10: build/propellor] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
>
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -b' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/16/propellor_5.13-3_unstable.log
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: propellor
Source-Version: 5.17-1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
propellor, 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 1049...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated propellor 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: Tue, 16 Apr 2024 19:17:26 +0200
Source: propellor
Architecture: source
Version: 5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1045437 1049841 1053981 1054640 1054828
Changes:
propellor (5.17-1) unstable; urgency=medium
.
* QA upload.
* New upstream release. (Closes: #1054640, #1053981, #1054828)
* Clean more build artefacts. (Closes: #1045437, #1049841)
Checksums-Sha1:
92a0775bcb34c479323628f90a690fde2d970e6c 3094 propellor_5.17-1.dsc
be0ceea30e7f191116fa6c77b7e32462b07703b4 738024 propellor_5.17.orig.tar.xz
b4100815057fc23ea29552df6790f43f9f17e76e 31624 propellor_5.17-1.debian.tar.xz
b64211982b6779f77c8d6bbc2f71af4ad5022557 9447 propellor_5.17-1_source.buildinfo
Checks
Bug#1045437: marked as done (propellor: Fails to build source after successful build)
Your message dated Tue, 16 Apr 2024 17:35:28 + with message-id and subject line Bug#1045437: fixed in propellor 5.17-1 has caused the Debian Bug report #1045437, regarding propellor: Fails to build source after successful build 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.) -- 1045437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: propellor Version: 5.13-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > > > dpkg-buildpackage: info: source package propellor > dpkg-buildpackage: info: source version 5.13-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Beckmann > dpkg-source --before-build . > dpkg-source: info: using options from propellor-5.13/debian/source/options: > --extend-diff-ignore=(^|/)(\.cabal-sandbox|docsets|\.dir-locals\.el|cabal\.sandbox\.config) > debian/rules clean > test -x debian/rules > dh_clean > perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \ > -E 'clean_recipe' > Running debian/hlibrary.setup clean > cleaning... > Running rm -rf dist dist-ghc dist-ghcjs dist-hugs > Running rm -f debian/hlibrary.setup > Running rm -f Setup.hi Setup.ho Setup.o > Running rm -f > rm -f configure-ghc-stamp > rm -f build-ghc-stamp build-hugs-stamp build-haddock-stamp > rm -f check-ghc-stamp > rm -f debian/tmp > rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs > rm -rf debian/tmp-db > rm -f debian/hlibrary.Makefile > dpkg-source -b . > dpkg-source: info: using options from propellor-5.13/debian/source/options: > --extend-diff-ignore=(^|/)(\.cabal-sandbox|docsets|\.dir-locals\.el|cabal\.sandbox\.config) > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building propellor using existing > ./propellor_5.13.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: error: cannot represent change to propellor: > dpkg-source: error: new version is symlink to > dist/build/propellor-config/propellor-config > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to Setup: binary file contents > changed > dpkg-source: error: add Setup in debian/source/include-binaries if you want > to store the modified binary in the debian tarball > dpkg-source: warning: executable mode 0755 of 'Setup' will not be represented > in diff > dpkg-source: warning: newly created empty file 'configured' will not be > represented in diff > dpkg-source: warning: newly created empty file 'tags' will not be represented > in diff > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/propellor_5.13-3_unstable.log 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: propellor Source-Version: 5.17-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of propellor, wh
Processed: tagging 1061213, tagging 1061215, tagging 1068134, tagging 1068133, tagging 965837, tagging 1065976 ...
Processing commands for cont...@bugs.debian.org:
> tags 1061213 + upstream
Bug #1061213 [src:intel-graphics-compiler] Please upgrade to llvm-toolchain-17
Added tag(s) upstream.
> tags 1061215 + upstream
Bug #1061215 [src:oclgrind] Please upgrade to llvm-toolchain-17
Added tag(s) upstream.
> tags 1068134 + sid trixie
Bug #1068134 {Done: Mattias Ellert }
[src:globus-gram-job-manager-scripts] globus-gram-job-manager-scripts: arch:all
package depends on pre-t64 library
Added tag(s) trixie and sid.
> tags 1068133 + sid trixie
Bug #1068133 {Done: Mattias Ellert }
[src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64
library
Added tag(s) sid and trixie.
> tags 965837 + patch
Bug #965837 [src:tart] tart: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) patch.
> tags 1065976 + pending
Bug #1065976 [src:python-levenshtein] python-levenshtein: FTBFS on arm{el,hf}:
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’?
[-Werror=implicit-function-declaration]
Added tag(s) pending.
> tags 1061434 + pending
Bug #1061434 [python3-levenshtein] python 3.12 extension not working
Added tag(s) pending.
> reassign 1069004 src:casacore-data-sources 2-4
Bug #1069004 [casacore-data-services] casacore-data-services: Hard coded
build-depends on decrufted lib libcasa-meas7
Warning: Unknown package 'casacore-data-services'
Bug reassigned from package 'casacore-data-services' to
'src:casacore-data-sources'.
No longer marked as found in versions 2-4.
Ignoring request to alter fixed versions of bug #1069004 to the same values
previously set
Bug #1069004 [src:casacore-data-sources] casacore-data-services: Hard coded
build-depends on decrufted lib libcasa-meas7
Marked as found in versions casacore-data-sources/2-4.
> tags 1069004 + sid trixie
Bug #1069004 [src:casacore-data-sources] casacore-data-services: Hard coded
build-depends on decrufted lib libcasa-meas7
Added tag(s) trixie and sid.
> tags 1044915 + pending
Bug #1044915 [src:emscripten] emscripten: Fails to build source after
successful build
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1044915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044915
1061213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061213
1061215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061215
1061434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061434
1065976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065976
1068133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068133
1068134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068134
1069004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069004
965837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066073: marked as done (wireless-tools: nmudiff for the 30~pre9-16.2 upload)
Your message dated Tue, 16 Apr 2024 08:37:35 + with message-id and subject line Bug#1066073: fixed in wireless-tools 30~pre9-17 has caused the Debian Bug report #1066073, regarding wireless-tools: nmudiff for the 30~pre9-16.2 upload 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.) -- 1066073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wireless-tools Version: 30~pre9-16.2 Severity: normal Tags: d-i patch X-Debbugs-Cc: Steve Langasek , debian-b...@lists.debian.org Hi, The previous upload broke udeb support, pointing to a non-existing udeb in the shlibs file. This made wireless-tools-udeb uninstallable. Seeing how this package is QA-maintained, I decided to just upload a fix without filing a bug report separately. I've verified the Depends field of the wireless-tools-udeb package looks fine; I didn't try and perform any runtime tests (other packages are broken right now). The source debdiff is attached. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant diff -Nru wireless-tools-30~pre9/debian/changelog wireless-tools-30~pre9/debian/changelog --- wireless-tools-30~pre9/debian/changelog 2024-02-29 03:02:19.0 +0100 +++ wireless-tools-30~pre9/debian/changelog 2024-03-12 01:42:45.0 +0100 @@ -1,3 +1,11 @@ +wireless-tools (30~pre9-16.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix shlibs entry for the udeb: it isn't getting renamed for the 64-bit +time_t transition. This makes wireless-tools-udeb installable again. + + -- Cyril Brulebois Tue, 12 Mar 2024 01:42:45 +0100 + wireless-tools (30~pre9-16.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru wireless-tools-30~pre9/debian/libiw30t64.shlibs wireless-tools-30~pre9/debian/libiw30t64.shlibs --- wireless-tools-30~pre9/debian/libiw30t64.shlibs 2024-02-29 03:01:29.0 +0100 +++ wireless-tools-30~pre9/debian/libiw30t64.shlibs 2024-03-12 01:42:42.0 +0100 @@ -1,2 +1,2 @@ libiw 30 libiw30t64 (>= 30~pre1) -udeb: libiw 30 libiw30t64-udeb (>= 30~pre1) +udeb: libiw 30 libiw30-udeb (>= 30~pre1) --- End Message --- --- Begin Message --- Source: wireless-tools Source-Version: 30~pre9-17 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of wireless-tools, 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. Petter Reinholdtsen (supplier of updated wireless-tools 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: Tue, 16 Apr 2024 08:52:02 +0200 Source: wireless-tools Architecture: source Version: 30~pre9-17 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1066073 Changes: wireless-tools (30~pre9-17) unstable; urgency=medium . * QA upload. . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/control: Remove trailing whitespaces * d/control: Add Vcs-* field . [ Petter Reinholdtsen ] * Acknowledge NMU 30~pre9-16.2 (Closes: #1066073). * Updated Standards-Version from 4.6.2 to 4.7.0. * Switched to debhelper-compat style build-depend. Checksums-Sha1: 33b0dea3962bc9ab12c20a2ab22f094491571713 2307 wireless-tools_30~pre9-17.dsc d62a69e9c79013b6d9b1e1a759a44e8e9daa90f6 12572 wireless-tools_30~pre9-17.debian.tar.xz cf59e7ba5505070f0ad7b6258fcb1cb4db65a6ec 6462 wireless-tools_30~pre9-17_source.buildinfo Checksums-Sha256: fd8890adacdc1c31750ca8cc967cab88b24442b8c733fb04fa46e7c93ae635db 2307 wireless-tools_30~pre9-17.dsc a23e8d2c9a96c7ff16a4ebc0d13cfdd7979b0946dd80d6517ec935b08803dde5 12572 wireless-tools_30~pre9-17.debian.tar.xz 75d2594ad322114d8e2a801f877840f5b02f94a5b8f99c6a44a741dc8eb15e1a 6462 wireless-tools_30~pre9-17_source.buildinfo Files: 78a943384753f4da4172b4b41fc32a8c 2307 net optional wireless-tools_30~pre9-17.dsc e2d7d55571ef6d1dea58dc9f55fc3b77 12572 net optional wireless-t
Bug#746198: marked as done (unar fails to extract test rar on arm.)
Your message dated Tue, 16 Apr 2024 00:44:38 +0200 with message-id and subject line Re: Bug#746198: unar fails to extract test rar on arm. has caused the Debian Bug report #746198, regarding unar fails to extract test rar on arm. 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.) -- 746198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.1-2 Severity: important x-debbugs-cc: debian-...@lists.debian.org I recently got the following report from a raspbian wheezy user (https://bugs.launchpad.net/raspbian/+bug/1165466). Using the simple test file found at http://www.maximumcompression.com/data/files/text-test.rar <http://www.maximumcompression.com/data/files/text-test.rar>: "unar text-test.rar" and "lsar text-test.rar" raise the error: "text-test.rar: RAR Archive parsing failed! (Unknown error.)" unar on my Squeeze desktop happily extracted the above archive. So I decided to test it in some test chroots (note: the i386 chroot was on an amd64 host, the arm chroots were all on an armv7 host) debian wheezy i386: works debian wheezy armel: fails debian wheezy armhf: fails debian jessie armel: fails debian jessie armhf: fails raspbian jessie: fails So it looks like a general arm breakage, not something specific to raspbian. --- End Message --- --- Begin Message --- This is certainly fixed.--- End Message ---
Bug#850878: marked as done (unar: Pathological file causes lsar to consume all available memory)
Your message dated Tue, 16 Apr 2024 00:42:29 +0200 with message-id and subject line Re: unar: Pathological file causes lsar to consume all available memory has caused the Debian Bug report #850878, regarding unar: Pathological file causes lsar to consume all available memory 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.) -- 850878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.8.1-3+b1 Severity: normal Dear Maintainer, The file below causes lsar to consume all available memory. This could lead to a denial of service. To duplicate the bug, run the Base-64 encoded data below through "base64 -d > decoded_data.doc" and then feed the resulting file to lsar: lsar decoded_data.doc lsar will consume memory without bound. Regards, Dianne. 0M8R4KGxGuEAPgADAP7/CQAGAAABNwAA EAAAOQEAAAD+ADYAAAD/ ///s pcEAX8AZBAAA8BK/EAAACAAAKBQAAA4AYmpiagAVABUA AAAJBBYA5BoAAGJ/AABifwAAYwQZpgD//w8A AAD//w8AAAD//w8AALcAALwGvAYAABYU FhQAAABmFGYUZhQAABQAAP8AehQA AAB6FHoUAAA4shQAABQAAADGFAAAFHoUbCoAADABAADaFAAA ANoU2hQAAADaFNoU3iYAAADeJgAAAN4m 7CgAAPUAAADhKQAAAOEp4SkAAADhKQAAAOEp4SkAACQA AACcKwAAsgIAAE4uAAAqBSoAACEAZhQAAADeJgAA AABiJgAAfN4m3iYAAADeJgUq AAAWFBYU2hQAANoUAACIEQAAJioAABYw KDAoMCgAAADeJgAA4gAAABYUAAA42hQAAABmFNoU 7CgAADAo 3iYAAADsKAAAMCgA ADAoThQAABgA MCgAAADaFP8AsK9yJGZq 0gEAAP8AwCcwKAAA2CgAABQ8KgAAMAAA AGwqMCgAAAB4LgAAAMAnAABweC4wKAAA AAAw KAAAOHguAABmFGgoAABw3iYAAADeJgAAADAo 3iYAAADeJgAA3iYA AADeJgAAAN4mBSoFKgAA MCgAAN4m 3iYAAADeJgAAAGwq3iYAAADeJgAAAN4m3iYA AP8A/wD//wD/ AP8A/wD/AP8A/wD/AP8A /wD/AP8A/wD/AHgu3iYAAADe JgAAAN4m3iYAAADeJgAAAN4m AADeJgAAAN4m3iYA AAC8BgAAIAwAANwSAAA6AQAABQASAQAAGQQA AAgICAgt LS0tLUJFR0lOIFBHUCBNRVNTQUdFLS0tLS0NLS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9D Sy0tLS0tDVZlcnNpb246IEdudVBHDQ1tUUlOQkZiZ3ZHQUJFQUM2T3NZc0pDM1ZrdEIrcHZVUGxz S2x6NzVaMjBGQjkzNks3NlVJRWtJYXRjOWI5RFRBDXlaUXVzUENJWWxhUlMyU2l
Bug#1066610: marked as done (gnomad2: FTBFS: jukebox.c:1979:13: error: implicit declaration of function ‘set_tag_for_file’; did you mean ‘set_tag_for_mp3file’? [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 21:36:53 + with message-id and subject line Bug#1066610: fixed in gnomad2 2.9.6-9 has caused the Debian Bug report #1066610, regarding gnomad2: FTBFS: jukebox.c:1979:13: error: implicit declaration of function ‘set_tag_for_file’; did you mean ‘set_tag_for_mp3file’? [-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.) -- 1066610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnomad2 Version: 2.9.6-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 -DPACKAGE_NAME=\"gnomad2\" -DPACKAGE_TARNAME=\"gnomad2\" > -DPACKAGE_VERSION=\"2.9.6\" -DPACKAGE_STRING=\"gnomad2\ 2.9.6\" > -DPACKAGE_BUGREPORT=\"tr...@df.lth.se\" -DPACKAGE_URL=\"\" > -DPACKAGE=\"gnomad2\" -DVERSION=\"2.9.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 > -DHAVE_TAGLIB=1 -DHAVE_LIBMTP=1 -DHAVE_LIBMTP_030=1 -DHAVE_GUDEV=1 > -DGETTEXT_PACKAGE=\"gnomad2\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 > -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DENABLE_NLS=1 -DGNOMADLOCALEDIR=\"/usr/share/locale\" -DHAVE_DIRENT_H=1 > -DHAVE_MALLOC_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_FCNTL_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_CHDIR=1 -I. -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 > -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/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread > -I/usr/include/libusb-1.0 -I/usr/include/taglib -I/usr/include/gudev-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DPREFIX=\"/usr\" -DSYSCONFDIR=\"/etc\" -DDATADIR=\"/usr/share\" > -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" -DPIXMAPSDIR=\""/usr/share/pixmaps"\" > -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 > -DGTK_DISABLE_SINGLE_INCLUDES -DG_DISABLE_SINGLE_INCLUDES -c -o editmeta.o > editmeta.c > gnomad2.c: In function ‘scan_jukebox’: > gnomad2.c:282:3: warning: ‘g_thread_create’ is deprecated: Use 'g_thread_new' > instead [-Wdeprecated-declarations] > 282 | g_thread_create(scan_thread,(gpointer) _thread_args, FALSE, > NULL); > | ^~~ > In file included from /usr/include/glib-2.0/glib.h:115, > from /usr/include/gtk-3.0/gdk/gdkconfig.h:8, > from /usr/include/gtk-3.0/gdk/gdk.h:30, > from /usr/include/gtk-3.0/gtk/gtk.h:30, > from common.h:51, > from gnomad2.c:20: > /usr/include/glib-2.0/glib/deprecated/gthread.h:102:10: note: declared here > 102 | GThread *g_thread_create (GThreadFunc func, > | ^~~ > gnomad2.c: In function ‘main’: > gnomad2.c:456:3: warning: ‘g_thread_init’ is deprecated > [-Wdeprecated-declarations] > 456 | g_thread_init(NULL); > | ^ > /usr/include/glib-2.0/glib/deprecated/gthread.h:267:10: note: declared here > 267 | void g_thread_init
Bug#1068663: marked as done (zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined)
Your message dated Mon, 15 Apr 2024 21:38:21 +
with message-id
and subject line Bug#1068663: fixed in zzuf 0.15-4
has caused the Debian Bug report #1068663,
regarding zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol
`open64' is already defined
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.)
--
1068663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zzuf
Version: 0.15-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=zzuf=armhf=0.15-3=1712473020=0
In file included from /usr/include/arm-linux-gnueabihf/sys/cdefs.h:24,
from libzzuf/lib-mem.c:24:
/usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
_DEFAULT_SOURCE"
| ^~~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-DLIBZZUF -I./libzzuf -I./common -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -std=c99 -g -O2 -Wall
-W -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow
-Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c
libzzuf/lib-signal.c -o libzzuf/la-lib-signal.o >/dev/null 2>&1
/tmp/ccnMZahz.s: Assembler messages:
/tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined
/tmp/ccnMZahz.s:4926: Error: symbol `lseek64' is already defined
make[3]: *** [Makefile:708: libzzuf/la-lib-fd.lo] Error 1
make[3]: *** Waiting for unfinished jobs
/tmp/ccKhQeYR.s: Assembler messages:
/tmp/ccKhQeYR.s:1867: Error: symbol `mmap64' is already defined
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: zzuf
Source-Version: 0.15-4
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
zzuf, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated zzuf 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: Mon, 15 Apr 2024 23:12:17 +0200
Source: zzuf
Architecture: source
Version: 0.15-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1068663
Changes:
zzuf (0.15-4) unstable; urgency=medium
.
* QA upload.
* Undefine _FILE_OFFSET_BITS and _TIME_BITS for some files that want to
provide replacements for both e.g. open() and open64(). (Closes: #1068663)
Checksums-Sha1:
6df0c7d0f6e2777870dd4a53e9a36ec7d56fdd0a 1822 zzuf_0.15-4.dsc
a377c8d4090ad985780061ceacd20b10abe8b10b 5540 zzuf_0.15-4.debian.tar.xz
988ea0f5f38a4d05e6736938fd68098431fc43e8 5604 zzuf_0.15-4_source.buildinfo
Checksums-Sha256:
8dec6637bafb148e3be768cef4a866365488e444725d9d119255a92ada84a927 1822
zzuf_0.15-4.dsc
c5f669388cb4b7ba5f9843d3bb721c6c4732d5b61cba6544318c8d428d5b2b21 5540
zzuf_0.15-4.debian.tar.xz
2ce4c9453bd77db2536fa364f9abe79e8825c020fede9d730597f2cdaba78413 5604
zzuf_0.15-4_source.buildinfo
Files:
c0b8e2ef1db0e0fd6011b11f66f7db3e 1822 devel optional zzuf_0.15-4.dsc
57205e69c1a512cb282f401294e415f5 5540 devel optional zzuf_0.15-4.debian.tar.xz
e3bd916968eb9359efaa1a270f874b6f 5604 devel optional
zzuf_0.15-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdmJUQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCMc/D/44LrvN+nxIUVOHDtwyKkTu2TRThNFJDwI8
ZkpE7GEhUz4uJKyLWno2z0SXUtkRVjiMsT+m7uc+9rc7AHvV4p1s6grho+qpdbrn
XwNLo4851Zhj/IX/vNjuIjA+HtpRkYDH2tO78lx4c1pKHzOx9x//wHt/h7Sh0vo7
wjki+MVq9r6iyy/m7d8LU87Zb0i+5k4MLFE/y0hV79Q/BJ3KtDjoaqZUMnAZyD8J
jQwwkNOsJyUED+1QNaMpEXZKL4eeCe7O2MOR6sIEml5NfoIZuvNKToXrtytZLVRz
sS4LakQRICeDSoUq3oJ91J7lVINVQ0IJsBizZ1Q/TgYg
Bug#974972: marked as done (unar: There is a new upstream version)
Your message dated Mon, 15 Apr 2024 20:56:18 + with message-id and subject line Bug#974972: fixed in unar 1.10.8+ds1-1 has caused the Debian Bug report #974972, regarding unar: There is a new upstream version 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.) -- 974972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Version: 1.10.1-2+b6 Severity: important Hi, unar code is now hosted on GitHub under the address: https://github.com/MacPaw/XADMaster The latest version is 1.10.7 and it contains many bugfixes: https://github.com/MacPaw/XADMaster/releases I hope unar can be updated in Debian. Thanks --- End Message --- --- Begin Message --- Source: unar Source-Version: 1.10.8+ds1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of unar, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated unar 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: Mon, 15 Apr 2024 22:08:17 +0200 Source: unar Architecture: source Version: 1.10.8+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 974972 Changes: unar (1.10.8+ds1-1) unstable; urgency=medium . * QA upload. * Recover usable changes from 1.10.7+ds1-1. * Recover patches from 1.10.7+ds1-1 with removed prefix. * Patch: Use package uchardet with universaldetector. * d/copyright: Correct info for new version. * New upstream version 1.10.8+ds1. (Closes: #974972) Checksums-Sha1: 6d86571a5ed93bb23f6ef5961131fe8b4fd1ab80 1919 unar_1.10.8+ds1-1.dsc e1cd61c86b4fdffee951765db63ed9474c24f8a3 939856 unar_1.10.8+ds1.orig.tar.xz b1fcac28fea489c96a015c11b24ff1f64126170e 7836 unar_1.10.8+ds1-1.debian.tar.xz 2ff2c4295e98175bc5287a1a2e99d8e06c0f130d 6717 unar_1.10.8+ds1-1_source.buildinfo Checksums-Sha256: f5b71c5c9037033ce7f05500955f5ad965bbde97fd592ef3df9800b7a0cf1dfd 1919 unar_1.10.8+ds1-1.dsc a3556266033e3fd7d788cf9e4f9a62cdb0d2a62d899971a1989504f8780d983a 939856 unar_1.10.8+ds1.orig.tar.xz e32bdc6b58300029c7e2aca73ca620c39b6f986eef2c09b89fab5cba6b302f46 7836 unar_1.10.8+ds1-1.debian.tar.xz 2ef7db74e273784bfc410ff8e6cae139eda7b35d5d05578c62996cd9f7f57c74 6717 unar_1.10.8+ds1-1_source.buildinfo Files: ed26064be180513a13ac7292018bf8aa 1919 utils optional unar_1.10.8+ds1-1.dsc 116f5bc3e473514496193e11fd320eac 939856 utils optional unar_1.10.8+ds1.orig.tar.xz c829c70cb395dbda46b14b4a8c5572bc 7836 utils optional unar_1.10.8+ds1-1.debian.tar.xz a154f38562677b9b7e1b6538a00be141 6717 utils optional unar_1.10.8+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYdixsQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFICNC/9HIoyLKitQWeNJ/RrsQknzTuMoNq6kczbj IPEjBxg1nQaCiLsuGEo7gQZNL0b8sKaVDFaMsBWqztm4FtbGwG0HWK7NO46Czsq1 cnM3L0Pza3vuSFlyKi9dW0Ny0BIHm4cSYuJa2Ep2POTkmY9VEXgMCt6Ev8jznUyO G+/IwRHKhqJK7MUal3qMMLytrPM9riaUmVsF6Q4Ku14ABp+oRMAdTYrsVviA704w Cojo9FN4v2EooxoCGOqP04qGANhPDVRM+ocoeHxDpi5aOkMZAuVjBFQeUu4ZrY3e tuD4SHFzQlqLIvntSpI2JL3a4DbqywmW1hZ3yicObYdwJrbXPxyupLD7eCP/jK1q l6hbsNJLt6pNIql5nUdP1sUBJxQWmlL/JhP/LFZpW0yWCwEOA4WA5aFr2HJKiPiI Fk3FY5A9DYLM8bs65S80y8qUmFa6oHWi28Ii+jH/aFdET2G3pk4H1MS7cbWlXzaR Zppiar6OsZYFqUZR6zsAhmrLdhhAapk= =xzuZ -END PGP SIGNATURE- pgpVPF06PwbWm.pgp Description: PGP signature --- End Message ---
Bug#1023971: marked as done (pantalaimon: Missing dependency on python3-pydbus)
Your message dated Mon, 15 Apr 2024 19:19:20 +
with message-id
and subject line Bug#1023971: fixed in pantalaimon 0.10.5-2
has caused the Debian Bug report #1023971,
regarding pantalaimon: Missing dependency on python3-pydbus
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.)
--
1023971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pantalaimon
Version: 0.9.1-1
Dear maintainers,
When python3-pydbus is not installed, panctl errors with this traceback:
$ panctl
Traceback (most recent call last):
File "/usr/bin/panctl", line 33, in
sys.exit(load_entry_point('pantalaimon==0.9.1', 'console_scripts',
'panctl')())
File "/usr/bin/panctl", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in
_find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in
_call_with_frames_removed
File "/usr/lib/python3/dist-packages/pantalaimon/panctl.py", line 32,
in
from pydbus import SessionBus
ModuleNotFoundError: No module named 'pydbus'
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pantalaimon
Source-Version: 0.10.5-2
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
pantalaimon, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated pantalaimon 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: Mon, 15 Apr 2024 20:49:27 +0200
Source: pantalaimon
Binary: pantalaimon python3-pantalaimon
Architecture: source all
Version: 0.10.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Description:
pantalaimon - E2EE aware proxy daemon for matrix clients - daemon
python3-pantalaimon - E2EE aware proxy daemon for matrix clients - python3
module
Closes: 1023971
Changes:
pantalaimon (0.10.5-2) unstable; urgency=medium
.
* QA upload. binary:all upload built with nocheck.
* Add B-D: python3-logbook.
* Add pantalaimon and panctl smoketests.
* Add dependencies for panctl: python3-gi, python3-pydbus.
* Add dependencies for pantalaimon: python3-dbus, python3-notify2.
(Closes: #1023971)
Checksums-Sha1:
e442c718bdb3b62cdaafe3f273b0f2ce285479f1 2441 pantalaimon_0.10.5-2.dsc
7db7db42ab11c2b08884aa3e5aa37f841c874fc7 4540
pantalaimon_0.10.5-2.debian.tar.xz
12c2a458415774a2e82a894ac85589d10033bc11 16208 pantalaimon_0.10.5-2_all.deb
a356851719314bbb7ba579cee7a1cac637ea88eb 9585
pantalaimon_0.10.5-2_amd64.buildinfo
f2251560c957e30b65844b1da22996c9c263eb5c 38908
python3-pantalaimon_0.10.5-2_all.deb
Checksums-Sha256:
7bc4184a52527f3ea6fb7d4817b5ed4d5fa9bf8e50080777de44fba930393dba 2441
pantalaimon_0.10.5-2.dsc
bfc24e9be69d8a3881368414aca69b8d23dd2c239bda2a923533afae513230e1 4540
pantalaimon_0.10.5-2.debian.tar.xz
d2f3d5068b380c8984048ac685fab9c21176d515d118739fa84e82dea83fec9b 16208
pantalaimon_0.10.5-2_all.deb
4ed389ed20d5419fe0979e01661b759f10f624d8f751f2752918fdb4d4385bdd 9585
pantalaimon_0.10.5-2_amd64.buildinfo
74b6ae4476667191c48937d1ff6e6b6d66c9a3255b67470870ae63a5dbd12850 38908
python3-pantalaimon_0.10.5-2_all.deb
Files:
9f39798579e47d132627338fa13be0e8 2441 net optional pantalaimon_0.10.5-2.dsc
66185ea48bf7339c094ad21417fd65ca 4540 net optional
pantalaimon_0.10.5-2.debian.tar.xz
009541a1a605bbf782cfbf54054f1db3 16208 net optional
pantalaimon_0.10.5-2_all.deb
30ee0ee0ad2ccd7d1ae57584c30b919a 9585 net o
Bug#1044667: marked as done (esnacc: Fails to build source after successful build)
Your message dated Mon, 15 Apr 2024 17:50:05 + with message-id and subject line Bug#1044667: fixed in esnacc 1.8.1-4 has caused the Debian Bug report #1044667, regarding esnacc: Fails to build source after successful build 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.) -- 1044667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: esnacc Version: 1.8.1-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package esnacc > dpkg-buildpackage: info: source version 1.8.1-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Rene Engelhard > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean --with autoreconf > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >debian/rules override_dh_auto_clean > make[1]: Entering directory '/<>' > dh_auto_clean > dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > make -j1 distclean > make[2]: Entering directory '/<>' > rm -f compiler/esnacc > rm -f c-examples/simple/genber c-examples/simple/minbuf > c-examples/simple/expbuf c-examples/simple/sbuf c-examples/test-lib/testlib > cxx-examples/main > test -z "compiler/core/lex-asn1.c compiler/core/y.output > compiler/core/y.tab.c compiler/core/y.tab.h compiler/esnacc.xml > asn1specs/p-rec.h asn1specs/p-rec.c pr.ber test.txt > cxx-examples/src/autotags.cpp cxx-examples/src/autotags.h > cxx-examples/src/rfc1157-snmp.cpp cxx-examples/src/rfc1157-snmp.h > cxx-examples/src/rfc1155-smi.cpp cxx-examples/src/rfc1155-smi.h" || rm -f > compiler/core/lex-asn1.c compiler/core/y.output compiler/core/y.tab.c > compiler/core/y.tab.h compiler/esnacc.xml asn1specs/p-rec.h asn1specs/p-rec.c > pr.ber test.txt cxx-examples/src/autotags.cpp cxx-examples/src/autotags.h > cxx-examples/src/rfc1157-snmp.cpp cxx-examples/src/rfc1157-snmp.h > cxx-examples/src/rfc1155-smi.cpp cxx-examples/src/rfc1155-smi.h > test -z "c-lib/libcasn1.la cxx-lib/libcxxasn1.la" || rm -f c-lib/libcasn1.la > cxx-lib/libcxxasn1.la > rm -f c-lib/so_locations cxx-lib/so_locations > rm -rf .libs _libs > rm -rf c-examples/simple/.libs c-examples/simple/_libs > rm -rf c-examples/test-lib/.libs c-examples/test-lib/_libs > rm -rf c-lib/.libs c-lib/_libs > rm -rf c-lib/src/.libs c-lib/src/_libs > rm -rf compiler/.libs compiler/_libs > rm -rf cxx-examples/.libs cxx-examples/_libs > rm -rf cxx-lib/.libs cxx-lib/_libs > rm -rf cxx-lib/src/.libs cxx-lib/src/_libs > rm -f *.o > rm -f asn1specs/*.o > rm -f c-examples/simple/*.o > rm -f c-examples/test-lib/*.o > rm -f c-lib/src/*.o > rm -f c-lib/src/*.lo > rm -f compiler/back-ends/*.o > rm -f compiler/back-ends/c++-gen/*.o > rm -f compiler/back-ends/c-gen/*.o > rm -f compiler/back-ends/idl-gen/*.o > rm -f compiler/core/*.o > rm -f cxx-examples/src/*.o > rm -f cxx-lib/src/*.o > rm -f cxx-lib/src/*.lo > test -z "c-examples/simple/genber.log c-examples/simple/minbuf.log > c-examples/simple/expbuf.log c-examples/simple/sbuf.log > c-examples/test-lib/testlib.log cxx-examples/main.log" || rm -f > c-examples/simple/genber.log c-examples/simple/minbuf.log > c-examples/simple/expbuf.log c-examples/simple/sbuf.log > c-examples/test-lib/testlib.log cxx-examples/main.log > test -z "c-examples/simple/genber.trs c-examples/simple/minbuf.t
Bug#1066970: marked as done (FTBFS: error: implicit declaration of function 'InitNibbleMem' [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 17:50:05 + with message-id and subject line Bug#1066970: fixed in esnacc 1.8.1-4 has caused the Debian Bug report #1066970, regarding FTBFS: error: implicit declaration of function 'InitNibbleMem' [-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.) -- 1066970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: esnacc Version: 1.8.1-3 Severity: serious Justification: FTBFS Tags: sid ftbfs User: lu...@debian.org Usertags: ftbfs-impfuncdef Hi, esnacc FTBFS: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -c -o c-examples/simple/sbuf-sbuf-ex.o `test -f 'c-examples/simple/sbuf-ex.c' || echo './'`c-examples/simple/sbuf-ex.c /bin/bash ./libtool --tag=CC --mode=link gcc -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -Wl,-z,relro -o c-examples/simple/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o c-examples/simple/sbuf-sbuf-ex.o c-lib/libcasn1.la -lm libtool: link: gcc -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -Wl,-z -Wl,relro -o c-examples/simple/.libs/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o c-examples/simple/sbuf-sbuf-ex.o c-lib/.libs/libcasn1.so -lm -pthread gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O0 -Wall -Wextra -c -o c-examples/test-lib/testlib-test-lib.o `test -f 'c-examples/test-lib/test-lib.c' || echo './'`c-examples/test-lib/test-lib.c c-examples/test-lib/test-lib.c: In function 'main': c-examples/test-lib/test-lib.c:68:5: error: implicit declaration of function 'InitNibbleMem' [-Werror=implicit-function-declaration] 68 | InitNibbleMem (256, 256); | ^ [...] 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 Indeed a build with export DEB_BUILD_MAINT_OPTIONS=qa=-bug-implicit-func works. But better than disabling it would be to fix it of course ;) Regards, Rene --- End Message --- --- Begin Message --- Source: esnacc Source-Version: 1.8.1-4 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of esnacc, 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 Beckmann (supplier of updated esnacc 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: Mon, 15 Apr 2024 19:35:47 +0200 Source: esnacc Architecture: source Version: 1.8.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1011071 1044667 1066970 Changes: esnacc (1.8.1-4) unstable; urgency=medium . [ Andreas Beckmann ] * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066970) * Fix building twice in a row. (Closes: #1044667) * esnacc-doc: Do not recommend evince. (Closes: #1011071) * Declare Rules-Requires-Root: no. * CI: Allow the reprotest to fail due to libeoffice #1065448. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Debian Janitor
Bug#1011071: marked as done (esnacc-doc: pulls in evince by default)
Your message dated Mon, 15 Apr 2024 17:50:05 + with message-id and subject line Bug#1011071: fixed in esnacc 1.8.1-4 has caused the Debian Bug report #1011071, regarding esnacc-doc: pulls in evince by 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.) -- 1011071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: esnacc-doc Version: 1.8.1-1 Severity: minor Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? `apt install libesnacc-dev` in an up-to-date bullseye chroot. * What was the outcome of this action? evince with a whole heap of GUI-related dependencies would be pulled in in a build chroot. * What outcome did you expect instead? Installation of libesnacc-dev and libesnacc180 only, which can be achieved using apt flag `--no-install-recommends`. I would propose dropping evince from "Recommends:" and possibly adding pdf-viewer to "Suggests:" to prevent a development package from pulling in a specific PDF viewer by default. -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled esnacc-doc depends on no packages. Versions of packages esnacc-doc recommends: ii evince 3.38.2-1 esnacc-doc suggests no packages. --- End Message --- --- Begin Message --- Source: esnacc Source-Version: 1.8.1-4 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of esnacc, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated esnacc 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: Mon, 15 Apr 2024 19:35:47 +0200 Source: esnacc Architecture: source Version: 1.8.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1011071 1044667 1066970 Changes: esnacc (1.8.1-4) unstable; urgency=medium . [ Andreas Beckmann ] * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066970) * Fix building twice in a row. (Closes: #1044667) * esnacc-doc: Do not recommend evince. (Closes: #1011071) * Declare Rules-Requires-Root: no. * CI: Allow the reprotest to fail due to libeoffice #1065448. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Debian Janitor ] * Apply multi-arch hints. + libesnacc-dev: Add Multi-Arch: same. Checksums-Sha1: fc4d4525b8014f90334758183a9d1584afb92be5 2121 esnacc_1.8.1-4.dsc 2681312d536bf62f68fcc887c6927e8f2e08f96e 11084 esnacc_1.8.1-4.debian.tar.xz 3634445bc8fa71d7e5f969ef18904db90a654302 5870 esnacc_1.8.1-4_source.buildinfo Checksums-Sha256: 0c3d45d5f01a55409cbae6f38e947d8edeaf011a65535566012bc46f75d3ba02 2121 esnacc_1.8.1-4.dsc c9410bda41832825db2b47d78a23729e0a1b4003aa32dd241f2a84a6ca718498 11084 esnacc_1.8.1-4.debian.tar.xz 7989ac997002845ab99f03a542e67312a692263726a3bbce464e75594d44298b 5870 esnacc_1.8.1-4_source.buildinfo Files: 2c67d113fea50ff0dafc796fbba4d798 2121 devel optional esnacc_1.8.1-4.dsc a3008e8f740bc424f8828023ae4d1a8a 11084 devel optional esnacc_1.8.1-4.debian.tar.xz c23a242a2fc6c94605a758ccaf734828 5870 devel optional esnacc_1.8.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdZcwQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCO8iD/4zTJn++OCwI8HRB8DtapNzQV0pE5w+/g/4 V4a5oVdLhHQrr2qakAxfagn2F4CzUtl+kbBPB9SnrndE6OZmEXn30qB9E4CDrMaU LfaTFSNhGP5wIW/XN3+ZuF0JxB7NjBCqaFlH/cAdJhOAjQvaNJXvIl7Sn4rw9Ttl In/IvRU1wLEm2omSmJ9eG2VilCulApTPy6BRBwlmpSsqDacqXEM4KRtF2jeHu4n7 9h2lll9JiDypmnbsOhOiBcFaau49xJWu+ccZ+FJjNEcC
Bug#1058545: marked as done (esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25)
Your message dated Mon, 15 Apr 2024 19:29:57 +0200 with message-id <18f89cf6-16e4-9739-0711-f193711a6...@debian.org> and subject line Re: due to #1058653 has caused the Debian Bug report #1058545, regarding esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25 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.) -- 1058545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: esnacc Version: 1.8.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 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 '/<>' > dh_install > dh_install: warning: Compatibility levels before 10 are deprecated (level 9 > in use) > rm -rf /<>/debian/esnacc/usr/share/doc/snacc-doc/ \ > /<>/debian/esnacc/usr/share/man/man1/snacced.1* > make[1]: Leaving directory '/<>' >dh_installdocs > dh_installdocs: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > dh_installdocs: error: Cannot find (any matches for) "doc/Esnacc.pdf" (tried > in .) > > make: *** [debian/rules:13: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/esnacc_1.8.1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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 --- On Sat, 16 Mar 2024 11:07:30 +0100 Rene Engelhard wrote: Error: source file could not be loaded (the last message is it, the javaldx warning is harmless) Which is due to a bug in libreoffice which is fixed by libreoffice (4:24.2.0-2) experimental; urgency=medium Sid now has 4:24.2.2-3 and the problem is no longer reproducible, thus closing. Andreas--- End Message ---
Processed: Re: Bug#575781: Please resolve IPv6 gateway too
Processing control commands: > tags -1 - patch Bug #575781 [libnss-gw-name] Please resolve IPv6 gateway too Removed tag(s) patch. -- 575781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021466: marked as done (pacman: reproducible-builds: build path embedded in /usr/games/pacman)
Your message dated Mon, 15 Apr 2024 16:06:01 + with message-id and subject line Bug#1021466: fixed in pacman 10-20 has caused the Debian Bug report #1021466, regarding pacman: reproducible-builds: build path embedded in /usr/games/pacman 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.) -- 1021466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pacman Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The build path is embedded in /usr/games/pacman: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/pacman.html /build/1st/pacman-10/pac.cc:85 vs. /build/2/pacman-10/2nd/pac.cc:85 The attached patch fixes this adjusting the generated Makefile from debian/rules to include -ffile-prefix-map in the CXXFLAGS_DEFINES variable. Alternately, it might be worth using "dpkg-buildflags --get CXXFLAGS" instead of hard-coding -ffile-prefix-map, and will benefit from other useful flags as well. According to my local tests, with this patch applied, pacman should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining pacman! live well, vagrant From c2c6a41d218ae21765360832814e1d61d887f529 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Sun, 9 Oct 2022 00:20:22 + Subject: [PATCH 1/2] debian/rules: Add -ffile-prefix-map to CXXEXTRA_DEFINES in generated Makefile to avoid embedding build paths. https://reproducible-builds.org/docs/build-path/ --- debian/rules | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/rules b/debian/rules index 406e691..5092f98 100755 --- a/debian/rules +++ b/debian/rules @@ -10,6 +10,8 @@ build-indep: build-stamp build-stamp: dh_testdir xmkmf -a + # Avoid embedding build path + sed -i -e "s,CXXEXTRA_DEFINES =,CXXEXTRA_DEFINES = -ffile-prefix-map=$(CURDIR)=.,g" Makefile $(MAKE) touch build-stamp -- 2.37.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: pacman Source-Version: 10-20 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of pacman, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated pacman 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: Mon, 15 Apr 2024 17:51:04 +0200 Source: pacman Architecture: source Version: 10-20 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1021466 Changes: pacman (10-20) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to enforce the use of pristine-tar. * Updated vcs in d/control to Salsa. * Updated Standards-Version from 4.6.0 to 4.7.0. * Switched to simpler dh build rules and enabled hardening. * Replaced obsolete build dependency libncurses5-dev with libncurses-dev. * Add xmkmf override to make build reproducible. (Closes: 1021466) Checksums-Sha1: bf1a261b16b3cea593bf9cf0eb8914d357725aae 1795 pacman_10-20.dsc 51769f1d6e8babe3d0caaf87aabfbe11b81f314b 9704 pacman_10-20.debian.tar.xz 26b33de3cb83e3635c8f9f02a2fd3972dc85ea66 6917 pacman_10-20_source.buildinfo Checksums-Sha256: 939bdbc8ddcd1c67f8fef50b4642a0678a3b0b5d83171e66860cfab747d9aa7f 1795 pacman_10-20.dsc 8aa9df29d1f7ab185e9be5314d956c0ad32305ede73ddf2b62bc00456bcd6522 9704 pacman_10-20.debian.tar.xz 25ec510f5c4fea6ca8d7a71d4a29e3f1ad1f76c3c3166a4ba65c13fb3787b0e9 6917 pacman_10-20_source.buildinfo Files: 7d74eb2c4d8955acc549f7193b449c60 1795 games optional pacman_10-20.dsc ea65d498a18c1ef2740004f5cbe4c4bd 9704 games optional pacman_10-20.debian.tar.xz 586c5eef3066cfb69279f1a52936d3dd 6917 games optional pacman_10-20_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYdTUAACgkQgSgKoIe6 +w4xghAAqPv90sX5G8MiMKg2Ml4q0NmjBdOx/R2uoO100iJ+f6R
Bug#1067278: marked as done (proxycheck: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 1)
Your message dated Mon, 15 Apr 2024 12:51:14 + with message-id and subject line Bug#1067278: fixed in proxycheck 0.49a-8 has caused the Debian Bug report #1067278, regarding proxycheck: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 1 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.) -- 1067278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: proxycheck Version: 0.49a-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean >debian/rules override_dh_auto_clean > make[1]: Entering directory '/<>' > ./configure > Configuring proxycheck 0.49a (2004-05-29) > > checking for C compiler... gcc > checking whenever C compiler (gcc) works... yes > checking for socket routines... no > checking for socket routines in -lsocket -lnsl... no > configure: see config.log and conftest.* for possible explanation > make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/19/proxycheck_0.49a-7_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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: proxycheck Source-Version: 0.49a-8 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of proxycheck, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated proxycheck 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: Mon, 15 Apr 2024 13:46:34 +0200 Source: proxycheck Architecture: source Version: 0.49a-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1067278 Changes: proxycheck (0.49a-8) unstable; urgency=medium . * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1067278) * Simplify cleaning. Checksums-Sha1: db6112dfcccd5db34cd909ae3ca111810cfbb2d9 1878 proxycheck_0.49a-8.dsc 569008ea966ea58957ab85be00f84f6ba5ed327e 6080 proxycheck_0.49a-8.debian.tar.xz 688779f76f3c053b79784a048c32c6a528b46d09 5639 proxycheck_0.49a-8_source.buildinfo Checksums-Sha256: ba82257767ebddd0c0433fe0914946dd9c74addc7f512490bd52064956dab8e6 1878 proxycheck_0.49a-8.dsc f243f2375a18bd657c60e0cf72dd27c31c46dc45c2a1648658596bdb003903dc 6080 proxycheck_0.49a-8.debian.tar.xz 15143e8abb28be221138a086da74564003e2228cf4b90367acab04df3f915534 5639 proxycheck_0.49a-8_source.buildinfo Files: 54ec053366ca1d98b768e66a09dfcc5a 1878 net optional proxycheck_0.49a-8.dsc 0c08920a78ade9d5122f0cc29f5b9442 6080 net optional proxycheck_0.49a-8.debian.tar.xz 0bc8a1209efb2f5eca9250b87249ff14 5639 net optional proxycheck_0.49a-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdFCoQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCDBfD/9q9eogC3ImTJqVtkvKOb8OgrIzdgHOEWuQ WpbtxmFPHREpeCbOi8wQEaKFl/yDVxgKKZ0B1DOh80Hn+K0MkHCuu1H47TOlTGTL b8TWyC846ntHp+JzIxov2e6L+1NQu4jD7va1XXuh3WuSEggNPbF+vfaozO6di1lL 4hAuPwhEd8+8RXyL6XBA8o38HKDPPyR1JC/emlXxOKF8Gm10/noSNtB6Jt1m5ENh lVCphn8kBx4wL3TS1kqruuipaFb+/xWWh5Zh1SiVN+W
Processed: closing 1054749
Processing commands for cont...@bugs.debian.org: > close 1054749 Bug #1054749 [src:ruby-pry-byebug] ruby-android-key-attestation: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require "pry-byebug" Bug #1054737 [src:ruby-pry-byebug] ruby-pry-byebug: FTBFS: ERROR: Test "ruby3.1" failed: :86:in `require': cannot load such file -- pry-byebug (LoadError) Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054737 1054749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065774: marked as done (libdigidoc: FTBFS on arm{el,hf}: /<>/libdigidoc/DigiDocService.c:327:19: error: implicit declaration of function ‘ddocAddSignatureFromMemory’ [-Werror=implici
Your message dated Mon, 15 Apr 2024 10:35:35 +
with message-id
and subject line Bug#1065774: fixed in libdigidoc 3.10.5-5
has caused the Debian Bug report #1065774,
regarding libdigidoc: FTBFS on arm{el,hf}:
/<>/libdigidoc/DigiDocService.c:327:19: error: implicit
declaration of function ‘ddocAddSignatureFromMemory’
[-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.)
--
1065774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigidoc
Version: 3.10.5-4.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=libdigidoc=armel=3.10.5-4.1=1709133165=0
/<>/libdigidoc/DigiDocService.c:327:19: error: implicit
declaration of function ‘ddocAddSignatureFromMemory’
[-Werror=implicit-function-declaration]
327 | err = ddocAddSignatureFromMemory(pSigDoc, szFileName,
(const void*)p1, strlen(p1));
| ^~
cc1: some warnings being treated as errors
make[3]: *** [libdigidoc/CMakeFiles/digidoc.dir/build.make:359:
libdigidoc/CMakeFiles/digidoc.dir/DigiDocService.c.o] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libdigidoc
Source-Version: 3.10.5-5
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
libdigidoc, 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.
Andreas Beckmann (supplier of updated libdigidoc 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: Mon, 15 Apr 2024 12:12:47 +0200
Source: libdigidoc
Architecture: source
Version: 3.10.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 1065774 1066271
Changes:
libdigidoc (3.10.5-5) unstable; urgency=medium
.
* QA upload.
* Fix building with -Werror=implicit-function-declaration.
(Closes: #1066271, #1065774)
Checksums-Sha1:
b7cacb6f90edab58327d0a6b694df6ca5658d951 2233 libdigidoc_3.10.5-5.dsc
65787b8b2461c57bc208b324f06e3b556a936b49 4652 libdigidoc_3.10.5-5.debian.tar.xz
31d7fa4d3e4fb3b07ad36626abb4b2bee390d03f 7036
libdigidoc_3.10.5-5_source.buildinfo
Checksums-Sha256:
e6edd8df607f9aead6625c3e0a3aee65e3a90c9b351e8b3b255b9cd88b299a25 2233
libdigidoc_3.10.5-5.dsc
8160c7f51500213815ebac9a8d6b5b07449a870b0ae6c64c96ab10da4d63be1e 4652
libdigidoc_3.10.5-5.debian.tar.xz
5d056276648af5f2c512f09d5e40d08f030925057e8ff8ab3a81578d0166123b 7036
libdigidoc_3.10.5-5_source.buildinfo
Files:
dc036a6015487b6a6e9690624fd8b613 2233 libs optional libdigidoc_3.10.5-5.dsc
bbcbd3fda191ef240794054e4246949f 4652 libs optional
libdigidoc_3.10.5-5.debian.tar.xz
073144d90fda2940909e3539f721d6f4 7036 libs optional
libdigidoc_3.10.5-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYc/eoQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCCEhD/9cNKDoqJ9e1e3CzsbkO5z+FWGm+PvTzswp
ZAGNjTk/5SOTYL2TNK9tQdFniPpyez5gIL8nkdchIVGQVSBwxD4DofUGnPgn4HrH
USUBLSHoIQzHj2fkN4PKC8xmtOO2U5bp7FYoOdnujthulAwTnl2+kfKWtD0uFXij
S7Ok39Z+3rldQbNDoeZBOlUsobP26jXjc2gguO/q2nkvRu9BTvOcuU+v03CZ4uL6
8mTVbRlIfiuwOvYg+uToxYX0KICU+jgG6nOiYGAnCCAXPQVvp/oeXRT/qzJLinZp
NrA1XWFyvf79EkItEoLcxrwyY7T1stzIB4rhotFcpLArJMqjfhUjhOZNWb+jPFYf
u2/vTYLMtlpG5kQuOLnadqHZK0YyEWR2QqjQC2a4c5IGOIZRn65rQdQU3R9ob2Rf
haBt3mKoB1HHb/swtz9AwmS/iFDTn9zcmCjpG75C2lsXpKn37fmMmxB2P/aWX4fP
FBcTbhGeXNY4TthRK7n1ILkEKtxDldg8RpsNefgm6B4ttzP3H6Ll/VZ8ccR87yN4
+Gy+ZcoeimDr+9HCpFn9WoXyNbotdKpubXs3WZBNRyTPRJXFPZ1hQT3SXeYRDpaK
eULiw00C26Bvnuvltwu7lHc1DYlKk9sSj/w9sIRp6CzT2ERDp5xL3iGtv/3MXfQc
24xjqaLexg==
=3MsA
-END PGP SIGNATURE-
pgp4R_PWaHetr.pgp
Description: PGP signature
--- End Message ---
Bug#1066271: marked as done (libdigidoc: FTBFS: DigiDocVerify.c:939:11: error: implicit declaration of function ‘ddocGetDNPartFromString’ [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 10:35:35 +
with message-id
and subject line Bug#1066271: fixed in libdigidoc 3.10.5-5
has caused the Debian Bug report #1066271,
regarding libdigidoc: FTBFS: DigiDocVerify.c:939:11: error: implicit
declaration of function ‘ddocGetDNPartFromString’
[-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.)
--
1066271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigidoc
Version: 3.10.5-4.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):
> cd /<>/obj-x86_64-linux-gnu/libdigidoc && /usr/bin/cc
> -DBUILD_DATE=\"28.02.2024\" -DBUILD_VER=0 -DMAJOR_VER=3 -DMINOR_VER=10
> -DRELEASE_VER=5 -DVER_SUFFIX=\"\" -Ddigidoc_EXPORTS -I/<>
> -I/<>/obj-x86_64-linux-gnu -I/usr/include/libxml2 -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 -fPIC
> -fvisibility=hidden -MD -MT libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o
> -MF CMakeFiles/digidoc.dir/DigiDocOCSP.c.o.d -o
> CMakeFiles/digidoc.dir/DigiDocOCSP.c.o -c
> /<>/libdigidoc/DigiDocOCSP.c
> /<>/libdigidoc/DigiDocVerify.c:939:11: error: implicit
> declaration of function ‘ddocGetDNPartFromString’
> [-Werror=implicit-function-declaration]
> 939 | err = ddocGetDNPartFromString(sDN, sId, );
> | ^~~
> /<>/libdigidoc/DigiDocVerify.c: In function
> ‘verifyNotaryInfoCERT2’:
> /<>/libdigidoc/DigiDocVerify.c:1568:35: warning: passing
> argument 1 of ‘ossl_check_X509_type’ discards ‘const’ qualifier from pointer
> target type [-Wdiscarded-qualifiers]
> 1568 | sk_X509_push(ver_certs, notCert);
> | ^~~
> In file included from /usr/include/openssl/types.h:33,
> from /usr/include/openssl/x509.h:26:
> /usr/include/openssl/x509.h:78:1: note: expected ‘X509 *’ {aka ‘struct
> x509_st *’} but argument is of type ‘const X509 *’ {aka ‘const struct x509_st
> *’}
>78 | SKM_DEFINE_STACK_OF_INTERNAL(X509, X509, X509)
> | ^
> In file included from /usr/include/string.h:535,
> from /usr/include/openssl/ec.h:23,
> from /usr/include/openssl/x509.h:33,
> from /<>/libdigidoc/DigiDocLib.h:36,
> from /<>/libdigidoc/DigiDocConvert.h:25,
> from /<>/libdigidoc/DigiDocConvert.c:24:
> In function ‘strncat’,
> inlined from ‘breakToLinesOf64’ at
> /<>/libdigidoc/DigiDocConvert.c:887:7:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:138:10: warning:
> ‘__builtin_strncat’ specified bound [9223372036854775811,
> 18446744073709551615] exceeds maximum object size 9223372036854775807
> [-Wstringop-overread]
> 138 | return __builtin___strncat_chk (__dest, __src, __len,
> | ^~
> 139 | __glibc_objsize (__dest));
> | ~
> /<>/libdigidoc/DigiDocOCSP.c: In function ‘WriteOCSPResponse’:
> /<>/libdigidoc/DigiDocOCSP.c:249:18: warning: passing argument 1
> of ‘ASN1_i2d_bio’ from incompatible pointer type
> [-Wincompatible-pointer-types]
> 249 | ASN1_i2d_bio((int (*)(void*, unsigned char**))i2d_OCSP_RESPONSE,
> bout, (unsigned char*)resp);
> | ^~
> | |
> | int (*)(void *, unsigned char **)
> In file included from /usr/include/openssl/objects.h:21,
> from /usr/include/openssl/evp.h:43,
> from /usr/include/openssl/x509.h:29,
>
Bug#1066246: marked as done (lcm: FTBFS: emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 10:04:58 + with message-id and subject line Bug#1066246: fixed in lcm 1.3.1+repack1-8 has caused the Debian Bug report #1066246, regarding lcm: FTBFS: emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ [-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.) -- 1066246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lcm Version: 1.3.1+repack1-7 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 -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" > -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" > -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -I. -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -Wdate-time > -D_FORTIFY_SOURCE=2 -g -std=gnu99 -Wall -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE_SOURCE -D_REENTRANT -Wno-unused-parameter > -Wno-format-zero-length -Wshadow -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o emit_csharp.o emit_csharp.c > emit_cpp.c: In function ‘emit_header_start’: > emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ > [-Werror=implicit-function-declaration] > 306 | _exit(1); > | ^ > emit_cpp.c:306:19: warning: incompatible implicit declaration of built-in > function ‘_exit’ [-Wbuiltin-declaration-mismatch] > In function ‘ensure_token_capacity’, > inlined from ‘tokenize_next_internal’ at tokenize.c:325:14: > tokenize.c:127:28: warning: argument 2 range [18446744071562067968, > 18446744073709551615] exceeds maximum object size 9223372036854775807 > [-Walloc-size-larger-than=] > 127 | t->token = (char*) realloc(t->token, t->token_capacity); > |^~~~ > In file included from tokenize.c:1: > /usr/include/stdlib.h: In function ‘tokenize_next_internal’: > /usr/include/stdlib.h:564:14: note: in a call to allocation function > ‘realloc’ declared here > 564 | extern void *realloc (void *__ptr, size_t __size) > | ^~~ > gcc -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" > -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" > -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -I. -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -Wdate-time > -D_FORTIFY_SOURCE=2 -g -std=gnu99 -Wall -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE_SOURCE -D_REENTRANT -Wno-unused-parameter > -Wno-format-zero-length -Wshadow -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o emit_python.o emit_python.c > gcc -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" > -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" > -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAV
Bug#1066368: marked as done (filter: FTBFS: actions.c:255:21: error: implicit declaration of function ‘wait’ [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 08:49:14 +
with message-id
and subject line Bug#1066368: fixed in filter 2.6.3+ds1-4
has caused the Debian Bug report #1066368,
regarding filter: FTBFS: actions.c:255:21: error: implicit declaration of
function ‘wait’ [-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.)
--
1066368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: filter
Version: 2.6.3+ds1-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):
> cc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c
> -o actions.o actions.c
> actions.c:200:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 200 | mail_message(address, fptr,resendflag)
> | ^~~~
> actions.c: In function ‘mail_message’:
> actions.c:255:21: error: implicit declaration of function ‘wait’
> [-Werror=implicit-function-declaration]
> 255 | wait();
> | ^~~~
> actions.c:292:14: error: implicit declaration of function ‘lock’; did you
> mean ‘lockf’? [-Werror=implicit-function-declaration]
> 292 | if (!lock()) {
> | ^~~~
> | lockf
> actions.c:336:9: error: implicit declaration of function ‘unlock’; did you
> mean ‘unlink’? [-Werror=implicit-function-declaration]
> 336 | unlock(); /* blamo or not? Let it decide! */
> | ^~
> | unlink
> actions.c: In function ‘save_message’:
> actions.c:393:27: error: implicit declaration of function ‘save_to_folder’
> [-Werror=implicit-function-declaration]
> 393 | ret = save_to_folder(foldername,tmpfptr);
> | ^~
> actions.c: In function ‘mail_message’:
> actions.c:269:21: warning: ignoring return value of ‘setuid’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 269 | setuid(user_uid);
> | ^~~~
> actions.c:270:21: warning: ignoring return value of ‘setgid’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 270 | setgid(user_gid);
> | ^~~~
> actions.c: In function ‘execute’:
> actions.c:544:17: warning: ignoring return value of ‘setgid’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 544 | setgid(user_gid);
> | ^~~~
> actions.c:545:17: warning: ignoring return value of ‘setuid’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 545 | setuid(user_uid);
> | ^~~~
> actions.c:549:17: warning: ignoring return value of ‘dup’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 549 | dup(tmpfd);
> | ^~
> cc1: some warnings being treated as errors
> make[1]: *** [: actions.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/filter_2.6.3+ds1-3_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 ---
--- Begi
Bug#1044588: marked as done (filter: Fails to build source after successful build)
Your message dated Mon, 15 Apr 2024 08:49:14 + with message-id and subject line Bug#1044588: fixed in filter 2.6.3+ds1-4 has caused the Debian Bug report #1044588, regarding filter: Fails to build source after successful build 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.) -- 1044588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: filter Version: 2.6.3+ds1-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package filter > dpkg-buildpackage: info: source version 2.6.3+ds1-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Axel Beckert > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_auto_clean > dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > make -j1 clean > make[1]: Entering directory '/<>' > /bin/rm -f actions.o filter.o lock.o parse.o regexp.o rules.o summarize.o > utils.o audit.o istrcmp.o mk_lockname.o strtokq.o filter core > make[1]: Leaving directory '/<>' >dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in > use) > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building filter using existing > ./filter_2.6.3+ds1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > filter-2.6.3+ds1/config.h > filter-2.6.3+ds1/config.sh > filter-2.6.3+ds1/sysdefs.h > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/filter_2.6.3+ds1-3.diff.PO9Xjy > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/filter_2.6.3+ds1-3_unstable.log 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: filter Source-Version: 2.6.3+ds1-4 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of filter, 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 1044...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated filter 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: Mon, 15 Apr 2024 10
Bug#1066492: marked as done (tinydyndns: FTBFS: seek_set.c:7:7: error: implicit declaration of function ‘lseek’ [-Werror=implicit-function-declaration])
Your message dated Mon, 15 Apr 2024 08:39:54 +
with message-id
and subject line Bug#1066492: fixed in tinydyndns 0.4.2.debian1-3
has caused the Debian Bug report #1066492,
regarding tinydyndns: FTBFS: seek_set.c:7:7: error: implicit declaration of
function ‘lseek’ [-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.)
--
1066492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tinydyndns
Version: 0.4.2.debian1-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):
> make[2]: Entering directory '/<>'
> ( cat warn-auto.sh; \
> echo 'main="$1"; shift'; \
> echo exec "`head -1 conf-ld`" \
> '-o "$main" "$main".o ${1+"$@"}' \
> ) > load
> ( cat warn-auto.sh; \
> echo exec "`head -1 conf-cc`" '-c ${1+"$@"}' \
> ) > compile
> chmod 755 load
> chmod 755 compile
> cat warn-auto.sh choose.sh \
> | sed s}HOME}"`head -1 conf-home`"}g \
> > choose
> ( cat warn-auto.sh; \
> echo CC=\'`head -1 conf-cc`\'; \
> echo LD=\'`head -1 conf-ld`\'; \
> cat find-systype.sh; \
> ) | sh > systype
> ./compile env.c
> ./compile alloc.c
> ./compile alloc_re.c
> ./compile getln.c
> chmod 755 choose
> ./compile getln2.c
> ./compile stralloc_cat.c
> ./compile stralloc_catb.c
> ./compile stralloc_cats.c
> ./compile stralloc_copy.c
> ./compile stralloc_eady.c
> ./compile stralloc_num.c
> ./compile stralloc_opyb.c
> ./compile stralloc_opys.c
> ./compile stralloc_pend.c
> ./compile buffer.c
> ./compile buffer_1.c
> ./compile buffer_2.c
> ./compile buffer_copy.c
> ./compile buffer_get.c
> ./compile buffer_put.c
> ./compile strerr_die.c
> ./compile strerr_sys.c
> ./compile buffer_read.c
> ./compile buffer_write.c
> ./compile error.c
> ./compile error_str.c
> ./compile ndelay_off.c
> ./compile ndelay_on.c
> ./compile open_read.c
> ./compile open_trunc.c
> ./compile openreadclose.c
> ./compile readclose.c
> ./compile seek_set.c
> ./compile socket_accept.c
> ./compile socket_bind.c
> seek_set.c: In function ‘seek_set’:
> seek_set.c:7:7: error: implicit declaration of function ‘lseek’
> [-Werror=implicit-function-declaration]
> 7 | { if (lseek(fd,(off_t) pos,SET) == -1) return -1; return 0; }
> | ^
> ./compile socket_conn.c
> ./compile socket_listen.c
> ./compile socket_recv.c
> ./compile socket_send.c
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile.djbdns:767: seek_set.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/tinydyndns_0.4.2.debian1-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: tinydyndns
Source-Version: 0.4.2.debian1-3
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
tinydyndns, 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 Beckma
Processed: found 1068663 in 0.15-2
Processing commands for cont...@bugs.debian.org:
> found 1068663 0.15-2
Bug #1068663 [src:zzuf] zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error:
symbol `open64' is already defined
Marked as found in versions zzuf/0.15-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066221: marked as done (citadel-client: FTBFS: src/routines2.c:370:29: error: implicit declaration of function ‘ka_wait’ [-Werror=implicit-function-declaration])
Your message dated Sun, 14 Apr 2024 22:20:01 +
with message-id
and subject line Bug#1066221: fixed in citadel-client 916-5
has caused the Debian Bug report #1066221,
regarding citadel-client: FTBFS: src/routines2.c:370:29: error: implicit
declaration of function ‘ka_wait’ [-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.)
--
1066221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citadel-client
Version: 916-4
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[1]: Entering directory '/<>'
>
> CC src/citadel.c
> Dependencies: gcc -M -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I ./src/include/ |
> sed -e 's!.o!.o /.o buildinfo!' > buildinfo
> Complie: gcc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wall -O2 -Wall -Wcast-qual -Wcast-align -Wstrict-prototypes
> -Wno-strict-aliasing -D_REENTRANT -pthread -I ./include/ -Wdate-time
> -D_FORTIFY_SOURCE=2 -I. -I ./src/include/ -DHAVE_CONFIG_H
> -DDIFF="/usr/bin/diff" -DPATCH="/usr/bin/patch" -c -o buildinfo
> LDFLAGS: -Wl,-z,relro -Wl,-z,now
> CC src/client_chat.c
> CC src/client_passwords.c
> CC src/commands.c
> CC src/md5.c
>
> CC src/messages.c
> CC src/rooms.c
> CC src/routines.c
> src/md5.c: In function ‘MD5Final’:
> src/md5.c:153:26: warning: argument to ‘sizeof’ in ‘memset’ call is the same
> expression as the destination; did you mean to dereference it?
> [-Wsizeof-pointer-memaccess]
> 153 | memset(ctx, 0, sizeof(ctx));/* In case it's sensitive */
> | ^
> src/commands.c: In function ‘getcmd’:
> src/commands.c:1051:72: warning: the comparison will always evaluate as
> ‘true’ for the address of ‘c_keys’ will never be NULL [-Waddress]
> 1051 | if ((cptr->c_keys[cmdpos +
> 1]) != 0)
> |
> ^~
> src/commands.c:71:14: note: ‘c_keys’ declared here
>71 | char c_keys[5][64];
> | ^~
> src/messages.c: In function ‘read_message’:
> src/messages.c:624:29: warning: the comparison will always evaluate as ‘true’
> for the address of ‘email’ will never be NULL [-Waddress]
> 624 | if ((message->email != NULL) &&
> (!IsEmptyStr(message->email))) {
> | ^~
> In file included from src/messages.c:46:
> ./src/include/citadel_ipc.h:241:14: note: ‘email’ declared here
> 241 | char email[SIZ];/* Email address of sender */
> | ^
> src/messages.c:640:28: warning: the comparison will always evaluate as ‘true’
> for the address of ‘msgid’ will never be NULL [-Waddress]
> 640 | if (message->msgid != NULL) {
> |^~
> ./src/include/citadel_ipc.h:237:14: note: ‘msgid’ declared here
> 237 | char msgid[SIZ];/* Original message ID */
> | ^
> src/messages.c:644:33: warning: the comparison will always evaluate as ‘true’
> for the address of ‘references’ will never be NULL [-Waddress]
> 644 | if (message->references != NULL) if
> (!IsEmptyStr(message->references)) {
> | ^~
> ./src/include/citadel_ipc.h:255:14: note: ‘references’ declared here
> 255 | char references[SIZ]; /* Thread references */
> | ^~
> src/messages.c:648:30: warning: the comparison will always evaluate as ‘true’
> for the address of ‘subject’ will never be NULL [-Waddress]
> 648 | if (message->subject != NULL) {
> | ^~
> ./src/include/citadel_i
Processed: retitle 1064925 to RFP: fail2ban-prometheus-exporter -- collect and export Prometheus metrics on Fail2Ban ...
Processing commands for cont...@bugs.debian.org:
> retitle 1064925 RFP: fail2ban-prometheus-exporter -- collect and export
> Prometheus metrics on Fail2Ban
Bug #1064925 [wnpp] RFP: fail2ban-prometheus-exporter - collect and export
Prometheus metrics on Fail2Ban)
Changed Bug title to 'RFP: fail2ban-prometheus-exporter -- collect and export
Prometheus metrics on Fail2Ban' from 'RFP: fail2ban-prometheus-exporter -
collect and export Prometheus metrics on Fail2Ban)'.
> retitle 1000161 ITP: himalaya -- cli to manage emails
Bug #1000161 [wnpp] ITP: cli to manage emails
Changed Bug title to 'ITP: himalaya -- cli to manage emails' from 'ITP: cli to
manage emails'.
> found 1061212 3.1.6~dfsg-7
Bug #1061212 [src:emscripten] Please upgrade to llvm-toolchain-17
Marked as found in versions emscripten/3.1.6~dfsg-7.
> found 1061215 21.10-4
Bug #1061215 [src:oclgrind] Please upgrade to llvm-toolchain-17
Marked as found in versions oclgrind/21.10-4.
> found 1061216 10.0.1-2.1
Bug #1061216 [src:openvdb] Please upgrade to llvm-toolchain-17
Marked as found in versions openvdb/10.0.1-2.1.
> found 1061213 1.0.15136.3-1
Bug #1061213 [src:intel-graphics-compiler] Please upgrade to llvm-toolchain-17
Marked as found in versions intel-graphics-compiler/1.0.15136.3-1.
> found 1061214 0.41.1-1
Bug #1061214 [src:llvmlite] Please upgrade to llvm-toolchain-17
Marked as found in versions llvmlite/0.41.1-1.
> fixed 1039985 2.2-3
Bug #1039985 [libjson-smart-java] libjson-smart-java: buster-lts has a newer
version than bullseye/bookworm/sid
Marked as fixed in versions json-smart/2.2-3.
> tags 1068975 + sid trixie
Bug #1068975 [src:python-zxcvbn] Abandoned upstream and unmaintained
Added tag(s) trixie and sid.
> tags 1068937 + sid trixie
Bug #1068937 {Done: Mathias Gibbens } [python3-lxc]
python3-lxc: hard-coded dependency on liblcx1
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000161
1039985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039985
1061212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061212
1061213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061213
1061214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061214
1061215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061215
1061216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061216
1064925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064925
1068937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068937
1068975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012137: marked as done (RFH: unar -- Unarchiver for a variety of file formats)
Your message dated Sun, 14 Apr 2024 21:46:36 +0200 with message-id <752cb9bd-e1c3-468e-b473-002e78042...@debian.org> and subject line Re: RFH: unar -- Unarchiver for a variety of file formats has caused the Debian Bug report #1012137, regarding RFH: unar -- Unarchiver for a variety of file formats 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.) -- 1012137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unar Severity: normal I request assistance with maintaining the unar package. The package description is: The Unarchiver is an archive unpacker program with support for the popular zip, RAR, 7z, tar, gzip, bzip2, LZMA, XZ, CAB, MSI, NSIS, EXE, ISO, BIN, and split file formats, as well as the old Stuffit, Stuffit X, DiskDouble, Compact Pro, Packit, cpio, compress (.Z), ARJ, ARC, PAK, ACE, ZOO, LZH, ADF, DMS, LZX, PowerPacker, LBR, Squeeze, Crunch, and other old formats. . This package contains the lsar tool which lists the contents of archives and the unar tool which extracts those contents. Unar is an important dependency to a wide range of archiver-related packages (KDE's ark, GNOME's file-roller, xarchiver, etc.) I have adopted it after the previous ITS process as in https://bugs.debian.org/1008569 . When updating it to the latest upstream release (1.10.7), its autopkgtest fails on some release architectures (armhf, s390x). Since this project is written in Objective-C which is unfamiliar to me and crashes on some hardware architectures different from i386/arm64, debugging is not easy to me. Help is welcome on fixing bugs for the 1.10.7+ds1-1 version, which you may find its source package archived in snapshot.debian.org. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- The package was orphaned.--- End Message ---
Processed: bumping severity
Processing commands for cont...@bugs.debian.org: > severity 1061214 serious Bug #1061214 [src:llvmlite] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > severity 1061219 serious Bug #1061219 [src:triton] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > severity 1061213 serious Bug #1061213 [src:intel-graphics-compiler] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > severity 1061216 serious Bug #1061216 [src:openvdb] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > severity 1061215 serious Bug #1061215 [src:oclgrind] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > severity 1061212 serious Bug #1061212 [src:emscripten] Please upgrade to llvm-toolchain-17 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061212 1061213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061213 1061214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061214 1061215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061215 1061216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061216 1061219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#737968: marked as done (magicmaze: please provide a desktop file and icons)
Your message dated Sun, 14 Apr 2024 07:04:35 + with message-id and subject line Bug#737968: fixed in magicmaze 1.4.3.6+dfsg-4 has caused the Debian Bug report #737968, regarding magicmaze: please provide a desktop file and icons 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.) -- 737968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: magicmaze Version: 1.4.3.6+dfsg-2 Severity: wishlist User: pkg-games-de...@lists.alioth.debian.org Usertags: desktop-integration goals not-gamesteam Dear maintainer, currently magicmaze does not supply a desktop file and no desktop icons. Hence the game is not well integrated into the user's desktop environment. Please consider helping to improve the desktop integration of games in Debian. https://wiki.debian.org/Games/JessieReleaseGoal Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: magicmaze Source-Version: 1.4.3.6+dfsg-4 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of magicmaze, 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 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated magicmaze 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: Sun, 14 Apr 2024 08:52:39 +0200 Source: magicmaze Architecture: source Version: 1.4.3.6+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 737968 972615 Changes: magicmaze (1.4.3.6+dfsg-4) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.4 to 4.7.0. * Updated vcs in d/control to Salsa. * Switched from debhelper compat level 9 to 13. * Updated homepage link in d/control to new location. (Closes: #972615) * Added magicmaze.desktop file for desktop integration. Dropped old menu file. (Closes: #737968) * Changed obsolete package priority extra to optional. Checksums-Sha1: 2e452ff35ff31a2c83d6814bdd408f65e0212579 1893 magicmaze_1.4.3.6+dfsg-4.dsc dd1db78d5b424a2a68c657d3bc0f71e35167efb8 6432 magicmaze_1.4.3.6+dfsg-4.debian.tar.xz 8c15a5d8f1ff6824b12d8ebf1e8d5adb172e58c3 6393 magicmaze_1.4.3.6+dfsg-4_source.buildinfo Checksums-Sha256: 88fe664eb047e61808a1bdc7d841886fb2feb44d2ad0a5c9982f95f7528ad075 1893 magicmaze_1.4.3.6+dfsg-4.dsc 436bb3a8a5e8f6200fb4cc3d5eaf04f3fe3e88f7f8523cc6d46c4577b139b06f 6432 magicmaze_1.4.3.6+dfsg-4.debian.tar.xz 6d19eeaad83ad433c014bd16311138afc11ac40ad55e5e70ad3e1a459c1c16b5 6393 magicmaze_1.4.3.6+dfsg-4_source.buildinfo Files: e0036332f91ed55121a865631d986a7a 1893 games optional magicmaze_1.4.3.6+dfsg-4.dsc 542fd2b50a2f6e6f920cd960b96e55c9 6432 games optional magicmaze_1.4.3.6+dfsg-4.debian.tar.xz df7de6d481b88972614656942ca07599 6393 games optional magicmaze_1.4.3.6+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYbfZgACgkQgSgKoIe6 +w7+2A/9GA7MkO95a5kRK7o/WXcZ2bVNCX4inDTUmFj9D8RM9qtFnkBdcdW2HgGy BFq++ppaf/RgUhUWoreJ0rQGJXWPDpIbjXFwdEGq8vPAaNX/OMSw7ZWIUIZsY28t FOL+VY/m1p4E7J91NzQ9hm0bhSqWym1FgkZd93lFKG0UmzPQ+CcTKAdeR48DqVo5 Y+UiiCGBf0HZayCCGlxT6AEQU3B9IWXbas53YGoZWngQZuWK8isAY2EFDqSg4y81 jZG6jTsr0bcTP97YG/WZZjUQmJfhnuEv6A+QUeWGliaCt1gGSWiJO1zYfWv9SU3z Wj/UCbpuyC79NMHmDeiB+UxaJMkVYL+ct0/FeZRK1wvE45aDe9cRRxi67O/W4er6 Jq2JtqeU01XEN/GAAadVm6sjgr3dv5pOg4jo+jGl/4A68GQfaMERi58S2yd8Bh83 2jXZT5YyzZz/7wR+WGroFAdb51rpAuye8tUeFUuG37B5Px21SHXowpryzbagUeKv iLeFTCM4q2yEt/j1iVYRcWM3ytVKnvu8xjAQRdaCBPldIN9QOn/dJVvlSfaO2Zlf lBQKgh/WQ61GEv7qHFZd+dB5NZWCi1FmGWQ1x+TRAR/3iyHQEL6eEaiuIdaY1y7Q qzg+Er0FQUdnFfuWonjgADKvYmEEzSrR0v0KGQPRKQ0M3F4b8/M= =T4Zj -END PGP SIGNATURE- pgpfJH1H9XzgE.pgp Description: PGP signature --- End Message ---
Bug#972615: marked as done (magicmaze: homepage changed)
Your message dated Sun, 14 Apr 2024 07:04:35 + with message-id and subject line Bug#972615: fixed in magicmaze 1.4.3.6+dfsg-4 has caused the Debian Bug report #972615, regarding magicmaze: homepage changed 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.) -- 972615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: magicmaze Version: 1.4.3.6+dfsg-3 Severity: normal Dear Maintainers, as Rubyforge was discontinued, it seems that the homepage as moved to https://github.com/kentdahl/magic_maze Regards, Bernhard --- End Message --- --- Begin Message --- Source: magicmaze Source-Version: 1.4.3.6+dfsg-4 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of magicmaze, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated magicmaze 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: Sun, 14 Apr 2024 08:52:39 +0200 Source: magicmaze Architecture: source Version: 1.4.3.6+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 737968 972615 Changes: magicmaze (1.4.3.6+dfsg-4) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.4 to 4.7.0. * Updated vcs in d/control to Salsa. * Switched from debhelper compat level 9 to 13. * Updated homepage link in d/control to new location. (Closes: #972615) * Added magicmaze.desktop file for desktop integration. Dropped old menu file. (Closes: #737968) * Changed obsolete package priority extra to optional. Checksums-Sha1: 2e452ff35ff31a2c83d6814bdd408f65e0212579 1893 magicmaze_1.4.3.6+dfsg-4.dsc dd1db78d5b424a2a68c657d3bc0f71e35167efb8 6432 magicmaze_1.4.3.6+dfsg-4.debian.tar.xz 8c15a5d8f1ff6824b12d8ebf1e8d5adb172e58c3 6393 magicmaze_1.4.3.6+dfsg-4_source.buildinfo Checksums-Sha256: 88fe664eb047e61808a1bdc7d841886fb2feb44d2ad0a5c9982f95f7528ad075 1893 magicmaze_1.4.3.6+dfsg-4.dsc 436bb3a8a5e8f6200fb4cc3d5eaf04f3fe3e88f7f8523cc6d46c4577b139b06f 6432 magicmaze_1.4.3.6+dfsg-4.debian.tar.xz 6d19eeaad83ad433c014bd16311138afc11ac40ad55e5e70ad3e1a459c1c16b5 6393 magicmaze_1.4.3.6+dfsg-4_source.buildinfo Files: e0036332f91ed55121a865631d986a7a 1893 games optional magicmaze_1.4.3.6+dfsg-4.dsc 542fd2b50a2f6e6f920cd960b96e55c9 6432 games optional magicmaze_1.4.3.6+dfsg-4.debian.tar.xz df7de6d481b88972614656942ca07599 6393 games optional magicmaze_1.4.3.6+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYbfZgACgkQgSgKoIe6 +w7+2A/9GA7MkO95a5kRK7o/WXcZ2bVNCX4inDTUmFj9D8RM9qtFnkBdcdW2HgGy BFq++ppaf/RgUhUWoreJ0rQGJXWPDpIbjXFwdEGq8vPAaNX/OMSw7ZWIUIZsY28t FOL+VY/m1p4E7J91NzQ9hm0bhSqWym1FgkZd93lFKG0UmzPQ+CcTKAdeR48DqVo5 Y+UiiCGBf0HZayCCGlxT6AEQU3B9IWXbas53YGoZWngQZuWK8isAY2EFDqSg4y81 jZG6jTsr0bcTP97YG/WZZjUQmJfhnuEv6A+QUeWGliaCt1gGSWiJO1zYfWv9SU3z Wj/UCbpuyC79NMHmDeiB+UxaJMkVYL+ct0/FeZRK1wvE45aDe9cRRxi67O/W4er6 Jq2JtqeU01XEN/GAAadVm6sjgr3dv5pOg4jo+jGl/4A68GQfaMERi58S2yd8Bh83 2jXZT5YyzZz/7wR+WGroFAdb51rpAuye8tUeFUuG37B5Px21SHXowpryzbagUeKv iLeFTCM4q2yEt/j1iVYRcWM3ytVKnvu8xjAQRdaCBPldIN9QOn/dJVvlSfaO2Zlf lBQKgh/WQ61GEv7qHFZd+dB5NZWCi1FmGWQ1x+TRAR/3iyHQEL6eEaiuIdaY1y7Q qzg+Er0FQUdnFfuWonjgADKvYmEEzSrR0v0KGQPRKQ0M3F4b8/M= =T4Zj -END PGP SIGNATURE- pgpRn4dyNDXFy.pgp Description: PGP signature --- End Message ---
Bug#1013837: marked as done (pexec: Please remove dependency on install-info)
Your message dated Sun, 14 Apr 2024 04:19:42 + with message-id and subject line Bug#1013837: fixed in pexec 1.0~rc8-5 has caused the Debian Bug report #1013837, regarding pexec: Please remove dependency on install-info 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.) -- 1013837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pexec Severity: minor Dear Maintainer, your package declares a dependency on "install-info". However this dependency should only be needed for info viewers, as they have to care about updating the info index. Your package does not seem to provide an info viewer hence the dependency on "install-info" is not needed. Consider to remove it. The alternative dep "dpkg (>= 1.15.4)" (if present) can be removed too. https://wiki.debian.org/Transitions/DpkgToGnuInstallInfo Many thanks, Hilmar PreuÃe --- End Message --- --- Begin Message --- Source: pexec Source-Version: 1.0~rc8-5 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of pexec, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated pexec 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: Sun, 14 Apr 2024 05:49:13 +0200 Source: pexec Architecture: source Version: 1.0~rc8-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1013837 Changes: pexec (1.0~rc8-5) unstable; urgency=medium . * QA upload. . * Added d/gbp.conf to enforce the use of pristine-tar. * Updated Standards-Version from 3.9.3 to 4.7.0. * Updated vcs in d/control to Salsa. * Switched from debhelper compat level 7 to 13. * Changed obsolete package priority extra to optional. * Added new cflags.patch to make sure CFLAGS set in d/rules are applied. * Drop unnecessary dependency on install-info. (Closes: #1013837) * Drop root requirement for targets in d/rules. * Added no-use-after-free.patch to avoid incorrect use of memory block. Checksums-Sha1: 5ba941bdbd0a1d0b80a34203917078928611c1c0 1829 pexec_1.0~rc8-5.dsc b7f6bc3a0105c609d48add8a3f3cbf98cea52748 5728 pexec_1.0~rc8-5.debian.tar.xz 159eacd7736963562c08e5d26091f3aa972ea97d 6684 pexec_1.0~rc8-5_source.buildinfo Checksums-Sha256: 8dbd2e7c889e683b594ce1129a3701519005f4c52579dd006a0580c292497f96 1829 pexec_1.0~rc8-5.dsc c462d96e89073258140ac8c30f1ab7c6f4f0f1e9d66e6bd9b2271fb1d73e81a9 5728 pexec_1.0~rc8-5.debian.tar.xz b5e8c6137936cfde2cd9001d942b527bc7c64a9ebd59d4bd2ea38e6cb9171f0f 6684 pexec_1.0~rc8-5_source.buildinfo Files: 43950bddc5be141c789e5b47c5a6c21d 1829 utils optional pexec_1.0~rc8-5.dsc 4ab0cfba8f16a7d862b646c6247cb8bb 5728 utils optional pexec_1.0~rc8-5.debian.tar.xz d872446be4a3e389096a750cd33563bb 6684 utils optional pexec_1.0~rc8-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYbUmsACgkQgSgKoIe6 +w6o6xAAgZ7J/PWsRGwhCqRc8ViQtVevw2lYzrdeTykJk73bKj5IiB1z2nJlg00Z 3mTHCDDSjyf4XtdgoqbNaYz+1M3l1bi55nSIBKY3Q3yB19FdrMyPIya7OXR0ou12 ri0fPAlTeLAh2Hoy2LKnPHTRbtXkgeHrVquS6FJqulZ3iLOwblhPVFAWcmjnCDxQ tREXsXo6zub+sic6TTM5xLiBY8/qT7j/dDtkipF7M0QTC6xI2UKm3J5M4WW5IQMv FEsuYr+PgxhEApodak8hs/D9shp3NU1Bxr3o97KFfXkLNgOE70LBYOlHqS2BigM1 qCRbFBXl2ZA3L7iNXJ+BQfHXyNuqj4uxHHGd1tg15T4kmwva+rYGaspq+UOEexn1 XyUyh5wR0epUtKjZrbobrAuaruraz96JeJAy3C0gtyYIe1c51oXxZfgKsCRLPczj lrKRtbrNrbqKim9aUb+Mih9FBwaZIvGdyGkT5SH2j9+ZXhiVcpP5h0FulkLeb92n 1TQsARQ7Rvo7w3RJinRnUmKRMgh3KnDznlVbfZnQcUPNVnFc/B4T/IyWUS/N4Z7V jfLfIiVqkAAGtzBN+BigYnf5ahwQb0cy8R2Bqlt5eH7cGUhIM5ivloFh6WPwrQt+ HadjQiIdVaG4xn/DtD9E5MDz/P3d7D0E6dqLFsnSXco2h3+inKo= =g3Rl -END PGP SIGNATURE- pgpUWxlxLpz8C.pgp Description: PGP signature --- End Message ---
Bug#1066670: marked as done (ldap2dns: FTBFS: ldap2dns.c:477:25: error: implicit declaration of function ‘ldap_search_s’; did you mean ‘ldap_search_ext’? [-Werror=implicit-function-declaration])
Your message dated Sun, 14 Apr 2024 02:38:01 +
with message-id
and subject line Bug#1066670: fixed in ldap2dns 0.3.1-6
has caused the Debian Bug report #1066670,
regarding ldap2dns: FTBFS: ldap2dns.c:477:25: error: implicit declaration of
function ‘ldap_search_s’; did you mean ‘ldap_search_ext’?
[-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.)
--
1066670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldap2dns
Version: 0.3.1-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):
> gcc -g -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -DVERSION='"0.3.1"' -Wdate-time -D_FORTIFY_SOURCE=2 -c ldap2dns.c -o
> ldap2dns.o-dbg
> ldap2dns.c: In function ‘read_resourcerecords’:
> ldap2dns.c:477:25: error: implicit declaration of function ‘ldap_search_s’;
> did you mean ‘ldap_search_ext’? [-Werror=implicit-function-declaration]
> 477 | if ( (ldaperr = ldap_search_s(ldap_con, dn,
> LDAP_SCOPE_SUBTREE, "objectclass=DNSrrset", NULL, 0, ))!=LDAP_SUCCESS )
> | ^
> | ldap_search_ext
> ldap2dns.c:558:82: warning: format ‘%s’ expects argument of type ‘char *’,
> but argument 3 has type ‘char (*)[20]’ [-Wformat=]
> 558 | if
> (sscanf(bvals[0]->bv_val, "%16s", )!=1)
> |
> ~~~^ ~
> |
>| |
> |
>| char (*)[20]
> |
>char *
> ldap2dns.c: In function ‘read_dnszones’:
> ldap2dns.c:714:98: warning: format ‘%s’ expects argument of type ‘char *’,
> but argument 3 has type ‘char (*)[64]’ [-Wformat=]
> 714 | if
> (sscanf(bvals[zonenames]->bv_val, "%64s", [zonenames])!=1)
> |
> ~~~^ ~~~
> |
>| |
> |
>| char (*)[64]
> |
>char *
> ldap2dns.c: In function ‘connect’:
> ldap2dns.c:801:28: error: implicit declaration of function ‘ldap_init’
> [-Werror=implicit-function-declaration]
> 801 | ldap_con = ldap_init(options.hostname[i],
> options.port[i]);
> |^
> ldap2dns.c:801:26: warning: assignment to ‘LDAP *’ {aka ‘struct ldap *’} from
> ‘int’ makes pointer from integer without a cast [-Wint-conversion]
> 801 | ldap_con = ldap_init(options.hostname[i],
> options.port[i]);
> | ^
> ldap2dns.c:802:21: error: implicit declaration of function
> ‘ldap_simple_bind_s’; did you mean ‘ldap_sasl_bind_s’?
> [-Werror=implicit-function-declaration]
> 802 | if (ldap_simple_bind_s(ldap_con, options.binddn,
> options.password)==LDAP_SUCCESS) {
> | ^~
> | ldap_sasl_bind_s
> ldap2dns.c: In function ‘main’:
> ldap2dns.c:818:9: error: implicit declaration of function ‘umask’
> [-Werror=implicit-function-declaration]
> 818 | umask(022);
> | ^
> lda
Bug#1066567: marked as done (easyh10: FTBFS: ucs2char_iconv.c:319:25: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declaration])
Your message dated Sat, 13 Apr 2024 22:50:31 + with message-id and subject line Bug#1066567: fixed in easyh10 1.5-6 has caused the Debian Bug report #1066567, regarding easyh10: FTBFS: ucs2char_iconv.c:319:25: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-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.) -- 1066567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: easyh10 Version: 1.5-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): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -I../include -I. -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 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o ucs2char_iconv.lo > ucs2char_iconv.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I. > -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 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > ucs2char.c -fPIC -DPIC -o .libs/ucs2char.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I. > -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 -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > ucs2char_iconv.c -fPIC -DPIC -o .libs/ucs2char_iconv.o > ucs2char.c: In function ‘print_ucs2’: > ucs2char.c:284:28: warning: format ‘%c’ expects a matching ‘int’ argument > [-Wformat=] > 284 | fprintf(stderr, "0x%X %c ", *str); > | ~^ > || > |int > ucs2char_iconv.c: In function ‘print_ucs2’: > ucs2char_iconv.c:57:28: warning: format ‘%c’ expects a matching ‘int’ > argument [-Wformat=] >57 | fprintf(stderr, "0x%X %c ", *str); > | ~^ > || > |int > ucs2char_iconv.c: In function ‘iconv_convert’: > ucs2char_iconv.c:169:27: warning: passing argument 2 of ‘iconv’ from > incompatible pointer type [-Wincompatible-pointer-types] > 169 | iconv(cd, (const char **)inbuf, , (char > **)outbuf, ); > | ^~~~ > | | > | const char ** > In file included from ucs2char_iconv.c:40: > /usr/include/iconv.h:49:54: note: expected ‘char ** restrict’ but argument is > of type ‘const char **’ >49 | extern size_t iconv (iconv_t __cd, char **__restrict __inbuf, > |~~^~~ > ucs2char_iconv.c:177:50: warning: passing argument 2 of ‘iconv’ from > incompatible pointer type [-Wincompatible-pointer-types] > 177 | int iconvret = iconv(cd, (const char > **)inbuf, , , ); > | ^~~~ > | | > |
Bug#1067639: marked as done (sasl2-bin: terminates with smashed stack)
Your message dated Sat, 13 Apr 2024 13:35:02 + with message-id and subject line Bug#1067639: fixed in db5.3 5.3.28+dfsg2-7 has caused the Debian Bug report #1067639, regarding sasl2-bin: terminates with smashed stack 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.) -- 1067639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sasl2-bin Version: 2.1.28+dfsg1-5 X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org The openldap build on an m68k qemu-user buildd cannot install sasl2-bin in the chroot: […] Setting up pkg-config:m68k (1.8.1-1) ... Setting up libsasl2-2:m68k (2.1.28+dfsg1-5) ... Setting up libsasl2-modules-gssapi-mit:m68k (2.1.28+dfsg1-5) ... Setting up unixodbc-dev:m68k (2.3.12-1+b1) ... Setting up libgnutls28-dev:m68k (3.8.3-1.1+b2) ... Setting up libhcrypto5t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ... Setting up libotp0t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ... Setting up db-util (5.3.3) ... Setting up bind9-libs:m68k (1:9.19.21-1+b1) ... Setting up libsl0t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ... Setting up sasl2-bin (2.1.28+dfsg1-5) ... *** stack smashing detected ***: terminated qemu: uncaught target signal 6 (Aborted) - core dumped Aborted dpkg: error processing package sasl2-bin (--configure): installed sasl2-bin package post-installation script subprocess returned error exit status 134 Setting up libperl-dev:m68k (5.38.2-3.2+b1) ... Setting up libsasl2-dev (2.1.28+dfsg1-5) ... Setting up libgssrpc4t64:m68k (1.20.1-6+b1) ... Setting up libhx509-5t64-heimdal:m68k (7.8.git20221117.28daf24+dfsg-5+b2) ... dpkg: dependency problems prevent configuration of sbuild-build-depends-main-dummy: sbuild-build-depends-main-dummy depends on sasl2-bin; however: Package sasl2-bin is not configured yet. dpkg: error processing package sbuild-build-depends-main-dummy (--configure): dependency problems - leaving unconfigured […] Unpacking sbuild-build-depends-dose3-dummy (0.invalid.0) ... Setting up sasl2-bin (2.1.28+dfsg1-5) ... BDB0002 __fop_file_setup: Retry limit (100) exceeded saslpasswd2: generic failure dpkg: error processing package sasl2-bin (--configure): installed sasl2-bin package post-installation script subprocess returned error exit status 1 […] See: https://buildd.debian.org/status/fetch.php?pkg=openldap=m68k=2.5.16%2Bdfsg-2%2Bb2=1711312418=0 This does not seem to be specific to one buildd. Any idea how this can be debugged? --- End Message --- --- Begin Message --- Source: db5.3 Source-Version: 5.3.28+dfsg2-7 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of db5.3, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated db5.3 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: SHA384 Format: 1.8 Date: Sat, 13 Apr 2024 15:12:36 +0200 Source: db5.3 Architecture: source Version: 5.3.28+dfsg2-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Thorsten Glaser Closes: 1067639 Changes: db5.3 (5.3.28+dfsg2-7) unstable; urgency=medium . [ Bastian Germann ] * Compile db_signature with expected flags . [ Thorsten Glaser ] * QA upload. * Fix misuse of struct timespec (buffer overflow on ILP32 t64 architectures, more on big endian); with help from Bernhard Übelacker (Closes: #1067639) Checksums-Sha1: ae6b6bf62faf76943895c864d05803e2a8a8f39d 2374 db5.3_5.3.28+dfsg2-7.dsc 7229d42ffee9d6610e1a09aa397a500bbaee5c12 35232 db5.3_5.3.28+dfsg2-7.debian.tar.xz Checksums-Sha256: f7313fb306b5bf7ad6a428bffb581e649318859df139e35dd47c3d1f733803b2 2374 db5.3_5.3.28+dfsg2-7.dsc 9cee8969e1f440ec8aa2fbacd3a5819907829e0e7e7f1f746dccaa2c93fbf3f2 35232 db5.3_5.3.28+dfsg2-7.debian.tar.xz Files: 0916eb49829c7123e1527919815ef254 2374 libs optional db5.3_5.3.28+dfsg2-7.dsc 437d896417d8acac807d1e666850cae8 35232 libs optional db5.3_5.3.28+dfsg2-7.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (MirBSD
Bug#1066658: marked as done (sup: FTBFS: scm.c:316:9: error: implicit declaration of function ‘setproctitle’ [-Werror=implicit-function-declaration])
Your message dated Sat, 13 Apr 2024 09:07:47 +
with message-id
and subject line Bug#1066658: fixed in sup 20100519-4
has caused the Debian Bug report #1066658,
regarding sup: FTBFS: scm.c:316:9: error: implicit declaration of function
‘setproctitle’ [-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.)
--
1066658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sup
Version: 20100519-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):
> cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR
> -DNEED_SETPROCTITLE -DLIBWRAP -I. -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 -c
> -o stree.o stree.c
> scm.c: In function ‘service’:
> scm.c:316:9: error: implicit declaration of function ‘setproctitle’
> [-Werror=implicit-function-declaration]
> 316 | setproctitle("Serving %s", remotehost());
> | ^~~~
> scm.c: In function ‘request’:
> scm.c:448:16: warning: ignoring return value of ‘write’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 448 | (void) write(netfile, , sizeof(int));
> |^~~
> scmio.c: In function ‘readfile’:
> scmio.c:670:32: warning: ignoring return value of ‘write’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 670 | (void) write(f, buf, (size_t)XFERSIZE(count));
> |^~
> scmio.c: In function ‘crosspatch’:
> scmio.c:743:40: warning: ignoring return value of ‘write’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 743 | (void) write(1, buf, (size_t)c);
> |^~~~
> scmio.c:753:40: warning: ignoring return value of ‘write’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 753 | (void) write(netfile, buf, (size_t)c);
> |^~
> supcmeat.c: In function ‘setup’:
> supcmeat.c:321:24: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 321 | (void) chdir(thisC->Cbase);
> |^~~
> supcmeat.c: In function ‘listfiles’:
> supcmeat.c:522:24: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 522 | (void) chdir(thisC->Cprefix);
> |^
> supcmeat.c: In function ‘recvdir’:
> supcmeat.c:889:24: warning: ignoring return value of ‘chown’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 889 | (void) chown(t->Tname, t->Tuid, t->Tgid);
> |^
> supcmeat.c: In function ‘recvreg’:
> supcmeat.c:968:32: warning: ignoring return value of ‘chown’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 968 | (void) chown(t->Tname, t->Tuid, t->Tgid);
> |^
> supcmeat.c:1030:24: warning: ignoring return value of ‘chown’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 1030 | (void) chown(t->Tname, t->Tuid, t->Tgid);
> |^
> supcmeat.c: In function ‘copyfile’:
> supcmeat.c:1152:32: warning: ignoring return value of ‘chdir’ declared with
> attribute ‘warn_unused_result’ [-Wunused-r
Bug#987406: marked as done (planner has mailcap entries with quoted %-escapes)
Your message dated Sat, 13 Apr 2024 08:36:03 + with message-id and subject line Bug#987406: fixed in planner 0.14.92-1 has caused the Debian Bug report #987406, regarding planner has mailcap entries with quoted %-escapes 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.) -- 987406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: planner Version: 0.14.6-9 Tags: patch, security Dear Maintainer, the planner package has mailcap entries with quoted %-escapes. That is considered unsafe. Proper escaping should be left to the programs using the entry. This Lintian tag is triggered: https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html See also grave bug #930908, which was recently closed because "a Lintian test already exists": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908 I'm using the "security" tag because the affected rules in combination with certain mail user agents (or document openers) are the cause of a shell command injection vulnerability. If you need more information let me know. Thanks, MNZ diff -ru a/debian/planner.mime b/debian/planner.mime --- a/debian/planner.mime 2013-04-09 09:17:18.0 +0200 +++ b/debian/planner.mime 2021-04-23 11:10:50.218473457 +0200 @@ -1 +1 @@ -application/x-planner; planner '%s'; edit=planner '%s'; description="Planner document"; test=test "$DISPLAY" != ""; nametemplate=%s.planner +application/x-planner; planner %s; edit=planner %s; description="Planner document"; test=test "$DISPLAY" != ""; nametemplate=%s.planner --- End Message --- --- Begin Message --- Source: planner Source-Version: 0.14.92-1 Done: Shriram Ravindranathan We believe that the bug you reported is fixed in the latest version of planner, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shriram Ravindranathan (supplier of updated planner 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: Wed, 28 Feb 2024 14:18:28 + Source: planner Architecture: source Version: 0.14.92-1 Distribution: unstable Urgency: medium Maintainer: Shriram Ravindranathan Changed-By: Shriram Ravindranathan Closes: 892919 987406 1062785 Changes: planner (0.14.92-1) unstable; urgency=medium . * New upstream version 0.14.92 * New Maintainer (Closes: #892919) * d/control: - Bump Standards-Version to 4.6.2 - Bump debhelper-compat version to 13 - Add new maintainer's name to maintainer field - Add VCS information * d/copyright: - Change source url to use https - Add new authors' copyright details - Update copyright years - Add new maintainer to copyright field - Add Upstream-Contact details * d/watch: - Bump watch version to 4 * Add d/upstream/metadata * Add libplanner-*.so symlink to not-installed * Add usr/share/GConf to planner-data.install * Add planner.lintian-overrides (unnecessary ldconfig activation) * Add planner-data.lintian-overrides (missing desktop command) . [Helmut Grohne] * d/rules: Fix FTCBFS, skip gtkdoc in arch-only build (Closes: #1062785) . [Marriott NZ] * d/planner.mime: Remove quoted placeholder from mailcap entry. Fixes lintian warning (Closes: #987406) Checksums-Sha1: 20c20632aa72b5006d2f26c31a1af3810f5be313 1945 planner_0.14.92-1.dsc 63be450ae11ee15c03b04e20bea5305089f0c33a 3888436 planner_0.14.92.orig.tar.xz c7abfa3ea5aaa54d6ee85744dc446a09af47a5ea 13292 planner_0.14.92-1.debian.tar.xz 383da805d3dc2733bd5c41f0edad1f968112793b 15284 planner_0.14.92-1_source.buildinfo Checksums-Sha256: 93201d945a47bbca2b70c8ac13fd204d0525974c5a6553e9f101b4c232cd1f7f 1945 planner_0.14.92-1.dsc fda2a7ef5db69d746fb7f3f164d060e042dd400e537ac0e535e932e369d0d833 3888436 planner_0.14.92.orig.tar.xz 2731072f971e7cebd70f31c62ada7a08a9c06fdc899f6bbe57740b366dde2807 13292 planner_0.14.92-1.debian.tar.xz ceb2b738dc40a236849d9f15ce71df327ff4e751cf04bc5fa6aad67c0f3f8c55 15
Bug#1062785: marked as done (planner FTCBFS: fails during gtk-doc-scan)
Your message dated Sat, 13 Apr 2024 08:36:03 + with message-id and subject line Bug#1062785: fixed in planner 0.14.92-1 has caused the Debian Bug report #1062785, regarding planner FTCBFS: fails during gtk-doc-scan 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.) -- 1062785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: planner Version: 0.14.91-3 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs planner fails to cross build from source, because it fails running the gtk-doc scanner with an Exec format error. Fortunately, the documentation is split out to an Arch:all package. Hence, we can fix the cross build by disabling gtk-doc in arch-only builds. I'm attaching a patch for your convenience. Helmut --- planner-0.14.91/debian/changelog +++ planner-0.14.91/debian/changelog @@ -1,3 +1,9 @@ +planner (0.14.91-4) UNRELEASED; urgency=medium + + * Fix FTCBFS: Skip gtkdoc in arch-only build. (Closes: #-1) + + -- Helmut Grohne Sat, 03 Feb 2024 08:56:18 +0100 + planner (0.14.91-3) unstable; urgency=medium * QA upload --- planner-0.14.91/debian/rules +++ planner-0.14.91/debian/rules @@ -6,7 +6,7 @@ dh $@ override_dh_auto_configure: - dh_auto_configure -- -Dgtk_doc=true + dh_auto_configure -- -Dgtk_doc=$(if $(filter planner-doc,$(shell dh_listpackages)),true,false) override_dh_shlibdeps: dh_shlibdeps -l$(CURDIR)/debian/planner/usr/lib/$(DEB_HOST_MULTIARCH)/planner --- End Message --- --- Begin Message --- Source: planner Source-Version: 0.14.92-1 Done: Shriram Ravindranathan We believe that the bug you reported is fixed in the latest version of planner, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shriram Ravindranathan (supplier of updated planner 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: Wed, 28 Feb 2024 14:18:28 + Source: planner Architecture: source Version: 0.14.92-1 Distribution: unstable Urgency: medium Maintainer: Shriram Ravindranathan Changed-By: Shriram Ravindranathan Closes: 892919 987406 1062785 Changes: planner (0.14.92-1) unstable; urgency=medium . * New upstream version 0.14.92 * New Maintainer (Closes: #892919) * d/control: - Bump Standards-Version to 4.6.2 - Bump debhelper-compat version to 13 - Add new maintainer's name to maintainer field - Add VCS information * d/copyright: - Change source url to use https - Add new authors' copyright details - Update copyright years - Add new maintainer to copyright field - Add Upstream-Contact details * d/watch: - Bump watch version to 4 * Add d/upstream/metadata * Add libplanner-*.so symlink to not-installed * Add usr/share/GConf to planner-data.install * Add planner.lintian-overrides (unnecessary ldconfig activation) * Add planner-data.lintian-overrides (missing desktop command) . [Helmut Grohne] * d/rules: Fix FTCBFS, skip gtkdoc in arch-only build (Closes: #1062785) . [Marriott NZ] * d/planner.mime: Remove quoted placeholder from mailcap entry. Fixes lintian warning (Closes: #987406) Checksums-Sha1: 20c20632aa72b5006d2f26c31a1af3810f5be313 1945 planner_0.14.92-1.dsc 63be450ae11ee15c03b04e20bea5305089f0c33a 3888436 planner_0.14.92.orig.tar.xz c7abfa3ea5aaa54d6ee85744dc446a09af47a5ea 13292 planner_0.14.92-1.debian.tar.xz 383da805d3dc2733bd5c41f0edad1f968112793b 15284 planner_0.14.92-1_source.buildinfo Checksums-Sha256: 93201d945a47bbca2b70c8ac13fd204d0525974c5a6553e9f101b4c232cd1f7f 1945 planner_0.14.92-1.dsc fda2a7ef5db69d746fb7f3f164d060e042dd400e537ac0e535e932e369d0d833 3888436 planner_0.14.92.orig.tar.xz 2731072f971e7cebd70f31c62ada7a08a9c06fdc899f6bbe57740b366dde2807 13292 planner_0.14.92-1.debian.tar.xz ceb2b738dc40a236849d9f15ce71df327ff4e751cf04bc5fa6aad67c0f3f8c55 15284 planner_0.14.92-1_source.buildinfo Files: 5c6cc54e104a3119b67df0baa9eab072 1945 gnome optional planner_0.14.92-1.dsc 6da4c5b199bb269ab0bba3157b8cd9d0
Bug#1042866: marked as done (planner: Frequent segmentation faults)
Your message dated Sat, 13 Apr 2024 10:20:09 +0200 with message-id <56ce224f-e638-4843-a95a-20a928d54...@debian.org> and subject line Re: planner: Frequent segmentation faults has caused the Debian Bug report #1042866, regarding planner: Frequent segmentation faults 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.) -- 1042866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: planner Version: 0.14.91-2 Severity: important Dear Maintainer, (This seems to be a different segfault from #928029) planner seems to segfault randomly at different times after being used for a few seconds to a few minutes. This is one I managed to reproduce when trying to remove a resource I'd just added (it was an accident, I didn't mean to hit the delete icon but the one next to it to add another resource). However, I've seen others I haven't been able to reproduce reliably. To reproduce: -- start planner -- Select 'Resources' -- Add a resource, and insert its name -- hit the 'delete resource' icon Thread 1 "planner" received signal SIGSEGV, Segmentation fault. (gdb) bt #0 0x in () #1 0x77de93d8 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x77dfc407 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x77e02c97 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x77fa9a67 in mrp_project_remove_resource (project=0x557971d0, resource=0x55be4580) at ../libplanner/mrp-project.c:1414 #6 0x555775fe in resource_cmd_remove_do (cmd_base=0x55ad0b40) at ../src/planner-resource-view.c:861 #7 0x55585290 in cmd_manager_insert (manager=0x556d8b20, cmd=cmd@entry=0x55ad0b40, run_do=run_do@entry=1) at ../src/planner-cmd-manager.c:353 #8 0x5558536d in planner_cmd_manager_insert_and_do (manager=, cmd=cmd@entry=0x55ad0b40) at ../src/planner-cmd-manager.c:371 #9 0x55579ac1 in resource_cmd_remove (resource=0x55be4580, view=0x557ef680) at ../src/planner-resource-view.c:920 #10 resource_view_remove_resource_cb (action=, data=0x557ef680) at ../src/planner-resource-view.c:938 #11 0x77de93d8 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x77dfbede in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x77e02c97 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x77789b40 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #16 0x776f2e69 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x774d8650 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x774d68f0 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #25 0x77495a09 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #26 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #28 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x775adb06 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x77dec412 in g_cclosure_marshal_VOID__BOXEDv () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #31 0x77de95d1 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #32 0x77e02fdf in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #33 0x77e031bf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #34 0x775aabf3 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #35 0x775ac1f3 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #36 0x775af362 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #37 0x7757489d in gtk_event_control
Processed: working on a fix
Processing commands for cont...@bugs.debian.org: > reassign 1067639 libdb5.3t64 Bug #1067639 [sasl2-bin] sasl2-bin: terminates with smashed stack Bug reassigned from package 'sasl2-bin' to 'libdb5.3t64'. No longer marked as found in versions cyrus-sasl2/2.1.28+dfsg1-5. Ignoring request to alter fixed versions of bug #1067639 to the same values previously set > affects 1067639 sasl2-bin Bug #1067639 [libdb5.3t64] sasl2-bin: terminates with smashed stack Added indication that 1067639 affects sasl2-bin > tags 1067639 + pending Bug #1067639 [libdb5.3t64] sasl2-bin: terminates with smashed stack Added tag(s) pending. > outlook 1067639 working on a fix and will QA upload once tested Outlook recorded from message bug 1067639 message > thanks Stopping processing here. Please contact me if you need assistance. -- 1067639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1044421: marked as done (ftpcopy: Fails to build source after successful build)
Your message dated Fri, 12 Apr 2024 18:49:07 + with message-id and subject line Bug#1044421: fixed in ftpcopy 0.6.7-7 has caused the Debian Bug report #1044421, regarding ftpcopy: Fails to build source after successful build 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.) -- 1044421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ftpcopy Version: 0.6.7-6 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package ftpcopy > dpkg-buildpackage: info: source version 0.6.7-6 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bastian Germann > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean >dh_auto_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building ftpcopy using existing ./ftpcopy_0.6.7.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: error: cannot represent change to compile/dns_packet.c: > dpkg-source: error: new version is symlink to src/dns_packet.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/socket_bind.c: > dpkg-source: error: new version is symlink to src/socket_bind.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/stralloc_opys.c: > dpkg-source: error: new version is symlink to src/stralloc_opys.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/tai.h: > dpkg-source: error: new version is symlink to src/tai.h > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/ip4_scan.c: > dpkg-source: error: new version is symlink to src/ip4_scan.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/ip6_scan.c: > dpkg-source: error: new version is symlink to src/ip6_scan.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/dns_ip64.c: > dpkg-source: error: new version is symlink to src/dns_ip64.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/stralloc_opyb.c: > dpkg-source: error: new version is symlink to src/stralloc_opyb.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/conf-cflags: > dpkg-source: error: new version is symlink to src/conf-cflags > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/buffer_put.c: > dpkg-source: error: new version is symlink to src/buffer_put.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/inq_winsize.c: > dpkg-source: error: new version is symlink to src/inq_winsize.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/error_str.c: > dpkg-source: error: new version is symlink to src/error_str.c > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot represent change to compile/ndelay.h: > dpkg-source: error: new version is symlink to src/ndelay.h > dpkg-source: error: old version is nonexistent > dpkg-source: error: cannot
Bug#1066223: marked as done (ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration])
Your message dated Fri, 12 Apr 2024 18:49:07 +
with message-id
and subject line Bug#1066223: fixed in ftpcopy 0.6.7-7
has caused the Debian Bug report #1066223,
regarding ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of
function ‘_exit’ [-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.)
--
1066223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ftpcopy
Version: 0.6.7-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):
> make[2]: Entering directory '/<>'
> ./package/compile
> Linking ./src/* into ./compile...
> Compiling everything in ./compile...
> gmake[3]: Entering directory '/<>/compile'
> cmp: auto-compiler-config.stamp: No such file or directory
> configuration has changed
> conftest-1663389.c: In function ‘main’:
> conftest-1663389.c:6:12: warning: format ‘%d’ expects argument of type ‘int’,
> but argument 2 has type ‘long unsigned int’ [-Wformat=]
> 6 | printf("%d\n",8*sizeof(x));
> | ~^~~~
> |||
> |int long unsigned int
> | %ld
> gmake[4]: Entering directory '/<>/compile'
> gmake[4]: Leaving directory '/<>/compile'
> sh typesize.sh >typesize.t
> rm -f typesize.t
> touch auto-typesize.stamp
> sh find_socket_func.sh >auto-socket.t && mv auto-socket.t auto-socket.lib
> sh have_func.sh fsync "#include " "fsync(0)" "" ""
> >auto-have_fsync.h.t && mv auto-have_fsync.h.t auto-have_fsync.h
> sh have_func.sh utimes "#include " "utimes(0,0)" "" ""
> >auto-have_utimes.h.t && mv auto-have_utimes.h.t auto-have_utimes.h
> conftest1663576.c: In function ‘main’:
> conftest1663576.c:5:9: warning: argument 1 null where non-null expected
> [-Wnonnull]
> 5 | utimes(0,0)
> | ^~
> In file included from conftest1663576.c:2:
> /usr/include/x86_64-linux-gnu/sys/time.h:162:12: note: in a call to function
> ‘utimes’ declared ‘nonnull’
> 162 | extern int utimes (const char *__file, const struct timeval __tvp[2])
> |^~
> conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’
> [-Werror=implicit-function-declaration]
> 7 | _exit(0);
> | ^
> conftest1663576.c:7:9: warning: incompatible implicit declaration of built-in
> function ‘_exit’ [-Wbuiltin-declaration-mismatch]
> cc1: some warnings being treated as errors
> sh gettimeofday.sh >gettimeofday.t && mv gettimeofday.t auto-gettimeofday.lib
> gmake[3]: *** [Makefile:100: auto-gettimeofday.lib] Error 1
> gmake[3]: Leaving directory '/<>/compile'
> make[2]: *** [Makefile:2: all] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ftpcopy_0.6.7-6_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: ftpcopy
Source-Version: 0.6.7-7
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
ftpcopy, 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
Bug#991022: marked as done (dvbackup FTCBFS: builds for the build architecture)
Your message dated Fri, 12 Apr 2024 16:49:02 + with message-id and subject line Bug#991022: fixed in dvbackup 1:0.0.4-10 has caused the Debian Bug report #991022, regarding dvbackup FTCBFS: builds for the build architecture 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.) -- 991022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvbackup Version: 1:0.0.4-10 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs dvbackup fails to cross build from source, because the upstream Makefile hard codes the build architecture compiler (and strip executable). To make it cross buildable, those need to be substituted. Since debhelper automatically performs the substitution, all that is left here is making them substitutable. Please consider applying the attached patch. Helmut --- dvbackup-0.0.4.orig/Makefile +++ dvbackup-0.0.4/Makefile @@ -1,3 +1,5 @@ +CC?=gcc +STRIP?=strip #Flags for fast code: #CFLAGS=-Wall -O3 -mcpu=i686 -fomit-frame-pointer CFLAGS=-Wall -O3 -fomit-frame-pointer @@ -13,16 +15,16 @@ all: dvbackup dvconnect Makefile dvconnect: dvconnect.c Makefile - gcc $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) -DHAVE_LIBPOPT -o dvconnect dvconnect.c -lpopt -lpthread + $(CC) $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) -DHAVE_LIBPOPT -o dvconnect dvconnect.c -lpopt -lpthread dvbackup: dvbackup.c minilogo.c Makefile - gcc $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) -I/usr/include -o dvbackup dvbackup.c minilogo.c -lpopt -lm -lz + $(CC) $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) -I/usr/include -o dvbackup dvbackup.c minilogo.c -lpopt -lm -lz install: dvbackup dvconnect install dvbackup $(install_dir) install dvconnect $(install_dir) - strip $(install_dir)/dvconnect - strip $(install_dir)/dvbackup + $(STRIP) $(install_dir)/dvconnect + $(STRIP) $(install_dir)/dvbackup clean: rm dvbackup --- End Message --- --- Begin Message --- Source: dvbackup Source-Version: 1:0.0.4-10 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of dvbackup, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated dvbackup 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, 12 Apr 2024 18:29:46 +0200 Source: dvbackup Architecture: source Version: 1:0.0.4-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 991022 1066238 Changes: dvbackup (1:0.0.4-10) unstable; urgency=medium . [ Andreas Beckmann ] * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066238) * Declare Rules-Requires-Root: no. . [ Helmut Grohne ] * Fix FTCBFS. (Closes: #991022) . [ Jelmer Vernooij ] * Migrate repository from alioth to salsa. Checksums-Sha1: 15d76e059d6f5f5c3c85650116edb49765d55a3c 1906 dvbackup_0.0.4-10.dsc dcb4c98d04ccbdb32155e0dd38fb6c5b20a763f1 8892 dvbackup_0.0.4-10.debian.tar.xz c2744b8f3e1ad11545551d26da5ab4a94ab076db 5926 dvbackup_0.0.4-10_source.buildinfo Checksums-Sha256: 45c6dfd5320666d5ff27537044d5dbf9f650a1b06f2f3baeea0ca8deb1d5c87f 1906 dvbackup_0.0.4-10.dsc 2d5062a5b08703eab6063e147f057428c0ff7d3dc848ef706cb14c9bb09f6c33 8892 dvbackup_0.0.4-10.debian.tar.xz 13b772d7641d45c24baba1cd5d5bfb131c91e596aac9ad55763a55753d356f71 5926 dvbackup_0.0.4-10_source.buildinfo Files: b08370f72af8580ab7104da40833980d 1906 admin optional dvbackup_0.0.4-10.dsc 7f04a7bcf0ba2bc288a6e5ddb06ec147 8892 admin optional dvbackup_0.0.4-10.debian.tar.xz ac3951841ce4875c01473173bbd0865a 5926 admin optional dvbackup_0.0.4-10_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYZYr8QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCK3mD/9x59qA8Gvqdp00qkQ7f+SNeDYabobu9Ywa 6nL5GX+uGkQVWR1GaT/lmlwBUoMB/Scb7lCSZ1Xz7jApdHmsInSjs4NoO55gdWNz HsypJ/YuSGzeOQJJU6lF/jeD0RcdiV5oCLZw2FRXOVHw2Qt2AdYGJbGzIAjdV/t/ peYzf8K+fHmGsXIveaxs4ubpL3jIlNlG+E2x5SKSnFDQhh00OlRCZiS21RHlqC44 9e5boP8H6yJHB6keH8dXi6y96ffM1TM+HwKQU9LR
Bug#1066238: marked as done (dvbackup: FTBFS: dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])
Your message dated Fri, 12 Apr 2024 16:49:02 +
with message-id
and subject line Bug#1066238: fixed in dvbackup 1:0.0.4-10
has caused the Debian Bug report #1066238,
regarding dvbackup: FTBFS: dvconnect.c:264:33: 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.)
--
1066238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvbackup
Version: 1:0.0.4-9
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 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -fPIE -pie -Wl,-z,relro -Wl,-z,now -D_FORTIFY_SOURCE=2 -DHAVE_LIBPOPT -o
> dvconnect dvconnect.c -lpopt -lpthread
> dvconnect.c: In function ‘handle_packet’:
> dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’
> [-Werror=implicit-function-declaration]
> 264 | memcpy(p_out, data + 12, 480);
> | ^~
> dvconnect.c:22:1: note: include ‘’ or provide a declaration of
> ‘memcpy’
>21 | #include
> +++ |+#include
>22 |
> dvconnect.c:264:33: warning: incompatible implicit declaration of built-in
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
> 264 | memcpy(p_out, data + 12, 480);
> | ^~
> dvconnect.c:264:33: note: include ‘’ or provide a declaration of
> ‘memcpy’
> dvconnect.c: In function ‘capture_raw’:
> dvconnect.c:326:26: error: implicit declaration of function ‘strcmp’
> [-Werror=implicit-function-declaration]
> 326 | if (!filename || strcmp(filename, "-") == 0) {
> | ^~
> dvconnect.c:326:26: note: include ‘’ or provide a declaration of
> ‘strcmp’
> dvconnect.c:401:25: error: implicit declaration of function ‘memset’
> [-Werror=implicit-function-declaration]
> 401 | memset(curr, 0, v.buf_size);
> | ^~
> dvconnect.c:401:25: note: include ‘’ or provide a declaration of
> ‘memset’
> dvconnect.c:401:25: warning: incompatible implicit declaration of built-in
> function ‘memset’ [-Wbuiltin-declaration-mismatch]
> dvconnect.c:401:25: note: include ‘’ or provide a declaration of
> ‘memset’
> dvconnect.c:426:41: warning: incompatible implicit declaration of built-in
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
> 426 | memcpy(outbuf + outbuf_used,
> curr+ofs,
> | ^~
> dvconnect.c:426:41: note: include ‘’ or provide a declaration of
> ‘memcpy’
> dvconnect.c:431:41: warning: incompatible implicit declaration of built-in
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
> 431 | memcpy(outbuf + outbuf_used,
> | ^~
> dvconnect.c:431:41: note: include ‘’ or provide a declaration of
> ‘memcpy’
> dvconnect.c: In function ‘fill_buffer’:
> dvconnect.c:584:33: warning: incompatible implicit declaration of built-in
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
> 584 | memcpy(f_node->data,
> underrun_data_frame,
> | ^~
> dvconnect.c:584:33: note: include ‘’ or provide a declaration of
> ‘memcpy’
> dvconnect.c:633:25: warning: incompatible implicit declaration of built-in
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
> 633 | memcpy(p, frame + vdata, 480);
> | ^~
> dvconnect.c:633:25: note: include ‘’ or provide a declaration of
> ‘memcpy’
> dvconnect.c: In function ‘send_raw’:
> dvconnect.c:782:9
Bug#1066626: marked as done (lua-svn: FTBFS: src/luasvn.c:1306:13: error: implicit declaration of function ‘svn_prop_needs_translation’ [-Werror=implicit-function-declaration])
Your message dated Fri, 12 Apr 2024 16:25:45 + with message-id and subject line Bug#1066626: fixed in lua-svn 0.4.0-11 has caused the Debian Bug report #1066626, regarding lua-svn: FTBFS: src/luasvn.c:1306:13: error: implicit declaration of function ‘svn_prop_needs_translation’ [-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.) -- 1066626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-svn Version: 0.4.0-10 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): > /<>/debian/.dh_lua-libtool/libtool --tag=CC --mode=compile > x86_64-linux-gnu-gcc -c -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 -I/usr/include/lua5.1 -I > /usr/include/subversion-1 -DLINUX -D_REENTRANT -D_GNU_SOURCE > -I/usr/include/apr-1.0 -Wall -Wextra -o > /<>/5.1-svn/src/luasvn.lo src/luasvn.c > libtool: compile: x86_64-linux-gnu-gcc -c -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 > -I/usr/include/lua5.1 -I /usr/include/subversion-1 -DLINUX -D_REENTRANT > -D_GNU_SOURCE -I/usr/include/apr-1.0 -Wall -Wextra src/luasvn.c -fPIC -DPIC > -o /<>/5.1-svn/src/.libs/luasvn.o > src/luasvn.c: In function ‘init_pool’: > src/luasvn.c:58:9: warning: ‘svn_dso_initialize’ is deprecated > [-Wdeprecated-declarations] >58 | svn_dso_initialize (); > | ^~ > In file included from src/luasvn.c:5: > /usr/include/subversion-1/svn_dso.h:70:1: note: declared here >70 | svn_dso_initialize(void); > | ^~ > src/luasvn.c: In function ‘init_function’: > src/luasvn.c:96:9: warning: ‘svn_client_create_context’ is deprecated > [-Wdeprecated-declarations] >96 | err = svn_client_create_context (ctx, *pool); > | ^~~ > In file included from src/luasvn.c:4: > /usr/include/subversion-1/svn_client.h:1117:1: note: declared here > 1117 | svn_client_create_context(svn_client_ctx_t **ctx, > | ^ > src/luasvn.c:105:9: warning: ‘svn_cmdline_setup_auth_baton’ is deprecated > [-Wdeprecated-declarations] > 105 | err = svn_cmdline_setup_auth_baton(, > | ^~~ > In file included from src/luasvn.c:8: > /usr/include/subversion-1/svn_cmdline.h:405:1: note: declared here > 405 | svn_cmdline_setup_auth_baton(svn_auth_baton_t **ab, > | ^~~~ > src/luasvn.c: In function ‘log_msg_func2’: > src/luasvn.c:179:54: warning: unused parameter ‘commit_items’ > [-Wunused-parameter] > 179 |const apr_array_header_t *commit_items, > |~~^~~~ > src/luasvn.c: In function ‘l_add’: > src/luasvn.c:236:9: warning: ‘svn_path_canonicalize’ is deprecated > [-Wdeprecated-declarations] > 236 | path = svn_path_canonicalize (path, pool); > | ^~~~ > In file included from src/luasvn.c:6: > /usr/include/subversion-1/svn_path.h:284:1: note: declared here > 284 | svn_path_canonicalize(const char *path, apr_pool_t *pool); > | ^ > src/luasvn.c:238:9: warning: ‘svn_client_add3’ is deprecated > [-Wdeprecated-declarations] > 238 | err = svn_client_add3 (path, recursive, force, no_ignore, > ctx, pool); > | ^~~ > /usr/include/subversion-1/svn_client.h:1714:1: note: declared here > 1714 | svn_client_add3(const char *path, > | ^~~ > src/luasvn.c: In function ‘l_cat’: > src/luasvn.c:279:9: warning: ‘svn_path_canonicalize’ is deprecated > [-Wdeprecated-de
