Bug#1073782: marked as done (sigscheme: FTBFS: Add support for LoongArch)
Your message dated Wed, 18 Sep 2024 08:51:23 + with message-id and subject line Bug#1073782: fixed in sigscheme 0.9.1-3 has caused the Debian Bug report #1073782, regarding sigscheme: FTBFS: Add support for LoongArch 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.) -- 1073782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sigscheme Version: 0.9.1-2 Severity: normal Tags: FTBFS patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, Compiling the sigscheme failed for loong64 in the Debian Package Auto-Building environment. The build error log is as follows, ``` In file included from ./include/private/gc_priv.h:68, from mach_dep.c:16: ./include/private/gcconfig.h:496:5: error: #error "The collector has not been ported to this machine/OS combination." 496 | # error "The collector has not been ported to this machine/OS combination." | ^ .. ``` The full log can be found at https://buildd.debian.org/status/logs.php?pkg=sigscheme&ver=0.9.1-2&arch=loong64. Build failed 14 times. Please consider the patch I attached. I have built sigscheme successfully in my local ENV. ``` .. dpkg-deb: building package 'libgcroots-dev' in '../libgcroots-dev_0.9.1-2+loong64_loong64.deb'. dpkg-genbuildinfo -O../sigscheme_0.9.1-2+loong64_loong64.buildinfo dpkg-genchanges -O../sigscheme_0.9.1-2+loong64_loong64.changes dpkg-genchanges: info: not including original source code in upload dpkg-source --after-build . ``` Your opinions are welcome. Thanks, Dandan Zhang diff -Nru sigscheme-0.9.1/debian/changelog sigscheme-0.9.1/debian/changelog --- sigscheme-0.9.1/debian/changelog2022-06-27 00:39:24.0 + +++ sigscheme-0.9.1/debian/changelog2024-06-18 09:22:24.0 + @@ -1,3 +1,9 @@ +sigscheme (0.9.1-2+loong64) unreleased; urgency=medium + + * Add support for LoongArch. + + -- Dandan Zhang Tue, 18 Jun 2024 09:22:24 + + sigscheme (0.9.1-2) unstable; urgency=medium * QA upload. diff -Nru sigscheme-0.9.1/debian/patches/series sigscheme-0.9.1/debian/patches/series --- sigscheme-0.9.1/debian/patches/series 2020-08-25 05:45:19.0 + +++ sigscheme-0.9.1/debian/patches/series 2024-06-18 09:22:24.0 + @@ -1,3 +1,4 @@ test-gc-protect-coll-0.8.3 test-storage-coll-0.8.3 support-automake-test-log-driver +sigscheme-add-LoongArch-support.patch diff -Nru sigscheme-0.9.1/debian/patches/sigscheme-add-LoongArch-support.patch sigscheme-0.9.1/debian/patches/sigscheme-add-LoongArch-support.patch --- sigscheme-0.9.1/debian/patches/sigscheme-add-LoongArch-support.patch 1970-01-01 00:00:00.0 + +++ sigscheme-0.9.1/debian/patches/sigscheme-add-LoongArch-support.patch 2024-06-18 09:22:24.0 + @@ -0,0 +1,43 @@ +Description: Add support for LoongArch + . + sigscheme (0.9.1-2+loong64) unreleased; urgency=medium + . + * Add support for LoongArch. +Author: Dandan Zhang + +--- +Last-Update: 2024-06-18 + +--- sigscheme-0.9.1.orig/libgcroots/include/private/gcconfig.h sigscheme-0.9.1/libgcroots/include/private/gcconfig.h +@@ -483,6 +483,10 @@ + # define RISCV + # define mach_type_known + # endif ++# if defined(__loongarch__) && defined(LINUX) ++# define LOONGARCH ++# define mach_type_known ++# endif + + /* Feel free to add more clauses here */ + +@@ -1336,6 +1340,19 @@ + # endif + # endif /* RISCV */ + ++# ifdef LOONGARCH ++# define MACH_TYPE "LoongArch" ++# define CPP_WORDSZ _LOONGARCH_SZPTR ++# define ALIGNMENT (_LOONGARCH_SZPTR/8) ++# ifdef LINUX ++# define OS_TYPE "LINUX" ++ extern int __data_start[]; ++# define DATASTART ((ptr_t)__data_start) ++# define LINUX_STACKBOTTOM ++# define DYNAMIC_LOADING ++# endif ++# endif /* LoongArch */ ++ + # ifdef NS32K + # define MACH_TYPE "NS32K" + # define ALIGNMENT 4 --- End Message --- --- Begin Message --- Source: sigscheme Source-Version: 0.9.1-3 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of sigscheme, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distr
Processed: bts
Processing commands for cont...@bugs.debian.org: > severity 1039898 serious Bug #1039898 [libapache2-mod-qos] mod-qos can not be enabled correctly for apache2 in Debian 12 Severity set to 'serious' from 'critical' > close 1039898 11.74-1 Bug #1039898 [libapache2-mod-qos] mod-qos can not be enabled correctly for apache2 in Debian 12 Ignoring request to alter fixed versions of bug #1039898 to the same values previously set Bug #1039898 [libapache2-mod-qos] mod-qos can not be enabled correctly for apache2 in Debian 12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1039898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075240: marked as done (lua-svn: ftbfs with GCC-14)
Your message dated Sun, 15 Sep 2024 22:51:05 + with message-id and subject line Bug#1075240: fixed in lua-svn 0.4.0-12 has caused the Debian Bug report #1075240, regarding lua-svn: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1075240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lua-svn Version: 0.4.0-11 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/lua-svn_0.4.0-11_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] src/luasvn.c: In function ‘l_revprop_set’: src/luasvn.c:1409:9: warning: ‘svn_path_canonicalize’ is deprecated [-Wdeprecated-declarations] 1409 | url = svn_path_canonicalize (url, pool); | ^~~ /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:1418:25: warning: ‘svn_subst_translate_string’ is deprecated [-Wdeprecated-declarations] 1418 | err = svn_subst_translate_string (&sstring, sstring, APR_LOCALE_CHARSET, pool); | ^~~ /usr/include/subversion-1/svn_subst.h:687:14: note: declared here 687 | svn_error_t *svn_subst_translate_string(svn_string_t **new_value, | ^~ src/luasvn.c:1422:17: warning: ‘svn_client_revprop_set’ is deprecated [-Wdeprecated-declarations] 1422 | err = svn_client_revprop_set (propname_utf8, sstring, url, &revision, &rev, force, ctx, pool); | ^~~ /usr/include/subversion-1/svn_client.h:6183:1: note: declared here 6183 | svn_client_revprop_set(const char *propname, | ^~ src/luasvn.c:1424:17: warning: ‘svn_client_revprop_set’ is deprecated [-Wdeprecated-declarations] 1424 | err = svn_client_revprop_set (propname_utf8, NULL, url, &revision, &rev, force, ctx, pool); | ^~~ /usr/include/subversion-1/svn_client.h:6183:1: note: declared here 6183 | svn_client_revprop_set(const char *propname, | ^~ src/luasvn.c: In function ‘status_func’: src/luasvn.c:1609:9: warning: ‘svn_path_local_style’ is deprecated [-Wdeprecated-declarations] 1609 | print_status (svn_path_local_style (path, pool), | ^~~~ /usr/include/subversion-1/svn_path.h:82:1: note: declared here 82 | svn_path_local_style(const char *path, apr_pool_t *pool); | ^~~~ src/luasvn.c: In function ‘l_status’: src/luasvn.c:1669:9: warning: ‘svn_path_canonicalize’ is deprecated [-Wdeprecated-declarations] 1669 | path = svn_path_canonicalize (path, pool); | ^~~~ /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:1679:9: warning: ‘svn_client_status2’ is deprecated [-Wdeprecated-declarations] 1679 | err = svn_client_status2 (&rev, path, &revision, status_func, &baton, | ^~~ /usr/include/subversion-1/svn_client.h:2724:1: note: declared here 2724 | svn_client_status2(svn_revnum_t *result_rev, | ^~ src/luasvn.c: In function ‘l_update’: src/luasvn.c:1725:9: warning: ‘svn_path_canonicalize’ is deprecated [-Wdeprecated-declarations] 1725 | path = s
Bug#1047641: marked as done (pathspider: Fails to build source after successful build)
Your message dated Sat, 14 Sep 2024 14:38:45 + with message-id and subject line Bug#1081741: Removed package(s) from unstable has caused the Debian Bug report #1047641, regarding pathspider: 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.) -- 1047641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pathspider Version: 2.0.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 pathspider > dpkg-buildpackage: info: source version 2.0.1-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bastian Germann > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean --with python3,sphinxdoc --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:275: python3.11 setup.py clean > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: > UserWarning: Unknown distribution option: 'test_requires' > warnings.warn(msg) > running clean > removing '/<>/.pybuild/cpython3_3.11/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pathspider using existing > ./pathspider_2.0.1.orig.tar.gz > dpkg-source: warning: ignoring deletion of file > pathspider/tests/test_plugin_evilbit.py, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > pathspider/tests/test_plugin_udpzero.py, use --include-removal to override > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/basic.doctree: binary file contents changed > dpkg-source: error: add doc/_build/html/.doctrees/chains/basic.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/dns.doctree: binary file contents changed > dpkg-source: error: add doc/_build/html/.doctrees/chains/dns.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/dscp.doctree: binary file contents changed > dpkg-source: error: add doc/_build/html/.doctrees/chains/dscp.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/ecn.doctree: binary file contents changed > dpkg-source: error: add doc/_build/html/.doctrees/chains/ecn.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/evilbit.doctree: binary file contents changed > dpkg-source: error: add doc/_build/html/.doctrees/chains/evilbit.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to > doc/_build/html/.doctrees/chains/ic
Bug#1018434: marked as done (pathspider: build-depends on python3-nose or uses it for autopkgtest)
Your message dated Sat, 14 Sep 2024 14:38:45 + with message-id and subject line Bug#1081741: Removed package(s) from unstable has caused the Debian Bug report #1018434, regarding pathspider: build-depends on python3-nose or uses it for autopkgtest 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.) -- 1018434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pathspider Version: 2.0.1-2.1 User: python-modules-t...@lists.alioth.debian.org Usertags: nose-rm Dear Maintainer, Your package still uses nose [1], which is an obsolete testing framework for Python, dead and unmaintained since 2015 [2][3]. If you received this bug report, it means that your package either has a build-dependency on python3-nose or uses that package in debian/tests/control. If that is not the case, please reply and CC me explicitly. Please port your package to one of the alternatives: nose2 [4], pytest [5] or unittest from Python standard library [6]. There is a script called nose2pytest [7] which can assist with migrating from nose to pytest. This mass bug filing was discussed on debian-devel in [8]. [1]: https://tracker.debian.org/pkg/nose [2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad [3]: https://pypi.org/project/nose/#history [4]: https://docs.nose2.io/en/latest/ [5]: https://docs.pytest.org/en/latest/ [6]: https://docs.python.org/3/library/unittest.html [7]: https://github.com/pytest-dev/nose2pytest [8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html -- Dmitry Shachnev --- End Message --- --- Begin Message --- Version: 2.0.1-4+rm Dear submitter, as the package pathspider has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1081741 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1061212: marked as done (emscripten: Please upgrade to llvm-toolchain-18)
Your message dated Sat, 14 Sep 2024 14:35:14 + with message-id and subject line Bug#1061212: fixed in emscripten 3.1.66~dfsg-1 has caused the Debian Bug report #1061212, regarding emscripten: Please upgrade to llvm-toolchain-18 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.) -- 1061212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emscripten Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -17. This package depends on 14. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: emscripten Source-Version: 3.1.66~dfsg-1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of emscripten, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated emscripten 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: Sat, 14 Sep 2024 14:58:58 +0200 Source: emscripten Architecture: source Version: 3.1.66~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1061212 Changes: emscripten (3.1.66~dfsg-1) unstable; urgency=medium . [ Bastian Germann ] * QA upload. * d/copyright: Files-Excluded for next version. * New upstream version 3.1.61~dfsg. * Update patches for (re)moved files. * Update to llvm 18. (Closes: #1061212) * Download current emscripten-source-map.min.js. * Use llvm 18 in patches . [ Sebastian Ramacher ] * New upstream version 3.1.66~dfsg * debian/patches/Refresh patches for new upstream version * debian/missing-sources: Add new source-map-footer.js * debian/rules: Update files to add/remove executable flag Checksums-Sha1: f17f3a6c3374914d876092988b44883b3d53f255 2199 emscripten_3.1.66~dfsg-1.dsc 2b0ec2d8e8b1d942b989072ab872120106764655 5480 emscripten_3.1.66~dfsg.orig-Xtypes.tar.xz d4963741cce14c3b353ca1a7b051cb47751a363d 19176192 emscripten_3.1.66~dfsg.orig.tar.xz e308049e4a4c0709a21e0e673934e05f31bbb6ff 82572 emscripten_3.1.66~dfsg-1.debian.tar.xz 84dbcafc0a52ecfd8c75801f13d7aaadb5bc2a4f 12205 emscripten_3.1.66~dfsg-1_amd64.buildinfo Checksums-Sha256: 0da46cea470bb19f5f7ea1b3a8f88b9bb3b0d1c45c050c7600a0b502a9aeac73 2199 emscripten_3.1.66~dfsg-1.dsc 124c22ee291c12bab9041aa36b72f350ddc6c9f44c0b2b79c631acb9b4113759 5480 emscripten_3.1.66~dfsg.orig-Xtypes.tar.xz bc13eba02929fd4410e6b55aeb16d7b1fb6145305aedb2b83cd823d348354d2e 19176192 emscripten_3.1.66~dfsg.orig.tar.xz d8b4b579d00e71a11c4b463a76da7e226947e454bd0e74cb5cd0f80f7f986ec0 82572 emscripten_3.1.66~dfsg-1.debian.tar.xz a0e086691d75abbc219bef0700a54a8410c7641ea5ec8f1050e2c05ce8dffdaa 12205 emscripten_3.1.66~dfsg-1_amd64.buildinfo Files: 0eda0a6310ed7e53a4d465946b5e4b81 2199 devel optional emscripten_3.1.66~dfsg-1.dsc 784e5604eb7d102555fdc8a8f8b6241e 5480 devel optional emscripten_3.1.66~dfsg.orig-Xtypes.tar.xz 8ec310d8b06140f601d5fd6a3a8d4c59 19176192 devel optional emscripten_3.1.66~dfsg.orig.tar.xz 84c0f5678751562ab4b0d914fc6fd49b 82572 devel optional emscripten_3.1.66~dfsg-1.debian.tar.xz 7e8efeaf944b86e52de45a5153be01d2 12205 devel optional emscripten_3.1.66~dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZuWaHwAKCRAhk2s2YA/N iVB8AP9dvSYb1OsKTCU1OJmQSKeV6nvN5cjpCt/ObIizUdLvgQEA5bBhLcd7fPKR fCwrII10JMTbP+ddFJcaFiA62dNK/g4= =wlJr -END PGP SIGNATURE- pgpImwav_EfZ4.pgp Description: PGP signature --- End Message ---
Processed: tagging 1018434
Processing commands for cont...@bugs.debian.org: > tags 1018434 + wontfix Bug #1018434 [src:pathspider] pathspider: build-depends on python3-nose or uses it for autopkgtest Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 1018434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018463: marked as done (python-bayespy: build-depends on python3-nose or uses it for autopkgtest)
Your message dated Sat, 14 Sep 2024 13:20:25 + with message-id and subject line Bug#1018463: fixed in python-bayespy 0.6.2-1 has caused the Debian Bug report #1018463, regarding python-bayespy: build-depends on python3-nose or uses it for autopkgtest 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.) -- 1018463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-bayespy Version: 0.5.22-2 User: python-modules-t...@lists.alioth.debian.org Usertags: nose-rm Dear Maintainer, Your package still uses nose [1], which is an obsolete testing framework for Python, dead and unmaintained since 2015 [2][3]. If you received this bug report, it means that your package either has a build-dependency on python3-nose or uses that package in debian/tests/control. If that is not the case, please reply and CC me explicitly. Please port your package to one of the alternatives: nose2 [4], pytest [5] or unittest from Python standard library [6]. There is a script called nose2pytest [7] which can assist with migrating from nose to pytest. This mass bug filing was discussed on debian-devel in [8]. [1]: https://tracker.debian.org/pkg/nose [2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad [3]: https://pypi.org/project/nose/#history [4]: https://docs.nose2.io/en/latest/ [5]: https://docs.pytest.org/en/latest/ [6]: https://docs.python.org/3/library/unittest.html [7]: https://github.com/pytest-dev/nose2pytest [8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html -- Dmitry Shachnev --- End Message --- --- Begin Message --- Source: python-bayespy Source-Version: 0.6.2-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-bayespy, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-bayespy 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: Sat, 14 Sep 2024 14:21:07 +0200 Source: python-bayespy Architecture: source Version: 0.6.2-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1018463 Changes: python-bayespy (0.6.2-1) unstable; urgency=medium . * QA upload. * New upstream version 0.6.2 * Replace Nose with Pytest (Closes: #1018463) Checksums-Sha1: a800d7af8780f69933fe2a48ed92e6674f446348 2245 python-bayespy_0.6.2-1.dsc d6832926c5db1ee170c40981b248b1ff872ec9c6 405302 python-bayespy_0.6.2.orig.tar.gz a172d3740eca5417a0c1ac9ccf7470e40bdaffbd 23604 python-bayespy_0.6.2-1.debian.tar.xz 559fd3c844d1f1ee5f50fb6b5eef82a5cc76ef30 12258 python-bayespy_0.6.2-1_source.buildinfo Checksums-Sha256: 5e389c36cc1eec047e9ae25cd6fa7abb8d440a235ad9c93f2a9a021cae21db3d 2245 python-bayespy_0.6.2-1.dsc 593f94ffd7dea5856c9836fec30c0b43f2245a1e5d6b6662d1a6c2a567489a2d 405302 python-bayespy_0.6.2.orig.tar.gz 86ee4f0942d6c2ddb7d64e6ebe53b3647c1a6f79f161651218f314e9eacf23c5 23604 python-bayespy_0.6.2-1.debian.tar.xz 240da31b717a985047772465726983b50377452fd959dcabc9f436bbfb895ac2 12258 python-bayespy_0.6.2-1_source.buildinfo Files: bbd3f49a8bac48841f84050af86c2371 2245 python optional python-bayespy_0.6.2-1.dsc 1cf94fedde856a1a25cce1136b5a7312 405302 python optional python-bayespy_0.6.2.orig.tar.gz e0c2570b12202fa49c776ac02a6140c1 23604 python optional python-bayespy_0.6.2-1.debian.tar.xz c29f0f6ce50b5a9eea40510abc4420e4 12258 python optional python-bayespy_0.6.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmbliWcRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBrkSw/+OMSCQiqa2O5auh7p6ByVZPj8YBted+Bf C7M3YLVXF5A1wZBEsDqlg5A+8Q7SN6VoP9RnnhDMnT1083Pd5FvD5s9YXRQthA7A 04DJxr7FRyDiSFjrxoyD0Ip74KrS+npxafrIUg+nZE08g1y5hMPLLhlx++lxBiJu phMk+3zCn+CJMZICvpU81a15YZ6Vq2U5S6t5XdPra6+LGi6HM5BtvUQtGWbUAMQ2 hFnPjbqiHrotizhMnuHUs55isg5uig26PnZBJLkcrsttxYbU+QozOuU1pVWTgbRe 2RfP2gfW1dWpGs/mWvzNY5EGCj7H3iD2xt2qBBi3CGynN2DeCq9/mRACEk6LRyQd ajKwXMVAdBBXXsx+BHkjZp3lCPE
Bug#1075639: marked as done (wily: ftbfs with GCC-14)
Your message dated Fri, 13 Sep 2024 22:01:35 + with message-id and subject line Bug#1075639: fixed in wily 0.13.42-3 has caused the Debian Bug report #1075639, regarding wily: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1075639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wily Version: 0.13.42-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/wily_0.13.42-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] make[3]: warning: -j8 forced in submake: resetting jobserver mode. gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o arith.o arith.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o frptofchar.o frptofchar.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o frselect.o frselect.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o frstr.o frstr.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o connect.o connect.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o balloc.o balloc.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o bitblt.o bitblt.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o msg.o msg.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o bitbltclip.o bitbltclip.c arith.c:110:1: error: return type defaults to ‘int’ [-Wimplicit-int] 110 | eqpt(Point p, Point q) | ^~~~ gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o util.o util.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror
Bug#1080998: marked as done (gthumb FTBFS on 32 bit architectures with 64 bit time_t with gcc 14)
Your message dated Fri, 13 Sep 2024 19:04:54 +
with message-id
and subject line Bug#1080998: fixed in gthumb 3:3.12.6-2
has caused the Debian Bug report #1080998,
regarding gthumb FTBFS on 32 bit architectures with 64 bit time_t with gcc 14
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.)
--
1080998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gthumb
Version: 3:3.12.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gthumb&ver=3%3A3.12.6-1%2Bb3
...
../gthumb/main-migrate-catalogs.c: In function ‘migration_for_each_file’:
../gthumb/main-migrate-catalogs.c:316:57: error: passing argument 1 of
‘localtime’ from incompatible pointer type [-Wincompatible-pointer-types]
316 | tm = localtime (&date);
| ^
| |
| long int *
In file included from /usr/include/features.h:510,
from
/usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,
from /usr/include/string.h:26,
from ../gthumb/main-migrate-catalogs.c:23:
/usr/include/time.h:141:19: note: expected ‘const time_t *’ {aka ‘const long
long int *’} but argument is of type ‘long int *’
141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
| ^~
...
--- End Message ---
--- Begin Message ---
Source: gthumb
Source-Version: 3:3.12.6-2
Done: Pino Toscano
We believe that the bug you reported is fixed in the latest version of
gthumb, 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 1080...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pino Toscano (supplier of updated gthumb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 13 Sep 2024 19:54:12 +0200
Source: gthumb
Architecture: source
Version: 3:3.12.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Pino Toscano
Closes: 1080998
Changes:
gthumb (3:3.12.6-2) unstable; urgency=medium
.
* QA upload.
* d/p/b/b48e34c436eb59877b0fe75ba3bf724c0de4dc36.patch: backport upstream
change to fix a time_t usage. (Closes: #1080998)
* Update lintian overrides.
* Drop autopkgtest: it builds gthumb from sources and run the unit tests of
the just built sources, never using the already packaged bits.
Checksums-Sha1:
4467ee43ca83cf0712b8b83417f3adae4cc2 2275 gthumb_3.12.6-2.dsc
edc8e808c2c37db16f8268dbf98ef9c4f949982a 32572 gthumb_3.12.6-2.debian.tar.xz
acf59e0bb1166ceb08b2963aa8ecfb62d4c74205 15169 gthumb_3.12.6-2_source.buildinfo
Checksums-Sha256:
eaf289449db7e50435ba81bbfc3d87fcb92d5f3ac47cf8ebb8eaaa95050fa74e 2275
gthumb_3.12.6-2.dsc
b25f112b1c62c7e9c8c3f8b84d4a6aeeb0145aed688419997fde6922e9bac4ff 32572
gthumb_3.12.6-2.debian.tar.xz
2dbb5e8f4afed653f0adf31bc8f5126cad1e206776d0feb4f13f877d59953f66 15169
gthumb_3.12.6-2_source.buildinfo
Files:
67f4224e732ca863d3bb9591ff72a48e 2275 gnome optional gthumb_3.12.6-2.dsc
e60476abfcbbec6bf23319464567a3aa 32572 gnome optional
gthumb_3.12.6-2.debian.tar.xz
220e71762b0f035c13baebe644a8e20c 15169 gnome optional
gthumb_3.12.6-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmbkfJ4ACgkQLRkciEOx
P017Ew/8CEHkH6oBXm+C6Gy+GkqglvFT5ta2tptJPJvpp/9cfwtiKPrHZPpDvlNt
aASxrbnUtexcR9b4rkMNy1e1YpeBzaGa6V0Ajc8H8nMKuLjLABBHbNVRclyUoZWq
zEgWhbW2BK7bLqzEH47tRXaY0N7wEyMKPcXaMsPcsbErJN1SjSXXJ4wRBU1xUsHQ
laG7eqFEtQGHQHqP9QpnvyjtedtcheWFjOW9sT6qDo5/i/96lKAGEyRtkuOAQOYG
vVS2MjSEfiQtTz1t680HabE/GxVDBVwpHtu0KsdfKkJ9r85/G+P+1bVHzUDTXkIb
Dx5Z+p8pqrXuDIvE9GsdPfKvM0Yx4Y+SO+ETu378tb8aWLvSkhNJ2/J/ZFJFQb8l
QMmF7BZsmkveJHsg8VQL7uwZXBzz7iybVVPaT4oH6dRDMlm+oRtUpILlj1mi9uTS
m25AUDnNzqQ1Mhpy9p7I6oGQsODZrg+ISjw39Fcv5PwDTzOkr5EElKyoa8Klqk5x
7rM25z3ajusUZjZE/PFJdRwTJTv2rKGG73gHFZo/8wGcuzlMcswA3QbRuMcHjDOx
oqYfS+ry0
Processed: fixed 1065892 in gthumb/3:3.12.6-1, closing 1065892
Processing commands for cont...@bugs.debian.org: > fixed 1065892 gthumb/3:3.12.6-1 Bug #1065892 [gthumb] gthumb: please package upstream 3.12.6 Marked as fixed in versions gthumb/3:3.12.6-1. > close 1065892 Bug #1065892 [gthumb] gthumb: please package upstream 3.12.6 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1065892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1064435 in gthumb/3:3.12.5-1, closing 1064435
Processing commands for cont...@bugs.debian.org: > fixed 1064435 gthumb/3:3.12.5-1 Bug #1064435 [gthumb] gthumb: please package new upstream 3.12.5 Marked as fixed in versions gthumb/3:3.12.5-1. > close 1064435 Bug #1064435 [gthumb] gthumb: please package new upstream 3.12.5 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1064435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1080998
Processing commands for cont...@bugs.debian.org: > tags 1080998 + upstream fixed-upstream pending Bug #1080998 [src:gthumb] gthumb FTBFS on 32 bit architectures with 64 bit time_t with gcc 14 Added tag(s) pending, upstream, and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1080998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075346: marked as done (openwince-jtag: ftbfs with GCC-14)
Your message dated Fri, 13 Sep 2024 10:34:22 +
with message-id
and subject line Bug#1075346: fixed in openwince-jtag 0.5.1-11
has caused the Debian Bug report #1075346,
regarding openwince-jtag: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1075346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openwince-jtag
Version: 0.5.1-10
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/openwince-jtag_0.5.1-10_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
gcc -DHAVE_CONFIG_H -I. -I. -I.. -DLOCALEDIR=\"/usr/share/locale\" -Wdate-time
-D_FORTIFY_SOURCE=2 -I/usr/include/openwince -I/usr/include/openwince/device
-I/usr/include/openwince/arm -I.. -I../include -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wall -c `test -f 'bsdl2jtag.c' || echo
'./'`bsdl2jtag.c
jtag.c: In function ‘jtag_parse_file’:
jtag.c:209:39: error: passing argument 2 of ‘getline’ from incompatible pointer
type [-Wincompatible-pointer-types]
209 | while (go && (getline( &line, &n, f ) != -1))
| ^~
| |
| int *
In file included from /usr/include/stdio.h:960,
from jtag.c:27:
/usr/include/x86_64-linux-gnu/bits/stdio.h:118:36: note: expected ‘size_t *’
{aka ‘long unsigned int *’} but argument is of type ‘int *’
118 | getline (char **__lineptr, size_t *__n, FILE *__stream)
|^~~
bsdl2jtag.c: In function ‘endline’:
bsdl2jtag.c:217:48: warning: logical not is only applied to the left hand side
of comparison [-Wlogical-not-parentheses]
217 | if(!strlen(att)==IR_l) {
|^~
bsdl2jtag.c:217:36: note: add parentheses around left hand side expression to
silence this warning
217 | if(!strlen(att)==IR_l) {
|^~~~
|( )
make[4]: *** [Makefile:333: jtag.o] Error 1
make[4]: *** Waiting for unfinished jobs
bsdl2jtag.c: In function ‘main’:
bsdl2jtag.c:320:37: warning: ignoring return value of ‘fgets’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
320 | if(b!='\n') fgets(line, 1023, infile);
| ^
flash.c: In function ‘flashmsbin’:
flash.c:129:17: warning: ignoring return value of ‘fread’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
129 | fread( &sync, sizeof (char), 7, f );
| ^~~
flash.c:143:17: warning: ignoring return value of ‘fread’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
143 | fread( &start, sizeof start, 1, f );
| ^~~
flash.c:144:17: warning: ignoring return value of ‘fread’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
144 | fread( &len, sizeof len, 1, f );
| ^~
Bug#1080275: marked as done (FTBFS with setuptools >= 72: error: invalid command 'test')
Your message dated Thu, 12 Sep 2024 12:19:44 + with message-id and subject line Bug#1080275: fixed in hovercraft 2.7-7 has caused the Debian Bug report #1080275, regarding FTBFS with setuptools >= 72: error: invalid command 'test' 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.) -- 1080275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hovercraft Version: 2.7-6 Severity: serious Tags: ftbfs Justification: FTBFS User: debian-pyt...@lists.debian.org Usertags: setup.py-test Dear maintainer, During a test rebuild for packages affected by setuptools 72, hovercraft failed to rebuild. FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementation of test_suite in setup.py to see what magic it does for test setup. --- [...] I: pybuild base:311: python3.12 setup.py config running config debian/rules override_dh_auto_test make[1]: Entering directory '/<>' py3versions: no X-Python3-Version in control file, using supported versions set -e; for PY in python3.12; do \ http_proxy='127.0.0.1:9' https_proxy='127.0.0.1:9' python3 setup.py test; \ done usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2024-08-28T01:08:40Z --- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/552643/ About the archive rebuild: The build was made on debusine.debian.net, using sbuild. You can find the build task here: https://debusine.debian.net/work-request/9699/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks, Stefano --- End Message --- --- Begin Message --- Source: hovercraft Source-Version: 2.7-7 Done: Alexandre Detiste 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (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: SHA512 Format: 1.8 Date: Thu, 12 Sep 2024 13:19:33 +0200 Source: hovercraft Architecture: source Version: 2.7-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1080275 Changes: hovercraft (2.7-7) unstable; urgency=medium . * QA upload. * Trim d/rules and rely more on pybuild magic (Closes: #1080275) Checksums-Sha1: 8d9b35f81057d0b9e6440ab4f43a8cfe1f0c61a4 2164 hovercraft_2.7-7.dsc 93a3a17ed6516d4bbd2bf491464b53ee039a6fbb 8460 hovercraft_2.7-7.debian.tar.xz 5cea338bbe7afbbda663c5e84a4666cdeafbe4c5 8566 hovercraft_2.7-7_source.buildinfo Checksums-Sha256: 3f857a0856e0e216398558ab07e4148139507c3c5ff9eae4f9a2f72dc9b27dc3 2164 hovercraft_2.7-7.dsc 504fe560ca9709f9d4e6da670ca12124dadf00020bf83a0df28eb6d7b459cf31 8460 hovercraft_2.7-7.debian.tar.xz 7602d499169d81023d77672cb6a38bd27cc5f40b1dc55b7181c00c5dd804aa9d 8566 hovercraft_2.7-7_source.buildinfo Files: 04f526ad568547e3e8b394d7f40f58c9 2164 misc optional hovercraft_2.7-7.dsc 6e6697a8f939308dd4632ac726588cb2 8460
Bug#1074999: marked as done (gimp-gap: ftbfs with GCC-14)
Your message dated Thu, 12 Sep 2024 12:04:05 + with message-id and subject line Bug#1074999: fixed in gimp-gap 2.6.0+dfsg-9 has caused the Debian Bug report #1074999, regarding gimp-gap: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1074999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gimp-gap Version: 2.6.0+dfsg-8 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/gimp-gap_2.6.0+dfsg-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] | ~^~ gap_mov_dialog.c: In function ‘mov_grab_bezier_path’: gap_mov_dialog.c:1194:10: warning: variable ‘image_id’ set but not used [-Wunused-but-set-variable] 1194 | gint32 image_id; | ^~~~ gap_mov_dialog.c: In function ‘mov_pgrab_callback’: gap_mov_dialog.c:1396:5: warning: ‘gimp_vectors_get_name’ is deprecated: Use 'gimp_item_get_name' instead [-Wdeprecated-declarations] 1396 | vectorname = gimp_vectors_get_name(vectors_id); | ^~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:64, from gap_mov_dialog.c:112: /usr/include/gimp-2.0/libgimp/gimpvectors.h:38:16: note: declared here 38 | gchar* gimp_vectors_get_name(gint32 vectors_ID); |^ gap_mov_dialog.c: In function ‘mov_imglayer_menu_callback’: gap_mov_dialog.c:2088:3: warning: ‘gimp_drawable_get_image’ is deprecated: Use 'gimp_item_get_image' instead [-Wdeprecated-declarations] 2088 | l_image_id = gimp_drawable_get_image(id); | ^~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41: /usr/include/gimp-2.0/libgimp/gimpdrawable.h:99:16: note: declared here 99 | gint32 gimp_drawable_get_image (gint32 drawable_ID); |^~~ gap_mov_dialog.c: In function ‘p_points_from_tab’: gap_mov_dialog.c:2507:15: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 2507 | (int)scale, (int)spinbutton); | ^ gap_mov_dialog.c:2507:27: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 2507 | (int)scale, (int)spinbutton); | ^ gap_mov_dialog.c: In function ‘mov_path_prevw_preview_init’: gap_mov_dialog.c:4416:5: warning: ‘gimp_drawable_get_image’ is deprecated: Use 'gimp_item_get_image' instead [-Wdeprecated-declarations] 4416 | image_id = gimp_drawable_get_image(mgp->drawable->drawable_id); | ^~~~ /usr/include/gimp-2.0/libgimp/gimpdrawable.h:99:16: note: declared here 99 | gint32 gimp_drawable_get_image (gint32 drawable_ID); |^~~ gap_mov_dialog.c: In function ‘p_get_flattened_drawable’: gap_mov_dialog.c:5050:3: warning: ‘gimp_drawable_get’ is deprecated: Use 'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations] 5050 | l_drawable_ptr = gimp_drawable_get (gap_image_merge_visible_layers(image_id, GIMP_CLIP_TO_IMAGE)); | ^~ /usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here 52 | GimpDrawable * gimp_drawable_get
Processed: Bug#1080275 marked as pending in hovercraft
Processing control commands: > tag -1 pending Bug #1080275 [src:hovercraft] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) pending. -- 1080275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 1010974, notfixed 1010974 in 5.3.28+dfsg1-0.9
Processing commands for cont...@bugs.debian.org:
> unarchive 1010974
Bug #1010974 {Done: Bastian Germann } [src:db5.3] db5.3:
CVE-2019-8457 in embedded sqlite3 copy
Unarchived Bug 1010974
> notfixed 1010974 5.3.28+dfsg1-0.9
Bug #1010974 {Done: Bastian Germann } [src:db5.3] db5.3:
CVE-2019-8457 in embedded sqlite3 copy
No longer marked as fixed in versions db5.3/5.3.28+dfsg1-0.9.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1080588: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Wed, 11 Sep 2024 11:34:23 + with message-id and subject line Bug#1080588: fixed in djvubind 1.2.1-7 has caused the Debian Bug report #1080588, regarding Missing Build-Depends on 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.) -- 1080588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: djvubind Version: 1.2.1-6 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: djvubind Source-Version: 1.2.1-7 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of djvubind, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated djvubind 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, 11 Sep 2024 13:06:44 +0200 Source: djvubind Architecture: source Version: 1.2.1-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1080588 Changes: djvubind (1.2.1-7) unstable; urgency=medium . * QA upload. * Add explicit dependency on python3-setuptools (Closes: #1080588) Checksums-Sha1: 775ff75c94c31754273d7c492917417a77cbf4c1 1922 djvubind_1.2.1-7.dsc a97c7ef5d2696421855aa2fe6b2b486673310d12 1836 djvubind_1.2.1-7.debian.tar.xz bbc3c50dc25841f8aefa1f18c2627230bdbd914c 7057 djvubind_1.2.1-7_source.buildinfo Checksums-Sha256: 4afe74eab36152ce0ae51d41d35a743ce8cf6f1959a67acf5db25b1f59248be6 1922 djvubind_1.2.1-7.dsc 8a50b4d11a5331fd90102f735edf59b22650f7dc5730e565104b492d591fe193 1836 djvubind_1.2.1-7.debian.tar.xz 924dfa4cc57e26f2c5411183805cb482e5a83d3a10ca5c474c694cdc42621dc7 7057 djvubind_1.2.1-7_source.buildinfo Files: 152077860ce107734ae62536a74c1443 1922 graphics optional djvubind_1.2.1-7.dsc 43b5f60c1d4badb30dd4f0de953fb464 1836 graphics optional djvubind_1.2.1-7.debian.tar.xz 41739e81b077a12de7066d58e9426f29 7057 graphics optional djvubind_1.2.1-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmbhee0RHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpFCA/+OGEPYcWYsdoUKwMA30lQH9Vba2H1w3rw eL8tVyLGy9IFJJ/SzAsnOyeSS6vIy1hALm7Za5XwLqbpz7veJndP4qHmNGco0xPH Plbjqbja9WPe7upPHFfl2xyAJOOQInf5RF/nMrfpKcVuzAJxZD8LXMi6BMNCpWnA ZBmLAYk8QmNOkvgnTXkEYHsc+gv4jFggriDdN6mKHCvVEyhhZgfI39RpvNELj/bR 2R5wxpobduTFdyafxtBxW1pTyA64YIjIiyrv6vRhdjFOi0KZaV2lgW5lAh71ATHK fCDN0qcUttBKCNdh4ZUDjqm4QE+jGnctepPftEwtq0QakCgmnPd03jwAdHtIsFfX 200SJlNAZvFr2VHKkjwb7hItZbtu5llsmHDDusmlxUuPBTJErTcY4VbRmnVbFwS3 2xxN7oVcj2uFBdxCFCAwt/EBnbwiVqr99xqg8FzkSyfaAS4s8xOUCBE4qbsgHjgm /wRqFp9Y2YtrZ6Wi0ok8TxBnGo0ywkE+kaPinhQZVTVAd/aolWQ7heeRmuS489Te oRQMTJpneiR2aQQ5yhQZDzncHN17aDA2Q1wqiC5gYmG8uzOS/3hQ2KzHpzPnYL31 j+rIF7JEQ1pJeHkMHJFk5EBaS4eqwyD1VoF0/oIh6NTMMlL2DNTWugYOQMM65ktx t6DNHfi4nns= =Nl9x -END PGP SIGNATURE- pgp64NDqPCgvs.pgp Description: PGP signature --- End Message ---
Bug#1080563: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Wed, 11 Sep 2024 11:34:11 + with message-id and subject line Bug#1080563: fixed in cdist 7.0.0-5 has caused the Debian Bug report #1080563, regarding Missing Build-Depends on 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.) -- 1080563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cdist Version: 7.0.0-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: cdist Source-Version: 7.0.0-5 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of cdist, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated cdist 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, 11 Sep 2024 13:02:11 +0200 Source: cdist Architecture: source Version: 7.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1080563 Changes: cdist (7.0.0-5) unstable; urgency=medium . * QA upload. * Add build-dependency on python3-setuptools (Closes: #1080563) Checksums-Sha1: 67b99896603972cf1bef39ad900e652dbf10c90c 2052 cdist_7.0.0-5.dsc 738676ab7fdcbfd62d93915ea244f665f46dcd3b 7844 cdist_7.0.0-5.debian.tar.xz d27962508fb2db9d13f6a8b749b8372087f11f73 8485 cdist_7.0.0-5_source.buildinfo Checksums-Sha256: 454ebbfb554da9051bfdf327675a7d48549f668c7b25e7170d2be9ed165791c7 2052 cdist_7.0.0-5.dsc 068b4ce3fce6db5b48097cf79fa0570d5aac9cc70fdfa62332b7b584516910d1 7844 cdist_7.0.0-5.debian.tar.xz 8f7db3ec4adf422037d28bbcdc71dcb03a370e35d6bbb0852711139a435d0926 8485 cdist_7.0.0-5_source.buildinfo Files: a8f86c09f8503bb2b827697dc20842ea 2052 admin optional cdist_7.0.0-5.dsc ff33a1d65df18349115ecaea8260f5a7 7844 admin optional cdist_7.0.0-5.debian.tar.xz ead104fbacf2559dfbdabfb57f3101ef 8485 admin optional cdist_7.0.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmbhePQRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBqcUw//fdSRk6a3GLFg0fcYUhuVDpdH9itIYmkc k0HB15et5+cGmQX0jp9pVuXrpgDIOftfQtZXcB5sKGsJVb/k3st/Mz2V4JHXX6ic ZMFwEVvk4QS4afIJzIAmxO5xKA2vGn+e241z/tEzt6WCD16pbNHHaSC+rDhop01K 1bDIJc+dnmLSfxBfXx/O1UvAV5vu8uAHk/n4tkNS94T4iQ15WBL1fsvDgMOZCmzb DN9Urk5N5MiQoa9geAIp70Ob591qiEmFKyTuUp34bnN0MhIuamPI/WF+VF32eQKa a/MB3PhDdv3j38ox8TPm6hEHVrwxYYYIS2kqmDqD1QAd3DzeNXy/3Hxyl7btyplI V0mN1WdHUR+1IFMfMhUYR9zk5D+EzH9dXQ38GhXiblUEwp0dzICeKUR7+OCjBzji tcrQvwZsUOlrpMos4GsTrbuXlxZCaEF3lRohefU/Rz6hJDmT28/pVMEkYvbFV9Vk fhHKWT3TrXV3Vpx4Sxyo/2nCi4+6EnscNq78L/AxfnhUPmIt6yJRdCDA3y1yBG6Q vtB53zA/pAgv1OMJVo1iFG2PNXJiTXsTgdrakADFlipIUMEYPfcwk8V6O5NmxRtH d6Y8vqpgqosIQEpaRQIhIUM6ci0jzbEqs7aAKnZix8MiyGw1vs7Rv9RZygfb2e89 N4U8VhTOjHg= =D0lM -END PGP SIGNATURE- pgp5kKt6vXXLB.pgp Description: PGP signature --- End Message ---
Bug#1080923: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Wed, 11 Sep 2024 11:22:05 + with message-id and subject line Bug#1080923: fixed in python-djvulibre 0.9.0-5 has caused the Debian Bug report #1080923, regarding Missing Build-Depends on 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.) -- 1080923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-djvulibre Version: 0.9.0-4 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: python-djvulibre Source-Version: 0.9.0-5 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-djvulibre, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-djvulibre 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, 11 Sep 2024 12:34:11 +0200 Source: python-djvulibre Architecture: source Version: 0.9.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexandre Detiste Closes: 945190 1080923 Changes: python-djvulibre (0.9.0-5) unstable; urgency=medium . * Adopt package inside DPT (Closes: #945190) * Switch to pybuild-plugin-pyproject (Closes: #1080923) Checksums-Sha1: 08dc7ee4b69133abe75cc76e916f5df726e64719 2425 python-djvulibre_0.9.0-5.dsc 6c516b563f635719ab39ac0cabb7c1e5054ef122 18044 python-djvulibre_0.9.0-5.debian.tar.xz 46069814c8780777b314fcae84439b6f55ec9441 11958 python-djvulibre_0.9.0-5_source.buildinfo Checksums-Sha256: 4e1f6a1a363fcb79cb4442ad29a00d42b371b127300e18556ec1eb3d436dff68 2425 python-djvulibre_0.9.0-5.dsc 69e0ad949b6e6d44e1e544cf65e3645dfc86c9dc13007911d55fe42d678b1d36 18044 python-djvulibre_0.9.0-5.debian.tar.xz 6199bed81ec290bf4f690a97901d09959906ff56cd05a956b762c41697d0ef11 11958 python-djvulibre_0.9.0-5_source.buildinfo Files: 3f83fcfcbdf3719fa76d158d4e3b1242 2425 python optional python-djvulibre_0.9.0-5.dsc 0f87621a5edc5f8f181a6bf05a279e15 18044 python optional python-djvulibre_0.9.0-5.debian.tar.xz 08f5f7743a0edf6ed8b9ab476e538ab5 11958 python optional python-djvulibre_0.9.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmbhd28RHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBou+xAApA1jxdRpm5aujXMDnGbLajCTlutWZC1+ SANKkSTlpG/Ywbb7XOXVcIE761PjNG94cbvHRy9PWy54gsAW1cKcU1bgK6eIswOy LuhObrcUiPk4Eak6rniORacNedYZaVA3R8Ov5d2GILftoSCKCnl7hLj056oKYnU6 k8vY+IT2YAYu2aDKFJYDLz2S9HpeslBLo9Gc80q22JjchN2/T82WFlgUhPbhAbwQ m6EXaFPvPC669G7sVzCrQQX/s58CM3tVcgyJQ2OcydgBp4WMcLSgUndgIofsdt59 AsbcSQ/UP5U8bzCmFYKgPYkMdhcsC20ybTAe6+czXyiGjK8yq3jUQS5dCrcVTovk TUbrIQB++DxgWQwuQmS8sYNc6ug+mr+Mk+Z64FlL89zsxUPqSX1Nu64mUR1r6RZF qygR2/xfSc4Zu/Hx60DxvEJ561ak0r5XZZldI0GUm+GFHTaojkEPPtk1HsxbolL8 cfrTVqcYugqj53+HRiDrWOghATEl3X7uHjy3Azu3ZoovRPfDxtpaJt8qqrhrchSF LdqpN9yPFid6/MHNu5mwrMJSF/A931PH3I8GbzTaSG+QgiPIN3GRS9GW5guuGS0m 70jRRd7khGGQp8dCpsYCV9uqp7Lg7Dbmlp8EalJb6YrxwvddTq0/dEd6LP5yMy1z KaEuT0J/DCE= =Q3zc -END PGP SIGNATURE- pgpmxt3yI2Cgx.pgp Description: PGP signature --- End Message ---
Bug#1081242: marked as done (irony-mode: Please build with llvm/clang 18 or 19)
Your message dated Wed, 11 Sep 2024 10:50:07 + with message-id and subject line Bug#1081242: fixed in irony-mode 1.6.1-1 has caused the Debian Bug report #1081242, regarding irony-mode: Please build with llvm/clang 18 or 19 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.) -- 1081242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irony-mode Severity: important Dear Maintainer, We would like to remove llvm-toolchain-16 and this package uses clang 16. Please update to 18 or 19. Thanks Sylvesre -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (500, 'oldstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: irony-mode Source-Version: 1.6.1-1 Done: Nicholas D Steeves We believe that the bug you reported is fixed in the latest version of irony-mode, 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 1081...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas D Steeves (supplier of updated irony-mode 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, 11 Sep 2024 06:36:55 -0400 Source: irony-mode Architecture: source Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Nicholas D Steeves Closes: 1081242 Changes: irony-mode (1.6.1-1) unstable; urgency=medium . * QA upload. * New upstream release. * Migrate to llvm-toolchain-19 (Closes: #1081242) Checksums-Sha1: 5f2e00a4b82db24c4cd1e648a53ced59c2f45f13 2037 irony-mode_1.6.1-1.dsc 5a50cd4f5c28838ddb9fd3caaa6558487d669893 346612 irony-mode_1.6.1.orig.tar.gz df744594aec4b66165df177657e9a595f05d035e 7908 irony-mode_1.6.1-1.debian.tar.xz 28b005562b215301b388d1f81b98ebecc80bd650 11108 irony-mode_1.6.1-1_amd64.buildinfo Checksums-Sha256: 91252300bd2982d97d694259f4c9ac9aa9f46e3a5ac6d76e200474e773c20d1b 2037 irony-mode_1.6.1-1.dsc efcaad5e92024bb25103d143b1e154f75e32a0f1cab3b7ee621242d439c2eecb 346612 irony-mode_1.6.1.orig.tar.gz 2bb9326f1035d762fb9928b2a6e2b6b9f7f2a2b87528ba2dcf5d638ce379e8c0 7908 irony-mode_1.6.1-1.debian.tar.xz af56187c3c1ceb8982ce3a1bfa7055bdf224818749890bf04ac8377af22dca86 11108 irony-mode_1.6.1-1_amd64.buildinfo Files: 5365fb52d3afd70cc4cd96ffbb7a3759 2037 editors optional irony-mode_1.6.1-1.dsc 4d5b695b207e4a8c60ecb14466f5f004 346612 editors optional irony-mode_1.6.1.orig.tar.gz 360e6d165e5a83683de8105652a419c3 7908 editors optional irony-mode_1.6.1-1.debian.tar.xz 8ed0b64a5d7ca0b9a3ee00114c825333 11108 editors optional irony-mode_1.6.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmbhc10ACgkQWogwR199 EGFSBw/7BWrEOLAsF4NeXObQkzy3jIy7pm4D2JcCoR+3uE39ADO4YP07Jb6HKVeS dcf5D3WkkmdCVTvwmJW3A3VhPJFX08uUkNVZ1Al13Oo813+N5RtQi1rLLAStt4ZT 8y7SHDBYhaNSpu0zkqgND1N6aqnx19E8VYE8KxKmMSggGkoCJtzJ/4NYIfER8Ao3 bs87bBEM3vP87cfZdww1lkQbI+hc3TDGF9m6WmwTFQGbAcegwzBvZEhXhr6N/E8C BegzL5riXw0zOfeo1UAcKusCFFnwff5MZXlG7jlFQr+xWXVApp2JAXCu0pgqSmdz +EjaJV5z5YRDbQeJcPD601k/MLADsnRgwXlLwuwQC4O0ALuHA2bq7vJTUPA1DQBu ZFApS7ZYU0cYmZZUIZ7L8DGz9yfnTc2A+EnqEojAKBdtyDt6B6Hp36OacuNdhshn Cb6mwsyYnejRTh7c0JEOPpYvOZT2eG3bE/Y4m9RpwXQQmgjlTCJnZZ8NTrDJMwva VjVJPxXm/4I3Og31+Xo9ODiYF5zmts3kzd9K2R+fltpJvpaCfQzs7AKGzq9GwGIi hhO3krHkMhGV26xTWVNE0h24ya6v+J3B+i48AnAL6E25T2cg9XG9d/XR04/DaycC ZQ3Tia7jK+QqyZ05bB9z3qrIalCYAP7HTRgsJAQ2gk08jsc0YPw= =8URg -END PGP SIGNATURE- pgpDDjCMKTzpe.pgp Description: PGP signature --- End Message ---
Bug#1074810: marked as done (ample: ftbfs with GCC-14)
Your message dated Wed, 11 Sep 2024 01:19:00 +
with message-id
and subject line Bug#1074810: fixed in ample 0.5.7-14
has caused the Debian Bug report #1074810,
regarding ample: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1074810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ample
Version: 0.5.7-13
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/ample_0.5.7-13_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
helper.c: In function ‘setid3v2title’:
helper.c:746:9: warning: ignoring return value of ‘fread’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
746 | fread(header, sizeof(char), 10, file);
| ^
helper.c: In function ‘setid3v1title’:
helper.c:704:17: warning: ignoring return value of ‘fgets’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
704 | fgets(buffer, 31, file);
| ^~~
configuration.c: In function ‘readrequest’:
configuration.c:298:32: warning: comparison between pointer and zero character
constant [-Wpointer-compare]
298 | if(tmp == '\0' || strlen(tmp) < 1) {
|^~
configuration.c:298:28: note: did you mean to dereference the pointer?
298 | if(tmp == '\0' || strlen(tmp) < 1) {
|^
configuration.c: In function ‘parseconfopt’:
configuration.c:570:54: warning: field precision specifier ‘.*’ expects
argument of type ‘int’, but argument 4 has type ‘long int’ [-Wformat=]
570 | snprintf(retval, (end - tmp + 1), "%.*s", (end - tmp),
tmp);
|~~^~ ~~~
| | |
| int long int
configuration.c:584:54: warning: field precision specifier ‘.*’ expects
argument of type ‘int’, but argument 4 has type ‘long int’ [-Wformat=]
584 | snprintf(retval, (end - tmp + 1), "%.*s", (end - tmp),
tmp);
|~~^~ ~~~
| | |
| int long int
entries.c: In function ‘checkpathtype’:
entries.c:750:25: warning: ignoring return value of ‘chdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
750 | chdir(dname);
| ^~~~
entries.c:757:25: warning: ignoring return value of ‘chdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
757 | chdir(owd);
| ^~
configuration.c: In function ‘preparehtml’:
entries.c: In function ‘parsem3u’:
entries.c:890:9: warning: ignoring return value of ‘chdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
890 | chdir(dname);
| ^~~~
entries.c:922:9: warning: ignoring return value of ‘chdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
922 | chdir(owd);
| ^~
configuration.c:438:33: warning: ign
Bug#1074992: marked as done (gftp: ftbfs with GCC-14)
Your message dated Tue, 10 Sep 2024 19:34:17 + with message-id and subject line Bug#1074992: fixed in gftp 2.9.1~beta-3 has caused the Debian Bug report #1074992, regarding gftp: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1074992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gftp Version: 2.9.1~beta-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/gftp_2.9.1~beta-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] /usr/bin/msgfmt -o sr.mo sr.po /usr/bin/msgfmt -o sv.mo sv.po /usr/bin/msgfmt -o ta.mo ta.po /usr/bin/msgfmt -o te.mo te.po /usr/bin/msgfmt -o th.mo th.po /usr/bin/msgfmt -o tr.mo tr.po /usr/bin/msgfmt -o uk.mo uk.po /usr/bin/msgfmt -o zh_CN.mo zh_CN.po /usr/bin/msgfmt -o zh_HK.mo zh_HK.po /usr/bin/msgfmt -o zh_TW.mo zh_TW.po make[3]: Leaving directory '/<>/po' Making all in lib make[3]: Entering directory '/<>/lib' gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -D_REENTRANT -DSHARE_DIR=\"/usr/share/gftp\" -DLOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o cache.o cache.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -D_REENTRANT -DSHARE_DIR=\"/usr/share/gftp\" -DLOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o charset-conv.o charset-conv.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -D_REENTRANT -DSHARE_DIR=\"/usr/share/gftp\" -DLOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o config_file.o config_file.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -D_REENTRANT -DSHARE_DIR=\"/usr/share/gftp\" -DLOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o fsplib.o fsplib.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -D_REENTRANT -DSHARE_DIR=\"/usr/share/gftp\" -DLOCALE_DIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unus
Bug#1074928: marked as done (easyh10: ftbfs with GCC-14)
Your message dated Tue, 10 Sep 2024 16:04:06 +
with message-id
and subject line Bug#1074928: fixed in easyh10 1.5-7
has caused the Debian Bug report #1074928,
regarding easyh10: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1074928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:easyh10
Version: 1.5-6
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/easyh10_1.5-6_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
|%hn
h10db_dat.c:264:33: warning: format ‘%s’ expects argument of type ‘char *’, but
argument 3 has type ‘ucs2_char_t *’ {aka ‘short unsigned int *’} [-Wformat=]
264 | fprintf(fp, "unknown8: %s\n", item->unknown8);
|~^ ~~
| | |
| char *ucs2_char_t * {aka short
unsigned int *}
|%hn
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 crc.c -o crc.o >/dev/null 2>&1
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 h10db_upd.c -o h10db_upd.o
>/dev/null 2>&1
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 h10db_idx.c -o h10db_idx.o
>/dev/null 2>&1
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 h10db_model.c -o h10db_model.o
>/dev/null 2>&1
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=/<>=.
-fst
Bug#1081112: marked as done (ddcui: FTBFS on all archs, unmaintained)
Your message dated Tue, 10 Sep 2024 07:35:41 +0100 with message-id and subject line Re: ddcui: FTBFS on all archs, unmaintained has caused the Debian Bug report #1081112, regarding ddcui: FTBFS on all archs, unmaintained 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.) -- 1081112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ddcui Version: 0.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) FTBFS and should not be in the next release unless it is fixed. Scott K --- End Message --- --- Begin Message --- Fixed in version 0.5.4-1 and closing. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Buy Me A Coffee: https://buymeacoffee.com/kathenasorg Internet Relay Chat (IRC): kathenas Matrix: #kathenas:matrix.org Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Threads: https://www.threads.net/@kathenasorg -- signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: fixed 1081112 in 0.5.4-1
Processing commands for cont...@bugs.debian.org: > fixed 1081112 0.5.4-1 Bug #1081112 [src:ddcui] ddcui: FTBFS on all archs, unmaintained Marked as fixed in versions ddcui/0.5.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1081112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074925: marked as done (dvi2dvi: ftbfs with GCC-14)
Your message dated Tue, 10 Sep 2024 03:19:30 + with message-id and subject line Bug#1074925: fixed in dvi2dvi 2.0alpha-12 has caused the Debian Bug report #1074925, regarding dvi2dvi: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1074925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dvi2dvi Version: 2.0alpha-11 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/dvi2dvi_2.0alpha-11_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-b1459cd5-63de-4ac5-b897-21fad9bb7f7f SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package dvi2dvi dpkg-buildpackage: info: source version 2.0alpha-11 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Andreas Beckmann dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' dh_auto_clean make -j8 clean make[2]: Entering directory '/<>' rm -f dvi2dvi *.o *.orig core make[2]: Leaving directory '/<>' rm -rf lib/ make[1]: Leaving directory '/<>' dh_clean debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build make -j8 make[2]: Entering directory '/<>' 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 -Wl,-z,relro -c -DDVI2PATH=\".:/etc/texmf/dvi2dvi\" -DDVI2LIB=\"/etc/texmf/dvi2dvi\" -DFONTDESC=\"//fontdesc\" dvi2.c 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 dviconv.o dviconv.c 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 dfdcom.o dfdcom.c 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 fontcom.o fontcom.c 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 set.o set.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-pr
Bug#1074965: marked as done (freecdb: ftbfs with GCC-14)
Your message dated Mon, 09 Sep 2024 23:20:08 + with message-id and subject line Bug#1074965: fixed in freecdb 0.78 has caused the Debian Bug report #1074965, regarding freecdb: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1074965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freecdb Version: 0.77 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/freecdb_0.77_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] 14 | if (!n) return; *--to = *--from; --n; | ^ byte_cr.c:15:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 15 | if (!n) return; *--to = *--from; --n; | ^~ byte_cr.c:15:21: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 15 | if (!n) return; *--to = *--from; --n; | ^ byte_cr.c:16:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 16 | if (!n) return; *--to = *--from; --n; | ^~ byte_diff.c: In function ‘byte_diff’: byte_diff.c:11:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 11 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_cr.c:16:21: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 16 | if (!n) return; *--to = *--from; --n; | ^ byte_diff.c:11:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 11 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:12:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 12 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:12:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 12 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:13:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 13 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:13:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 13 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:14:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 14 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ byte_diff.c:14:23: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 14 | if (!n) return 0; if (*s != *t) break; ++s; ++t; --n; | ^~ gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cdb.o cdb.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cdb_hash.o cdb_hash.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 1075944 by 1081241 Bug #1075944 [ftp.debian.org] RM: llvm-toolchain-16 -- ROM; too many llvm version 1075944 was blocked by: 1081228 1081229 1075944 was not blocking any bugs. Added blocking bug(s) of 1075944: 1081241 > block 1075944 by 1081242 Bug #1075944 [ftp.debian.org] RM: llvm-toolchain-16 -- ROM; too many llvm version 1075944 was blocked by: 1081228 1081229 1081241 1075944 was not blocking any bugs. Added blocking bug(s) of 1075944: 1081242 > block 1075944 by 1081244 Bug #1075944 [ftp.debian.org] RM: llvm-toolchain-16 -- ROM; too many llvm version 1075944 was blocked by: 1081228 1081229 1081241 1081242 1075944 was not blocking any bugs. Added blocking bug(s) of 1075944: 1081244 > thanks Stopping processing here. Please contact me if you need assistance. -- 1075944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970657: marked as done (tcpspy FTCBFS: hard codes the build architecture compiler)
Your message dated Mon, 09 Sep 2024 19:12:10 + with message-id and subject line Bug#970657: fixed in tcpspy 1.7d-16 has caused the Debian Bug report #970657, regarding tcpspy FTCBFS: hard codes the build architecture compiler 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.) -- 970657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcpspy Version: 1.7d-15 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs tcpspy fails to cross build from source, because the upstream Makefile hard codes the build architecture compiler gcc. Please consider applying the attached patch to make it substitutable and tcpspy cross buildable. Helmut --- tcpspy-1.7d.orig/Makefile +++ tcpspy-1.7d/Makefile @@ -22,7 +22,7 @@ all: tcpspy doc tcpspy: log.o rule_lexer.o rule_grammar.o rule.o tcpspy.o - gcc $(LDFLAGS) $(CFLAGS) $(CPPFLAGS) log.o rule_lexer.o rule_grammar.o rule.o tcpspy.o -o tcpspy + $(CC) $(LDFLAGS) $(CFLAGS) $(CPPFLAGS) log.o rule_lexer.o rule_grammar.o rule.o tcpspy.o -o tcpspy log.o: log.c --- End Message --- --- Begin Message --- Source: tcpspy Source-Version: 1.7d-16 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of tcpspy, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated tcpspy 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, 09 Sep 2024 13:09:13 -0300 Source: tcpspy Architecture: source Version: 1.7d-16 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Joao Eriberto Mota Filho Closes: 970657 1075556 Changes: tcpspy (1.7d-16) unstable; urgency=medium . * QA upload. * debian/control: - Bumped Standards-Version to 4.7.0. - Dropped dependency on obsolete lsb-base. The sysvinit-utils is providing the scripts needed by /etc/init.d/* files. * debian/copyright: updated packaging copyright years. * debian/patches/: - 20_add-GCC-hardening.patch: updated to fix a FTCBFS because it was using an implicit gcc command. Thanks to Helmut Grohne . (Closes: #970657) - 60_fix-gcc-warning.patch: added a value to return function to fix a FTBFS. (Closes: #1075556) Checksums-Sha1: eeda20fb1f796c6a60d1cf9add960173269486db 1800 tcpspy_1.7d-16.dsc 9942814001b7c59d2ca3f04876a480572a3fa935 13360 tcpspy_1.7d-16.debian.tar.xz d00741905c4990411c7306c68ecbdcb2e0a6d65c 6522 tcpspy_1.7d-16_source.buildinfo Checksums-Sha256: 7c63ed9b89d902f4cd9abe1b2ad236899fd001bd7f5e9c3b3b0253571a596a80 1800 tcpspy_1.7d-16.dsc 7dbebbc96652d3f3ab041b1f7d3ca7c826042ba7e82f7b6a87b3b6d45053b53c 13360 tcpspy_1.7d-16.debian.tar.xz a62befd6c3cbcc569a9584c0a2d81ad7d8f9c27ae345ff70d7e910cb8dd3a022 6522 tcpspy_1.7d-16_source.buildinfo Files: 8c231164e8e470e05cfd2fa6e13e662d 1800 net optional tcpspy_1.7d-16.dsc b6e9c5953d410269408d73daf412fcd1 13360 net optional tcpspy_1.7d-16.debian.tar.xz d1eaa182ebc5dc8570d73da7a851fd11 6522 net optional tcpspy_1.7d-16_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmbfPLoACgkQ3mO5xwTr 6e/RVw//c96bWYOy9Kxc5OrWFftZsl/w7olyRAHkCUxkzmfe5WDzxezaSjJXtx5o GR5BpeGoe4SA788BOcumOx+c9aTbFjXTOedXfnEEqPcH3wbc8MxxqEJbVSIiIbhW tXZkzsxhZduHYBvaw20wXdHk1DGrJi0I1Dpzb5FB5uBb88TOJrjI7ksFguUkhFrI IRv6CQQE88Rz22hr/1PMd4K79RzYpMJipGAZrRMa4H5AiNw747YM+1Sb0J9IVV69 deVt4FPsu2eRW5bSlTnDFeB/sUOnZkYECPBpNt/O0UAE+BhxzBHRsipDdxFmsa8h xHm5OeQX80PuDj1amqhMjKGtFSC1uhdyC5Z4RqxCrNJLtn46mxq7q33TSOHlx8Kj tJ4AOoqSSNo8ZtR1KCJQkdlIgeBElGxRvJ+Qm9fH5uQleBZiXld1Zt9hNjN4ZIV3 6laiS0WOWz5JhJRlsi1Q9vRXB1Xb9DtZXl3aiZ2FBjbbPU+ilFIF3QxTzktKCgSj GGOPOmqB/4rB4o/fFpD+IXtMn1GoBftJMZsXjck6wuyMocjCO6dK9/qoS1n/dnUD Mxf5UMrmb6njBYZZXJFXsk2D3o+wlxX4MRdVuydMmxqq5g64+LLAqH9Ij+zzf7yZ Ha8Dvfh5F2YtJ9T3so5FDVr9Cme7J6Xlj2yuw+Gf2qhoKfLZiTw= =5Rw4 -END PGP SIGNATURE- pgpqL3NU6jULG.pgp Description: PGP signature --- End Message ---
Bug#1075556: marked as done (tcpspy: ftbfs with GCC-14)
Your message dated Mon, 09 Sep 2024 19:12:10 + with message-id and subject line Bug#1075556: fixed in tcpspy 1.7d-16 has caused the Debian Bug report #1075556, regarding tcpspy: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1075556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tcpspy Version: 1.7d-15 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/tcpspy_1.7d-15_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] Sufficient free space for build User Environment APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-e38bf3c1-c25c-4397-8b1c-3c5dfcdfe4bc SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package tcpspy dpkg-buildpackage: info: source version 1.7d-15 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Joao Eriberto Mota Filho dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean --no-parallel dh_auto_clean -O--no-parallel make -j1 clean make[1]: Entering directory '/<>' rm -f log.o rule_lexer.o rule_grammar.o rule_lexer.c \ rule_grammar.c rule_grammar.h rule.o tcpspy.o tcpspy \ tcpspy.ps tcpspy.pdf make[1]: Leaving directory '/<>' dh_autoreconf_clean -O--no-parallel dh_clean -O--no-parallel debian/rules binary dh binary --no-parallel dh_update_autotools_config -O--no-parallel dh_autoreconf -O--no-parallel dh_auto_configure -O--no-parallel dh_auto_build -O--no-parallel make -j1 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DFACILITY=LOG_LOCAL1 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -c -o log.o log.c bison -p rule -o rule_grammar.c -d rule_grammar.y flex -Prule -orule_lexer.c rule_lexer.l cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DFACILITY=LOG_LOCAL1 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -c -o rule_lexer.o rule_lexer.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DFACILITY=LOG_LOCAL1 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -c -o rule_grammar.o rule_grammar.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DFACILITY=LOG_LOCAL1 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -c -o rule.o rule.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-pro
Bug#1074885: marked as done (clipit: ftbfs with GCC-14)
Your message dated Mon, 09 Sep 2024 18:35:04 + with message-id and subject line Bug#1074885: fixed in clipit 1.4.5+git20210313-3 has caused the Debian Bug report #1074885, regarding clipit: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1074885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:clipit Version: 1.4.5+git20210313-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/clipit_1.4.5+git20210313-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] 931 | gtk_image_menu_item_set_image((GtkImageMenuItem*)menu_item, menu_image); | ^ /usr/include/gtk-3.0/gtk/deprecated/gtkimagemenuitem.h:92:12: note: declared here 92 | void gtk_image_menu_item_set_image (GtkImageMenuItem *image_menu_item, |^ main.c:935:17: warning: ‘gtk_image_menu_item_new_from_stock’ is deprecated: Use 'gtk_menu_item_new' instead [-Wdeprecated-declarations] 935 | menu_item = gtk_image_menu_item_new_from_stock(GTK_STOCK_PREFERENCES, NULL); | ^ /usr/include/gtk-3.0/gtk/deprecated/gtkimagemenuitem.h:84:12: note: declared here 84 | GtkWidget* gtk_image_menu_item_new_from_stock(const gchar *stock_id, |^~ preferences.c:1086:3: warning: ‘gtk_misc_set_alignment’ is deprecated [-Wdeprecated-declarations] 1086 | gtk_misc_set_alignment((GtkMisc*)label, 0.0, 0.50); | ^~ main.c:935:17: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 935 | menu_item = gtk_image_menu_item_new_from_stock(GTK_STOCK_PREFERENCES, NULL); | ^ /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:72:9: note: declared here 72 | voidgtk_misc_set_alignment (GtkMisc *misc, | ^~ main.c:939:17: warning: ‘gtk_image_menu_item_new_from_stock’ is deprecated: Use 'gtk_menu_item_new' instead [-Wdeprecated-declarations] 939 | menu_item = gtk_image_menu_item_new_from_stock(GTK_STOCK_QUIT, NULL); | ^ /usr/include/gtk-3.0/gtk/deprecated/gtkimagemenuitem.h:84:12: note: declared here 84 | GtkWidget* gtk_image_menu_item_new_from_stock(const gchar *stock_id, |^~ preferences.c:1095:3: warning: ‘gtk_misc_set_alignment’ is deprecated [-Wdeprecated-declarations] 1095 | gtk_misc_set_alignment((GtkMisc*)label, 0.0, 0.50); | ^~ /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:72:9: note: declared here 72 | voidgtk_misc_set_alignment (GtkMisc *misc, | ^~ main.c:939:17: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 939 | menu_item = gtk_image_menu_item_new_from_stock(GTK_STOCK_QUIT, NULL); | ^ main.c: In function ‘create_app_indicator’: preferences.c:1104:3: warning: ‘gtk_misc_set_alignment’ is deprecated [-Wdeprecated-declarations] 1104 | gtk_misc_set_alignment((GtkMisc*)label, 0.0, 0.50); | ^~ /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:72:9: note: declared here 72 | voidgtk_misc_set_alig
Bug#981490: marked as done (goban: Wrong homepage)
Your message dated Mon, 09 Sep 2024 06:34:23 + with message-id and subject line Bug#981490: fixed in goban 1.1-8 has caused the Debian Bug report #981490, regarding goban: Wrong homepage 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.) -- 981490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: goban Version: 1.1-6 Severity: normal I have see that the project homepage do not respond anymore: https://draves.org/goban/ I think that the homepage is now: https://draves.org/goban/goban.html Ciao Davide Note: this is a simplified bug report that I use to report homepage problems found at https://repology.org/repository/debian_testing/problems --- End Message --- --- Begin Message --- Source: goban Source-Version: 1.1-8 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of goban, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated goban 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, 09 Sep 2024 08:09:15 +0200 Source: goban Architecture: source Version: 1.1-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 981490 993690 1075032 Changes: goban (1.1-8) unstable; urgency=medium . * QA upload. . * Updated homepage URLs to current location (Closes: #981490). * Adjusted install path for binary to where xscreensaver find it (Closes: #993690). * Fixed sighandler signature to work with GCC 14 (Closes: #1075032). Checksums-Sha1: 570bc9488dfcb4d4258c74bc88b1e5ecfb3babf9 1868 goban_1.1-8.dsc d805aaea0db69bcd22784d3f6eb531a7b162a318 7340 goban_1.1-8.debian.tar.xz 0581e6012fdfb5b1d9a5cc5f079bbf4818f78a21 6767 goban_1.1-8_source.buildinfo Checksums-Sha256: 71994392992666da8ea6e539523f0398b2eced10e609f1b856bdb58c9e03453e 1868 goban_1.1-8.dsc 1d0603752d4746c8ceda61aba2b38fe6a8e29246f4aee6b0db693823ff4eaee5 7340 goban_1.1-8.debian.tar.xz 43a9aa11ca7f039a74aa9c5d04677f01ef8152e618f4aa8dc0b3b664a07e6aaa 6767 goban_1.1-8_source.buildinfo Files: 7dc79e69f32671969e7436862596fdc4 1868 x11 optional goban_1.1-8.dsc 4126141c89a807dc81734c5fba3c6112 7340 x11 optional goban_1.1-8.debian.tar.xz b36fc5b8cea547c0bf980b3fe24e4dc6 6767 x11 optional goban_1.1-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmbekY4ACgkQgSgKoIe6 +w42yw//Xz7Cl5ltAK1597hJPHvCOBHv3JH4ggu4gUWHPwcxmAVBS4q8I40iNCmV oh5Ivq9XTMNprzmwvbh90C048redQDj8hVh1rwAfJMfM8NQP3S5nNu2CxpPLOVAz BEQU37bRQQ9qhIVANKDCbVnM5uiN8jEVXtH2UfNtrxg9aveDjIAfCeFDKtzAUYlF 0XCprj5/R106LMorRmiikR6Pxddu0Pgv3iyEQFeebIEJMbhHbxWlEo85vqP4b4Bh Bs7NSXw9DBCczUakH/qJ3VD793fjEkfhFxzdVI8PjS1yELCnNx2thQn/3bWbt+Zs 2jujZaxaXrgoRRo2CyXqdoUNkDArGlrv+QHT48hzlRhYE5Pz4r9WbJdNunKaUJ30 3CRin9GwZEgiY/PGhlUOjDR8ieo6o3Z9hBGzGlgLt5a/SKFUw0sWfylgZw9FCouo 51y8RhqJWmibZj7NFQfd1ZGtUD6T2QEUTV2lhGYC2ube9NkFNWH8rjmaw/a1Yeoi Sda6is6O5Ya/0qKoducV5wzEcOBtmomHpg+BkyyqfBExit7w7OomVp84eggyahtT yV6xiL+6Uyh9Tn2SKkodhma2d9XhKD28QsdEWoY8E5VF3CSymlZyUWMMBRQmnLaZ dkEYtnrp+4/kE9HP4XsP+3pJcwjbcr5FgA+E37cmvI02MDLCREg= =DDtC -END PGP SIGNATURE- pgpnRtnUK7p9p.pgp Description: PGP signature --- End Message ---
Bug#1075032: marked as done (goban: ftbfs with GCC-14)
Your message dated Mon, 09 Sep 2024 06:34:23 +
with message-id
and subject line Bug#1075032: fixed in goban 1.1-8
has caused the Debian Bug report #1075032,
regarding goban: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1075032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:goban
Version: 1.1-7
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/goban_1.1-7_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ~~~^
main.c:60:20: error: passing argument 2 of ‘signal’ from incompatible pointer
type [-Wincompatible-pointer-types]
60 | signal(SIGHUP, sigHandler);
|^~
||
|void * (*)()
/usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void
(*)(int)’} but argument is of type ‘void * (*)()’
88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
| ~~~^
make[3]: *** [Makefile:678: goban-main.o] Error 1
make[3]: *** Waiting for unfinished jobs
match.c: In function ‘newKomi’:
match.c:498:24: warning: ‘%g’ directive writing between 1 and 13 bytes into a
region of size 7 [-Wformat-overflow=]
498 | sprintf(curValue, "%g", m->komi);
|^~
match.c:498:23: note: assuming directive output of 12 bytes
498 | sprintf(curValue, "%g", m->komi);
| ^~~~
In file included from /usr/include/stdio.h:964,
from ./wms.h:30,
from match.c:7:
In function ‘sprintf’,
inlined from ‘newKomi’ at match.c:498:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note:
‘__builtin___sprintf_chk’ output between 2 and 14 bytes into a destination of
size 7
30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~
31 | __glibc_objsize (__s), __fmt,
| ~
32 | __va_arg_pack ());
| ~
match.c: In function ‘changeKomi’:
match.c:760:21: warning: ‘%g’ directive writing between 1 and 13 bytes into a
region of size 10 [-Wformat-overflow=]
760 | sprintf(komiStr, "%g", m->komi);
| ^~
match.c:760:20: note: assuming directive output of 12 bytes
760 | sprintf(komiStr, "%g", m->komi);
|^~~~
In function ‘sprintf’,
inlined from ‘changeKomi’ at match.c:760:3:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note:
‘__builtin___sprintf_chk’ output between 2 and 14 bytes into a destination of
size 10
30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~
31 | __glibc_objsize (__s), __fmt,
| ~
32 | __va_arg_pack ());
| ~
match.c: In function ‘changeHcap’:
match.c:787:21: warning: ‘%d’ directive writing betwe
Bug#993690: marked as done (goban-ss: Goban-ss binary in incorrect location)
Your message dated Mon, 09 Sep 2024 06:34:23 + with message-id and subject line Bug#993690: fixed in goban 1.1-8 has caused the Debian Bug report #993690, regarding goban-ss: Goban-ss binary in incorrect location 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.) -- 993690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: goban-ss Version: 1.1-6 Severity: important Tags: a11y Dear Maintainer, On a new installation of Debian 11, the goban-ss package installs the binary file for the screensaver into the directory /usr/lib/xscreensaver/goban. The xscreensaver package sets the default directory for binaries as /usr/libexec/xscreensaver/goban. When the goban-ss package in installed the xscreensaver progam show the module as "Not Installed". I was able to correct this by creating a simlink to put the goban-ss binary in the correct location (sudo ln -s /usr/lib/xscreensaver/goban /usr/libexec/xscreensaver/goban). -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 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 Versions of packages goban-ss depends on: ii libc6 2.31-13 ii libx11-6 2:1.7.2-1 Versions of packages goban-ss recommends: ii goban-original-games 1.1-6 ii xscreensaver 5.45+dfsg1-2 goban-ss suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: goban Source-Version: 1.1-8 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of goban, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated goban 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, 09 Sep 2024 08:09:15 +0200 Source: goban Architecture: source Version: 1.1-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 981490 993690 1075032 Changes: goban (1.1-8) unstable; urgency=medium . * QA upload. . * Updated homepage URLs to current location (Closes: #981490). * Adjusted install path for binary to where xscreensaver find it (Closes: #993690). * Fixed sighandler signature to work with GCC 14 (Closes: #1075032). Checksums-Sha1: 570bc9488dfcb4d4258c74bc88b1e5ecfb3babf9 1868 goban_1.1-8.dsc d805aaea0db69bcd22784d3f6eb531a7b162a318 7340 goban_1.1-8.debian.tar.xz 0581e6012fdfb5b1d9a5cc5f079bbf4818f78a21 6767 goban_1.1-8_source.buildinfo Checksums-Sha256: 71994392992666da8ea6e539523f0398b2eced10e609f1b856bdb58c9e03453e 1868 goban_1.1-8.dsc 1d0603752d4746c8ceda61aba2b38fe6a8e29246f4aee6b0db693823ff4eaee5 7340 goban_1.1-8.debian.tar.xz 43a9aa11ca7f039a74aa9c5d04677f01ef8152e618f4aa8dc0b3b664a07e6aaa 6767 goban_1.1-8_source.buildinfo Files: 7dc79e69f32671969e7436862596fdc4 1868 x11 optional goban_1.1-8.dsc 4126141c89a807dc81734c5fba3c6112 7340 x11 optional goban_1.1-8.debian.tar.xz b36fc5b8cea547c0bf980b3fe24e4dc6 6767 x11 optional goban_1.1-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmbekY4ACgkQgSgKoIe6 +w42yw//Xz7Cl5ltAK1597hJPHvCOBHv3JH4ggu4gUWHPwcxmAVBS4q8I40iNCmV oh5Ivq9XTMNprzmwvbh90C048redQDj8hVh1rwAfJMfM8NQP3S5nNu2CxpPLOVAz BEQU37bRQQ9qhIVANKDCbVnM5uiN8jEVXtH2UfNtrxg9aveDjIAfCeFDKtzAUYlF 0XCprj5/R106LMorRmiikR6Pxddu0Pgv3iyEQFeebIEJMbhHbxWlEo85vqP4b4Bh Bs7NSXw9DBCczUakH/qJ3VD793fjEkfhFxzdVI8PjS1yELCnNx2thQn/3bWbt+Zs 2jujZaxaXrgoRRo2CyXqdoUNkDArGlrv+QHT48hzlRhYE5Pz4r9WbJdNunKaUJ30 3CRin9GwZEgiY/PGhlUOjDR8ieo6o3Z9hBGzGlgLt5a/SKFUw0sWfylgZw9FCouo 51y8RhqJWmibZj7NFQfd1ZGtUD6T2QEUTV2lhGYC2ube9NkFNWH8rjmaw/a1Yeoi Sda6is6O5Ya/0qKoducV5wzEcOBtmomHpg+BkyyqfBExit7w7OomVp84eggyahtT yV6xiL+6Uyh9Tn2SKkodhma2d9XhKD28Qs
Processed: Re: goban: ftbfs with GCC-14
Processing control commands: > tags -1 + patch Bug #1075032 [src:goban] goban: ftbfs with GCC-14 Added tag(s) patch. -- 1075032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: goban-ss: Goban-ss binary in incorrect location
Processing control commands: > tags -1 + patch Bug #993690 [goban-ss] goban-ss: Goban-ss binary in incorrect location Added tag(s) patch. -- 993690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039415: marked as done (watchcatd: ships sysv-init script without systemd unit)
Your message dated Sun, 08 Sep 2024 15:58:24 + with message-id and subject line Bug#1074225: Removed package(s) from unstable has caused the Debian Bug report #1039415, regarding watchcatd: ships sysv-init script without systemd unit 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.) -- 1039415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: watchcatd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), watchcatd has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being deprecated and will be removed by the time Trixie ships, so the remaining packages that ship init scripts without systemd units will stop working. There are various advantages to using native units, for example the legacy generator cannot tell the different between a oneshot service and a long running daemon. Also, sanboxing and security features become available for services. For more information, consult the systemd documentation: https://www.freedesktop.org/software/systemd/man/systemd.unit.html You can find the Lintian warning here: https://lintian.debian.org/sources/watchcatd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks! --- End Message --- --- Begin Message --- Version: 1.2.1-5+rm Dear submitter, as the package watchcatd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1074225 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#868736: marked as done (watchcatd: non-Englishness in description)
Your message dated Sun, 08 Sep 2024 15:58:24 + with message-id and subject line Bug#1074225: Removed package(s) from unstable has caused the Debian Bug report #868736, regarding watchcatd: non-Englishness in description 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.) -- 868736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: watchcatd Severity: minor Dear Maintainer, the long description of the packages contains the sentence "[...], the watchcat helps killing him." from the context it is clear that "him" refers to a locked up process. but in English - unlike in other languages lke German or French - things (like "processes") are referred to via a neutral pronoun "it", rather than it's gendered versions "he" or "she". thus the sentence should read: "[...], the watchcat helps killing it." -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages watchcatd depends on: ii libc6 2.24-12 ii libevent-2.0-5 2.0.21-stable-3 watchcatd recommends no packages. watchcatd suggests no packages. --- End Message --- --- Begin Message --- Version: 1.2.1-5+rm Dear submitter, as the package watchcatd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1074225 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: bug 1080998 is forwarded to https://gitlab.gnome.org/GNOME/gthumb/-/merge_requests/53
Processing commands for cont...@bugs.debian.org: > forwarded 1080998 https://gitlab.gnome.org/GNOME/gthumb/-/merge_requests/53 Bug #1080998 [src:gthumb] gthumb FTBFS on 32 bit architectures with 64 bit time_t with gcc 14 Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gthumb/-/merge_requests/53'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1080998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1078019: marked as done (cpupowergui: process org.rnd2.cpupower_gui exited with status 1)
Your message dated Fri, 06 Sep 2024 18:06:55 +0200
with message-id <172563881522.1163810.8041270626014217187@localhost>
and subject line Re: Bug#1078019: Acknowledgement (cpupowergui: process
org.rnd2.cpupower_gui exited with status 1) (SOLVED)
has caused the Debian Bug report #1078019,
regarding cpupowergui: process org.rnd2.cpupower_gui exited with status 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.)
--
1078019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpupower-gui
Version: 1.0.0-1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
today I can't start cpupower-gui, this error comes back:
$ cpupower-gui
Traceback (most recent call last):
File "/bin/cpupower-gui", line 367, in
from cpupower_gui import main
File "/usr/share/cpupower-gui/cpupower_gui/main.py", line 38, in
from .window import CpupowerGuiWindow
File "/usr/share/cpupower-gui/cpupower_gui/window.py", line 23, in
gi.require_version("Handy", "1")
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Handy not available
and I can't find the required "handy" module among the available packages.
Thanks,
Antonio
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (520, 'stable-security'), (500,
'stable-updates'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.10.3-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cpupower-gui depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2
ii gir1.2-gtk-3.0 3.24.43-1
ii hicolor-icon-theme 0.18-1
ii init-system-helpers 1.66
ii polkitd 124-3
ii python3 3.12.4-1
ii python3-dbus 1.3.2-5+b3
ii python3-gi 3.48.2-1+b1
cpupower-gui recommends no packages.
Versions of packages cpupower-gui suggests:
pn lxqt-policykit
pn lxsession
pn mate-polkit
ii policykit-1-gnome 0.105-8+b1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.0-2
On Mon, 12 Aug 2024 09:07:18 +0200 Antonio wrote:
> please add "gir1.2-handy-1 libhandy-1-0" package to dependences
>
> view https://github.com/vagnum08/cpupower-gui/issues/70
>
> now it works
Done in 1.0.0-2.
signature.asc
Description: signature
--- End Message ---
Bug#1080515: marked as done (ddcutil: FTBFS on arm{el,hf}: passing argument 2 of 'str_to_long' from incompatible pointer type)
Your message dated Fri, 6 Sep 2024 16:13:26 +0300
with message-id
and subject line Fixed in 2.1.4-3
has caused the Debian Bug report #1080515,
regarding ddcutil: FTBFS on arm{el,hf}: passing argument 2 of 'str_to_long'
from incompatible pointer type
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.)
--
1080515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddcutil
Version: 1.4.1-1
Severity: serious
Tags: ftbfs
Your package failed to build on armel and armhf:
dsa2.c: In function 'dsa2_adjust_for_rcnt_successes':
dsa2.c:782:63: warning: format '%ld' expects argument of type 'long int', but
argument 4 has type 'time_t' {aka 'long long int'} [-Wformat=]
dsa2.c: In function 'dsa2_save_persistent_stats':
dsa2.c:1193:44: warning: format '%ld' expects argument of type 'long int', but
argument 5 has type 'time_t' {aka 'long long int'} [-Wformat=]
dsa2.c: In function 'cirb_parse_and_add':
dsa2.c:1271:51: error: passing argument 2 of 'str_to_long' from incompatible
pointer type [-Wincompatible-pointer-types]
1271 | result &= str_to_long(comma_pos2 + 1, &si.epoch_seconds,
10);
| ^
| |
| time_t * {aka long
long int *}
In file included from ../../src/util/data_structures.h:22,
from dsa2.c:21:
../../src/util/string_util.h:96:46: note: expected 'long int *' but argument is
of type 'time_t *' {aka 'long long int *'}
96 | bool str_to_long( const char * sval, long * p_ival, int base);
| ^~
This is related to the recent 64bit time_t transition on arm{el,hf}.
Full build log at
https://buildd.debian.org/status/fetch.php?pkg=ddcutil&arch=armhf&ver=2.1.4-2&stamp=1725477887&raw=0
Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Version: 2.1.4-3
ddcutil (2.1.4-3) unstable; urgency=medium
...
* Update and rename debian/patches/fix-building-on-arm.patch to
fix-building-on-32bit.patch.
-- Soren Stoutner Thu, 05 Sep 2024 16:49:36 -0700--- End Message ---
Bug#1080460: marked as done (Autopkgtests fail with the setuptools 73.0.1-1)
Your message dated Fri, 06 Sep 2024 12:51:43 +
with message-id
and subject line Bug#1080460: fixed in python-svg.path 6.3-3
has caused the Debian Bug report #1080460,
regarding Autopkgtests fail with the setuptools 73.0.1-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.)
--
1080460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-svg.path
Version: 6.3-2
Severity: normal
The setuptools upstream version 72.0.0 removed support for the "test"
command expecting users to migrate to a different test runner [1].
The python-svg.path package is one of the affected packages. The reported
autopkgtest failure may be seen here [2]. This could be fixed
on the lines of [3].
[1] https://setuptools.pypa.io/en/stable/history.html#v72.0.0
[2]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-oracular/oracular/amd64/p/python-svg.path/20240826_170003_ee830@/log.gz
[3]
https://salsa.debian.org/python-team/packages/supervisor/-/commit/ea8be48cf0094cc11f38ca110470767a0109ab67
--- End Message ---
--- Begin Message ---
Source: python-svg.path
Source-Version: 6.3-3
Done: Pushkar Kulkarni
We believe that the bug you reported is fixed in the latest version of
python-svg.path, 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 1080...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pushkar Kulkarni (supplier of updated
python-svg.path package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 06 Sep 2024 14:23:18 +0200
Source: python-svg.path
Built-For-Profiles: noudeb
Architecture: source
Version: 6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Pushkar Kulkarni
Closes: 1079763 1080460
Changes:
python-svg.path (6.3-3) unstable; urgency=medium
.
* QA upload.
* d/{control,rules,test/control}: Move to using
autopkgtest-pkg-pybuild as the test runner.
(Closes: #1079763, #1080460)
* d/patches: Remove an unwanted patch.
Checksums-Sha1:
f857ad2f8ce85652daf06239cdc2b04793978850 2092 python-svg.path_6.3-3.dsc
9e3777145903caa0f31b2e870b2fb2a6b0a29bef 8176
python-svg.path_6.3-3.debian.tar.xz
522b161278e09a9d541ba0b712ef47f254da4cc3 10331
python-svg.path_6.3-3_source.buildinfo
Checksums-Sha256:
045c24f96836e17cd238d9881c778455f5f226d9ba365d996c4aaa3804d45e84 2092
python-svg.path_6.3-3.dsc
882bb274c614f4efff67f0a4cee706217ba2d31ecd68f929b8361b1b9cde6222 8176
python-svg.path_6.3-3.debian.tar.xz
fd894196d81ef2c7cb216fb4c9fd536429e994aa381e00f27fec2d6c8d7d22d1 10331
python-svg.path_6.3-3_source.buildinfo
Files:
77417382ddc253f758e4b258d1dfe483 2092 python optional python-svg.path_6.3-3.dsc
941fd2f8ca8a393e3ca16b02dba2ca03 8176 python optional
python-svg.path_6.3-3.debian.tar.xz
9fccd65fff919c9efb21b378c2a64b71 10331 python optional
python-svg.path_6.3-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmba9RMACgkQFZ61xO/I
d0yrAQ//ba1zBfHqqjlB9nyl39R1ycLI8m42lTAxefyhAuq1Ej/IGfzIJnlvNSON
HxMqbcF62rLP315nTGxLjGKaPxri08mCnwQ/1oQ2frzV1O2OWYhRPyjDVH1o74KO
9l2cF0ovUhpRWs4hgo0nbZzo4sa5ZZUfZD3GHMg9V45Lkt4Bnmtyz9jdojpjOKTI
ca5xqT/+LvKXZxfNj4YK/k6zwjKoJdvbg+b4ePiuyNcbvC2OYcdV0cAJqNoxqm2r
XudC1nGj6AI8z8iOg+0nyJ//4x0AdlBNaSnyPtC6m/iTr0BR33TzSfatkNxDIBPS
e68LqDk/q4jvp3J/GMas8jjf1NqaAAh9wKbC3uWePAHXB5GctHEIqQDGzLn0t6gc
l8i8WjTtpvG/yPj86WZBDgdioxqSHsHnnTKX93k2IKs8DqcFrulnapUCWGe1lFa7
4ZLr/FhkCVnYHro/YOm5L6dh552pfon/7sgIKbr4fmr5lOrszN5LezdANa9cV//b
ux7BfSUlmIsnggKuq7oJwwJpKlV7zqSguKNUjq+bgUxk84tsIDb7QEFzhVNV90tf
2r1A17+Zt6YQcKJxhXjT3DgYy+N8Xw65Huzt0uiA0k0TE+Zk6R/HkIx44jZsgVde
LJhuveTZ614AAvrHkMppiHW69dh3eUxKG7KxzeFebS2R+lyrMvw=
=7vwU
-END PGP SIGNATURE-
pgpqCiIwVwRNW.pgp
Description: PGP signature
--- End Message ---
Bug#1079763: marked as done (setuptools test command is removed)
Your message dated Fri, 06 Sep 2024 12:51:43 +
with message-id
and subject line Bug#1079763: fixed in python-svg.path 6.3-3
has caused the Debian Bug report #1079763,
regarding setuptools test command is removed
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.)
--
1079763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-svg.path
Version: 6.3-2
Severity: serious
Tags: sid trixie
setuptools test command is removed, the package at least uses this
command in it's autopkg tests.
setuptools v72.0.0:
Deprecations and Removals
-
- The test command has been removed. Users relying on 'setup.py test'
will need to migrate to another test runner or pin setuptools before
this version. (#931)
[...]
46s autopkgtest [04:08:35]: test command1: [---
47s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268:
UserWarning: Unknown distribution option: 'tests_require'
47s warnings.warn(msg)
47s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268:
UserWarning: Unknown distribution option: 'test_suite'
47s warnings.warn(msg)
47s usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
47sor: setup.py --help [cmd1 cmd2 ...]
47sor: setup.py --help-commands
47sor: setup.py cmd --help
47s
47s error: invalid command 'test'
--- End Message ---
--- Begin Message ---
Source: python-svg.path
Source-Version: 6.3-3
Done: Pushkar Kulkarni
We believe that the bug you reported is fixed in the latest version of
python-svg.path, 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 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pushkar Kulkarni (supplier of updated
python-svg.path package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 06 Sep 2024 14:23:18 +0200
Source: python-svg.path
Built-For-Profiles: noudeb
Architecture: source
Version: 6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Pushkar Kulkarni
Closes: 1079763 1080460
Changes:
python-svg.path (6.3-3) unstable; urgency=medium
.
* QA upload.
* d/{control,rules,test/control}: Move to using
autopkgtest-pkg-pybuild as the test runner.
(Closes: #1079763, #1080460)
* d/patches: Remove an unwanted patch.
Checksums-Sha1:
f857ad2f8ce85652daf06239cdc2b04793978850 2092 python-svg.path_6.3-3.dsc
9e3777145903caa0f31b2e870b2fb2a6b0a29bef 8176
python-svg.path_6.3-3.debian.tar.xz
522b161278e09a9d541ba0b712ef47f254da4cc3 10331
python-svg.path_6.3-3_source.buildinfo
Checksums-Sha256:
045c24f96836e17cd238d9881c778455f5f226d9ba365d996c4aaa3804d45e84 2092
python-svg.path_6.3-3.dsc
882bb274c614f4efff67f0a4cee706217ba2d31ecd68f929b8361b1b9cde6222 8176
python-svg.path_6.3-3.debian.tar.xz
fd894196d81ef2c7cb216fb4c9fd536429e994aa381e00f27fec2d6c8d7d22d1 10331
python-svg.path_6.3-3_source.buildinfo
Files:
77417382ddc253f758e4b258d1dfe483 2092 python optional python-svg.path_6.3-3.dsc
941fd2f8ca8a393e3ca16b02dba2ca03 8176 python optional
python-svg.path_6.3-3.debian.tar.xz
9fccd65fff919c9efb21b378c2a64b71 10331 python optional
python-svg.path_6.3-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmba9RMACgkQFZ61xO/I
d0yrAQ//ba1zBfHqqjlB9nyl39R1ycLI8m42lTAxefyhAuq1Ej/IGfzIJnlvNSON
HxMqbcF62rLP315nTGxLjGKaPxri08mCnwQ/1oQ2frzV1O2OWYhRPyjDVH1o74KO
9l2cF0ovUhpRWs4hgo0nbZzo4sa5ZZUfZD3GHMg9V45Lkt4Bnmtyz9jdojpjOKTI
ca5xqT/+LvKXZxfNj4YK/k6zwjKoJdvbg+b4ePiuyNcbvC2OYcdV0cAJqNoxqm2r
XudC1nGj6AI8z8iOg+0nyJ//4x0AdlBNaSnyPtC6m/iTr0BR33TzSfatkNxDIBPS
e68LqDk/q4jvp3J/GMas8jjf1NqaAAh9wKbC3uWePAHXB5GctHEIqQDGzLn0t6gc
l8i8WjTtpvG/yPj86WZBDgdioxqSHsHnnTKX93k2IKs8DqcFrulnapUCWGe1lFa7
4ZLr/FhkCVnYHro/YOm5L6dh552pfon/7sgIKbr4fmr5lOrszN5LezdANa9cV//b
ux7BfSUlmIsnggKuq7oJwwJpKlV7zqSguKNUjq+bgUxk84tsIDb7QEFzhVNV90tf
2r1A17+Zt6YQcKJxhXjT3DgYy+N8Xw65Huzt0uiA0k0TE+Zk6R/HkIx44jZsgVde
LJhuveTZ614AAvrHkMppiHW69dh3eUxKG7KxzeFebS2R+lyrMvw=
=7vwU
-END PGP SIGNATU
Processed: Bug#1079763 marked as pending in python-svg.path
Processing control commands: > tag -1 pending Bug #1079763 [src:python-svg.path] setuptools test command is removed Added tag(s) pending. -- 1079763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1080894: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Fri, 06 Sep 2024 04:06:22 + with message-id and subject line Bug#1080894: fixed in python-pmw 2.1-4 has caused the Debian Bug report #1080894, regarding Missing Build-Depends on 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.) -- 1080894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pmw Version: 2.1-3 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: python-pmw Source-Version: 2.1-4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of python-pmw, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated python-pmw 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: Thu, 05 Sep 2024 23:45:31 -0400 Source: python-pmw Architecture: source Version: 2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 1080894 Changes: python-pmw (2.1-4) unstable; urgency=medium . * QA upload. * debian/control: Add missing build-dep python3-setuptools. (Closes: #1080894) Checksums-Sha1: c4c1029612eea4310f604fb43d3507372b912714 1988 python-pmw_2.1-4.dsc 8f6c2aea0a46dda6afd858cf1df204c0e7114249 1076920 python-pmw_2.1.orig.tar.gz 1f09a9fb5092c738410fd9dccf6ef576cd39068c 5280 python-pmw_2.1-4.debian.tar.xz 6daab3184064c5d492b82dc38dae799e30e71607 7701 python-pmw_2.1-4_amd64.buildinfo Checksums-Sha256: 40d33df2f2ea51205ab8695c96ed9b92c20f9be06940366aaa416df30c9f9e8d 1988 python-pmw_2.1-4.dsc c35a92a6cabacd866467f7a1a19ab01b8e8175aadfc083c93ac8baf98e92b6ce 1076920 python-pmw_2.1.orig.tar.gz 211a7df72895b98de35792436102026bd5015eedcafc8f74af654bcd15b920b4 5280 python-pmw_2.1-4.debian.tar.xz 5ba689b7d4e7ae2389713210abc174f6e44e68fe4e7e933fe37fb5cbced448ab 7701 python-pmw_2.1-4_amd64.buildinfo Files: f3d24634ab071aa9c3c3afbda4237d1e 1988 python optional python-pmw_2.1-4.dsc 64bb62cb851a6c915be6f98e56a89e4e 1076920 python optional python-pmw_2.1.orig.tar.gz 91ae7ca803247cb75ed6d8c307d6ada0 5280 python optional python-pmw_2.1-4.debian.tar.xz a52f66f6f555251a101b598935e7f420 7701 python optional python-pmw_2.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmbae3kACgkQwpPntGGC Ws4ZTRAAoJwdorv7UTPxYGltUFCT/zLiA+XF9f+dARrAIcfJ+MxyaZiciaHMVA5M NVRApNix2lrwp3x/vlSGoSMieEO3AtwcIqkyNFffRRHMF/KWCFqdZFzVupHXnGQV aItQ6diMRawaOcHKJF2PGV4LkSTHyk21wJdlsKwJ+BHL0GmuQtu+4bHx2g5JHqRU mKI1Fmpl+UyPRJVDR3cWnw+v4jXip9UgomXHwqka9gfk5o17kacBREQxn7EDiL/f iZL4ffskQWjWgFG24A99H6y/zSS5KsJrVO0HlyaTIjsH4m0U4bmu3Nb5CTk2iSKd 3ESY/MZvdNgE5v6XAkKj2wcTlBrGknFcn4YCbAxcWir4SazmhdC1s0HcvnSywslf vU6kOcNdA8G3BeLj6wJdVTxIiZ3YHdoo/Q9dH8GYpv6X6umELcGy+U/oBwDCXrcF BPsscsWrjE7ogvff9ra/FP4ZtzbGm5mmFNPpYUWeEiQhuuAz9t/RlrHujWsCI2nC VB81tXXu59BjCAKz+YusGHyFR51bHk68huwbJ331JLm1pM5AdBGfk66ZBRqCcyru ICCaSTNTUrlf88ak34jsB+hFbJuw1hxJYzsEsXwa/iKDPFQKiszWGFNAcRGy9DtG WLmb/NJOOodg8sNu1LeCHYg5EXNl7y+a9YGuHJ4jf+vbZwrEgtE= =awuE -END PGP SIGNATURE- pgpBJoXDH7N6g.pgp Description: PGP signature --- End Message ---
Bug#1080839: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Thu, 5 Sep 2024 17:41:42 +0200 with message-id and subject line Whoops, existing FTBFS has caused the Debian Bug report #1080839, regarding Missing Build-Depends on 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.) -- 1080839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xmms2 Version: 0.8+dfsg-26 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Whoops, this was an existing FTBFS, should not have been part of the mass-bug filing. Sorry for the noise. Stefano--- End Message ---
Bug#953938: marked as done (zfs-fuse: Switch from deprecated to )
Your message dated Thu, 05 Sep 2024 14:54:09 + with message-id and subject line Bug#953938: fixed in zfs-fuse 0.7.0-29 has caused the Debian Bug report #953938, regarding zfs-fuse: Switch from deprecated to 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.) -- 953938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zfs-fuse Source-Version: 0.7.0-20 Severity: important User: a...@packages.debian.org Usertags: libattr-drop-attr-xattr-header Hi! This package uses the deprecated header (from libattr) instead of the one provided now by glibc . The former header has been removed in upstream libattr, but got reintroduced in Debian to avoid breakage just before the Debian buster freeze. But I'd like to be able to remove it in Debian too, so that the interface can be synced with upstream. It looks like this is the only header used by this package from libattr, so you should be able to drop the dependency on libattr entirely, as glibc should be providing all that is needed now. Thanks, Guillem --- End Message --- --- Begin Message --- Source: zfs-fuse Source-Version: 0.7.0-29 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of zfs-fuse, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated zfs-fuse 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, 05 Sep 2024 15:19:32 +0200 Source: zfs-fuse Architecture: source Version: 0.7.0-29 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Hilko Bengen Closes: 953938 Changes: zfs-fuse (0.7.0-29) unstable; urgency=medium . * QA upload. * Add patch to use sys/xattr.h instead of xattr/xattr.h (Closes: #953938) Checksums-Sha1: 288d705c9a940d0d5002e0e5f66a17406de2b5a2 2025 zfs-fuse_0.7.0-29.dsc 8c31c7a2ffde4f3c1c517ca5838e898e0997ab09 30924 zfs-fuse_0.7.0-29.debian.tar.xz 7e375190d8089e7484e3d7811359b99bee10afa9 7915 zfs-fuse_0.7.0-29_source.buildinfo Checksums-Sha256: a09e06510fb7e562c5142d5bb8a82f3906c1105a28cc5a525135011be14b7ffd 2025 zfs-fuse_0.7.0-29.dsc f3d2d91123f030839fb962be0b3ca8fe9c525d206c124b1d1d20158a86f584c8 30924 zfs-fuse_0.7.0-29.debian.tar.xz 19e680672103cc1c5e28563edaae52ae00eec2666ef5d831bf73e0a458b3b5f3 7915 zfs-fuse_0.7.0-29_source.buildinfo Files: cd030d5b564df846a62d6da5b8b5a6c2 2025 otherosfs optional zfs-fuse_0.7.0-29.dsc 92c395c86074e1223911be9c5d2b6aaa 30924 otherosfs optional zfs-fuse_0.7.0-29.debian.tar.xz 356a10b45dcd7940a4e6b0b640992a46 7915 otherosfs optional zfs-fuse_0.7.0-29_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmbZuNUACgkQdbcQY1wh On7yWQ/+K5ias/gDWPe8WH/s/NIxoTFiinuy6KaYLP/eU8IjqsbCuVgr1D1Fjk8s FqcQOS1JqRDDHn2kp7XXw+d2hWlQ3HnBO7hs5j0mhfYdHz6IiSZnCSjdXqif7SR3 7IH/SUni9bafibVaEY3yRWEdTfHKY3Qjjx4yscpC+RiAkqQJjfRNyCwy1wgF9Trv c62NeDz6q6J1kNrgj2MMMXRz0QaS3/aBKwsOdtLXxRnBb5hO5a/+5O1GXCpDZAV8 ghgg+Y9ILUshf1L+rutxfElPJZgYdcx6esuoAYk16jkx6bnaSkWfmJparoa3fp0+ ZvA+Cs027cp8TRb0LFT0nOJR6vWoeA5Un40qDk4bgopzZXGSz1MfmYIHB22r3chE tgvXMD/1a7g/Km6vIllO3x0Teik1UInD2xyIsE7gL1LU882r+u7OkAJIVgjYt1et z50P+fR08yQTVR3o7LkYn0qsgozSVkeyptfNEJutFt/KVX9kktQKazNxvCYCVHg3 BdEMrgKF3qOrJlFnCy+I5aJJlCS49Ieka6D6Uqh+u1PYlBpZZDuHx2U7Z4GPEDo6 CMJrPLDCR3Na3BZaMnJdouMQ45jAxrsRUouqtowIyj8Z0tQeOfbb17LDPLBHVMbl NU6o5/Fopk+KDwvhmWPgHy62EZbKghAYBeR6Cet8lHMlAIyPdb4= =EJ4d -END PGP SIGNATURE- pgpdF_8D9Jj8c.pgp Description: PGP signature --- End Message ---
Bug#1079258: marked as done (gnome-shell-mailnag: needs update for GNOME Shell 47)
Your message dated Wed, 04 Sep 2024 04:43:51 + with message-id and subject line Bug#1080310: Removed package(s) from unstable has caused the Debian Bug report #1079258, regarding gnome-shell-mailnag: needs update for GNOME Shell 47 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.) -- 1079258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-mailnag Version: 40.0-7 Severity: wishlist Tags: trixie sid upstream User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-47 As with every 6-month GNOME Shell release cycle, extensions will need to be updated for GNOME Shell 47, which is currently being prepared in experimental. A porting guide is available here: https://gjs.guide/extensions/upgrading/gnome-shell-47.html It might be as simple as adding 47 to the list of supported versions in metadata.json, or it might require more involved code changes. I couldn't see an upstream issue for this. GNOME 47 is expected to be the version that is shipped in the Debian 13 'trixie' stable release. If not updated, this extension will have to be removed from testing for the GNOME Shell 47 transition in late 2024. This bug will be raised to serious severity when the transition is ready to go ahead. smcv --- End Message --- --- Begin Message --- Version: 40.0-7+rm Dear submitter, as the package gnome-shell-mailnag has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080310 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#948134: marked as done (gnome-shell-mailnag FTCBFS: stores valac in CC)
Your message dated Wed, 04 Sep 2024 04:43:51 + with message-id and subject line Bug#1080310: Removed package(s) from unstable has caused the Debian Bug report #948134, regarding gnome-shell-mailnag FTCBFS: stores valac in CC 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.) -- 948134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-shell-mailnag Version: 3.28.0-0.1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: block -1 by 948128 gnome-shell-mailnag fails to cross build from source, because its Makefile stores valac in CC. dh_auto_build supplies a c compiler there and that fails. Passing the right vala compiler fixes this part. However, the cross build then fails due to #948128. Please consider applying the attached patch. Helmut diff --minimal -Nru gnome-shell-mailnag-3.28.0/debian/changelog gnome-shell-mailnag-3.28.0/debian/changelog --- gnome-shell-mailnag-3.28.0/debian/changelog 2018-11-03 22:18:05.0 +0100 +++ gnome-shell-mailnag-3.28.0/debian/changelog 2020-01-04 12:15:54.0 +0100 @@ -1,3 +1,10 @@ +gnome-shell-mailnag (3.28.0-0.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Pass valac as CC. (Closes: #-1) + + -- Helmut Grohne Sat, 04 Jan 2020 12:15:54 +0100 + gnome-shell-mailnag (3.28.0-0.1) unstable; urgency=medium * Non-maintainer upload diff --minimal -Nru gnome-shell-mailnag-3.28.0/debian/rules gnome-shell-mailnag-3.28.0/debian/rules --- gnome-shell-mailnag-3.28.0/debian/rules 2018-11-03 22:18:05.0 +0100 +++ gnome-shell-mailnag-3.28.0/debian/rules 2020-01-04 12:15:54.0 +0100 @@ -1,7 +1,18 @@ #!/usr/bin/make -f +include /usr/share/dpkg/architecture.mk + +ifeq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) +VALAC ?= valac +else +VALAC ?= $(DEB_HOST_GNU_TYPE)-valac +endif + %: dh $@ +override_dh_auto_build: + dh_auto_build -- CC=$(VALAC) + override_dh_auto_install: $(MAKE) install prefix="$(CURDIR)/debian/gnome-shell-mailnag/usr" --- End Message --- --- Begin Message --- Version: 40.0-7+rm Dear submitter, as the package gnome-shell-mailnag has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080310 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1078015: marked as done (gnome-shell-mailnag: works poorly)
Your message dated Wed, 04 Sep 2024 04:43:51 + with message-id and subject line Bug#1080310: Removed package(s) from unstable has caused the Debian Bug report #1078015, regarding gnome-shell-mailnag: works poorly 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.) -- 1078015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-shell-mailnag Version: 40.0-7 Severity: serious The user interface for gnome-shell-mailnag is really poor. - The top bar main icon is missing - When I tested it today, the menu stopped working completely - It requires configuring email through a separate app (which is installed via Depends at least) - I got this error in my systemd journal gnome-shell: JS ERROR: ReferenceError: assignment to undeclared variable ext enable/this.watch_id--- End Message --- --- Begin Message --- Version: 40.0-7+rm Dear submitter, as the package gnome-shell-mailnag has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080310 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#978012: marked as done (xsddiagram: No diagram is shown)
Your message dated Wed, 04 Sep 2024 04:31:46 + with message-id and subject line Bug#1079905: Removed package(s) from unstable has caused the Debian Bug report #978012, regarding xsddiagram: No diagram is shown 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.) -- 978012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xsddiagram Version: 1.0-1 Severity: important X-Debbugs-Cc: vincent.vsme...@gmail.com Hello, I just installed xsddiagram and opened an xsd file. It shows the window and all the tabs for the included xsd files. The tabs are however all empty. No error messages are shown. So it looks like the files are opened correctly but the graphics aren't shown. I am using XWayland. Is it possible that xsddiagram is only working with X11 and not with XWayland? Regards, Vincent -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xsddiagram depends on: ii libmono-corlib4.5-cil6.8.0.105+dfsg-3 ii libmono-system-drawing4.0-cil6.8.0.105+dfsg-3 ii libmono-system-windows-forms4.0-cil 6.8.0.105+dfsg-3 ii libmono-system-xml4.0-cil6.8.0.105+dfsg-3 ii libmono-system4.0-cil6.8.0.105+dfsg-3 ii mono-runtime 6.8.0.105+dfsg-3 xsddiagram recommends no packages. xsddiagram suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.0-2+rm Dear submitter, as the package xsddiagram has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079905 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#907974: marked as done (perl-doc-html: Should be updated to 5.28 at the point of the transition)
Your message dated Wed, 04 Sep 2024 04:10:48 + with message-id and subject line Bug#1079690: Removed package(s) from unstable has caused the Debian Bug report #907974, regarding perl-doc-html: Should be updated to 5.28 at the point of the transition 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.) -- 907974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl-doc-html Version: 5.26.0-4 Severity: wishlist User: debian-p...@lists.debian.org Usertags: perl-5.28-transition X-Debbugs-Cc: p...@packages.debian.org We should make this bug serious at the point of the 5.28 transition so that we don't end up releasing with documentation for the wrong version of perl. See #907273 and #154963 for additional context. --- End Message --- --- Begin Message --- Version: 5.26.0-7+rm Dear submitter, as the package perl-doc-html has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079690 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: tagging 1070885, tagging 1079650, tagging 1080199, tagging 1080140, tagging 1080135, tagging 1080130 ...
Processing commands for cont...@bugs.debian.org:
> tags 1070885 + sid trixie
Bug #1070885 {Done: Jonathan McDowell } [src:openocd]
openocd: FTBFS with libgpiod/2.1
Added tag(s) trixie and sid.
> tags 1079650 + sid trixie
Bug #1079650 [src:devscripts] devscripts: FTBFS due to use of `setup.py test`
(removed in setuptools 72)
Added tag(s) trixie and sid.
> tags 1080199 + sid trixie
Bug #1080199 [src:parmetis] parmetis: autopkgtest regressions with mpich as
default provider on 32 bit architectures
Added tag(s) sid and trixie.
> tags 1080140 + sid trixie
Bug #1080140 [src:sshguard] sshguard: FTBFS: ./configure: line 5319: syntax
error near unexpected token `;;'
Added tag(s) sid and trixie.
> tags 1080135 + sid trixie
Bug #1080135 [src:python-ofxhome] python-ofxhome: FTBFS: ERROR:
testOptionalBroker
(ofxhome.tests.test_suite.InstitutionTestCase.testOptionalBroker)
Added tag(s) sid and trixie.
> tags 1080130 + sid trixie
Bug #1080130 [src:python-funcsigs] python-funcsigs: FTBFS: ERROR: test_readme
(tests.test_funcsigs.TestFunctionSignatures)
Added tag(s) sid and trixie.
> tags 1080127 + sid trixie
Bug #1080127 [src:python-bitcoinlib] python-bitcoinlib: FTBFS: ERROR:
test_tx_invalid
(bitcoin.tests.test_transactions.Test_CTransaction.test_tx_invalid)
Added tag(s) trixie and sid.
> tags 1080126 + sid trixie
Bug #1080126 [src:python-applicationinsights] python-applicationinsights:
FTBFS: ModuleNotFoundError: No module named 'django'
Added tag(s) trixie and sid.
> tags 1080125 + sid trixie
Bug #1080125 [src:pyramid-jinja2] pyramid-jinja2: FTBFS: ModuleNotFoundError:
No module named 'pyramid.scaffolds'
Added tag(s) trixie and sid.
> tags 1080123 + sid trixie
Bug #1080123 [src:pycollada] pycollada: FTBFS: FAIL: test_cimage_data_loading
(collada.tests.test_material.TestMaterial.test_cimage_data_loading)
Added tag(s) trixie and sid.
> tags 1080116 + sid trixie
Bug #1080116 [src:manuel] manuel: FTBFS: TypeError: TestCase.__init__() missing
2 required positional arguments: 'regions' and 'globs'
Added tag(s) trixie and sid.
> tags 1080111 + sid trixie
Bug #1080111 [src:gstreamermm-1.0] gstreamermm-1.0: FTBFS: ./configure: line
19147: syntax error near unexpected token `fi'
Added tag(s) sid and trixie.
> tags 1080101 + sid trixie
Bug #1080101 [src:dbus-deviation] dbus-deviation: FTBFS: ERROR:
test_multiline_comments
(dbusapi.tests.test_interfaceparser.TestParserNormal.test_multiline_comments)
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070885
1079650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079650
1080101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080101
1080111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080111
1080116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080116
1080123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080123
1080125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080125
1080126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080126
1080127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080127
1080130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080130
1080135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080135
1080140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080140
1080199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1080232, tagging 1080234, tagging 1080275, tagging 1080276, tagging 1080277, tagging 1080278 ...
Processing commands for cont...@bugs.debian.org: > tags 1080232 + sid trixie Bug #1080232 [src:python-pgpdump] FTBFS with setuptools 72: error: invalid command 'test' Added tag(s) trixie and sid. > tags 1080234 + sid trixie Bug #1080234 [src:serpent] FTBFS with setuptools 72: error: invalid command 'test' Added tag(s) sid and trixie. > tags 1080275 + sid trixie Bug #1080275 [src:hovercraft] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) sid and trixie. > tags 1080276 + sid trixie Bug #1080276 [src:morfessor] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) sid and trixie. > tags 1080277 + sid trixie Bug #1080277 [src:pyemd] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) trixie and sid. > tags 1080278 + sid trixie Bug #1080278 [src:python-autopage] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) trixie and sid. > tags 1080281 + sid trixie Bug #1080281 [src:python-mujson] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) trixie and sid. > tags 1080282 + sid trixie Bug #1080282 [src:python-potr] FTBFS with setuptools >= 72: error: invalid command 'test' Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1080232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080232 1080234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080234 1080275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080275 1080276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080276 1080277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080277 1080278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080278 1080281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080281 1080282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: b43 wlan0 disappears when on battery
Processing control commands: > close -1 Bug #696811 [firmware-b43-installer] b43 wlan0 disappears when on battery Marked Bug as done -- 696811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: firmware-b43-installer: Drivers in this package are not available in debian-12.0.0-amd64-netinst.iso at time of writing.
Processing control commands: > tags -1 wontfix Bug #1041004 [firmware-b43-installer] firmware-b43-installer: Drivers in this package are not available in debian-12.0.0-amd64-netinst.iso at time of writing. Added tag(s) wontfix. > close -1 Bug #1041004 [firmware-b43-installer] firmware-b43-installer: Drivers in this package are not available in debian-12.0.0-amd64-netinst.iso at time of writing. Marked Bug as done -- 1041004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 668613 964140
Processing commands for cont...@bugs.debian.org: > forcemerge 668613 964140 Bug #668613 [firmware-b43-installer] firmware-b43-installer: postinst not working if second broadcom chip exists Bug #668633 [firmware-b43-installer] firmware-b43-installer: postinst does not work if second card present Bug #668633 [firmware-b43-installer] firmware-b43-installer: postinst does not work if second card present Marked as found in versions b43-fwcutter/1:019-6. Marked as found in versions b43-fwcutter/1:019-6. Bug #964140 [firmware-b43-installer] V1:19-6 loads wrong firmware when >1 Broadcom network adapter present Severity set to 'important' from 'normal' Marked as found in versions b43-fwcutter/1:015-14 and b43-fwcutter/1:015-12. Added tag(s) moreinfo. Merged 668613 668633 964140 > thanks Stopping processing here. Please contact me if you need assistance. -- 668613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668613 668633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668633 964140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 742555
Processing commands for cont...@bugs.debian.org: > close 742555 Bug #742555 [firmware-b43-installer] firmware-b43-installer: BCM4306 Wireles controller fails to start after upgrade memory to 2GB Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 742555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: metadata
Processing commands for cont...@bugs.debian.org: > found 1053015 0.6.0-1.1 Bug #1053015 [src:cava] cava: FTBFS with OpenJDK 21 due to new compiler warnings Ignoring request to alter found versions of bug #1053015 to the same values previously set > tags 1078338 + ftbfs Bug #1078338 [src:cuneiform] cuneiform: FTBFS with GCC 14: error: type defaults to 'int' in declaration of 'broken_ii' Added tag(s) ftbfs. > found 1075223 5.2.0-4.3 Bug #1075223 [src:linphone] linphone: ftbfs with GCC-14 Ignoring request to alter found versions of bug #1075223 to the same values previously set > found 1053068 2.2-2 Bug #1053068 [src:openhft-affinity] openhft-affinity: FTBFS with default Java 21 Marked as found in versions openhft-affinity/2.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053015 1053068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053068 1075223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075223 1078338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949265: marked as done (URL www[dot]htdig[dot]org is advertisement)
Your message dated Fri, 30 Aug 2024 13:20:29 + with message-id and subject line Bug#949265: fixed in htdig 1:3.2.0b6-21 has caused the Debian Bug report #949265, regarding URL www[dot]htdig[dot]org is advertisement 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.) -- 949265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: htdig Version: 1:3.2.0b6-18 The URL www[dot]htdig[dot]org, which is embedded throughout the htdig code and installed files, is now an advertisement site. Since it is no longer under control of the ht://Dig project, Debian (and derivatives) should consider removing or replacing the links and references to www[dot]htdig[dot]org. - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE3RmV4WutJ2KyCS2zPcxbabkKGJ8FAl4j7sQACgkQPcxbabkK GJ+oAQ//fc3rQRqYL7m71lTcRtzcD6wplZ3HzMEXQYDASroV0wikXgSpevPv6YQI LJSeUO1Wsc/iUebMJaO/J7Pcss5vo2neUv0IOcG2hXnmlx0J3HiRE2+uRBreofnS L8cMbZvyil4GQOKkgzp7V4DpYfkfiCP6UWWPsA5zd8L09V+HN1na2ET9wYctDZd6 GHTNdARAa31rIxqMePLiQAPbixQYKNC9/5uL30gTCQO1V6yNWy480z0T3zOmfdRc /tXuBYE5x3DI8FVxE8rLN+mNywgCrMkf6fMvCZfJ7PpesBThFnAFdSusP1YrpFr4 cVUG9eNZcoZpsKUEyFUhq3RWZKv03rDg8L40B69p06hY9vV+SuBLuE6Qfaj65HXl LT1hdCM9oU8Q/AxXbmt9FcFZplWeoM7Nwa2ueL4BkZXqi8N/dxsXhjE+LwF6VCbI 7eV9IMx85eALm/mKE6njPUcsKjyjAhJ1JIrKlUKpmwuF7g4ntYrkXF1CJ3kh57Y0 jh3cFp6xFNQ3Ot5D/hlMY6/4+JKpJ2Se7EqAk0b4aYFBy14vZi2oTxoko3lelRoJ oqgiAWL6/Q4XiwRxLlLgKrYyA111ZBx4XnbIgV0ksIpOKl9QT5thDQm0IAH090yT 65IovLOoGsKjqPyYhEVLRkUBywThIoGnjdGsu3fAZZ0pD705iPY= =XgAq -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: htdig Source-Version: 1:3.2.0b6-21 Done: Roland Rosenfeld We believe that the bug you reported is fixed in the latest version of htdig, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Rosenfeld (supplier of updated htdig 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, 30 Aug 2024 14:49:52 +0200 Source: htdig Architecture: source Version: 1:3.2.0b6-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Roland Rosenfeld Closes: 133086 949265 1040977 Changes: htdig (1:3.2.0b6-21) unstable; urgency=medium . * QA upload. * Add debian/gbp.conf for pristine-tar and branch-names. * Add Vcs-Git/Vcs-Browser. * Update to Standards-Version 4.7.0. * Switch to debhelper-compat (= 13). * Remove README from htdig-doc, otherwise it conflicts with htdig pkg. * Add debian/salsa-ci.yml pipeline. * debian/watch: Redirect URL to htdig.sourceforge.net. * Replace rmdir by rm -rf to remove empty xmlsearch dirs. * Add Homepage to debian/control. * Enable SSL support (Closes: #133086, #1040977). * homepage-url.patch: Change all homepage-links to https://htdig.sourceforge.net, since old homepage no longer exists (Closes: #949265). Checksums-Sha1: 5b34233d873b59102c95e175603274187e89a868 1904 htdig_3.2.0b6-21.dsc a48131b5474e7b317f52d6ebca85825edd575035 65400 htdig_3.2.0b6-21.debian.tar.xz 9f47bd0f2ee1407ef441a9212379483d4bf76993 6319 htdig_3.2.0b6-21_source.buildinfo Checksums-Sha256: 207152b4f3b3300d1cc660ba573f5829c55ca42c599e31ad14d54c8febe1a9c2 1904 htdig_3.2.0b6-21.dsc 002937c6a10ad5cb788ffb27ce07180b47059560e71dfdeae157b4b437416026 65400 htdig_3.2.0b6-21.debian.tar.xz 265796b2c1208e745e39231732661d8e5d266e17826d6796564c2cd4da7c299b 6319 htdig_3.2.0b6-21_source.buildinfo Files: 9e36471c4bce7563e2befd76e2ae7d2a 1904 web optional htdig_3.2.0b6-21.dsc 408c3a1540fca8363991c2cd134c3ed5 65400 web optional htdig_3.2.0b6-21.debian.tar.xz 0e290ec9327a48fa872e37c63862125f 6319 web optional htdig_3.2.0b6-21_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAmbRwBIACgkQAnE7z8pU ELJgqg/+ObYBfZa+z3pAjksUUdPQu0s7CbfP/8u0Jrb/5AOIIHSmZiEtrFynFfRb diFb09iYSUmTnurq3r33X+PntsLVrCU7qzRO/DgORrYFxwTZ5H4kvD5N44vj0MH8 6e4yiO4HOELiTc7pH3AP3hdnee99F9cz/ssZT3f2Ia1C+XQx9rjoEgDgrv4RbWjN U8EO20WA1Y60J1wvnuN
Bug#133086: marked as done (htdig-ssl version with https: support)
Your message dated Fri, 30 Aug 2024 13:20:29 + with message-id and subject line Bug#133086: fixed in htdig 1:3.2.0b6-21 has caused the Debian Bug report #133086, regarding htdig-ssl version with https: support 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.) -- 133086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=133086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: htdig Version: 3.1.6-0.snapshot08 Severity: wishlist Tags: patch Hello, maybe you will build a non_US version with https: support. The needed patches are not in the upstream sources but on the website www.htdig.org: http://htdig.org/contrib/ -> Patches or direct: ftp://ftp.ccsf.org/htdig-patches/ ftp://ftp.ccsf.org/htdig-patches/3.1.6/ssl.9 Would be great. Thanks. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux debian 2.4.16-pre1 #2 Sun Nov 25 21:33:40 CET 2001 i686 Locale: LANG=de_DE.ISO-8859-1, LC_CTYPE=en_US Versions of packages htdig depends on: ii libc6 2.2.4-7 GNU C Library: Shared libraries an ii libdb2 2:2.7.7.0-3.1 The Berkeley database routines (ru ii libstdc++2.10-glibc2.2 1:2.95.4-1The GNU stdc++ library ii lockfile-progs 0.1.9 Programs for locking and unlocking ii perl 5.6.1-7 Larry Wall's Practical Extraction ii zlib1g 1:1.1.3-19compression library - runtime --- End Message --- --- Begin Message --- Source: htdig Source-Version: 1:3.2.0b6-21 Done: Roland Rosenfeld We believe that the bug you reported is fixed in the latest version of htdig, 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 133...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Rosenfeld (supplier of updated htdig 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, 30 Aug 2024 14:49:52 +0200 Source: htdig Architecture: source Version: 1:3.2.0b6-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Roland Rosenfeld Closes: 133086 949265 1040977 Changes: htdig (1:3.2.0b6-21) unstable; urgency=medium . * QA upload. * Add debian/gbp.conf for pristine-tar and branch-names. * Add Vcs-Git/Vcs-Browser. * Update to Standards-Version 4.7.0. * Switch to debhelper-compat (= 13). * Remove README from htdig-doc, otherwise it conflicts with htdig pkg. * Add debian/salsa-ci.yml pipeline. * debian/watch: Redirect URL to htdig.sourceforge.net. * Replace rmdir by rm -rf to remove empty xmlsearch dirs. * Add Homepage to debian/control. * Enable SSL support (Closes: #133086, #1040977). * homepage-url.patch: Change all homepage-links to https://htdig.sourceforge.net, since old homepage no longer exists (Closes: #949265). Checksums-Sha1: 5b34233d873b59102c95e175603274187e89a868 1904 htdig_3.2.0b6-21.dsc a48131b5474e7b317f52d6ebca85825edd575035 65400 htdig_3.2.0b6-21.debian.tar.xz 9f47bd0f2ee1407ef441a9212379483d4bf76993 6319 htdig_3.2.0b6-21_source.buildinfo Checksums-Sha256: 207152b4f3b3300d1cc660ba573f5829c55ca42c599e31ad14d54c8febe1a9c2 1904 htdig_3.2.0b6-21.dsc 002937c6a10ad5cb788ffb27ce07180b47059560e71dfdeae157b4b437416026 65400 htdig_3.2.0b6-21.debian.tar.xz 265796b2c1208e745e39231732661d8e5d266e17826d6796564c2cd4da7c299b 6319 htdig_3.2.0b6-21_source.buildinfo Files: 9e36471c4bce7563e2befd76e2ae7d2a 1904 web optional htdig_3.2.0b6-21.dsc 408c3a1540fca8363991c2cd134c3ed5 65400 web optional htdig_3.2.0b6-21.debian.tar.xz 0e290ec9327a48fa872e37c63862125f 6319 web optional htdig_3.2.0b6-21_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAmbRwBIACgkQAnE7z8pU ELJgqg/+ObYBfZa+z3pAjksUUdPQu0s7CbfP/8u0Jrb/5AOIIHSmZiEtrFynFfRb diFb09iYSUmTnurq3r33X+PntsLVrCU7qzRO/DgORrYFxwTZ5H4kvD5N44vj0MH8 6e4yiO4HOELiTc7pH3AP3hdnee99F9cz/ssZT3f2Ia1C+XQx9rjoEgDgrv4RbWjN U8EO20WA1Y60J1wvnuN/7YX1McXE+Cn+bSJbA4ULRncixvHrQ8N5L8bMejcjm/qa BO6jgJexTmxvFTA0XALYThVGvVYqF65lLqkYxJJBGFtHPzZPZqDrHp107GZz5OvM QU9nL0KMZ2sn0fn43aa7VMDNi8fWMJVUI0WRrWg4JpuTlqN7IpoRDynL
Bug#1040977: marked as done (htdig built without SSL support)
Your message dated Fri, 30 Aug 2024 13:20:29 + with message-id and subject line Bug#1040977: fixed in htdig 1:3.2.0b6-21 has caused the Debian Bug report #1040977, regarding htdig built without SSL support 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.) -- 1040977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: htdig Version: 1:3.2.0b6-19+b1 Severity: important Dear Maintainer, The version of htdig shipped with Debian Bookworm is built without SSL support and cannot index HTTPS sites. The simple fix is to add "--with-ssl" to the configure invocation in debian/rules; I have built my own debian packages with this change and have verified that it works. Regards, Dianne. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.3 (SMP w/1 CPU thread; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages htdig depends on: ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9 ii libstdc++6 12.2.0-14 ii lockfile-progs 0.1.19 ii perl 5.36.0-7 ii zlib1g 1:1.2.13.dfsg-1 htdig recommends no packages. Versions of packages htdig suggests: ii apache2 [httpd] 2.4.57-2 pn htdig-doc -- Configuration Files: /etc/htdig/footer.html changed [not included] /etc/htdig/header.html changed [not included] /etc/htdig/htdig.conf changed [not included] /etc/htdig/nomatch.html changed [not included] -- debconf information excluded --- End Message --- --- Begin Message --- Source: htdig Source-Version: 1:3.2.0b6-21 Done: Roland Rosenfeld We believe that the bug you reported is fixed in the latest version of htdig, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Rosenfeld (supplier of updated htdig 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, 30 Aug 2024 14:49:52 +0200 Source: htdig Architecture: source Version: 1:3.2.0b6-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Roland Rosenfeld Closes: 133086 949265 1040977 Changes: htdig (1:3.2.0b6-21) unstable; urgency=medium . * QA upload. * Add debian/gbp.conf for pristine-tar and branch-names. * Add Vcs-Git/Vcs-Browser. * Update to Standards-Version 4.7.0. * Switch to debhelper-compat (= 13). * Remove README from htdig-doc, otherwise it conflicts with htdig pkg. * Add debian/salsa-ci.yml pipeline. * debian/watch: Redirect URL to htdig.sourceforge.net. * Replace rmdir by rm -rf to remove empty xmlsearch dirs. * Add Homepage to debian/control. * Enable SSL support (Closes: #133086, #1040977). * homepage-url.patch: Change all homepage-links to https://htdig.sourceforge.net, since old homepage no longer exists (Closes: #949265). Checksums-Sha1: 5b34233d873b59102c95e175603274187e89a868 1904 htdig_3.2.0b6-21.dsc a48131b5474e7b317f52d6ebca85825edd575035 65400 htdig_3.2.0b6-21.debian.tar.xz 9f47bd0f2ee1407ef441a9212379483d4bf76993 6319 htdig_3.2.0b6-21_source.buildinfo Checksums-Sha256: 207152b4f3b3300d1cc660ba573f5829c55ca42c599e31ad14d54c8febe1a9c2 1904 htdig_3.2.0b6-21.dsc 002937c6a10ad5cb788ffb27ce07180b47059560e71dfdeae157b4b437416026 65400 htdig_3.2.0b6-21.debian.tar.xz 265796b2c1208e745e39231732661d8e5d266e17826d6796564c2cd4da7c299b 6319 htdig_3.2.0b6-21_source.buildinfo Files: 9e36471c4bce7563e2befd76e2ae7d2a 1904 web optional htdig_3.2.0b6-21.dsc 408c3a1540fca8363991c2cd134c3ed5 65400 web optional htdig_3.2.0b6-21.debian.tar.xz 0e290ec9327a48fa872e37c63862125f 6319 web optional htdig_3.2.0b6-21_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAmbRwBIACgkQAnE7z8pU ELJgqg
Bug#1079342: marked as done (FTBFS with newer imagemagick7)
Your message dated Fri, 30 Aug 2024 12:49:03 + with message-id and subject line Bug#1079342: fixed in lebiniou 3.66.0-4 has caused the Debian Bug report #1079342, regarding FTBFS with newer imagemagick7 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.) -- 1079342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lebiniou Tags: ftbfs Control: block 1060103 by -1 Control: tag -1 + sid Dear Maintainer, You package FTBFS with newer imagemagick Could you help the transition Full log could be found here https://salsa.debian.org/debian/imagemagick/-/jobs/6158076 Thanks Rouca signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: lebiniou Source-Version: 3.66.0-4 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of lebiniou, 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 1079...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated lebiniou package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Aug 2024 09:18:25 + Source: lebiniou Architecture: source Version: 3.66.0-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastien Roucariès Closes: 1079342 Changes: lebiniou (3.66.0-4) unstable; urgency=medium . * QA upload * Move to salsa * Port to newer imagemagick (Closes: #1079342) * Add salsa-ci.yml Checksums-Sha1: ea5ebf6a86a0dd424d91c348584720fecf880964 2160 lebiniou_3.66.0-4.dsc c274d8554c6fe6900978af01366e3afc6ae7f61e 7168 lebiniou_3.66.0-4.debian.tar.xz d610e31255d08cfb8d648ab027eeef64736de44b 18117 lebiniou_3.66.0-4_amd64.buildinfo Checksums-Sha256: 9fe3019e05c7d9a78aa8921900a2e6c44d01ca1a2cf97a0505891c7a5398ad6c 2160 lebiniou_3.66.0-4.dsc 54f468c5a1d5c206f0a21c12fb14eb423c8bbbeffbce4479a4fe1d9bfd60fafa 7168 lebiniou_3.66.0-4.debian.tar.xz 69a0a7163a36d1f84663837c5f96c3253e16e45092dbe8e429e0301ca8f32eec 18117 lebiniou_3.66.0-4_amd64.buildinfo Files: fb1eb78becf05c6274189c0beb1b33f3 2160 graphics optional lebiniou_3.66.0-4.dsc cd8dddb7541093beec5b88dc9174545f 7168 graphics optional lebiniou_3.66.0-4.debian.tar.xz 3c905ae5d52011514ab0f05daf19082d 18117 graphics optional lebiniou_3.66.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmbRvj4RHHJvdWNhQGRl Ymlhbi5vcmcACgkQADoaLapBCF/+LhAAqAuddvIQRN2vO5G1e91BANOD/4uKdtUi 1aXMvQlw5fW+yN0poj8HkOeCoYhaApHsMhNFCgcUcx0ZxFe7pbqJWIBwoHMsWjAN S3nXX42obqohr8BYeSFQms5EZJbR9QFWqmjVV3rkc2y9UYOt/lr+aKhEonrUcyCV CdVyfZM8iTnz/lYyGclgcET9+Ce54tszx8ZY7ZsePS3xrP43GSQk0JB4DjpwjOTE 9sjeMjMKQ1GfvgxOvC57xwHohQnbsvWtux7bA2Clfpz0agTvCzOlvOrfPkhne8Q4 xNshp4KrKFLZmnnYrRYD+nr1CJ4H9hA0y7pGOzboLubREJ9H8mTYlfG7PRsoP8h6 +fCmEo013yGmVxFooVeGQwej8GU5jhpuihLnf5Ey9zCrcMXCY0fr3UkAp4q6lpIT Jnt7s4P9PnUrDqPi/pzxrRr1P3yPu+yxCm2hMLrYQcGdHlrxOK+KwmxxA1/ChJez labdND6bSOi5HCTRnTktWB/SpITlFPpxNxDWXQOffZ/BOqt+rvVeOADx118dvfX5 KzMzDZU1HI+DKvuEpI+iU87a4KgMU+kgKDR5JiB31ujAMiFYl0HjaJy3yGQMoPne ME2jcH2Dto2rpG5YObXSVzl+jQzJojaCWbx4rP+lxVxG9UaqQcRnpj4fzlFZQwS9 jfyN5pSMgM8= =lufU -END PGP SIGNATURE- pgpeY1D7nAqGu.pgp Description: PGP signature --- End Message ---
Processed: metadata
Processing commands for cont...@bugs.debian.org: > tags 1053015 + trixie sid Bug #1053015 [src:cava] cava: FTBFS with OpenJDK 21 due to new compiler warnings Added tag(s) sid and trixie. > tags 1078338 + trixie sid Bug #1078338 [src:cuneiform] cuneiform: FTBFS with GCC 14: error: type defaults to 'int' in declaration of 'broken_ii' Added tag(s) sid and trixie. > severity 1074912 serious Bug #1074912 [src:dircproxy] dircproxy: ftbfs with GCC-14 Severity set to 'serious' from 'important' > tags 1053068 + trixie sid Bug #1053068 [src:openhft-affinity] openhft-affinity: FTBFS with default Java 21 Added tag(s) trixie and sid. > found 1078241 1.2.2-2 Bug #1078241 [src:reiser4progs] reiser4progs: FTBFS with GCC 14: error: initialization of ... from incompatible pointer type ... Marked as found in versions reiser4progs/1.2.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053015 1053068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053068 1074912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074912 1078241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078241 1078338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992372: marked as done (kst: Dirfile data sources (via libgetdata) are no longer recognized)
Your message dated Thu, 29 Aug 2024 09:00:56 -0700 with message-id and subject line Fwd: Bug#992372: Info received (kst: Dirfile data sources (via libgetdata) are no longer recognized) has caused the Debian Bug report #992372, regarding kst: Dirfile data sources (via libgetdata) are no longer recognized 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.) -- 992372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kst Version: 2.0.8-4+b1 Severity: important Dear Maintainer, KST used to recognize dirfile data sources via libgetdata. However, sometime since I last used it (perhaps several years) it stopped. Dirfile is no longer recognized in the data wizard. In previous installations, I think this happened when libgetdata was not installed. However, I've installed everything libgetdata-ish I can find and do not see any change in behaviour. I've just cross-checked against Ubuntu 20.04 and dirfiles are still recognized there under the same conditions. best, Graeme -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kst depends on: ii libc62.31-11 ii libcfitsio9 3.490-3 ii libgcc-s110.2.1-6 ii libgetdata++70.10.0-10 ii libgsl25 2.6+dfsg-2 ii libmatio11 1.5.19-2 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5network5 5.15.2+dfsg-2 ii libqt5printsupport5 5.15.2+dfsg-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libqt5xml5 5.15.2+dfsg-5 ii libstdc++6 10.2.1-6 Versions of packages kst recommends: ii kst-doc 2.0.8-4 kst suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Underlying getdata bug (992437) is now resolved. Forwarded Message Subject: Bug#992372: Info received (kst: Dirfile data sources (via libgetdata) are no longer recognized) Date: Wed, 18 Aug 2021 16:57:03 +0000 From: Debian Bug Tracking System Reply-To: 992...@bugs.debian.org To: Graeme Smecher Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian QA Group If you wish to submit further information on this problem, please send it to 992...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 992372:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992372 Debian Bug Tracking System contactow...@bugs.debian.org with problems --- End Message ---
Processed: Re: Bug#1077410: sitecopy: FTBFS: src/ftp.c:645:47: error: passing argument 3 of ‘getsockname’ from incompatible pointer type [-Wincompatible-pointer-types]
Processing control commands: > tag -1 patch Bug #1077410 [src:sitecopy] sitecopy: FTBFS: src/ftp.c:645:47: error: passing argument 3 of ‘getsockname’ from incompatible pointer type [-Wincompatible-pointer-types] Added tag(s) patch. -- 1077410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #876872 [keepassx] icons missing in toolbar Added tag(s) wontfix. -- 876872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #955588 [keepassx] keepassx: description says "install keepassx instead" Added tag(s) wontfix. -- 955588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #866715 [keepassx] keepassx: KeepassX 2.x shouldn't automatically replace older versions Added tag(s) wontfix. -- 866715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #866769 [keepassx] keepassx fails to clear KDE clipboard history, leaving passwords visible Added tag(s) wontfix. -- 866769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #863422 [keepassx] keepassx: Cant change keyboard layout after i accidently try to autotype greek Added tag(s) wontfix. -- 863422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #850178 [keepassx] not work AutoInput Added tag(s) wontfix. -- 850178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #835602 [keepassx] keepassx: Auto-Type does not complete Added tag(s) wontfix. -- 835602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #830851 [keepassx] Keyboard shortcuts do not move with letters when changing keyboard layout Added tag(s) wontfix. -- 830851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #815806 [keepassx] keepassx: How do you set a default browser in 2.*? Added tag(s) wontfix. -- 815806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #812067 [keepassx] keepassx: Show timer for copy buffer erasure Added tag(s) wontfix. -- 812067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #812110 [keepassx] KeePassX 0.4 and KeePassX 2.0 should be in different packages Added tag(s) wontfix. -- 812110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #812065 [keepassx] keepassx: Support for FIDO U2F Security Key devices Added tag(s) wontfix. -- 812065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #799947 [keepassx] [keepassx] 'No systemtrayicon available' error when launched with desktop environment Added tag(s) wontfix. -- 799947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #700014 [keepassx] keepassx: If file changed file is not locked on timeout Added tag(s) wontfix. -- 700014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #729578 [keepassx] keepassx: Store location of key file in bookmark Added tag(s) wontfix. -- 729578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #658312 [keepassx] keepassx: lock file was not deleted Added tag(s) wontfix. -- 658312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #567661 [keepassx] keepassx fails on non alphanumeric characters in passwords Added tag(s) wontfix. -- 567661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: keepassx: The package is replaced by keepassxc
Processing control commands: > tags -1 wontfix Bug #1002304 [keepassx] keepassx: 1) Keepassx fails to preserve interface size when closing. Added tag(s) wontfix. -- 1002304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074935: marked as done (elk: ftbfs with GCC-14)
Your message dated Thu, 29 Aug 2024 09:19:08 +
with message-id
and subject line Bug#1074935: fixed in elk 3.99.8-8
has caused the Debian Bug report #1074935,
regarding elk: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1074935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:elk
Version: 3.99.8-7
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/elk_3.99.8-7_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ^~~
io.c:180:5: note: in expansion of macro ‘Alloca_Begin’
180 | Alloca_Begin;
| ^~~~
io.c: At top level:
io.c:220:6: warning: no previous prototype for ‘Close_All_Files’
[-Wmissing-prototypes]
220 | void Close_All_Files () {
| ^~~
io.c:230:8: warning: no previous prototype for ‘Open_File’
[-Wmissing-prototypes]
230 | Object Open_File (char *name, int flags, int err) {
|^
io.c: In function ‘Open_File’:
../include/stkmem.h:57:26: warning: variable ‘_Check_Alloca_Begin’ set but not
used [-Wunused-but-set-variable]
57 | #define Alloca_Begin int _Check_Alloca_Begin
| ^~~
io.c:235:5: note: in expansion of macro ‘Alloca_Begin’
235 | Alloca_Begin;
| ^~~~
io.c: In function ‘General_Open_File’:
../include/stkmem.h:57:26: warning: variable ‘_Check_Alloca_Begin’ set but not
used [-Wunused-but-set-variable]
57 | #define Alloca_Begin int _Check_Alloca_Begin
| ^~~
io.c:270:5: note: in expansion of macro ‘Alloca_Begin’
270 | Alloca_Begin;
| ^~~~
io.c: At top level:
io.c:331:8: warning: no previous prototype for ‘General_Close_Port’
[-Wmissing-prototypes]
331 | Object General_Close_Port (Object port) {
|^~
io.c:379:8: warning: no previous prototype for ‘General_Call_With’
[-Wmissing-prototypes]
379 | Object General_Call_With (Object name, int flags, Object proc) {
|^
make[4]: *** [Makefile:752: libelk_la-heap.lo] Error 1
make[4]: *** Waiting for unfinished jobs
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include
-Wdate-time -D_FORTIFY_SOURCE=2 -DSCM_DIR=\"/usr/share/elk\"
-DLIB_DIR=\"/usr/lib/x86_64-linux-gnu/elk\" -I/usr/include/libelf
-Wpointer-arith -Wcast-align -Wcast-qual -Wshadow -Wmissing-prototypes
-Wnested-externs -Wsign-compare -Wall -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -c libelk.c -fPIC -DPIC -o
.libs/libelk_la-libelk.o
libelk.c:155:6: warning: no previous prototype for ‘Check_If_Dump_Works’
[-Wmissing-prototypes]
155 | void Check_If_Dump_Works () {
| ^~~
libelk.c:362:6: warning: no previous prototype for ‘Usage’
[-Wmissing-prototypes]
362 | void Usage () {
| ^
libelk.c:371:6: warning: no previous prototype for ‘Init_Everything’
[-Wmissing-prototypes]
371 | void Init_Everything () {
| ^~~
libelk.c:396:6: warning: no previous prototype for ‘Get_Stack_Limit’
[-Wmissing-prototypes]
396 | void Get_Stack_Limit () {
| ^~~
libelk.c:412:5: warning: no previous prototype fo
Processed: Re: Bug#978012: xsddiagram: No diagram is shown
Processing control commands: > severity -1 grave Bug #978012 [xsddiagram] xsddiagram: No diagram is shown Severity set to 'grave' from 'important' -- 978012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075074: marked as done (hunt: ftbfs with GCC-14)
Your message dated Wed, 28 Aug 2024 05:49:04 +
with message-id
and subject line Bug#1075074: fixed in hunt 1.5-10
has caused the Debian Bug report #1075074,
regarding hunt: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not 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.)
--
1075074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hunt
Version: 1.5-9
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/hunt_1.5-9_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ~
32 | __va_arg_pack ());
| ~
cc -Wl,-z,relro -Wl,-z,now -o hunt hunt.o main.o c/list.o c/hash.o c/array.o
util.o net.o rst.o menu.o hijack.o rstd.o sniff.o macdisc.o tap.o arphijack.o
tty.o synchijack.o arpspoof.o hostup.o addpolicy.o options.o resolv.o timer.o
pktrelay.o -lpthread
make[2]: Leaving directory '/<>'
dh_auto_build --sourcedirectory=tpserv
cd tpserv && make -j8 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>/tpserv'
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-O2 -g -ffile-prefix-map=/<>/tpserv=. -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o tpserv.o tpserv.c
tpserv.c:58:13: warning: conflicting types for built-in function ‘log’;
expected ‘double(double)’ [-Wbuiltin-declaration-mismatch]
58 | static void log(int level, int pid, char *format, ...)
| ^~~
tpserv.c:23:1: note: ‘log’ is declared in header ‘’
22 | #include
+++ |+#include
23 |
tpserv.c: In function ‘process_request_connect’:
tpserv.c:161:32: error: passing argument 2 of ‘connect’ from incompatible
pointer type [-Wincompatible-pointer-types]
161 | if (connect(fd_remote, to_addr, to_addr_len) < 0) {
|^~~
||
|struct sockaddr_in *
In file included from tpserv.c:11:
/usr/include/x86_64-linux-gnu/sys/socket.h:126:52: note: expected ‘const struct
sockaddr *’ but argument is of type ‘struct sockaddr_in *’
126 | extern int connect (int __fd, __CONST_SOCKADDR_ARG __addr, socklen_t
__len);
|^
tpserv.c:166:69: warning: pointer targets in passing argument 3 of
‘getsockname’ differ in signedness [-Wpointer-sign]
166 | if (getsockname(fd_remote, (struct sockaddr *) &local_addr,
&local_addr_len) < 0) {
|
^~~
| |
| int
*
/usr/include/x86_64-linux-gnu/sys/socket.h:117:47: note: expected ‘socklen_t *
restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
117 | socklen_t *__restrict __len) __THROW;
| ~~^
tpserv.c: In function ‘serv_slave’:
tpserv.c:216:59: warning: pointer targets in passing argument 3 of
‘getsockname’ differ in signedness [-Wpointer-sign]
216 |
Processed: Re: sntop: sntop missing newline in version output
Processing control commands: > tags -1 + patch Bug #139010 [sntop] sntop: sntop missing newline in version output Added tag(s) patch. -- 139010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075171: marked as done (libgpod: ftbfs with GCC-14)
Your message dated Tue, 27 Aug 2024 19:20:36 + with message-id and subject line Bug#1075171: fixed in libgpod 0.8.3-22 has caused the Debian Bug report #1075171, regarding libgpod: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not 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.) -- 1075171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libgpod Version: 0.8.3-19.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/libgpod_0.8.3-19.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] | ^~~~ /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/libxml2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/libmount -I/usr/include/blkid -pthread -DLIBGPOD_BLOB_DIR=\"/usr/lib/x86_64-linux-gnu/libgpod\" -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 -c -o libgpod_la-itdb_track.lo `test -f 'itdb_track.c' || echo '../../../src/'`itdb_track.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/libxml2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/libmount -I/usr/include/blkid -pthread -DLIBGPOD_BLOB_DIR=\"/usr/lib/x86_64-linux-gnu/libgpod\" -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 -c -o libgpod_la-itdb_tzinfo.lo `test -f 'itdb_tzinfo.c' || echo '../../../src/'`itdb_tzinfo.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/libxml2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/libmount -I/usr/include/blkid -pthread -DLIBGPOD_BLOB_DIR=\"/usr/lib/x86_64-linux-gnu/libgpod\" -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 -c ../../../src/itdb_track.c -fPIC -DPIC -o .libs/libgpod_la-itdb_track.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -pthread -I/usr/include/libxml2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/
Bug#965577: marked as done (haskell98-tutorial: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sun, 25 Aug 2024 22:57:13 + with message-id and subject line Bug#1079656: Removed package(s) from unstable has caused the Debian Bug report #965577, regarding haskell98-tutorial: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell98-tutorial Version: 26-2-3 Severity: normal Usertags: compat-5-6-removal Hi, The package haskell98-tutorial uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 26-2-3+rm Dear submitter, as the package haskell98-tutorial has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079656 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#990147: marked as done (ifscheme: legacy conffiles leftover)
Your message dated Sun, 25 Aug 2024 22:56:14 + with message-id and subject line Bug#1079645: Removed package(s) from unstable has caused the Debian Bug report #990147, regarding ifscheme: legacy conffiles leftover 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.) -- 990147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifscheme Version: 1.7-6 Severity: normal Hi. Apparently the package used to contain the conffiles: /etc/bash_completion.d/ifscheme but no longer does so. Please properly clean them up using dpkg-maintscript-helper(1). (AFAIU, the version that needs to be specified for that is NOT the version where the conffile was dropped, but rather "the latest version of the package whose upgrade should trigger the operation" Quoting the manpage: For example, for a conffile removed in version 2.0-1 of a package, prior-version should be set to 2.0-1~. This will cause the conffile to be removed even if the user rebuilt the previous version 1.0-1 as 1.0-1local1. Or a package switching a path from a symlink (shipped in version 1.0-1) to a directory (shipped in version 2.0-1), but only performing the actual switch in the maintainer scripts in version 3.0-1, should set prior-version to 3.0-1~. Cheers, Chris. --- End Message --- --- Begin Message --- Version: 1.7-9+rm Dear submitter, as the package ifscheme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079645 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#981637: marked as done (ifscheme: ifup no longer recognises interface names with ifscheme suffixes)
Your message dated Sun, 25 Aug 2024 22:56:14 + with message-id and subject line Bug#1079645: Removed package(s) from unstable has caused the Debian Bug report #981637, regarding ifscheme: ifup no longer recognises interface names with ifscheme suffixes 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.) -- 981637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifscheme Version: 1.7-6 Severity: important X-Debbugs-Cc: richardle...@fastmail.co.uk I've used ifscheme happily for a long time and on numerous computers. Just recently I installed "unstable" from scratch on a Dell XPS 13 9343. And now ifscheme doesn't work anymore. This if the configuration I have in /etc/network/interfaces: mapping wlp2s0 script ifscheme-mapping iface wlp2s0-home inet dhcp wpa-ssid MyWiFi wpa-psk MyPSK dns-nameservers 208.67.222.222 208.67.220.220 iface wlp2s0-mobile inet dhcp wpa-ssid PhoneWiFi wpa-psk PhonePSK I can verify that ifscheme is parsing my config correctly: $ sudo ifscheme --list home mobile But when I try to select a network and bring up the interface, I get the error "unknown interface": $ sudo ifscheme home Scheme changed to home. $ sudo ifup -v wlp2s0 ifup: running mapping script ifscheme-mapping on wlp2s0 ifup: ignoring unknown interface wlp2s0=wlp2s0 I know this isn't the correct way to use it, but just in case I also tried bringing up the interface with the ifscheme suffix: $ sudo ifup -v wlp2s0-home ifup: configuring interface wlp2s0-home=wlp2s0-home (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant wpa_supplicant: wpa-driver nl80211,wext (default) wpa_supplicant: /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlp2s0-home.pid -i wlp2s0-home -D nl80211,wext -C /run/wpa_supplicant Starting /sbin/wpa_supplicant... wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlp2s0-home I guess this would happen even if I didn't have the ifscheme mapping configured; it's effectively assuming that an interface called literally wlp2s0-home exists. I'm wondering if this might have something to do with the new(-ish) "predictable" network interface names. The reason I considered this is because my old laptop had a WiFi interface called wlan0 under the old scheme (as well as eth0). That machine was also Debian "unstable" but was originally installed c.2013 and just continuously upgraded. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifscheme depends on: ii ifupdown 0.8.36 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ifscheme recommends no packages. ifscheme suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.7-9+rm Dear submitter, as the package ifscheme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079645 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#711002: marked as done (ifscheme doesn't consider /etc/network/interfaces.d/)
Your message dated Sun, 25 Aug 2024 22:56:14 + with message-id and subject line Bug#1079645: Removed package(s) from unstable has caused the Debian Bug report #711002, regarding ifscheme doesn't consider /etc/network/interfaces.d/ 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.) -- 711002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifscheme Version: 1.7-3 Severity: normal Hi. It seems that ifschme doesn't consider the configuration in /etc/network/interfaces.d/ Cheers, Chris. --- End Message --- --- Begin Message --- Version: 1.7-9+rm Dear submitter, as the package ifscheme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079645 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#848614: marked as done (ifscheme interface ignored at boot due to tmpfs)
Your message dated Sun, 25 Aug 2024 22:56:14 + with message-id and subject line Bug#1079645: Removed package(s) from unstable has caused the Debian Bug report #848614, regarding ifscheme interface ignored at boot due to tmpfs 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.) -- 848614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifscheme Version: 1.7-3 Severity: important I'm not filing this under 700335 since I wasn't getting the error about the state file, but it could be the same thing. Basically I get "ignoring unknown interface wlan0=wlan0" At boot it seems that ifscheme-mapping can't read /etc/network/run/scheme. The machine is a recent Jessie install, and it seems that /run is a tmpfs (which I assume is the default, since I didn't set it up specially). In order to get my network up I need to "ifup -a" after boot. My longer term fix is to change SCHEME=/etc/network/run/scheme to SCHEME=/var/lib/scheme I've not moved the state since I assume that is fine on a tmpfs *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifscheme depends on: ii ifupdown 0.7.53.1 ifscheme recommends no packages. ifscheme suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.7-9+rm Dear submitter, as the package ifscheme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079645 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#700335: marked as done (ifscheme: NIC stays unconfigured after booting)
Your message dated Sun, 25 Aug 2024 22:56:14 + with message-id and subject line Bug#1079645: Removed package(s) from unstable has caused the Debian Bug report #700335, regarding ifscheme: NIC stays unconfigured after booting 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.) -- 700335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifscheme Version: 1.7-3 Severity: important Hi Guus, when I boot my notebook the following error will be displayed: Can't read ifupdown state file (/etc/network/ifstate or /etc/network/run/ifstate). Scheme unchanged. Thus the NIC stays unconfigured. I have to set the scheme manually (`ifscheme -s $SCHEME`) and bring up the interface (`ifup $IFACE`). If I remember correctly, this is related to the ifupdown update many months ago. Regards, Pascal -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 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 ifscheme depends on: ii ifupdown 0.7.5 ifscheme recommends no packages. ifscheme suggests no packages. -- Configuration Files: /etc/default/ifscheme changed: BOOT_SCHEME=$SCHEME -- no debconf information --- End Message --- --- Begin Message --- Version: 1.7-9+rm Dear submitter, as the package ifscheme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079645 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#946039: marked as done (picport: Will crash with Linux 5.5 due to cli)
Your message dated Sun, 25 Aug 2024 22:34:28 + with message-id and subject line Bug#1079308: Removed package(s) from unstable has caused the Debian Bug report #946039, regarding picport: Will crash with Linux 5.5 due to cli 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.) -- 946039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: picport Version: 1.9.1-4 Severity: serious Justification: always crash on x86 Hello, Admittedly this is early since 5.5 is not released yet, but better submit this while I'm thinking about it: as described in https://lwn.net/Articles/804143/ , starting from version 5.5, Linux will make iopl(3) only enable I/O port access, and not allow userland application to use the cli asm instruction any more. picport.cc uses it, and will thus just always crash. Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 1.9.1-5+rm Dear submitter, as the package picprog has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079308 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#675280: marked as done (picprog: FTBFS on Debian GNU/Hurd [Patch attached])
Your message dated Sun, 25 Aug 2024 22:34:28 + with message-id and subject line Bug#1079308: Removed package(s) from unstable has caused the Debian Bug report #675280, regarding picprog: FTBFS on Debian GNU/Hurd [Patch 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.) -- 675280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: picprog Version: 1.9.1-2 Severity: normal User: bdefre...@debian.org Usertags: hurd Tags: patch Hi, Currently picprog fails to build on Debian GNU/Hurd. Hurd does not support iopl even though we have a stub in io.h. The following patch works though I am not sure it is the "best" solution. You obviously must also add hurd-any to debian/control. Thank you, Barry deFreese Index: picprog-1.9.1/picport.cc === --- picprog-1.9.1.orig/picport.cc 2012-05-30 15:04:37.0 + +++ picprog-1.9.1/picport.cc2012-05-30 15:06:03.0 + @@ -39,9 +39,11 @@ #include -#if defined(__i386__) || defined(__x86_64__) - #include - #define HAVE_IOPL +#ifndef __GNU__ + #if defined(__i386__) || defined(__x86_64__) +#include +#define HAVE_IOPL + #endif #endif #include --- End Message --- --- Begin Message --- Version: 1.9.1-5+rm Dear submitter, as the package picprog has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079308 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: closing 1075458
Processing commands for cont...@bugs.debian.org:
> close 1075458
Bug #1075458 [src:ruby-curses] ruby-curses: ftbfs with GCC-14
Marked Bug as done
> fixed 1075458 1.4.6-1
Bug #1075458 {Done: Cédric Boutillier } [src:ruby-curses]
ruby-curses: ftbfs with GCC-14
Marked as fixed in versions ruby-curses/1.4.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1075458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
