Bug#1047757: marked as done (mp3burn: Fails to build source after successful build)
Your message dated Wed, 27 Mar 2024 15:50:44 + with message-id and subject line Bug#1047757: fixed in mp3burn 0.4.2-5 has caused the Debian Bug report #1047757, regarding mp3burn: 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.) -- 1047757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp3burn Version: 0.4.2-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package mp3burn > dpkg-buildpackage: info: source version 0.4.2-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Jelmer Vernooij > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean >dh_auto_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building mp3burn using existing ./mp3burn_0.4.2.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > mp3burn-0.4.2/mp3burn.1 > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/mp3burn_0.4.2-4.diff.t_QI5R > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/mp3burn_0.4.2-4_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: mp3burn Source-Version: 0.4.2-5 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of mp3burn, 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 1047...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated mp3burn 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, 27 Mar 2024 16:30:11 +0100 Source: mp3burn Architecture: source Version: 0.4.2-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Metzler Closes: 1047757 Changes: mp3burn (0.4.2-5) unstable; urgency=medium . * QA upload. * Depend on mpg123 instead of mpg321 | mpg123. * [lintian] Delete trailing-whitespace in changelog. * [lintian] Fix spelling errors in copyright file. * [lintian] Set Rules-Requires-Root: no. * Delete mp3burn.1 on clean. Closes: #1047757 Checksums-Sha1: 81e3aacd4a5359e85d6892f7cd9e6f198ad67db2 1825
Bug#894117: marked as done (typespeed FTCBFS: does not pass --host to ./configure)
Your message dated Tue, 26 Mar 2024 20:43:58 + with message-id and subject line Bug#894117: fixed in typespeed 0.6.5-5 has caused the Debian Bug report #894117, regarding typespeed FTCBFS: does not pass --host to ./configure 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.) -- 894117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: typespeed Version: 0.6.5-2.1 Tags: patch User: helm...@debian.org Usertags: rebootstrap typespeed fails to cross build from source, because it does not pass the relevant --host flag to ./configure. Using dh_auto_configure fixes that. Still it fails, because the upstream build system fails to propagate the cross compiler from configure to make. After removing the erroneous assignments, it cross builds. Please consider applying the attached patch. Also please consider rebuilding Makefile.in from Makefile.am during build. Helmut diff -u typespeed-0.6.5/debian/changelog typespeed-0.6.5/debian/changelog --- typespeed-0.6.5/debian/changelog +++ typespeed-0.6.5/debian/changelog @@ -1,3 +1,12 @@ +typespeed (0.6.5-2.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Let dh_auto_configure pass --host to ./configure. ++ 0003-cross.patch: Propagate CC from configure to make. + + -- Helmut Grohne Mon, 26 Mar 2018 17:04:24 +0200 + typespeed (0.6.5-2.1) unstable; urgency=medium * Non-maintainer upload. diff -u typespeed-0.6.5/debian/control typespeed-0.6.5/debian/control --- typespeed-0.6.5/debian/control +++ typespeed-0.6.5/debian/control @@ -1,5 +1,5 @@ Source: typespeed -Build-Depends: debhelper (>= 5), quilt (>= 0.46-7), libncurses5-dev, autotools-dev +Build-Depends: debhelper (>= 7), quilt (>= 0.46-7), libncurses5-dev, autotools-dev Section: games Priority: optional Maintainer: Dafydd Harries diff -u typespeed-0.6.5/debian/patches/series typespeed-0.6.5/debian/patches/series --- typespeed-0.6.5/debian/patches/series +++ typespeed-0.6.5/debian/patches/series @@ -1,0 +2 @@ +0003-cross.patch diff -u typespeed-0.6.5/debian/rules typespeed-0.6.5/debian/rules --- typespeed-0.6.5/debian/rules +++ typespeed-0.6.5/debian/rules @@ -16,8 +16,7 @@ config.log: patch dh_autotools-dev_updateconfig - ./configure --prefix=/usr --bindir=/usr/games --localstatedir=/var \ - --sysconfdir=/etc + dh_auto_configure -- --bindir=/usr/games debian/build-stamp: config.log dh_testdir only in patch2: unchanged: --- typespeed-0.6.5.orig/.pc/.quilt_patches +++ typespeed-0.6.5/.pc/.quilt_patches @@ -0,0 +1 @@ +./debian/patches only in patch2: unchanged: --- typespeed-0.6.5.orig/.pc/.quilt_series +++ typespeed-0.6.5/.pc/.quilt_series @@ -0,0 +1 @@ +series only in patch2: unchanged: --- typespeed-0.6.5.orig/.pc/.version +++ typespeed-0.6.5/.pc/.version @@ -0,0 +1 @@ +2 only in patch2: unchanged: --- typespeed-0.6.5.orig/debian/patches/0003-cross.patch +++ typespeed-0.6.5/debian/patches/0003-cross.patch @@ -0,0 +1,44 @@ +Index: typespeed-0.6.5/src/Makefile.am +=== +--- typespeed-0.6.5.orig/src/Makefile.am typespeed-0.6.5/src/Makefile.am +@@ -1,4 +1,3 @@ +-CC = gcc + AM_CFLAGS = -Wall -W -pedantic -std=c99 + + HIGHFILE = typespeed.score +Index: typespeed-0.6.5/src/Makefile.in +=== +--- typespeed-0.6.5.orig/src/Makefile.in typespeed-0.6.5/src/Makefile.in +@@ -85,7 +85,7 @@ + AUTOHEADER = @AUTOHEADER@ + AUTOMAKE = @AUTOMAKE@ + AWK = @AWK@ +-CC = gcc ++CC = @CC@ + CCDEPMODE = @CCDEPMODE@ + CFLAGS = @CFLAGS@ + CPP = @CPP@ +Index: typespeed-0.6.5/testsuite/Makefile.am +=== +--- typespeed-0.6.5.orig/testsuite/Makefile.am typespeed-0.6.5/testsuite/Makefile.am +@@ -1,4 +1,3 @@ +-CC = gcc + AM_CFLAGS = -I../src -Wall -W -pedantic -std=c99 + + localedir = $(datadir)/locale +Index: typespeed-0.6.5/testsuite/Makefile.in +=== +--- typespeed-0.6.5.orig/testsuite/Makefile.in typespeed-0.6.5/testsuite/Makefile.in +@@ -98,7 +98,7 @@ + AUTOHEADER = @AUTOHEADER@ + AUTOMAKE = @AUTOMAKE@ + AWK = @AWK@ +-CC = gcc ++CC = @CC@ + CCDEPMODE = @CCDEPMODE@ + CFLAGS = @CFLAGS@ + CPP = @CPP@ --- End Message --- --- Begin Message --- Source: typespeed Source-Version: 0.6.5-5 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version
Bug#662805: marked as done (typespeed: Homepage seems to have changed)
Your message dated Tue, 26 Mar 2024 20:43:58 + with message-id and subject line Bug#662805: fixed in typespeed 0.6.5-5 has caused the Debian Bug report #662805, regarding typespeed: Homepage seems to have changed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 662805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: typespeed Version: 0.6.5-1.1 Severity: minor Hi, mymachine:~# aptitude show typespeed Package: typespeed Version: 0.6.5-1.1 Homepage: http://tobias.eyedacor.org/typespeed/ It seems this homepage is not available anymore. http://freecode.com/projects/typespeed lists http://typespeed.sourceforge.net/ as the project site. Memnon -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages typespeed depends on: ii coreutils8.13-3 ii libc62.13-26 ii libncurses5 5.9-4 typespeed recommends no packages. typespeed suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: typespeed Source-Version: 0.6.5-5 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of typespeed, 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 662...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated typespeed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Mar 2024 20:16:06 + Source: typespeed Architecture: source Version: 0.6.5-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 662805 894117 1046694 Changes: typespeed (0.6.5-5) unstable; urgency=medium . * QA upload * Drop unnecessary B-D quilt * Correct Homepage (Closes: #662805) * Pass --host to configure (Closes: #894117) * Clean typespeedrc (Closes: #1046694) * Drop unnecessary Depends . [ Helmut Grohne ] * Propagate CC from configure to make Checksums-Sha1: 7d478c1f195fb2558a59ba9f5b06179f13b355b6 1706 typespeed_0.6.5-5.dsc 3f20975b67d0e36a864ccb86a6009b40ca083026 8792 typespeed_0.6.5-5.debian.tar.xz 51273e2e26c18c5db549de7708f2f257b62398f7 6179 typespeed_0.6.5-5_source.buildinfo Checksums-Sha256: 2df9563fb3d7455de032415928c76302e17e2f94ebf9dfd52ab19ce0320fbaa7 1706 typespeed_0.6.5-5.dsc 7291fb70ff89e75a0f1b2a377385220d7d6b1f2262e7706e5c0c6b864a5a9f95 8792 typespeed_0.6.5-5.debian.tar.xz 75ef5f2d226062bbf875cc8b96b446ec61931d264b0073999e73c16de5137abf 6179 typespeed_0.6.5-5_source.buildinfo Files: cf150f1eb2e188eab6cd3bac87f3830f 1706 games optional typespeed_0.6.5-5.dsc 3c7aab8222481ec80a98c6aa24df38f1 8792 games optional typespeed_0.6.5-5.debian.tar.xz 8afca966a6ee539cf143ef2154fc2c65 6179 games optional typespeed_0.6.5-5_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYDLaMQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFMk1DADm2yhcDBX9iNhiobZfNdDbp1gNJX/6JdS8 S6pEXGrOt7SY2xQkaOzdaqshDV6x9pI8Dxj+BsDPnUcGDxE8nO1ZZyIfnyrlTnql a9eKdVIfXADDXC1dIu5eETyYVb1jYLdEqTWwWOzswLAVFOZ4LcjZi4klP4F9NkgE 82zMBoluj2VpJP3c27YLoPBSJTqYGubGMH+BHH8nO83JLp6y/DWCSyoNlCQigPKd Hr98TqqijGIFvFkJS9gzgoA+jdapWiAbqjuyJWD/2Mc+gN9jtGm3skx9mL5A2oFy HhsD+7htVc1AKid8a1609VJ8i0yEaVFlZvTMwPmFYnCXspCi3PAfy1MYtkoVIyZx vhDn67RLH3kmMje9r3hBkjLehk+UZRAOxOtNgEHCb3N8+NJ/szVWLtZ7jZYnxba/ l+gEtQk7TWkXkj4BelsAKJ3giSa3gIRT4SOENzefgAOn+BQjjRlv9QloepHLZFqr UDjDTMqq/ppBSgHp6GW2J1Tyt1+DL2s= =eQ/l -END PGP SIGNATURE- pgpeoKlchsCKQ.pgp Description: PGP signature --- End Message ---
Bug#1046694: marked as done (typespeed: Fails to build source after successful build)
Your message dated Tue, 26 Mar 2024 20:43:59 + with message-id and subject line Bug#1046694: fixed in typespeed 0.6.5-5 has caused the Debian Bug report #1046694, regarding typespeed: 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.) -- 1046694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: typespeed Version: 0.6.5-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package typespeed > dpkg-buildpackage: info: source version 0.6.5-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Jelmer Vernooij > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean --without autoreconf >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > Making distclean in words > make[2]: Entering directory '/<>/words' > test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/words' > Making distclean in testsuite > make[2]: Entering directory '/<>/testsuite' > test -z "t_level t_loadwords t_typorankkaus t_unescstr" || rm -f t_level > t_loadwords t_typorankkaus t_unescstr > rm -f *.o > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > rm -rf ./.deps > rm -f Makefile > make[2]: Leaving directory '/<>/testsuite' > Making distclean in src > make[2]: Entering directory '/<>/src' > test -z "typespeed" || rm -f typespeed > test -z "convert" || rm -f convert > rm -f *.o > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > rm -rf ./.deps > rm -f Makefile > make[2]: Leaving directory '/<>/src' > Making distclean in rules > make[2]: Entering directory '/<>/rules' > test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/rules' > Making distclean in po > make[2]: Entering directory '/<>/po' > rm -f *.insert-header > rm -f remove-potcdate.sed > rm -f stamp-poT > rm -f core core.* typespeed.po typespeed.1po typespeed.2po *.new.po > rm -fr *.o > rm -f Makefile Makefile.in POTFILES *.mo > make[2]: Leaving directory '/<>/po' > Making distclean in man > make[2]: Entering directory '/<>/man' > test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/man' > Making distclean in etc > make[2]: Entering directory '/<>/etc' > test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/etc' > Making distclean in doc > make[2]: Entering directory '/<>/doc' > test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/doc' > Making distclean in . > make[2]: Entering directory '/<>' > test -z "" || rm -f > rm -f config.h stamp-h1 > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > make[2]: Leaving directory '/<>' > rm -f config.status config.cache config.log configure.lineno > config.status.lineno > rm -f Makefile > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building typespeed using existing > ./typespeed_0.6.5.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/se
Bug#1066619: marked as done (libstroke: FTBFS: stroke.c:267:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration])
Your message dated Tue, 26 Mar 2024 13:37:42 + with message-id and subject line Bug#1066619: fixed in libstroke 0.5.1-10 has caused the Debian Bug report #1066619, regarding libstroke: FTBFS: stroke.c:267:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstroke Version: 0.5.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libstroke -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 > stroke.c -fPIC -DPIC -o .libs/stroke.o > stroke.c: In function 'stroke_trans': > stroke.c:267:5: error: implicit declaration of function 'strcpy' > [-Werror=implicit-function-declaration] > 267 | strcpy (sequence,"0"); > | ^~ > stroke.c:15:1: note: include '' or provide a declaration of 'strcpy' >14 | #include > +++ |+#include >15 | > stroke.c:267:5: warning: incompatible implicit declaration of built-in > function 'strcpy' [-Wbuiltin-declaration-mismatch] > 267 | strcpy (sequence,"0"); > | ^~ > stroke.c:267:5: note: include '' or provide a declaration of > 'strcpy' > cc1: some warnings being treated as errors > make[3]: *** [Makefile:300: stroke.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libstroke_0.5.1-9_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libstroke Source-Version: 0.5.1-10 Done: Bdale Garbee We believe that the bug you reported is fixed in the latest version of libstroke, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bdale Garbee (supplier of updated libstroke package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Mar 2024 21:48:52 +0900 Source: libstroke Architecture: source Version: 0.5.1-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bdale Garbee Closes: 1066619 Changes: libstroke (0.5.1-10) unstable; urgency=medium . * add string.h include to resolve implicit declaration, closes: #1066619 Checksums-Sha1: f945a8fac59095a0c8209c5eed6862eefd055b58 1897 libstroke_0.5.1-10.dsc 85fb74d902cc380501970199f5b7fa66ee6ed64e 179528 libstroke_0.5.1-10.debian.tar.xz d84e67485c86e3e2f7ff747be546c5929f740da6 6359 libstroke_0.5.1-10_source.buildinfo Checksums-Sha256: 022de435f5ef014a92b45a37650ff6d3c93ea6446b1c7c2cfe9ab4c7a6afbf12 1897 libstroke_0.5.1-10.dsc 27b30815ae21166c70195af5a122c770633de6979a56524f4c388e8a6931e992 179528 libstroke_0.5.1-10.debian.ta
Bug#1066518: marked as done (fgetty: FTBFS: fgetty.c:278:12: error: implicit declaration of function ‘isdigit’ [-Werror=implicit-function-declaration])
Your message dated Tue, 26 Mar 2024 01:42:01 + with message-id and subject line Bug#1066518: fixed in fgetty 0.7-9 has caused the Debian Bug report #1066518, regarding fgetty: FTBFS: fgetty.c:278:12: error: implicit declaration of function ‘isdigit’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fgetty Version: 0.7-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -Os -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 checkpassword.c -lcrypt -Wl,-z,relro > -Wl,-z,now -o checkpassword > fgetty.c: In function ‘main’: > fgetty.c:278:12: error: implicit declaration of function ‘isdigit’ > [-Werror=implicit-function-declaration] > 278 | else if (isdigit(tty[0])) { > |^~~ > fgetty.c:16:1: note: include ‘’ or provide a declaration of ‘isdigit’ >15 | #include "fmt.h" > +++ |+#include >16 | > login.c:61:1: warning: return type defaults to ‘int’ [-Wimplicit-int] >61 | main(int argc,char *argv[]) { > | ^~~~ > login2.c:60:1: warning: return type defaults to ‘int’ [-Wimplicit-int] >60 | main(int argc,char *argv[]) { > | ^~~~ > checkpassword.c: In function ‘__write2’: > checkpassword.c:16:3: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] >16 | write(2,message,strlen(message)); > | ^~~~ > diet -Os cc -Wl,-z,relro -Wl,-z,now -o login login.o > cc1: some warnings being treated as errors > make[1]: *** [Makefile:13: fgetty.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/fgetty_0.7-8_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: fgetty Source-Version: 0.7-9 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of fgetty, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated fgetty package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Mar 2024 00:32:16 + Source: fgetty Architecture: source Version: 0.7-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 1066518 Changes: fgetty (0.7-9) unstable; urgency=medium . * QA upload. * Address compiler warnings. (Closes: #1066518) Checksums-Sha1: e729a50798021b4e722331f4d192ca9770434862 1910 fgetty_0.7-9.dsc 18c32f871d914630dc22130d507213d3ed618df8 9648 fgetty_0.7-9.debian.
Bug#928860: marked as done (libjconv FTCBFS: does not pass cross tools to make)
Your message dated Mon, 25 Mar 2024 18:29:58 + with message-id and subject line Bug#1066994: Removed package(s) from unstable has caused the Debian Bug report #928860, regarding libjconv FTCBFS: does not pass cross tools to make 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.) -- 928860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjconv Version: 2.8-7 Tags: patch User: helm...@debian.org Usertags: rebootstrap libjconv fails to cross build from source, because it does not pass cross tools to make. The easiest way of doing so - using dh_auto_build - makes libjconv cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru libjconv-2.8/debian/changelog libjconv-2.8/debian/changelog --- libjconv-2.8/debian/changelog 2016-07-11 03:00:39.0 +0200 +++ libjconv-2.8/debian/changelog 2019-05-12 09:47:41.0 +0200 @@ -1,3 +1,9 @@ +libjconv (2.8-8) UNRELEASED; urgency=medium + + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1) + + -- Helmut Grohne Sun, 12 May 2019 09:47:41 +0200 + libjconv (2.8-7) unstable; urgency=medium * QA upload. diff --minimal -Nru libjconv-2.8/debian/rules libjconv-2.8/debian/rules --- libjconv-2.8/debian/rules 2016-07-11 02:43:33.0 +0200 +++ libjconv-2.8/debian/rules 2019-05-12 09:47:10.0 +0200 @@ -22,7 +22,7 @@ build-arch: dh_testdir - $(MAKE) MAJOR=$(major) + dh_auto_build -- MAJOR=$(major) build: build-indep build-arch --- End Message --- --- Begin Message --- Version: 2.8-7+rm Dear submitter, as the package libjconv 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/1066994 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. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#370060: marked as done (Segmentation fault if linked with the pthread library)
Your message dated Mon, 25 Mar 2024 18:31:02 + with message-id and subject line Bug#1066993: Removed package(s) from unstable has caused the Debian Bug report #370060, regarding Segmentation fault if linked with the pthread library 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.) -- 370060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=370060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpcl1 Version: 1.6-1 I have a situation on the ARM platform where if I compile an executable to use both libpcl and libpthread, then even if I'm not actually using threads, trying to do anything to a coroutine causes an immediate segmentation fault. To replicate: $ gcc /usr/share/doc/libpc1-dev/examples/cobench.c -lpcl --> produces working executable. $ ldd ./a.out libpcl.so.1 => /usr/lib/libpcl.so.1 (0x4001e000) libc.so.6 => /lib/libc.so.6 (0x40029000) /lib/ld-linux.so.2 (0x4000) gcc /usr/share/doc/libpc1-dev/examples/cobench.c -lpcl -lpthread --> produces failing executable. $ ldd ./a.out libpcl.so.1 => /usr/lib/libpcl.so.1 (0x4001e000) libpthread.so.0 => /lib/libpthread.so.0 (0x40029000) libc.so.6 => /lib/libc.so.6 (0x40083000) /lib/ld-linux.so.2 (0x4000) The reason why this is an issue is that I have an application which uses coroutines, but not pthreads, which wants to link to the sqlite library. When sqlite was built, it was done so with its threading support enabled; which means that it tries to call mutex primitives in the pthreads library. This means that linking an application against libsqlite will implicitly pull in libpthread, which then causes it to fail. This actually sounds suspiciously similar to a problem I previously encountered on the i386, Debian bug 339827. To summarise: on i386 when running a sufficiently old kernel that does not have thread-local storage, the threading library figures out which thread is running by the location of the stack pointer. If the application has allocated a user stack, it fails to cope and crashes. This means that calling any thread-safe function which needs to know what the calling thread is will fail when it is called from any user stack. The only workaround I've got for this is to recompile sqlite without threading support, which is painful. Architecture: Linux pyanfar 2.6.15-1-nslu2 #2 Tue Mar 7 17:36:32 UTC 2006 armv5tel GNU/Linux Debian version: Etch (current) signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.12-2+rm Dear submitter, as the package libpcl1 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/1066993 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. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1066533: marked as done (libpcl1: FTBFS: cobench.c:125:44: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration])
Your message dated Mon, 25 Mar 2024 18:31:02 + with message-id and subject line Bug#1066993: Removed package(s) from unstable has caused the Debian Bug report #1066533, regarding libpcl1: FTBFS: cobench.c:125:44: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpcl1 Version: 1.12-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -I./../include -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o cothread.o cothread.c > cobench.c: In function ‘run_test’: > cobench.c:62:28: warning: format ‘%p’ expects argument of type ‘void *’, but > argument 3 has type ‘pthread_t’ {aka ‘long unsigned int’} [-Wformat=] >62 | fprintf(stdout, "[%p] measuring co_create+co_delete > performance ...\n", > | ~^ > || > |void * > | %ld >63 | pthread_self()); > | ~~ > | | > | pthread_t {aka long unsigned int} > cobench.c:78:28: warning: format ‘%p’ expects argument of type ‘void *’, but > argument 3 has type ‘pthread_t’ {aka ‘long unsigned int’} [-Wformat=] >78 | fprintf(stdout, "[%p] %g usec\n", pthread_self(), > | ~^ ~~ > || | > |void * pthread_t {aka long > unsigned int} > | %ld > cobench.c:83:36: warning: format ‘%p’ expects argument of type ‘void *’, but > argument 3 has type ‘pthread_t’ {aka ‘long unsigned int’} [-Wformat=] >83 | fprintf(stdout, "[%p] measuring switch performance > ...\n", > | ~^ > || > |void * > | %ld >84 | pthread_self()); > | ~~ > | | > | pthread_t {aka long unsigned int} > cobench.c:96:36: warning: format ‘%p’ expects argument of type ‘void *’, but > argument 3 has type ‘pthread_t’ {aka ‘long unsigned int’} [-Wformat=] >96 | fprintf(stdout, "[%p] %g usec\n", pthread_self(), > | ~^ ~~ > || | > |void * pthread_t {aka long > unsigned int} > | %ld > cobench.c: In function ‘main’: > cobench.c:125:44: error: implicit declaration of function ‘atoi’ > [-Werror=implicit-function-declaration] > 125 | nthreads = atoi(argv[i]); > |^~~~ > cobench.c:131:39: error: implicit declaration of function ‘malloc’ > [-Werror=implicit-function-declaration] > 131 | thids = (pthread_t *) malloc(nthreads * > sizeof(pthread_t)); > | ^~ > cobench.c:30:1: note: include ‘’ or provide a declaration of > ‘malloc’ >29 | #include > +++ |+#include >30 | > cobench.c:131:39: warning: incompatible implicit declaration of built-in > function ‘malloc’ [-Wbuiltin-declaration-mismatch] > 131 | thids = (pthread_
Bug#598632: marked as done (libpcl: New version 1.10 available)
Your message dated Mon, 25 Mar 2024 18:31:02 + with message-id and subject line Bug#1066993: Removed package(s) from unstable has caused the Debian Bug report #598632, regarding libpcl: New version 1.10 available 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.) -- 598632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpcl1 Version: 1.6 Severity: wishlist Hi! There's version 1.10 available in upstream, it would be nice to get that packaged. (As a side note, it would make sense to rename the source package to just libpcl instead of libpcl1, this should not requires going through NEW.) thanks, guillem --- End Message --- --- Begin Message --- Version: 1.12-2+rm Dear submitter, as the package libpcl1 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/1066993 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. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1066487: marked as done (libgpiv: FTBFS: ../../lib/img.c:939:16: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration])
Your message dated Mon, 25 Mar 2024 18:31:52 + with message-id and subject line Bug#1066990: Removed package(s) from unstable has caused the Debian Bug report #1066487, regarding libgpiv: FTBFS: ../../lib/img.c:939:16: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgpiv Version: 0.6.1-7.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -fopenmp > -DHAVE_CONFIG_H -I. -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o io_png.lo ../../lib/io_png.c > libtool: compile: x86_64-linux-gnu-gcc -fopenmp -DHAVE_CONFIG_H -I. > -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c ../../lib/imgproc_deform.c -fPIC > -DPIC -o .libs/imgproc_deform.o > libtool: compile: x86_64-linux-gnu-gcc -fopenmp -DHAVE_CONFIG_H -I. > -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c ../../lib/io.c -fPIC -DPIC -o > .libs/io.o > libtool: compile: x86_64-linux-gnu-gcc -fopenmp -DHAVE_CONFIG_H -I. > -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c ../../lib/imgproc_par.c -fPIC > -DPIC -o .libs/imgproc_par.o > libtool: compile: x86_64-linux-gnu-gcc -fopenmp -DHAVE_CONFIG_H -I. > -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c ../../lib/io_png.c -fPIC -DPIC -o > .libs/io_png.o > ../../lib/img.c: In function ‘gpiv_img_read_header’: > ../../lib/img.c:939:16: error: implicit declaration of function ‘gets’; did > you mean ‘fgets’? [-Werror=implicit-function-declaration] > 939 | while (gets (line) != NULL) { > |^~~~ > |fgets > ../../lib/img.c:939:28: warning: comparison between pointer and integer > 939 | while (gets (line) != NULL) { > |^~ > libtool: compile: x86_64-linux-gnu-gcc -fopenmp -DHAVE_CONFIG_H -I. > -I../../lib -I.. -I../../include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/realtime/include > -I/usr/include/hdf5/serial -I/usr/include/hdf5/serial -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-cl
Bug#1066495: marked as done (libjconv: FTBFS: jconv.c:34:21: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])
Your message dated Mon, 25 Mar 2024 18:29:58 + with message-id and subject line Bug#1066994: Removed package(s) from unstable has caused the Debian Bug report #1066495, regarding libjconv: FTBFS: jconv.c:34:21: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjconv Version: 2.8-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fPIC -DHAVE_CODESET -Wdate-time -D_FORTIFY_SOURCE=2 -c -o jconv.o jconv.c > jconv.c: In function ‘main’: > jconv.c:34:21: error: implicit declaration of function ‘strcmp’ > [-Werror=implicit-function-declaration] >34 | if (strcmp(argv[i], "-c") == 0) { > | ^~ > jconv.c:9:1: note: include ‘’ or provide a declaration of ‘strcmp’ > 8 | #include "jconv.h" > +++ |+#include > 9 | > cc1: some warnings being treated as errors > make[1]: *** [: jconv.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libjconv_2.8-7_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 2.8-7+rm Dear submitter, as the package libjconv 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/1066994 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. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Processed: reassign 1032766 to src:libreoffice-dictionaries, fixed 1032766 in 1:7.6.4-1 ..., tagging 1067654 ...
ebian.org/cgi-bin/bugreport.cgi?bug=948238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024927: marked as done (libtextwrap should support the noudeb build profile)
Your message dated Mon, 25 Mar 2024 07:36:09 + with message-id and subject line Bug#1024927: fixed in libtextwrap 0.1-17 has caused the Debian Bug report #1024927, regarding libtextwrap should support the noudeb build profile 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.) -- 1024927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtextwrap Version: 0.1-15 Severity: minor Tags: patch User: helm...@debian.org Usertags: rebootstrap libtextwrap builds a udeb. Therefore, it should support a noudeb build profile. It's a one-line change and I'm attaching a patch for your convenience. Helmut diff --minimal -Nru libtextwrap-0.1/debian/changelog libtextwrap-0.1/debian/changelog --- libtextwrap-0.1/debian/changelog2021-09-14 23:53:23.0 +0200 +++ libtextwrap-0.1/debian/changelog2022-11-27 16:58:09.0 +0100 @@ -1,3 +1,9 @@ +libtextwrap (0.1-16) UNRELEASED; urgency=medium + + * Support the noudeb build profile. (Closes: #-1) + + -- Helmut Grohne Sun, 27 Nov 2022 16:58:09 +0100 + libtextwrap (0.1-15) unstable; urgency=medium * QA upload. diff --minimal -Nru libtextwrap-0.1/debian/control libtextwrap-0.1/debian/control --- libtextwrap-0.1/debian/control 2021-09-14 23:34:20.0 +0200 +++ libtextwrap-0.1/debian/control 2022-11-27 16:58:08.0 +0100 @@ -60,4 +60,5 @@ ${misc:Depends}, ${shlibs:Depends}, Package-Type: udeb +Build-Profiles: Description: text-wrapping library with i18n - runtime udeb --- End Message --- --- Begin Message --- Source: libtextwrap Source-Version: 0.1-17 Done: Helmut Grohne We believe that the bug you reported is fixed in the latest version of libtextwrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helmut Grohne (supplier of updated libtextwrap 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, 25 Mar 2024 08:19:27 +0100 Source: libtextwrap Architecture: source Version: 0.1-17 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Helmut Grohne Closes: 1024927 1066229 Changes: libtextwrap (0.1-17) unstable; urgency=medium . * QA upload. * Fix FTBFS: Add missing #includes. (Closes: #1066229) * Support the noudeb build profile. (Closes: #1024927) Checksums-Sha1: fb01d6acd02313df77081c33e1e566550f959367 2013 libtextwrap_0.1-17.dsc 3f13321ae7eaf1ed1d2ecce329351ccd970eab10 6464 libtextwrap_0.1-17.debian.tar.xz 4613be51cf9ba8aaf25f7e7cdcd9b919adcaa474 6811 libtextwrap_0.1-17_amd64.buildinfo Checksums-Sha256: 9a3d1bbb09eb234ef9b1a112cba3524b25a47a2bdb2774f7ee271a65b34c7bdb 2013 libtextwrap_0.1-17.dsc 6769d8f0a33a9c0d6197335c9a1d597c8a9e8d41aee81e216f70447d8b567b76 6464 libtextwrap_0.1-17.debian.tar.xz f9b4e36e2c3424950d5cb6006ca4bd1d2a9bfde51dd21129926b98624863079c 6811 libtextwrap_0.1-17_amd64.buildinfo Files: 4f57d307b838e585c4924de8a7f0f070 2013 libs important libtextwrap_0.1-17.dsc b5d267f7a4e5aa39255ac6b038d083e9 6464 libs important libtextwrap_0.1-17.debian.tar.xz 6f4a7659f26b1076baad9a96d6949a15 6811 libs important libtextwrap_0.1-17_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmYBJbsACgkQLRqqzyRE RELRNQ//WtnFlL8MpFX1wyvufLa5qTK+78Y1zVGSOTkXV551nVfvk2uN1BCp9Ho/ vC5PSrahycxCNa9/xRg4EkSWSA1np4iTn8pq87mF18HWpcjxrCYA5ssDwxqIjdza 54I+mn1MzmlczrIqoy8AnWlz1upRCyQv7QqWZNoGUGLIHNUiCEb0j/C0KJ/fiEOy lzR/lms/MdbrqFlh+pm98pLY8B+jnWAAQPFu/wcBhIqFpQicjEkgtBtmHxRv6dK5 Jelrr2Bq6gwv/ocUWZqpuZyg+4nmq072tunRZmoNnxFc/m2OzLc2qAkXy7DlX7EL ZiqHz6Cp8CKYZ9WTdzYsc/vZXwTZVa2oo5e9U1I3rHrTCLkgkwTu0DRIJV9K9cLk nfFPZcjLhpu/6KgZMIY8AIXgiKT4YnlivZV1/iA6tJGUJ+G15bVhXXzbZtW0mG+Y SCsyFcbx0p+74JjTCcxZdweLVh8oVKP0cvbDZJT1kTIasY9DaGBBqPkEJorjoeb6 cBL/xcMOjhTFFhUbGtRDHqYPrzoYgiaOeTwRaWtbTmcAjUR3J3EN5+n0hGnEqe3J sYZbS5si/L9xpW2wFOGipHXr2iUiIoXIFElo2uTq6mAfEdTnE4Xq3BvvCMGM0ij0 +LbuuyW9TdHrbL9wCu181FUEgM+HAdipGUI9RhgAiA9/jlCdQkQ= =heer -END PGP SIGNATURE- pgpmBOASAieUX.pgp Description: PGP signature --- End Message ---
Bug#1066229: marked as done (libtextwrap: FTBFS: textwrap.c:166:10: error: implicit declaration of function ‘wcwidth’; did you mean ‘mbwidth’? [-Werror=implicit-function-declaration])
Your message dated Mon, 25 Mar 2024 07:36:09 + with message-id and subject line Bug#1066229: fixed in libtextwrap 0.1-17 has caused the Debian Bug report #1066229, regarding libtextwrap: FTBFS: textwrap.c:166:10: error: implicit declaration of function ‘wcwidth’; did you mean ‘mbwidth’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtextwrap Version: 0.1-16 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -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 textwrap.lo textwrap.c > libtool: compile: gcc -DHAVE_CONFIG_H -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 -c > textwrap.c -fPIC -DPIC -o .libs/textwrap.o > textwrap.c: In function ‘mbwidth’: > textwrap.c:166:10: error: implicit declaration of function ‘wcwidth’; did you > mean ‘mbwidth’? [-Werror=implicit-function-declaration] > 166 | return wcwidth(c[0]); > | ^~~ > | mbwidth > cc1: some warnings being treated as errors > make[2]: *** [Makefile:553: textwrap.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libtextwrap_0.1-16_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libtextwrap Source-Version: 0.1-17 Done: Helmut Grohne We believe that the bug you reported is fixed in the latest version of libtextwrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helmut Grohne (supplier of updated libtextwrap 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, 25 Mar 2024 08:19:27 +0100 Source: libtextwrap Architecture: source Version: 0.1-17 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Helmut Grohne Closes: 1024927 1066229 Changes: libtextwrap (0.1-17) unstable; urgency=medium . * QA upload. * Fix FTBFS: Add missing #includes. (Closes: #1066229) * Support the noudeb build profile. (Closes: #1024927) Checksums-Sha1: fb01d6acd02313df77081c33e1e566550f959367 2013 libtextwrap_0.1-17.dsc 3f13321ae7eaf1ed1d2ecce329351ccd970eab10 6464 libtextwrap_0.1-17.debian.tar.xz 4613be51cf9ba8aaf25f7e7cdcd9b919adcaa474 6811 libtextwrap_0.1-17_amd64.buildinfo Checksums-Sha256: 9a3d1bbb09eb234ef9b1a112cba3524b25a47a2bdb2774f7ee271a65b34c7bdb 2013 libtextwrap_0.1-17.dsc 6769d8f0a33a9c0d6197335c9a1d597c8a9e8
Processed: tagging 1067618, tagging 1067624, tagging 1067596, tagging 1067623, tagging 1067609, tagging 1067547 ...
y-gnome/3.4.3-2. > fixed 1038298 3.4.3-4 Bug #1038298 {Done: Jeremy Bícha } [src:ruby-gnome] please drop transitional package ruby-gnome2-dev from src:ruby-gnome Marked as fixed in versions ruby-gnome/3.4.3-4. > reassign 1038297 src:ruby-gnome 3.4.3-2 Bug #1038297 {Done: Jeremy Bícha } [ruby-gnome2] please drop transitional package ruby-gnome2 from src:ruby-gnome Bug reassigned from package 'ruby-gnome2' to 'src:ruby-gnome'. No longer marked as found in versions ruby-gnome/3.4.3-2. No longer marked as fixed in versions ruby-gnome/3.4.3-4. Bug #1038297 {Done: Jeremy Bícha } [src:ruby-gnome] please drop transitional package ruby-gnome2 from src:ruby-gnome Marked as found in versions ruby-gnome/3.4.3-2. > fixed 1038297 3.4.3-4 Bug #1038297 {Done: Jeremy Bícha } [src:ruby-gnome] please drop transitional package ruby-gnome2 from src:ruby-gnome Marked as fixed in versions ruby-gnome/3.4.3-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016379 1032715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032715 1032716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032716 1032755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032755 1032788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032788 1038226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038226 1038297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038297 1038298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038298 1038301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038301 1038304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038304 1050523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050523 1065915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065915 1066102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066102 1067139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067139 1067219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067219 1067221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067221 1067223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067223 1067224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067224 1067304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067304 1067367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067367 1067547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067547 1067596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067596 1067609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067609 1067618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067618 1067623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067623 1067624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962752: marked as done (wiipdf FTCBFS: does not pass cross tools to make)
Your message dated Sat, 23 Mar 2024 15:59:46 + with message-id and subject line Bug#962752: fixed in wiipdf 1.4-4 has caused the Debian Bug report #962752, regarding wiipdf FTCBFS: does not pass cross tools to make 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.) -- 962752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wiipdf Version: 1.4-3 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs wiipdf fails to cross build from source, because it does not pass cross tools to make. The easiest way of fixing that - using dh_auto_build - makes wiipdf cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru wiipdf-1.4/debian/changelog wiipdf-1.4/debian/changelog --- wiipdf-1.4/debian/changelog 2020-06-08 21:06:00.0 +0200 +++ wiipdf-1.4/debian/changelog 2020-06-13 15:15:39.0 +0200 @@ -1,3 +1,9 @@ +wiipdf (1.4-4) UNRELEASED; urgency=medium + + * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1) + + -- Helmut Grohne Sat, 13 Jun 2020 15:15:39 +0200 + wiipdf (1.4-3) unstable; urgency=medium * QA upload. diff --minimal -Nru wiipdf-1.4/debian/rules wiipdf-1.4/debian/rules --- wiipdf-1.4/debian/rules 2020-06-08 21:06:00.0 +0200 +++ wiipdf-1.4/debian/rules 2020-06-13 15:15:38.0 +0200 @@ -19,10 +19,7 @@ build-indep: build-stamp build-stamp: dh_testdir - - # Add here commands to compile the package. - $(MAKE) - + dh_auto_build touch $@ clean: --- End Message --- --- Begin Message --- Source: wiipdf Source-Version: 1.4-4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of wiipdf, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated wiipdf 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, 23 Mar 2024 16:19:07 +0100 Source: wiipdf Built-For-Profiles: noudeb Architecture: source Version: 1.4-4 Distribution: unstable Urgency: medium Maintainer: Ubuntu Developers Changed-By: Matthias Klose Closes: 962752 1011489 Changes: wiipdf (1.4-4) unstable; urgency=medium . * QA upload. * Drop hard-coded dependency on shared library. * d/rules: Use dh_auto_build. Closes: #962752, #1011489. * Bump standards version. Checksums-Sha1: ed836af908d0b36ad6d7c16ecc6727e893546fc0 1802 wiipdf_1.4-4.dsc 78b68c099c189def9dd5620b4bd0299dbdaeb295 3588 wiipdf_1.4-4.debian.tar.xz 81e7a9cf5cffe52b580995dc618854ecc1b8a289 7276 wiipdf_1.4-4_source.buildinfo Checksums-Sha256: f3b77f1805518fa7514608a63241b6ee2c9f601cca1bc6439c49afb742ced4ee 1802 wiipdf_1.4-4.dsc 0ea3361b43b0041800cb99c097a391ede18d2394930929ce0111348fc3abb342 3588 wiipdf_1.4-4.debian.tar.xz 6f8318c26e80c107344f2baf7bb35634a2f706eed6fcd6beaa530f91fd5f9305 7276 wiipdf_1.4-4_source.buildinfo Files: e2b99828a62206dc3225baaab06902dc 1802 utils optional wiipdf_1.4-4.dsc a4f940a008bb5b20bc626de1514037bc 3588 utils optional wiipdf_1.4-4.debian.tar.xz 42ca260fb5c38f0a845a47e42b0d587f 7276 utils optional wiipdf_1.4-4_source.buildinfo Original-Maintainer: Debian QA Group -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmX+9AIQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9bXUD/0UvU664WWTh+81pJM/57kuLohQL/v5tnEW vFzmqcVj7ZraUWkL5IFQ13r+GgfBdZLWW79QgBHeDdy0IhSuR1RtkuObIwQKBbqs PS6RR3nR5dESBbudn0nocOZm1Il133GAB1nxgjwpVvIbINNYZSlL2akdGsvh5xl9 48LVu+V5XazSL4Y7JqwMDKGK0MulMbctEAA81cgwvPFz8qAWNu8ciFymBsXWlqbK vGSCoBaTSn58BTU5BV9wtUBaEENOEramkeIn1VC5rYS+wNdJW7G1NkCG3wVpbbRw Qt9dY5D5eKQWmIJzBPeoEWgPTbf9aSAPVn2I0Jq5IUjrMRTL6LKkZG4/zK0oSUUQ 1Wh5PBkMSdcBtLnrdBJN9jBc0g3w2FWeeA/2cJ/MLxu8Q48HX/gTTtJ0Dfh8fXcl Dz6rhPXnq0wcMFtBdtcsLtjLgi3RVuuSi6X1kRVcjqEHHm8CunBahzYmDRIpSXMf wzRmjUCzj4rUnLqsKi37o8VAy46TyUmOC16feKE/nLDK4AX8HanP/U3VlaQ/lYfZ UCvZxmpLajbujyP/jC8Vso7/nqIWhPpt1V/vtwljkH9hlaCYkUGEMJwYhEval99c MrmjGFn1k0xcrqKNs0iKL2HsmMH12jycjj7e9uoKdSqT3MoDaXRlepIBRW2xulI8 b5izzIpgRA== =Kx8o -END PGP SIGNATURE
Bug#1011489: marked as done (wiipdf: reproducible-builds: embedded build paths in /usr/bin/wiipdf)
Your message dated Sat, 23 Mar 2024 15:59:46 + with message-id and subject line Bug#1011489: fixed in wiipdf 1.4-4 has caused the Debian Bug report #1011489, regarding wiipdf: reproducible-builds: embedded build paths in /usr/bin/wiipdf 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.) -- 1011489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wiipdf Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The build path is embedded in /usr/bin/wiipdf: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/wiipdf.html /build/1st/wiipdf-1.4/wiipdf.c:114 vs. /build/2/wiipdf-1.4/2nd/wiipdf.c:114 The attached patch fixes this by calling dh_auto_build instead of $(MAKE) from debian/rules, which passes the default build flags including -ffile-prefix-map, which avoids embedding the absolute path in compiled files. Alternately, updating to dh and a newer debhelper-compat level would likely fix this as well, as it includes -ffile-prefix-map by default. With this patch applied, wiipdf should build reproducibly on tests.reproducible-builds.org! live well, vagrant From b5bb2fee67f79baaf5d2d949aa97b8e28dc1b45e Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 23 May 2022 21:53:21 + Subject: [PATCH] debian/rules: Use dh_auto_build instead of $(MAKE). --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index d4b3d3f..6955032 100755 --- a/debian/rules +++ b/debian/rules @@ -21,7 +21,7 @@ build-stamp: dh_testdir # Add here commands to compile the package. - $(MAKE) + dh_auto_build touch $@ -- 2.36.1 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: wiipdf Source-Version: 1.4-4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of wiipdf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated wiipdf 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, 23 Mar 2024 16:19:07 +0100 Source: wiipdf Built-For-Profiles: noudeb Architecture: source Version: 1.4-4 Distribution: unstable Urgency: medium Maintainer: Ubuntu Developers Changed-By: Matthias Klose Closes: 962752 1011489 Changes: wiipdf (1.4-4) unstable; urgency=medium . * QA upload. * Drop hard-coded dependency on shared library. * d/rules: Use dh_auto_build. Closes: #962752, #1011489. * Bump standards version. Checksums-Sha1: ed836af908d0b36ad6d7c16ecc6727e893546fc0 1802 wiipdf_1.4-4.dsc 78b68c099c189def9dd5620b4bd0299dbdaeb295 3588 wiipdf_1.4-4.debian.tar.xz 81e7a9cf5cffe52b580995dc618854ecc1b8a289 7276 wiipdf_1.4-4_source.buildinfo Checksums-Sha256: f3b77f1805518fa7514608a63241b6ee2c9f601cca1bc6439c49afb742ced4ee 1802 wiipdf_1.4-4.dsc 0ea3361b43b0041800cb99c097a391ede18d2394930929ce0111348fc3abb342 3588 wiipdf_1.4-4.debian.tar.xz 6f8318c26e80c107344f2baf7bb35634a2f706eed6fcd6beaa530f91fd5f9305 7276 wiipdf_1.4-4_source.buildinfo Files: e2b99828a62206dc3225baaab06902dc 1802 utils optional wiipdf_1.4-4.dsc a4f940a008bb5b20bc626de1514037bc 3588 utils optional wiipdf_1.4-4.debian.tar.xz 42ca260fb5c38f0a845a47e42b0d587f 7276 utils optional wiipdf_1.4-4_source.buildinfo Original-Maintainer: Debian QA Group -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmX+9AIQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9bXUD/0UvU664WWTh+81pJM/57kuLohQL/v5tnEW vFzmqcVj7ZraUWkL5IFQ13r+GgfBdZLWW79QgBHeDdy0IhSuR1RtkuObIwQKBbqs PS6RR3nR5dESBbudn0nocOZm1Il133GAB1nxgjwpVvIbINNYZSlL2akdGsvh5xl9 48LVu+V5XazSL4Y7JqwMDKGK0MulMbctEAA81cgwvPFz8qAWNu8ciFymBsXWlqbK vGSCoBaTSn58BTU5BV9wtUBaEENOEramkeIn1VC5rYS+wNdJW7G1NkCG3wVpbbRw Qt9dY5D5eKQWmIJzBPeoEWgPTbf9aSAPVn2I0Jq5IUjrMRTL6LKkZG4/zK0oSUUQ 1Wh5PBkMSdcBtLnrdBJN9jBc0g3w2FWeeA/2cJ/MLxu8Q48HX/gTTtJ0Dfh8fXcl
Bug#1067439: marked as done (cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12)
Your message dated Sat, 23 Mar 2024 14:47:54 + with message-id and subject line Bug#1067439: fixed in cpu 1.4.3-14 has caused the Debian Bug report #1067439, regarding cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12 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.) -- 1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cpu Version: 1.4.3-13+b1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** It was working on Debian 11, but after upgrading to Debian 12 just calling the program make it crash: root@davis:~# cpu CPU_loadLibrary: dlopen(libcpu_ldap.so, RTLD_NOW) failed. CPU_loadLibrary: /lib/x86_64-linux-gnu/libcpu_ldap.so: undefined symbol: globalLdap There was an error loading the ldap library. Exiting. Regards Simone -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cpu depends on: ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9+deb12u4 ii libcrack2 2.9.6-5+b1 ii libcrypt1 1:4.4.33-2 ii libldap-2.5-0 2.5.13+dfsg-5 ii ucf3.0043+nmu1 cpu recommends no packages. cpu suggests no packages. -- debconf information: cpu/ldap/BIND_PASS: (password omitted) cpu/ldap/USER_BASE: ou=People,dc=truelite,dc=it cpu/ldap/BIND_DN: cn=admin,dc=truelite,dc=it cpu/ldap/GROUP_BASE: ou=Group,dc=truelite,dc=it cpu/ldap/LDAP_URI: ldap://localhost cpu/do_debconf: true --- End Message --- --- Begin Message --- Source: cpu Source-Version: 1.4.3-14 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of cpu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated cpu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Mar 2024 14:39:06 +0100 Source: cpu Architecture: source Version: 1.4.3-14 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1067439 Changes: cpu (1.4.3-14) unstable; urgency=medium . * QA upload. * Actually provide a definition of globalLdap. (Closes: #1067439) * Add smoke test. Checksums-Sha1: 01a806fd3c51c723c331ec64b2338c5a594e0389 1851 cpu_1.4.3-14.dsc c3037f05780131501432e95d748763de9a7a7f77 29748 cpu_1.4.3-14.debian.tar.xz 4391fa52798b9e9a1962bf981706ea2d599213f1 6038 cpu_1.4.3-14_source.buildinfo Checksums-Sha256: 6d7f47b547abc058ad98a75ea7f33c5f719ae7d4bb9231a5ff101c5b894e16e1 1851 cpu_1.4.3-14.dsc 708be0c474ef369420d0e6c9482aa2ef784585dfe4422eaab57fef1a24b6aa98 29748 cpu_1.4.3-14.debian.tar.xz 3a07e37198d86abbd7258e3e3cbcefb19607dad8bb1a28247d0652489a75ced2 6038 cpu_1.4.3-14_source.buildinfo Files: 0c8d30636b23ac17fc1dbc77ef10062b 1851 admin optional cpu_1.4.3-14.dsc 49235e9d7c29aa01905e14354b6868ff 29748 admin optional cpu_1.4.3-14.debian.tar.xz 4a441e27c1dfe2ac939942b1077fafc5 6038 admin optional cpu_1.4.3-14_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmX+3CMQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCPNHD/4nHcGH6U/dsAk5HQEVszjv3TfQliOy/Ak+ PlGCcJKOGQqOXa64PSnGOiZtqAp5BC56BGuw4oKqOY5pA99vJquPnKiaOU8m5Tp9 KPPV+BrUTqhxW0rqIGbTHPv0a8ZMnr9RTrPNjlTjlyZbhS4/9GyHc2lbTUJQv1ws
Bug#1065915: marked as done (pdfkit: Please drop dependencies on python3-distutils)
Your message dated Sat, 23 Mar 2024 08:59:42 +0100 with message-id <23cc132f-577e-4d84-a5be-71e2e82ac...@debian.org> and subject line fixed in 1.0.0-3 has caused the Debian Bug report #1065915, regarding pdfkit: Please drop dependencies on python3-distutils 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.) -- 1065915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdfkit Version: 1.0.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Version: 1.0.0-3 fixed--- End Message ---
Processed: reassign 1065343 to src:util-linux, affects 1065343, tagging 1067439, found 1067473 in 3.19.0-2 ...
Processing commands for cont...@bugs.debian.org: > reassign 1065343 src:util-linux Bug #1065343 [libuuid1t64] E: Tried to extract package, but file already exists. Exit... Warning: Unknown package 'libuuid1t64' Bug reassigned from package 'libuuid1t64' to 'src:util-linux'. Ignoring request to alter found versions of bug #1065343 to the same values previously set Ignoring request to alter fixed versions of bug #1065343 to the same values previously set > affects 1065343 + libuuid1t64 Bug #1065343 [src:util-linux] E: Tried to extract package, but file already exists. Exit... Added indication that 1065343 affects libuuid1t64 > tags 1067439 + sid trixie bookworm bullseye Bug #1067439 [cpu] cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12 Added tag(s) trixie, bullseye, bookworm, and sid. > found 1067473 3.19.0-2 Bug #1067473 {Done: Bastian Germann } [gambas3] gambas3: ftbfs on time64 arches Marked as found in versions gambas3/3.19.0-2. > found 1067474 0.15.1-2 Bug #1067474 [gxr-openvr] gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built There is no source info for the package 'gxr-openvr' at version '0.15.1-2' with architecture '' Unable to make a source version for version '0.15.1-2' Marked as found in versions 0.15.1-2. > tags 1067474 + sid trixie Bug #1067474 [gxr-openvr] gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built Added tag(s) trixie and sid. > tags 1067460 + sid trixie Bug #1067460 [entropybroker] entropybroker: please fix libpng-dev build dependency Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1065343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065343 1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439 1067460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067460 1067473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067473 1067474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1063118 is important, user release.debian....@packages.debian.org, usertagging 1063118 ...
Processing commands for cont...@bugs.debian.org: > severity 1063118 important Bug #1063118 {Done: Benjamin Drung } [src:hdf-eos5] hdf-eos5: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was sebas...@debian.org). > usertags 1063118 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > severity 1063134 important Bug #1063134 {Done: Benjamin Drung } [src:libquazip] libquazip: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > usertags 1063134 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > severity 1063294 important Bug #1063294 {Done: Benjamin Drung } [src:pth] pth: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > usertags 1063294 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > severity 1066395 important Bug #1066395 {Done: Bas Couwenberg } [src:python-hdf4] python-hdf4: FTBFS: ld: cannot find -lmfhdf: No such file or directory Severity set to 'important' from 'serious' > usertags 1066395 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > severity 1066442 important Bug #1066442 {Done: Bas Couwenberg } [src:merkaartor] merkaartor: FTBFS: Preferences/MerkaartorPreferences.h:28:10: fatal error: proxy.h: No such file or directory Severity set to 'important' from 'serious' > usertags 1066442 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > severity 1066747 important Bug #1066747 {Done: Bas Couwenberg } [src:rasterio] rasterio: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 Severity set to 'important' from 'serious' > usertags 1066747 time-t-downgrade There were no usertags set. Usertags are now: time-t-downgrade. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063118 1063134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063134 1063294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063294 1066395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066395 1066442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066442 1066747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1062123 is important, severity of 1062246 is important, severity of 1062476 is important ...
Processing commands for cont...@bugs.debian.org: > severity 1062123 important Bug #1062123 {Done: Steve Langasek } [src:gr-osmosdr] gr-osmosdr: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1062246 important Bug #1062246 {Done: Lukas Märdian } [src:libcdk5] libcdk5: NMU diff for 64-bit time_t transition Ignoring request to change severity of Bug 1062246 to the same value. > severity 1062476 important Bug #1062476 {Done: Steve Langasek } [src:gnuradio] gnuradio: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1062692 important Bug #1062692 {Done: Graham Inggs } [src:libusb3380] libusb3380: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1062737 important Bug #1062737 {Done: Graham Inggs } [src:libxtrxll] libxtrxll: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1062981 important Bug #1062981 {Done: Benjamin Drung } [src:thrift] thrift: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1063052 important Bug #1063052 {Done: Steve Langasek } [src:volk] volk: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1063085 important Bug #1063085 {Done: Steve Langasek } [src:uhd] uhd: NMU diff for 64-bit time_t transition Ignoring request to change severity of Bug 1063085 to the same value. > severity 1064292 important Bug #1064292 {Done: Steve Langasek } [src:pyside2] pyside2: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1064708 important Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does not match "Parameter 'surface' is invalid" Severity set to 'important' from 'serious' > severity 1063279 important Bug #1063279 {Done: Steve Langasek } [src:xmlrpc-c] xmlrpc-c: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > severity 1063130 important Bug #1063130 {Done: Benjamin Drung } [src:libmspack] libmspack: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062123 1062246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062246 1062476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062476 1062692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062692 1062737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062737 1062981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062981 1063052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063052 1063085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063085 1063130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063130 1063279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063279 1064292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064292 1064708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062521: marked as done (lcm: NMU diff for 64-bit time_t transition)
Your message dated Thu, 21 Mar 2024 10:31:30 +0100 with message-id <20240321093130.36tezlpg4gefk...@notk.org> and subject line No ABI change due to time_t has caused the Debian Bug report #1062521, regarding lcm: NMU diff for 64-bit time_t 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.) -- 1062521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lcm Version: 1.3.1+repack1-7 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified lcm as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for lcm which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect diff -Nru lcm-1.3.1+repack1/debian/changelog lcm-1.3.1+repack1/debian/changelog --- lcm-1.3.1+repack1/debian/changelog 2023-12-06 20:48:38.0 + +++ lcm-1.3.1+repack1/debian/changelog 2024-02-01 18:25:16.0 + @@ -1,3 +1,10 @@ +lcm (1.3.1+repack1-7.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Graham Inggs Thu, 01 Feb 2024 18:25:16 + + lcm (1.3.1+repack1-7) unstable; urgency=medium * QA upload. diff -Nru lcm-1.3.1+repack1/debian/control lcm-1.3.1+repack1/debian/control --- lcm-1.3.1+repack1/debian/control2023-12-06 00:27:57.0 + +++ lcm-1.3.1+repack1/debian/control2024-02-01 18:25:16.0 + @@ -12,7 +12,10 @@ Vcs-Browser: https://salsa.debian.org/debian/lcm Rules-Requires-Root: no -Package: liblcm1 +Package: liblcm1t64 +Provides: ${t64:Provides} +Replaces: liblcm1 +Breaks: liblcm1 (<< ${source:Version}) Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: Lightweight Communications and Marshalling @@ -26,7 +29,7 @@ Package: liblcm-dev Architecture: any -Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, +Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, liblcm-bin Description: Lightweight Communications and Marshalling LCM is a set of libraries and tools for message passing and data marshalling, @@ -39,7 +42,7 @@ Package: liblcm-bin Architecture: any -Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Description: Lightweight Communications and Marshalling LCM is a set of libraries and tools for message passing and data marshalling, targeted at real-time systems where high-bandwidth and low latency are @@ -51,7 +54,7 @@ Package: liblcm-java Architecture: any -Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, +Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, liblcm-bin Description:
Processed: closing 1066394
Processing commands for cont...@bugs.debian.org: > close 1066394 5.3.28+dfsg2-6 Bug #1066394 [src:db5.3] db5.3: "build did not include support for sequences" The source 'db5.3' and version '5.3.28+dfsg2-6' do not appear to match any binary packages Marked as fixed in versions db5.3/5.3.28+dfsg2-6. Bug #1066394 [src:db5.3] db5.3: "build did not include support for sequences" Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1066394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066003: marked as done (libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.)
Your message dated Wed, 20 Mar 2024 21:40:03 + with message-id and subject line Bug#1066003: fixed in db5.3 5.3.28+dfsg2-6 has caused the Debian Bug report #1066003, regarding libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. 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.) -- 1066003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libberkeleydb-perl Version: 0.64-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libberkeleydb-perl=armhf=0.64-2%2Bb3=1709868730=0 Test Summary Report --- t/sequence.t (Wstat: 65280 (exited 255) Tests: 3 Failed: 1) Failed test: 3 Non-zero exit status: 255 Parse errors: Bad plan. You planned 13 tests but ran 3. Files=35, Tests=1861, 3 wallclock secs ( 0.24 usr 0.06 sys + 2.78 cusr 0.30 csys = 3.38 CPU) Result: FAIL Failed 1/35 test programs. 1/1861 subtests failed. make[1]: *** [Makefile:1040: test_dynamic] Error 255 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: db5.3 Source-Version: 5.3.28+dfsg2-6 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of db5.3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated db5.3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Mar 2024 21:33:34 +0100 Source: db5.3 Architecture: source Version: 5.3.28+dfsg2-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1066003 Changes: db5.3 (5.3.28+dfsg2-6) unstable; urgency=medium . * QA upload * debian/patches: Add missing #include to fix configure check (Closes: #1066003) Checksums-Sha1: 46f0ff9a1c87b991fe8c4c1f153c3477ca466c05 1769 db5.3_5.3.28+dfsg2-6.dsc f296a283c01ab48980528661c756bd8b144ae8b6 34196 db5.3_5.3.28+dfsg2-6.debian.tar.xz 7d5254e7d2c44ec1e86f67ce9ae0cde448a3a30e 6064 db5.3_5.3.28+dfsg2-6_source.buildinfo Checksums-Sha256: f56d1b663622620445a0654a7b5efc0ad7d04cc0278d8695f159d76ac272b0b8 1769 db5.3_5.3.28+dfsg2-6.dsc e1ebfb15e23cd7f64d801ec4bad0c30aa178ab0d23e75b993896f1ece8187cff 34196 db5.3_5.3.28+dfsg2-6.debian.tar.xz 6eb969c385bf1d60b94dde2b99d20658e379bc9edc6e79ff0fac5348d25991e0 6064 db5.3_5.3.28+dfsg2-6_source.buildinfo Files: 2f189861f025d6d58fd4ea0f411ba24b 1769 libs optional db5.3_5.3.28+dfsg2-6.dsc 206a137f8b206af9acee350c6a73017d 34196 libs optional db5.3_5.3.28+dfsg2-6.debian.tar.xz 5c5e9b119e3151fe1d6c5174c6bd5c65 6064 libs optional db5.3_5.3.28+dfsg2-6_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZftLiwAKCRAhk2s2YA/N iRV7AQD9Kf04qgv3b1pRSguQ/3ELOZ6hta4Lj9KXZVJY59fbxAD9HmmZf/1HWBP8 7G9yk1Sr52NHdgiUozJKQfczCAJc8wU= =r45U -END PGP SIGNATURE- pgpfjgr17Qt6b.pgp Description: PGP signature --- End Message ---
Processed: reassign 1066003 to src:db5.3
Processing commands for cont...@bugs.debian.org: > reassign 1066003 src:db5.3 5.3.28+dfsg2-4 Bug #1066003 [src:libberkeleydb-perl] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Bug reassigned from package 'src:libberkeleydb-perl' to 'src:db5.3'. No longer marked as found in versions libberkeleydb-perl/0.64-2. Ignoring request to alter fixed versions of bug #1066003 to the same values previously set Bug #1066003 [src:db5.3] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Marked as found in versions db5.3/5.3.28+dfsg2-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067171: marked as done (bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)
Your message dated Wed, 20 Mar 2024 20:37:34 + with message-id and subject line Bug#1067171: fixed in bleachbit 4.6.0-3 has caused the Debian Bug report #1067171, regarding bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf 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.) -- 1067171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bleachbit Version: 4.6.0-2 Severity: serious Justification: blocker for 64-bit time_t transition User: debian-...@lists.debian.org Usertags: time-t Control: block 1036884 by -1 bleachbit is an Architecture: all package, but has a direct dependency on libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via gir1.2-gtk-3.0. On the architectures affected by the 64-bit time_t transition (notably armel and armhf), this is an impossible dependency, because libgtk-3-0 and libgtk-3-0t64 conflict. Please remove the explicit dependency on libgtk-3-0. For Python code that uses GTK via GObject-Introspection, it is sufficient to depend on gir1.2-gtk-3.0. More information about this transition is available on <https://wiki.debian.org/ReleaseGoals/64bit-time>. Thanks, smcv --- End Message --- --- Begin Message --- Source: bleachbit Source-Version: 4.6.0-3 Done: Fabio Fantoni We believe that the bug you reported is fixed in the latest version of bleachbit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Fantoni (supplier of updated bleachbit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2024 21:57:51 +0100 Source: bleachbit Architecture: source Version: 4.6.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team , Changed-By: Fabio Fantoni Closes: 1065808 1067171 Changes: bleachbit (4.6.0-3) unstable; urgency=medium . * Return to Debian Python Team and add myself to uploaders (Closes: #1065808) * Remove libgtk-3-0 from depends (Closes: #1067171) Checksums-Sha1: 4e6386dbc57cba80d49827cdf5073f7fd29c7249 2037 bleachbit_4.6.0-3.dsc a3fe5a3ba1064b3eb35e80020b00e43764eee209 12496 bleachbit_4.6.0-3.debian.tar.xz a717e7adb163146d4c462b54c1e4fb378b97e098 7313 bleachbit_4.6.0-3_source.buildinfo Checksums-Sha256: 88edad2e16b348cd6593c47cecc4a5ba63fe00f52708fb3365525074b0ece2d5 2037 bleachbit_4.6.0-3.dsc 0d1b9655dacdd675e1f2dc0efe34d1faf6c6e4f9206425b642554fb14ceaef44 12496 bleachbit_4.6.0-3.debian.tar.xz 461efab7ea3aa504b3d204b4ad29877100bb26a1d4afaccb528a6d36cf3b3d99 7313 bleachbit_4.6.0-3_source.buildinfo Files: da8a82ce3a556863d5d91bf103a0176f 2037 admin optional bleachbit_4.6.0-3.dsc 6608c8dcec373bed4232dd5d0c766f7a 12496 admin optional bleachbit_4.6.0-3.debian.tar.xz 5c7210b628cc77bd5074ef86686e14cf 7313 admin optional bleachbit_4.6.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmX7P8MACgkQMfMURUSh dBrgjQ//f/jeTpoOLUKj6oeOIbN/AHySurU+m+6zaOobDuDAN4C+vcTJvuLwgdJR VZX3y/3EQNKh5oayrkRUQFQEo1ffKw7hM7MZ1U1/q92ZILOi0S7U1uWVE9tHw6sG FaErQXGLV+aCY9UICV16VN1TTFiseEokone8BCsozCJ7L/jXGKYnG3D1rZBHPkCg ymGiWekqBoOTii8dd9Smw6TADjWg2CUI5j9G+NfyD5SV2X/K7FdoBqR3QM/olsDL lV3UbwoZmeuGl4qwU/15asqllg2KCTmvmli+DYmL88gwrFRkVNkdL+VUGFqbAKPd gLo7S4VSskmsesQQmlEyLCPvRK12xZ2h23v+63xi6gwb/KXauy0rfU3R7GbTM0Mu gF/bid0IP9cW7kf3e3cHgPLwJynZN3PgBypZmOsOTYCG4gVs36kAl2nFRAI1EXUE qk0BSwUOzaV+SH3d3aFWnbkv9bEyHfHK80seOcQDGoZf18VZATJnBoWjs3crcoCD uocyGUCgXZdof/Vda8xLZz8Fg6g/Dr2aqDc3SmruRHsj0xo7jyEEXyfKN4xBdVTn 0oqkwGkMC/YKh2rddfs2aXJlr4m8VG0/SlsGWpe+EJrl2grC9VzolUQC5PPaHTAy reKFEG5bD1avdgklfNle9U6I5JX+JKk9jN/x4+519/NeOH1iexM= =xAVI -END PGP SIGNATURE- pgpUPROJ_7J5Q.pgp Description: PGP signature --- End Message ---
Bug#1065769: marked as done (libexplain: FTBFS on arm{el,hf}: libexplain/buffer/ipc_perm.c:104:38: error: ‘const struct ipc_perm’ has no member named ‘key’; did you mean ‘__key’?)
Your message dated Wed, 20 Mar 2024 18:06:44 + with message-id and subject line Bug#1065769: fixed in libexplain 1.4.D001-13 has caused the Debian Bug report #1065769, regarding libexplain: FTBFS on arm{el,hf}: libexplain/buffer/ipc_perm.c:104:38: error: ‘const struct ipc_perm’ has no member named ‘key’; did you mean ‘__key’? 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.) -- 1065769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libexplain Version: 1.4.D001-12.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libexplain=armel=1.4.D001-12.1=1709133439=0 libtool: compile: gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -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 -Wall -Wextra -Wl,--as-needed -I. -c libexplain/buffer/ipc_perm.c -fPIC -DPIC -o libexplain/buffer/.libs/ipc_perm.o libexplain/buffer/ipc_perm.c: In function ‘explain_buffer_ipc_perm’: libexplain/buffer/ipc_perm.c:104:38: error: ‘const struct ipc_perm’ has no member named ‘key’; did you mean ‘__key’? 104 | explain_buffer_int(sb, data->key); | ^~~ | __key libexplain/buffer/ipc_perm.c:128:41: error: ‘const struct ipc_perm’ has no member named ‘seq’; did you mean ‘__seq’? 128 | explain_buffer_ushort(sb, data->seq); | ^~~ | __seq make[1]: *** [Makefile:11444: libexplain/buffer/ipc_perm.lo] Error 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libexplain Source-Version: 1.4.D001-13 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of libexplain, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated libexplain package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 20 Mar 2024 18:45:42 +0100 Source: libexplain Architecture: source Version: 1.4.D001-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1065769 1066443 Changes: libexplain (1.4.D001-13) unstable; urgency=medium . * QA upload. * Fix generation of toplevel ./configure script. * Fix building with -Werror=implicit-function-declaration. (Closes: #1065769, #1066443) Checksums-Sha1: c3e49cc4d5c39db6e268b36de9731ecb04231e19 2241 libexplain_1.4.D001-13.dsc 7c9c88abdfc52c51fa3170365c13b7ebc3fe0c02 47996 libexplain_1.4.D001-13.debian.tar.xz bce86acbffdf68d60665609f14ef6c7ac0e38d79 7695 libexplain_1.4.D001-13_source.buildinfo Checksums-Sha256: 6570c54765810038661bc4b0ea9a960c0090fa1475162a076bd495d5894bed7a 2241 libexplain_1.4.D001-13.dsc c0be85ea34eccdde818cf0a8accdbae5384d33857db1a261b0389c917e2d9c62 47996 libexplain_1.4.D001-13.debian.tar.xz d2edea629a0dee19983698910cda3efb6b234298bd79a284b065b17803a40ccc 7695 libexplain_1.4.D001-13_source.buildinfo Files: a6c8a6ceee014ac214bdec6e128b65f7 2241 devel optional libexplain_1.4.D001-13.dsc daf6fae66380abb33490b4c6ccab374e 47996 devel optional libexplain_1.4.D001-13.debian.tar.xz 813223870dd3c5b4d0202fedc05df69d 7695 devel optional libexplain_1.4.D001-13_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmX7IaYQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCFeaD/0fFeqpT1NZTNo/ta0zCACPFfQFfdXZOSKh cLGjNKMTVMBHKw+f3xIt6z21VWuA1S6qn7DNLG/RrZLgM2i6tHHClbEc7GDRgi3K WfqbqR02uLXzPWYBUnbSQ261yJ4735ugpDf6sDQQsKEs13LW/TYma6Ku3wtDUx/P FEfUAV2itanl11CgrP/q0E4B+ol1ZKztFSywgdrFKiGHmsS+SoZwFf18lYDeq97b DBpARXwQkDCgBquMNy7O+nhCDDppfrWrAVzWXTayVxx1DXUT4WBt
Bug#1062953: marked as done (python3-pyocd: Module is unusable (missing runtime dependencies))
Your message dated Wed, 20 Mar 2024 11:01:58 + with message-id and subject line Bug#1062953: fixed in pyocd 0.36.0-2 has caused the Debian Bug report #1062953, regarding python3-pyocd: Module is unusable (missing runtime dependencies) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1062953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pyocd Version: 0.36.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, The upload of python3-pyocd 0.36.0-1 appears to be completely unusable: $ python3 Python 3.11.7 (main, Dec 8 2023, 14:22:46) [GCC 13.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import pyOCD Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/pyOCD/__init__.py", line 21, in from . import gdbserver File "/usr/lib/python3/dist-packages/pyOCD/gdbserver/__init__.py", line 17, in from .gdbserver import GDBServer File "/usr/lib/python3/dist-packages/pyOCD/gdbserver/gdbserver.py", line 42, in from ..rtos import RTOS File "/usr/lib/python3/dist-packages/pyOCD/rtos/__init__.py", line 29, in load_plugin_classes_of_type('pyocd.rtos', RTOS, ThreadProvider) File "/usr/lib/python3/dist-packages/pyOCD/core/plugin.py", line 97, in load_plugin_classes_of_type plugin = entry_point.load()() ^^ File "/usr/lib/python3/dist-packages/importlib_metadata/__init__.py", line 203, in load module = import_module(match.group('module')) File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/usr/lib/python3/dist-packages/pyocd/__init__.py", line 21, in from . import gdbserver File "/usr/lib/python3/dist-packages/pyocd/gdbserver/__init__.py", line 17, in from .gdbserver import GDBServer File "/usr/lib/python3/dist-packages/pyocd/gdbserver/gdbserver.py", line 50, in return _bootstrap._gcd_import(name[level:], package, level) File "/usr/lib/python3/dist-packages/pyocd/probe/jlink_probe.py", line 22, in import pylink ModuleNotFoundError: No module named 'pylink' The build log reports several missing dependencies: I: dh_python3 pydist:302: Cannot find package that provides cmsis_pack_manager. I: dh_python3 pydist:302: Cannot find package that provides libusb_package. I: dh_python3 pydist:302: Cannot find package that provides pylink_square. Although present in the distribution, no tests are configured to run at build time. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pyocd depends on: ii python3 3.11.6-1 ii python3-capstone 4.0.2-5+b1 ii python3-colorama 0.4.6-4 ii python3-importlib-metadata 4.12.0-1 ii python3-importlib-resources 6.0.1-1 ii python3-intelhex 2.3.0-2 ii python3-intervaltree 3.0.2-1.1 ii python3-lark 1.1.9-1 ii python3-natsort 8.0.2-2 ii python3-pkg-resources68.1.2-2 ii python3-prettytable 3.6.0-1 ii python3-pyelftools 0.30-1 ii python3-six 1.16.0-4 ii python3-typing-extensions4.7.1-2 ii python3-usb 1.2.1-2 ii python3-yaml 6.0.1-1+b1 python3-pyocd recommends no packages. python3-pyocd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pyocd Source-Version: 0.36.0-2 Done: Jakob Haufe We believe that the bug you reported is fixed in the latest version of pyocd, which is due to be installed in the Debian FTP archive. A summary of th
Processed: Bug#1067171 marked as pending in bleachbit
Processing control commands: > tag -1 pending Bug #1067171 [bleachbit] bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf Added tag(s) pending. -- 1067171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf
Processing control commands: > block 1036884 by -1 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1067170 1065787 1065973 1067069 1055352 1065816 1066049 1066794 1055530 1062847 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067171 -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 1067171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bookworm-pu: package hovercraft/2.7-6~deb12u1
Processing control commands: > affects -1 + src:hovercraft Bug #1067149 [release.debian.org] bookworm-pu: package hovercraft/2.7-6~deb12u1 Added indication that 1067149 affects src:hovercraft > block 1025655 with -1 Bug #1025655 {Done: Andreas Beckmann } [hovercraft] hovercraft: requires python3-setuptools 1025655 was not blocked by any bugs. 1025655 was not blocking any bugs. Added blocking bug(s) of 1025655: 1067149 > affects 1067148 + src:hovercraft Bug #1067148 [release.debian.org] bullseye-pu: package hovercraft/2.7-2+deb11u1 Added indication that 1067148 affects src:hovercraft > block 1025655 with 1067148 Bug #1025655 {Done: Andreas Beckmann } [hovercraft] hovercraft: requires python3-setuptools 1025655 was blocked by: 1067149 1025655 was not blocking any bugs. Added blocking bug(s) of 1025655: 1067148 -- 1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655 1067148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067148 1067149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025655: marked as done (hovercraft: requires python3-setuptools)
Your message dated Tue, 19 Mar 2024 01:36:25 + with message-id and subject line Bug#1025655: fixed in hovercraft 2.7-6 has caused the Debian Bug report #1025655, regarding hovercraft: requires python3-setuptools to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hovercraft Version: 2.7-2 Severity: important X-Debbugs-Cc: bms.deb...@barwap.com Dear Maintainer, fresh install, running hovercraft $ hovercraft planning_presentation.rst html Traceback (most recent call last): File "/usr/bin/hovercraft", line 33, in sys.exit(load_entry_point('hovercraft==2.7', 'console_scripts', 'console_script')()) File "/usr/bin/hovercraft", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load module = import_module(match.group('module')) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/share/hovercraft/hovercraft/__init__.py", line 6, in import pkg_resources File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3243, in def _initialize_master_working_set(): File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3226, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'setuptools' distribution was not found and is required by hovercraft * What outcome did you expect instead? $ hovercraft planning_presentation.rst html (No errors - what did happen after apt-get install python3-setuptools) -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-19-amd64 (SMP w/12 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hovercraft depends on: ii libjs-impress 1.0.0-1 ii libjs-sphinxdoc3.4.3-2 ii python33.9.2-3 ii python3-docutils 0.16+dfsg-4 ii python3-lxml 4.6.3+dfsg-0.1+deb11u1 ii python3-pkg-resources 52.0.0-4 ii python3-pygments 2.7.1+dfsg-2.1 ii python3-svg.path 3.0-2 ii python3-watchdog 1.0.2-2 hovercraft recommends no packages. hovercraft suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: hovercraft Source-Version: 2.7-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of hovercraft, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated hovercraft package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Mar 2024 02:12:55 +0100 Source: hovercraft Architecture: sou
Processed: found 1025655 in 2.7-5, found 1025655 in 2.6-2, tagging 1067117, tagging 1067021, tagging 1066860 ...
Processing commands for cont...@bugs.debian.org: > found 1025655 2.7-5 Bug #1025655 [hovercraft] hovercraft: requires python3-setuptools Marked as found in versions hovercraft/2.7-5. > found 1025655 2.6-2 Bug #1025655 [hovercraft] hovercraft: requires python3-setuptools Marked as found in versions hovercraft/2.6-2. > tags 1067117 - sid trixie Bug #1067117 [src:budgie-desktop] budgie-desktop: Fails to build with mutter >= 45 Removed tag(s) trixie and sid. > tags 1067021 - sid trixie Bug #1067021 {Done: Jose Luis Blanco Claraco } [src:mrpt] mrpt ftbfs on armhf (32bit time_t64 architecture) Removed tag(s) sid and trixie. > tags 1066860 - sid trixie Bug #1066860 [src:libprelude] libprelude ftbfs on time_t64 archs Removed tag(s) sid and trixie. > tags 1058377 - sid trixie Bug #1058377 [src:watcher] watcher: FTBFS: failed tests Removed tag(s) trixie and sid. > notfound 1065083 1.10.2-2 Bug #1065083 {Done: David Kunz } [icingaweb2-module-director] $icingaweb2-module-director: [INTL:de] updated German icingaweb2-module-director translation\ No longer marked as found in versions icingaweb2-module-director/1.10.2-2. > notfound 1066919 1.2.0-3 Bug #1066919 {Done: David Kunz } [icingaweb2-module-fileshipper] icingaweb2-module-fileshipper: [INTL:de] updated German po file translation No longer marked as found in versions icingaweb2-module-fileshipper/1.2.0-3. > notfound 1066923 2.1.0-2 Bug #1066923 {Done: David Kunz } [icingaweb2-module-generictts] icingaweb2-module-generictts: [INTL:de] updated German po file translation No longer marked as found in versions icingaweb2-module-generictts/2.1.0-2. > tags 1046634 + sid trixie Bug #1046634 {Done: Bas Couwenberg } [src:libapreq2] libapreq2: Fails to build source after successful build Ignoring request to alter tags of bug #1046634 to the same tags previously set > tags 1048642 + experimental Bug #1048642 {Done: David Prévot } [src:php-text-template] php-text-template: Fails to build source after successful build Added tag(s) experimental. > tags 1040481 + experimental Bug #1040481 {Done: intrigeri } [src:apparmor] apparmor: Add lock file permission to snap browsers Added tag(s) experimental. > tags 892541 + experimental Bug #892541 {Done: Matthew Vernon } [src:pcre2] pcre2: JIT broken on mips Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655 1040481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040481 1046634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046634 1048642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048642 1058377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058377 1065083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065083 1066860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066860 1066919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066919 1066923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066923 1067021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067021 1067117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067117 892541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928742: marked as done (unworkable FTCBFS: hard codes the build architecture pkg-config)
Your message dated Mon, 18 Mar 2024 02:49:12 + with message-id and subject line Bug#928742: fixed in unworkable 0.53-6 has caused the Debian Bug report #928742, regarding unworkable FTCBFS: hard codes the build architecture pkg-config 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.) -- 928742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unworkable Version: 0.53-4 Tags: patch User: helm...@debian.org Usertags: rebootstrap unworkable fails to cross build from source, because it uses the build architecture pkg-config for discovering libbsd-overlay and thus fails finding it. Making pkg-config substitutable is enough to make unworkable cross buildable. Please consider applying the attached patch. Helmut --- unworkable-0.53.orig/GNUmakefile +++ unworkable-0.53/GNUmakefile @@ -30,8 +30,9 @@ UNAME=$(shell uname) ifneq (, $(filter Linux GNU GNU/%, $(UNAME))) SRCS+=openbsd-compat/sha1.c -LIBS+=$(shell pkg-config --libs libbsd-overlay) -CFLAGS+=$(shell pkg-config --cflags libbsd-overlay) +PKG_CONFIG?= pkg-config +LIBS+=$(shell $(PKG_CONFIG) --libs libbsd-overlay) +CFLAGS+=$(shell $(PKG_CONFIG) --cflags libbsd-overlay) else ifeq ($(UNAME),sunos) SRCS+=openbsd-compat/err.c --- End Message --- --- Begin Message --- Source: unworkable Source-Version: 0.53-6 Done: David da Silva Polverari We believe that the bug you reported is fixed in the latest version of unworkable, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David da Silva Polverari (supplier of updated unworkable 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, 18 Mar 2024 02:04:28 + Source: unworkable Architecture: source Version: 0.53-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: David da Silva Polverari Closes: 928742 Changes: unworkable (0.53-6) unstable; urgency=medium . [ David da Silva Polverari ] * QA upload. * Ran wrap-and-sort. * debian/control: - Added 'Rules-Requires-Root: no' to source stanza. - Bumped Standards-Version to 4.6.2. - Changed from obsolete package pkg-config to pkgconf in Build-Depends. * debian/copyright: - Added missing Files stanzas and respective stand-alone License stanzas. - Fixed existing upstream copyright years. * debian/gbp.conf: created to make git repository comply with DEP-14. * debian/lintian-overrides: removed, as its only override referred to an unknown tag. * debian/patches/: - Updated metadata in all previous patches. - cross.patch: added to fix a FTCBFS. Thanks to Helmut Grohne . (Closes: #928742) * debian/salsa-ci.yml: added to provide CI tests for Salsa. * debian/watch: bumped to version 4. . [ Debian Janitor ] * Update renamed lintian tag names in lintian overrides. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.5.0, no changes needed. * Bump debhelper from old 12 to 13. + debian/rules: Drop --fail-missing argument to dh_missing, which is now the default. * Update renamed lintian tag names in lintian overrides. * Update standards version to 4.6.1, no changes needed. Checksums-Sha1: 3518cec10eaf508c39a6d4b55c79ef975f2e465c 1896 unworkable_0.53-6.dsc e931afbed73f87962ca0226287b70c03f75bff14 5696 unworkable_0.53-6.debian.tar.xz 87e4d328df519a8f5391790bb4e0a74714014e30 6246 unworkable_0.53-6_source.buildinfo Checksums-Sha256: 757ea5f853e739008b261e91ba8d027fc217b00816d2d74407e819bfaf3bf89e 1896 unworkable_0.53-6.dsc 5fc3374fab4cb81037e5a8b25af3ad5eb9a151677cc61c84098bcc086fb4ab9e 5696 unworkable_0.53-6.debian.tar.xz 76f53d4641fd08c9bb5c19e76c327debd3f82364beff9f0f575fbf0dc08ef98c 6246 unworkable_0.53-6_source.buildinfo Files: feec8164e85bf9acf7bb34bd8453e343 1896 net optional unworkable_0.53-6.dsc edb84c2a9c364a888ebd04528a87 5696 net optional unworkable_0.53-6.debian.tar.xz
Bug#982626: marked as done (autoconf: Ships identical NEWS and NEWS.Debian files)
Your message dated Sun, 17 Mar 2024 23:19:15 + with message-id and subject line Bug#982626: fixed in autoconf 2.72-2 has caused the Debian Bug report #982626, regarding autoconf: Ships identical NEWS and NEWS.Debian files 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.) -- 982626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: autoconf Version: 2.69-14 Severity: normal Hi! This package ships identical NEWS and NEWS.Debian file. This means no upstream NEWS file is shipped, where all new features are described in a concise way. Thanks, Guillem --- End Message --- --- Begin Message --- Source: autoconf Source-Version: 2.72-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of autoconf, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated autoconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Mar 2024 23:51:12 +0100 Source: autoconf Architecture: source Version: 2.72-2 Distribution: experimental Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 977331 982626 Changes: autoconf (2.72-2) experimental; urgency=medium . * Drop debian/NEWS. Thanks Sven Joachim for the patch. (Closes: #982626) * d/control: add Vcs fields. * d/copyright: add myself to debian/ part. * d/rules.old: removed. * Adopt package. (Closes: #977331) Checksums-Sha1: 82728d2bb484ef82c37d11626685ec79c69eb2ed 2062 autoconf_2.72-2.dsc 7bcca02fef8dfe38eb64bc816103f34f0f80443e 22928 autoconf_2.72-2.debian.tar.xz 2810e469c8bbeb80499da978562951f12081f75e 7197 autoconf_2.72-2_source.buildinfo Checksums-Sha256: 4d5a5b18bfd30ec369a8cdb7b0b301b200e7112379f0345acd26363211c0b50b 2062 autoconf_2.72-2.dsc 06d8881bf49906bfe48a101e942493b1cf6b104598e7f6a981f7062aa74bbc96 22928 autoconf_2.72-2.debian.tar.xz b190569ef162996edccf22bf77cedf4c0b1f70a3f1fa80d481f341dbf809b257 7197 autoconf_2.72-2_source.buildinfo Files: f433adcc0cee7f8dfa103f8a831c3bc6 2062 devel optional autoconf_2.72-2.dsc 193f4e80b54518c1fbabc2fa15bdb375 22928 devel optional autoconf_2.72-2.debian.tar.xz 040899ebfd74b6eb96bbdf4940606d41 7197 devel optional autoconf_2.72-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmX3dwYACgkQEWhSvN91 FcBZdhAAgV+Qw/bSzyOHeccq89jMruet3qqufJQTlPpMTIc/Ttu95BPPH17FPTo3 2A67HKw5axnDjOiLTKwJYjnJGJ8ipX7gfcEvNB3G3N8Krmbhg3mS/pLJ8Y0B1m4I 9KOj7ejqhDvqzeMrtTUFJuc4PVQMluQ9ykI++7J0OSQYjHIhRzXQTmKmco9cw8UT 8hj4Hs46BDo2yLhEJxFE71Sb3dbPtUc99cz012qJwDkvAAhHEs+6xB1R/A62Eq2x zw5lHX+GRiDT3ki4pV8MqKiKSXYWBzM2ul0PFypqt3bUs3F0FqilK81IFImn65Ya Lcr92vQx2HwkBD6aGSObHqy2j4IDP8WyQRIUtLDf2764Q4u4k6IroDIrHjZhbx4t mEjFYrrg48a6YCPeU3xU/dSwttTT6kZJ5/7Iu7WV81ZfvkaiZ+f5wOEMMnxtaa0t G5fngFru83gBKMp5/1MmB/QgTqMDkl9dwnkZ1keQFG5vR8yBzyECBjU4aMrjy4Sw GhTWaPtMvoRtyhZ6UcDjq08Tqy5sLeRKNqxo9pMoLBOeV7QCApR30b/xfl5fvyIz 28r2ROFw7teiRm65aY94sHMUAG/1wD9yOURoFB2aeDp8+Sd7pqUrsf6IjaBte8LE e6CzD3JwCHmyKjPaX/J9Z+PjjEvoTPpikPe1na5nXweKITvhgQ0= =LQXY -END PGP SIGNATURE- pgpIKvbh6DZl_.pgp Description: PGP signature --- End Message ---
Bug#1064971: marked as done (libpoco-dev: Package is not multi-arch, first install libpoco-dev:i386, then install libpoco-dev:amd64, and /usr/lib/x86_64-linux-gnu/libPoco*.so survives, but not /usr/li
Your message dated Sun, 17 Mar 2024 21:26:35 + with message-id and subject line Bug#1064971: fixed in poco 1.13.0-6 has caused the Debian Bug report #1064971, regarding libpoco-dev: Package is not multi-arch, first install libpoco-dev:i386, then install libpoco-dev:amd64, and /usr/lib/x86_64-linux-gnu/libPoco*.so survives, but not /usr/lib/i386-linux-gnu/libPoco*.so symlinks 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.) -- 1064971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpoco-dev Version: 1.11.0-3+b1 Severity: important Dear Maintainer, I maintain a docker image with multiple foreign archs, installing libpoco-dev for each arch in sequence causes only the last arch to preserve the undecorated symlinks. libpoco-dev: Package is not multi-arch, first install libpoco-dev:i386, then install libpoco-dev:amd64, and /usr/lib/x86_64-linux-gnu/libPoco*.so survives, but not /usr/lib/i386-linux-gnu/libPoco*.so symlink. The installation script needs to not delete the undecorated symlinks of prior installed libpoco-dev sub packages for another arch. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-17-amd64 (SMP w/16 CPU threads; PREEMPT) 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 libpoco-dev depends on: ii default-libmysqlclient-dev 1.1.0 ii libexpat1-dev 2.5.0-1 ii libpcre3-dev 2:8.39-15 ii libpocoactiverecord80 1.11.0-3+b1 ii libpococrypto80 1.11.0-3+b1 ii libpocodata80 1.11.0-3+b1 ii libpocodatamysql80 1.11.0-3+b1 ii libpocodataodbc80 1.11.0-3+b1 ii libpocodatapostgresql80 1.11.0-3+b1 ii libpocodatasqlite80 1.11.0-3+b1 ii libpocoencodings80 1.11.0-3+b1 ii libpocofoundation80 1.11.0-3+b1 ii libpocojson80 1.11.0-3+b1 ii libpocojwt80 1.11.0-3+b1 ii libpocomongodb80 1.11.0-3+b1 ii libpoconet80 1.11.0-3+b1 ii libpoconetssl80 1.11.0-3+b1 ii libpocoredis80 1.11.0-3+b1 ii libpocoutil80 1.11.0-3+b1 ii libpocoxml80 1.11.0-3+b1 ii libpocozip80 1.11.0-3+b1 ii libsqlite3-dev 3.40.1-2 ii libssl-dev 3.0.11-1~deb12u2 ii zlib1g-dev 1:1.2.13.dfsg-1 libpoco-dev recommends no packages. libpoco-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: poco Source-Version: 1.13.0-6 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of poco, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated poco 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: Sun, 17 Mar 2024 19:41:11 + Source: poco Architecture: source Version: 1.13.0-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 1064971 Changes: poco (1.13.0-6) unstable; urgency=medium . * QA upload * Integrate the 64t NMU * Disclaim libpoco-dev to be MA same (Closes: #1064971) Checksums-Sha1: 7ae48153129eeed924abc2b93e5fc3e04afae59e 3038 poco_1.13.0-6.dsc 2bc4ffe4dd4a5418706001eb7eab4d971661973e 16396 poco_1.13.0-6.debian.tar.xz b6c429719a14569d39a4e296dc6777903c5996e2 7669 poco_1.13.0-6_source.buildinfo Checksums-Sha256: 8b2650e60a87eba964427a4c1f2808a2ee5bd073ca31430c381e5c36cda5a59f 3038 poco_1.13.0-6.dsc d215479914d79392613d5c4fd9df609a72967f31f7fca9a6938d537af674504f 16396 poco_1.13.0-6.debian.tar.xz 807222b556faf0b561b7555917373a99e6b175c53d189fb8c424e1f81acdc19c 7669 poco_1.13.0-6_source.buildinfo Files: 330bc73b55ca2f420ca06e5623ec13dc 3038 libs optional poco_1.13.0-6.dsc f7b4f44c6a6b2638627c4560a8da1b36 16396 libs optional poco_1.13.0-6.debian.tar.xz 50ac821573df914be2649ed2e6451022 7669 libs optional poco_1.13.0-6_source.buildinfo -BEGIN PGP SIGNATURE
Bug#1066752: marked as done (django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" --system=custom "--test-args=PYTHONPATH=. {interpreter} -m pytest" ret
Your message dated Sun, 17 Mar 2024 13:04:23 + with message-id and subject line Bug#1066752: fixed in django-maintenancemode 0.11.7+git221001-4 has caused the Debian Bug report #1066752, regarding django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" --system=custom "--test-args=PYTHONPATH=. {interpreter} -m pytest" returned exit code 13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-maintenancemode Version: 0.11.7+git221001-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- --system=custom --test-args="PYTHONPATH=. {interpreter} -m > pytest" > I: pybuild base:305: PYTHONPATH=. python3.12 -m pytest > = test session starts > == > platform linux -- Python 3.12.2, pytest-8.0.2, pluggy-1.4.0 > django: settings: maintenancemode.tests.settings (from ini) > rootdir: /<> > configfile: setup.cfg > plugins: django-4.5.2 > collected 0 items / 1 error > > ERRORS > > __ ERROR collecting maintenancemode/tests/test_middleware.py > ___ > ImportError while importing test module > '/<>/maintenancemode/tests/test_middleware.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > maintenancemode/tests/test_middleware.py:6: in > from django.utils.six import StringIO > E ModuleNotFoundError: No module named 'django.utils.six' > > During handling of the above exception, another exception occurred: > /usr/lib/python3.12/importlib/__init__.py:90: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > maintenancemode/tests/test_middleware.py:8: in > from six import StringIO > E ModuleNotFoundError: No module named 'six' > === warnings summary > === > ../../../usr/lib/python3/dist-packages/django/conf/__init__.py:241 > /usr/lib/python3/dist-packages/django/conf/__init__.py:241: > RemovedInDjango50Warning: The default value of USE_TZ will change from False > to True in Django 5.0. Set USE_TZ to False in your project settings if you > want to keep the current default behavior. > warnings.warn( > > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html > === short test summary info > > ERROR maintenancemode/tests/test_middleware.py > Interrupted: 1 error during collection > > = 1 warning, 1 error in 0.12s > == > E: pybuild pybuild:389: test: plugin custom failed with: exit code=2: > PYTHONPATH=. python3.12 -m pytest > I: pybuild base:305: PYTHONPATH=. python3.11 -m pytest > = test session starts > == > platform linux -- Python 3.11.8, pytest-8.0.2, pluggy-1.4.0 > django: settings: maintenancemode.tests.settings (from ini) > rootdir: /<> > configfile: setup.cfg > plugins: django-4.5.2 > collected 0 items / 1 error > > ERRORS > > __ ERROR collecting maintenancemode/tests/test_middleware.py > ___ > ImportError while importing test module > '/<>/maintenancemode/tests/test_middleware.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > maintenancemode/tests/test_middleware.py:6: in > from django.utils.six import StringIO > E ModuleNotFoundError: No module named 'django.utils.six' > > During handling of the above exception, another exception occurred: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > maintenancemode/tests/test_middleware.py:8: in > from six import StringIO >
Processed: Bug#1066752 marked as pending in django-maintenancemode
Processing control commands: > tag -1 pending Bug #1066752 [src:django-maintenancemode] django-maintenancemode: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" --system=custom "--test-args=PYTHONPATH=. {interpreter} -m pytest" returned exit code 13 Added tag(s) pending. -- 1066752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1025655 is serious
Processing commands for cont...@bugs.debian.org: > severity 1025655 serious Bug #1025655 [hovercraft] hovercraft: requires python3-setuptools Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066208: marked as done (htdig: FTBFS: os_map.c:87:33: error: implicit declaration of function ‘CDB___db_eopnotsup’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 17:20:05 + with message-id and subject line Bug#1066208: fixed in htdig 1:3.2.0b6-20 has caused the Debian Bug report #1066208, regarding htdig: FTBFS: os_map.c:87:33: error: implicit declaration of function ‘CDB___db_eopnotsup’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: htdig Version: 1:3.2.0b6-19 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc > -DHAVE_CONFIG_H -I. -I./../htlib -D_REENTRANT -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 os_map.lo os_map.c > libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I./../htlib > -D_REENTRANT -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 os_map.c -fPIC -DPIC -o > .libs/os_map.o > os_map.c: In function ‘CDB___os_r_sysattach’: > os_map.c:87:33: error: implicit declaration of function ‘CDB___db_eopnotsup’ > [-Werror=implicit-function-declaration] >87 | return (CDB___db_eopnotsup(dbenv)); > | ^~ > cc1: some warnings being treated as errors > make[3]: *** [Makefile:682: os_map.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/htdig_3.2.0b6-19_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: htdig Source-Version: 1:3.2.0b6-20 Done: Andrey Rakhmatullin 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrey Rakhmatullin (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: SHA512 Format: 1.8 Date: Sat, 16 Mar 2024 21:46:16 +0500 Source: htdig Architecture: source Version: 1:3.2.0b6-20 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andrey Rakhmatullin Closes: 1066208 Changes: htdig (1:3.2.0b6-20) unstable; urgency=medium . * QA upload. * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066208). Checksums-Sha1: 096f50ac6fc1632924deedf7bacc3df8478e61cc 1744 htdig_3.2.0b6-20.dsc 5c0452058afc6a54c97e88fe00d5ae0e7c873c1c 42480 htdig_3.2.0b6-20.debian.tar.xz 698b52583799ec2fd161b92f55bb4996f3ccc8f1 6660 htdig_3.2.0b6-20_amd64.buildinfo Checksums-Sha256: c5fe15bc4e2e7fd2ec834b
Bug#1066341: marked as done (gtkam: FTBFS: gtkam-preview.c:443:17: error: implicit declaration of function ‘gp_setting_set’; did you mean ‘g_settings_set’? [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 17:05:12 + with message-id and subject line Bug#1066341: fixed in gtkam 1.0-4 has caused the Debian Bug report #1066341, regarding gtkam: FTBFS: gtkam-preview.c:443:17: error: implicit declaration of function ‘gp_setting_set’; did you mean ‘g_settings_set’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtkam Version: 1.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2 -I.. -I../src -DLOCALEDIR=\"/usr/share/locale\" > -DAPP_DATADIR=\"/usr/share\" -DIMAGE_DIR=\"/usr/share/images/gtkam\" -Wall > -Wmissing-declarations -Wmissing-prototypes -g -I/usr/include/gtk-2.0 > -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 > -pthread -I/usr/include/gphoto2 -I/usr/include/gtk-2.0 > -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 > -pthread-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 libgtkam_a-gtkam-version.o > `test -f 'gtkam-version.c' || echo './'`gtkam-version.c > gtkam-preview.c: In function ‘download_captured_image’: > gtkam-preview.c:191:9: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' > instead [-Wdeprecated-declarations] > 191 | GTimeVal time; > | ^~~~ > /usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here > 580 | struct _GTimeVal > |^ > gtkam-preview.c:197:9: warning: ‘g_get_current_time’ is deprecated: Use > 'g_get_real_time' instead [-Wdeprecated-declarations] > 197 | g_get_current_time(); > | ^~ > In file included from /usr/include/glib-2.0/glib/giochannel.h:35, > from /usr/include/glib-2.0/glib.h:56: > /usr/include/glib-2.0/glib/gmain.h:728:8: note: declared here > 728 | void g_get_current_time (GTimeVal *result); > |^~ > gtkam-preview.c:199:9: warning: ‘g_time_val_to_iso8601’ is deprecated: Use > 'g_date_time_format' instead [-Wdeprecated-declarations] > 199 | time_s = g_time_val_to_iso8601(); > | ^~ > In file included from /usr/include/glib-2.0/glib.h:92: > /usr/include/glib-2.0/glib/gtimer.h:75:10: note: declared here >75 | gchar* g_time_val_to_iso8601 (GTimeVal*time_) G_GNUC_MALLOC; > | ^ > gtkam-preview.c: In function ‘timeout_func’: > gtkam-preview.c:267:42: warning: pointer targets in passing argument 2 of > ‘gdk_pixbuf_loader_write’ differ in signedness [-Wpointer-sign] > 267 | gdk_pixbuf_loader_write (loader, data, size, NULL); > | ^~~~ > | | > | const char * > In f
Bug#1066496: marked as done (rdiff-backup-fs: FTBFS: gstats.h:44:30: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 16:51:33 + with message-id and subject line Bug#1066496: fixed in rdiff-backup-fs 1.0.0-8 has caused the Debian Bug report #1066496, regarding rdiff-backup-fs: FTBFS: gstats.h:44:30: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdiff-backup-fs Version: 1.0.0-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -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 -Wall -g -O3 -I/usr/include/fuse > -D_FILE_OFFSET_BITS=64 -c -o gutils.o gutils.c > gutils.c: In function ‘gdesccopy’: > gutils.c:9:17: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 9 | write(dest, buffer, result); > | ^~~ > gpath.c: In function ‘gpthcldptr’: > gpath.c:82:5: warning: this ‘for’ clause does not guard... > [-Wmisleading-indentation] >82 | for (; (i >= 0) && (path[i] != '/'); i--); > | ^~~ > gpath.c:83:9: note: ...this statement, but the latter is misleadingly > indented as if it were guarded by the ‘for’ >83 | (*pointer) = path + i + 1; > | ^ > grdiff.c: In function ‘snapshot_copy’: > grdiff.c:305:17: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 305 | write(snapshot_desc, buffer, result); > | ^~~~ > grdiff.c: In function ‘snapshot_append’: > In file included from gtree.h:5, > from gtree.c:3: > gtree.c: In function ‘gtreenew’: > grdiff.c:331:9: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 331 | write(snapshot_desc, buffer, 1); > | ^~~ > gstats.h:44:30: error: implicit declaration of function ‘time’ > [-Werror=implicit-function-declaration] >44 | (stats)->ctime = time(0); \ > | ^~~~ > gtree.c:42:5: note: in expansion of macro ‘set_directory_stats’ >42 | set_directory_stats(stats); > | ^~~ > gtree.c:5:1: note: ‘time’ is defined in header ‘’; did you forget to > ‘#include ’? > 4 | #include "gutils.h" > +++ |+#include > 5 | > grdiff.c:333:17: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 333 | write(snapshot_desc, buffer, result); > | ^~~~ > gtree.c: In function ‘tree_save_node’: > gtree.c:269:9: error: implicit declaration of function ‘asprintf’; did you > mean ‘vsprintf’? [-Werror=implicit-function-declaration] > 269 | asprintf(, "File %s\n", node->stats->internal); > | ^~~~ > | vsprintf > gtree.c:295:9: warning: ignoring return value of ‘write’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 295 | write(desc, result, strlen(result)); > | ^~~ > gstring.c: In function ‘__gstrcat’: > gstring.c:60:5: warning: ‘__builtin_strncpy’ specified bound depends on the > length of the source argument [-Wstringop-truncation] >60 | strncpy((*dest), source, count); > | ^ > In function ‘gstrcpy’, > inlined from ‘gstrcpy’ at gstring.c:67:5, > inlined from ‘__gstrcat’ at gstring.c:23:5: >
Bug#1066648: marked as done (ots: FTBFS: grader-tf.c:108:9: error: implicit declaration of function ‘log’ [-Werror=implicit-function-declaration])
Your message dated Sat, 16 Mar 2024 15:46:42 + with message-id and subject line Bug#1066648: fixed in ots 0.5.0-9 has caused the Debian Bug report #1066648, regarding ots: FTBFS: grader-tf.c:108:9: error: implicit declaration of function ‘log’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ots Version: 0.5.0-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -DVERSION=\"0.5.0\" -DDICTIONARY_DIR=\"/usr/share/ots/\" -I. -I.. -I.. > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/libxml2 -Wall -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 text.lo text.c > dictionary.c: In function ‘ots_load_xml_dictionary’: > dictionary.c:321:40: warning: pointer targets in passing argument 2 of > ‘xmlGetProp’ differ in signedness [-Wpointer-sign] > 321 |idf_key=xmlGetProp(tf_words,"idf"); > |^ > || > |char * > In file included from /usr/include/libxml2/libxml/parser.h:16, > from /usr/include/libxml2/libxml/globals.h:18, > from /usr/include/libxml2/libxml/threads.h:35, > from /usr/include/libxml2/libxml/xmlmemory.h:218, > from dictionary.c:28: > /usr/include/libxml2/libxml/tree.h:1030:57: note: expected ‘const xmlChar *’ > {aka ‘const unsigned char *’} but argument is of type ‘char *’ > 1030 | const xmlChar *name); > | ~~~^~~~ > dictionary.c:322:84: warning: pointer targets in passing argument 1 of ‘atof’ > differ in signedness [-Wpointer-sign] > 322 |Doc->tf_terms = g_list_append > (Doc->tf_terms,ots_new_OtsWordTF(key,atof(idf_key))); > | > ^~~ > | > | > | > xmlChar * {aka unsigned char *} > In file included from /usr/include/features.h:490, > from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from dictionary.c:21: > /usr/include/x86_64-linux-gnu/bits/stdlib-float.h:25:1: note: expected ‘const > char *’ but argument is of type ‘xmlChar *’ {aka ‘unsigned char *’} >25 | __NTH (atof (const char *__nptr)) > | ^ > dictionary.c:322:75: warning: pointer targets in passing argument 1 of > ‘ots_new_OtsWordTF’ differ in signedness [-Wpointer-sign] > 322 |Doc->tf_terms = g_list_append > (Doc->tf_terms,ots_new_OtsWordTF(key,atof(idf_key))); > | > ^~~ > | > | > | > xmlChar * {aka unsigned char *} > In file included from dictionary.c:25: > libots.h:114:43: note: expected ‘const char *’ but argument is of type > ‘xmlChar *’ {aka ‘unsigned char *’} > 114 | OtsWordTF* ots_new_OtsWordTF(const char* word,const double idf); > | ^~~~ > grader-tf.c: In function ‘ots_calc_idf’: > grader-tf.c:108:9: error
Processed: block
Processing commands for cont...@bugs.debian.org: > unblock 1050069 by 1061212 Bug #1050069 [ftp.debian.org] RM: llvm-toolchain-14 -- ROM; Too many version of llvm 1050069 was blocked by: 1061219 1061210 1061209 1061211 1061218 1061212 1061213 1061216 1061215 1061214 1061217 1050069 was not blocking any bugs. Removed blocking bug(s) of 1050069: 1061212 > block 1050070 by 1061212 Bug #1050070 [ftp.debian.org] RM: llvm-toolchain-15 -- ROM; too many llvm version 1050070 was blocked by: 1061205 1061207 1061206 1051680 1061208 1050070 was not blocking any bugs. Added blocking bug(s) of 1050070: 1061212 > End of message, stopping processing here. Please contact me if you need assistance. -- 1050069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050069 1050070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > unarchive 1058653 Bug #1058653 {Done: Rene Engelhard } [libreoffice-writer-nogui] libreoffice-writer-nogui: fails to convert ODT to PDF without libreoffice-core (libcuilo.so): Error: source file could not be loaded Unarchived Bug 1058653 > found 1058653 4:7.6.0~beta1-1 Bug #1058653 {Done: Rene Engelhard } [libreoffice-writer-nogui] libreoffice-writer-nogui: fails to convert ODT to PDF without libreoffice-core (libcuilo.so): Error: source file could not be loaded Marked as found in versions libreoffice/4:7.6.0~beta1-1. > block 1058545 by 1058653 Bug #1058545 [src:esnacc] esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25 1058545 was not blocked by any bugs. 1058545 was not blocking any bugs. Added blocking bug(s) of 1058545: 1058653 > thanks Stopping processing here. Please contact me if you need assistance. -- 1058545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058545 1058653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): due to #1058653
Processing commands for cont...@bugs.debian.org: > block 1058545 by 1058653 Bug #1058545 [src:esnacc] esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25 No valid blocking bug(s) given; not doing anything Failed to set blocking bugs of 1058545: Unknown/archived blocking bug(s):1058653. > tag 1058545 + patch Bug #1058545 [src:esnacc] esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1065767 1066319
Processing commands for cont...@bugs.debian.org: > forcemerge 1065767 1066319 Bug #1065767 [src:libopendbx] libopendbx: FTBFS on arm{el,hf}: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration] Bug #1066319 [src:libopendbx] libopendbx: FTBFS: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration] Merged 1065767 1066319 > thanks Stopping processing here. Please contact me if you need assistance. -- 1065767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065767 1066319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065979: marked as done (nsync: FTBFS on arm{el,hf}: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Fri, 15 Mar 2024 10:10:03 + with message-id and subject line Bug#1065979: fixed in nsync 1.26.0-2 has caused the Debian Bug report #1065979, regarding nsync: FTBFS on arm{el,hf}: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 1065979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nsync Version: 1.26.0-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nsync=armel=1.26.0-1.1=1709541871=0 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libnsync-cpp1t64/DEBIAN/symbols doesn't match completely debian/libnsync-cpp1t64.symbols --- debian/libnsync-cpp1t64.symbols (libnsync-cpp1t64_1.26.0-1.1_armel) +++ dpkg-gensymbolswG9L1v 2024-03-04 08:44:26.711800650 + @@ -24,8 +24,8 @@ _ZN5nsync15nsync_mu_unlockEPNS_11nsync_mu_s_E@Base 1.20.1 _ZN5nsync15nsync_note_freeEPNS_13nsync_note_s_E@Base 1.20.1 _ZN5nsync15nsync_note_waitEPNS_13nsync_note_s_E8timespec@Base 1.20.1 - (arch=!x32)_ZN5nsync15nsync_time_s_nsElj@Base 1.20.1 - (arch=x32)_ZN5nsync15nsync_time_s_nsExj@Base 1.20.1 +#MISSING: 1.26.0-1.1# (arch=!x32)_ZN5nsync15nsync_time_s_nsElj@Base 1.20.1 + _ZN5nsync15nsync_time_s_nsExj@Base 1.20.1 _ZN5nsync15nsync_time_zeroE@Base 1.20.1 _ZN5nsync16nsync_dll_first_EPNS_20nsync_dll_element_s_E@Base 1.20.1 _ZN5nsync16nsync_mu_runlockEPNS_11nsync_mu_s_E@Base 1.20.1 dh_makeshlibs: error: failing due to earlier errors Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: nsync Source-Version: 1.26.0-2 Done: Amin Bandali We believe that the bug you reported is fixed in the latest version of nsync, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Amin Bandali (supplier of updated nsync package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Mar 2024 05:20:28 -0400 Source: nsync Architecture: source Version: 1.26.0-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Amin Bandali Closes: 1065979 Changes: nsync (1.26.0-2) unstable; urgency=medium . * QA upload. * debian/libnsync-cpp1t64.symbols: Update to reflect the 64-bitness of time_t on the relevant arches. (Closes: #1065979) Checksums-Sha1: fff537326b37d1284b2946ad76dbab636d2ff9d5 1976 nsync_1.26.0-2.dsc 89f796f8a3a7a019dacad8207066c87bede5a8d8 155509 nsync_1.26.0.orig.tar.gz 3ac93c9e3ec69cc61a68b18a62fbb028aab48dd6 4104 nsync_1.26.0-2.debian.tar.xz d497cbdd5d4614ac15af4ac8639d870c8935b099 6568 nsync_1.26.0-2_source.buildinfo Checksums-Sha256: 608be094ab3e3f6e1b3abf5b31b08287dde602014e07704c66f22565fc150320 1976 nsync_1.26.0-2.dsc 80fc1e605bb3cf5f272811ece39c4fb6761ffcb9b30563301845cc9ff381eb8b 155509 nsync_1.26.0.orig.tar.gz c6fb9441dea2fe4c397780c5affad260cbb381e29296a49af19dbe2d241ae4ab 4104 nsync_1.26.0-2.debian.tar.xz dc0eb92a6092f9f6d911a82acfae0bfe4c6481fac18205da151ceeed206e3416 6568 nsync_1.26.0-2_source.buildinfo Files: e1c123f4ff2bcd4dd182c319142ba0d8 1976 science optional nsync_1.26.0-2.dsc 35c3515c50ff5086df53cfa16fcb8756 155509 science optional nsync_1.26.0.orig.tar.gz d46accaf0ea436015f92ac62f702127c 4104 science optional nsync_1.26.0-2.debian.tar.xz 91753a3a13943aa7309a93179fc77e99 6568 science optional nsync_1.26.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEObM8jZRIDS3cwqSYi0Sgzce5VvIFAmX0FcUACgkQi0Sgzce5 VvI63hAAnU9aRyDrmVtztrO/V3x3A+xmZxichMoQHZfPq5y8iHSwj8Zrlr79COmS 6Tv+qGOpAt04mGIQl1m6IwfEgXGIpvx0eUvLJXctfOLaephffd7MhzvjYCl/EWiA aMieqhezi3eNM8dZxgEbotU5H5rrI21DlpYEttFgIvSxqJjWqa6664kaoEmGruev 2WVMHQ9XNabhAkR5Wd6tmsoQ6kGj4iRm
Bug#1066420: marked as done (sendmail: FTBFS: ./debian/./debian/conftest.c:37:(.text.startup+0xb): undefined reference to `__res_query')
Your message dated Fri, 15 Mar 2024 01:36:05 + with message-id and subject line Bug#1066420: fixed in sendmail 8.18.1-2 has caused the Debian Bug report #1066420, regarding sendmail: FTBFS: ./debian/./debian/conftest.c:37:(.text.startup+0xb): undefined reference to `__res_query' 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.) -- 1066420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sendmail Version: 8.18.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccO4jMcD.o: in function `main': > ./debian/./debian/conftest.c:37:(.text.startup+0xb): undefined reference to > `__res_query' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/sendmail_8.18.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: sendmail Source-Version: 8.18.1-2 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of sendmail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated sendmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Mar 2024 01:52:07 +0100 Source: sendmail Architecture: source Version: 8.18.1-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1066420 Changes: sendmail (8.18.1-2) unstable; urgency=medium . * QA upload. * Fix building with -Werror=implicit-function-declaration. (Closes: #1066420) Checksums-Sha1: d3191bf8a1f88b48618bb3af8f92f7038395d76d 2819 sendmail_8.18.1-2.dsc 6f280de31dff44bf7d7cb3e145615bfdc4642fdf 247848 sendmail_8.18.1-2.debian.tar.xz 1d335e4fe40114b0b344c0c22aa007939b811787 6682 sendmail_8.18.1-2_source.buildinfo Checksums-Sha256: 40e0063b7f025a7520d64ec0813dab6f025ee091e211054d0daef86903f03c82 2819 sendmail_8.18.1-2.dsc 4c312879ed2083595275e0238c423ecfa398f185c2924b738330899b12099a1e 247848 sendmail_8.18.1-2.debian.tar.xz 3adf0411876d8f530f61db6079b8aeeaa57d280939169a0af1db3c9d620bdf5b 6682 sendmail_8.18.1-2_source.buildinfo Files: 62fd7f37535006b86a29e5a350210bfe 2819 mail optional sendmail_8.18.1-2.dsc d658a0ca44d559f13f714a66b839b3b5 247848 mail optional sendmail_8.18.1-2.debian.tar.xz 9064c81fffa23eb5203f3ef928f3e70d 6682 mail optional sendmail_8.18.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXznToQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCJCWEACQ0jfUsPgtf1Qh14xztXfe4f9JDRX3/Odc dOnyKsPLgW+IpjzT8ranqQ1h8W38aKpHS0lGJDsE11yhtnK+5x6Ya3RPEBkQ6SCT O/Kn3OW+RvjIa09c31o1xInNiqwEdio4YS92Ltzll99Q3OVrAdkurXnP6AGxgXPg ZJMEBGb875hoUMpP0HbPQ3MuygKMKtLUTkATxmh7Ei9HuXSkeyvSR8Kc/6zP7OiF VK/JPbtGLQ0esxXVFP40GnEljNB+JUqyNcUvSOGg9mAVGkXkrVbAGB+RzsLSveTj zxDvQqhoIhn0v9mNL8Q15Z7IMVt4ZIxcNEVohBTyR4KfUwEtIqFRvKZn8BE5J+61 TgDeZTGLSeW+UlPLqWvPvwSgEo/oemC/wDCnMAWHS0QcvPb/pAT5oN39jyjUP4zO 6dYv3Pj6x0U8jaA6uZdAMBC7vzHzZzGLn2nkyOfrybQdKl9o3zmQPktRzuIAzk1L JFrCK8Fcf+j9BKz+ymA/pvzTV30GR3YoWqgCVz5vIGxbs6jfkXcUtr9H/japu/2A UI3emTnEkeg/w/hPbMSVedUODOkmN0Kgj3FHEw4X7rvRnjMlYm0Yuc+2u1j9KZ3
Bug#1066401: marked as done (playmidi: FTBFS: io_gtk.c:19:10: fatal error: gtk/gtk.h: No such file or directory)
Your message dated Thu, 14 Mar 2024 20:45:41 + with message-id and subject line Bug#1066401: fixed in playmidi 2.4debian-14 has caused the Debian Bug report #1066401, regarding playmidi: FTBFS: io_gtk.c:19:10: fatal error: gtk/gtk.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: playmidi Version: 2.4debian-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > for i in *.c; do cc -E -M -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -I/usr/X11R6/include -DNARROWPROTO -I/usr/local/include $i; done >.depend > io_gtk.c:19:10: fatal error: gtk/gtk.h: No such file or directory >19 | #include > | ^~~ > compilation terminated. > io_svgalib.c:17:10: fatal error: vga.h: No such file or directory >17 | #include > | ^~~ > compilation terminated. > rm -f *.o playmidi splaymidi xplaymidi a.out toy seq2mid beat > make[2]: Leaving directory '/<>' > > Successful. Trying to make again > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o playmidi.o playmidi.c > playmidi.c: In function ‘main’: > playmidi.c:558:17: warning: ignoring return value of ‘fgets’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 558 | fgets(temp, sizeof(temp), mfd); /* skip 1st line */ > | ^~ > playmidi.c:559:17: warning: ignoring return value of ‘fgets’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 559 | fgets(temp, sizeof(temp), mfd); > | ^~ > playmidi.c:578:9: warning: ignoring return value of ‘fread’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 578 | fread(filebuf, 1, info.st_size, mfd); > | ^~~~ > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o readmidi.o readmidi.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o playevents.o playevents.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o patchload.o patchload.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o emumidi.o emumidi.c > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -c io_ncurses.c -o io_ncurses.o > cc -Wl,-z,relro -o playmidi playmidi.o readmidi.o playevents.o patchload.o > emumidi.o io_ncurses.o -L/usr/lib -L/usr/lib64 -lncurses > cc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -I/usr/X11R6/include -DNARROWPROTO -c io_xaw.c -o io_xaw.o > cc -Wl,-z,relro -o xplaymidi playmidi.o readmidi.o playevents.o patchload.o > emumidi.o io_xaw.o -L/usr/X11R6/lib -L/usr/X11R6/lib64 -lXaw -lXt -lX11 > make[1]: Leaving directory '/<>' > touch build-stamp > fakeroot debian/rules binary > dh_testdir
Bug#1066464: marked as done (liece: FTBFS: dcc.c:128:7: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration])
Your message dated Thu, 14 Mar 2024 17:05:05 + with message-id and subject line Bug#1066464: fixed in liece 2.0+0.20030527cvs-14 has caused the Debian Bug report #1066464, regarding liece: FTBFS: dcc.c:128:7: error: implicit declaration of function ‘sleep’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liece Version: 2.0+0.20030527cvs-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -I. -I.. -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" > -DPACKAGE=\"liece\" -DVERSION=\"2.0.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 > -DHAVE_SYS_SELECT_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_STRTOUL=1 -DHAVE_MEMMOVE=1 > -DHAVE_GETADDRINFO=1 -DHAVE_BASENAME=1 -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 -c > -o dcc.o dcc.c > dcc.c: In function ‘prepare_listen_port’: > dcc.c:128:7: error: implicit declaration of function ‘sleep’ > [-Werror=implicit-function-declaration] > 128 | sleep (20); /* wait 20 seconds and try again */ > | ^ > dcc.c: In function ‘get_address_externally’: > dcc.c:163:3: error: implicit declaration of function ‘close’; did you mean > ‘pclose’? [-Werror=implicit-function-declaration] > 163 | close(dummy); > | ^ > | pclose > dcc.c: In function ‘send_file’: > dcc.c:189:3: error: implicit declaration of function ‘gethostname’; did you > mean ‘gethostbyname’? [-Werror=implicit-function-declaration] > 189 | gethostname(namebuf, sizeof (namebuf)); > | ^~~ > | gethostbyname > dcc.c:205:34: warning: format ‘%u’ expects argument of type ‘unsigned int’, > but argument 4 has type ‘u_long’ {aka ‘long unsigned int’} [-Wformat=] > 205 | printf ("DCC send %s %d %u %d\n", ifile, port, addr, > statbuf.st_size); > | ~^ > | | | > | unsigned int u_long {aka > long unsigned int} > | %lu > dcc.c:205:37: warning: format ‘%d’ expects argument of type ‘int’, but > argument 5 has type ‘__off_t’ {aka ‘long int’} [-Wformat=] > 205 | printf ("DCC send %s %d %u %d\n", ifile, port, addr, > statbuf.st_size); > |~^ > ~~~ > | | | > | int > __off_t {aka long int} > |%ld > dcc.c:209:17: error: implicit declaration of function ‘read’; did you mean > ‘fread’? [-Werror=implicit-function-declaration] > 209 | while ((len = read (ifd, buf, sizeof (buf))) > 0) { > | ^~~~ > | fread > dcc.c:210:5: error: implicit declaration of function ‘write’; did you mean > ‘fwrite’? [-Werror=implicit-function-declaration] > 210 | write (ofd, buf, len); > | ^ > | fwrite > dcc.c: In function ‘receive_file’: > dcc.c:24
Bug#1066199: marked as done (wv: FTBFS: wvWare.c:1474:40: error: implicit declaration of function ‘strcasecmp’; did you mean ‘g_strcasecmp’? [-Werror=implicit-function-declaration])
Your message dated Thu, 14 Mar 2024 00:20:00 + with message-id and subject line Bug#1066199: fixed in wv 1.2.9-8 has caused the Debian Bug report #1066199, regarding wv: FTBFS: wvWare.c:1474:40: error: implicit declaration of function ‘strcasecmp’; did you mean ‘g_strcasecmp’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wv Version: 1.2.9-7 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -DVERSION=\"1.2.9\" > -DXMLCONFIG=\"/usr/share/wv/wvConfig.xml\" > -DHTMLCONFIG=\"/usr/share/wv/wvHtml.xml\" -DWVDATADIR=\"/usr/share/wv\" -I. > -I. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libgsf-1 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/libxml2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -ansi -MT wvWare.o -MD -MP -MF .deps/wvWare.Tpo -c -o wvWare.o wvWare.c > wvWare.c: In function ‘wvPrintGraphics’: > wvWare.c:1262:19: warning: repeated '-' flag in format [-Wformat=] > 1262 | printf ("\n\\resizebox{%dpt}{%dpt}\ > | ^~~ > 1263 | {\\includegraphics{%s.eps}}\ > | > 1264 | \n% -- %#.2x graphic -- \n", width, height, source, > graphicstype); > | ~~~ > wvWare.c:1262:19: warning: repeated ' ' flag in format [-Wformat=] > wvWare.c:1262:19: warning: conversion lacks type at end of format [-Wformat=] > wvWare.c: In function ‘mySpecCharProc’: > wvWare.c:1474:40: error: implicit declaration of function ‘strcasecmp’; did > you mean ‘g_strcasecmp’? [-Werror=implicit-function-declaration] > 1474 | if ((!message) && (strcasecmp ("UTF-8", charset))) > |^~ > |g_strcasecmp > wvWare.c: In function ‘HandleBitmap’: > wvWare.c:182:18: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 182 | if (ps->dir) chdir (ps->dir); > | ^~~ > wvWare.c:184:18: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 184 | if (ps->dir) chdir (wv_cwd); > | ^~ > wvWare.c: In function ‘HandleMetafile’: > wvWare.c:209:18: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 209 | if (ps->dir) chdir (ps->dir); > | ^~~ > wvWare.c:211:18: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 211 | if (ps->dir) chdir (wv_cwd); > | ^~ > wvWare.c: In function ‘main’: > wvWare.c:410:5: warning: ignoring return value of ‘getcwd’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 410 | getcwd (wv_cwd,4096); > | ^~~~ > wvWare.c: In function ‘mySpecCharProc’: > wvWare.c:1362:34: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1362 | if (ps->dir) chdir (ps->dir); > | ^~~ > wvWare.c:1367:34: warning: ignoring return value of ‘chdir’ declared with > attribute ‘warn_unused_result’ [-Wunused-result] > 1367 | if (ps->dir)
Bug#1066720: marked as done (seyon: FTBFS: SeGeneric.c:222:16: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:25:16 + with message-id and subject line Bug#1066720: fixed in seyon 2.20c-35 has caused the Debian Bug report #1066720, regarding seyon: FTBFS: SeGeneric.c:222:16: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seyon Version: 2.20c-34 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -fcommon -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall > -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE > -D_SVID_SOURCE -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 >-DFUNCPROTO=15 -DNARROWPROTO -Wdate-time -D_FORTIFY_SOURCE=2 > -c -o SeGeneric.o SeGeneric.c > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from SeGeneric.c:12: > /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > SeGeneric.c: In function ‘TtyTimedWaitFor’: > SeGeneric.c:222:16: error: implicit declaration of function ‘time’ > [-Werror=implicit-function-declaration] > 222 | expireTime = time((time_t*)0) + waitTime; > |^~~~ > SeGeneric.c:26:1: note: ‘time’ is defined in header ‘’; did you > forget to ‘#include ’? >25 | #include "SeDecl.h" > +++ |+#include >26 | > cc1: some warnings being treated as errors > make[2]: *** [: SeGeneric.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/seyon_2.20c-34_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: seyon Source-Version: 2.20c-35 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of seyon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated seyon 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, 13 Mar 2024 22:54:54 +0100 Source: seyon Architecture: source Version: 2.20c-35 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes:
Bug#1066516: marked as done (openwince-jtag: FTBFS: flash/cfi.c:84:9: error: implicit declaration of function ‘printf’ [-Werror=implicit-function-declaration])
Your message dated Wed, 13 Mar 2024 23:20:53 + with message-id and subject line Bug#1066516: fixed in openwince-jtag 0.5.1-9 has caused the Debian Bug report #1066516, regarding openwince-jtag: FTBFS: flash/cfi.c:84:9: error: implicit declaration of function ‘printf’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openwince-jtag Version: 0.5.1-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/openwince -I/usr/include/openwince/device > -I/usr/include/openwince/arm -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 -o cfi.o `test -f > 'flash/cfi.c' || echo './'`flash/cfi.c > flash/cfi.c: In function ‘cfi_detect’: > flash/cfi.c:84:9: error: implicit declaration of function ‘printf’ > [-Werror=implicit-function-declaration] >84 | printf("buswidth: %d\n",bw); > | ^~ > flash/cfi.c:38:1: note: include ‘’ or provide a declaration of > ‘printf’ >37 | #include > +++ |+#include >38 | #include > flash/cfi.c:84:9: warning: incompatible implicit declaration of built-in > function ‘printf’ [-Wbuiltin-declaration-mismatch] >84 | printf("buswidth: %d\n",bw); > | ^~ > flash/cfi.c:84:9: note: include ‘’ or provide a declaration of > ‘printf’ > cc1: some warnings being treated as errors > make[5]: *** [Makefile:429: cfi.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/openwince-jtag_0.5.1-8_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: openwince-jtag Source-Version: 0.5.1-9 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of openwince-jtag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated openwince-jtag 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, 13 Mar 2024 23:08:59 +0100 Source: openwince-jtag Architecture: source Version: 0.5.1-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1066516 Changes: openwince-jtag (0.5.1-9) unstable; urgency=medium . * QA upload. * debian/patches: Add missing includes. (Closes: 1066516) Checksums-Sha1: 55f19add9aeb3071b9c4fbe0b365f52d2c1b8cf3 1219 openwince-jtag_0.5.1-9.dsc 5cff1eff7caf7ffc3ae1ab612f0bf6d5b30b7765 4248 openwince-jtag_0.5.1-9.debian.tar.xz e
Processed: db5.3: "build did not include support for sequences"
Processing commands for cont...@bugs.debian.org: > clone 1066003 -1 Bug #1066003 [src:libberkeleydb-perl] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Bug 1066003 cloned as bug 1066394 > reassign -1 src:db5.3 5.3.28+dfsg2-5 Bug #1066394 [src:libberkeleydb-perl] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Bug reassigned from package 'src:libberkeleydb-perl' to 'src:db5.3'. No longer marked as found in versions libberkeleydb-perl/0.64-2. Ignoring request to alter fixed versions of bug #1066394 to the same values previously set Bug #1066394 [src:db5.3] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Marked as found in versions db5.3/5.3.28+dfsg2-5. > retitle -1 db5.3: "build did not include support for sequences" Bug #1066394 [src:db5.3] libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed. Changed Bug title to 'db5.3: "build did not include support for sequences"' from 'libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1066003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066003 1066394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021473 [src:nitpic] nitpic: reproducible-builds: buildid differs in /usr/bin/nitpic Severity set to 'wishlist' from 'normal' -- 1021473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021472 [src:xzoom] xzoom: reproducible-builds: build path embedded in /usr/bin/xzoom Severity set to 'wishlist' from 'normal' -- 1021472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021470 [src:xsok] xsok: reproducible-builds: build path embedded in /usr/games/xsok Severity set to 'wishlist' from 'normal' -- 1021470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021461 [src:icon] icon: reproducible-builds: buildid differences in /usr/bin/icon* Severity set to 'wishlist' from 'normal' -- 1021461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021466 [src:pacman] pacman: reproducible-builds: build path embedded in /usr/games/pacman Severity set to 'wishlist' from 'normal' -- 1021466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021458 [src:o3dgc] o3dgc: reproducible-builds: build path embedded in libo3dgc_common_lib.a Severity set to 'wishlist' from 'normal' -- 1021458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021464 [src:stfl] stfl: reproducible-builds: build path embedded in binaries Severity set to 'wishlist' from 'normal' -- 1021464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021457 [src:olpc-powerd] olpc-powerd: reproducible-builds: build path embedded in debugging symbols Severity set to 'wishlist' from 'normal' -- 1021457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021456 [src:bwbasic] bwbasic: reproducible-builds: build path embedded in /usr/bin/bwbasic Severity set to 'wishlist' from 'normal' -- 1021456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021452 [src:libdv] libdv: reproducible-builds: build path embedded in libdv.so.4.0.3 Severity set to 'wishlist' from 'normal' -- 1021452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020876 [src:yaskkserv] yaskkserv: reproducible-builds: buildid differences in various binaries Severity set to 'wishlist' from 'normal' -- 1020876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020808 [src:powerdebug] powerdebug: reproducible-builds: Embedded build paths in /usr/sbin/powerdebug Severity set to 'wishlist' from 'normal' -- 1020808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020806 [src:perl-byacc] perl-byacc: reproducible-builds: differing buildid in in /usr/bin/pbyacc Severity set to 'wishlist' from 'normal' -- 1020806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1024283 [src:ipsvd] ipsvd: reproducible-builds: buildid differences in various binaries Severity set to 'wishlist' from 'normal' -- 1024283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1024279 [src:tolua++] tolua++: reproducible-builds: build path embedded in tolua++5.1 Severity set to 'wishlist' from 'normal' -- 1024279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1023960 [src:libcgicc] libcgicc: reproducible-builds: build path embedded in /usr/bin/cgicc-config Severity set to 'wishlist' from 'normal' -- 1023960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021509 [src:xxkb] xxkb: reproducible-builds: build path embedded in /usr/bin/xxkb Severity set to 'wishlist' from 'normal' -- 1021509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1021498 [src:tcm] tcm: reproducible-builds: build path embedded in /usr/bin/tcm Severity set to 'wishlist' from 'normal' -- 1021498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1033032 [src:buddy] buddy: reproducible-builds: Embedded build path and usrmerge paths in example Makefile Severity set to 'wishlist' from 'normal' -- 1033032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065713: marked as done (directfb: FTBFS on arm{el,hf}: error: ‘const struct input_event’ has no member named ‘time’)
Your message dated Tue, 12 Mar 2024 00:13:52 + with message-id and subject line Bug#1065713: fixed in directfb 1.7.7-12 has caused the Debian Bug report #1065713, regarding directfb: FTBFS on arm{el,hf}: error: ‘const struct input_event’ has no member named ‘time’ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: directfb Version: 1.7.7-11.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, mwhud...@debian.org https://buildd.debian.org/status/fetch.php?pkg=directfb=armel=1.7.7-11.1=1709087518=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../lib -I../../include -I../../lib -I../../src -I../../systems -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-strict-aliasing -Werror-implicit-function-declaration -O3 -g2 -ffast-math -pipe -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_GNU_SOURCE -std=gnu99 -Werror-implicit-function-declaration -c linux_input.c -fPIC -DPIC -o .libs/linux_input.o linux_input.c: In function ‘translate_event’: linux_input.c:761:28: error: ‘const struct input_event’ has no member named ‘time’ 761 | devt->timestamp = levt->time; |^~ Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: directfb Source-Version: 1.7.7-12 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of directfb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated directfb 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, 11 Mar 2024 22:56:50 +0100 Source: directfb Architecture: source Version: 1.7.7-12 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1065713 Changes: directfb (1.7.7-12) unstable; urgency=medium . * QA upload. * debian/patches: Fix use of input_event (Closes: #1065713) Thanks to Simon McVittie for the hint. Checksums-Sha1: 96001c76e30da517288337bcdd8e463b7cd77c2d 2231 directfb_1.7.7-12.dsc 0bb33e3758aa8223f95ca9eccb688a00c455ad89 27088 directfb_1.7.7-12.debian.tar.xz 6cca27310283064d7b7d86fea3bd22fa455be277 10502 directfb_1.7.7-12_amd64.buildinfo Checksums-Sha256: 719346f8fe9e97a52643e76f1e99ccff955eeb030aa165d2a371358b3d2aac78 2231 directfb_1.7.7-12.dsc 04c13187e77c5d9b30bfc7461881eb3bb476f447b5c623281338fd7c0c755dc3 27088 directfb_1.7.7-12.debian.tar.xz 42a860873ba39dc17bba95ace8b14dfbf8e282605a211cab2293d248f52083a9 10502 directfb_1.7.7-12_amd64.buildinfo Files: dcd856a0b6cc5ab17261c5601ff7caf6 2231 libs optional directfb_1.7.7-12.dsc f6a7ba45f627cab47b09ad48153426bd 27088 libs optional directfb_1.7.7-12.debian.tar.xz 4601007a94392729a0e648a52dc0b512 10502 libs optional directfb_1.7.7-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZe9/rAAKCRAhk2s2YA/N iat/AP9VjNEo4MJxS2kRVQdY9FxTwUdLafW5XOTcPL3KGEolawD/WndF9OQrghx8 /VYAfwMzESbXfnUAZ3mAo/DSa8u3lwQ= =I66r -END PGP SIGNATURE- pgphe7CcJrQR0.pgp Description: PGP signature --- End Message ---
Bug#1065772: marked as done (freewnn: FTBFS on arm{el,hf}:)
Your message dated Sun, 10 Mar 2024 13:13:40 + with message-id and subject line Bug#1065772: fixed in freewnn 1.1.1~a021+cvs20130302-8 has caused the Debian Bug report #1065772, regarding freewnn: FTBFS on arm{el,hf}: 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.) -- 1065772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freewnn Version: 1.1.1~a021+cvs20130302-7.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=freewnn=armel=1.1.1%7Ea021%2Bcvs20130302-7.1=1709116867=0 /bin/bash ../../libtool --mode=compile gcc -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Dlinux -D_GNU_SOURCE -D_POSIX_SOURCE -D_BSD_SOURCE -DHAVE_CONFIG_H -I../../Wnn/include -I../.. -DLIBDIR=\"/usr/share/wnn\" -DJAPANESE -DCHINESE -DKOREAN -DLATIN -DWRITE_CHECK ../../Wnn/etc/`basename bcopy.o .o`.c In file included from js.c:97: ../etc/pwd.c: In function ‘new_pwd’: ../etc/pwd.c:78:7: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration] 78 | x = time (NULL); | ^~~~ ../etc/pwd.c:37:1: note: ‘time’ is defined in header ‘’; did you forget to ‘#include ’? 36 | # include +++ |+#include 37 | #endif js.c: In function ‘js_disconnect’: js.c:982:3: warning: returning ‘void *’ from a function with return type ‘int’ makes integer from pointer without a cast [-Wint-conversion] 982 | handler_of_jserver_dead (NULL); | ^~~ js.c:982:3: warning: returning ‘void *’ from a function with return type ‘int’ makes integer from pointer without a cast [-Wint-conversion] In file included from js.c:96: ../etc/bdic.c: In function ‘check_backup’: ../etc/bdic.c:415:7: warning: ignoring return value of ‘link’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 415 | link (p, n); | ^~~ ../etc/bdic.c: In function ‘make_backup_file’: ../etc/bdic.c:480:3: warning: ignoring return value of ‘link’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 480 | link (p2, p); | ^~~~ ../etc/bdic.c: In function ‘move_tmp_to_org’: ../etc/bdic.c:534:7: warning: ignoring return value of ‘link’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 534 | link (tmp_name, org_name); | ^ jl.c: In function ‘change_ascii_to_int’: jl.c:3079:14: warning: comparison between pointer and integer 3079 | while (*st != NULL) | ^~ jl.c: In function ‘get_pwd’: jl.c:1674:7: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1674 | fgets (pwd, WNN_PASSWD_LEN, fp); | ^~~ jl.c: In function ‘create_file’: libtool: compile: gcc -c -g -O2 -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Dlinux -D_GNU_SOURCE -D_POSIX_SOURCE -D_BSD_SOURCE -DHAVE_CONFIG_H -I../../Wnn/include -I../.. -DLIBDIR=\"/usr/share/wnn\" -DJAPANESE -DCHINESE -DKOREAN -DLATIN -DWRITE_CHECK wnnerrmsg.c -o wnnerrmsg.o >/dev/null 2>&1 jl.c:3167:15: warning: ignoring return value of ‘chown’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 3167 | chown (n + 1, getuid (), -1); /* H.T. */ | ^~~~ jl.c:3219:15: warning: ignoring return value of ‘chown’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 3219 | chown (n + 1, getuid (), -1); | ^~~~ jl.c: In function ‘make_dir1’: jl.c:3312:7: warning: ignoring return value of ‘chown’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 3312 | chown (dirname + 1, getuid (), -1); | ^~ Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: freewnn Source-Version: 1.1.1~a021+cvs20130302-8 Done: Andreas Metzler We believe that the bug you reported is
Bug#1065703: marked as done (t64 transition broke build of other packages)
Your message dated Sat, 09 Mar 2024 11:15:40 + with message-id and subject line Bug#1065703: fixed in libident 0.32-3 has caused the Debian Bug report #1065703, regarding t64 transition broke build of other packages 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.) -- 1065703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libident Severity: serious Tags: patch Version: 0.32-2 X-Debbugs-Cc: by...@debian.org, efing...@packages.debian.org, vor...@debian.org, debian.a...@manchmal.in-ulm.de Control: block 1065100 by -1 Control: block 1065101 by -1 For libident, the t64 transition was done in a slightly different way: Instead of appending t64, the library package was renamed from libident to libident0. While technically being a library transition, the usual steps were obviously not done, especially: Rebuilding the reverse build dependencies to check for possible problems. Instead some bugs were filed against those packages, severity serious. This is at least about: efingerd: #1065100 (maintainer Cc'ed) ngircd: #1065101 (maintained by yours truly) If those test rebuilds had been done, the following error could not have been overseen (for efingerd, likewise ngircd): (...) dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libident.so.0 (used by debian/efingerd/usr/sbin/efingerd) Hint: check if the library actually comes from a package. dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/efingerd.substvars debian/efingerd/usr/sbin/efingerd returned exit code 25 dh_shlibdeps: error: Aborting due to earlier error After spending some hours in the related tooling to understand the root cause without avail, I suggest to modernize src:libident by replacing .shlibs with .symbols. If solves the problem for me, and it's how things should be done anyway. Aside, the change also triggers an "unused-override" from lintian. Christoph diff --git a/debian/libident0.shlibs b/debian/libident0.shlibs deleted file mode 100644 index f0da07c..000 --- a/debian/libident0.shlibs +++ /dev/null @@ -1 +0,0 @@ -libident0 0 libident0 (>= 0.32) diff --git a/debian/libident0.symbols b/debian/libident0.symbols new file mode 100644 index 000..550c842 --- /dev/null +++ b/debian/libident0.symbols @@ -0,0 +1,15 @@ +libident.so.0 libident0 #MINVER# +* Build-Depends-Package: libident-dev + id_close@Base 0.32 + id_open@Base 0.32 + id_open_addr@Base 0.32 + id_parse@Base 0.32 + id_query@Base 0.32 + id_strdup@Base 0.32 + id_strtok@Base 0.32 + id_version@Base 0.32 + ident_free@Base 0.32 + ident_id@Base 0.32 + ident_lookup@Base 0.32 + ident_query@Base 0.32 + ident_query_addr@Base 0.32 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libident Source-Version: 0.32-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libident, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libident package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Mar 2024 11:03:29 +0100 Source: libident Built-For-Profiles: noudeb Architecture: source Version: 0.32-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1065703 Changes: libident (0.32-3) unstable; urgency=medium . * QA upload. . [ Christoph Biedl ] * Replace shlibs with symbols (Closes: #1065703) . [ Sebastiam Ramacher ] * debian: Temporarily stop installing in.identtestd. The daemon should not be part of the shared library package. It will be reintroduced later in a separate binary package. * debian/control: - Remove Suggests: libident-dev from shared library package. - Remove ${shlibs:Depends} from libident-dev - Mark libident0 as MA: same Checksums-Sha1: fdd1eb477f0e9e55a375526d4c7ea02bc1f9db9d 1331 libide
Bug#1065634: marked as done (wv: /usr/share/doc wv is a dangling symlink)
Your message dated Sat, 09 Mar 2024 07:04:43 + with message-id and subject line Bug#1065634: fixed in wv 1.2.9-7 has caused the Debian Bug report #1065634, regarding wv: /usr/share/doc wv is a dangling symlink 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.) -- 1065634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wv Version: 1.2.9-6.1 Severity: serious X-Debbugs-Cc: Sven Joachim , Steve Langasek After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the /usr/share/doc/wv symlink has become dangling. , | $ file /usr/share/doc/wv | /usr/share/doc/wv: broken symbolic link to libwv-1.2-4 ` It should point to libwv-1.2-4t64 instead, obviously. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.81-nouveau (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages wv depends on: ii libc62.37-15.1 ii libglib2.0-0t64 2.78.4-3 ii libgsf-1-114 1.14.51-2 ii libwv-1.2-4t64 1.2.9-6.1 wv recommends no packages. Versions of packages wv suggests: ii elinks 0.16.1.1-4.1+b2 ii ghostscript [postscript-viewer] 10.02.1~dfsg-3 ii imagemagick 8:6.9.12.98+dfsg1-5.1+b1 ii imagemagick-6.q16 [imagemagick] 8:6.9.12.98+dfsg1-5.1+b1 ii lynx 2.9.0rel.0-2 ii okular [postscript-viewer] 4:23.08.1-2 ii texlive 2023.20240207-1 -- no debconf information --- End Message --- --- Begin Message --- Source: wv Source-Version: 1.2.9-7 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of wv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated wv 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, 09 Mar 2024 06:50:23 + Source: wv Architecture: source Version: 1.2.9-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Steve Langasek Closes: 1065634 Changes: wv (1.2.9-7) unstable; urgency=medium . [ Sven Joachim ] * QA upload. * Fix dangling /usr/share/doc symlinks (Closes: #1065634). Checksums-Sha1: f607fea806da9ec3b7b388a8a7531034be870d2a 1987 wv_1.2.9-7.dsc 99d393a1facc57021e3f1b3bac689601c9cbe3d3 13508 wv_1.2.9-7.debian.tar.xz 36a0068ed8ee5d9bacb46144a3c0ed413fc2b936 5932 wv_1.2.9-7_source.buildinfo Checksums-Sha256: ffbfd72adc2105dd3f0871d85a656a51458e49bbfd2bfabd8ea2458ea30343b0 1987 wv_1.2.9-7.dsc a314942da026298af9e33709fffaecd6b92c205de9a6ae824db243087dca650c 13508 wv_1.2.9-7.debian.tar.xz 865b17487ebb969a7003179448659d33933dba8ac68c7e62919a7e08c8f54881 5932 wv_1.2.9-7_source.buildinfo Files: 2fc6b08a886af292768fc5bb1881db68 1987 text optional wv_1.2.9-7.dsc 9f5c130bdcbee4207eedfb5d12e88c3e 13508 text optional wv_1.2.9-7.debian.tar.xz 1dbcab72af3b5406b17835a3c6e8fb41 5932 text optional wv_1.2.9-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXsBsASHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM9JmsP/1Gg3FgTA06NoPvv0KvHVtGMMMY22rT1 o+iSbZmB2L/OedMZXzHSm6+cLREGGDEyDB8ZXE16ZS858aKtfnBQxIxlJ2cgQlkL bhU/vfhe3+iqTGkyycLfCTshLrWJAOYdkd2AztbVWqEwYegInXxbhmXkJQvW5cZP 4MsvUoyCzYKsWBjlxVwkNAN9HdLQZCp92j7XLA5Aq/GwDVlIYc1DeBC2dzMhw778 fnh3pu2Yssxv88O2dCFp4WwfSLNK/l5ZTOvJZKCP61o5LOv75hg2Cvabw9y+3851 Dbd4YSeruBmf9OJUxCWP0lBD1pahnoG6Llhna6bFmUM3Z2wP2ddqcTw6JJ4FRBsD 5wNBtuDeE+cU6ad0MgotsRAzPPyj5OuHOIf5vsMpUE8Rnj/OCwjiuS7MDufDqClG 2j9xGC8UdDMKXYLEbfYeNNOyulvLybnLFrZa/VDuYnuaj2DzVM7o8WA210kfRq0T So0O6MIc5FxA93WrdcxH8aWx2ur9nfIVjscgBxb/vbdc5+fpoTo1bpY3rEV7kiDf UTFdQgIfv0/jphGgzH7Nxrfi0pzmTpSEO40RLlw9mw+GM/xnqUFwUcamavkt9X12 jiNtFk4C1zrVpdeV8GV9n7NQoM9W1OxqPG46DLi9xJJLoLrShrMH3hzWMF0sgiS
Processed: fix ftbfs bug metadata
ign from binary to source > reassign 986494 src:sipxtapi Bug #986494 [sipxtapi] sipxtapi: FTBFS with glibc >= 2.32 Bug reassigned from package 'sipxtapi' to 'src:sipxtapi'. No longer marked as found in versions 3.3.0~test18+dfsg.1-0.1. Ignoring request to alter fixed versions of bug #986494 to the same values previously set > # restore found version after reassign > found 986494 sipxtapi/3.3.0~test18+dfsg.1-0.1 Bug #986494 [src:sipxtapi] sipxtapi: FTBFS with glibc >= 2.32 Marked as found in versions sipxtapi/3.3.0~test18+dfsg.1-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000213 1010533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010533 1014512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014512 1020160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020160 1020185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020185 1051985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051985 1064128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064128 1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 985813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985813 986494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986494 989391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989391 989392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989392 989395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989395 989399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989399 989533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989533 989804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989804 991213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984446: marked as done (CVE-2021-3420)
Your message dated Fri, 08 Mar 2024 07:04:38 + with message-id and subject line Bug#984446: fixed in newlib 4.4.0.20231231-2 has caused the Debian Bug report #984446, regarding CVE-2021-3420 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.) -- 984446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: newlib Severity: important Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2021-3420 and also affects src:newlib: https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=aa106b29a6a8a1b0df9e334704292cbc32f2d44e Cheers, Moritz --- End Message --- --- Begin Message --- Source: newlib Source-Version: 4.4.0.20231231-2 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of newlib, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated newlib 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, 08 Mar 2024 07:19:10 +0100 Source: newlib Architecture: source Version: 4.4.0.20231231-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 984446 1037427 1064733 Changes: newlib (4.4.0.20231231-2) unstable; urgency=medium . * QA upload. * Upload to unstable. . newlib (4.4.0.20231231-1) experimental; urgency=medium . * QA upload. * Orphan package with approval from the current maintainer. . [ Vagrant Cascadian ] * debian/rules: Pass arguments to tar for consistency (Closes: #1037427) . [ Petter Reinholdtsen ] * New upstream version 4.4.0.20231231 - Fixes CVE-2021-3420 (Closes: #984446). - Fixes build problem (Closes: #1064733). * Switched from debhelper compat level 9 to 10 to avoid deprication warning. * Updated to Standards-Version 4.6.2. * Added some metadata to d/patches/ files. Checksums-Sha1: 8b5b776b244a88a82c9be73fac58215f8d5460d9 2275 newlib_4.4.0.20231231-2.dsc 8fd26bb257e735a7016774eda722bcc130174272 13736 newlib_4.4.0.20231231-2.debian.tar.xz dc2af75684038e1368e3f8d109bdd0d7aa7497c9 6970 newlib_4.4.0.20231231-2_source.buildinfo Checksums-Sha256: b5afbf17238a92de3cd710f9766c499bc26c0be5fe903e8e707a91f71a6ef4b2 2275 newlib_4.4.0.20231231-2.dsc 7487340dd0f9a4cb17fed22b16adcf86235b3f81c22b8cf16634bc2cbec19986 13736 newlib_4.4.0.20231231-2.debian.tar.xz dcebb3e6fcdcc381088e3fbebc51cd39eb1201b01d01396a5718dfc277008a46 6970 newlib_4.4.0.20231231-2_source.buildinfo Files: fc3c9757559d09f241d4b90db61c8e94 2275 devel optional newlib_4.4.0.20231231-2.dsc 31d3d55a644f6d45030127722a385411 13736 devel optional newlib_4.4.0.20231231-2.debian.tar.xz 55dcc00dd1b02fd08a4c67220633b289 6970 devel optional newlib_4.4.0.20231231-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmXqsRsACgkQgSgKoIe6 +w4uiw//e/tARvKRc68N+V+UyaV9u93Krs1uNhbwG/ReBhicvzCNaxKAPZxtVYHJ FvVYAHV9zEX+gBsQS3srzP+mM+POuYVckd5zpUz11PbBVkm14tRdDTFmeB4fAUFt nYewUIy3gFq0etmoB9cgi/1qSYsF+nTTr/bPn6dMiLXZa24GL7VhFDnXOKXrhHzI iPu87dIz7zPGCpdCH1TZX9RB5OKbXG5jFGAiiknMcPijecXXPz/Lr2qu6wmyIJQX vuX7tpo+VJv1NLyPVE0lyM7xsI8jJS1ajPFztGfKua8eqOQOyfzFOXwp32SQ7czj Pebr21p2e0E/JsOYMq61Eg8A45wgbMiKQIJgDpYHFS7RH1gUln5BoF9tAVNPK87F 72jlbUai1c1cP1Sv10T8djPa/e+b6Ik+094h6gMKbSFdYTsAI++yc+uHWP0oby6r nWP2MkQvq6uF5B+/3lbiub7uvNAc0c+DkE9JsM93ZHSHG4Gu0MGBAVdeyEE4/O8Z l7REeEe7uB4LLW+d5ZdsLERyhUbShIjmtfqeQVYknxq4tGKqwVLOSXAnwELAzIB3 kTmOMqIkzEnZTGZiu9KnMZRhuzgAgCOCIiK082rlwI3V9ieFBMnSTq+egdnr/Ai5 q9eYyzeyhPRWWlGMRM2g8A5XXsKq7P2VKUTj6Hr0521WLyt6CDU= =WV/G -END PGP SIGNATURE- pgpqT1IsEMI46.pgp Description: PGP signature --- End Message ---
Bug#1037427: marked as done (newlib: reproducible builds: tarball embeds various metadata from build machine)
Your message dated Fri, 08 Mar 2024 07:04:38 + with message-id and subject line Bug#1037427: fixed in newlib 4.4.0.20231231-2 has caused the Debian Bug report #1037427, regarding newlib: reproducible builds: tarball embeds various metadata from build machine 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.) -- 1037427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: newlib Version: 3.3.0-1.3 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: username timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The source tarball /usr/src/newlib/newlib-3.3.0.tar.xz embeds timestamps, file mode, username, userid, groupname and groupid of the build user: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/newlib.html The attached patch fixes this by passing arguments to tar in debian/rules to ensure consistent sort order, timestamps, user, group, uid and gid and file mode in the generated tarball. According to my local tests, with this patch applied newlib should become reproducible on tests.reproducible-builds.org once it migrates to trixie/testing! Unfortunately, other issues (build paths) tested on unstable and experimental are still unresolved. Thanks for maintaining newlib! live well, vagrant From 9bd70cde30f64de8f34902e73768b6224b7526ed Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 9 Jun 2023 20:12:09 -0700 Subject: debian/rules: Pass arguments to tar for consistent sort order, timestamps, user, group and mode. https://reproducible-builds.org/docs/archives/ --- debian/rules | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index c7e4891..c4895fb 100755 --- a/debian/rules +++ b/debian/rules @@ -67,7 +67,12 @@ CONFIGURE_FLAGS_NANO = \ dh $@ -B$(BUILD_DIR) --with autotools-dev --parallel debian/newlib-$(DEB_VERSION_UPSTREAM).tar.xz: - tar -acf $@ --exclude=debian --exclude-vcs --exclude='*.dh-orig' `pwd`/../`basename $(TOP_DIR)` + tar -acf $@ --exclude=debian --exclude-vcs --exclude='*.dh-orig' \ + --sort=name \ + --mtime="@$(SOURCE_DATE_EPOCH)" \ + --owner=0 --group=0 --numeric-owner \ + --mode=go=rX,u+rw,a-s \ + `pwd`/../`basename $(TOP_DIR)` override_dh_clean: dh_clean -- 2.39.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: newlib Source-Version: 4.4.0.20231231-2 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of newlib, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated newlib 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, 08 Mar 2024 07:19:10 +0100 Source: newlib Architecture: source Version: 4.4.0.20231231-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 984446 1037427 1064733 Changes: newlib (4.4.0.20231231-2) unstable; urgency=medium . * QA upload. * Upload to unstable. . newlib (4.4.0.20231231-1) experimental; urgency=medium . * QA upload. * Orphan package with approval from the current maintainer. . [ Vagrant Cascadian ] * debian/rules: Pass arguments to tar for consistency (Closes: #1037427) . [ Petter Reinholdtsen ] * New upstream version 4.4.0.20231231 - Fixes CVE-2021-3420 (Closes: #984446). - Fixes build problem (Closes: #1064733). * Switched from debhelper compat level 9 to 10 to avoid deprication warning. * Updated to Standards-Version 4.6.2. * Added some metadata to d/patches/ files. Checksums-Sha1: 8b5b776b244a88a82c9be73fac58215f8d5460d9 2275 newlib_4.4.0.20231231-2.dsc 8fd26bb257e735a7016774eda722bcc130174272 13736 newlib_4.4.0.20231231-2.debian.tar.xz dc2af75684038e1368e3f8d109bdd0d7aa7497c9 6970 newlib_4.4.0.20231231-2_source.buildinfo Checksums-Sha256: b5afbf17238a92de3cd710f9766c499bc26c0be5fe903e8e707a91f71a6
Processed: Re: Bug#1065634: wv: /usr/share/doc wv is a dangling symlink
Processing control commands: > tags -1 + patch Bug #1065634 [wv] wv: /usr/share/doc wv is a dangling symlink Added tag(s) patch. -- 1065634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1046607: marked as done (tcmu: Fails to build source after successful build)
Your message dated Thu, 07 Mar 2024 17:30:37 + with message-id and subject line Bug#1046607: fixed in tcmu 1.5.4-6 has caused the Debian Bug report #1046607, regarding tcmu: 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.) -- 1046607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcmu Version: 1.5.4-4.1 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 tcmu > dpkg-buildpackage: info: source version 1.5.4-4.1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Cyril Brulebois > dpkg-source --before-build . > debian/rules clean > dh clean >dh_auto_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building tcmu using existing ./tcmu_1.5.4.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > tcmu-1.5.4/logrotate.conf_install.cmake > tcmu-1.5.4/tcmu.conf_install.cmake > tcmu-1.5.4/tcmuhandler-generated.c > tcmu-1.5.4/tcmuhandler-generated.h > tcmu-1.5.4/version.h > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/tcmu_1.5.4-4.1.diff.9rC_aa > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/tcmu_1.5.4-4.1_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: tcmu Source-Version: 1.5.4-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of tcmu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1046...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated tcmu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Mar 2024 17:46:11 +0100 Source: tcmu Architecture: source Version: 1.5.4-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1046607 1053169 Changes: tcmu (1.5.4-6) unstable; urgency=medium . * QA upload. * Restrict librbd-dev build-dependency to 64-bit architectures. (Closes: #1053169) * Clean more generated files. (Closes: #1046607) Checksums-Sha1: 5f910bbdef89d98ab9cfaaaccd71a2cfabefdc90 2055 tcmu_1.5.4-6.dsc 672
Bug#1053169: marked as done (Please remove librbd-dev build-depends on all 32 bits arch)
Your message dated Thu, 07 Mar 2024 17:30:37 + with message-id and subject line Bug#1053169: fixed in tcmu 1.5.4-6 has caused the Debian Bug report #1053169, regarding Please remove librbd-dev build-depends on all 32 bits arch 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.) -- 1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcmu Version: 1.5.4-4.1 Severity: important Hi, I'd like to remove 32 bits support from Ceph, because upstream makes some 64 bits assumptions a bit everywhere, because it's not tested in upstream CI, and because it is increasingly difficult to build Ceph on a smaller addressing footprint (we used to have many tricks to reduce the build footprint that isn't sustainable in the long run). So please remove librbd-dev in build-depends of your package for all 32 bits arch, and remove Ceph support in all 32 bits binaries. I'll upload Ceph with Build-Depends: architecture-is-64-bit as soon as this is done for the 4 affected packages: - fio - libvirt - tcmu - qemu Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Source: tcmu Source-Version: 1.5.4-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of tcmu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated tcmu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Mar 2024 17:46:11 +0100 Source: tcmu Architecture: source Version: 1.5.4-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1046607 1053169 Changes: tcmu (1.5.4-6) unstable; urgency=medium . * QA upload. * Restrict librbd-dev build-dependency to 64-bit architectures. (Closes: #1053169) * Clean more generated files. (Closes: #1046607) Checksums-Sha1: 5f910bbdef89d98ab9cfaaaccd71a2cfabefdc90 2055 tcmu_1.5.4-6.dsc 672887b22bc094c50fc4a219606a73f2d564e17b 7032 tcmu_1.5.4-6.debian.tar.xz 3ba9361d32dec4b5f6b1d4e68a47ec890a85d37a 8367 tcmu_1.5.4-6_source.buildinfo Checksums-Sha256: a2a9ad0801ccc4d36c3ee445326e3b84076c642bc401f42f301b401ae2e030dc 2055 tcmu_1.5.4-6.dsc 68f00ab5994c0296254a180e7166bbbfa7906264eae6a89c3ad57de7141040ff 7032 tcmu_1.5.4-6.debian.tar.xz ad80c370754ee4eb8f97f8e91608b8847caa7e4754121a8d80ab9252dd76095c 8367 tcmu_1.5.4-6_source.buildinfo Files: 58c49cd8c4ece1329443b50c8b8bcbb1 2055 admin optional tcmu_1.5.4-6.dsc c013bfe5e853d2ed1aefedcea785e814 7032 admin optional tcmu_1.5.4-6.debian.tar.xz 4db50bc72d4a8f77180687b4617248b6 8367 admin optional tcmu_1.5.4-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXp8BEQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCG+ND/0WbWflFoAtL0wzPo2gm2Hjt6TKp1CzF/yQ RuwXEaz05nlC1Ris9G5ZJY3S7nVUuUxH9/tByR/U6eYlhxtQV/GPRV4aMqeWVgrK Xyi7h1fguYB6T+MOjXoFtuZFH/R6tewnB9ceC6aXC2Wnc1Ki6VwVfPDHPrV6AjTR mPc6CvPhdlmUCBSlaEFxUDtuITnHVdt7XmGLe+hfRjbuNTjSxhLH/aotp2z8L9lJ II+eZNdhKLchrUxF6p1aeklfYDe+6XHUZYUc8YUhTrm3J9YotQx60LAUU/yb3yGc b8SgnN/I2V6kCpEn0Syn/5Q63YV3qRwYQFqrcoSoEiuate4+6uyu2/Zh8uCUBbec 48GaLwNktqWLDcpFYK/OZkYMvNnKNEWOsN5LHfqz54E502CMtHHm1yBfxDQ2393E 2jC+NILOUgw/SCFPvcu2yqpQDJ+3eJJAv77tmLrVBgspLgzK0qNLqGv1Vgd7kbZW ijew8F0rP/vYtasqHJaKtUOwDSM0WaMlDjeTh7e1DXlgNznJhjkwTARjU7Xuy0mW otHo18+Fy1eOMwvTspkjOaiMQ2uyISHsByxf4JHrv9cm6W3CYNWghvpzuaA4onzA nRDSxhJDsB6ZxMlrwCCj8LKXpwLQdZ3ogVgYE+fH86+XT+gAEEmb/XQaO3b6iKcT XrfuQ+R1AA== =OLoE -END PGP SIGNATURE- pgphygW1R9AG8.pgp Description: PGP signature --- End Message ---
Bug#1065126: marked as done (libelk0t64 has an undeclared file conflict)
Your message dated Tue, 05 Mar 2024 15:34:10 + with message-id and subject line Bug#1065126: fixed in elk 3.99.8-6 has caused the Debian Bug report #1065126, regarding libelk0t64 has an undeclared file conflict 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.) -- 1065126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libelk0t64 Version: 3.99.8-5 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libelk0 libelk0t64 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0 * /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0.0.0 * /usr/lib/x86_64-linux-gnu/libelk-xt.so.0 * /usr/lib/x86_64-linux-gnu/libelk-xt.so.0.0.0 * /usr/lib/x86_64-linux-gnu/libelk.so.0 * /usr/lib/x86_64-linux-gnu/libelk.so.0.0.0 are contained in the packages * libelk0/3.99.8-4.2+b1 as present in bookworm|bullseye|trixie|unstable * libelk0t64/3.99.8-5 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: elk Source-Version: 3.99.8-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of elk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated elk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 05 Mar 2024 16:08:09 +0100 Source: elk Architecture: source Version: 3.99.8-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1065126 Changes: elk (3.99.8-6) unstable; urgency=medium . * QA upload. * Fix Breaks+Replaces for the 64-bit time_t transition. (Closes: #1065126) * Set Rules-Requires-Root: no. Checksums-Sha1: 2d3185a41c9222a948cee70b65d0df6b49ff4ddc 2108 elk_3.99.8-6.dsc e84748903f2cfec702762bf388e9cc3d41cd55b1 8940 elk_3.99.8-6.debian.tar.xz 78d1a002047933302e05192b7f962cdb2fb18fe1 7423 elk_3.99.8-6_source.buildinfo Checksums-Sha256: 4098897c3346fd9c716624e03c6de76929f51736366e5a1edf6ef1f81cbf29d7 2108 elk_3.99.8-6.dsc 9aee532e6db34d523a58f80e2caad2ca224656043990c312040d55c4f76cfa8f 8940 elk_3.99.8-6.debian.tar.xz 1b0e54f33734d9c75dda3a93f102ae6475b08aea93f80a44c1c65412e2df9f0a 7423 elk_3.99.8-6_source.buildinfo Files: 201b56fb95964bd6d5bd6a2ab1738dec 2108 devel optional elk_3.99.8-6.dsc 7f9369b6e403bd31c30375a8652fd288 8940 devel optional elk_3.99.8-6.debian.tar.xz 2ad3740a33d4b50573f1cc444f4868ea 7423 devel optional elk_3.99.8-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXnNdgQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCC78D/9t8WleGNleKjPjoIjr6mwlbD4mTejBdLDB RP7gqNkI0d8Y0oAYfL3d+dIXiGNAASH2QkF6n+D7XtrQhROP+Y9l9eCDgdBOCDoQ sSDon9SRkvsH+bXSBeDObtXiz/Mv/wHDATMJuxhDCwkDOcYoWP1xZJTwYPPtphWl fFfto6If55nOtGJ7nJMuqV8duCvfKJcl1uKE/WBJWWOP/le1oVhCKGWVvBISffd+ I/A9u2jK5c1+hpBA2fE474UOYS1UVUQOZjCtwu73ZZip/Ks4k/tqYDOZiYqbyik5 DkC2yVInQ2oR72h49FqTOOWguxIWd8WUADYO3oXy5Mg5encIIh3bYVXRIvqQXKBC eVd/u97p572Sa5LVSpdzHUNPlc63qAv9Dn8aA3inji16HLgI6SNwioP0A0YoBDet dYshic2G83DJAeApw6qIvcVQd5zsdzB3UrUTrXEWamMDvmIA42a3guBmqLOgLBYy YJa5jiF+jG6ohnNMqvBMftDMukeW8X/Kz6dNs5T14PeuMSYf9NJYjzddB3O5kLzU 0K9C9ntARqemxzE0pP1Ipxq9P7BxeGSfvtjGSKzqR7PaPc8xaCtf2a9gKCRjaXnP Qxe14vr6GYLPg047DGJUDneu2tCShDCMrP91hxdyKJfk+QvFq6oi0QEErR/wgj6u GP4QwNmI8w== =RGHv -END PGP SIGNATURE- pgpmCMkFLRDRq.pgp Description: PGP signature --- End
Processed: unarchiving 1056147, tagging 1065435, tagging 1065486, found 1053196 in 2.0.24-2, tagging 1053195 ...
Processing commands for cont...@bugs.debian.org: > unarchive 1056147 Bug #1056147 {Done: Andreas Beckmann } [src:midge] midge possibly contains non-DFSG-free examples Unarchived Bug 1056147 > tags 1065435 + sid trixie Bug #1065435 [src:aptitude] aptitude: FTBFS on armhf and armel: deduced conflicting types for parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’}) Added tag(s) sid and trixie. > tags 1065486 + sid trixie Bug #1065486 [src:sbd] sbd: FTBFS due to hardcoded libaio SONAME used in dlopen() Added tag(s) trixie and sid. > found 1053196 2.0.24-2 Bug #1053196 [uwsgi] Please remove librados-dev build-depends on all 32 bits arch Marked as found in versions uwsgi/2.0.24-2. > tags 1053195 + sid trixie Bug #1053195 [src:nfs-ganesha] Please remove librados-dev build-depends on all 32 bits arch Added tag(s) trixie and sid. > tags 1053169 + sid trixie Bug #1053169 [src:tcmu] Please remove librbd-dev build-depends on all 32 bits arch Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169 1053195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053195 1053196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053196 1056147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056147 1065435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065435 1065486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062352: marked as done (libgsmme1t64 has an undeclared file conflict)
Your message dated Tue, 5 Mar 2024 15:06:16 +0100 with message-id <9683feb7-5761-62f2-9ee2-0bbe59add...@debian.org> and subject line Re: libgsmme1t64 has an undeclared file conflict has caused the Debian Bug report #1062352, regarding libgsmme1t64 has an undeclared file conflict 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.) -- 1062352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgsmme1t64 Version: 1.10+20120414.gita5e5ae9a-2.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libgsmme1v5 X-Debbugs-Cc: Graham Inggs , vor...@debian.org libgsmme1t64 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libgsmext.so.1 * /usr/lib/x86_64-linux-gnu/libgsmext.so.1.0.4 * /usr/lib/x86_64-linux-gnu/libgsmme.so.1 * /usr/lib/x86_64-linux-gnu/libgsmme.so.1.0.4 are contained in the packages * libgsmme1t64/1.10+20120414.gita5e5ae9a-2.1~exp1 as present in experimental * libgsmme1v5 * 1.10+20120414.gita5e5ae9a-2+b1 as present in bookworm|trixie|unstable * 1.10+20120414.gita5e5ae9a-2~bpo11+1 as present in bullseye-backports These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Version: 1.10+20120414.gita5e5ae9a-3 That seems to be fixed now: Package: libgsmme1t64 Source: gsmlib Version: 1.10+20120414.gita5e5ae9a-3 Installed-Size: 608 Maintainer: Debian QA Group Architecture: amd64 Replaces: libgsmme1c102, libgsmme1c2, libgsmme1c2a, libgsmme1v5 Provides: libgsmme1v5 (= 1.10+20120414.gita5e5ae9a-3) Depends: libc6 (>= 2.33), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1) Conflicts: libgsmme1, libgsmme1c102, libgsmme1c2, libgsmme1c2a Breaks: libgsmme1v5 (<< 1.10+20120414.gita5e5ae9a-3) Andreas--- End Message ---
Bug#1065185: marked as done (zfs-fuse: missing build-dep on libtirpc-dev)
Your message dated Tue, 05 Mar 2024 11:55:10 + with message-id and subject line Bug#1065185: fixed in zfs-fuse 0.7.0-27 has caused the Debian Bug report #1065185, regarding zfs-fuse: missing build-dep on libtirpc-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zfs-fuse Version: 0.7.0-26 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-gl...@lists.debian.org Usertags: libtirpc-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev, which depends on libtirpc-dev, has been added to the libc6-dev package. The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1 NMU, as part of the 64-bit time_t transition. This causes zfs-fuse to FTBFS in sid with: | gcc -o lib/libnvpair/build-user/nvpair.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DNDEBUG -O2 -DLINUX_AIO -Ilib/libnvpair/include -Ilib/libsolcompat/include -I/usr/include/tirpc lib/libnvpair/nvpair.c | lib/libnvpair/nvpair.c:33:10: fatal error: rpc/types.h: No such file or directory |33 | #include | | ^ | compilation terminated. | scons: *** [lib/libnvpair/build-user/nvpair.o] Error 1 | scons: building terminated because of errors. | make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:38: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This could be fixed by adding an explicit Build-Depends on libtirpc-dev. The glibc change will likely be reverted in the short term, but given its a change we want to do for Trixie, this will only lower the severity of the bug. Regards Aurelien --- End Message --- --- Begin Message --- Source: zfs-fuse Source-Version: 0.7.0-27 Done: Andreas Beckmann 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (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: Tue, 05 Mar 2024 12:23:25 +0100 Source: zfs-fuse Architecture: source Version: 0.7.0-27 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1065185 Changes: zfs-fuse (0.7.0-27) unstable; urgency=medium . * QA upload. * Add libtirpc-dev build-dependency. (Closes: #1065185) * Set Rules-Requires-Root: no. * Bump debhelper-compat to 13. * Do not reinvent dh_update_autotools_config etc. Checksums-Sha1: f9c9a866b118f34eb6eb15a8029a73a1294bb35f 2050 zfs-fuse_0.7.0-27.dsc ebd91fb9fddbf1a860ece6b11a152862070301c9 28668 zfs-fuse_0.7.0-27.debian.tar.xz e4ba8cf4451566c164c9675220a00ca3e5a65173 6812 zfs-fuse_0.7.0-27_source.buildinfo Checksums-Sha256: c6e0f75892cdfd08f25e37b082fde9e3a8c038e9a3cc07e05116787a2e0decdb 2050 zfs-fuse_0.7.0-27.dsc ac95ba629198181fe9510d91867148184ea99983992a919799820b537988a56e 28668 zfs-fuse_0.7.0-27.debian.tar.xz f319e317c7dcd118c2759b3f5f7bcc07e572ea19722ec25f77add734f73d0854 6812 zfs-fuse_0.7.0-27_source.buildinfo Files: e7592c0d1a0190e9090ab91c72a431d7 2050 otherosfs optional zfs-fuse_0.7.0-27.dsc 3683067169c59c5813f9c4090f03ecb5 28668 otherosfs optional zfs-fuse_0.7.0-27.debian.tar.xz e90c2988556aab35e6c9fc7e57f7f882 6812 otherosfs optional zfs-fuse_0.7.0-27_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXnAVAQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCC6+EACMNNgihV1VDB2tS5cIiQ5O7Dg4+5OWdiID UWBpXiO9D4lWzn6X5xv6wZMvb7R8E5c2f9ekaDMGcPqeWBEy
Processed: raise bug severity, as Ceph 18.2.1 is now in unstable without 32 bits support
Processing commands for cont...@bugs.debian.org: > severity 1053195 serious Bug #1053195 [src:nfs-ganesha] Please remove librados-dev build-depends on all 32 bits arch Severity set to 'serious' from 'important' > severity 1053169 serious Bug #1053169 [src:tcmu] Please remove librbd-dev build-depends on all 32 bits arch Severity set to 'serious' from 'important' > severity 1053196 serious Bug #1053196 [uwsgi] Please remove librados-dev build-depends on all 32 bits arch Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169 1053195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053195 1053196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1065089 to wnpp, reassign 1065090 to wnpp, notfound 1065069 in apt-move/4.2.27-6+b1 ...
/bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065108 1065109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065109 1065110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065110 1065129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065129 1065160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065160 1065162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065162 1065179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065179 1065182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065182 1065186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063134: marked as done (libquazip: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 12:51:37 + with message-id and subject line Bug#1063134: fixed in libquazip 0.9.1-3.1 has caused the Debian Bug report #1063134, regarding libquazip: NMU diff for 64-bit time_t 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.) -- 1063134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libquazip Version: 0.9.1-3 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified libquazip as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for libquazip which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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) diff -Nru libquazip-0.9.1/debian/changelog libquazip-0.9.1/debian/changelog --- libquazip-0.9.1/debian/changelog2022-11-03 08:46:42.0 + +++ libquazip-0.9.1/debian/changelog2024-02-05 08:02:49.0 + @@ -1,3 +1,11 @@ +libquazip (0.9.1-3.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + * Bump build-dependency on d-shlibs for --t64 support. + + -- Steve Langasek Mon, 05 Feb 2024 08:02:49 + + libquazip (0.9.1-3) unstable; urgency=medium * QA (group) upload diff -Nru libquazip-0.9.1/debian/control libquazip-0.9.1/debian/control --- libquazip-0.9.1/debian/control 2022-11-03 08:46:42.0 + +++ libquazip-0.9.1/debian/control 2024-02-05 08:02:49.0 + @@ -3,7 +3,7 @@ Section: libs Priority: optional Build-Depends: debhelper-compat (= 13), - d-shlibs, + d-shlibs (>= 0.106), cmake, qtbase5-dev, qtchooser, @@ -17,7 +17,7 @@ Homepage: https://github.com/stachenov/quazip Rules-Requires-Root: no -Package: libquazip5-1 +Package: libquazip5-1t64 Architecture: any Multi-Arch: same Section: libs @@ -25,10 +25,11 @@ ${misc:Depends} Suggests: libquazip-doc Pre-Depends: ${misc:Pre-Depends} +Conflicts: libquazip5-1 (<< ${source:Version}) Breaks: libquazip1-qt5 -Provides: libquazip1-qt5, +Provides: ${t64:Provides}, libquazip1-qt5, libquazip-qt5-1 -Replaces: libquazip1-qt5, +Replaces: libquazip5-1, libquazip1-qt5, libquazip-qt5-1 Description: C++ wrapper for ZIP/UNZIP QuaZIP is a simple C++ wrapper over Gilles Vollant's ZIP/UNZIP package that @@ -47,7 +48,7 @@ Architecture: any Multi-Arch: same Section: libdevel -Depends: libquazip5-1 (= ${binary:Version}), +Depends: libquazip5-1t64 (= ${binary:Version}), ${misc:Depends}, zlib1g-dev Breaks: libquazip-qt5-1-dev (<= 0.7-2), diff -Nru libquazip-0.9.1/debian/libquazip5-1.1 libquazip-0.9.1/debian/li
Bug#1063129: marked as done (libmicrohttpd: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 12:37:04 + with message-id and subject line Bug#1063129: fixed in libmicrohttpd 1.0.0-2.1 has caused the Debian Bug report #1063129, regarding libmicrohttpd: NMU diff for 64-bit time_t 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.) -- 1063129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmicrohttpd Version: 1.0.0-1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified libmicrohttpd as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for libmicrohttpd which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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) diff -Nru libmicrohttpd-1.0.0/debian/changelog libmicrohttpd-1.0.0/debian/changelog --- libmicrohttpd-1.0.0/debian/changelog2024-02-03 05:32:37.0 + +++ libmicrohttpd-1.0.0/debian/changelog2024-02-05 07:55:29.0 + @@ -1,3 +1,10 @@ +libmicrohttpd (1.0.0-1.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Steve Langasek Mon, 05 Feb 2024 07:55:29 + + libmicrohttpd (1.0.0-1) sid; urgency=medium * Uploading to sid. diff -Nru libmicrohttpd-1.0.0/debian/control libmicrohttpd-1.0.0/debian/control --- libmicrohttpd-1.0.0/debian/control 2024-02-03 05:31:57.0 + +++ libmicrohttpd-1.0.0/debian/control 2024-02-05 07:55:28.0 + @@ -24,7 +24,7 @@ Multi-arch: same Depends: libgnutls28-dev, - libmicrohttpd12 (= ${binary:Version}), + libmicrohttpd12t64 (= ${binary:Version}), ${misc:Depends}, Description: library embedding HTTP server functionality (development) GNU libmicrohttpd is a small C library that is supposed to make it easy to run @@ -32,7 +32,10 @@ . This package contains the development files. -Package: libmicrohttpd12 +Package: libmicrohttpd12t64 +Provides: ${t64:Provides} +Replaces: libmicrohttpd12 +Breaks: libmicrohttpd12 (<< ${source:Version}) Section: libs Architecture: any Multi-arch: same diff -Nru libmicrohttpd-1.0.0/debian/libmicrohttpd12.install libmicrohttpd-1.0.0/debian/libmicrohttpd12.install --- libmicrohttpd-1.0.0/debian/libmicrohttpd12.install 2024-02-03 05:31:57.0 + +++ libmicrohttpd-1.0.0/debian/libmicrohttpd12.install 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -usr/lib/*/*.so.* diff -Nru libmicrohttpd-1.0.0/debian/libmicrohttpd12.symbols libmicrohttpd-1.0.0/debian/libmicrohttpd12.symbols --- libmicrohttpd-1.0.0/debian/libmicrohttpd12.symbols 2024-02-03 05:31:57.0 + +++ libmicrohttpd-1.0.0/debian/libmicrohttpd12.symbols 1970-01-01 00:00:00.0 + @@ -1,64 +0,0 @@ -libmicroht
Bug#1062399: marked as done (liblip: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 00:06:56 + with message-id and subject line Bug#1062399: fixed in liblip 2.0.0-2.1 has caused the Debian Bug report #1062399, regarding liblip: NMU diff for 64-bit time_t 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.) -- 1062399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblip Version: 2.0.0-2 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified liblip as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for liblip which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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) diff -Nru liblip-2.0.0/debian/changelog liblip-2.0.0/debian/changelog --- liblip-2.0.0/debian/changelog 2023-08-09 15:43:43.0 + +++ liblip-2.0.0/debian/changelog 2024-02-01 09:23:30.0 + @@ -1,3 +1,10 @@ +liblip (2.0.0-2.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Steve Langasek Thu, 01 Feb 2024 09:23:30 + + liblip (2.0.0-2) unstable; urgency=medium * QA upload. diff -Nru liblip-2.0.0/debian/control liblip-2.0.0/debian/control --- liblip-2.0.0/debian/control 2023-08-09 15:43:43.0 + +++ liblip-2.0.0/debian/control 2024-02-01 09:23:30.0 + @@ -6,7 +6,10 @@ Homepage: http://www.deakin.edu.au/~gleb/lip.html Standards-Version: 3.7.2 -Package: liblip2 +Package: liblip2t64 +Provides: ${t64:Provides} +Replaces: liblip2 +Breaks: liblip2 (<< ${source:Version}) Section: libs Priority: optional Architecture: any @@ -59,7 +62,7 @@ Section: libdevel Priority: optional Architecture: any -Depends: ${shlibs:Depends}, libtnt-dev, liblip2 (= ${binary:Version}) +Depends: ${shlibs:Depends}, libtnt-dev, liblip2t64 (= ${binary:Version}) Description: reliable interpolation of multivariate scattered data Lip interpolates scattered multivariate data with a Lipschitz function. . diff -Nru liblip-2.0.0/debian/liblip2t64.lintian-overrides liblip-2.0.0/debian/liblip2t64.lintian-overrides --- liblip-2.0.0/debian/liblip2t64.lintian-overrides1970-01-01 00:00:00.0 + +++ liblip-2.0.0/debian/liblip2t64.lintian-overrides2024-02-01 09:23:30.0 + @@ -0,0 +1 @@ +liblip2t64: package-name-doesnt-match-sonames liblip2 diff -Nru liblip-2.0.0/debian/rules liblip-2.0.0/debian/rules --- liblip-2.0.0/debian/rules 2023-08-09 15:43:43.0 + +++ liblip-2.0.0/debian/rules 2024-02-01 09:23:30.0 + @@ -30,7 +30,7 @@ -rm -f `find . -name "*~"` -rm -rf tnt shared static -rm -rf debian/tmp debian/files* core debian/substvars debian/debhelper.log - -rm -rf debia
Bug#1062851: marked as done (redland: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 23:44:28 + with message-id and subject line Bug#1062851: fixed in redland 1.0.17-3.1 has caused the Debian Bug report #1062851, regarding redland: NMU diff for 64-bit time_t 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.) -- 1062851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: redland Version: 1.0.17-3 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified redland as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for redland which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect diff -Nru redland-1.0.17/debian/changelog redland-1.0.17/debian/changelog --- redland-1.0.17/debian/changelog 2022-11-14 05:03:12.0 + +++ redland-1.0.17/debian/changelog 2024-02-03 20:23:07.0 + @@ -1,3 +1,10 @@ +redland (1.0.17-3.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Sergio Durigan Junior Sat, 03 Feb 2024 20:23:07 + + redland (1.0.17-3) unstable; urgency=medium * QA upload. diff -Nru redland-1.0.17/debian/control redland-1.0.17/debian/control --- redland-1.0.17/debian/control 2022-11-14 04:57:56.0 + +++ redland-1.0.17/debian/control 2024-02-03 20:23:07.0 + @@ -28,7 +28,7 @@ Depends: libraptor2-dev, librasqal3-dev, - librdf0 (= ${binary:Version}), + librdf0t64 (= ${binary:Version}), ${misc:Depends}, Suggests: librdf-perl, librdf-ruby, python-librdf Recommends: redland-utils @@ -36,7 +36,10 @@ RDF development libraries, header files, documentation and utilities needed by program that want to be compiled with Redland. -Package: librdf0 +Package: librdf0t64 +Provides: ${t64:Provides} +Replaces: librdf0 +Breaks: librdf0 (<< ${source:Version}) Section: libs Architecture: any Multi-Arch: same diff -Nru redland-1.0.17/debian/librdf0.install redland-1.0.17/debian/librdf0.install --- redland-1.0.17/debian/librdf0.install 2013-11-12 19:06:26.0 + +++ redland-1.0.17/debian/librdf0.install 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -debian/tmp/usr/lib/*/librdf*.so.* diff -Nru redland-1.0.17/debian/librdf0.manpages redland-1.0.17/debian/librdf0.manpages --- redland-1.0.17/debian/librdf0.manpages 2009-12-17 04:17:33.0 + +++ redland-1.0.17/debian/librdf0.manpages 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -docs/redland.3 diff -Nru redland-1.0.17/debian/librdf0.shlibs redland-1.0.17/debian/librdf0.shlibs --- redland-1.0.17/debian/librdf0.shlibs2013-12-28
Bug#1062771: marked as done (rasqal: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 23:43:59 + with message-id and subject line Bug#1062771: fixed in rasqal 0.9.33-2.1 has caused the Debian Bug report #1062771, regarding rasqal: NMU diff for 64-bit time_t 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.) -- 1062771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rasqal Version: 0.9.33-2 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified rasqal as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for rasqal which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect diff -Nru rasqal-0.9.33/debian/changelog rasqal-0.9.33/debian/changelog --- rasqal-0.9.33/debian/changelog 2023-02-22 16:42:12.0 + +++ rasqal-0.9.33/debian/changelog 2024-02-03 04:26:57.0 + @@ -1,3 +1,10 @@ +rasqal (0.9.33-2.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Sergio Durigan Junior Sat, 03 Feb 2024 04:26:57 + + rasqal (0.9.33-2) unstable; urgency=medium * QA upload. diff -Nru rasqal-0.9.33/debian/control rasqal-0.9.33/debian/control --- rasqal-0.9.33/debian/control2023-02-22 16:41:55.0 + +++ rasqal-0.9.33/debian/control2024-02-03 04:26:56.0 + @@ -16,12 +16,15 @@ Suggests: librasqal3-doc Section: libdevel Architecture: any -Depends: librasqal3 (= ${binary:Version}), libraptor2-dev, libgmp-dev, ${misc:Depends} +Depends: librasqal3t64 (= ${binary:Version}), libraptor2-dev, libgmp-dev, ${misc:Depends} Description: Rasqal RDF query library development libraries and headers Development libraries, header files and documentation needed by programs that want to compile with the Rasqal RDF query library. -Package: librasqal3 +Package: librasqal3t64 +Provides: ${t64:Provides} +Replaces: librasqal3 +Breaks: librasqal3 (<< ${source:Version}) Section: libs Architecture: any Multi-Arch: same diff -Nru rasqal-0.9.33/debian/librasqal3.docs rasqal-0.9.33/debian/librasqal3.docs --- rasqal-0.9.33/debian/librasqal3.docs2022-05-16 17:13:02.0 + +++ rasqal-0.9.33/debian/librasqal3.docs1970-01-01 00:00:00.0 + @@ -1,4 +0,0 @@ -README -NEWS -AUTHORS -NOTICE diff -Nru rasqal-0.9.33/debian/librasqal3.install rasqal-0.9.33/debian/librasqal3.install --- rasqal-0.9.33/debian/librasqal3.install 2022-05-16 17:13:02.0 + +++ rasqal-0.9.33/debian/librasqal3.install 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -debian/tmp/usr/lib/*/librasqal.so.* diff -Nru rasqal-0.9.33/debian/librasqal3.
Processed: libelk0t64 has an undeclared file conflict
Processing control commands: > affects -1 + libelk0 Bug #1065126 [libelk0t64] libelk0t64 has an undeclared file conflict Added indication that 1065126 affects libelk0 -- 1065126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062714: marked as done (qdbm: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 22:07:49 + with message-id and subject line Bug#1062714: fixed in qdbm 1.8.78-12.1 has caused the Debian Bug report #1062714, regarding qdbm: NMU diff for 64-bit time_t 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.) -- 1062714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qdbm Version: 1.8.78-12 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified qdbm as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for qdbm which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect diff -Nru qdbm-1.8.78/debian/changelog qdbm-1.8.78/debian/changelog --- qdbm-1.8.78/debian/changelog2022-11-02 21:02:48.0 + +++ qdbm-1.8.78/debian/changelog2024-02-02 21:46:29.0 + @@ -1,3 +1,10 @@ +qdbm (1.8.78-12.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Sergio Durigan Junior Fri, 02 Feb 2024 21:46:29 + + qdbm (1.8.78-12) unstable; urgency=medium * QA upload. diff -Nru qdbm-1.8.78/debian/control qdbm-1.8.78/debian/control --- qdbm-1.8.78/debian/control 2022-11-02 21:02:48.0 + +++ qdbm-1.8.78/debian/control 2024-02-02 21:46:29.0 + @@ -10,7 +10,10 @@ XS-Ruby-Versions: all Section: libs -Package: libqdbm14 +Package: libqdbm14t64 +Provides: ${t64:Provides} +Replaces: libqdbm14 +Breaks: libqdbm14 (<< ${source:Version}) Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: QDBM Database Libraries without GDBM wrapper[runtime] @@ -32,7 +35,7 @@ Package: libqdbm-dev Section: libdevel Architecture: any -Depends: libqdbm14 (= ${binary:Version}), ${misc:Depends} +Depends: libqdbm14t64 (= ${binary:Version}), ${misc:Depends} Recommends: pkg-config Suggests: qdbm-doc Description: QDBM Database Libraries [development] @@ -57,11 +60,13 @@ Description: QDBM Database CGI commands This is the QDBM Database command package to be used as CGI commands. -Package: libxqdbm3c2 +Package: libxqdbm3t64 +Provides: ${t64:Provides} +X-Time64-Compat: libxqdbm3c2 Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} -Replaces: libqdbm3++c2 (<< 1.8.77-1) -Breaks: libqdbm3++c2 (<< 1.8.77-1) +Replaces: libxqdbm3c2, libqdbm3++c2 (<< 1.8.77-1) +Breaks: libxqdbm3c2 (<< ${source:Version}), libqdbm3++c2 (<< 1.8.77-1) Description: QDBM Database Libraries for C++ [runtime] QDBM is an embedded database library compatible with GDBM and NDBM. It features hash database and B+ tree database and is developed referring @@ -
Bug#1063265: marked as done (poco: NMU diff for 64-bit time_t transition)
Your message dated Thu, 29 Feb 2024 22:04:22 + with message-id and subject line Bug#1063265: fixed in poco 1.11.0-4.1 has caused the Debian Bug report #1063265, regarding poco: NMU diff for 64-bit time_t 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.) -- 1063265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poco Version: 1.11.0-4 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified poco as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for poco which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.2.0-39-generic (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, 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) diff -Nru poco-1.11.0/debian/changelog poco-1.11.0/debian/changelog --- poco-1.11.0/debian/changelog2024-01-16 02:46:36.0 -0300 +++ poco-1.11.0/debian/changelog2024-02-05 19:14:40.0 -0300 @@ -1,3 +1,10 @@ +poco (1.11.0-4.1) experimental; urgency=medium + + * Non-maintainer upload. + * Rename libraries for 64-bit time_t transition. + + -- Lucas Kanashiro Mon, 05 Feb 2024 19:14:40 -0300 + poco (1.11.0-4) unstable; urgency=medium * QA upload. diff -Nru poco-1.11.0/debian/control poco-1.11.0/debian/control --- poco-1.11.0/debian/control 2024-01-16 02:36:47.0 -0300 +++ poco-1.11.0/debian/control 2024-02-05 19:14:40.0 -0300 @@ -22,7 +22,7 @@ Section: libdevel Architecture: any Multi-Arch: same -Depends: ${misc:Depends}, libpocoactiverecord80 (= ${binary:Version}), libpococrypto80 (= ${binary:Version}), libpocodata80 (= ${binary:Version}), libpocoencodings80 (= ${binary:Version}), libpocofoundation80 (= ${binary:Version}), libpocojson80 (= ${binary:Version}), libpocojwt80 (= ${binary:Version}), libpocodatamysql80 (= ${binary:Version}), libpocodatapostgresql80 (= ${binary:Version}), libpocomongodb80 (= ${binary:Version}), libpoconet80 (= ${binary:Version}), libpoconetssl80 (= ${binary:Version}), libpocodataodbc80 (= ${binary:Version}), libpocodatasqlite80 (= ${binary:Version}), libpocoredis80 (= ${binary:Version}), libpocoutil80 (= ${binary:Version}), libpocoxml80 (= ${binary:Version}), libpocozip80 (= ${binary:Version}), libexpat1-dev, default-libmysqlclient-dev, libpcre3-dev, libsqlite3-dev, libssl-dev, zlib1g-dev +Depends: ${misc:Depends}, libpocoactiverecord80t64 (= ${binary:Version}), libpococrypto80t64 (= ${binary:Version}), libpocodata80t64 (= ${binary:Version}), libpocoencodings80t64 (= ${binary:Version}), libpocofoundation80t64 (= ${binary:Version}), libpocojson80t64 (= ${binary:Version}), libpocojwt80t64 (= ${binary:Version}), libpocodatamysql80t64 (= ${binary:Version}), libpocodatapostgresql80t64 (= ${binary:Version