Bug#966655: Orthanc and all its plugins are getting removed from testing
Dear all, Because of the bug #966655 [1], and because of the fact that orthanc-1.7.2+dfsg-2 is pending in the NEW queue [2], I cannot commit the fix regarding the missing build dependency on tzdata until the NEW packages get accepted. But, as #966655 is tagged as serious, the entire Orthanc ecosystem was removed from Debian testing during this week-end. Is there anything I can do to prevent this? Many thanks in advance for your help, Sébastien- [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655 [2] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-July/082973.html
Bug#954189: Upload approval for acmetool 0.2 in buster-backports
Hi Ralph, On Thu, Aug 06, 2020 at 03:38:33PM -0700, Ralph Giles wrote: > I wanted to request approval from the maintainer team to upload the > acmetool 0.2.1-2 package currently in testing/unstable to buster- > backports. Please feel free to go ahead with backporting acmetool and needed golang dependencies to buster. I recently moved the acmetool package to the go-team, which you will need to join on salsa to push to its git repository. Please let me know in case you have any questions. Peter
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
Triggered this with an apt upgrade dist-upgrade APT::Default-Release "buster"; grub-pc 2.02+dfsg1-20+deb10u2 ,.,. This system had mirrored drives - Had to boot off a thumbdrive - enter rescue - when it asked for the boot drive - had to tell it to build raid - then select the raid ( /dev/md0) as the boot drive. There then was a menu item to fix grub - wondered if it worked - so I entered a shell and did an update-grub2 After reboot all was well. I don't know if this will repeat or not? Be kind to the developers - it has been over a decade for a nasty like this to sneak by - which is amazing. Karl Schmidt EMail k...@lrak.net 3209 West 9th Street Ph (785) 979-8397 Lawrence, KS 66049 Politicians are authors of fiction that specialize in the genre of the false narrative. -kps
Processed: bug 966985 is forwarded to https://github.com/mozilla/bleach/issues/543
Processing commands for cont...@bugs.debian.org:
> forwarded 966985 https://github.com/mozilla/bleach/issues/543
Bug #966985 [src:python-bleach] python-bleach: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/mozilla/bleach/issues/543'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-08-10 02:34:03.162662+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # not all bin pkgs are leaf for src:python-pam, lower severity > severity 937996 normal Bug #937996 [src:python-pam] python-pam: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 937996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939259: webcheck: Python2 removal in sid/bullseye
that sounds good, i've opened #968160 to remove webcheck from Debian; it can be re-introduced once its python3 port is completed On Sun, Aug 9, 2020 at 10:10 AM Arthur de Jong wrote: > > On Mon, 2020-07-27 at 00:42 -0400, Sandro Tosi wrote: > > 9 months have passed and i dont see any progress on this porting to > > python3: last commits on https://arthurdejong.org/git/webcheck are > > from 2013 (!) > > > > Are you still interested in this program (which you wrote)? should we > > just remove it from Debian entire? > > Hi Sandro, > > Thanks for the reminder. > > I haven't really found the time to work on webcheck for a while now so > if removing it from Debian makes migration easier that would be fine. > If anyone is willing to help test/port a new version that would be > really welcome though. > > Kind regards, > > -- > -- arthur - adej...@debian.org - https://people.debian.org/~adejong -- > -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#966908: marked as done (mailfilter: FTBFS: rc.tab.c:173:10: fatal error: rc.tab.h: No such file or directory)
Your message dated Mon, 10 Aug 2020 00:18:39 + with message-id and subject line Bug#966908: fixed in mailfilter 0.8.7-1 has caused the Debian Bug report #966908, regarding mailfilter: FTBFS: rc.tab.c:173:10: fatal error: rc.tab.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.) -- 966908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mailfilter Version: 0.8.6-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I. -I../include -I.. > -DLOCALEDIR=\"/usr/share/locale\" -I../intl -I.. -I../include -I. -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o rcparser.o > rcparser.cc > rc.tab.c:173:10: fatal error: rc.tab.h: No such file or directory > compilation terminated. > make[3]: *** [Makefile:462: rcparser.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/mailfilter_0.8.6-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: mailfilter Source-Version: 0.8.7-1 Done: Elimar Riesebieter We believe that the bug you reported is fixed in the latest version of mailfilter, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Elimar Riesebieter (supplier of updated mailfilter 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, 09 Aug 2020 14:13:22 +0200 Source: mailfilter Architecture: source Version: 0.8.7-1 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert Changed-By: Elimar Riesebieter Closes: 966908 Changes: mailfilter (0.8.7-1) unstable; urgency=medium . * Import new upstream version. Thanks upstream for cooperation. (Closes: 966908) * Point watch to github. Create a version 4 watchfile. * Declare compliance with Debian Policy 4.5.0. (No changes needed.) Bump debhelper compatibility level to 13. + Replace debian/compat with a versioned b-d on debhelper-compat. * Added Vcs-(Browser|Git) to d/c. * "Rules-Requires-Root: no" noted in d/c. * Set fileencoding=utf-8 to debian/po/*.po. * Do not use 05-Remove-unused-linking-with-libfl.patch. * Respect autogen.sh via override_dh_autoreconf. * Removed src/rcparser.hh src/rfc822parser.cc src/rfc822parser.hh from copyright. They are no longer distributed. * Added metadata. * 03_fix_invalid_conversion.patch does not to be forwarded. * Introduced 06-Set-fileencoding-to-utf-8-on-AUTHORS-and-THANKS.patch. Checksums-Sha1: 485208a7b8e81e8e6aa78a969468bcad19cafcf3 1944 mailfilter_0.8.7-1.dsc 6fe6f07a98d0a996ed1478ec3b34612b8bab8be5 145589 mailfilter_0.8.7.orig.tar.gz af81a30536dc3901ad30ef2c0566e23e1a5a14ba 15052 mailfilter_0.8.7-1.debian.tar.xz b44649fb33fe8116686785295917badde88283ff 5221 mailfilter_0.8.7-1_source.buildinfo Checksums-Sha256: d26e779ce8279a36337835140e45ea16bbaf1ef13191d96e2b7f1e05409a3944 1944 mailfilter_0.8.7-1.dsc 09ec5285162b6325d34c6c9ca406bf7b21faa422e4218287ed5ac09600882c8a 145589 mailfilter_0.8.7.orig.tar.gz ed4b7b74c2f7b248b217e57d49cd4df08089a91ac9e0f421ddc982240a03f7e6 15052 mailfilter_0.8.7-1.debian.tar.xz ebbc825a71ef1ed4876fa1ab499f837c1085e5a632fc380db9e9869210a3156f 5221 mailfilter_0.8.7-1_source.buildinfo Files: dd6427befd517b95e9a782f30cab4d44 1944 mail optional mailfilter_0.8.7-1.dsc 1d52bf97a442a1686e8071bcfb83defc 145589 mail optional mailfilter_0.8.7.orig.tar.gz
Bug#968157: src:haskell-cborg: testsuite fails due to bus errors on armhf
Package: src:haskell-cborg Version: 0.2.3.0-1 Severity: serious Unlike some other armhf bus errors, this problem does not go away when compiler optimization is disabled.
Bug#963772: marked as done (nodejs breaks node-leveldown autopkgtest: Test: require Aborted)
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-leveldown autopkgtest: Test: require Aborted 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.) -- 966008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs, node-leveldown Control: found -1 nodejs/12.18.0~dfsg-3 Control: found -1 node-leveldown/5.4.1+dfsg-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nodejs the autopkgtest of node-leveldown fails in testing when that autopkgtest is run with the binary packages of nodejs from unstable. It passes when run with only packages from testing. In tabular form: passfail nodejs from testing12.18.0~dfsg-3 node-leveldown from testing5.4.1+dfsg-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of nodejs to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nodejs https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-leveldown/6049319/log.gz autopkgtest [21:35:55]: test pkg-js-autopkgtest-require: [--- Using package.json Node module name is leveldown Test: require Aborted autopkgtest [21:35:55]: test pkg-js-autopkgtest-require: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 14.7.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 00:43:34 +0200 Source: nodejs Architecture: source Version: 14.7.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 966008 967032 968139 Changes: nodejs (14.7.0~dfsg-1) experimental; urgency=medium . * New upstream version 14.7.0~dfsg (Closes: #968139). * Two tests won't pass on IPv6-only hosts * There was no such thing as libnode64-dev, remove it * libnode83 breaks libnode64, libnode72 Closes: #966008 * nodejs-doc: depends node-highlight.js instead of libjs * python3 support (Closes: #967032): + tests/control: depends python3, python3-distutils + python3 patch: use env.PYTHON in two tests + export PYTHON = python3 for Makefile * tests/control: drop cdbs, now useless * Update make-doc.patch to deal with new syntax in esm.md * Refresh patches: + drop mips-fix + drop revert-extra-ca Checksums-Sha1: c940ecaea25f84d0f2b8d4a37cff06d9acd1d97d 3163 nodejs_14.7.0~dfsg-1.dsc 101d84d7f1ee24dfd04ea2a39cab6e75058d5b41 18714280 nodejs_14.7.0~dfsg.orig.tar.xz da111bced73875cdf165f5788499d6f229380b61 133128 nodejs_14.7.0~dfsg-1.debian.tar.xz 7065ce0278b04e3e32f9838ba246089d9e335476 9091 nodejs_14.7.0~dfsg-1_source.buildinfo Checksums-Sha256: eee11378b2c5994d31477ad380829ba0becb525f9ae8dde0d8d1f087f5c66f2b 3163 nodejs_14.7.0~dfsg-1.dsc 2233cd6ae8ef212afb1f697846cecb9d28275b80a985e41abf99d691c2ae2237 18714280 nodejs_14.7.0~dfsg.orig.tar.xz 3760f42249b15a34c99af3831610826bd4371ff6a1ffde84389d0f5d2fee0cc0 133128 nodejs_14.7.0~dfsg-1.debian.tar.xz
Bug#967032: marked as done (nodejs: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#967032: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #967032, regarding nodejs: Unversioned Python removal in sid/bullseye 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.) -- 967032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nodejs Version: 12.18.2~dfsg-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/n/nodejs/6517579/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 14.7.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 00:43:34 +0200 Source: nodejs Architecture: source Version: 14.7.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 966008 967032 968139 Changes: nodejs (14.7.0~dfsg-1) experimental; urgency=medium . * New upstream version 14.7.0~dfsg (Closes: #968139). * Two tests won't pass on IPv6-only hosts * There was no such thing as libnode64-dev, remove it * libnode83 breaks libnode64, libnode72 Closes: #966008 * nodejs-doc: depends node-highlight.js instead of libjs * python3 support (Closes: #967032): + tests/control: depends python3, python3-distutils + python3 patch: use env.PYTHON in two tests + export PYTHON = python3 for Makefile * tests/control: drop cdbs, now useless * Update make-doc.patch to deal with new syntax in esm.md * Refresh patches: + drop mips-fix + drop revert-extra-ca Checksums-Sha1: c940ecaea25f84d0f2b8d4a37cff06d9acd1d97d 3163 nodejs_14.7.0~dfsg-1.dsc 101d84d7f1ee24dfd04ea2a39cab6e75058d5b41 18714280 nodejs_14.7.0~dfsg.orig.tar.xz da111bced73875cdf165f5788499d6f229380b61 133128 nodejs_14.7.0~dfsg-1.debian.tar.xz 7065ce0278b04e3e32f9838ba246089d9e335476 9091 nodejs_14.7.0~dfsg-1_source.buildinfo Checksums-Sha256: eee11378b2c5994d31477ad380829ba0becb525f9ae8dde0d8d1f087f5c66f2b 3163 nodejs_14.7.0~dfsg-1.dsc 2233cd6ae8ef212afb1f697846cecb9d28275b80a985e41abf99d691c2ae2237 18714280 nodejs_14.7.0~dfsg.orig.tar.xz 3760f42249b15a34c99af3831610826bd4371ff6a1ffde84389d0f5d2fee0cc0 133128 nodejs_14.7.0~dfsg-1.debian.tar.xz c88fb0440b63719f148d9d0c770e8d9a55a35334e4d5cbbd2a70d6a9fef7 9091 nodejs_14.7.0~dfsg-1_source.buildinfo Files: 3888d469030bc0e328559b91f41eb32d 3163 javascript optional nodejs_14.7.0~dfsg-1.dsc 65125bf562232cf848013a761c1591bd 18714280 javascript optional nodejs_14.7.0~dfsg.orig.tar.xz 0a3e010be4986c99722cdf7ebd5ab4ee 133128 javascript optional nodejs_14.7.0~dfsg-1.debian.tar.xz 05b0aded48415f2893069bcbccd49b47 9091 javascript optional
Bug#963935: marked as done (node-modern-syslog: missing versioned dependency relation?: modern-syslog/build/Release/core.node',was compiled against a different Node.js version)
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding node-modern-syslog: missing versioned dependency relation?: modern-syslog/build/Release/core.node',was compiled against a different Node.js version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-modern-syslog Version: 1.2.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, nod...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:nodejs Dear maintainer(s), With a recent upload of nodejs the autopkgtest of node-modern-syslog fails in testing when that autopkgtest is run with the binary packages of nodejs from unstable. It passes when run with only packages from testing. In tabular form: passfail nodejs from testing12.18.0~dfsg-3 node-modern-syslog from testing1.2.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Similar to the issues with node-iconv, node-expat and node-node-sass, node-modern-syslog seems to be missing a versioned relation with nodejs. Because of the missing relation, nodejs can be upgraded without the rebuild node-modern-syslog unstable. Currently this regression is blocking the migration of nodejs to testing [1]. Of course, nodejs shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in nodejs was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from nodejs should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nodejs https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-modern-syslog/6061132/log.gz Error: The module '/usr/lib/x86_64-linux-gnu/nodejs/modern-syslog/build/Release/core.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 64. This version of Node.js requires NODE_MODULE_VERSION 72. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`). at Object.Module._extensions..node (internal/modules/cjs/loader.js:1188:18) at Module.load (internal/modules/cjs/loader.js:986:32) at Function.Module._load (internal/modules/cjs/loader.js:879:14) at Module.require (internal/modules/cjs/loader.js:1026:19) at require (internal/modules/cjs/helpers.js:72:18) at Object. (/usr/lib/x86_64-linux-gnu/nodejs/modern-syslog/index.js:9:12) at Module._compile (internal/modules/cjs/loader.js:1138:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10) at Module.load (internal/modules/cjs/loader.js:986:32) at Function.Module._load (internal/modules/cjs/loader.js:879:14) signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 14.7.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 00:43:34 +0200 Source: nodejs Architecture: source Version: 14.7.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript
Bug#966008: marked as done (libnode72 needs Breaks: libnode64)
Your message dated Sun, 09 Aug 2020 23:03:28 +
with message-id
and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1
has caused the Debian Bug report #966008,
regarding libnode72 needs Breaks: libnode64
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.)
--
966008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode72
Severity: serious
For more details see
https://lists.debian.org/debian-devel/2020/07/msg00092.html
The alternative solution of modifying every single reverse dependency
of libnode72 to add nodejs (>= ${nodejs:Depends}) AND adding Breaks:
to nodejs on every single package depending on libnode64 in buster
or bullseye is just more work for achieving less (it wouldn't work
for packages in buster-backports).
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 14.7.0~dfsg-1
Done: =?utf-8?b?SsOpcsOpbXkgTGFs?=
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 10 Aug 2020 00:43:34 +0200
Source: nodejs
Architecture: source
Version: 14.7.0~dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Closes: 966008 967032 968139
Changes:
nodejs (14.7.0~dfsg-1) experimental; urgency=medium
.
* New upstream version 14.7.0~dfsg (Closes: #968139).
* Two tests won't pass on IPv6-only hosts
* There was no such thing as libnode64-dev, remove it
* libnode83 breaks libnode64, libnode72 Closes: #966008
* nodejs-doc: depends node-highlight.js instead of libjs
* python3 support (Closes: #967032):
+ tests/control: depends python3, python3-distutils
+ python3 patch: use env.PYTHON in two tests
+ export PYTHON = python3 for Makefile
* tests/control: drop cdbs, now useless
* Update make-doc.patch to deal with new syntax in esm.md
* Refresh patches:
+ drop mips-fix
+ drop revert-extra-ca
Checksums-Sha1:
c940ecaea25f84d0f2b8d4a37cff06d9acd1d97d 3163 nodejs_14.7.0~dfsg-1.dsc
101d84d7f1ee24dfd04ea2a39cab6e75058d5b41 18714280
nodejs_14.7.0~dfsg.orig.tar.xz
da111bced73875cdf165f5788499d6f229380b61 133128
nodejs_14.7.0~dfsg-1.debian.tar.xz
7065ce0278b04e3e32f9838ba246089d9e335476 9091
nodejs_14.7.0~dfsg-1_source.buildinfo
Checksums-Sha256:
eee11378b2c5994d31477ad380829ba0becb525f9ae8dde0d8d1f087f5c66f2b 3163
nodejs_14.7.0~dfsg-1.dsc
2233cd6ae8ef212afb1f697846cecb9d28275b80a985e41abf99d691c2ae2237 18714280
nodejs_14.7.0~dfsg.orig.tar.xz
3760f42249b15a34c99af3831610826bd4371ff6a1ffde84389d0f5d2fee0cc0 133128
nodejs_14.7.0~dfsg-1.debian.tar.xz
c88fb0440b63719f148d9d0c770e8d9a55a35334e4d5cbbd2a70d6a9fef7 9091
nodejs_14.7.0~dfsg-1_source.buildinfo
Files:
3888d469030bc0e328559b91f41eb32d 3163 javascript optional
nodejs_14.7.0~dfsg-1.dsc
65125bf562232cf848013a761c1591bd 18714280 javascript optional
nodejs_14.7.0~dfsg.orig.tar.xz
0a3e010be4986c99722cdf7ebd5ab4ee 133128 javascript optional
nodejs_14.7.0~dfsg-1.debian.tar.xz
05b0aded48415f2893069bcbccd49b47 9091 javascript optional
nodejs_14.7.0~dfsg-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl8wfDISHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0A0QP/05Ch1DQ6qc1akiflS9X3rnFCgOihiIV
4fyk58pqdgZRQHiovy1aI/xL5xNSIEE09gkvu4T7M7CJkyQQHYVpFeRWXFAkWQg/
LUpv/mC/m0vnnKx0G2i04myVuTaxxr3gTn4getzuL+bWU70Hwlb2UlMTUnrOLAHh
vO9Q8NRy/Tb5yjvT+oex5gozA/pv0Brh8CH2gRqggSrtM3fQdhHNWB/CcJqSCsK0
gURM6F3s54GSPPBGl4EBqx3C855HM+bpds1NsnUPjsdIyxwrJAZQ3tCpYv7ucnY7
aummTfn75AuOVJra6w2AgGjiAAHzbxf0+4KisM/TmMrZ6u3jJSmArnsDHxyWBBUs
CQ9kARQuAYQFQ68DY6lmXiewO5hEo+EOSpxmrD+jGKaBiIHK1yXmx2yrgZ01TkBa
CaHSqWjaa/vEAHfsnQa2qYgZXFUTFkuASqUpCjpCX5ZmT45uEubKxtP9xrnm6rA0
l5F1f1MJg3WHjQVBzwYZFiqA+aqmzFTdRB/FtMeisMD+adFy6biqqxLRbyj7qlRx
5VrXxBrPJ2JZMcdYusL6Te+CupY3Eft+gJL4WB6dXsmUOXDOVz6zoZwzM1Vr5qQX
Bug#963769: marked as done (nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted))
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted) 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.) -- 966008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs, node-iconv-lite Control: found -1 nodejs/12.18.0~dfsg-3 Control: found -1 node-iconv-lite/0.5.1-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nodejs the autopkgtest of node-iconv-lite fails in testing when that autopkgtest is run with the binary packages of nodejs from unstable. It passes when run with only packages from testing. In tabular form: passfail nodejs from testing12.18.0~dfsg-3 node-iconv-litefrom testing0.5.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of nodejs to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nodejs https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-iconv-lite/6049317/log.gz autopkgtest [21:36:16]: test pkg-js-autopkgtest: [--- Using package.json Node module name is iconv-lite # Copy test files Looking at /usr/lib/nodejs/iconv-lite Looking at /usr/lib/*/nodejs/iconv-lite Looking at /usr/share/nodejs/iconv-lite Found /usr/share/nodejs/iconv-lite Linking /usr/share/nodejs/iconv-lite/encodings Linking /usr/share/nodejs/iconv-lite/generation Linking /usr/share/nodejs/iconv-lite/lib Linking /usr/share/nodejs/iconv-lite/node_modules Linking /usr/share/nodejs/iconv-lite/package.json Launch debian/tests/pkg-js/test with sh -ex + mocha --bail --reporter spec --grep . malloc(): invalid next size (unsorted) Aborted autopkgtest [21:36:17]: test pkg-js-autopkgtest: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 14.7.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 00:43:34 +0200 Source: nodejs Architecture: source Version: 14.7.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 966008 967032 968139 Changes: nodejs (14.7.0~dfsg-1) experimental; urgency=medium . * New upstream version 14.7.0~dfsg (Closes: #968139). * Two tests won't pass on IPv6-only hosts * There was no such thing as libnode64-dev, remove it * libnode83 breaks libnode64, libnode72 Closes: #966008 * nodejs-doc: depends node-highlight.js instead of libjs * python3 support (Closes: #967032): + tests/control: depends python3, python3-distutils + python3 patch: use env.PYTHON in two tests + export PYTHON = python3 for Makefile * tests/control: drop cdbs, now useless * Update make-doc.patch to deal with new syntax in esm.md * Refresh patches: + drop mips-fix + drop revert-extra-ca Checksums-Sha1: c940ecaea25f84d0f2b8d4a37cff06d9acd1d97d 3163 nodejs_14.7.0~dfsg-1.dsc 101d84d7f1ee24dfd04ea2a39cab6e75058d5b41 18714280 nodejs_14.7.0~dfsg.orig.tar.xz
Bug#963065: marked as done (nodejs breaks node-encoding autopkgtest: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp'))
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-encoding autopkgtest: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp') 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.) -- 966008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs, node-encoding Control: found -1 nodejs/12.18.0~dfsg-3 Control: found -1 node-encoding/0.1.12-3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nodejs the autopkgtest of node-encoding fails in testing when that autopkgtest is run with the binary packages of nodejs from unstable. It passes when run with only packages from testing. In tabular form: passfail nodejs from testing12.18.0~dfsg-3 node-encoding from testing0.1.12-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of nodejs to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nodejs https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-encoding/5930265/log.gz autopkgtest [00:26:31]: test pkg-js-autopkgtest: [--- Using package.json Node module name is encoding # Copy test files Looking at /usr/lib/nodejs/encoding Looking at /usr/lib/*/nodejs/encoding Looking at /usr/share/nodejs/encoding Found /usr/share/nodejs/encoding Linking /usr/share/nodejs/encoding/lib Linking /usr/share/nodejs/encoding/package.json Launch debian/tests/pkg-js/test with sh -ex + nodeunit test [1mtest[22m [31m✖ General tests - Iconv is available[39m AssertionError: at Object.ok (/usr/lib/nodejs/nodeunit/lib/types.js:83:39) at Object.Iconv is available (/tmp/autopkgtest-lxc.ykcnkdm9/downtmp/autopkgtest_tmp/smokeeIxCcR/test/test.js:9:14) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) at /usr/lib/nodejs/nodeunit/lib/core.js:118:25 at /usr/share/javascript/async/async.js:665:13 at iterate (/usr/share/javascript/async/async.js:149:13) at async.eachSeries (/usr/share/javascript/async/async.js:165:9) (node:14186) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. ✔ General tests - From UTF-8 to Latin_1 with Iconv ✔ General tests - From Latin_1 to UTF-8 with Iconv ✔ General tests - From UTF-8 to UTF-8 with Iconv ✔ General tests - From Latin_13 to Latin_15 with Iconv Error: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp') at Object.getCodec (/usr/share/nodejs/iconv-lite/lib/index.js:106:23) at Object.getDecoder (/usr/share/nodejs/iconv-lite/lib/index.js:127:23) at Object.decode (/usr/share/nodejs/iconv-lite/lib/index.js:40:25) at convertIconvLite (/usr/share/nodejs/encoding/lib/encoding.js:91:26) at Object.convert (/usr/share/nodejs/encoding/lib/encoding.js:51:22) at Object.From ISO-2022-JP to UTF-8 with Iconv (/tmp/autopkgtest-lxc.ykcnkdm9/downtmp/autopkgtest_tmp/smokeeIxCcR/test/test.js:44:33) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) [31m✖ General tests - From ISO-2022-JP to UTF-8 with Iconv[39m AssertionError: deepEqual at Object.deepEqual (/usr/lib/nodejs/nodeunit/lib/types.js:83:39) at Object.From ISO-2022-JP to UTF-8 with Iconv (/tmp/autopkgtest-lxc.ykcnkdm9/downtmp/autopkgtest_tmp/smokeeIxCcR/test/test.js:44:14) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
Bug#967017: marked as done (request-tracker4: FTBFS: GPG test failures)
Your message dated Sun, 09 Aug 2020 22:33:58 + with message-id and subject line Bug#967017: fixed in request-tracker4 4.4.4-2 has caused the Debian Bug report #967017, regarding request-tracker4: FTBFS: GPG test failures 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.) -- 967017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: request-tracker4 Version: 4.4.4-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > /usr/bin/perl ./sbin/rt-test-dependencies --with-SQLite --with-fastcgi > perl: > >=5.10.1(5.30.3) ...found > users: > rt group (user42) ...found > bin owner (user42) ...found > libs owner (user42) ...found > libs group (user42) ...found > web owner (user42) ...found > web group (user42) ...found > CLI dependencies: > Getopt::Long >= 2.24 ...found > HTTP::Request::Common ...found > LWP >= 6.02 ...found > Term::ReadLine ...found > Term::ReadKey ...found > Text::ParseWords ...found > CORE dependencies: > CGI >= 4 ...found > Convert::Color ...found > URI::QueryParam ...found > File::Glob ...found > Text::Quoted >= 2.07 ...found > HTML::FormatText::WithLinks::AndTables >= 0.06 ...found > Role::Basic >= 0.12 ...found > Scope::Upper ...found > MIME::Types ...found > HTML::Mason >= 1.43 ...found > IPC::Run3 ...found > File::Temp >= 0.19 ...found > Tree::Simple >= 1.04 ...found > Text::Wrapper ...found > Email::Address >= 1.912 ...found > Plack >= 1.0002 ...found > Storable >= 2.08 ...found > DateTime::Format::Natural >= 0.67 ...found > Data::Page::Pageset ...found > Regexp::Common::net::CIDR ...found > UNIVERSAL::require ...found > Mail::Mailer >= 1.57 ...found > Date::Extract >= 0.02 ...found > Errno ...found > HTML::Quoted ...found > Crypt::Eksblowfish ...found > CGI::Emulate::PSGI ...found > Locale::Maketext >= 1.06 ...found > Devel::StackTrace >= 1.19 ...found > CGI::Cookie >= 1.20 ...found > Log::Dispatch >= 2.30 ...found > HTML::Entities ...found > HTTP::Message >= 6.0 ...found > Text::Template >= 1.44 ...found > Digest::base ...found > Regexp::IPv6 ...found > HTML::Scrubber >= 0.08 ...found > Plack::Handler::Starlet ...MISSING > LWP::Simple ...found > Text::WikiFormat >= 0.76 ...found > Apache::Session >= 1.53 ...found > Net::CIDR ...found > XML::RSS >= 1.05 ...found > CSS::Squish >= 0.06 ...found > Encode >= 2.64 ...found > DateTime >= 0.44 ...found > Data::ICal ...found > Data::GUID ...found > Module::Refresh >= 0.03 ...found > File::ShareDir ...found > Symbol::Global::Name >= 0.05 ...found > JSON ...found > DBIx::SearchBuilder >= 1.65 ...found > Business::Hours ...found > Pod::Select ...found > List::MoreUtils ...found > Locale::Maketext::Fuzzy >= 0.11 ...found > Class::Accessor::Fast ...found > Regexp::Common ...found > Date::Manip ...found > Locale::Maketext::Lexicon >= 0.32 ...found > MIME::Entity >= 5.504 ...found > Module::Versions::Report >= 1.05 ...found > Email::Address::List >= 0.06 ...found > URI >= 1.59 ...found > Text::Password::Pronounceable ...found > Mail::Header >= 2.12 ...found > Time::HiRes ...found > Sys::Syslog >= 0.16 ...found > Devel::GlobalDestruction ...found > CSS::Minifier::XS ...found > HTML::FormatText::WithLinks >= 0.14 ...found > Clone ...found > DateTime::Locale >= 0.40 ...found > HTML::RewriteAttributes >= 0.05 ...found > JavaScript::Minifier::XS ...found > Time::ParseDate ...found > Digest::MD5 >= 2.27 ...found > File::Spec >= 0.8 ...found > CGI::PSGI >= 0.12 ...found > Net::IP ...found > Scalar::Util ...found > HTML::Mason::PSGIHandler >= 0.52 ...found > DBI >= 1.37 ...found > Digest::SHA ...found > DEVELOPER dependencies: > Test::Email ...found > Test::Warn ...found > Test::NoWarnings ...found > Plack::Middleware::Test::StashWarnings >= 0.08 ...found >
Processed: hardinfo: diff for NMU version 0.5.1+git20180227-2.1
Processing control commands: > tags 957327 + patch Bug #957327 [src:hardinfo] hardinfo: ftbfs with GCC-10 Added tag(s) patch. > tags 957327 + pending Bug #957327 [src:hardinfo] hardinfo: ftbfs with GCC-10 Added tag(s) pending. -- 957327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957327: hardinfo: diff for NMU version 0.5.1+git20180227-2.1
Control: tags 957327 + patch
Control: tags 957327 + pending
Dear maintainer,
I've prepared an NMU for hardinfo (versioned as 0.5.1+git20180227-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru hardinfo-0.5.1+git20180227/debian/changelog
hardinfo-0.5.1+git20180227/debian/changelog
--- hardinfo-0.5.1+git20180227/debian/changelog 2018-12-24 05:56:13.0
+
+++ hardinfo-0.5.1+git20180227/debian/changelog 2020-08-09 22:16:41.0
+0100
@@ -1,3 +1,10 @@
+hardinfo (0.5.1+git20180227-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-10. (Closes: #957327)
+
+ -- Sudip Mukherjee Sun, 09 Aug 2020 22:16:41
+0100
+
hardinfo (0.5.1+git20180227-2) unstable; urgency=medium
* Change my email to tsimo...@debian.org now that I am a Debian Developer.
diff -Nru hardinfo-0.5.1+git20180227/debian/patches/fix_ftbfs.patch
hardinfo-0.5.1+git20180227/debian/patches/fix_ftbfs.patch
--- hardinfo-0.5.1+git20180227/debian/patches/fix_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ hardinfo-0.5.1+git20180227/debian/patches/fix_ftbfs.patch 2020-08-09
22:16:03.0 +0100
@@ -0,0 +1,29 @@
+Description: Fix ftbfs with GCC-10
+ The enum variable is not used, use that as the enum name to declare it.
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/957327
+Forwarded: no
+
+---
+
+--- hardinfo-0.5.1+git20180227.orig/includes/benchmark.h
hardinfo-0.5.1+git20180227/includes/benchmark.h
+@@ -5,7 +5,7 @@
+
+ extern ProgramParameters params;
+
+-enum {
++enum BenchmarkEntries {
+ BENCHMARK_BLOWFISH,
+ BENCHMARK_CRYPTOHASH,
+ BENCHMARK_FIB,
+@@ -15,7 +15,7 @@ enum {
+ BENCHMARK_RAYTRACE,
+ BENCHMARK_GUI,
+ BENCHMARK_N_ENTRIES
+-} BenchmarkEntries;
++};
+
+ void benchmark_bfish(void);
+ void benchmark_cryptohash(void);
diff -Nru hardinfo-0.5.1+git20180227/debian/patches/series
hardinfo-0.5.1+git20180227/debian/patches/series
--- hardinfo-0.5.1+git20180227/debian/patches/series1970-01-01
01:00:00.0 +0100
+++ hardinfo-0.5.1+git20180227/debian/patches/series2020-08-09
22:00:12.0 +0100
@@ -0,0 +1 @@
+fix_ftbfs.patch
Bug#957981: marked as done (xgammon: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 21:03:35 + with message-id and subject line Bug#957981: fixed in xgammon 0.99.1128-4 has caused the Debian Bug report #957981, regarding xgammon: ftbfs with GCC-10 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.) -- 957981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xgammon Version: 0.99.1128-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/xgammon_0.99.1128-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: decision.o:/<>/src/gammon.h:140: multiple definition of `possible_moves'; allow.o:/<>/src/gammon.h:140: first defined here /usr/bin/ld: decision.o:/<>/src/gammon.h:125: multiple definition of `rollout_position'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:125: multiple definition of `Pin'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:120: multiple definition of `Player'; allow.o:/<>/src/gammon.h:120: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:163: multiple definition of `endgame_database'; allow.o:/<>/src/gammon.h:163: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:161: multiple definition of `rollout_save'; allow.o:/<>/src/gammon.h:161: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:154: multiple definition of `tournament'; allow.o:/<>/src/gammon.h:154: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:140: multiple definition of `list'; allow.o:/<>/src/gammon.h:140: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:140: multiple definition of `possible_moves'; allow.o:/<>/src/gammon.h:140: first defined here /usr/bin/ld: edit.o:/<>/src/gammon.h:125: multiple definition of `rollout_position'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: edit.o:/<>/src/xgammon.h:73: multiple definition of `gammon_resource'; drawing.o:/<>/src/xgammon.h:73: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:120: multiple definition of `Player'; allow.o:/<>/src/gammon.h:120: first defined here /usr/bin/ld: misc.o:/<>/src/xgammon.h:73: multiple definition of `gammon_resource'; drawing.o:/<>/src/xgammon.h:73: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:125: multiple definition of `Pin'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:154: multiple definition of `tournament'; allow.o:/<>/src/gammon.h:154: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:140: multiple definition of `possible_moves'; allow.o:/<>/src/gammon.h:140: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:140: multiple definition of `list'; allow.o:/<>/src/gammon.h:140: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:163: multiple definition of `endgame_database'; allow.o:/<>/src/gammon.h:163: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:161: multiple definition of `rollout_save'; allow.o:/<>/src/gammon.h:161: first defined here /usr/bin/ld: misc.o:/<>/src/gammon.h:125: multiple definition of `rollout_position'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: save.o:/<>/src/gammon.h:125: multiple definition of `Pin'; allow.o:/<>/src/gammon.h:125: first defined here /usr/bin/ld: save.o:/<>/src/xgammon.h:73: multiple definition of `gammon_resource'; drawing.o:/<>/src/xgammon.h:73: first defined here /usr/bin/ld:
Bug#943302: zsnapd: Python2 removal in sid/bullseye
Followup-For: Bug #943302 Control: found -1 0.8.11h-2 zsnapd FTBFS in a minimal up-to-date sid chroot due to some more changes in the python ecosystem: fakeroot debian/rules clean dh clean dh_auto_clean dh_auto_clean: warning: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_clean: warning: This feature will be removed in compat 12. Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. dh_auto_clean: error: failed to run pyversions make: *** [debian/rules:14: clean] Error 25 Andreas
Processed: Re: zsnapd: Python2 removal in sid/bullseye
Processing control commands:
> found -1 0.8.11h-2
Bug #943302 {Done: Matthew Grant } [src:zsnapd] zsnapd:
Python2 removal in sid/bullseye
Marked as found in versions zsnapd/0.8.11h-2; no longer marked as fixed in
versions zsnapd/0.8.11h-2 and reopened.
--
943302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966653: gitlab: [BUG] Segmentation fault at 0x0000000000000000
I got bitten by the same crash during a system upgrade from Buster 10.4 to Buster 10.5, on a system using the Buster Fasttrack repositories. Reverting the older versions of the following packages allowed me to avoid the crash: - ruby-google-protobuf:amd64=3.11.4-5+fto10+1 - ruby-grpc:amd64=1.26.0-3+fto10+1 So the following command might help work around it for people that get this crash on a Debian Buster: apt install ruby-google-protobuf:amd64=3.11.4-5+fto10+1 ruby-grpc:amd64=1.26.0-3+fto10+1 I use no instance of GitLab on Bullseye/Sid, so sadly I am not able to run tests in this context.
Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id
Package: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym Version: 8.0.20-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package mysql-server-core-8.0-dbgsym. Preparing to unpack .../mysql-server-core-8.0-dbgsym_8.0.20-1~exp1_amd64.deb ... Unpacking mysql-server-core-8.0-dbgsym (8.0.20-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/mysql-server-core-8.0-dbgsym_8.0.20-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/.build-id/7f/f600335ee6385a37d764bd373780917736d638.debug', which is also in package mysql-router-dbgsym 8.0.20-1~exp1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mysql-server-core-8.0-dbgsym_8.0.20-1~exp1_amd64.deb This is likely caused by the corresponding binary packages shipping identical binaries (or librariesi, ...) with different names. cheers, mysql-router-dbgsym=8.0.20-1~exp1_mysql-server-core-8.0-dbgsym=8.0.20-1~exp1.log.gz Description: application/gzip
Bug#957286: marked as done (gnomekiss: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 19:33:28 + with message-id and subject line Bug#957286: fixed in gnomekiss 2.0-6.1 has caused the Debian Bug report #957286, regarding gnomekiss: ftbfs with GCC-10 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.) -- 957286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gnomekiss Version: 2.0-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/gnomekiss_2.0-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] | ^~ In file included from /usr/include/glib-2.0/glib.h:82, from /usr/include/gtk-3.0/gdk/gdkconfig.h:13, from /usr/include/gtk-3.0/gdk/gdk.h:30, from /usr/include/gtk-3.0/gtk/gtk.h:30, from util.c:23: /usr/include/glib-2.0/glib/gstrfuncs.h:201:23: note: declared here 201 | gint g_strcasecmp (const gchar *s1, | ^~~~ util.c: In function ‘event_find_or_insert’: util.c:387:5: warning: ‘g_mem_chunk_alloc0’ is deprecated [-Wdeprecated-declarations] 387 | event= g_chunk_new0(KissActionList, event_chunk); | ^ In file included from /usr/include/glib-2.0/glib.h:105, from /usr/include/gtk-3.0/gdk/gdkconfig.h:13, from /usr/include/gtk-3.0/gdk/gdk.h:30, from /usr/include/gtk-3.0/gtk/gtk.h:30, from util.c:23: /usr/include/glib-2.0/glib/deprecated/gallocator.h:52:17: note: declared here 52 | gpointerg_mem_chunk_alloc0 (GMemChunk*mem_chunk); | ^~ gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\" -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -D_REENTRANT -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -c -o interface.o interface.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\" -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -D_REENTRANT -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -c -o callbacks.o
Bug#966653: See if the same error comes with gitlab 13.2.3 which I just uploaded
From the previous comment on this bug, it appears to be caused by ruby-google-protobuf and ruby-grpc. Can you try the new gitlab version I just uploaded?
Bug#957684: marked as done (pick: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 17:49:00 +
with message-id
and subject line Bug#957684: fixed in pick 2.0.2-1.1
has caused the Debian Bug report #957684,
regarding pick: ftbfs with GCC-10
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.)
--
957684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pick
Version: 2.0.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pick_2.0.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
dh_update_autotools_config
dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
configure.ac:5: installing './compile'
configure.ac:32: installing './config.guess'
configure.ac:32: installing './config.sub'
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.after
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for pledge... no
checking for reallocarray... yes
checking for strtonum... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for library containing setupterm... -lcurses
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for linux-gnu malloc hardening options... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
dh_auto_build
make -j4
make[1]:
Bug#957928: marked as done (welcome2l: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 17:34:13 + with message-id and subject line Bug#957928: fixed in welcome2l 3.04-27.1 has caused the Debian Bug report #957928, regarding welcome2l: ftbfs with GCC-10 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.) -- 957928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:welcome2l Version: 3.04-27 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/welcome2l_3.04-27_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package welcome2l dpkg-buildpackage: info: source version 3.04-27 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Robert Luberda dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh "clean" debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' dh_auto_clean -v -Smakefile --parallel make -j4 clean make[2]: Entering directory '/<>' rm -f *~ core build/* rm -f Welcome2L *.o version.h make[2]: Leaving directory '/<>' rm -rf debian/_tmp_ debian/default make[1]: Leaving directory '/<>' dh_clean debian/rules binary dh "binary" dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/<>' Setting Debian in debian/default dh_auto_build -v -Smakefile --parallel -- STRIP=: make -j4 "INSTALL=install --strip-program=true" STRIP=: make[2]: Entering directory '/<>' gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wall -fno-strength-reduce ansi.c gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wall -fno-strength-reduce main.c In file included from /usr/include/string.h:495, from main.c:36: In function ‘strncpy’, inlined from ‘main’ at main.c:448:4: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 25 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘main’ at main.c:501:4: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 15 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ gcc -Wl,-z,relro -Wl,-z,now -v *.o -o Welcome2L Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 10-20200222-1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
Bug#968130: Acknowledgement (iwd: Doesn't start at boot for beowulf)
Ah shoot, sorry, please close this bug. I sent it to the wrong address... Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Sunday, August 9, 2020 8:57 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 968130: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Andreas Henriksson andr...@fatal.se > > If you wish to submit further information on this problem, please > send it to 968...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > --- > > 968130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#957515: marked as done (macopix: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 17:00:09 + with message-id and subject line Bug#957515: fixed in macopix 3.4.0+dfsg.1-1 has caused the Debian Bug report #957515, regarding macopix: ftbfs with GCC-10 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.) -- 957515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:macopix Version: 1.7.4-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/macopix_1.7.4-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: ssl.o:./src/main.h:328: multiple definition of `ClockType'; main.o:./src/main.h:328: first defined here /usr/bin/ld: ssl.o:./src/main.h:321: multiple definition of `TypInterpolate'; main.o:./src/main.h:321: first defined here /usr/bin/ld: ssl.o:./src/main.h:313: multiple definition of `DuetAnimeMode'; main.o:./src/main.h:313: first defined here /usr/bin/ld: ssl.o:./src/main.h:286: multiple definition of `TypBalloon'; main.o:./src/main.h:286: first defined here /usr/bin/ld: ssl.o:./src/main.h:277: multiple definition of `PosBalloon'; main.o:./src/main.h:277: first defined here /usr/bin/ld: ssl.o:./src/main.h:270: multiple definition of `AutoBar'; main.o:./src/main.h:270: first defined here /usr/bin/ld: ssl.o:./src/main.h:267: multiple definition of `FFPos'; main.o:./src/main.h:267: first defined here /usr/bin/ld: ssl.o:./src/main.h:264: multiple definition of `MoveMode'; main.o:./src/main.h:264: first defined here /usr/bin/ld: ssl.o:./src/main.h:257: multiple definition of `HomePos'; main.o:./src/main.h:257: first defined here /usr/bin/ld: ssl.o:./src/main.h:222: multiple definition of `ClockMode'; main.o:./src/main.h:222: first defined here /usr/bin/ld: ssl.o:./src/main.h:175: multiple definition of `MaCoPiXFolder'; main.o:./src/main.h:175: first defined here /usr/bin/ld: ssl.o:./src/main.h:139: multiple definition of `MENU_EXT'; main.o:./src/main.h:139: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:546: multiple definition of `CompositeFlag'; main.o:./src/main.h:546: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:526: multiple definition of `ScanMenuDir'; main.o:./src/main.h:526: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:523: multiple definition of `ConsMode'; main.o:./src/main.h:523: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:519: multiple definition of `SignalAction'; main.o:./src/main.h:519: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:492: multiple definition of `MailStatus'; main.o:./src/main.h:492: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:463: multiple definition of `MailPixPos'; main.o:./src/main.h:463: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:461: multiple definition of `MailStatus0'; main.o:./src/main.h:461: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:453: multiple definition of `SetReleaseData'; main.o:./src/main.h:453: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:451: multiple definition of `GuiColorConf'; main.o:./src/main.h:451: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:436: multiple definition of `GuiFontConf'; main.o:./src/main.h:436: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:343: multiple definition of `MenuSelect'; main.o:./src/main.h:343: first defined here /usr/bin/ld: sslmanager.o:./src/main.h:328: multiple definition of `ClockType';
Bug#968130: iwd: Doesn't start at boot for beowulf
Package: iwd Version: 0.14-2 Severity: grave Tags: patch Justification: renders package unusable iwd 0.14-2 doesn't get started by init. I have to manually start it. This can be fixed easily by adding an sysvinit script at the debian directory. I have a fix available at https://git.devuan.org/jobbautista9/iwd/src/branch/suites/beowulf. I would like it to be accepted into the main archive, which I can't do via a new issue at git. signature.asc Description: OpenPGP digital signature
Processed: closing 961203
Processing commands for cont...@bugs.debian.org: > close 961203 2.13.0-1 Bug #961203 [src:ensmallen] ensmallen FTBFS on armel/armhf/mipsel: test failure Marked as fixed in versions ensmallen/2.13.0-1. Bug #961203 [src:ensmallen] ensmallen FTBFS on armel/armhf/mipsel: test failure Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 961203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968047: marked as done (texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804))
Your message dated Sun, 09 Aug 2020 15:52:49 + with message-id and subject line Bug#968047: fixed in texlive-extra 2020.20200804-2 has caused the Debian Bug report #968047, regarding texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804) 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.) -- 968047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: texlive-fonts-extra-links Version: 2020.20200804-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../texlive-fonts-extra-links_2020.20200804-1_all.deb ... Unpacking texlive-fonts-extra-links (2020.20200804-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-fonts-extra-links_2020.20200804-1_all.deb (--unpack): trying to overwrite '/usr/share/texlive/texmf-dist/fonts/truetype/google/noto-emoji/NotoColorEmoji.ttf', which is also in package texlive-fonts-extra 2020.20200629-1 Errors were encountered while processing: /var/cache/apt/archives/texlive-fonts-extra-links_2020.20200804-1_all.deb cheers, Andreas texlive-fonts-extra=2020.20200629-1_texlive-fonts-extra-links=2020.20200804-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: texlive-extra Source-Version: 2020.20200804-2 Done: Norbert Preining We believe that the bug you reported is fixed in the latest version of texlive-extra, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated texlive-extra 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, 09 Aug 2020 21:18:11 +0900 Source: texlive-extra Architecture: source Version: 2020.20200804-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX Task Force Changed-By: Norbert Preining Closes: 968047 Changes: texlive-extra (2020.20200804-2) unstable; urgency=medium . * Fix some replace/breaks due to font move to -links (Closes: #968047) Checksums-Sha1: d87f99f59fab1d5d2070fe7313a4a846af83228d 3445 texlive-extra_2020.20200804-2.dsc a5cf04e88be42c4cf79cc9a18d1b408757744db1 180508 texlive-extra_2020.20200804-2.debian.tar.xz 0f172a6851f66584e74c23f6537cdda0712c9398 5910 texlive-extra_2020.20200804-2_source.buildinfo Checksums-Sha256: 31a4a44bf273f5df198e8b5aaff17786193d6dc57980194aab61b8feaa8e6fa0 3445 texlive-extra_2020.20200804-2.dsc 3afabf7e626b31bfcd158c6dab62dea0b66f6369529723ad85c0ab10d617 180508 texlive-extra_2020.20200804-2.debian.tar.xz 265efedece815b445beb79a3058b1749bbb2eae0778a399c49f1ba1d0e50c62a 5910 texlive-extra_2020.20200804-2_source.buildinfo Files: 434bd26b96151d8ab67934170ac05ac3 3445 tex optional texlive-extra_2020.20200804-2.dsc aedf8e2de62a9bd58e98c35689302dc1 180508 tex optional texlive-extra_2020.20200804-2.debian.tar.xz 0a13e46141948a06d026dee007b80477 5910 tex optional texlive-extra_2020.20200804-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl8wE6gACgkQ2A4JsIcU AGbK+gf+LZecqfS4XJ6RjmBQgVj5gyhV/jLXC+xpTcJwEz22+VANWwICV35sxQmT YL3ItD1wNk5FFGnOujgURo+pRUoIpWUBz+eaehFkMOQhKGD3puLGhg/LJFcLlovN IzC824m+BJdP2Gm1W5eJ8l3dO5l76PntnI8onjeEJYzMeY1bHN5qUwxIvkEU9alb QzLGMQAsg5y2VM02sy5Ma0DKGc3+NotSvN5+Dw2fEQ5pecr4CiiYXenyUR9woCLW vvXAcPDhHcPCsST1/alKP0J1cM9nCthzx677LPqPTJwcBHvE65EAvB43lk8B292i FwtDHLr3bzrU9nvKWh4HArdKrQEUJw== =FgWQ -END PGP SIGNATURE End Message ---
Bug#967912: marked as done (texlive-luatex: file conflict with old texlive-latex-extra package)
Your message dated Sun, 09 Aug 2020 15:50:34 + with message-id and subject line Bug#967912: fixed in texlive-base 2020.20200804-2 has caused the Debian Bug report #967912, regarding texlive-luatex: file conflict with old texlive-latex-extra package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: texlive-luatex Version: 2020.20200804-1 Severity: serious There was a hiccup installing your package (sorry for the German): , | Entpacken von texlive-luatex (2020.20200804-1) über (2020.20200629-1) ... | dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-78owrZ/04-texlive-luatex_2020.20200804-1_all.deb (--unpack): | Versuch, »/usr/share/texlive/texmf-dist/scripts/cloze/cloze.lua« zu überschreiben, welches auch in Paket texlive-latex-extra 2020.20200629-1 ist ` After upgrading texlive-latex-extra to 2020.20200804-1, the texlive-luatex installation completed successfully, so it seems another Breaks+Replaces combo is in order. Thanks for maintaining texlive! :-) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-nouveau (SMP w/2 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-luatex depends on: ii libjs-jquery 3.5.1+dfsg-4 ii lmodern 2.004.5-6 ii tex-common6.15 ii texlive-base 2020.20200804-1 ii texlive-binaries 2020.20200327.54578-4+b1 texlive-luatex recommends no packages. texlive-luatex suggests no packages. Versions of packages tex-common depends on: ii dpkg 1.20.5 ii ucf 3.0043 Versions of packages tex-common suggests: ii debhelper 13.2 Versions of packages texlive-luatex is related to: ii tex-common6.15 ii texlive-binaries 2020.20200327.54578-4+b1 -- debconf information: tex-common/check_texmf_missing: tex-common/check_texmf_wrong: tex-common/singleuser: false --- End Message --- --- Begin Message --- Source: texlive-base Source-Version: 2020.20200804-2 Done: Norbert Preining We believe that the bug you reported is fixed in the latest version of texlive-base, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated texlive-base 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, 09 Aug 2020 21:19:03 +0900 Source: texlive-base Architecture: source Version: 2020.20200804-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX Task Force Changed-By: Norbert Preining Closes: 967912 Changes: texlive-base (2020.20200804-2) unstable; urgency=medium . * Fix missing replace/breaks for cloze moved to tl-luatex (Closes: #967912) Checksums-Sha1: 78f93f6026c81cee93ff34c370c54eda4c8ff54c 2716 texlive-base_2020.20200804-2.dsc be02585eb32b89f7c6b40752fc18b327f3983d05 2028976 texlive-base_2020.20200804-2.debian.tar.xz 075170873b1d4287807fbc2a901718901bfbb2a8 5906 texlive-base_2020.20200804-2_source.buildinfo Checksums-Sha256: ac2ca7a5883e0e47d3ddef3938fdd3a63c6fe62a6d54c71f0be726ad2d47a9bb 2716 texlive-base_2020.20200804-2.dsc c050bc917782507d1fa26cea984683bcef0494f21f7074f4fbe33381f587 2028976 texlive-base_2020.20200804-2.debian.tar.xz e3c6f675dac75d8c23b15a07de885804e1724b68e300305fd26c48ddecd8fd59 5906 texlive-base_2020.20200804-2_source.buildinfo Files: 98fa57b1b834e6bd705d354bf26f9e40 2716 tex optional texlive-base_2020.20200804-2.dsc 86506484421192efd3da81f945cbaa0c 2028976 tex optional texlive-base_2020.20200804-2.debian.tar.xz 8bf122794f09d2fdaf8fd19be269c399 5906 tex optional texlive-base_2020.20200804-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl8wE6QACgkQ2A4JsIcU
Bug#963658: marked as done (urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index.)
Your message dated Sun, 09 Aug 2020 15:35:59 + with message-id and subject line Bug#963658: fixed in urwid 2.1.1-1 has caused the Debian Bug report #963658, regarding urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index. 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.) -- 963658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: urwid Version: 2.1.0-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx3.1 Hi, urwid fails to build with Sphinx 3.1, currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/numedit.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/raw_display.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/lcd_display.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/__init__.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/font.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/html_fragment.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/split_repr.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/display_common.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/text_layout.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/canvas.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/decoration.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/compat.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/util.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/curses_display.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/old_str_util.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/_async_kw_event_loop.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/treetools.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/vterm.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/version.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/listbox.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/monitored_list.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/graphics.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/command_map.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/main_loop.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/widget.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/signals.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/escape.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/container.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/web_display.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > copying urwid/wimp.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid > creating /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_text_layout.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_widget.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/__init__.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_util.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_doctests.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/util.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_event_loops.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_graphics.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_escapes.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_canvas.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_container.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_decoration.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_listbox.py -> > /<>/.pybuild/cpython3_3.8_urwid/build/urwid/tests > copying urwid/tests/test_str_util.py -> >
Bug#957460: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxxvideo Version: 0.1-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxxvideo_0.1-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking X11/Xlib.h usability... yes checking X11/Xlib.h presence... yes checking for X11/Xlib.h... yes checking X11/extensions/Xv.h usability... yes checking X11/extensions/Xv.h presence... yes checking for X11/extensions/Xv.h... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c -o libomxxvideo_la-omx_xvideo_sink_component.lo `test -f 'omx_xvideo_sink_component.c' || echo './'`omx_xvideo_sink_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_xvideo_sink_component.c -fPIC -DPIC -o .libs/libomxxvideo_la-omx_xvideo_sink_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_xvideo_sink_component.c -o libomxxvideo_la-omx_xvideo_sink_component.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror
Bug#957459: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxil-bellagio Version: 0.9.3-4.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxil-bellagio_0.9.3-4.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders\/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxil_bellagio_la-common.lo `test -f 'common.c' || echo './'`common.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c common.c -fPIC -DPIC -o .libs/libomxil_bellagio_la-common.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c common.c -o libomxil_bellagio_la-common.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders\/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxil_bellagio_la-content_pipe_inet.lo `test -f 'content_pipe_inet.c' || echo './'`content_pipe_inet.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c content_pipe_inet.c -fPIC -DPIC -o .libs/libomxil_bellagio_la-content_pipe_inet.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c content_pipe_inet.c -o libomxil_bellagio_la-content_pipe_inet.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders\/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxil_bellagio_la-content_pipe_file.lo `test -f 'content_pipe_file.c' || echo './'`content_pipe_file.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\" -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c content_pipe_file.c -fPIC -DPIC -o .libs/libomxil_bellagio_la-content_pipe_file.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I./base -I./core_extensions -DINSTALL_PATH_STR=\"/usr/lib/libomxil-bellagio0\" -DOMX_LOADERS_DIRNAME=\"/usr/lib/omxloaders/\"
Bug#957461: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxvorbis Version: 0.1-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxvorbis_0.1-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking for VORBIS... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c -o libomxvorbis_la-omx_vorbisdec_component.lo `test -f 'omx_vorbisdec_component.c' || echo './'`omx_vorbisdec_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c omx_vorbisdec_component.c -fPIC -DPIC -o .libs/libomxvorbis_la-omx_vorbisdec_component.o omx_vorbisdec_component.c: In function ‘omx_vorbisdec_component_BufferMgmtCallbackVorbis’: omx_vorbisdec_component.c:280:7: warning: variable ‘eos’ set but not used [-Wunused-but-set-variable] 280 | int eos=0; | ^~~ omx_vorbisdec_component.c:271:11: warning: variable ‘outputLength’ set but not used [-Wunused-but-set-variable] 271 | OMX_U32 outputLength; | ^~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable
Bug#957458: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxvideosrc Version: 0.1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxvideosrc_0.1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking linux/videodev2.h usability... yes checking linux/videodev2.h presence... yes checking for linux/videodev2.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating test/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c -o libomxvideosrc_la-omx_videosrc_component.lo `test -f 'omx_videosrc_component.c' || echo './'`omx_videosrc_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c omx_videosrc_component.c -fPIC -DPIC -o .libs/libomxvideosrc_la-omx_videosrc_component.o omx_videosrc_component.c: In function ‘omx_videosrc_component_Destructor’: omx_videosrc_component.c:163:17: warning: variable ‘err’ set but not used [-Wunused-but-set-variable] 163 | OMX_ERRORTYPE err = OMX_ErrorNone; | ^~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g
Bug#957457: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxmad Version: 0.1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxmad_0.1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking for MAD... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c -o libomxmad_la-omx_maddec_component.lo `test -f 'omx_maddec_component.c' || echo './'`omx_maddec_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_maddec_component.c -fPIC -DPIC -o .libs/libomxmad_la-omx_maddec_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_maddec_component.c -o libomxmad_la-omx_maddec_component.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c -o
Bug#957290: marked as done (gnuais: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 15:35:05 + with message-id and subject line Bug#957290: fixed in gnuais 0.3.3-9 has caused the Debian Bug report #957290, regarding gnuais: ftbfs with GCC-10 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.) -- 957290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gnuais Version: 0.3.3-8 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/gnuais_0.3.3-8_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuais.dir/protodec.c.o -c /<>/src/protodec.c [ 70%] Building C object src/CMakeFiles/gnuais.dir/rwlock.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuais.dir/rwlock.c.o -c /<>/src/rwlock.c [ 75%] Building C object src/CMakeFiles/gnuais.dir/serial.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuais.dir/serial.c.o -c /<>/src/serial.c [ 79%] Building C object src/gui/CMakeFiles/gnuaisgui.dir/osm-gps-map-ais.c.o cd /<>/obj-x86_64-linux-gnu/src/gui && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/osmgpsmap-1.0 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuaisgui.dir/osm-gps-map-ais.c.o -c /<>/src/gui/osm-gps-map-ais.c [ 83%] Building C object src/CMakeFiles/gnuais.dir/spsymbol.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuais.dir/spsymbol.c.o -c /<>/src/spsymbol.c [ 87%] Building C object src/CMakeFiles/gnuais.dir/ipc.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/gnuais.dir/ipc.c.o -c /<>/src/ipc.c /<>/src/spsymbol.c: In function ‘symbol_lookup_db_mem’: /<>/src/spsymbol.c:73:12: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 73 | return (spkey_t)se; |^ /<>/src/spsymbol.c: In function ‘symbol_db_mem’: /<>/src/spsymbol.c:106:12: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 106
Bug#957456: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxalsa Version: 0.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxalsa_0.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking for ALSA... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating test/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c -o libomxalsa_la-omx_alsasink_component.lo `test -f 'omx_alsasink_component.c' || echo './'`omx_alsasink_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_alsasink_component.c -fPIC -DPIC -o .libs/libomxalsa_la-omx_alsasink_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_alsasink_component.c -o libomxalsa_la-omx_alsasink_component.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c -o libomxalsa_la-omx_alsasrc_component.lo `test -f 'omx_alsasrc_component.c' || echo './'`omx_alsasrc_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Werror -pthread -g -Wall -c omx_alsasrc_component.c -fPIC -DPIC -o .libs/libomxalsa_la-omx_alsasrc_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I..
Bug#957455: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxfbdevsink Version: 0.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxfbdevsink_0.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking linux/fb.h usability... yes checking linux/fb.h presence... yes checking for linux/fb.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c -o libomxfbdev_la-omx_fbdev_sink_component.lo `test -f 'omx_fbdev_sink_component.c' || echo './'`omx_fbdev_sink_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c omx_fbdev_sink_component.c -fPIC -DPIC -o .libs/libomxfbdev_la-omx_fbdev_sink_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c omx_fbdev_sink_component.c -o
Bug#957453: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables 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.) -- 957453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxcamera Version: 0.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libomxcamera_0.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for library containing dlopen... -ldl checking linux/videodev2.h usability... yes checking linux/videodev2.h presence... yes checking for linux/videodev2.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating m4/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in m4 make[3]: Entering directory '/<>/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/m4' Making all in src make[3]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c -o libomxcamera_la-omx_camera_source_component.lo `test -f 'omx_camera_source_component.c' || echo './'`omx_camera_source_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c omx_camera_source_component.c -fPIC -DPIC -o .libs/libomxcamera_la-omx_camera_source_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wno-error=unused-but-set-variable -Werror -pthread -g -Wall -c
Bug#963658: marked as pending in urwid
Control: tag -1 pending Hello, Bug #963658 in urwid reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/urwid/-/commit/038fd16b03179cd7260f2820450face4b5d6f6f2 Add patch for new Sphinx Closes: #963658 (this message was generated automatically) -- Greetings https://bugs.debian.org/963658
Processed: Bug#963658 marked as pending in urwid
Processing control commands: > tag -1 pending Bug #963658 [src:urwid] urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index. Added tag(s) pending. -- 963658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966171: marked as done (ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common)
Your message dated Sun, 09 Aug 2020 15:20:15 + with message-id and subject line Bug#966171: fixed in ydpdict 1.0.3-1 has caused the Debian Bug report #966171, regarding ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common 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.) -- 966171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ydpdict Version: 1.0.2+1.0.3-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Hi, ydpdict started to FTBFS when GCC 10 was made the default compiler: /bin/bash ../libtool --tag=CC --mode=link gcc -Wall -g -O2 -fdebug-prefix-map=/build/ydpdict-1.0.2+1.0.3=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc\" -g -O2 -fdebug-prefix-map=/build/ydpdict-1.0.2+1.0. 3=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -Wl,-z,relro -o ydpdict ydpdict-ydpconfig.o ydpdict-ydpsound.o ydpdict-ydpdict.o ydpdict-xmalloc.o ydpdict-adpcm.o -lm -lncursesw -lydpdict -lao -lncursesw libtool: link: gcc -Wall -g -O2 -fdebug-prefix-map=/build/ydpdict-1.0.2+1.0.3=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc\" -g -O2 -fdebug-prefix-map=/build/ydpdict-1.0.2+1.0.3=. -fstack-protector-strong -Wf ormat -Werror=format-security -DHAVE_CONFIG_H -Wl,-z -Wl,relro -o ydpdict ydpdict-ydpconfig.o ydpdict-ydpsound.o ydpdict-ydpdict.o ydpdict-xmalloc.o ydpdict-adpcm.o -lm -lydpdict -lao -lncursesw /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:55: multiple definition of `config_cdpath'; ydpdict-ydpconfig.o:./src/ydpconfig.h:55: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:56: multiple definition of `config_player'; ydpdict-ydpconfig.o:./src/ydpconfig.h:56: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:58: multiple definition of `config_audio'; ydpdict-ydpconfig.o:./src/ydpconfig.h:58: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:64: multiple definition of `config_cf2'; ydpdict-ydpconfig.o:./src/ydpconfig.h:64: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:63: multiple definition of `config_cf1'; ydpdict-ydpconfig.o:./src/ydpconfig.h:63: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:62: multiple definition of `config_text'; ydpdict-ydpconfig.o:./src/ydpconfig.h:62: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:61: multiple definition of `config_transparent'; ydpdict-ydpconfig.o:./src/ydpconfig.h:61: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:60: multiple definition of `config_color'; ydpdict-ydpconfig.o:./src/ydpconfig.h:60: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:59: multiple definition of `config_dict'; ydpdict-ydpconfig.o:./src/ydpconfig.h:59: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:57: multiple definition of `config_word'; ydpdict-ydpconfig.o:./src/ydpconfig.h:57: first defined here /usr/bin/ld: ydpdict-ydpsound.o:./src/ydpconfig.h:54: multiple definition of `config_path'; ydpdict-ydpconfig.o:./src/ydpconfig.h:54: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:54: multiple definition of `config_path'; ydpdict-ydpconfig.o:./src/ydpconfig.h:54: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:59: multiple definition of `config_dict'; ydpdict-ydpconfig.o:./src/ydpconfig.h:59: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:61: multiple definition of `config_transparent'; ydpdict-ydpconfig.o:./src/ydpconfig.h:61: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:60: multiple definition of `config_color'; ydpdict-ydpconfig.o:./src/ydpconfig.h:60: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:57: multiple definition of `config_word'; ydpdict-ydpconfig.o:./src/ydpconfig.h:57: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:62: multiple definition of `config_text'; ydpdict-ydpconfig.o:./src/ydpconfig.h:62: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:63: multiple definition of `config_cf1'; ydpdict-ydpconfig.o:./src/ydpconfig.h:63: first defined here /usr/bin/ld: ydpdict-ydpdict.o:./src/ydpconfig.h:64: multiple definition of `config_cf2';
Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start
Hi, On Sat, Aug 08, 2020 at 08:09:24PM +0200, Michel Le Bihan via Debian-on-mobile-maintainers wrote: > Package: phosh > Version: 0.4.3-1 > Severity: grave > Justification: renders package unusable > > Hello, > > On a freshly created Debian sid live system: > ``` > sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video- > all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/ > sudo chroot debian-live-root passwd > sudo chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1 > 123456) user > sudo chroot debian-live-root systemctl enable phosh > cp debian-live-root/vmlinuz .; cp debian-live-root/initrd.img . > sudo mksquashfs debian-live-root root.squashfs -comp lz4 > python3 -m http.server -b localhost 8080 > qemu-system-x86_64 -machine accel=kvm -m 4G -device virtio-net-pci,netdev=net0 > -serial stdio -monitor vc -netdev > user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian- > live -kernel ./vmlinuz -initrd ./initrd.img -append "console=ttyS0 > ip=frommedia boot=live nopersistence > fetch=http://10.0.2.252:8080/root.squashfs; > ``` > (last command is to start the test VM) > > Phosh doesn't start. On the console I see: > ``` > traps: phoc[362] trap int3 ip:7f684a6d9585 sp:7ffccc2cfe90 error:0 in > libglib-2.0.so.0.6400.4[7f684a69f000+81000] > ``` Your VM likely DRM capable GPU (see e.g. drm_info). -- Guido
Bug#966437: marked as done (bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1)
Your message dated Sun, 09 Aug 2020 15:03:29 +
with message-id
and subject line Bug#966437: fixed in bambam 1.0.2+dfsg-1
has caused the Debian Bug report #966437,
regarding bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bambam
Version: 1.0.1+dfsg-1
Severity: serious
Tags: bullseye sid
https://ci.debian.net/packages/b/bambam/unstable/amd64/
Test success with imagemagick < 8:6.9.11.24+dfsg-1:
...
On attempt 5 the average screen color was too close to white: 233,230,235.
On attempt 6 the average screen color was too close to white: 225,223,231.
On attempt 7 the average screen color was too close to white: 223,220,226.
...
Test failure with imagemagick 8:6.9.11.24+dfsg-1:
...
On attempt 37 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 38 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 39 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
Traceback (most recent call last):
File "./debian/tests/smoke-meat", line 101, in
main()
File "./debian/tests/smoke-meat", line 24, in main
await_startup()
File "./debian/tests/smoke-meat", line 45, in await_startup
raise Exception('Failed to see bambam start after %d attempts.' %
attempt_count)
Exception: Failed to see bambam start after 40 attempts.
I suspect the output of convert changed that is parsed in
https://sources.debian.org/src/bambam/1.0.1+dfsg-1/debian/tests/smoke-meat/#L83
--- End Message ---
--- Begin Message ---
Source: bambam
Source-Version: 1.0.2+dfsg-1
Done: Marcin Owsiany
We believe that the bug you reported is fixed in the latest version of
bambam, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcin Owsiany (supplier of updated bambam 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, 09 Aug 2020 16:25:46 +0200
Source: bambam
Binary: bambam
Architecture: source all
Version: 1.0.2+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Marcin Owsiany
Changed-By: Marcin Owsiany
Description:
bambam - keyboard mashing and doodling game for babies
Closes: 966437 966438
Changes:
bambam (1.0.2+dfsg-1) sid; urgency=medium
.
[ Debian Janitor ]
* Bump debhelper from old 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Marcin Owsiany ]
* New upstream release
* Improvements to the autopkgtest script to be more resilient to changes
of output format of the `convert` tool it uses. Closes: #966438, #966437
Checksums-Sha1:
dea1b0b77de500302b64d0a2d04e6c2819cdbaa3 2235 bambam_1.0.2+dfsg-1.dsc
bd0b7748d8ee05ab9808554aa72f0d8aef0b3fab 456867
bambam_1.0.2+dfsg.orig-extrasounds.tar.gz
aa516aba039c64889acf381f0832c000ed9504c8 458474 bambam_1.0.2+dfsg.orig.tar.gz
6e8ece39539f50d34860fac1e37654b2ff69c2e2 9948 bambam_1.0.2+dfsg-1.debian.tar.xz
07559b0882f20c16f0e29149f067c3f2f3693b53 567356 bambam_1.0.2+dfsg-1_all.deb
7cfc2e8d2f5eea44f42774bbf9c3cd49d0d7e3a0 5895
bambam_1.0.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
f9808eab8a7939faad62c2adc9d14227499a7bde2d7af4348994876f5b3c3d4c 2235
bambam_1.0.2+dfsg-1.dsc
609b79b59cd5bae685a8bfefcfc73da95551773ec3cc3add45a5b3789d82ac32 456867
bambam_1.0.2+dfsg.orig-extrasounds.tar.gz
ac73abcbbcc0a9af109dac981ae35344b9ecb6e454e50fc95f20b723234e66e1 458474
bambam_1.0.2+dfsg.orig.tar.gz
8255305bafffd74f707c8008a1e787ea55a5ff6334e16e7624837269cae35d6b 9948
bambam_1.0.2+dfsg-1.debian.tar.xz
8b46a8f4562a11ce1ba776c939018f83907093a6e099a32aaa29eb21ac17e973 567356
bambam_1.0.2+dfsg-1_all.deb
d267c1a28e1906be750feb7462763b94f19f41e459bd898e02a9238f3750b00e 5895
bambam_1.0.2+dfsg-1_amd64.buildinfo
Files:
20fcf747740b7f25b472b1fe604aab6d 2235 games optional bambam_1.0.2+dfsg-1.dsc
19b59afead7212dc37a053e0f3546ee3 456867 games optional
Bug#966438: marked as done (src:bambam: Autopkgtest fail wiht newer imagemagick*)
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966437: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966437, regarding src:bambam: Autopkgtest fail wiht newer imagemagick* 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.) -- 966437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bambam Version: 1.0.1+dfsg-1 Severity: serious Justification: block imagemagick Dear Maintainer, Upgrading imagemagick fail due to autopkg test failling for your package. See https://ci.debian.net/data/autopkgtest/testing/amd64/b/bambam/6448023/log.gz Could you : 1. Fix the failure 2. Please in case of error take a screenshot convert it to png and print the png as base64 (help debugging) Bastien --- End Message --- --- Begin Message --- Source: bambam Source-Version: 1.0.2+dfsg-1 Done: Marcin Owsiany We believe that the bug you reported is fixed in the latest version of bambam, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcin Owsiany (supplier of updated bambam 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, 09 Aug 2020 16:25:46 +0200 Source: bambam Binary: bambam Architecture: source all Version: 1.0.2+dfsg-1 Distribution: sid Urgency: medium Maintainer: Marcin Owsiany Changed-By: Marcin Owsiany Description: bambam - keyboard mashing and doodling game for babies Closes: 966437 966438 Changes: bambam (1.0.2+dfsg-1) sid; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 9 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Marcin Owsiany ] * New upstream release * Improvements to the autopkgtest script to be more resilient to changes of output format of the `convert` tool it uses. Closes: #966438, #966437 Checksums-Sha1: dea1b0b77de500302b64d0a2d04e6c2819cdbaa3 2235 bambam_1.0.2+dfsg-1.dsc bd0b7748d8ee05ab9808554aa72f0d8aef0b3fab 456867 bambam_1.0.2+dfsg.orig-extrasounds.tar.gz aa516aba039c64889acf381f0832c000ed9504c8 458474 bambam_1.0.2+dfsg.orig.tar.gz 6e8ece39539f50d34860fac1e37654b2ff69c2e2 9948 bambam_1.0.2+dfsg-1.debian.tar.xz 07559b0882f20c16f0e29149f067c3f2f3693b53 567356 bambam_1.0.2+dfsg-1_all.deb 7cfc2e8d2f5eea44f42774bbf9c3cd49d0d7e3a0 5895 bambam_1.0.2+dfsg-1_amd64.buildinfo Checksums-Sha256: f9808eab8a7939faad62c2adc9d14227499a7bde2d7af4348994876f5b3c3d4c 2235 bambam_1.0.2+dfsg-1.dsc 609b79b59cd5bae685a8bfefcfc73da95551773ec3cc3add45a5b3789d82ac32 456867 bambam_1.0.2+dfsg.orig-extrasounds.tar.gz ac73abcbbcc0a9af109dac981ae35344b9ecb6e454e50fc95f20b723234e66e1 458474 bambam_1.0.2+dfsg.orig.tar.gz 8255305bafffd74f707c8008a1e787ea55a5ff6334e16e7624837269cae35d6b 9948 bambam_1.0.2+dfsg-1.debian.tar.xz 8b46a8f4562a11ce1ba776c939018f83907093a6e099a32aaa29eb21ac17e973 567356 bambam_1.0.2+dfsg-1_all.deb d267c1a28e1906be750feb7462763b94f19f41e459bd898e02a9238f3750b00e 5895 bambam_1.0.2+dfsg-1_amd64.buildinfo Files: 20fcf747740b7f25b472b1fe604aab6d 2235 games optional bambam_1.0.2+dfsg-1.dsc 19b59afead7212dc37a053e0f3546ee3 456867 games optional bambam_1.0.2+dfsg.orig-extrasounds.tar.gz 56e9da5f9ce7faab1f668b20691acea8 458474 games optional bambam_1.0.2+dfsg.orig.tar.gz c8d9c00c64584b137774c175ef2b8a75 9948 games optional bambam_1.0.2+dfsg-1.debian.tar.xz e7a3ea907060b5d962b0944816d2e8ba 567356 games optional bambam_1.0.2+dfsg-1_all.deb 4d5dd3b45ba6d28edab591ad203e1ff6 5895 games optional bambam_1.0.2+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE2Dp1EgbvsNcTgWzOTmkxeq9EfzMFAl8wDFIACgkQTmkxeq9E fzM2Ng//aPgGxcIQ17uc6YpGxM+FpGMO7CkT7WWjVm7NplOZC4uGc5SvSjO5OZxz 0w3bi8D7NF3cudzJMQ1B5lq0JHN+mlX9KO4px3oSvsYUJKFaWli+y7YPlo7Cx0qB yW1PMBmd1RotGxJBuKK/XlTrJ5tm64EncQv8PyMOECyhOuIrnp9HKnWCBimzJUCT mgeRRK2lCS00iFak0pcZNWt7SP3GCz5JD3a5wOw1NXFm27HRS9cpgTpQoKQFLFUP fpRlMIOdj/Y1hwIggsDMIdYkFmmHD7A9dNl45pjBA048vEFZ0WqOpukJs7UoVLJD
Bug#966437: marked as done (bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1)
Your message dated Sun, 09 Aug 2020 15:03:29 +
with message-id
and subject line Bug#966438: fixed in bambam 1.0.2+dfsg-1
has caused the Debian Bug report #966438,
regarding bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bambam
Version: 1.0.1+dfsg-1
Severity: serious
Tags: bullseye sid
https://ci.debian.net/packages/b/bambam/unstable/amd64/
Test success with imagemagick < 8:6.9.11.24+dfsg-1:
...
On attempt 5 the average screen color was too close to white: 233,230,235.
On attempt 6 the average screen color was too close to white: 225,223,231.
On attempt 7 the average screen color was too close to white: 223,220,226.
...
Test failure with imagemagick 8:6.9.11.24+dfsg-1:
...
On attempt 37 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 38 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 39 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
Traceback (most recent call last):
File "./debian/tests/smoke-meat", line 101, in
main()
File "./debian/tests/smoke-meat", line 24, in main
await_startup()
File "./debian/tests/smoke-meat", line 45, in await_startup
raise Exception('Failed to see bambam start after %d attempts.' %
attempt_count)
Exception: Failed to see bambam start after 40 attempts.
I suspect the output of convert changed that is parsed in
https://sources.debian.org/src/bambam/1.0.1+dfsg-1/debian/tests/smoke-meat/#L83
--- End Message ---
--- Begin Message ---
Source: bambam
Source-Version: 1.0.2+dfsg-1
Done: Marcin Owsiany
We believe that the bug you reported is fixed in the latest version of
bambam, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcin Owsiany (supplier of updated bambam 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, 09 Aug 2020 16:25:46 +0200
Source: bambam
Binary: bambam
Architecture: source all
Version: 1.0.2+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Marcin Owsiany
Changed-By: Marcin Owsiany
Description:
bambam - keyboard mashing and doodling game for babies
Closes: 966437 966438
Changes:
bambam (1.0.2+dfsg-1) sid; urgency=medium
.
[ Debian Janitor ]
* Bump debhelper from old 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Marcin Owsiany ]
* New upstream release
* Improvements to the autopkgtest script to be more resilient to changes
of output format of the `convert` tool it uses. Closes: #966438, #966437
Checksums-Sha1:
dea1b0b77de500302b64d0a2d04e6c2819cdbaa3 2235 bambam_1.0.2+dfsg-1.dsc
bd0b7748d8ee05ab9808554aa72f0d8aef0b3fab 456867
bambam_1.0.2+dfsg.orig-extrasounds.tar.gz
aa516aba039c64889acf381f0832c000ed9504c8 458474 bambam_1.0.2+dfsg.orig.tar.gz
6e8ece39539f50d34860fac1e37654b2ff69c2e2 9948 bambam_1.0.2+dfsg-1.debian.tar.xz
07559b0882f20c16f0e29149f067c3f2f3693b53 567356 bambam_1.0.2+dfsg-1_all.deb
7cfc2e8d2f5eea44f42774bbf9c3cd49d0d7e3a0 5895
bambam_1.0.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
f9808eab8a7939faad62c2adc9d14227499a7bde2d7af4348994876f5b3c3d4c 2235
bambam_1.0.2+dfsg-1.dsc
609b79b59cd5bae685a8bfefcfc73da95551773ec3cc3add45a5b3789d82ac32 456867
bambam_1.0.2+dfsg.orig-extrasounds.tar.gz
ac73abcbbcc0a9af109dac981ae35344b9ecb6e454e50fc95f20b723234e66e1 458474
bambam_1.0.2+dfsg.orig.tar.gz
8255305bafffd74f707c8008a1e787ea55a5ff6334e16e7624837269cae35d6b 9948
bambam_1.0.2+dfsg-1.debian.tar.xz
8b46a8f4562a11ce1ba776c939018f83907093a6e099a32aaa29eb21ac17e973 567356
bambam_1.0.2+dfsg-1_all.deb
d267c1a28e1906be750feb7462763b94f19f41e459bd898e02a9238f3750b00e 5895
bambam_1.0.2+dfsg-1_amd64.buildinfo
Files:
20fcf747740b7f25b472b1fe604aab6d 2235 games optional bambam_1.0.2+dfsg-1.dsc
19b59afead7212dc37a053e0f3546ee3 456867 games optional
Bug#966438: marked as done (src:bambam: Autopkgtest fail wiht newer imagemagick*)
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966438: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966438, regarding src:bambam: Autopkgtest fail wiht newer imagemagick* 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.) -- 966438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bambam Version: 1.0.1+dfsg-1 Severity: serious Justification: block imagemagick Dear Maintainer, Upgrading imagemagick fail due to autopkg test failling for your package. See https://ci.debian.net/data/autopkgtest/testing/amd64/b/bambam/6448023/log.gz Could you : 1. Fix the failure 2. Please in case of error take a screenshot convert it to png and print the png as base64 (help debugging) Bastien --- End Message --- --- Begin Message --- Source: bambam Source-Version: 1.0.2+dfsg-1 Done: Marcin Owsiany We believe that the bug you reported is fixed in the latest version of bambam, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcin Owsiany (supplier of updated bambam 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, 09 Aug 2020 16:25:46 +0200 Source: bambam Binary: bambam Architecture: source all Version: 1.0.2+dfsg-1 Distribution: sid Urgency: medium Maintainer: Marcin Owsiany Changed-By: Marcin Owsiany Description: bambam - keyboard mashing and doodling game for babies Closes: 966437 966438 Changes: bambam (1.0.2+dfsg-1) sid; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 9 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Marcin Owsiany ] * New upstream release * Improvements to the autopkgtest script to be more resilient to changes of output format of the `convert` tool it uses. Closes: #966438, #966437 Checksums-Sha1: dea1b0b77de500302b64d0a2d04e6c2819cdbaa3 2235 bambam_1.0.2+dfsg-1.dsc bd0b7748d8ee05ab9808554aa72f0d8aef0b3fab 456867 bambam_1.0.2+dfsg.orig-extrasounds.tar.gz aa516aba039c64889acf381f0832c000ed9504c8 458474 bambam_1.0.2+dfsg.orig.tar.gz 6e8ece39539f50d34860fac1e37654b2ff69c2e2 9948 bambam_1.0.2+dfsg-1.debian.tar.xz 07559b0882f20c16f0e29149f067c3f2f3693b53 567356 bambam_1.0.2+dfsg-1_all.deb 7cfc2e8d2f5eea44f42774bbf9c3cd49d0d7e3a0 5895 bambam_1.0.2+dfsg-1_amd64.buildinfo Checksums-Sha256: f9808eab8a7939faad62c2adc9d14227499a7bde2d7af4348994876f5b3c3d4c 2235 bambam_1.0.2+dfsg-1.dsc 609b79b59cd5bae685a8bfefcfc73da95551773ec3cc3add45a5b3789d82ac32 456867 bambam_1.0.2+dfsg.orig-extrasounds.tar.gz ac73abcbbcc0a9af109dac981ae35344b9ecb6e454e50fc95f20b723234e66e1 458474 bambam_1.0.2+dfsg.orig.tar.gz 8255305bafffd74f707c8008a1e787ea55a5ff6334e16e7624837269cae35d6b 9948 bambam_1.0.2+dfsg-1.debian.tar.xz 8b46a8f4562a11ce1ba776c939018f83907093a6e099a32aaa29eb21ac17e973 567356 bambam_1.0.2+dfsg-1_all.deb d267c1a28e1906be750feb7462763b94f19f41e459bd898e02a9238f3750b00e 5895 bambam_1.0.2+dfsg-1_amd64.buildinfo Files: 20fcf747740b7f25b472b1fe604aab6d 2235 games optional bambam_1.0.2+dfsg-1.dsc 19b59afead7212dc37a053e0f3546ee3 456867 games optional bambam_1.0.2+dfsg.orig-extrasounds.tar.gz 56e9da5f9ce7faab1f668b20691acea8 458474 games optional bambam_1.0.2+dfsg.orig.tar.gz c8d9c00c64584b137774c175ef2b8a75 9948 games optional bambam_1.0.2+dfsg-1.debian.tar.xz e7a3ea907060b5d962b0944816d2e8ba 567356 games optional bambam_1.0.2+dfsg-1_all.deb 4d5dd3b45ba6d28edab591ad203e1ff6 5895 games optional bambam_1.0.2+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE2Dp1EgbvsNcTgWzOTmkxeq9EfzMFAl8wDFIACgkQTmkxeq9E fzM2Ng//aPgGxcIQ17uc6YpGxM+FpGMO7CkT7WWjVm7NplOZC4uGc5SvSjO5OZxz 0w3bi8D7NF3cudzJMQ1B5lq0JHN+mlX9KO4px3oSvsYUJKFaWli+y7YPlo7Cx0qB yW1PMBmd1RotGxJBuKK/XlTrJ5tm64EncQv8PyMOECyhOuIrnp9HKnWCBimzJUCT mgeRRK2lCS00iFak0pcZNWt7SP3GCz5JD3a5wOw1NXFm27HRS9cpgTpQoKQFLFUP fpRlMIOdj/Y1hwIggsDMIdYkFmmHD7A9dNl45pjBA048vEFZ0WqOpukJs7UoVLJD
Processed: py2removal bugs severity updates - 2020-08-09 14:34:05.556198+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-pam is a module and has 0 external rdeps or not in testing > severity 937996 serious Bug #937996 [src:python-pam] python-pam: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939259: webcheck: Python2 removal in sid/bullseye
On Mon, 2020-07-27 at 00:42 -0400, Sandro Tosi wrote: > 9 months have passed and i dont see any progress on this porting to > python3: last commits on https://arthurdejong.org/git/webcheck are > from 2013 (!) > > Are you still interested in this program (which you wrote)? should we > just remove it from Debian entire? Hi Sandro, Thanks for the reminder. I haven't really found the time to work on webcheck for a while now so if removing it from Debian makes migration easier that would be fine. If anyone is willing to help test/port a new version that would be really welcome though. Kind regards, -- -- arthur - adej...@debian.org - https://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#966085: gitlab contains git bundles with non-free code, unlisted code
Since there are many templates here, I have started https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/168 to track status of each template.
Bug#968131: hdate-applet FTBFS with gcc-10
Source: hdate-applet Version: 0.15.11-3 Severity: serious Tags: ftbfs hdate-applet fails to build from source in unstable: | gcc -g -O2 -ffile-prefix-map=/build/1st/hdate-applet-0.15.11=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o ghcal ghcal-main.o ghcal-interface.o ghcal-callbacks.o -lm -lhdate -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:46: multiple definition of `label_month'; ghcal-main.o:./src/ghcal-interface.h:46: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:47: multiple definition of `label_year'; ghcal-main.o:./src/ghcal-interface.h:47: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:50: multiple definition of `label_hebrew_month_and_year'; ghcal-main.o:./src/ghcal-interface.h:50: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:54: multiple definition of `event_box_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:54: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:51: multiple definition of `index_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:51: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:53: multiple definition of `label_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:53: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:55: multiple definition of `tooltip_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:55: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:45: multiple definition of `today'; ghcal-main.o:./src/ghcal-interface.h:45: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:52: multiple definition of `hdate_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:52: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:49: multiple definition of `spinbutton_year'; ghcal-main.o:./src/ghcal-interface.h:49: first defined here | /usr/bin/ld: ghcal-interface.o:./src/ghcal-interface.h:48: multiple definition of `combobox_month'; ghcal-main.o:./src/ghcal-interface.h:48: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:45: multiple definition of `today'; ghcal-main.o:./src/ghcal-interface.h:45: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:54: multiple definition of `event_box_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:54: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:46: multiple definition of `label_month'; ghcal-main.o:./src/ghcal-interface.h:46: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:47: multiple definition of `label_year'; ghcal-main.o:./src/ghcal-interface.h:47: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:53: multiple definition of `label_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:53: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:52: multiple definition of `hdate_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:52: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:55: multiple definition of `tooltip_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:55: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:50: multiple definition of `label_hebrew_month_and_year'; ghcal-main.o:./src/ghcal-interface.h:50: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:51: multiple definition of `index_day_of_month'; ghcal-main.o:./src/ghcal-interface.h:51: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:49: multiple definition of `spinbutton_year'; ghcal-main.o:./src/ghcal-interface.h:49: first defined here | /usr/bin/ld: ghcal-callbacks.o:./src/ghcal-interface.h:48: multiple definition of `combobox_month'; ghcal-main.o:./src/ghcal-interface.h:48: first defined here | collect2: error: ld returned 1 exit status | make[3]: *** [Makefile:352: ghcal] Error 1 | make[3]: Leaving directory '/build/1st/hdate-applet-0.15.11/src' | make[2]: *** [Makefile:337: all-recursive] Error 1 | make[2]: Leaving directory '/build/1st/hdate-applet-0.15.11' | make[1]: *** [Makefile:255: all] Error 2 | make[1]: Leaving directory '/build/1st/hdate-applet-0.15.11' | make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Reproduced by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/hdate-applet_0.15.11-3.rbuild.log.gz Helmut
Processed: Re: Bug#510368: libgamin0: libfam shlib dependency wrongly set to libfam0
Processing control commands: > severity -1 serious Bug #510368 [libgamin0] libgamin0: libfam shlib dependency wrongly set to libfam0 Severity set to 'serious' from 'important' -- 510368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967118: 0ad: Unversioned Python removal in sid/bullseye
Control: forwarded 936101 https://trac.wildfiregames.com/ticket/5694 Control: tags 936101 + upstream Note that "unversioned Python removal" is not the same as "Python 2 removal". At this point it seems likely that Python 2 will remain in the Debian archive for bullseye, but with a drastically reduced number of third-party modules, and only under the names "python2" and "python2.7" (not "python"). On Sun, 09 Aug 2020 at 13:12:49 +0200, Ludovic Rousseau wrote: > checking for python2.7... no > checking for python... no Changing the Build-Depends from python to python2 would probably solve this. The release-critical bug #967118 can be closed at that time, leaving non-RC bug #936101 open. > The problem is already knwon upstream. > https://trac.wildfiregames.com/ticket/5694 Dropping the dependency on Python 2 completely is a separate bug, #936101, which will need upstream work (whether that's done by 0ad's Debian maintainers or by other upstream contributors). I've marked that bug as forwarded based on the information you provided. Thanks, smcv
Processed: bug 956967 is forwarded to https://trac.wildfiregames.com/changeset/23794
Processing commands for cont...@bugs.debian.org: > forwarded 956967 https://trac.wildfiregames.com/changeset/23794 Bug #956967 [src:0ad] 0ad: FTBFS with gcc-10: undefined reference to `_xmlNode* FArchiveXML::AddPhysicsParameter(_xmlNode*, char const*, FCDParameterAnimatableT&)' Set Bug forwarded-to-address to 'https://trac.wildfiregames.com/changeset/23794'. > thanks Stopping processing here. Please contact me if you need assistance. -- 956967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchive 968130
Processing commands for cont...@bugs.debian.org:
> unarchive 968130
Bug #968130 {Done: Job Bautista } [iwd] iwd:
Doesn't start at boot for beowulf
Unarchived Bug 968130
> tags 968130 = invalid
Unknown tag/s: invalid.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye
bullseye-ignore bookworm bookworm-ignore.
Bug #968130 {Done: Job Bautista } [iwd] iwd:
Doesn't start at boot for beowulf
Removed tag(s) patch.
> severity 968130 wishlist
Bug #968130 {Done: Job Bautista } [iwd] iwd:
Doesn't start at boot for beowulf
Severity set to 'wishlist' from 'grave'
> archive 968130
Bug #968130 {Done: Job Bautista } [iwd] iwd:
Doesn't start at boot for beowulf
archived 968130 to archive/30 (from 968130)
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
968130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 963636 is forwarded to https://lore.kernel.org/lkml/20200809132327.GA145573@eldamar.local/T/#u
Processing commands for cont...@bugs.debian.org: > forwarded 963636 > https://lore.kernel.org/lkml/20200809132327.GA145573@eldamar.local/T/#u Bug #963636 [src:linux] linux: FTBFS with Sphinx 3.1: Could not import extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' (/usr/lib/python3/dist-packages/sphinx/domains/c.py)) Set Bug forwarded-to-address to 'https://lore.kernel.org/lkml/20200809132327.GA145573@eldamar.local/T/#u'. > thanks Stopping processing here. Please contact me if you need assistance. -- 963636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: archive 968130
Processing commands for cont...@bugs.debian.org:
> archive 968130
Bug #968130 {Done: Job Bautista } [iwd] iwd:
Doesn't start at boot for beowulf
archived 968130 to archive/30 (from 968130)
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
968130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#968130: marked as done (iwd: Doesn't start at boot for beowulf)
Your message dated Sun, 09 Aug 2020 13:00:46 + with message-id and subject line Close 968130 has caused the Debian Bug report #968130, regarding iwd: Doesn't start at boot for beowulf 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.) -- 968130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iwd Version: 0.14-2 Severity: grave Tags: patch Justification: renders package unusable iwd 0.14-2 doesn't get started by init. I have to manually start it. This can be fixed easily by adding an sysvinit script at the debian directory. I have a fix available at https://git.devuan.org/jobbautista9/iwd/src/branch/suites/beowulf. I would like it to be accepted into the main archive, which I can't do via a new issue at git. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Wrong send Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Sunday, August 9, 2020 8:58 PM, Job Bautista wrote: > Ah shoot, sorry, please close this bug. I sent it to the wrong address... > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Sunday, August 9, 2020 8:57 PM, Debian Bug Tracking System > ow...@bugs.debian.org wrote: > > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 968130: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130. > > This is an automatically generated reply to let you know your message > > has been received. > > Your message is being forwarded to the package maintainers and other > > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > > Andreas Henriksson andr...@fatal.se > > If you wish to submit further information on this problem, please > > send it to 968...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > > to report a problem with the Bug-tracking system. > > > > 968130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968130 > > Debian Bug Tracking System > > Contact ow...@bugs.debian.org with problems--- End Message ---
Processed: tagging 963636
Processing commands for cont...@bugs.debian.org: > tags 963636 + upstream Bug #963636 [src:linux] linux: FTBFS with Sphinx 3.1: Could not import extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' (/usr/lib/python3/dist-packages/sphinx/domains/c.py)) Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 963636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968127: view3dscene: FTBFS with fpc 3.2.0
Source: view3dscene Version: 3.18.0-4 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/view3dscene.html Compiling code/view3dscene.lpr view3dscene.lpr(55,3) Fatal: Can't find unit CastleUtils used by view3dscene Fatal: Compilation aborted
Bug#968126: mricron: FTBFS with fpc 3.2.0
Source: mricron Version: 0.20140804.1~dfsg.1-3 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mricron.html (3104) Compiling /build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas /build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas(561,10) Warning: (2005) Comment level 2 found /build/1st/mricron-0.20140804.1~dfsg.1/common/distr.pas(545,1) Fatal: (2000) Unexpected end of file Fatal: (1018) Compilation aborted
Bug#957587: marked as done (ncrack: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 12:04:34 +
with message-id
and subject line Bug#957587: fixed in ncrack 0.7+debian-2
has caused the Debian Bug report #957587,
regarding ncrack: ftbfs with GCC-10
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.)
--
957587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ncrack
Version: 0.7+debian-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ncrack_0.7+debian-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -I../../nbase -DHAVE_CONFIG_H
-DNSOCK_VERSION=\"0.02\" -D_FORTIFY_SOURCE=2 -I../include -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall proxy_socks4.c -o proxy_socks4.o
rm -f libnsock.a
ar cr libnsock.a error.o filespace.o gh_heap.o nsock_connect.o nsock_core.o
nsock_iod.o nsock_read.o nsock_timers.o nsock_write.o nsock_ssl.o nsock_event.o
nsock_pool.o netutils.o nsock_pcap.o nsock_engines.o engine_select.o
engine_epoll.o engine_kqueue.o engine_poll.o nsock_proxy.o nsock_log.o
proxy_http.o proxy_socks4.o
ranlib libnsock.a
make[2]: Leaving directory '/<>/nsock/src'
make ncrack
make[2]: Entering directory '/<>'
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -Inbase -Insock/include -Iopensshlib
-Imodules -DHAVE_CONFIG_H -DNCRACK_NAME=\"Ncrack\"
-DNCRACK_URL=\"http://ncrack.org\; -DNCRACK_PLATFORM=\"x86_64-pc-linux-gnu\"
-DNCRACKDATADIR=\"/usr/share/ncrack\" -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -fno-strict-aliasing ncrack.cc -o ncrack.o
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -Inbase -Insock/include -Iopensshlib
-Imodules -DHAVE_CONFIG_H -DNCRACK_NAME=\"Ncrack\"
-DNCRACK_URL=\"http://ncrack.org\; -DNCRACK_PLATFORM=\"x86_64-pc-linux-gnu\"
-DNCRACKDATADIR=\"/usr/share/ncrack\" -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -fno-strict-aliasing utils.cc -o utils.o
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -Inbase -Insock/include -Iopensshlib
-Imodules -DHAVE_CONFIG_H -DNCRACK_NAME=\"Ncrack\"
-DNCRACK_URL=\"http://ncrack.org\; -DNCRACK_PLATFORM=\"x86_64-pc-linux-gnu\"
-DNCRACKDATADIR=\"/usr/share/ncrack\" -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -fno-strict-aliasing TargetGroup.cc -o
TargetGroup.o
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -Inbase -Insock/include -Iopensshlib
-Imodules -DHAVE_CONFIG_H -DNCRACK_NAME=\"Ncrack\"
-DNCRACK_URL=\"http://ncrack.org\; -DNCRACK_PLATFORM=\"x86_64-pc-linux-gnu\"
-DNCRACKDATADIR=\"/usr/share/ncrack\" -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -fno-strict-aliasing Target.cc -o Target.o
ncrack.cc: In function ‘void lookup_init(const char*)’:
ncrack.cc:329:32: warning: ‘void* memset(void*, int, size_t)’ clearing an
object of type ‘global_service’ {aka ‘struct global_service’} with no trivial
copy-assignment; use assignment or value-initialization instead
[-Wclass-memaccess]
329 | memset(, 0, sizeof(temp));
|^
In file included from ncrack.h:266,
from ncrack.cc:133:
global_structures.h:170:16: note: ‘global_service’ {aka ‘struct
global_service’} declared
Bug#968125: hedgewars: FTBFS with fpc 3.2.0
Source: hedgewars Version: 1.0.0-9 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hedgewars.html uWorld.pas(167,13) Note: Call to subroutine "function GetRandom(m:LongWord):DWord;" marked as inline is not inlined uWorld.pas(713,5) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(993,13) Note: Call to subroutine "procedure Tint(c:LongWord);" marked as inline is not inlined uWorld.pas(1049,18) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1093,13) Note: Call to subroutine "procedure Tint(c:LongWord);" marked as inline is not inlined uWorld.pas(1095,13) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1103,9) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1185,13) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1364,17) Note: Call to subroutine "procedure Tint(c:LongWord);" marked as inline is not inlined uWorld.pas(1368,17) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1381,17) Note: Call to subroutine "procedure Tint(c:LongWord);" marked as inline is not inlined uWorld.pas(1385,17) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1395,13) Note: Call to subroutine "procedure Tint(c:LongWord);" marked as inline is not inlined uWorld.pas(1399,13) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1863,17) Note: Call to subroutine "procedure untint;" marked as inline is not inlined uWorld.pas(1214,5) Fatal: Internal error 200306031 Fatal: Compilation aborted
Bug#968124: diffoscope: FTBFS with fpc 3.2.0
Source: diffoscope
Version: 155
Severity: serious
Tags: ftbfs sid
X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net
Hi Maintainer
As can be seen on reproducible builds [1], this package FTBFS since
the upload of fpc 3.2.0+dfsg-5 to unstable.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope.html
=== FAILURES ===
_ test_identification __
file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
@skip_unless_tools_exist("ppudump")
def test_identification(file1):
> assert isinstance(file1, PpuFile)
E AssertionError: assert False
E+ where False = isinstance(<
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>,
PpuFile)
file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
tests/comparators/test_ppu.py:51: AssertionError
__ test_diff ___
differences = []
@skip_unless_tool_is_at_least("ppudump", ppudump_version, "3.0.0")
def test_diff(differences):
expected_diff = get_data("ppu_expected_diff")
> assert differences[0].unified_diff == expected_diff
E IndexError: list index out of range
differences = []
expected_diff = ('@@ -15,15 +15,15 @@\n'
' Definitions stored : 121\n'
' Symbols stored : 398\n'
' \n'
' Interface section\n'
' --\n'
' Module Name: CastleGenericLists\n'
' \n'
'-Source file 1 : castlegenericlists.pas 2016/02/17 15:03:46\n'
'+Source file 1 : castlegenericlists.pas 2016/02/17 15:04:53\n'
' Uses unit: System (Crc: 09C1FD4E, IntfcCrc: 3A093E2F, IndCrc: FEDD6E0A)\n'
' Uses unit: objpas (Crc: 663BC437, IntfcCrc: CA7886A2, IndCrc: 64D020AC)\n'
' Uses unit: fgl (Crc: C38E0A5A, IntfcCrc: 470D2834, IndCrc: 0764D076)\n'
' Link unit object file: castlegenericlists.o (static )\n'
' DerefMapsize: 2\n'
' DerefMap[0] = FGL\n'
' DerefMap[1] = SYSTEM\n')
tests/comparators/test_ppu.py:67: IndexError
__ test_compare_non_existing ___
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
@skip_unless_tool_is_at_least("ppudump", ppudump_version, "3.0.0")
def test_compare_non_existing(monkeypatch, file1):
> assert_non_existing(monkeypatch, file1, has_null_source=False)
file1 = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
tests/comparators/test_ppu.py:72:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
fixture = <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
has_null_source = False, has_details = True
def assert_non_existing(
monkeypatch, fixture, has_null_source=True, has_details=True
):
monkeypatch.setattr(Config(), "new_file", True)
assert Config().new_file, "Did not get patched"
difference = fixture.compare(MissingFile("/nonexisting", fixture))
assert difference.source2 == "/nonexisting"
> assert not has_details or len(difference.details) > 0
E AssertionError
difference =
fixture= <
/build/1st/diffoscope-155/.pybuild/cpython3_3.8/build/tests/data/test1.ppu>
has_details = True
has_null_source = False
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1522be2520>
tests/utils/nonexisting.py:35: AssertionError
Bug#968121: ddrescueview: FTBFS with fpc 3.2.0
Source: ddrescueview Version: 0.4~alpha3-3 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ddrescueview.html (3104) Compiling Parser.pas /build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(78,56) Error: (5098) Record or object type expected /build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(79,46) Error: (5098) Record or object type expected /build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(80,50) Error: (5098) Record or object type expected /build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(81,50) Error: (5098) Record or object type expected /build/1st/ddrescueview-0.4~alpha3/source/Parser.pas(85,1) Fatal: (10026) There were 4 errors compiling module, stopping Fatal: (1018) Compilation aborted
Processed: Bumping Sphinx v3 bugs severities to RC
Processing commands for cont...@bugs.debian.org:
> # Sphinx 3.2 is in unstable now
> severity 963633 serious
Bug #963633 {Done: Dmitry Shachnev } [src:breathe] breathe:
FTBFS with Sphinx 3.1: TypeError: __init__() takes 2 positional arguments but 3
were given
Bug #963638 {Done: Dmitry Shachnev } [src:breathe]
liborcus: FTBFS with Sphinx 3.1: TypeError: __init__() takes 2 positional
arguments but 3 were given
Bug #963641 {Done: Dmitry Shachnev } [src:breathe]
libixion: FTBFS with Sphinx 3.1: TypeError: __init__() takes 2 positional
arguments but 3 were given
Bug #963657 {Done: Dmitry Shachnev } [src:breathe] dballe:
FTBFS with Sphinx 3.1: TypeError: __init__() takes 2 positional arguments but 3
were given
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 963634 serious
Bug #963634 [src:aodh] aodh: FTBFS with Sphinx 3.1: Could not import extension
wsmeext.sphinxext (exception: cannot import name 'l_' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Severity set to 'serious' from 'important'
> severity 963635 serious
Bug #963635 [src:h5py] h5py: FTBFS with Sphinx 3.1: sed: no input files
Severity set to 'serious' from 'important'
> severity 963636 serious
Bug #963636 [src:linux] linux: FTBFS with Sphinx 3.1: Could not import
extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from
'sphinx.domains.c' (/usr/lib/python3/dist-packages/sphinx/domains/c.py))
Severity set to 'serious' from 'important'
> severity 963637 serious
Bug #963637 [src:rdkit] rdkit: FTBFS with Sphinx 3.1: ! LaTeX Error: Too deeply
nested.
Severity set to 'serious' from 'important'
> severity 963639 serious
Bug #963639 [src:pygame] pygame: FTBFS with Sphinx 3.1: Invalid C declaration:
Expected identifier in nested name. [error at 9] PyObject \*pgExc_BufferError
Severity set to 'serious' from 'important'
> severity 963640 serious
Bug #963640 [src:jansson] jansson: FTBFS with Sphinx 3.1: TypeError:
add_directive() takes from 3 to 4 positional arguments but 5 were given
Severity set to 'serious' from 'important'
> severity 963643 serious
Bug #963643 [src:gammu] gammu: FTBFS with Sphinx 3.1: Could not import
extension configext (exception: cannot import name 'l_' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Severity set to 'serious' from 'important'
> severity 963644 serious
Bug #963644 [src:alembic] alembic: FTBFS with Sphinx 3.1: AttributeError:
'tuple' object has no attribute 'docname'
Severity set to 'serious' from 'important'
> severity 963645 serious
Bug #963645 [src:libcork] libcork: FTBFS with Sphinx 3.1: assert
symbol.siblingAbove.siblingBelow is None
Severity set to 'serious' from 'important'
> severity 963646 serious
Bug #963646 [src:dynare] dynare: FTBFS with Sphinx 3.1: ImportError: cannot
import name 'l_' from 'sphinx.locale'
(/usr/lib/python3/dist-packages/sphinx/locale/__init__.py)
Severity set to 'serious' from 'important'
> severity 963648 serious
Bug #963648 [src:nghttp2] nghttp2: FTBFS with Sphinx 3.1: Could not import
extension sphinxcontrib.rubydomain (exception: cannot import name 'l_' from
'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
Severity set to 'serious' from 'important'
> severity 963649 serious
Bug #963649 [src:sqlalchemy] sqlalchemy: FTBFS with Sphinx 3.1: AttributeError:
'tuple' object has no attribute 'docname'
Severity set to 'serious' from 'important'
> severity 963650 serious
Bug #963650 [src:mako] mako: FTBFS with Sphinx 3.1: AttributeError: 'tuple'
object has no attribute 'docname'
Severity set to 'serious' from 'important'
> severity 963651 serious
Bug #963651 [src:morse-simulator] morse-simulator: FTBFS with Sphinx 3.1: Theme
error: An error happened in rendering the page morse.
Severity set to 'serious' from 'important'
> severity 963652 serious
Bug #963652 [src:python-m2r] python-m2r: FTBFS with Sphinx 3.1: TypeError:
add_source_parser() takes 2 positional arguments but 3 were given
Severity set to 'serious' from 'important'
> severity 963654 serious
Bug #963654 [src:pillow] pillow: FTBFS with Sphinx 3.1:
/<>/docs/conf.py:292: RemovedInSphinx40Warning: The
app.add_javascript() is deprecated. Please use app.add_js_file() instead.
Severity set to 'serious' from 'important'
> severity 963655 serious
Bug #963655 [src:python-apt] python-apt: FTBFS with Sphinx 3.1: Invalid C
declaration: Expected end of definition. [error at 10] pkgAcquire::Item
Severity set to 'serious' from 'important'
> severity 963656 serious
Bug #963656 [src:python-dogpile.cache] python-dogpile.cache: FTBFS with Sphinx
3.1: AttributeError: 'tuple' object has no attribute 'docname'
Severity set to 'serious' from 'important'
> severity 963658 serious
Bug #963658 [src:urwid] urwid: FTBFS with Sphinx 3.1: Theme error: An error
happened in rendering the page index.
Bug#968120: castle-game-engine: FTBFS with fpc 3.2.0
Source: castle-game-engine Version: 6.4+dfsg1-4 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/castle-game-engine.html Compiling ./src/base/castleutils.pas castleutils_struct_list.inc(27,12) Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" castleutils.pas(121,1) Fatal: There were 8 errors compiling module, stopping Fatal: Compilation aborted
Bug#958010: marked as done (yubikey-personalization: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 11:49:51 + with message-id and subject line Bug#958010: fixed in yubikey-personalization 1.20.0-2.1 has caused the Debian Bug report #958010, regarding yubikey-personalization: ftbfs with GCC-10 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.) -- 958010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:yubikey-personalization Version: 1.20.0-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/yubikey-personalization_1.20.0-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] gcc -DPACKAGE_NAME=\"yubikey-personalization\" -DPACKAGE_TARNAME=\"ykpers\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"yubikey-personalization\ 1.20.0\" -DPACKAGE_BUGREPORT=\"yubico-de...@googlegroups.com\" -DPACKAGE_URL=\"https://developers.yubico.com/yubikey-personalization/\; -DPACKAGE=\"ykpers\" -DVERSION=\"1.20.0\" -DHAVE_PTHREAD=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBYUBIKEY=1 -DHAVE_JSON_OBJECT_TO_JSON_STRING_EXT=1 -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_INLINE_ASM=1 -I. -I.. -I../ykcore -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/json-c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -c -o ykpersonalize.o ../ykpersonalize.c /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"yubikey-personalization\" -DPACKAGE_TARNAME=\"ykpers\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"yubikey-personalization\ 1.20.0\" -DPACKAGE_BUGREPORT=\"yubico-de...@googlegroups.com\" -DPACKAGE_URL=\"https://developers.yubico.com/yubikey-personalization/\; -DPACKAGE=\"ykpers\" -DVERSION=\"1.20.0\" -DHAVE_PTHREAD=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBYUBIKEY=1 -DHAVE_JSON_OBJECT_TO_JSON_STRING_EXT=1 -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_INLINE_ASM=1 -I. -I.. -I../ykcore -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/json-c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -c -o ykpers.lo ../ykpers.c /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"yubikey-personalization\" -DPACKAGE_TARNAME=\"ykpers\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"yubikey-personalization\ 1.20.0\" -DPACKAGE_BUGREPORT=\"yubico-de...@googlegroups.com\" -DPACKAGE_URL=\"https://developers.yubico.com/yubikey-personalization/\; -DPACKAGE=\"ykpers\" -DVERSION=\"1.20.0\" -DHAVE_PTHREAD=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBYUBIKEY=1 -DHAVE_JSON_OBJECT_TO_JSON_STRING_EXT=1 -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_INLINE_ASM=1 -I. -I.. -I../ykcore -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/json-c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security
Bug#966606: marked as done (yubikey-personalization: patch for newer json-c)
Your message dated Sun, 09 Aug 2020 11:49:51 + with message-id and subject line Bug#966606: fixed in yubikey-personalization 1.20.0-2.1 has caused the Debian Bug report #966606, regarding yubikey-personalization: patch for newer json-c 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.) -- 966606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yubikey-personalization Version: 1.20.0-2 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc. Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 Index: yubikey-personalization-1.20.0/ykpers-json.c === --- yubikey-personalization-1.20.0.orig/ykpers-json.c +++ yubikey-personalization-1.20.0/ykpers-json.c @@ -36,6 +36,14 @@ #include #include +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define yk_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, ) #else G. --- End Message --- --- Begin Message --- Source: yubikey-personalization Source-Version: 1.20.0-2.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of yubikey-personalization, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated yubikey-personalization 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, 07 Aug 2020 13:21:24 +0200 Source: yubikey-personalization Architecture: source Version: 1.20.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Sebastian Ramacher Closes: 958010 966606 Changes: yubikey-personalization (1.20.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Apply upstream patches to fix build with GCC 10 and json-c 0.14 and newer (Closes: #958010, #966606) Checksums-Sha1: 96f2909939c363a79e852c6a20724a6e881b0891 2546 yubikey-personalization_1.20.0-2.1.dsc 959a66dd4b89e9dc053cac8d0c96e4cb234841b8 45420 yubikey-personalization_1.20.0-2.1.debian.tar.xz Checksums-Sha256: 7f1cb5e503da86dfe29181cd9eef9f281202badb837d09f79f7a0ad57b1478f3 2546 yubikey-personalization_1.20.0-2.1.dsc ec3e76fd7956972d0edfedadb89a3ca7a7a1a89181b6a9a30954704363023388 45420 yubikey-personalization_1.20.0-2.1.debian.tar.xz Files: c1cc6df45e1e4c9de003a002fdc9c824 2546 utils optional yubikey-personalization_1.20.0-2.1.dsc a049e0b2facb2f7a55a7b6d89540b53b 45420 utils optional yubikey-personalization_1.20.0-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8tOYIACgkQafL8UW6n GZMCtw/+IHiXiviCfU9BCdZE4x6hbYw/PJVYQcbDShfhGOnpIPSiAZmPD6audvjQ XmjZsLMVXchNUCX65qqiHecwOipsn0KLN2m3iMMFdPpK5r1ZXJ/UKKLYrSoujHxD AiUiYd/VhZWjthqz6gvAfGepLmnpSovXmww7pPGJC03PvPAvajoRN6Ps3U/h//kH BaTO+FNbGKacG4p19PyqNZJ/dFDTQJKlzT/SHf6k242zBkGGnovrcqm4pkxIZlTE I9TUmQs8esnwcxHIc9dLlvmOLCz6cozJN53H4oyVisEL2uKpVXdB1DUoQwZwthJV aj5z1K+DLvhELn52obzq1w1zqeOLyrGgrBnIByqpKBid52SNepO/5tLlShUPg3Kw 9T/my7KkfIkpfz0f92OmcEgQVuyDbEEWVMdgRE3JKrA6PjXi948EQuApbr/qbbVw dLzPuH9IFXN+un3mX3xVj2ORrMHRF/GC6U5ijKiybYPHVID4R/ePo+gOlruQk6eN f5MpoV+w/dk1dlL+5P2GzKdq6qzFu13u8oIX1q8Ka1W6b2WAlVDNjv2NjglI3Xpg L1sbIeRkbC/Tl4rMiJomremvPoflX+vLBQVu1FrAnAAlecahs3cIwzH81TFMF6tY WTbApSksCrudlfUpyqp3OOcwa1TzxLZVRqXj5SRGZUVUgefcpR0= =D/sh -END PGP SIGNATURE End Message ---
Bug#966604: marked as done (libu2f-server: patch for newer json-c)
Your message dated Sun, 09 Aug 2020 11:33:34 + with message-id and subject line Bug#966604: fixed in libu2f-server 1.1.0-3.1 has caused the Debian Bug report #966604, regarding libu2f-server: patch for newer json-c 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.) -- 966604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libu2f-server Version: 1.1.10-1 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc. Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 Index: libu2f-server-1.1.0/u2f-server/core.c === --- libu2f-server-1.1.0.orig/u2f-server/core.c +++ libu2f-server-1.1.0/u2f-server/core.c @@ -37,6 +37,14 @@ #include "b64/cdecode.h" #include "sha256.h" +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define u2fs_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, ) #else G. --- End Message --- --- Begin Message --- Source: libu2f-server Source-Version: 1.1.0-3.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libu2f-server, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libu2f-server 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, 07 Aug 2020 13:15:15 +0200 Source: libu2f-server Architecture: source Version: 1.1.0-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Sebastian Ramacher Closes: 966604 Changes: libu2f-server (1.1.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * Apply upstream patch to fix build with json-c 0.14 and newer (Closes: #966604) Checksums-Sha1: fbe69d2fcd463bc29ad8ffee117aa7d720b49c34 2225 libu2f-server_1.1.0-3.1.dsc 301f572d265547a84b005e7bf9c629c0fef792dd 71940 libu2f-server_1.1.0-3.1.debian.tar.xz Checksums-Sha256: f951eebcd3f4bab6cbfd3fda8deec6464e1b57920d862b76d34e2a419a51449f 2225 libu2f-server_1.1.0-3.1.dsc 792e198e024952f56b3b1baa3b378ed6f1ae0aa44736af65523a1fd29a33e7fc 71940 libu2f-server_1.1.0-3.1.debian.tar.xz Files: 6a9ad8c351e316728babe3743a70682f 2225 utils optional libu2f-server_1.1.0-3.1.dsc 870c857170effc7c5bf2cfcbda0edbb9 71940 utils optional libu2f-server_1.1.0-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8tOEQACgkQafL8UW6n GZMNqQ/1EG6xnsP/D94Q9lV+64um8mBH74Z5lF9yTqgr9Wl3OfxlBo7uO/VOO08O 5g0GRl5oWosTJ5JP1UTllkJ5PIygSxZm9CITCzPmyWY4R2uvkAdq8AxRggzwIYj2 d47kcRLLRIbVZxT/SPB29D0eirmB/sBMITnEF4I5+vJMsCGX/waV8BAwEXVvxtQN 5au45tMPwHh19jWQVum1YfjP8tmSOihjP4Z2zN5ARgDT1k4vamL1EZjzOdGHWQCE aEJ+nrvMPfEWlT1/OmAq7pjGiYQW1PD4SrGPfq0FzS0KccmGGc6J+nrjIIUr0mDI 5Po5ejI/9g1pBWNx5qkAMNDqzz3gyX1tXNfzX/lAUdeaKygpnUBjAhPYZZxX7K7R 3czDUx/hGO/k+ySzKcQlvAHfFiYcncCp9jqi63SSC9qfo3tSVjQ7YftsMXfh3T01 U09fDMKGYRqdwcDXz6vjHdjMs7btoltnzMytIgKJ2hMLkysQGK8/MC/JJK0VpycK aKqnRGisvD2EH7sSFiYVUECmUh0SSX0/C67RAlvmY8wUmy8Nggfv0CzrUz/uUzMb 5MOuRyeYmsbnCWs/mIT3Qaamb5MmCspfiXVzy0HS8TaJBawMZlPLe85ebNGTXhGO zJkKXM87w0sc5sY8AySxndYHRC3RxST6FNiXINuILNRxWsB+Bw== =sUfL -END PGP SIGNATURE End Message ---
Bug#966859: marked as done (libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function))
Your message dated Sun, 09 Aug 2020 11:33:29 + with message-id and subject line Bug#966602: fixed in libu2f-host 1.1.10-1.1 has caused the Debian Bug report #966602, regarding libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libu2f-host Version: 1.1.10-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I../gl -I../gl -I./.. -I./.. -I/usr/include/hidapi -I/usr/include/json-c > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o u2fmisc.lo > u2fmisc.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../gl -I../gl -I./.. -I./.. > -I/usr/include/hidapi -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -c authenticate.c -fPIC -DPIC -o > .libs/authenticate.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../gl -I../gl -I./.. -I./.. > -I/usr/include/hidapi -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -c u2fmisc.c -fPIC -DPIC -o .libs/u2fmisc.o > u2fmisc.c: In function 'prepare_origin': > u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function) > 117 | if (u2fh_json_object_object_get (jo, "appId", k) == FALSE) > | ^ > u2fmisc.c:117:55: note: each undeclared identifier is reported only once for > each function it appears in > u2fmisc.c: In function 'get_fixed_json_data': > u2fmisc.c:393:51: error: 'FALSE' undeclared (first use in this function) > 393 | if (u2fh_json_object_object_get (jo, key, k) == FALSE) > | ^ > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../gl -I../gl -I./.. -I./.. > -I/usr/include/hidapi -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -c devs.c -o devs.o >/dev/null 2>&1 > make[4]: *** [Makefile:684: u2fmisc.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/libu2f-host_1.1.10-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libu2f-host Source-Version: 1.1.10-1.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libu2f-host, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libu2f-host 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, 07 Aug 2020 13:09:25 +0200 Source: libu2f-host Architecture: source Version: 1.1.10-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Sebastian Ramacher Closes: 966602 Changes: libu2f-host (1.1.10-1.1) unstable; urgency=medium . * Non-maintainer upload. * Apply upstream patch for compatibility with json-c 0.14 and newer (Closes: #966602) Checksums-Sha1: efa3425dc3e5c743c078b047e7fbfca311a6e993 2397 libu2f-host_1.1.10-1.1.dsc e3961be6870cd9be4aee2a572464a43354fdbe00 50392 libu2f-host_1.1.10-1.1.debian.tar.xz
Processed: 0ad
Processing commands for cont...@bugs.debian.org: > forwarded 967118 https://trac.wildfiregames.com/ticket/5694 Bug #967118 [src:0ad] 0ad: Unversioned Python removal in sid/bullseye Set Bug forwarded-to-address to 'https://trac.wildfiregames.com/ticket/5694'. > tags 967118 upstream Bug #967118 [src:0ad] 0ad: Unversioned Python removal in sid/bullseye Added tag(s) upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 967118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967118: 0ad: Unversioned Python removal in sid/bullseye
I tried to rebuild 0ad without python installed. The build fails with: [...] Building SpiderMonkey... SpiderMonkey build options: --enable-shared-js --disable-tests --without-intl-api --enable-shared-js --disable-tests --without-intl-api [...] checking for full perl installation... yes checking for python2.7... no checking for python... no configure: error: python was not found in $PATH [...] This is with SpiderMonkey from mozjs-38.2.1. The problem should be solved when 0ad will support a more recent version of SpiderMonkey. The problem is already knwon upstream. https://trac.wildfiregames.com/ticket/5694 Bye On Tue, 04 Aug 2020 09:27:36 + Matthias Klose wrote: > Package: src:0ad > Version: 0.0.23.1-4 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > We will keep some Python2 package as discussed in > https://lists.debian.org/debian-python/2020/07/msg00039.html > but removing the unversioned python packages python-minimal, python, > python-dev, python-dbg, python-doc. > > Your package either build-depends, depends on one of those packages. > Please either convert these packages to Python3, or if that is not > possible, replaces the dependencies on the unversioned Python > packages with one of the python2 dependencies (python2, python2-dev, > python2-dbg, python2-doc). > > Please check for dependencies, build dependencies AND autopkg tests. > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-pyt...@lists.debian.org mailing list. > >
Bug#966602: marked as done (libu2f-host: patch for newer json-c)
Your message dated Sun, 09 Aug 2020 11:33:29 + with message-id and subject line Bug#966602: fixed in libu2f-host 1.1.10-1.1 has caused the Debian Bug report #966602, regarding libu2f-host: patch for newer json-c 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.) -- 966602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libu2f-host Version: 1.1.10-1 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 --- libu2f-host-1.1.10.orig/u2f-host/u2fmisc.c +++ libu2f-host-1.1.10/u2f-host/u2fmisc.c @@ -26,6 +26,14 @@ #define HID_TIMEOUT 2 #define HID_MAX_TIMEOUT 4096 +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define u2fh_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, ) #else G. --- End Message --- --- Begin Message --- Source: libu2f-host Source-Version: 1.1.10-1.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libu2f-host, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libu2f-host 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, 07 Aug 2020 13:09:25 +0200 Source: libu2f-host Architecture: source Version: 1.1.10-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Sebastian Ramacher Closes: 966602 Changes: libu2f-host (1.1.10-1.1) unstable; urgency=medium . * Non-maintainer upload. * Apply upstream patch for compatibility with json-c 0.14 and newer (Closes: #966602) Checksums-Sha1: efa3425dc3e5c743c078b047e7fbfca311a6e993 2397 libu2f-host_1.1.10-1.1.dsc e3961be6870cd9be4aee2a572464a43354fdbe00 50392 libu2f-host_1.1.10-1.1.debian.tar.xz Checksums-Sha256: c76c11cb93209a98f61ff2b3a1a326dfa4ffe45da34ba4ddc3c2b32f24217b87 2397 libu2f-host_1.1.10-1.1.dsc f1d77f4415de076013b7d7c57c08474c2192889b05beb4bbed965fa3852465a1 50392 libu2f-host_1.1.10-1.1.debian.tar.xz Files: 5dc4127fee0fe6bd63dcc1559b900684 2397 utils optional libu2f-host_1.1.10-1.1.dsc 9fc601015679967b08d851152ce9f3fc 50392 utils optional libu2f-host_1.1.10-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8tNzIACgkQafL8UW6n GZOvRQ//QiazaaQMzESiKVdJT6tZEZoXHha4dHrZ3O/3IbqOHYn1+gU7HD2kCMdb ouE+fNsV4mck+1eLuyp6Ll/6jIV2pb0kqB5upB6YDzWKJZFF5j41Rmfz895udrMP Zlm28PA4NBG1eEdlKuUWajpc0W6xCMFyM/91c/5/jZ7BV590bdCf7/ng12aDCFPi +LfE7aPO7XpC8L2rDYgdbJHrX/7o+NeDicbOU/aQeXkLryZNGoKyi4GOTgx7fGLZ 9AMdsr3UWkqrKf1/hsYr6h0TqXY/jkqPmcYtid9KHNjGHfWlEMSd3hzXZDzEfnUa KPRy6GrNU+hnJgP0qPxtQfxfotlPb2+BTftFg5n27fcPIRtQWEkKnNn4M6U6THxu 97iq3iY3Z4h5C4gTh/1I0mYU9zD0lWf7n6Z3Khh9efbq3MoX5WlxAJVu+yQm+dHc KIioaHAEJRijKLvQMYNr2ZsQvxgRyznVClwmW0iEyv49z8ylbpgE5ZM7ZygH8ruW VmsZezKaKG2iwKy6yT9ypvoL+ozm09DXuw+ErHSaf2CHt8CTxnXDm58CrMuC/Za0 ZzrtOpfwvQLdSxq29l3m2SjfoNwis4BpngSoTDqNTJY3a4Ti6luErAG6QCg1b5Fm XUUapr6yf5vnLJ5ctQuaeQlISSqZ5GQIj4JbhOjQd6UO5AGhQ2Y= =q28c -END PGP SIGNATURE End Message ---
Bug#966887: marked as done (libu2f-server: FTBFS: core.c:480:58: error: ‘FALSE’ undeclared (first use in this function))
Your message dated Sun, 09 Aug 2020 11:33:34 + with message-id and subject line Bug#966604: fixed in libu2f-server 1.1.0-3.1 has caused the Debian Bug report #966604, regarding libu2f-server: FTBFS: core.c:480:58: error: ‘FALSE’ undeclared (first use in this function) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libu2f-server Version: 1.1.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc > -DPACKAGE_NAME=\"libu2f-server\" -DPACKAGE_TARNAME=\"libu2f-server\" > -DPACKAGE_VERSION=\"1.1.0\" -DPACKAGE_STRING=\"libu2f-server\ 1.1.0\" > -DPACKAGE_BUGREPORT=\"https://github.com/Yubico/libu2f-server/issues\; > -DPACKAGE_URL=\"https://developers.yubico.com/libu2f-server\; > -DPACKAGE=\"libu2f-server\" -DVERSION=\"1.1.0\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 > -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -I. -I./.. -I./.. > -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o core.lo core.c > libtool: compile: gcc -DPACKAGE_NAME=\"libu2f-server\" > -DPACKAGE_TARNAME=\"libu2f-server\" -DPACKAGE_VERSION=\"1.1.0\" > "-DPACKAGE_STRING=\"libu2f-server 1.1.0\"" > -DPACKAGE_BUGREPORT=\"https://github.com/Yubico/libu2f-server/issues\; > -DPACKAGE_URL=\"https://developers.yubico.com/libu2f-server\; > -DPACKAGE=\"libu2f-server\" -DVERSION=\"1.1.0\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 > -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -I. -I./.. -I./.. > -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c core.c -fPIC -DPIC -o .libs/core.o > libtool: compile: gcc -DPACKAGE_NAME=\"libu2f-server\" > -DPACKAGE_TARNAME=\"libu2f-server\" -DPACKAGE_VERSION=\"1.1.0\" > "-DPACKAGE_STRING=\"libu2f-server 1.1.0\"" > -DPACKAGE_BUGREPORT=\"https://github.com/Yubico/libu2f-server/issues\; > -DPACKAGE_URL=\"https://developers.yubico.com/libu2f-server\; > -DPACKAGE=\"libu2f-server\" -DVERSION=\"1.1.0\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 > -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -I. -I./.. -I./.. > -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c version.c -fPIC -DPIC -o .libs/version.o > libtool: compile: gcc -DPACKAGE_NAME=\"libu2f-server\" > -DPACKAGE_TARNAME=\"libu2f-server\" -DPACKAGE_VERSION=\"1.1.0\" > "-DPACKAGE_STRING=\"libu2f-server 1.1.0\"" > -DPACKAGE_BUGREPORT=\"https://github.com/Yubico/libu2f-server/issues\; > -DPACKAGE_URL=\"https://developers.yubico.com/libu2f-server\; > -DPACKAGE=\"libu2f-server\" -DVERSION=\"1.1.0\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 > -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -I. -I./.. -I./.. > -I/usr/include/json-c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c error.c -fPIC -DPIC -o .libs/error.o > libtool: compile: gcc
Bug#957580: marked as done (ncdu: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 11:18:32 +
with message-id
and subject line Bug#957580: fixed in ncdu 1.15.1-1
has caused the Debian Bug report #957580,
regarding ncdu: ftbfs with GCC-10
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.)
--
957580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ncdu
Version: 1.14.1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ncdu_1.14.1-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
| ^~~~
src/util.c:428:5: warning: ignoring return value of ‘read’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
428 | read(0, buf, sizeof(buf));\
| ^
src/util.c:432:30: note: in expansion of macro ‘wrap_oom’
432 | void *xmalloc(size_t size) { wrap_oom(malloc(size)) }
| ^~~~
src/util.c: In function ‘xcalloc’:
src/util.c:427:5: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
427 | write(2, oom_msg, sizeof(oom_msg));\
| ^~
src/util.c:433:40: note: in expansion of macro ‘wrap_oom’
433 | void *xcalloc(size_t n, size_t size) { wrap_oom(calloc(n, size)) }
|^~~~
src/util.c:428:5: warning: ignoring return value of ‘read’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
428 | read(0, buf, sizeof(buf));\
| ^
src/util.c:433:40: note: in expansion of macro ‘wrap_oom’
433 | void *xcalloc(size_t n, size_t size) { wrap_oom(calloc(n, size)) }
|^~~~
src/util.c: In function ‘xrealloc’:
src/util.c:427:5: warning: ignoring return value of ‘write’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
427 | write(2, oom_msg, sizeof(oom_msg));\
| ^~
src/util.c:434:42: note: in expansion of macro ‘wrap_oom’
434 | void *xrealloc(void *mem, size_t size) { wrap_oom(realloc(mem, size)) }
| ^~~~
src/util.c:428:5: warning: ignoring return value of ‘read’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
428 | read(0, buf, sizeof(buf));\
| ^
src/util.c:434:42: note: in expansion of macro ‘wrap_oom’
434 | void *xrealloc(void *mem, size_t size) { wrap_oom(realloc(mem, size)) }
| ^~~~
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wl,-z,relro -o ncdu src/browser.o
src/delete.o src/dirlist.o src/dir_common.o src/dir_export.o src/dir_import.o
src/dir_mem.o src/dir_scan.o src/exclude.o src/help.o src/shell.o src/quit.o
src/main.o src/path.o src/util.o -lncursesw
/usr/bin/ld: src/delete.o:./src/dir.h:106: multiple definition of
`dir_process'; src/browser.o:./src/dir.h:106: first defined here
/usr/bin/ld: src/delete.o:(.bss+0x8): multiple definition of `confirm_quit';
src/browser.o:(.bss+0x8): first defined here
/usr/bin/ld: src/dirlist.o:./src/dir.h:106: multiple definition of
`dir_process'; src/browser.o:./src/dir.h:106: first defined here
/usr/bin/ld: src/dirlist.o:(.bss+0x30): multiple definition of `confirm_quit';
src/browser.o:(.bss+0x8): first
Bug#957430: closing 957430
close 957430 6.5.1-3 thanks
Bug#957041: marked as done (bindfs: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 10:18:28 + with message-id and subject line Bug#957041: fixed in bindfs 1.14.7-1 has caused the Debian Bug report #957041, regarding bindfs: ftbfs with GCC-10 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.) -- 957041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bindfs Version: 1.14.1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/bindfs_1.14.1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for lutimes... yes checking for utimensat... yes checking for setxattr... yes checking for getxattr... yes checking for listxattr... yes checking for removexattr... yes checking for lsetxattr... yes checking for lgetxattr... yes checking for llistxattr... yes checking for lremovexattr... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for fuse... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating tests/internals/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o bindfs.o bindfs.c gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o debug.o debug.c gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o permchain.o permchain.c gcc -DHAVE_CONFIG_H -I. -I..
Processed: closing 957430
Processing commands for cont...@bugs.debian.org: > close 957430 6.5.1-3 Bug #957430 [src:libccp4] libccp4: ftbfs with GCC-10 The source 'libccp4' and version '6.5.1-3' do not appear to match any binary packages Marked as fixed in versions libccp4/6.5.1-3. Bug #957430 [src:libccp4] libccp4: ftbfs with GCC-10 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 957430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936326: marked as done (configparser: Python2 removal in sid/bullseye)
Your message dated Sun, 9 Aug 2020 11:56:54 +0200 with message-id <05669e4d-f99e-de04-44c2-f75a40c84...@debian.org> and subject line Re: configparser: Python2 removal in sid/bullseye has caused the Debian Bug report #936326, regarding configparser: Python2 removal in sid/bullseye 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.) -- 936326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:configparser Version: 3.5.0b2-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:configparser If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 3.5.0b2-3.1 Fixed.--- End Message ---
Processed: Re: octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type
Processing control commands:
> fixed -1 2.9.0-3
Bug #964673 {Done: Rafael Laboissière }
[src:octave-symbolic] octave-symbolic: FTBFS: ValueError: octoutput does not
know how to export type
Marked as fixed in versions octave-symbolic/2.9.0-3.
--
964673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966949: marked as done (kjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 09 Aug 2020 09:19:38 + with message-id and subject line Bug#966949: fixed in kjs 5.70.0-2 has caused the Debian Bug report #966949, regarding kjs: FTBFS: 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.) -- 966949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kjs Version: 5.70.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > chmod +x debian/libkf5kjs-dev/usr/share/kf5/kjs/create_hash_table > dh_fixperms > make[1]: Leaving directory '/<>' >dh_missing -O--buildsystem=kf5 >dh_dwz -a -O--buildsystem=kf5 >dh_strip -a -O--buildsystem=kf5 >dh_makeshlibs -a -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 > 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/libkf5js5/DEBIAN/symbols doesn't match > completely debian/libkf5js5.symbols > --- debian/libkf5js5.symbols (libkf5js5_5.70.0-1_amd64) > +++ dpkg-gensymbolsc07IjD 2020-08-02 17:29:22.852024119 + > @@ -117,6 +117,7 @@ > _ZN3KJS13ArrayInstanceD1Ev@Base 4.96.0 > _ZN3KJS13ArrayInstanceD2Ev@Base 4.96.0 > _ZN3KJS13PackageObject4infoE@Base 4.96.0 > + _ZN3KJS14ScopeChainLink5derefEv@Base 5.70.0-1 > _ZN3KJS14UnicodeSupport18setToLowerFunctionEPFiPtiRS1_E@Base 4.96.0 > _ZN3KJS14UnicodeSupport18setToUpperFunctionEPFiPtiRS1_E@Base 4.96.0 > _ZN3KJS14UnicodeSupport19setIdentPartCheckerEPFbiE@Base 4.96.0 > @@ -290,6 +291,8 @@ > _ZN3KJS8JSObject9constructEPNS_9ExecStateERKNS_4ListE@Base 4.96.0 > > _ZN3KJS8JSObject9constructEPNS_9ExecStateERKNS_4ListERKNS_10IdentifierERKNS_7UStringEi@Base > 4.96.0 > _ZN3KJS8JSObject9putDirectERKNS_10IdentifierEii@Base 4.96.0 > + _ZN3KJS8JSObjectC1EPNS_7JSValueE@Base 5.70.0-1 > + _ZN3KJS8JSObjectC2EPNS_7JSValueE@Base 5.70.0-1 > _ZN3KJS8jsStringEPKc@Base 4.96.0 > _ZN3KJS8jsStringEPKci@Base 4.96.0 > _ZN3KJS8jsStringERKNS_7UStringE@Base 4.96.0 > @@ -405,8 +408,8 @@ > _ZNK3KJS7JSValue16toUInt32SlowCaseEPNS_9ExecStateERb@Base 4.96.0 > _ZNK3KJS7JSValue20toIntegerPreserveNaNEPNS_9ExecStateE@Base 4.96.0 > _ZNK3KJS7JSValue7toFloatEPNS_9ExecStateE@Base 4.96.0 > - (optional=gccinternal)_ZNK3KJS7JSValue7toInt32EPNS_9ExecStateE@Base 5.11.0 > - _ZNK3KJS7JSValue8toNumberEPNS_9ExecStateE@Base 5.49.0 > +#MISSING: 5.70.0-1# > (optional=gccinternal)_ZNK3KJS7JSValue7toInt32EPNS_9ExecStateE@Base 5.11.0 > +#MISSING: 5.70.0-1# _ZNK3KJS7JSValue8toNumberEPNS_9ExecStateE@Base 5.49.0 > _ZNK3KJS7JSValue8toObjectEPNS_9ExecStateE@Base 4.96.0 > _ZNK3KJS7JSValue8toStringEPNS_9ExecStateE@Base 5.49.0 > _ZNK3KJS7JSValue8toUInt16EPNS_9ExecStateE@Base 4.96.0 > @@ -450,7 +453,8 @@ > _ZNK3KJS8JSObject9classNameEv@Base 4.96.0 > _ZNK3KJS8JSObject9toBooleanEPNS_9ExecStateE@Base 4.96.0 > _ZNK3KJS9ExecState18lexicalInterpreterEv@Base 4.96.0 > - > (optional=templinst)_ZNSt5dequeIPN3KJS7JSValueESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base > 4.96.0 > +#MISSING: 5.70.0-1# > (optional=templinst)_ZNSt5dequeIPN3KJS7JSValueESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base > 4.96.0 > + _ZNSt5dequeIPN3KJS7JSValueESaIS2_EE17_M_reallocate_mapEmb@Base 5.70.0-1 > _ZTIN14WTFNoncopyable11NoncopyableE@Base 4.96.0 > _ZTIN3KJS11FunctionImpE@Base 4.96.0 > _ZTIN3KJS11InterpreterE@Base 4.96.0 > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: warning: debian/libkf5jsapi5/DEBIAN/symbols doesn't match > completely debian/libkf5jsapi5.symbols > --- debian/libkf5jsapi5.symbols (libkf5jsapi5_5.70.0-1_amd64) > +++ dpkg-gensymbolstajAVo 2020-08-02 17:29:22.964024715 + > @@ -43,6 +43,8 @@ > (optional=gccinternal|arch=!armel !armhf)_ZN3KJS7JSValueD0Ev@Base 4.96.0 > (optional=gccinternal|arch=!armel !armhf)_ZN3KJS7JSValueD1Ev@Base 4.96.0 > (optional=gccinternal|arch=!armel !armhf)_ZN3KJS7JSValueD2Ev@Base 4.96.0 > + _ZN3KJS8JSObjectC1EPNS_7JSValueE@Base 5.70.0-1 > + _ZN3KJS8JSObjectC2EPNS_7JSValueE@Base 5.70.0-1 > _ZN7KJSDateC1EP10KJSContextRK9QDateTime@Base 4.96.0 > _ZN7KJSDateC2EP10KJSContextRK9QDateTime@Base 4.96.0 >
Bug#957400: marked as done (khtml: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 08:48:49 + with message-id and subject line Bug#957400: fixed in khtml 5.70.0-2 has caused the Debian Bug report #957400, regarding khtml: ftbfs with GCC-10 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.) -- 957400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:khtml Version: 5.62.0-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/khtml_5.62.0-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] Normalized debian/libkf5khtml-data/usr/share/locale/th/LC_MESSAGES/khtml5.mo Normalized debian/libkf5khtml-data/usr/share/locale/hr/LC_MESSAGES/khtml5.mo Normalized debian/libkf5khtml-data/usr/share/locale/it/LC_MESSAGES/khtml5.mo Normalized debian/libkf5khtml-data/usr/share/locale/kn/LC_MESSAGES/khtml5.mo dh_compress -X.dcl -X.docbook -X-license -X.tag -X.sty -X.el -O--buildsystem=kf5 dh_fixperms -O--buildsystem=kf5 dh_missing -O--buildsystem=kf5 debian/rules override_dh_strip make[1]: Entering directory '/<>' dh_strip --dbgsym-migration='libkf5khtml5-dbg (<= 5.19.0-1~~)' make[1]: Leaving directory '/<>' dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 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/libkf5khtml5/DEBIAN/symbols doesn't match completely debian/libkf5khtml5.symbols --- debian/libkf5khtml5.symbols (libkf5khtml5_5.62.0-1_amd64) +++ dpkg-gensymbolsDqWHen 2020-02-26 12:19:40.296626599 + @@ -46,8 +46,8 @@ _ZN11KHTMLGlobalC2Ev@Base 4.96.0 _ZN11KHTMLGlobalD1Ev@Base 4.96.0 _ZN11KHTMLGlobalD2Ev@Base 4.96.0 - (optional=templinst)_ZN12KConfigGroup10writeEntryIbEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base 4.100.0 - (optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base 4.100.0 +#MISSING: 5.62.0-1# (optional=templinst)_ZN12KConfigGroup10writeEntryIbEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base 4.100.0 +#MISSING: 5.62.0-1# (optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base 4.100.0 _ZN13KHTMLSettings10avFamiliesE@Base 4.96.0 _ZN13KHTMLSettings11addAdFilterERK7QString@Base 4.96.0 _ZN13KHTMLSettings11adviceToStrENS_17KJavaScriptAdviceE@Base 4.96.0 @@ -1841,6 +1841,7 @@ _ZN3DOMeqERKNS_9DOMStringEPKc@Base 4.96.0 _ZN3DOMeqERKNS_9DOMStringERK7QString@Base 4.96.0 _ZN3DOMeqERKNS_9DOMStringES2_@Base 4.96.0 + _ZN3KJS14ScopeChainLink5derefEv@Base 5.62.0-1 (optional=gccinternal)_ZN3KJS4List6appendEPNS_7JSValueE@Base 5.37.0 (optional=external|arch=!armel !armhf)_ZN3KJS6JSCell4markEv@Base 4.96.0 (optional=gccinternal|arch=!armel !armhf)_ZN3KJS7JSValueD0Ev@Base 5.24.0 @@ -2256,8 +2257,8 @@ (optional=templinst)_ZNK12KConfigGroup9readEntryIbEET_PKcRKS1_@Base 4.100.0 (optional=templinst|arch=!alpha !amd64 !arm64 !hppa !kfreebsd-amd64 !m68k !x32)_ZNK12KConfigGroup9readEntryIbEET_RK7QStringRKS1_@Base 5.37.0 (optional=templinst)_ZNK12KConfigGroup9readEntryIiEET_PKcRKS1_@Base 4.100.0 - (optional=templinst|arch=!amd64 !arm64 !kfreebsd-amd64 !x32)_ZNK12KConfigGroup9readEntryIjEET_PKcRKS1_@Base 4.100.0 -
Processed: tagging 966949
Processing commands for cont...@bugs.debian.org: > tags 966949 + pending Bug #966949 [src:kjs] kjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 966949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957122: marked as done (davfs2: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 08:33:27 + with message-id and subject line Bug#957122: fixed in davfs2 1.6.0-1 has caused the Debian Bug report #957122, regarding davfs2: ftbfs with GCC-10 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.) -- 957122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:davfs2 Version: 1.5.5-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/davfs2_1.5.5-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] dav_coda.c:429:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 429 | dav_node *node = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c: In function ‘coda_create’: dav_coda.c:463:26: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 463 | dav_node *parent = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c:486:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 486 | *((dav_node **) &(out->VFid.opaque[2])) = node; | ~^ dav_coda.c: In function ‘coda_getattr’: dav_coda.c:498:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 498 | dav_node *node = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c: In function ‘coda_lookup’: dav_coda.c:522:26: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 522 | dav_node *parent = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c:543:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 543 | *((dav_node **) &(out->VFid.opaque[2])) = node; | ~^ dav_coda.c: In function ‘coda_mkdir’: dav_coda.c:555:26: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 555 | dav_node *parent = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c:577:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 577 | *((dav_node **) &(out->VFid.opaque[2])) = node; | ~^ dav_coda.c: In function ‘coda_open_by_fd’: dav_coda.c:589:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 589 | dav_node *node = *((dav_node **) &(in->VFid.opaque[2])); | ~^~~~ dav_coda.c: In function ‘coda_root’: dav_coda.c:643:7: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 643 | *((dav_node **) &(out->VFid.opaque[2])) = node; | ~^ dav_coda.c: In function ‘coda_setattr’: dav_coda.c:654:24: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 654 | dav_node *node = *((dav_node **) &(in->VFid.opaque[2])); |
Processed: tagging 957400
Processing commands for cont...@bugs.debian.org: > tags 957400 + pending Bug #957400 [src:khtml] khtml: ftbfs with GCC-10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 957400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957401: marked as done (kcoreaddons: ftbfs with GCC-10)
Your message dated Sun, 09 Aug 2020 08:25:17 + with message-id and subject line Bug#957401: fixed in kcoreaddons 5.70.0-2 has caused the Debian Bug report #957401, regarding kcoreaddons: ftbfs with GCC-10 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.) -- 957401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kcoreaddons Version: 5.62.0-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/kcoreaddons_5.62.0-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] -- Installing: /<>/debian/tmp/usr/share/kf5/licenses/LGPL_V2 -- Installing: /<>/debian/tmp/usr/share/kf5/licenses/LGPL_V21 -- Installing: /<>/debian/tmp/usr/share/kf5/licenses/LGPL_V3 -- Installing: /<>/debian/tmp/usr/share/kf5/licenses/QPL_V1.0 -- Installing: /<>/debian/tmp/usr/share/kf5/licenses/ARTISTIC -- Installing: /<>/debian/tmp/usr/share/mime/packages/kde5.xml -- Installing: /<>/debian/tmp/usr/bin/desktoptojson make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_install -O--buildsystem=kf5 dh_movelibkdeinit -O--buildsystem=kf5 dh_installdocs -O--buildsystem=kf5 dh_installchangelogs -O--buildsystem=kf5 dh_installinit -O--buildsystem=kf5 dh_lintian -O--buildsystem=kf5 dh_perl -O--buildsystem=kf5 dh_link -O--buildsystem=kf5 dh_strip_nondeterminism -O--buildsystem=kf5 dh_compress -X.dcl -X.docbook -X-license -X.tag -X.sty -X.el -O--buildsystem=kf5 dh_fixperms -O--buildsystem=kf5 dh_missing -O--buildsystem=kf5 debian/rules override_dh_strip make[1]: Entering directory '/<>' dh_strip --dbgsym-migration='libkf5coreaddons5-dbg (<= 5.19.0-1~~)' make[1]: Leaving directory '/<>' dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5coreaddons5/DEBIAN/symbols doesn't match completely debian/libkf5coreaddons5.symbols --- debian/libkf5coreaddons5.symbols (libkf5coreaddons5_5.62.0-1_amd64) +++ dpkg-gensymbolsr9AFZl 2020-02-26 12:32:28.803935950 + @@ -47,9 +47,9 @@ _ZN10KAboutDataaSERKS_@Base 4.97.0 _ZN10KFileUtils11suggestNameERK4QUrlRK7QString@Base 5.61.0 _ZN10KOSReleaseC1ERK7QString@Base 5.61.0 - _ZN10KOSReleaseC2ERK7QString@Base 5.61.0 +#MISSING: 5.62.0-1# _ZN10KOSReleaseC2ERK7QString@Base 5.61.0 _ZN10KOSReleaseD1Ev@Base 5.61.0 - _ZN10KOSReleaseD2Ev@Base 5.61.0 +#MISSING: 5.62.0-1# _ZN10KOSReleaseD2Ev@Base 5.61.0 _ZN10KUserGroup13allGroupNamesEj@Base 4.98.0 _ZN10KUserGroup9allGroupsEj@Base 4.98.0 _ZN10KUserGroupC1E8KGroupId@Base 4.98.0 @@ -277,9 +277,9 @@ _ZN16KSharedDataCacheD1Ev@Base 4.97.0 _ZN16KSharedDataCacheD2Ev@Base 4.97.0 _ZN17Kdelibs4MigrationC1Ev@Base 4.99.0 - _ZN17Kdelibs4MigrationC2Ev@Base 4.99.0 +#MISSING: 5.62.0-1# _ZN17Kdelibs4MigrationC2Ev@Base 4.99.0 _ZN17Kdelibs4MigrationD1Ev@Base 4.99.0 - _ZN17Kdelibs4MigrationD2Ev@Base 4.99.0 +#MISSING: 5.62.0-1# _ZN17Kdelibs4MigrationD2Ev@Base 4.99.0 _ZN18KCharMacroExpander16expandPlainMacroERK7QStringiR11QStringList@Base 4.97.0 _ZN18KCharMacroExpander18expandEscapedMacroERK7QStringiR11QStringList@Base 4.97.0 _ZN18KMacroExpanderBase12expandMacrosER7QString@Base 4.97.0 @@ -399,10 +399,10 @@ _ZN7KFormat16staticMetaObjectE@Base 5.2.0+git20140930 _ZN7KFormatC1ERK7QLocale@Base 4.97.0 _ZN7KFormatC1ERKS_@Base 4.97.0 - _ZN7KFormatC2ERK7QLocale@Base 4.97.0 -
Processed: Re: Bug#967932 closed by Matthias Klose (Re: redland-bindings: FTBFS: lots of undefined reference errors from ld)
Processing control commands:
> fixed -1 1.0.17.1+dfsg-1.4
Bug #967932 {Done: Matthias Klose } [src:redland-bindings]
redland-bindings: FTBFS: lots of undefined reference errors from ld
Marked as fixed in versions redland-bindings/1.0.17.1+dfsg-1.4.
--
967932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#967932: closed by Matthias Klose (Re: redland-bindings: FTBFS: lots of undefined reference errors from ld)
Control: fixed -1 1.0.17.1+dfsg-1.4 On 2020-08-08 19:42 +, Matthias Klose wrote: > not sure what the bug submitter was trying, but 1.0.17.1+dfsg-1.4 just built > fine. I tried to build the package with sbuild in a sid chroot, which failed. Apparently some change in dh-python made it necessary to configure with --with-python=python2 as you did in 1.0.17.1+dfsg-1.4. I can confirm this version builds for me. Thanks, Sven
Processed: tagging 957401
Processing commands for cont...@bugs.debian.org: > tags 957401 + pending Bug #957401 [src:kcoreaddons] kcoreaddons: ftbfs with GCC-10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 957401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967183: marked as done (node-crc: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 09 Aug 2020 06:18:45 + with message-id and subject line Bug#967183: fixed in node-crc 3.8.0+ds-3 has caused the Debian Bug report #967183, regarding node-crc: Unversioned Python removal in sid/bullseye 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.) -- 967183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-crc Version: 3.8.0+ds-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: node-crc Source-Version: 3.8.0+ds-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-crc, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-crc 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, 09 Aug 2020 07:52:06 +0200 Source: node-crc Architecture: source Version: 3.8.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 953219 967183 Changes: node-crc (3.8.0+ds-3) unstable; urgency=medium . * Team upload * Replace python by python3 (Closes: #967183, #953219) Checksums-Sha1: cd6c115910e65cf2d5710c4ac99470f91a953b03 2217 node-crc_3.8.0+ds-3.dsc 0414b2c018b8ed2e11a2cb8e431a10b4d154d938 3708 node-crc_3.8.0+ds-3.debian.tar.xz Checksums-Sha256: cfcbb1b1417f219ab2a7c7c394d50d40fe235c08c8d302e57eb97ea893889a00 2217 node-crc_3.8.0+ds-3.dsc cfb0ee4cdb588cbe248857adab9191924e529e135664b7d79eefd6383082f81a 3708 node-crc_3.8.0+ds-3.debian.tar.xz Files: 2ca2273e726796ba7222913a562964ef 2217 javascript optional node-crc_3.8.0+ds-3.dsc 0e892a0ff3871cc0db6a8de810b8c2fd 3708 javascript optional node-crc_3.8.0+ds-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl8vj9UACgkQ9tdMp8mZ 7uljIBAAg+wsH9e0+rbllwnMOk6m2Douwxl061O1U20IZIVqg5f1fjybxQLKLuc+ UC1n8el0zKm3cJpal+onJARQQy34BwFPhU6Qg+CLwcyMKuV0l0fEp7IdZAbzdLCv PktnhvVjTexkKbUvyo7cUS0X7JNs8ftaPubBsgrXsJvzXMa7rpopUBznlOeENjnh XTHbWWMviqb0QUsPW11lpwC7XOJgrJ+NhbzvghcZ+/0LGh7Yufwq9bb30Oo7Pq1B HEIhC1bTpKaWZa+18gkTmLvG9OevJpLZ7Ij8wqvbyHBMR/h6kTZjflCXmQ0XifL+ a5+udMdrCRRsNcAt4d4KMt355mKGblRamsIP9QkurnpUIZMqyJhCqESt+mdWCyG1 FN37q46up7oHMy5q074q2sxnSEkMVwRCSpNsCnQC7HiVFp+dbgc34cMIS5MOVuZ2 xXUHnkbpT0wchjOGoqXqjW7mGrLxuUXJnNrpeY3pTxXWyOfkZV7GUrveIFJojk1+ 7hWnPbousmeVeVVnerAKI41P4Xc96U5FWhpXfQipgbdl4HskPfSPSu3lAzi3Uczp HDQ0UqW7zHWyN7OvEpomDw+Y5fyMu+JlVe6oQ/TOC4bumjQZCbBEs0ahRawuJNNN ENVcI4W1mb8DpaJgUYWC9+avtypKy7p8Cuqq+fF9FJ2fjZhTB+A= =26Dy -END PGP SIGNATURE End Message ---
Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory)
Your message dated Sun, 09 Aug 2020 06:18:40 + with message-id and subject line Bug#966903: fixed in gecode 6.2.0-5 has caused the Debian Bug report #966903, regarding gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: 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.) -- 966903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gecode Version: 6.2.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -I. -fcx-limited-range -fno-signaling-nans -fno-rounding-math > -ffinite-math-only -fno-math-errno -fno-strict-aliasing -fvisibility=hidden > -ggdb -std=c++11 -pipe -Wall -Wextra -fPIC -pthread -DNDEBUG -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -O3 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 > -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB > -DQT_CORE_LIB -I. -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport > -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets > -I/usr/include/x86_64-linux-gnu/qt5/QtGui > -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ \ > \ > -c -o gecode/flatzinc/parser.tab.o gecode/flatzinc/parser.tab.cpp > gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such > file or directory > 526 | #include "parser.tab.hpp" > | ^~~~ > compilation terminated. > make[2]: *** [Makefile:1492: gecode/flatzinc/parser.tab.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/gecode_6.2.0-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: gecode Source-Version: 6.2.0-5 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of gecode, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated gecode 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, 09 Aug 2020 08:34:08 +0300 Source: gecode Architecture: source Version: 6.2.0-5 Distribution: unstable Urgency: medium Maintainer: Kari Pahula Changed-By: Kari Pahula Closes: 966903 Changes: gecode (6.2.0-5) unstable; urgency=medium . * Revert to dh compat 10 to cope with cdbs and dh_systemd_enable. * Leave parser.tab.hpp renaming as parser.tab.hh in place and instead sed the #include in generated parser.tab.cpp file. (Closes: #966903) * Drop obsolete build deps autotools-deb and dh-autoreconf. Checksums-Sha1: 01b3ecfaa7dc02a9f8d855da3ff7014e2d0949db 2127 gecode_6.2.0-5.dsc a9f37a29a9933c46e6032707559223c3f0e4b426 16464 gecode_6.2.0-5.debian.tar.xz 3e900980389edd263e6a71059cf3b6272eca1236 10455 gecode_6.2.0-5_source.buildinfo Checksums-Sha256: fe6b259739e006ee919caaf61f7759b7a3e88e1bbfdc89683491c1c043876a33 2127 gecode_6.2.0-5.dsc d471bc653fd6bce207ff0ad02b0c3dcd91382e7a5b80900e09ad318351f57b53 16464 gecode_6.2.0-5.debian.tar.xz 28ff0898d72065068a970c7c9cf6034e35afc2619a6cfdd703e2e9da9434 10455 gecode_6.2.0-5_source.buildinfo Files: 9d1e5a2941e1a902a93a85d7461c9ca5 2127 libs optional gecode_6.2.0-5.dsc 4d3c85cc6b7530b88a6dbe463ca00e6d 16464 libs optional gecode_6.2.0-5.debian.tar.xz 9ea78f99c32edf84b4a8f07006923929 10455 libs optional gecode_6.2.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECcOX/lMRGGlaUzRFhAhn7p2PJlwFAl8vkM8ACgkQhAhn7p2P
Bug#967183: marked as pending in node-crc
Control: tag -1 pending Hello, Bug #967183 in node-crc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-crc/-/commit/6c0ca21b6b34b12fa8cfc27ad256db8d56dee315 Replace python by python3 Closes: #967183 (this message was generated automatically) -- Greetings https://bugs.debian.org/967183
Processed: Bug#967183 marked as pending in node-crc
Processing control commands: > tag -1 pending Bug #967183 [src:node-crc] node-crc: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
