Bug#957800: marked as done (siridb-server: ftbfs with GCC-10)
Your message dated Mon, 27 Jul 2020 06:03:40 + with message-id and subject line Bug#957800: fixed in siridb-server 2.0.37-1 has caused the Debian Bug report #957800, regarding siridb-server: 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.) -- 957800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:siridb-server Version: 2.0.34-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/siridb-server_2.0.34-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 [...] /usr/bin/ld: ./src/siri/db/re.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/re.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../include/logger/logger.h:26: first defined here /usr/bin/ld: ./src/siri/db/reindex.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/reindex.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../include/logger/logger.h:26: first defined here /usr/bin/ld: ./src/siri/db/replicate.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/replicate.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../include/logger/logger.h:26: first defined here /usr/bin/ld: ./src/siri/db/series.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/series.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../include/logger/logger.h:26: first defined here /usr/bin/ld: ./src/siri/db/server.o:./Release/../include/siri/net/tcp.h:17: multiple definition of `dns_req_family_map'; ./src/siri/service/client.o:./Release/../include/siri/net/tcp.h:17: first defined here /usr/bin/ld: ./src/siri/db/server.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/server.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../include/logger/logger.h:26: first defined here /usr/bin/ld: ./src/siri/db/servers.o:./Release/../include/siri/net/tcp.h:17: multiple definition of `dns_req_family_map'; ./src/siri/service/client.o:./Release/../include/siri/net/tcp.h:17: first defined here /usr/bin/ld: ./src/siri/db/servers.o:./Release/../include/siri/db/time.h:24: multiple definition of `siridb_time_short_map'; ./src/siri/service/account.o:./Release/../include/siri/db/time.h:24: first defined here /usr/bin/ld: ./src/siri/db/servers.o:./Release/../include/logger/logger.h:26: multiple definition of `LOGGER_LEVEL_NAMES'; ./src/xpath/xpath.o:./Release/../inc
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Le 26/07/2020 à 18:54, Pirate Praveen a écrit : > > > On Sun, Jul 26, 2020 at 19:35, Adrian Bunk wrote: >> On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote: >>> I'm wondering if this will require another bootstraping cycle as >>> node-babel7 >>> autopkgtest is also broken and it depends on itself. >> >> If the problem is in node-lodash and gets fixed there, >> shouldn't this fix everything? > > I don't think the problem is in lodash as I can see babel upstream is > already using lodash 4.17.19 in their yarn.lock > https://github.com/babel/babel/blob/f7964a9ac51356f7df6404a25b27ba1cffba1ba7/yarn.lock#L7114 Hi, our lodash build does not provide the same result than npm package. > I think babel needs to use the same version of lodash it was built with > and a breaking change in lodash was released as a minor/patch > release/security release. > > I think it is becoming more and more common to break API during security > releases (we had to face this in rack/rails in ruby team). > > Babel build situation is indeed a mess. the problem is in lodash. > They are dicussing removing lodash from babel though see > https://github.com/babel/babel/pull/11789
Bug#936699: hg-git: Python2 removal in sid/bullseye
On Fri, 30 Aug 2019 07:20:24 + Matthias Klose wrote: > Package: src:hg-git > Version: 0.8.12-1.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal there's a new alpha release from upstream https://foss.heptapod.net/mercurial/hg-git/-/tree/0.9.0a1 which seems to suggest some python3 porting work has been carried out already, further commits on master https://foss.heptapod.net/mercurial/hg-git/-/commits/branch/default may indicate more work is needed -- but it's progress -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#957589: nemo: ftbfs with GCC-10
On Thu, 23 Jul 2020, Fabio Fantoni wrote: > The gcc10 errors are already solved upstream in 4.6: > https://github.com/linuxmint/nemo/commit/c5f66756f0e20f763b67e4a64d7e898411a605c0 > > I not have time to test build with gcc10 now, someone have gcc10 build > of latest nemo to be sure is ok before close this? Same here, will do it in a few days. Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#957089: cjs: ftbfs with GCC-10
Hi Fabio, > I see only symbols "unexpected cases" and not build errors, I not have Yes, that is the problem. Gcc 10 seemingly breaks practically all packages due to symbols changes - I am really surprised that this happens, is this on purpose? I will make updates to the packages after the long weekend we are having here (and a online conference I somehow co-organized). Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#965289: marked as done (timekpr-next: Python2 removal in sid/bullseye)
Your message dated Mon, 27 Jul 2020 04:49:02 + with message-id and subject line Bug#965289: fixed in timekpr-next 0.4.0-2 has caused the Debian Bug report #965289, regarding timekpr-next: 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.) -- 965289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: timekpr-next Version: 0.4.0-1 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, in details: (binary:timekpr-next)Recommends->python-appindicator 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 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: timekpr-next Source-Version: 0.4.0-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of timekpr-next, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated timekpr-next package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Jul 2020 00:27:12 -0400 Source: timekpr-next Architecture: source Version: 0.4.0-2 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Sandro Tosi Closes: 965289 Changes: timekpr-next (0.4.0-2) unstable; urgency=medium . * Team upload. * Drop recommends on python-appindicator, not needed; Closes: #965289 Checksums-Sha1: 383a957c7409e8c08a31ffdaa36f2f44457561bc 2076 timekpr-next_0.4.0-2.dsc 75d0210173c63fa8721ded25639f41b17c477160 10068 timekpr-next_0.4.0-2.debian.tar.xz 519f4d4caaa0547fd1908fa82bf8f8d32ff62f4a 10026 timekpr-next_0.4.0-2_source.buildinfo Checksums-Sha256: d8f898fb042a326a8301859700a3c5010d91841add495ff8ee761e1652ebd288 2076 timekpr-next_0.4.0-2.dsc 944ad827793ca803e8e0e096fed15dd80837d22d75847c3514ed9a9b7bfe325e 10068 timekpr-next_0.4.0-2.debian.tar.xz 65723ee78de78958c9da1a15cbd0a9213620ac0f3d3faa2b9813ee518ed17db1 10026 timekpr-next_0.4.0-2_source.buildinfo Files: 0ef344acaa51830809cbc8e2897b7686 2076 admin optional timekpr-next_0.4.0-2.dsc a65b082db447136082c92a861d7f740e 10068 admin optional timekpr-next_0.4.0-2.debian.tar.xz 8babf3f4f0b6f7a2ee41fd
Bug#939259: webcheck: Python2 removal in sid/bullseye
On Tue, 22 Oct 2019 22:02:22 +0200 Arthur de Jong wrote: > > On Mon, 2019-09-02 at 15:09 +0200, Stefano Rivera wrote: > > 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. > > I would like to do this but it requires some time that I don't have a > lot of available at the moment. Any help will we appreciated. > > The upstream repo has a lot of changes relative to the latest release > because there was a plan to improve performance and make the tool a bit > more lightweight (most of that was done). While the code in the repo > should be reasonably stable it is not as nice as it could be and I > would also like to switch to using requests and a few other things but > it kind of lost focus on it :( > > Anyway, help is very welcome. > > I'm also not too adverse to removal from testing to help the Python 2 > migration along. 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? Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936146: archivemail - Python 3 porting
Hey Scott and Jonathan, On Thu, 28 May 2020 13:56:59 -0400 (EDT) Scott Talbert wrote: > On Tue, 26 May 2020, Jonathan Dowland wrote: > > >> archivemail seems to be a good candidate to RM due to dead upstream. > >> However, it still has a relatively high popcon, so people seem to be using > >> it. > >> > >> I'm willing to take a stab at porting to Python 3 if anyone is available to > >> test it? The port effort doesn't look that bad at first glance, but I > >> don't use this package. > > > > I'm happy to test anything you produce, but I'd warn you that I think > > it's quite a significant piece of work. From what I remember when I last > > looked at hacking a feature into it (#736327), archivemail uses the > > older of two different APIs provided by the python "mailbox" library, > > and only the newer one was carried forward to Python 3. So moving away > > from that older API is a big part of the work. > > You were right. This was harder than I expected. :) Mainly it is > exactly as you described - the rfc822.Message class (which doesn't exist > in Python 3) does not map exactly to the email.message.Message class. I'm > stuck at the moment with figuring out how to calculate the message size. > In rfc822.Message, you could access the file handle directly and get the > size that way. do you have any plan on completing this port? I'm not a user of archivemail but it looks like it should be removed, not salvaged: * no new upstream releases since 2011 (!) * last upload to debian in 2014 * retired from fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1777616 maybe it's time to let it go? If i dont hear otherwise in a week, i'll file for its removal Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936945: lightyears and python3: issue/pull-request logged upstream
Hey Steve, On Mon, 11 Nov 2019 17:14:00 +0100 Steve Cotton wrote: > Package: src:lightyears > > forwarded 936945 https://github.com/20kly/20kly/issues/2 > tags 936945 + patch upstream > thanks > > Both #936945 and #912488 are about migrating this game to something other than > Python2. The above Github link leads to my fork with a python3-pygame port, > there's another Github fork that's working on a Godot port. > > An old version of my fork's changes is in #912488. Would you be interested in taking over maintenance of this package? it's in rather bad shape and you clearly show interest (at least for the application itself). Cheers, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#947852: marked as done (python3-networkx needs Breaks on packages in buster it breaks)
Your message dated Mon, 27 Jul 2020 03:33:49 + with message-id and subject line Bug#947852: fixed in networkx 2.4-4 has caused the Debian Bug report #947852, regarding python3-networkx needs Breaks on packages in buster it breaks to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: networkx Version: 2.4-2 Severity: serious Control: block -1 by 945390 945392 Control: affects -1 python3-networkx The autopkgtest have shown that python3-networkx breaks older versions of some packages, at least androguard and python3-django-hyperkitty. Breaks on the affected versions in buster are needed to prevent people from ending up with known-broken combinations of packages, e.g. during upgrades or when using backports. --- End Message --- --- Begin Message --- Source: networkx Source-Version: 2.4-4 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of networkx, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated networkx 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, 26 Jul 2020 23:10:54 -0400 Source: networkx Architecture: source Version: 2.4-4 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 947852 963415 Changes: networkx (2.4-4) unstable; urgency=medium . * debian/control - adjust Breaks items as suggested by Adrian Bunk; Closes: #947852 - wrap-and-sort - bump Standards-Version to 4.5.0 (no changes needed) - bump compat to 12 * debian/patches/* - refresh patches * debian/patches/docs-remove-expected_failing_examples.patch - remove the sphinx_gallery expected_failing_examples directive, since plot_parallel_betweenness.py works just fine; Closes: #963415 Checksums-Sha1: 55bfa7a9330cf0223fb2c7191f1e1d66a0a4658e 2597 networkx_2.4-4.dsc 500a1c54eec269310924685f7c7f98f9618c4f6e 15036 networkx_2.4-4.debian.tar.xz 539f13a94949bd34551a9309dba6a8712a841dcb 8735 networkx_2.4-4_source.buildinfo Checksums-Sha256: 7343845b647c5096b789207851d5a989460d871f57a9404ede4ecea8e8b62367 2597 networkx_2.4-4.dsc 680427ce82186fd9d492c96f3b5dfd526201e7cc0a0f00105cb895d7ee7f1128 15036 networkx_2.4-4.debian.tar.xz 925347d4c2da4fc10259e0278a75b003dd8e6815cba12eea978d472a315d0ebd 8735 networkx_2.4-4_source.buildinfo Files: 9801842d965a075bca8229ecfdf35a10 2597 python optional networkx_2.4-4.dsc dead0ba628b3818ec6b9ce7714112b41 15036 python optional networkx_2.4-4.debian.tar.xz 5d9e9c0e3a10e478b027afb4b672891f 8735 python optional networkx_2.4-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8eRdkACgkQh588mTgB qU/vBhAAg+fYsijGTXwFQ90RNSCfRomy0gSa1AhfbbvNBhZlbppfgBHP3+uOOy7W DYGemJoYQMuFFWbXJhV8KtIGKP5a61k0YsqF+sByzNj2QcLawqSIa80zVa4P6ejg 3OqzgoRMn1bhdGWpJTJ28Cw3ak3mM+wcNEvG+nseqAJLfDfrR9b5uEkZ8Bk7DbCV xN7KnMVY+k20RXMYvz43jhm+ynzNv7MZxaaP39BeE2RbqbIPrACg/lbZ/UoPnYAV s1IiE4WxLPCHd1rG/6Z0q2JNtMRNeK40LlXLiXI+AIyVNjsIc0chHHJAdv866Xka d5eY1xgV+ZP2ejWo1Vr8gjcZc+jHOiefIj/Sx2Q7yvsIqPdDlLE55RJuYotVyAFO YWf5TMTGqDdHl6Theje9C+uV0Qd9V49522FkWn9oFavgZMiQ9kj8JsPAW+R2eczk pXz2JF3MbQkcV+TLExGqkDhOf20fCyqO0N+/WEn7rrF8fuaYfxZNwkR6h85iAliY E6jdYCNpU7NvTgdjYeVeLsfo1a/jaeBak17AlVaBv3O6WylmmRDT4Xs4iAi84/IT DuWlrbE6CCDKGAYJod3ZpN4aZWZuaCryc746T0rKR3h9uhra3A37aqwnAZkzZS4Z +AQPHB0LwYCF5KL/P7ng5iIf4tXtO4MvB9tfHrccQt1TVdb45iA= =whLW -END PGP SIGNATURE End Message ---
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Le 20-07-26 à 18 h 01, Pirate Praveen a écrit :
>
>>
>> File in node-lodash unstable package:
>> 4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/
>>
I made a dirty hack to check my theory and it looks like if I patch this
file by replacing 'isArray' with 'Array.IsArray' or if I append 'isArray
= require('./isArray')', I'm able to build broken packages like
node-babel7 or glewlwyd.
The only way I found to patch the package node-lodash is to manually
change the file lodash.js here:
https://salsa.debian.org/js-team/node-lodash/-/blob/master/lodash.js#L3724
and replacing 'isArray' with 'Array.IsArray'.
/Nicolas
Bug#954687: marked as done (networkx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Sun, 26 Jul 2020 22:01:58 -0400 with message-id and subject line Re: Bug#954687: networkx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #954687, regarding networkx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: networkx Version: 2.4-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > File "/<>/examples/advanced/plot_parallel_betweenness.py", > line 53, in betweenness_centrality_parallel > bt_sc = p.map(_betmap, > File "/usr/lib/python3.8/multiprocessing/pool.py", line 364, in map > return self._map_async(func, iterable, mapstar, chunksize).get() > File "/usr/lib/python3.8/multiprocessing/pool.py", line 768, in get > raise self._value > File "/usr/lib/python3.8/multiprocessing/pool.py", line 537, in > _handle_tasks > put(task) > File "/usr/lib/python3.8/multiprocessing/connection.py", line 206, in send > self._send_bytes(_ForkingPickler.dumps(obj)) > File "/usr/lib/python3.8/multiprocessing/reduction.py", line 51, in dumps > cls(buf, protocol).dump(obj) > _pickle.PicklingError: Can't pickle : > attribute lookup _betmap on __main__ failed > > generating gallery for auto_examples/advanced... [100%] > plot_iterated_dynamical_systems.py > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/03/22/networkx_2.4-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 --- > Relevant part (hopefully): > > File "/<>/examples/advanced/plot_parallel_betweenness.py", > > line 53, in betweenness_centrality_parallel > > bt_sc = p.map(_betmap, > > File "/usr/lib/python3.8/multiprocessing/pool.py", line 364, in map > > return self._map_async(func, iterable, mapstar, chunksize).get() > > File "/usr/lib/python3.8/multiprocessing/pool.py", line 768, in get > > raise self._value > > File "/usr/lib/python3.8/multiprocessing/pool.py", line 537, in > > _handle_tasks > > put(task) > > File "/usr/lib/python3.8/multiprocessing/connection.py", line 206, in send > > self._send_bytes(_ForkingPickler.dumps(obj)) > > File "/usr/lib/python3.8/multiprocessing/reduction.py", line 51, in dumps > > cls(buf, protocol).dump(obj) > > _pickle.PicklingError: Can't pickle : > > attribute lookup _betmap on __main__ failed > > > > generating gallery for auto_examples/advanced... [100%] > > plot_iterated_dynamical_systems.py > > E: Build killed with signal TERM after 150 minutes of inactivity i believe this was a one-off due to other circumstances, as i can run those tests just fine. Closing for now -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi--- End Message ---
Bug#936288: marked as done (cfv: Python2 removal in sid/bullseye)
Your message dated Mon, 27 Jul 2020 01:19:52 +0200 with message-id <20200726231952.ga6...@hem.alfredsson.org> and subject line Re: cfv has caused the Debian Bug report #936288, regarding cfv: 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.) -- 936288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cfv Version: 1.18.3-2.1 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:cfv 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 --- Closing since cfv is being removed due to python2 dependency. (removal request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966332 ) /Stefan--- End Message ---
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Quoting Pirate Praveen (2020-07-26 21:07:19) > Control: reopen -1 > > On Mon, Jul 27, 2020 at 00:32, Pirate Praveen > wrote: > > This did not fix the issue :( So we have to reopen this bug once the > > upload reaches the archive (which will close this bug as fixed). > > Thanks to the brave new world of embedding eveything and reducing the > number of js packages. Complicated build systems in favor of reducing > the metadata size, ftw! Only the package uploader can be blamed for embedding _everything_! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
On 2020, ജൂലൈ 27 1:42:32 AM IST, Nicolas Mora wrote: >I'm not sure yet if this would fix the bug but in all the build log >errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is >always the source of the error. > >The file _baseOrderBy.js in the package seems buggy for an unresolved reson. > >File in node-lodash unstable package: >4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/ > >File in node-lodash bullseye package >4.17.15+dfsg-2 _baseOrderBy.js https://paste.debian.net/1157887/ > >In the unstable version, the call to isArray line 24 is the root of errors. This is possibly introduced by the security fix, but I can't be sure. Hope someone else can clarify. >Also, I see that the upstream version 4.17.19 isn't tagged as latest >release, 4.17.16 is, maybe it's worth a try to package 4.17.16 instead? > >https://github.com/lodash/lodash/releases 4.17.19 is correct as per https://github.com/lodash/lodash/issues/4837#issuecomment-655648024 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#952369: marked as done (terraintool: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411.)
Your message dated Sun, 26 Jul 2020 21:52:15 +
with message-id
and subject line Bug#952369: fixed in terraintool 1.13-2.1
has caused the Debian Bug report #952369,
regarding terraintool: FTBFS: error: No member named $memberName at
/usr/share/perl5/Archive/Zip/Archive.pm line 411.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
952369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terraintool
Version: 1.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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 '/<>'
> docbook-to-man debian/manpage.sgml > terraintool.1
> dh_installman
> make[1]: Leaving directory '/<>'
>dh_icons
>dh_perl
>dh_link
>jh_installlibs
>jh_classpath
>jh_manifest
> error: No member named $memberName
> at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
>
> Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x55d144afbe08),
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
>
> main::update_jar("debian/terraintool/usr/share/terraintool/terraintool.jar",
> Debian::Javahelper::Manifest=HASH(0x55d144afc450)) called at
> /usr/bin/jh_manifest line 209
> Could not read manifest from
> debian/terraintool/usr/share/terraintool/terraintool.jar (2): at
> /usr/bin/jh_manifest line 298.
> make: *** [debian/rules:9: binary] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/terraintool_1.13-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: terraintool
Source-Version: 1.13-2.1
Done: Fabio Augusto De Muzio Tobich
We believe that the bug you reported is fixed in the latest version of
terraintool, 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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich (supplier of updated
terraintool 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, 24 Jul 2020 17:03:09 -0300
Source: terraintool
Architecture: source
Version: 1.13-2.1
Distribution: unstable
Urgency: medium
Maintainer: Wookey
Changed-By: Fabio Augusto De Muzio Tobich
Closes: 952369
Changes:
terraintool (1.13-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/control: bumped javahelper dependency version in Build-Depends-Indep
field, in source stanza, to 0.74 or greater, to avoid a FTBFS caused by a
bug in jh_manifest (see #952370). (Closes: #952369)
Checksums-Sha1:
86c2e1808d53d5b7a1aaa7eddf19e4b5a8434b8c 1809 terraintool_1.13-2.1.dsc
069118370c17a6f189de4f145c20a2df2313affc 13816
terraintool_1.13-2.1.debian.tar.xz
7736f42bcb4d3cdd50d77839593a8c55ab6ab8f2 4203
terraintool_1.13-2.1_source.buildinfo
Checksums-Sha256:
6ae9832d54e5133adf750c33c0f146c59f097e0f3dee41dafd3bda1c312730d8 1809
terraintool_1.13-2.1.dsc
09f342bf5dab805c0bbc6b3290740edc12ba5712aa7828939b82c9dcebfdc125 13816
terraintool_1.13-2.1.debian.tar.xz
4637121dc76d7e9ff1d07ef3bf9fa6e18c59b943eb3d9d5bbd76151dc3011e70 4203
terraintool_1.13-2.1_source.buildinfo
Files:
df85c4a1c86cbeef6e7aa0ad9f3a5621 1809 science extra terraintool_1.13-2.1.dsc
ca7f235e5ca3b85c1c58440861ffbe93 13816 science extra
terraintool_1.13-2.1.debian.tar.xz
8f8e340db61100b5a6f6e7fbe93d6e7f 4203 science extra
terraintool_1.13-2.1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl8bUG0ACgkQ3mO5xwTr
6e/+/g//cRrIjZEAVSrmoTYecqtFG0QgKem0yqilt3G27Pzku6x4J4kKiE7imXhG
iTH4uAk7VA4rR5En+zv7sNVqH8wNaJ7BvPJNq6EmubEwjPWOXSudjecWq3+W4VUR
Z5YlrfpfyM5U68O
Bug#936288: cfv: Python2 removal in sid/bullseye
Den 2020-07-26 kl. 13:17, skrev Moritz Mühlenhoff: On Fri, Aug 30, 2019 at 07:13:06AM +, Matthias Klose wrote: Package: src:cfv Version: 1.18.3-2.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Hi Stefan, given your comment at https://github.com/cfv-project/cfv/issues/8#issuecomment-615215686, let's proceed with removal? Yes, I don't see any progress on the py3 port since May (and I cannot commit myself to implement py3 support) so I just sent the removal request. Thanks for the reminder. /Stefan
Processed: e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a
Processing control commands: > found -1 1.46~WIP.2019.10.03-1 Bug #966330 [src:e2fsprogs] e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a Marked as found in versions e2fsprogs/1.46~WIP.2019.10.03-1. -- 966330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966330: e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a
Source: e2fsprogs Version: 1.45.6-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 1.46~WIP.2019.10.03-1 Hi, libblkid-dev recently dropped libblkid.a causing e2fsprogs to FTBFS: make[2]: Entering directory '/build/e2fsprogs-1.45.6/debian/BUILD-STD/e2fsck' gcc -Wl,-z,relro -Wl,-z,now -static -o e2fsck.static unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o logfile.o sigcatcher.o readahead.o extents.o ../lib/libsupport.a ../lib/libext2fs.a ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid ../lib/libe2p.a -ldl /usr/bin/ld: cannot find -lblkid /usr/bin/ld: logfile.o: in function `expand_percent_expression': ./debian/BUILD-STD/e2fsck/../../../e2fsck/logfile.c:141: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking collect2: error: ld returned 1 exit status make[2]: *** [Makefile:449: e2fsck.static] Error 1 Andreas
Bug#966323: marked as done (python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy)
Your message dated Sun, 26 Jul 2020 20:56:08 + with message-id and subject line Bug#966323: fixed in subvertpy 0.11.0~git20191228+2423bf1-5 has caused the Debian Bug report #966323, regarding python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-subvertpy Version: 0.11.0~git20191228+2423bf1-4 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 .../python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb ... Unpacking python3-subvertpy (0.11.0~git20191228+2423bf1-4) ... dpkg: error processing archive /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/subvertpy-fast-export.1.gz', which is also in package python-subvertpy 0.11.0~git20191228+2423bf1-3 Errors were encountered while processing: /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb Since python-subvertpy is gone, the B+R against it can be unversioned. cheers, Andreas python-subvertpy=0.11.0~git20191228+2423bf1-3_python3-subvertpy=0.11.0~git20191228+2423bf1-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: subvertpy Source-Version: 0.11.0~git20191228+2423bf1-5 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of subvertpy, 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. Sandro Tosi (supplier of updated subvertpy 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, 26 Jul 2020 15:58:37 -0400 Source: subvertpy Architecture: source Version: 0.11.0~git20191228+2423bf1-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 966323 Changes: subvertpy (0.11.0~git20191228+2423bf1-5) unstable; urgency=medium . * debian/rules - install a manpage named subvertpy3-fast-export.1, to match the binary name; Closes: #966323 Checksums-Sha1: e3ff8643b57fea71025a0bf491def003fae677a2 2236 subvertpy_0.11.0~git20191228+2423bf1-5.dsc 1ffa87133356f05f639d037c98c527ad73139da7 1419344 subvertpy_0.11.0~git20191228+2423bf1-5.debian.tar.xz 02ce28151befce51586ea297683c381dd81e678f 8666 subvertpy_0.11.0~git20191228+2423bf1-5_source.buildinfo Checksums-Sha256: 87d51be726404da233e07fb4c501a8a0bfd0275a32e8279a52f52e8eb6918ed3 2236 subvertpy_0.11.0~git20191228+2423bf1-5.dsc 33eabf6a0ff7b0a38318a958646fe8f919d1e79a937c8d3120956a75a6f4c971 1419344 subvertpy_0.11.0~git20191228+2423bf1-5.debian.tar.xz 03c34b8bb57c784d2a2d4ad9349420b51a425cb7bb3ec1f3e248a9d90c867286 8666 subvertpy_0.11.0~git20191228+2423bf1-5_source.buildinfo Files: 27f6793254ae86b196b0a805e42ea163 2236 python optional subvertpy_0.11.0~git20191228+2423bf1-5.dsc a2267599063cb124d63ff34e3b94120c 1419344 python optional subvertpy_0.11.0~git20191228+2423bf1-5.debian.tar.xz 1750be0b9bd562757c8a2fb3e50d6af1 8666 python optional subvertpy_0.11.0~git20191228+2423bf1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8d4IIACgkQh588mTgB qU8TKw//d+v/g5H2NJGxpzGGN9jv///xTS3zsC8SZfoBwKPwbuBwsiogegecmmKZ JwCjj8LpE67hUO7yEa4nzx5S75K8QzlgSHIdT/JJn08J4UyjCrwwkaPdZppaml6R 3fjrrjokCU8kKUr2QC02iIs4GwQE9J1rDNiR3vzm+dzaDCV/L7GX65VtyTFRVB4d IthRGx15840pXnS9CJJ9mOILP98USZ84vbZN88tANsK7wHMgXkWKt1DkTBGsKqHe TGTyWz6D/EjEKNh+UlpWs0/a39gD2is9k2svM0vIY0oc2pMcwZy1tftxSX3
Bug#957793: marked as done (sigma-align: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 20:56:03 + with message-id and subject line Bug#957793: fixed in sigma-align 1.1.3-7 has caused the Debian Bug report #957793, regarding sigma-align: 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.) -- 957793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sigma-align Version: 1.1.3-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/sigma-align_1.1.3-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 [...] checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking glib.h usability... yes checking glib.h presence... yes checking for glib.h... yes checking for an ANSI C-conforming const... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for gettimeofday... 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 config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build make -j4 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.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o parseopts.o parseopts.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o readfasta.o readfasta.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o getbgprobs.o getbgprobs.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o setbgprobs.o setbgprobs.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEBUG -O2 -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o initseqfrags.o initseqfrags.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/
Bug#957562: marked as done (mpc123: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 20:51:56 + with message-id and subject line Bug#957562: fixed in mpc123 0.2.4-7 has caused the Debian Bug report #957562, regarding mpc123: 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.) -- 957562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mpc123 Version: 0.2.4-5 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/mpc123_0.2.4-5_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 [...] SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-cdfc310e-adb5-4983-9569-216c76087c8c SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package mpc123 dpkg-buildpackage: info: source version 0.2.4-5 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Joao Eriberto Mota Filho dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' rm -f tags ao.o player.o playlist.o reader.o reader_file.o shuffle.o signals.o mpc123 LOCALES/it/LC_MESSAGES/mpc123.mo make[1]: Leaving directory '/<>' dh_clean debian/rules build dh build dh_update_autotools_config dh_autoreconf dh_auto_configure dh_auto_build make -j4 make[1]: Entering directory '/<>' /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o ao.o ao.c /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o player.o player.c /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o playlist.o playlist.c /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o reader.o reader.c player.c: In function ‘do_play_stream’: player.c:44:12: warning: variable ‘bytes_from_decoder’ set but not used [-Wunused-but-set-variable] 44 | unsigned bytes_from_decoder=0; |^~ /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o reader_file.o reader_file.c /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o shuffle.o shuffle.c /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o signals.o signals.c msgfmt LOCALES/it/LC_MESSAGES/mpc123.po -o LOCALES/it/LC_MESSAGES/mpc123.mo; Building mpc123 version 0.2 ... /usr/bin/cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -o mpc123 ao.o player.o playlist.o reader.o reader_file.o shuffle.o signals.o mpc123.c -Wl,-z,relro -Wl,-z,now -lao -lmpcdec /usr/bin/ld: player.o:./mpc123.h:148: multipl
Bug#966323: [Python-modules-team] Bug#966323: python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy
On 7/26/20 9:51 PM, Sandro Tosi wrote: > hm i dont think a B+R is needed here: python3-subvertpy installs a > binary called subvertpy3-fast-export so the manpage needs to match > that name; it's probably a relic of the py2 drop, looking at it right > now You know the package better than me to quickly spot the unusual case of something "just" being misnamed ;-) Andreas
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
I'm not sure yet if this would fix the bug but in all the build log errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is always the source of the error. The file _baseOrderBy.js in the package seems buggy for an unresolved reson. File in node-lodash unstable package: 4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/ File in node-lodash bullseye package 4.17.15+dfsg-2 _baseOrderBy.js https://paste.debian.net/1157887/ In the unstable version, the call to isArray line 24 is the root of errors. Also, I see that the upstream version 4.17.19 isn't tagged as latest release, 4.17.16 is, maybe it's worth a try to package 4.17.16 instead? https://github.com/lodash/lodash/releases
Processed: Bug#966323 marked as pending in subvertpy
Processing control commands: > tag -1 pending Bug #966323 [python3-subvertpy] python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy Added tag(s) pending. -- 966323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966323: marked as pending in subvertpy
Control: tag -1 pending Hello, Bug #966323 in subvertpy 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/subvertpy/-/commit/dd2d0acd28010a3d9dd6032d7f492ca1e530bfcd install a manpage named subvertpy3-fast-export.1, to match the binary name; Closes: #966323 (this message was generated automatically) -- Greetings https://bugs.debian.org/966323
Bug#966323: [Python-modules-team] Bug#966323: python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy
> From the attached log (scroll to the bottom...): > > Preparing to unpack > .../python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb ... > Unpacking python3-subvertpy (0.11.0~git20191228+2423bf1-4) ... > dpkg: error processing archive > /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb > (--unpack): >trying to overwrite '/usr/share/man/man1/subvertpy-fast-export.1.gz', > which is also in package python-subvertpy 0.11.0~git20191228+2423bf1-3 > Errors were encountered while processing: > > /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb > > Since python-subvertpy is gone, the B+R against it can be unversioned. hm i dont think a B+R is needed here: python3-subvertpy installs a binary called subvertpy3-fast-export so the manpage needs to match that name; it's probably a relic of the py2 drop, looking at it right now -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#966323: python3-subvertpy: missing (unversioned) Breaks+Replaces: python-subvertpy
Package: python3-subvertpy Version: 0.11.0~git20191228+2423bf1-4 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 .../python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb ... Unpacking python3-subvertpy (0.11.0~git20191228+2423bf1-4) ... dpkg: error processing archive /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/subvertpy-fast-export.1.gz', which is also in package python-subvertpy 0.11.0~git20191228+2423bf1-3 Errors were encountered while processing: /var/cache/apt/archives/python3-subvertpy_0.11.0~git20191228+2423bf1-4_amd64.deb Since python-subvertpy is gone, the B+R against it can be unversioned. cheers, Andreas python-subvertpy=0.11.0~git20191228+2423bf1-3_python3-subvertpy=0.11.0~git20191228+2423bf1-4.log.gz Description: application/gzip
Processed: Re: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Processing control commands:
> reopen -1
Bug #965353 {Done: Pirate Praveen } [node-lodash]
node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is
not defined
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-babel7/7.10.5+~cs65.71.38-3.
--
965353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Control: reopen -1 On Mon, Jul 27, 2020 at 00:32, Pirate Praveen wrote: This did not fix the issue :( So we have to reopen this bug once the upload reaches the archive (which will close this bug as fixed). Thanks to the brave new world of embedding eveything and reducing the number of js packages. Complicated build systems in favor of reducing the metadata size, ftw!
Bug#961652: marked as done (erlang-p1-pam: FTBFS with Erlang 23)
Your message dated Sun, 26 Jul 2020 19:04:05 + with message-id and subject line Bug#961652: fixed in erlang-p1-pam 1.0.8-1 has caused the Debian Bug report #961652, regarding erlang-p1-pam: FTBFS with Erlang 23 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: erlang-p1-pam Version: 1.0.7-1 Severity: normal Dear Maintainer, I'd like to upload Erlang 23 for the bullseye release, but this makes erlang-p1-pam fali to build from source. The problem is that erlang-p1-pam uses liberl_interface which now is obsoleted and removed from the Erlang distribution. Unfortunately, I don't know about any ready-to-use patch which would port epam.c to libei, so this'll require some work. In the meantime, erlang-p1-pam will FTBFS, but the already built one will be usable, because it's linked with liberl_interface statically. -- System Information: Debian Release: 10.4 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages erlang-p1-pam depends on: ii erlang-base [erlang-abi-17.0] 1:21.2.6+dfsg-1 ii libc6 2.28-10 ii libpam0g 1.3.1-5 erlang-p1-pam recommends no packages. erlang-p1-pam suggests no packages. --- End Message --- --- Begin Message --- Source: erlang-p1-pam Source-Version: 1.0.8-1 Done: Philipp Huebner We believe that the bug you reported is fixed in the latest version of erlang-p1-pam, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Huebner (supplier of updated erlang-p1-pam 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, 26 Jul 2020 20:43:39 +0200 Source: erlang-p1-pam Architecture: source Version: 1.0.8-1 Distribution: unstable Urgency: medium Maintainer: Ejabberd Packaging Team Changed-By: Philipp Huebner Closes: 961652 Changes: erlang-p1-pam (1.0.8-1) unstable; urgency=medium . * New upstream version 1.0.8 (Closes: #961652) Checksums-Sha1: 8e29a2d7e4a190f835f3ae333ca311c925bf50da 2106 erlang-p1-pam_1.0.8-1.dsc a327bee593b4d63e08c514ad31a221c9b74c791b 46813 erlang-p1-pam_1.0.8.orig.tar.gz a1f3b339b01668160e25c731d4be84df14271a86 3940 erlang-p1-pam_1.0.8-1.debian.tar.xz 33cda16ea846aa6f0dfc904438a840aec36b741f 11062 erlang-p1-pam_1.0.8-1_amd64.buildinfo Checksums-Sha256: 86ead786365f1ba3f6caa9c20a2e9ec181cc795ae92cc869de3c7d505018e461 2106 erlang-p1-pam_1.0.8-1.dsc aca1ece8a264950a53b4f2b6737a13bc33dfb28d01e093fbbf5e5d7178610f75 46813 erlang-p1-pam_1.0.8.orig.tar.gz f9dff22da292a6fdd57aeddc2dbf632be649bfca6c098a161a766bfb71b17044 3940 erlang-p1-pam_1.0.8-1.debian.tar.xz 5827d87c84c59c9665128699400ad5e3c2b8d320670774c16f4c7715545d91fa 11062 erlang-p1-pam_1.0.8-1_amd64.buildinfo Files: 6612c20de5d1c115da6b1c306d1ccd3e 2106 libs optional erlang-p1-pam_1.0.8-1.dsc 985500c800d5f9fc11358bd6d40f7a9f 46813 libs optional erlang-p1-pam_1.0.8.orig.tar.gz 7a39b6938f60a4b7be7a28f80d26c3fc 3940 libs optional erlang-p1-pam_1.0.8-1.debian.tar.xz 0f1b817e322ccdf930d22806e5b8ba5f 11062 libs optional erlang-p1-pam_1.0.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAl8dz3AVHGRlYmFsYW5j ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0c7IwQAOS1Rc9gERbyQDDeSa9XcCBHrzEq BKujk7/ny13xLZZrsFVpZntgH6trj1DllCL9MHwutbMEHbaCBAqpNWN7vvwrBFYh J54xYbkdRtTMpyrdoAd2falOmWlyuDPwN33gF4R0VhiJz3f+7/6hq6+l45rQmrfO 6ImBYq69aS55Z9ZCHGKIua5HNDID39qAoLAnoLBQz0Zms7wlPgjkJqlgjlMxtQXO 8T22kMe2rF5Lu+kRlByuO4Xyd3fcQocVH+lRUuiMFl8lLuiSKlQfLJt4C7/zG+C8 YvY5ZYNN1y5BeD9GmFM6J1Fc2mE4qXXZvyKVyYGLh6IvBf1DT+0D9/fowgV
Bug#965353: marked as done (node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined)
Your message dated Sun, 26 Jul 2020 19:05:27 +
with message-id
and subject line Bug#965353: fixed in node-babel7 7.10.5+~cs65.71.38-3
has caused the Debian Bug report #965353,
regarding node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js:
isArray is not defined
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
965353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-babel7&arch=all&ver=7.10.5%2B~cs65.71.38-2&stamp=1595148206&raw=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd babel-plugin-dynamic-import-node && babeljs-7 src --out-dir lib
ReferenceError: /<>/babel-plugin-dynamic-import-node/src/index.js:
isArray is not defined
at /usr/share/nodejs/lodash/_baseOrderBy.js:24:7
at arrayMap (/usr/share/nodejs/lodash/_arrayMap.js:19:21)
at baseOrderBy (/usr/share/nodejs/lodash/_baseOrderBy.js:23:17)
at /usr/share/nodejs/lodash/sortBy.js:48:10
at apply (/usr/share/nodejs/lodash/_apply.js:18:25)
at /usr/share/nodejs/lodash/_overRest.js:35:12
at PluginPass.exit
(/usr/share/nodejs/@babel/core/lib/transformation/block-hoist-plugin.js:58:43)
at newFn (/usr/share/nodejs/@babel/traverse/lib/visitors.js:175:21)
at NodePath._call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:42:17) {
code: 'BABEL_TRANSFORM_ERROR'
}
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: node-babel7
Source-Version: 7.10.5+~cs65.71.38-3
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
node-babel7, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated node-babel7 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, 26 Jul 2020 22:26:35 +0530
Source: node-babel7
Binary: node-babel7
Built-For-Profiles: pkg.node-babel7.yarnpkg
Architecture: source all
Version: 7.10.5+~cs65.71.38-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Pirate Praveen
Description:
node-babel7 - Babel command line
Closes: 965353
Changes:
node-babel7 (7.10.5+~cs65.71.38-3) unstable; urgency=medium
.
* Switch to yarnpkg from npm for bootstrap build (npm no longer works because
package.json uses yarn specific features)
* Binary included upload with DEB_BUILD_PROFILES=pkg.node-babel7.yarnpkg
(Closes: #965353)
* Add git as conditional dependency in bootstrapping build profile
* Force yarnpkg in component package.json
Checksums-Sha1:
1e2363c3a43be9420aeb1354a6143ab0ec151690 8655
node-babel7_7.10.5+~cs65.71.38-3.dsc
ddac1e8182d50d9b0faaf8781a0cfdb3beb8de9b 284856
node-babel7_7.10.5+~cs65.71.38-3.debian.tar.xz
58550147cb438910f4104b7ee7436ebe0ae4a881 671600
node-babel7_7.10.5+~cs65.71.38-3_all.deb
aeca9384bb9e4a63b818e427eb9337162fda9047 23446
node-babel7_7.10.5+~cs65.71.38-3_amd64.buildinfo
Checksums-Sha256:
f93e8a31e6bba1f0b2ef5eb734d97f8b417e5159b3eeb0725e28bf56353ff110 8655
node-babel7_7.10.5+~cs65.71.38-3.dsc
5fae9782c48f8319896a585c5e198dc865421d56f1f53c4f998a39cf85e7dd9b 284856
node-babel7_7.10.5+~cs65.71.38-3.debian.tar.xz
0c3e077233a0bfa0a92e59a14acf8d856d1f7a1b346ea2d5f0de14eb3abab6ff 671600
node-babel7_7.10.5+~cs65.71.38-3_all.deb
e9872feae89b327ef3af30fe12d8d0df80f9ea2d412eb778de52bfee956db8f1 23446
node-babel7_7.10.5+~cs65.71.38-3_amd64.buildinfo
Files:
8930ef813a38637d66cd77d201cc2358 8655 javascript optional
node-babel7_7.10.5+~cs65.71.38-3.dsc
6311ca592e7502e42e0c78c1ca95c2c1 284856 javascript optional
node-babel7_7.10.5+~cs65.71.38-3.debian.tar.xz
bd8c92b15a04a4f78ecb531cade51838 671600 javascript optional
node-babel7_7.10.5+~cs65.71.38-3_all.deb
eb85b1206e553d5c1b
Bug#964622: marked as done (erlang-p1-sqlite3: FTBFS: c_src/sqlite3_drv.h:10:10: fatal error: erl_interface.h: No such file or directory)
Your message dated Sun, 26 Jul 2020 19:04:12 + with message-id and subject line Bug#961651: fixed in erlang-p1-sqlite3 1.1.8-1 has caused the Debian Bug report #961651, regarding erlang-p1-sqlite3: FTBFS: c_src/sqlite3_drv.h:10:10: fatal error: erl_interface.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.) -- 961651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: erlang-p1-sqlite3 Version: 1.1.6-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > DC-Build-Header: erlang-p1-sqlite3 1.1.6-5 / 2020-07-09 00:54:40 + > DC-Task: type:rebuild-full source:erlang-p1-sqlite3 version:1.1.6-5 > chroot:unstable esttime:77 > logfile:/tmp/erlang-p1-sqlite3_1.1.6-5_unstable.log modes: > DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source > --apt-update -d unstable -v --no-run-lintian erlang-p1-sqlite3_1.1.6-5' > sbuild (Debian sbuild) 0.78.1 (09 February 2019) on > ip-172-31-4-212.eu-central-1.compute.internal > > +==+ > | erlang-p1-sqlite3 1.1.6-5 (amd64)Thu, 09 Jul 2020 00:54:40 > + | > +==+ > > Package: erlang-p1-sqlite3 > Version: 1.1.6-5 > Source Version: 1.1.6-5 > Distribution: unstable > Machine Architecture: amd64 > Host Architecture: amd64 > Build Architecture: amd64 > Build Type: full > > I: NOTICE: Log filtering will replace > 'var/run/schroot/mount/sid-amd64-sbuild-ff245520-f18b-41ea-92ec-3c9cac558a21' > with '<>' > I: NOTICE: Log filtering will replace > 'build/erlang-p1-sqlite3-zDKfv8/resolver-2luQBd' with '<>' > > +--+ > | Update chroot > | > +--+ > > Get:1 http://127.0.0.1:12990/debian sid InRelease [146 kB] > Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [27.9 kB] > Get:3 http://127.0.0.1:12990/debian sid/main amd64 Packages.diff/Index [27.9 > kB] > Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-07-08-2007.02.pdiff > [8408 B] > Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-07-08-2007.02.pdiff > [8408 B] > Get:5 http://127.0.0.1:12990/debian sid/main amd64 Packages > 2020-07-08-2007.02.pdiff [29.5 kB] > Get:5 http://127.0.0.1:12990/debian sid/main amd64 Packages > 2020-07-08-2007.02.pdiff [29.5 kB] > Fetched 240 kB in 1s (233 kB/s) > Reading package lists... > Reading package lists... > Building dependency tree... > Calculating upgrade... > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > +--+ > | Fetch source files > | > +--+ > > > Check APT > - > > Checking available source versions... > > Download source files with APT > -- > > Reading package lists... > NOTICE: 'erlang-p1-sqlite3' packaging is maintained in the 'Git' version > control system at: > https://salsa.debian.org/ejabberd-packaging-team/erlang-p1-sqlite3.git > Please use: > git clone > https://salsa.debian.org/ejabberd-packaging-team/erlang-p1-sqlite3.git > to retrieve the latest (possibly unreleased) updates to the package. > Need to get 1689 kB of source archives. > Get:1 http://127.0.0.1:12990/debian sid/main erlang-p1-sqlite3 1.1.6-5 (dsc) > [2188 B] > Get:2 http://127.0.0.1:12990/debian sid/main erlang-p1-sqlite3 1.1.6-5 (tar) > [1679 kB] > Get:3 http://127.0.0.1:12990/debian sid/main erlang-p1-sqlite3 1.1.6-5 (diff) > [7692 B] > Fetched 1689 kB in 0s (17.4 MB/s) > Download complete and in download only mode > I: NOTICE: Log filtering will replace > 'build/erlang-p1-sqlite3-zDKfv8/erlang-p1-sqlite3-1.1.6' with > '<>' > I: NOTICE: Log filtering will replace 'build/erlang-p1-sqlite3-zDKfv8' with > '<>' > > +--+ > | Install package build dependencies > | > +--
Bug#961651: marked as done (erlang-p1-sqlite3: FTBFS with Erlang 23)
Your message dated Sun, 26 Jul 2020 19:04:12 + with message-id and subject line Bug#961651: fixed in erlang-p1-sqlite3 1.1.8-1 has caused the Debian Bug report #961651, regarding erlang-p1-sqlite3: FTBFS with Erlang 23 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: erlang-p1-sqlite3 Version: 1.1.6-5 Severity: normal Dear Maintainer, I'd like to upload Erlang 23 for the bullseye release, but this makes erlang-p1-sqlite3 fail to build from source because of the usage of the obsolete liberl_interface recently removed from Erlang. Upstream already did some changes (see [1]), so you can take and apply them. [1] https://github.com/processone/erlang-sqlite3/commit/c31585341e9e4667bb54b2cbe1db6a449a2baace -- System Information: Debian Release: 10.4 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages erlang-p1-sqlite3 depends on: ii erlang-base [erlang-abi-17.0] 1:21.2.6+dfsg-1 ii libc6 2.28-10 ii libsqlite3-0 3.27.2-3 erlang-p1-sqlite3 recommends no packages. erlang-p1-sqlite3 suggests no packages. --- End Message --- --- Begin Message --- Source: erlang-p1-sqlite3 Source-Version: 1.1.8-1 Done: Philipp Huebner We believe that the bug you reported is fixed in the latest version of erlang-p1-sqlite3, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Huebner (supplier of updated erlang-p1-sqlite3 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, 26 Jul 2020 20:46:55 +0200 Source: erlang-p1-sqlite3 Architecture: source Version: 1.1.8-1 Distribution: unstable Urgency: medium Maintainer: Ejabberd Packaging Team Changed-By: Philipp Huebner Closes: 961651 Changes: erlang-p1-sqlite3 (1.1.8-1) unstable; urgency=medium . * New upstream version 1.1.8 (Closes: #961651) Checksums-Sha1: 25c38cd0a06246693a5769a28fa84c368427fce0 2188 erlang-p1-sqlite3_1.1.8-1.dsc 8ec9e637f99b9dec33cb3d1a48f2f964ac8201c9 1679372 erlang-p1-sqlite3_1.1.8.orig.tar.gz b94265408a923b1398719184a188aa367a0b3137 7716 erlang-p1-sqlite3_1.1.8-1.debian.tar.xz 3f0fc6a3397be96fc21524af41fcc421e5c82c1b 11120 erlang-p1-sqlite3_1.1.8-1_amd64.buildinfo Checksums-Sha256: 78c1a551c3e76a121ed946cbbb5e3495b4b8ec99a0965cfc2622ea744325b448 2188 erlang-p1-sqlite3_1.1.8-1.dsc 179e80c2f99edc91e20660e566538d6b03d6677cf319961a7a03444c210fdea2 1679372 erlang-p1-sqlite3_1.1.8.orig.tar.gz b56de9d2fa644498343b14b246eb029f42f77cd01cc841196227d67a4b9885d4 7716 erlang-p1-sqlite3_1.1.8-1.debian.tar.xz 84e1a525d8dd42306d171daa8b61d88ff23291f8c24a2d1c8b1eeffc35bc55c0 11120 erlang-p1-sqlite3_1.1.8-1_amd64.buildinfo Files: 6f9b19bc7ab40e3fb62ce59b7db7b5a6 2188 libs optional erlang-p1-sqlite3_1.1.8-1.dsc 0b8305ef01aafadc2540daa4124d6ec9 1679372 libs optional erlang-p1-sqlite3_1.1.8.orig.tar.gz 3343ca82c28e253efb02f91425f33b46 7716 libs optional erlang-p1-sqlite3_1.1.8-1.debian.tar.xz a4b9b352deed29101a03b24602c3a6f4 11120 libs optional erlang-p1-sqlite3_1.1.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAl8d0IYVHGRlYmFsYW5j ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cgogQALnZVoS2XiLbvXCC1itaY601DFHZ K0sotESwoYhKbHy05zZ94mJvUbgE7X5ckeWZZ8lJbHNj4OEIwmooUIiI20Af2Fo0 dmOfttIeOmXg9TnBrQutNxHxpR4f9MaqIkNmRAQahjARr4ysPlFw4UpHLfK2LwY/ pi1atSy/0IpD16lzVPNdDCX5oF2mSrvz3f+7I0laRgjwcKvaXSTOdCU/JTpFp1kr raReeZEPpp4vcZZYYIn5lbsdDtsxnejJtwZe6cDGETsrzNmF6rYWS5t5SbNUH3IG x6PyW5m/by97tBc/YPJoOEdTDsjSVYwQgXd9AW+ynJcu1Ai1FRkeQa6gK9zl4rrY H/91cBiLYwd
Bug#966322: marked as done (pycsw: Python2 removal in sid/bullseye)
Your message dated Sun, 26 Jul 2020 19:05:33 + with message-id and subject line Bug#966322: fixed in pycsw 2.4.2+dfsg-5 has caused the Debian Bug report #966322, regarding pycsw: 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.) -- 966322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pycsw Version: 2.4.2+dfsg-4 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, in details: (binary:pycsw-wsgi)Depends->libapache2-mod-wsgi 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 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: pycsw Source-Version: 2.4.2+dfsg-5 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of pycsw, 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. Bas Couwenberg (supplier of updated pycsw 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, 26 Jul 2020 20:18:47 +0200 Source: pycsw Architecture: source Version: 2.4.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 966322 Changes: pycsw (2.4.2+dfsg-5) unstable; urgency=medium . * Team upload. * Switch libapache2-mod-wsgi dependency to libapache2-mod-wsgi-py3. (closes: #966322) * Add lintian override for embedded-javascript-library. * Mark patches as Forwarded: not-needed. Checksums-Sha1: 9485e687a89cdc520f0ffa76617c8c21b29f96d5 2484 pycsw_2.4.2+dfsg-5.dsc 6c8ec32cbbfb4fbbca06d2361db6882d58babc96 17816 pycsw_2.4.2+dfsg-5.debian.tar.xz 102aaf14c02687d66493c0882128ee51b4da02af 12125 pycsw_2.4.2+dfsg-5_amd64.buildinfo Checksums-Sha256: 7bd8eb4307dc0d60c88a9fac06b4507a6bc6fc55ae8c5e31498ebc9e49058eae 2484 pycsw_2.4.2+dfsg-5.dsc dea99b4c6e7dab2b7af2b50a67e45cdf1a5d748979fbeb39178abd61f0d008a2 17816 pycsw_2.4.2+dfsg-5.debian.tar.xz e4bed114bb078bb79f12b737cbd082402e93eb12f11c2593b9ad32c01f02bc73 12125 pycsw_2.4.2+dfsg-5_amd64.buildinfo Files: 2481bb96645efe0ac1af3d1280f3b5d7 2484 non-free/python optional pycsw_2.4.2+dfsg-5.dsc 2e5aaf8399ccf8cd49d9bbb2c9ca5e35 17816
Bug#964633: marked as done (erlang-p1-pam: FTBFS: c_src/epam.c:22:10: fatal error: erl_interface.h: No such file or directory)
Your message dated Sun, 26 Jul 2020 19:04:05 +
with message-id
and subject line Bug#961652: fixed in erlang-p1-pam 1.0.8-1
has caused the Debian Bug report #961652,
regarding erlang-p1-pam: FTBFS: c_src/epam.c:22:10: fatal error:
erl_interface.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.)
--
961652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-pam
Version: 1.0.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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 '/<>'
> ./configure
> 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 make sets $(MAKE)... yes
> checking for an ANSI C-conforming const... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible malloc... yes
> checking for ANSI C header files... (cached) yes
> checking for erl... /usr/bin/erl
> checking for erlc... /usr/bin/erlc
> checking for library containing pam_start... -lpam
> checking for library containing pthread_create... -lpthread
> checking security/pam_appl.h usability... yes
> checking security/pam_appl.h presence... yes
> checking for security/pam_appl.h... yes
> configure: creating ./config.status
> config.status: creating vars.config
> dh_auto_configure
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> configure
> make[2]: Nothing to be done for 'configure'.
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> build
> echo rebar_compile
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Evaluating config script "/<>/rebar.config.script"
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/epam.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-p1-pam-1.0.7 (compile)
> DEBUG: Matched required ERTS version: 11.0.2 -> .*
> DEBUG: Matched required OTP release: 23 -> .*
> DEBUG: Min OTP version unconfigured
> DEBUG: erl_opts [debug_info,debug_info,{src_dirs,["src"]}]
> DEBUG: Files to compile first: []
> DEBUG: Starting 3 compile worker(s)
> Compiled src/epam_app.erl
> DEBUG: Worker exited cleanly
> Compiled src/epam_sup.erl
> DEBUG: Worker exited cleanly
> epam.erl:143: Warning: function get_bin_path/0 is unused
> Compiled src/epam.erl
> DEBUG: Worker exited cleanly
> DEBUG: Skipping deps parse of c_src/epam.d: enoent
> DEBUG: Last mod is 0 on c_src/epam.o
> INFO: sh info:
> cwd: "/<>"
> cmd: cc -c -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -Wall
> -fPIC -MMD -I"/usr/lib/erlang/lib/erl_interface-4.0/include"
> -I"/usr/lib/erlang/erts-11.0.2/include" c_src/epam.c -o c_src/epam.o
> DEBUG:opts: [{env,[{"REBAR_DEPS_DIR",
> "/<>/deps"},
> {"ERL_LIBS",
> "/<>/deps"},
> {"APT_CONFIG","/var/lib/sbuild/apt.conf"},
> {"AR","ar"},
> {"AS","as"},
> {"BINDIR","/usr/lib/erlang/erts-11.0.2/bin"},
> {"CC","cc"},
> {"CFLAGS",
> "-g -O2 -fdebug-prefix-ma
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
On Sun, Jul 26, 2020 at 22:43, Pirate Praveen wrote: On Sun, Jul 26, 2020 at 22:24, Pirate Praveen wrote: Babel build situation is indeed a mess. It is even worse than I estimated. We can no longer build it with npm DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild ... HOME=`pwd` npm i npm ERR! code EUNSUPPORTEDPROTOCOL npm ERR! Unsupported URL Type "link:": link:./eslint/babel-eslint-config-internal we have to change it to yarn. This did not fix the issue :( So we have to reopen this bug once the upload reaches the archive (which will close this bug as fixed).
Bug#957492: marked as done (linuxtv-dvb-apps: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 19:04:53 + with message-id and subject line Bug#957492: fixed in linuxtv-dvb-apps 1.1.1+rev1500-1.4 has caused the Debian Bug report #957492, regarding linuxtv-dvb-apps: 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.) -- 957492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linuxtv-dvb-apps Version: 1.1.1+rev1500-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/linuxtv-dvb-apps_1.1.1+rev1500-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 [...] CC gotox make[3]: Leaving directory '/<>/util/gotox' make -C zap all make[3]: Entering directory '/<>/util/zap' CC zap_ca.o CC zap_dvb.o CC zap make[3]: Leaving directory '/<>/util/zap' make -C lsdvb all make[3]: Entering directory '/<>/util/lsdvb' CC lsdvb lsdvb.c: In function ‘get_frontend_entry’: lsdvb.c:74:20: warning: ‘%s’ directive writing up to 255 bytes into a region of size 49 [-Wformat-overflow=] 74 | sprintf(tmp, "%s/%s", DVB_SYSFS_DIR, adap_dir->d_name); |^~ In file included from /usr/include/stdio.h:867, from lsdvb.c:24: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 16 and 271 bytes into a destination of size 64 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ lsdvb.c: In function ‘main’: lsdvb.c:292:33: warning: ‘%s’ directive writing up to 63 bytes into a region of size between 36 and 46 [-Wformat-overflow=] 292 |sprintf(fedev, "%s/adapter%d/%s", DVB_DIR, adapter, frontend); | ^~ In file included from /usr/include/stdio.h:867, from lsdvb.c:24: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 19 and 92 bytes into a destination of size 64 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ make[3]: Leaving directory '/<>/util/lsdvb' make -C alevt all make[3]: Entering directory '/<>/util/alevt' cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o main.o main.c cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o ui.o ui.c cc bdf2xbm.c -o bdf2xbm ./bdf2xbm font1 font1.xbm ./bdf2xbm font2 font2.xbm ./bdf2xbm font3 font3.xbm ./bdf2xbm font4 font4.xbm fgrep -h "#define" font1.xbm font2.xbm font3.xbm font4.xbm >fontsize.h cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o xio.o xio.c cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o fdset.o fdset.c cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o vbi.o vbi.c cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cache.o cache.c cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/
Bug#964615: marked as done (erlang-p1-eimp: FTBFS: c_src/eimp.c:21:10: fatal error: erl_interface.h: No such file or directory)
Your message dated Sun, 26 Jul 2020 18:48:45 +
with message-id
and subject line Bug#964615: fixed in erlang-p1-eimp 1.0.16-1
has caused the Debian Bug report #964615,
regarding erlang-p1-eimp: FTBFS: c_src/eimp.c:21:10: fatal error:
erl_interface.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.)
--
964615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-eimp
Version: 1.0.14-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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 '/<>'
> ./configure
> 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 make sets $(MAKE)... yes
> checking for an ANSI C-conforming const... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible malloc... yes
> checking for ANSI C header files... (cached) yes
> checking for erl... /usr/bin/erl
> checking for erlc... /usr/bin/erlc
> checking gd.h usability... yes
> checking gd.h presence... yes
> checking for gd.h... yes
> checking for library containing gdImageScale... -lgd
> checking jpeglib.h usability... yes
> checking jpeglib.h presence... yes
> checking for jpeglib.h... yes
> checking for library containing gdImageCreateFromJpegPtr, gdImageJpegPtr...
> none required
> checking for library containing jpeg_read_header... -ljpeg
> checking png.h usability... yes
> checking png.h presence... yes
> checking for png.h... yes
> checking for library containing gdImageCreateFromPngPtr, gdImagePngPtr...
> none required
> checking for library containing png_sig_cmp... -lpng
> checking webp/decode.h usability... yes
> checking webp/decode.h presence... yes
> checking for webp/decode.h... yes
> checking for library containing gdImageCreateFromWebpPtr, gdImageWebpPtr...
> none required
> checking for library containing WebPGetInfo... -lwebp
> configure: creating ./config.status
> config.status: creating vars.config
> dh_auto_configure
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> configure
> make[2]: Nothing to be done for 'configure'.
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> build
> echo rebar_compile
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Evaluating config script "/<>/rebar.config.script"
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/eimp.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-p1-eimp-1.0.14 (compile)
> DEBUG: Matched required ERTS version: 11.0.2 -> .*
> DEBUG: Matched required OTP release: 23 -> .*
> DEBUG: Min OTP version unconfigured
> DEBUG: erl_opts [debug_info,debug_info,
> {src_dirs,["src"]},
> {d,'HAVE_GD'},
> {d,'HAVE_WEBP'},
> {d,'HAVE_JPEG'},
> {d,'HAVE_PNG'},
> {d,'RAND_UNIFORM'}]
> DEBUG: Files to compile first: []
> DEBUG: Starting 3 compile worker(s)
> Compiled src/eimp_app.erl
> Compiled src/eimp_sup.erl
> Compiled src/eimp_limit.erl
> DEBUG: Worker exited cleanly
> Compiled src/eimp.erl
> DEBUG: Worker exited cleanly
> Compiled src/eimp_worker.erl
> DEBUG: Worker exited cleanly
> DEBUG: Skipping deps parse of c_src/eimp.d: enoent
> DEBUG: Last mod is 0 on c_src/eimp.o
> INFO: sh info:
> cwd: "/<>
Bug#957492: Bug#964223: linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function)
On 2020-07-19 19:35, Aurelien Jarno wrote:
> control: tag -1 + pending
>
> Dear maintainer,
>
> On 2020-07-13 23:44, Aurelien Jarno wrote:
> > control: severity -1 serious
> >
> > On 2020-07-03 22:27, Aurelien Jarno wrote:
> > > Source: linuxtv-dvb-apps
> > > Version: 1.1.1+rev1500-1.2
> > > Severity: important
> > > Tags: patch upstream
> > >
> > > linuxtv-dvb-apps fails to build from source with glibc 2.31:
> > >
> > > | CC dvbdate
> > > | dvbdate.c: In function ‘set_time’:
> > > | dvbdate.c:312:6: warning: implicit declaration of function ‘stime’; did
> > > you mean ‘ctime’? [-Wimplicit-function-declaration]
> > > | 312 | if (stime(new_time)) {
> > > | | ^
> > > | | ctime
> > > | /usr/bin/ld: /tmp/cchQDddv.o: in function `set_time':
> > > | ./util/dvbdate/dvbdate.c:312: undefined reference to `stime'
> > > | /usr/bin/ld: ./util/dvbdate/dvbdate.c:312: undefined reference to
> > > `stime'
> > > | collect2: error: ld returned 1 exit status
> > > | make[3]: *** [../../Make.rules:82: dvbdate] Error 1
> > > | make[3]: Leaving directory '/<>/util/dvbdate'
> > > | make[2]: *** [Makefile:10: all] Error 2
> > > | make[2]: Leaving directory '/<>/util'
> > > | make[1]: *** [Makefile:14: all] Error 2
> > > | make[1]: Leaving directory '/<>'
> > > | dh_auto_build: error: make -j1 returned exit code 2
> > > | make: *** [debian/rules:4: build] Error 25
> > > | dpkg-buildpackage: error: debian/rules build subprocess returned exit
> > > status 2
> > >
> > > The full build log is available there:
> > > http://qa-logs.debian.net/2020/06/24/linuxtv-dvb-apps_1.1.1+rev1500-1.2_unstable_glibc-exp.log
> > >
> > > The stime function has been marked as obsolete for some time, and since
> > > glibc 2.31 it is no longer available to newly linked binaries. The
> > > clock_settime function should be used instead.
> > >
> > > You will find attached a patch fixing that. It would be nice if it can
> > > be fixed relatively soon so that we can start the transition.
> > >
> >
> > Note that glibc 2.31 is now in unstable. I am therefore increasing the
> > severity to serious.
>
> I have prepared an NMU for linuxtv-dvb-apps (versioned as
> 1.1.1+rev1500-1.3), fixing the build issue with glibc 2.31. You will
> find the diff attached. I have uploaded it to DELAYED/7. Please feel
> free to tell me if I should delay it longer or cancel it altogether.
Unfortunately the NMU failed to build as in the meantime GCC 10 became
the default compiler and linuxtv-dvb-apps doesn't build with this
version due to bug #957492.
I have therefore done a second NMU, versioned 1.1.1+rev1500-1.4, and
uploaded directly to the archive (i.e. *not* through the delayed queue).
You will find the diff attached.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2020-07-19 19:11:31.0 +0200
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2020-07-26 20:42:38.0 +0200
@@ -1,3 +1,11 @@
+linuxtv-dvb-apps (1.1.1+rev1500-1.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to fix build with gcc 10, caused by multiple definition of the
+'sid' global variable. (Closes: #957492).
+
+ -- Aurelien Jarno Sun, 26 Jul 2020 20:42:38 +0200
+
linuxtv-dvb-apps (1.1.1+rev1500-1.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/gcc-10-sid-redefinition.patch linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/gcc-10-sid-redefinition.patch
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/gcc-10-sid-redefinition.patch 1970-01-01 01:00:00.0 +0100
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/gcc-10-sid-redefinition.patch 2020-07-26 20:39:03.0 +0200
@@ -0,0 +1,10 @@
+--- linuxtv-dvb-apps-1.1.1+rev1500.orig/util/alevt/vbi.c
linuxtv-dvb-apps-1.1.1+rev1500/util/alevt/vbi.c
+@@ -35,7 +35,6 @@ static void dvb_handler(struct vbi *vbi,
+
+ static u8 *rawbuf; // one common buffer for raw vbi data
+ static int rawbuf_size; // its current size
+-u_int16_t sid;
+ static char *vbi_names[]
+ = { "/dev/vbi", "/dev/vbi0", "/dev/video0", "/dev/dvb/adapter0/demux0",
+ NULL }; // default device names if none was given at the command line
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2020-07-19 19:11:31.0 +0200
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2020-07-26 20:38:59.0 +0200
@@ -10,3 +10,4 @@
fix-build-libpng16.patch
dst_test-no-set-id.patch
glibc-stime.patch
+gcc-10-sid-redefinition.patch
signature.asc
Description: PGP signature
Bug#961650: marked as done (erlang-p1-eimp: FTBFS with Erlang 23)
Your message dated Sun, 26 Jul 2020 18:48:45 + with message-id and subject line Bug#964615: fixed in erlang-p1-eimp 1.0.16-1 has caused the Debian Bug report #964615, regarding erlang-p1-eimp: FTBFS with Erlang 23 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: erlang-p1-eimp Version: 1.0.14-1 Severity: normal Dear Maintainer, I'd like to upload Erlang 23 for bullseye release, but unfortunately, this makes the erlang-p1-eimp fail to build from source. The problem is that erlang-p1-eimp uses liberl_interface, which has been removed in Erlang 23. Upstream already made the necessary changes (see [1]). I'd suggest to apply them. [1] https://github.com/processone/eimp/commit/7fe680d25426b1808f3c49e77240f3cfd5ef712b -- System Information: Debian Release: 10.4 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages erlang-p1-eimp depends on: ii erlang-base [erlang-abi-17.0] 1:21.2.6+dfsg-1 pn erlang-p1-utils ii libc6 2.28-10 ii libgd3 2.2.5-5.2 ii libjpeg62-turbo1:1.5.2-2+b1 ii libpng16-161.6.36-6 ii libwebp6 0.6.1-2 erlang-p1-eimp recommends no packages. erlang-p1-eimp suggests no packages. --- End Message --- --- Begin Message --- Source: erlang-p1-eimp Source-Version: 1.0.16-1 Done: Philipp Huebner We believe that the bug you reported is fixed in the latest version of erlang-p1-eimp, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Huebner (supplier of updated erlang-p1-eimp 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, 26 Jul 2020 20:37:18 +0200 Source: erlang-p1-eimp Architecture: source Version: 1.0.16-1 Distribution: unstable Urgency: medium Maintainer: Ejabberd Packaging Team Changed-By: Philipp Huebner Closes: 964615 Changes: erlang-p1-eimp (1.0.16-1) unstable; urgency=medium . * New upstream version 1.0.16 (Closes: #964615) * Updated Erlang dependencies Checksums-Sha1: 082b27f2c83d4c3493b78ea36db449df3da82fca 2146 erlang-p1-eimp_1.0.16-1.dsc 120ececbb0d2a92278e5bf0a12dc72df68869a77 3274515 erlang-p1-eimp_1.0.16.orig.tar.gz 0cff84ceb3342adb744d9043e11e9a03ca445e7f 3052 erlang-p1-eimp_1.0.16-1.debian.tar.xz a0ed231a6e6bd24ae74847dc5e189706e19049ae 12167 erlang-p1-eimp_1.0.16-1_amd64.buildinfo Checksums-Sha256: 12048ad8d15927b49eac1fef26295468d39271ff1b56fefabba0877dfa655275 2146 erlang-p1-eimp_1.0.16-1.dsc 8787c47357afa447e4c6eb7c54d484b16ee1c55eb813b9411a32dc857160101c 3274515 erlang-p1-eimp_1.0.16.orig.tar.gz 5e89db339c8b0cb4991e43ec1ba0bde31a80d29fa05b09ba83d6fc45a71c1301 3052 erlang-p1-eimp_1.0.16-1.debian.tar.xz 58f2c124f0c2220da1f378966e9e29d5c72d47bcbb81d1a88d6914cc443276d6 12167 erlang-p1-eimp_1.0.16-1_amd64.buildinfo Files: b77cdbbb7e9050e4c6d7e98df639cef8 2146 libs optional erlang-p1-eimp_1.0.16-1.dsc a9494c9840b97b2e95871123177b93b1 3274515 libs optional erlang-p1-eimp_1.0.16.orig.tar.gz 2643b85a6d92a524aed9e0760a2537c4 3052 libs optional erlang-p1-eimp_1.0.16-1.debian.tar.xz 293b6b37a809ef1a27497148f6d17400 12167 libs optional erlang-p1-eimp_1.0.16-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAl8dzf0VHGRlYmFsYW5j ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cTKEQALT3TbPgfbJBAMlsqHFRxBHi2tHo vT683cpvLQZ27iMs9vuIqvhTk48o9bFAxlmqdf6/uWXHFpFuj3NTmFn6j4xJ6rDS Tq17XbOHulrqbKinuOJAZ89DBeM/yVzuiOPHfqxTnpXCvAiNWcmo2cZSl0CIQpFh CpWwyPj9q3dGDkgb7W4Ot/uAcHiS0hcUdU
Bug#964220: marked as done (vdr: FTBFS with glibc 2.31 (uses removed stime function))
Your message dated Sun, 26 Jul 2020 18:38:54 +
with message-id
and subject line Bug#964220: fixed in vdr 2.4.1-4.1
has caused the Debian Bug report #964220,
regarding vdr: FTBFS with glibc 2.31 (uses removed stime 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.)
--
964220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr
Version: 2.4.1-4
Severity: important
Tags: patch upstream
Dear maintainer,
vdr fail to build from source with glibc 2.31:
| g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD -DSDNOTIFY
-DLIRC_DEVICE=\"/var/run/lirc/lircd\" -DVIDEODIR=\"/var/lib/video\"
-DCONFDIR=\"/var/lib/vdr\" -DARGSDIR=\"/etc/vdr/conf.d\"
-DCACHEDIR=\"/var/cache/vdr\" -DRESDIR=\"/usr/share/vdr\"
-DPLUGINDIR=\"/usr/lib/vdr/plugins\" -DLOCDIR=\"/usr/share/locale\"
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -o
eitscan.o eitscan.c
| eit.c: In constructor ‘cTDT::cTDT(const u_char*)’:
| eit.c:394:13: error: ‘stime’ was not declared in this scope; did you mean
‘ctime’?
| 394 | if (stime(&dvbtim) == 0)
| | ^
| | ctime
| make[2]: *** [Makefile:135: eit.o] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory '/<>'
| dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true"
PREFIX=/usr VIDEODIR=/var/lib/video LIBDIR=/usr/lib/vdr/plugins SDNOTIFY=1
VERBOSE=1 returned exit code 2
| make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:14: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
The full build log is available there:
http://qa-logs.debian.net/2020/06/24/vdr_2.4.1-4_unstable_glibc-exp.log
The stime function has been marked as obsolete for some time, and since
glibc 2.31 it is no longer available to newly linked binaries. The
clock_settime function should be used instead.
You will find attached a patch fixing that. It would be nice if it can
be fixed relatively soon so that we can start the transition.
Regards,
Aurelien
diff -Nru vdr-2.4.1/debian/patches/glibc-stime.patch
vdr-2.4.1/debian/patches/glibc-stime.patch
--- vdr-2.4.1/debian/patches/glibc-stime.patch 1970-01-01 00:00:00.0
+
+++ vdr-2.4.1/debian/patches/glibc-stime.patch 2020-07-03 18:47:22.0
+
@@ -0,0 +1,15 @@
+The obsolete function stime is no longer available to newly linked binaries
+since glibc 2.31. Replace it by clock_settime.
+
+--- a/eit.c
b/eit.c
+@@ -391,7 +391,8 @@ cTDT::cTDT(const u_char *Data)
+ if (abs(diff) > MAX_TIME_DIFF) {
+ mutex.Lock();
+ if (abs(diff) > MAX_ADJ_DIFF) {
+-if (stime(&dvbtim) == 0)
++struct timespec ts = { .tv_sec = dvbtim };
++if (clock_settime(CLOCK_REALTIME, &ts) == 0)
+isyslog("system time changed from %s (%ld) to %s (%ld)",
*TimeToString(loctim), loctim, *TimeToString(dvbtim), dvbtim);
+ else
+esyslog("ERROR while setting system time: %m");
diff -Nru vdr-2.4.1/debian/patches/series vdr-2.4.1/debian/patches/series
--- vdr-2.4.1/debian/patches/series 2019-11-01 12:11:11.0 +
+++ vdr-2.4.1/debian/patches/series 2020-07-03 18:45:29.0 +
@@ -6,3 +6,4 @@
allow-verbose-libsi-build.patch
use-cpp-flags.patch
configurable-pkg-config.patch
+glibc-stime.patch
--- End Message ---
--- Begin Message ---
Source: vdr
Source-Version: 2.4.1-4.1
Done: Aurelien Jarno
We believe that the bug you reported is fixed in the latest version of
vdr, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated vdr 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, 19 Jul 2020 19:22:51 +0200
Source: vdr
Architecture: source
V
Bug#957972: marked as done (xboard: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 18:39:01 +
with message-id
and subject line Bug#957972: fixed in xboard 4.9.1-2
has caused the Debian Bug report #957972,
regarding xboard: 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.)
--
957972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xboard
Version: 4.9.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/xboard_4.9.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
[...]
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from gtk/xengineoutput.c:52:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from gtk/xengineoutput.c:52:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Wdeprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/glib-2.0/gobject/gbinding.h:28,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from gtk/xengineoutput.c:52:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
551 | struct _GTimeVal
|^
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -Wno-parentheses -Wl,-z,relro
-Wl,-z,now -o xboard backend.o book.o childio.o gamelist.o ngamelist.o lists.o
moves.o parser.o pgntags.o uci.o board.o draw.o dialogs.o engineoutput.o
nengineoutput.o evalgraph.o nevalgraph.o history.o nhistory.o menus.o usounds.o
usystem.o zippy.o gtk/xboard.o gtk/xoptions.o gtk/xtimer.o gtk/xengineoutput.o
-ldl -lm -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
-lfontconfig -lfreetype -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0
-lpangocairo-1.0 -lpango-1.0 -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0
-lgobject-2.0 -lglib-2.0 -lcairo
/usr/bin/ld: book.o:./backend.h:245: multiple definition of `ics_type';
backend.o:./backend.h:245: first defined here
/usr/bin/ld: childio.o:./backend.h:245: multiple definition of `ics_type';
backend.o:./backend.h:245: first defined here
/usr/bin/ld: gamelist.o:./backend.h:245: multiple definition of `ics_type';
backend.o:./backend.h:245: first defined here
/usr/bin/ld: n
Processed: tagging 964231
Processing commands for cont...@bugs.debian.org: > tags 964231 + pending Bug #964231 [src:faketime] faketime: FTBFS with glibc 2.31 due to ftime deprecation Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-07-26 18:33:55.412811+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 > # dicoweb is an application and has 0 external rdeps or not in testing > severity 966320 serious Bug #966320 [src:dico] dico: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # mnemosyne is an application and has 0 external rdeps or not in testing > severity 966321 serious Bug #966321 [src:mnemosyne] mnemosyne: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # pycsw-wsgi is an application and has 0 external rdeps or not in testing > severity 966322 serious Bug #966322 [src:pycsw] pycsw: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 966320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966320 966321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966321 966322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal blocks updates - 2020-07-26 18:33:55.323289+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 > # mod-wsgi > block 937062 by 966320 966322 Bug #937062 [src:mod-wsgi] mod-wsgi: Python2 removal in sid/bullseye 937062 was blocked by: 936950 937063 938682 936189 936573 937062 was blocking: 937569 937695 Added blocking bug(s) of 937062: 966322 and 966320 > End of message, stopping processing here. Please contact me if you need assistance. -- 937062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964223: marked as done (linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function))
Your message dated Sun, 26 Jul 2020 18:20:41 +
with message-id
and subject line Bug#964223: fixed in linuxtv-dvb-apps 1.1.1+rev1500-1.3
has caused the Debian Bug report #964223,
regarding linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime 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.)
--
964223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linuxtv-dvb-apps
Version: 1.1.1+rev1500-1.2
Severity: important
Tags: patch upstream
linuxtv-dvb-apps fails to build from source with glibc 2.31:
| CC dvbdate
| dvbdate.c: In function ‘set_time’:
| dvbdate.c:312:6: warning: implicit declaration of function ‘stime’; did you
mean ‘ctime’? [-Wimplicit-function-declaration]
| 312 | if (stime(new_time)) {
| | ^
| | ctime
| /usr/bin/ld: /tmp/cchQDddv.o: in function `set_time':
| ./util/dvbdate/dvbdate.c:312: undefined reference to `stime'
| /usr/bin/ld: ./util/dvbdate/dvbdate.c:312: undefined reference to `stime'
| collect2: error: ld returned 1 exit status
| make[3]: *** [../../Make.rules:82: dvbdate] Error 1
| make[3]: Leaving directory '/<>/util/dvbdate'
| make[2]: *** [Makefile:10: all] Error 2
| make[2]: Leaving directory '/<>/util'
| make[1]: *** [Makefile:14: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:4: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
The full build log is available there:
http://qa-logs.debian.net/2020/06/24/linuxtv-dvb-apps_1.1.1+rev1500-1.2_unstable_glibc-exp.log
The stime function has been marked as obsolete for some time, and since
glibc 2.31 it is no longer available to newly linked binaries. The
clock_settime function should be used instead.
You will find attached a patch fixing that. It would be nice if it can
be fixed relatively soon so that we can start the transition.
Regards,
Aurelien
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch
linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch
1970-01-01 00:00:00.0 +
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch
2020-07-03 20:13:33.0 +
@@ -0,0 +1,16 @@
+The obsolete function stime is no longer available to newly linked binaries
+since glibc 2.31. Replace it by clock_settime.
+
+--- a/util/dvbdate/dvbdate.c
b/util/dvbdate/dvbdate.c
+@@ -309,7 +309,9 @@ int atsc_scan_date(time_t *rx_time, unsi
+ */
+ int set_time(time_t * new_time)
+ {
+- if (stime(new_time)) {
++ struct timespec ts = { .tv_sec = new_time };
++
++ if (clock_settime(CLOCK_REALTIME, &ts)) {
+ perror("Unable to set time");
+ return -1;
+ }
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series
linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series2018-01-23
17:50:35.0 +
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series2020-07-03
20:13:33.0 +
@@ -9,3 +9,4 @@
use-ldflags.patch
fix-build-libpng16.patch
dst_test-no-set-id.patch
+glibc-stime.patch
--- End Message ---
--- Begin Message ---
Source: linuxtv-dvb-apps
Source-Version: 1.1.1+rev1500-1.3
Done: Aurelien Jarno
We believe that the bug you reported is fixed in the latest version of
linuxtv-dvb-apps, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated linuxtv-dvb-apps
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, 19 Jul 2020 19:11:31 +0200
Source: linuxtv-dvb-apps
Architecture: source
Version: 1.1.1+rev1500-1.3
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team
Changed-By: Aurelien Jarno
Closes: 964223
Changes:
linuxtv-dvb-apps (1.1.1+rev1500-1.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Add a patch to replace
Bug#963673: marked as done (droopy: Droopy fails to start due to a deprecated python3 module (macpath))
Your message dated Sun, 26 Jul 2020 18:19:00 + with message-id and subject line Bug#963673: fixed in droopy 0.20160830-2 has caused the Debian Bug report #963673, regarding droopy: Droopy fails to start due to a deprecated python3 module (macpath) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: droopy Version: 0.20160830-1 Severity: grave Tags: upstream Justification: renders package unusable Dear maintainer. I launched droopy earlier to transfer some files, and it failed like so $ droopy Traceback (most recent call last): File "/usr/bin/droopy", line 81, in import macpath ModuleNotFoundError: No module named 'macpath' A small search brought me to this bug report in droopy's github page https://github.com/stackp/Droopy/issues/27 I doubt it will be fixed anytime soon, because the bug report has been opened ~9 months ago and droopy's last update was 4 years ago, so maybe it is time to remove it from the repo. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages droopy depends on: ii python3 3.8.2-3 droopy recommends no packages. droopy suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: droopy Source-Version: 0.20160830-2 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of droopy, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated droopy 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, 26 Jul 2020 19:40:06 +0200 Source: droopy Architecture: source Version: 0.20160830-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 963673 Changes: droopy (0.20160830-2) unstable; urgency=medium . * Drop macpath (Closes: #963673) * Bump Standards-Version to 4.5.0 * Switch to debhelper 13 * Set Rules-Requires-Root: no Checksums-Sha1: 7e018209ae7e77f6fb219f72a8c31a8bfe37398e 1852 droopy_0.20160830-2.dsc eb6ef5c27c382c8f784336c08631a9a2ec9d4c3f 3192 droopy_0.20160830-2.debian.tar.xz 11ba040fec8c3ba63d58e1dfb8c2676c938a1588 6908 droopy_0.20160830-2_source.buildinfo Checksums-Sha256: dbfa8b519ad45d3926473ef5f2aebd2595767a0137d4a8550e2269208398 1852 droopy_0.20160830-2.dsc 921d1801f083c31528a58b45f7ea65650fe3a0426d450e746c6b8de9b1193af4 3192 droopy_0.20160830-2.debian.tar.xz 92151d4208df4950eea94cc683bc2043254c82ce6a8eed8eb59d88b0edaa 6908 droopy_0.20160830-2_source.buildinfo Files: 530bf1ded5f0e116ab04e22180c9d916 1852 net optional droopy_0.20160830-2.dsc fb67772a33a2a62ce67a1b812201aef1 3192 net optional droopy_0.20160830-2.debian.tar.xz 25e160a356d69eeec5acada9eb27298d 6908 net optional droopy_0.20160830-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAl8dwQ4ACgkQFZ61xO/I d0xLMg//XTy0wnzdApemv9gx34oQ7v3eV9oqn1kTX0VKgSBBliKcLiHlNHAaPndt UXO18eFkDOCkLzVHipmDmFHdjfqeZimSzHfsho4Qi702PWTE8/9fhO/DBqo+nK73 7TmDUzu1GjGW1P77oyTxm3DXgoo/IXsogf9sm8G2+xvPBSG9c6mmvoIqMGrOrF0N 3/05R/HNJsSL8cs0qWyAt5uVvZ/vOaQGeW3GaTQhnh7FhOD0q3dTu8KECXuGupUE oZFSgcn9i7PP6/IBnbZYIoWkjz00jDq9N3G64q7ffksLxKzoNxRGYyHJhnkznn8L 30N4KKmAxhttIW3ZLI57Sbp1gg498YdLYFuUUPGLQVS5xTFudN1O+1lpdrDjHleI Jv2/9WLTMTkhvG0B6deiHyXLJfNyaKk8KUXWrRS10qckncCRem1O9n1oJdzlRK87 3sD+Lx7kc4j31hH0su+V7f3p9dYPN7doWmA72OMeco5tyUqrIRRb896cUKTnt07E nE98n3GFeR6vfm68fRYypO8KqoTOA6MBfu1mFeGVOkId16VD0OF87VYg2Ex6idHq FLXGYy7mgaHC4SmP8t1vthjcNtvR21WvWltg77hxmTaqWvdTgwncxjjuRjbgAh/o
Bug#957734: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #957734 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/0f50bd0e927ca1534eaa7c713e921c3ce5f8c7d8 Add a patch to fix webrtc build error with GCC 10. Closes: #957734. (this message was generated automatically) -- Greetings https://bugs.debian.org/957734
Processed: Bug#957734 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #957734 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: ftbfs with GCC-10 Added tag(s) pending. -- 957734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964649: marked as done (erlang-jose: FTBFS: ERROR: compile failed while processing /<>: rebar_abort)
Your message dated Sun, 26 Jul 2020 17:18:45 +
with message-id
and subject line Bug#964649: fixed in erlang-jose 1.10.1-2
has caused the Debian Bug report #964649,
regarding erlang-jose: FTBFS: ERROR: compile failed while processing
/<>: rebar_abort
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
964649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-jose
Version: 1.10.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package erlang-jose
> dpkg-buildpackage: info: source version 1.10.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Philipp Huebner
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_auto_clean -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> clean
> if [ -e debian/trash ]; then rm -f -f `cat debian/trash`; fi
> rm -f -rf debian/trash
> echo clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/jose.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-jose-1.10.1 (clean)
> INFO: sh info:
> cwd: "/<>"
> cmd: rm -rf ebin/*.beam
> DEBUG:opts: [{use_stdout,false},abort_on_error]
> DEBUG: Port Cmd: "rm -rf ebin/*.beam"
> Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide]
> INFO: sh info:
> cwd: "/<>"
> cmd: rm -rf priv/mibs/*.bin
> DEBUG:opts: [{use_stdout,false},abort_on_error]
> DEBUG: Port Cmd: "rm -rf priv/mibs/*.bin"
> Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide]
> INFO: sh info:
> cwd: "/<>"
> cmd: rm -rf /<>/.rebar/erlcinfo
> DEBUG:opts: [{use_stdout,false},abort_on_error]
> DEBUG: Port Cmd: "rm -rf /<>/.rebar/erlcinfo"
> Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide]
> INFO: sh info:
> cwd: "/<>"
> cmd: rm -rf .eunit
> DEBUG:opts: [{use_stdout,false},abort_on_error]
> DEBUG: Port Cmd: "rm -rf .eunit"
> Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide]
> INFO: sh info:
> cwd: "/<>"
> cmd: rm -rf .qc
> DEBUG:opts: [{use_stdout,false},abort_on_error]
> DEBUG: Port Cmd: "rm -rf .qc"
> Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide]
> DEBUG: Postdirs: []
> rm -rf ebin/*.beam
> rm -rf ebin/*.app
> rm -rf c_src/*.o
> rm -rf priv/.so
> rm -rf .eunit
>dh_autoreconf_clean -O--buildsystem=rebar
>dh_clean -O--buildsystem=rebar
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> rm -f -- debian/erlang-jose.substvars debian/files
> rm -fr -- debian/erlang-jose/ debian/tmp/
> find . \( \( \
> \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o
> -type f -a \
> \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> \) -exec rm -f {} + \) -o \
> \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
> \)
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building erlang-jose using existing
> ./erlang-jose_1.10.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building erlang-jose in erlang-jose_1.10.1-1.debian.tar.xz
> dpkg-source: info: building erlang-jose in erlang-jose_1.10.1-1.dsc
> debian/rules binary
> dh binary --buildsystem=rebar --with rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_autoreconf -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh
Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
On Sun, Jul 26, 2020 at 22:24, Pirate Praveen wrote: Babel build situation is indeed a mess. It is even worse than I estimated. We can no longer build it with npm DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild ... HOME=`pwd` npm i npm ERR! code EUNSUPPORTEDPROTOCOL npm ERR! Unsupported URL Type "link:": link:./eslint/babel-eslint-config-internal we have to change it to yarn.
Bug#964465: marked as done (python3-ironic-lib: missing Breaks+Replaces: ironic-common (<< 1:15))
Your message dated Sun, 26 Jul 2020 17:06:58 + with message-id and subject line Bug#964465: fixed in python-ironic-lib 4.2.1-2 has caused the Debian Bug report #964465, regarding python3-ironic-lib: missing Breaks+Replaces: ironic-common (<< 1:15) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-ironic-lib Version: 4.2.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', 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 This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-ironic-lib_4.2.1-1_all.deb ... Unpacking python3-ironic-lib (4.2.1-1) over (2.14.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-ironic-lib_4.2.1-1_all.deb (--unpack): trying to overwrite '/etc/ironic/rootwrap.d/ironic-lib.filters', which is also in package ironic-common 1:11.1.0-6 Errors were encountered while processing: /var/cache/apt/archives/python3-ironic-lib_4.2.1-1_all.deb (Not sure which ironic-common version dropped the file, the sid version no longer has it.) cheers, Andreas ironic-common=1:11.1.0-6_python3-ironic-lib=4.2.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-ironic-lib Source-Version: 4.2.1-2 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-ironic-lib, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-ironic-lib 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, 26 Jul 2020 12:59:14 +0200 Source: python-ironic-lib Architecture: source Version: 4.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 964465 Changes: python-ironic-lib (4.2.1-2) unstable; urgency=medium . * Add breaks+replaces: ironic-common (<< 1:15) (Closes: #964465). Checksums-Sha1: 2308c41f83c99b81d58e23cc15939711181fe3b3 2485 python-ironic-lib_4.2.1-2.dsc f5d7d5b853f2b7f088e29addcbeb7e1f2a5edb23 3204 python-ironic-lib_4.2.1-2.debian.tar.xz 7891dae6cfad498d8ee348f8cebd5193ff1e9daa 10468 python-ironic-lib_4.2.1-2_amd64.buildinfo Checksums-Sha256: b86ed71b8e6750d31254fee5abf212651b6c6457e95c7a4b5f8aa900cf0f428c 2485 python-ironic-lib_4.2.1-2.dsc 0f59f9e3d1f433b25d308ba11b95426c1fb63a03c33e1872d4bacba62a83713b 3204 python-ironic-lib_4.2.1-2.debian.tar.xz 89d3118a492d77b1cbc20c8707fe669a7628b0e150ca1d2e65b3b6eab372c3dc 10468 python-ironic-lib_4.2.1-2_amd64.buildinfo Files: ab4c223d0fa477c9bc484aa70fa8f1d5 2485 python optional python-ironic-lib_4.2.1-2.dsc cd7dc5c0b6baf66cb2780b32cc05e90e 3204 python optional python-ironic-lib_4.2.1-2.debian.tar.xz 002356a6adb34985a24da6e4a93a6016 10468 python optional python-ironic-lib_4.2.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl8dtCIACgkQ1BatFaxr Q/4wXQ//d9MH43ieh6LQBq4C7C9NAlYz7WTJDKwKKrmvwLYyoXpeW5GdnLNgZQdC DFrXJE9McJTqGtix7JzHd8U7YqqaEKvDOY9VNfmQkcn69fr7KCdw4TyN1Z+iZtUj YYZb4xtUWii6hh8OwSllTphTNgKwZ49//nJWoa8wSvq2YwmyXLKequlrcMLwawzo /5SZTc+43l6uQhUeFqhKJl9ssj5gNZX1AIop8TElXIGFiqTKJPCooN9AV/2596jW yfyxYa8Br9Xd7JP52rRbLHeWy9y139JpiJYY+lu2hwWrP5cEh7lX90OuJBQ0fwFt kdW/wR0tT0h7JaO1LEYgxxT9R4pot7I8lfsnoFdkEaXbJy3svZJg71UG2LmfLu1W geh3zSJErAwfYUcgN1RSR+KK9Hkx4z+eary18YxwvYs1lxbNEPjkF+ga5Dha4jeN bE5/sfNeW+4VItop1lgzzjbllrf66EOMwThtOG/x7L3mCZ0jxgCdwKbB2iYeZP6X SQSqO4u9t2MU4TddOT/rP2EVwhbeDYMlJ8ecPEXb
Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
On Sun, Jul 26, 2020 at 19:35, Adrian Bunk wrote: On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote: I'm wondering if this will require another bootstraping cycle as node-babel7 autopkgtest is also broken and it depends on itself. If the problem is in node-lodash and gets fixed there, shouldn't this fix everything? I don't think the problem is in lodash as I can see babel upstream is already using lodash 4.17.19 in their yarn.lock https://github.com/babel/babel/blob/f7964a9ac51356f7df6404a25b27ba1cffba1ba7/yarn.lock#L7114 I think babel needs to use the same version of lodash it was built with and a breaking change in lodash was released as a minor/patch release/security release. I think it is becoming more and more common to break API during security releases (we had to face this in rack/rails in ruby team). Babel build situation is indeed a mess. They are dicussing removing lodash from babel though see https://github.com/babel/babel/pull/11789
Processed: Bug#964465 marked as pending in python-ironic-lib
Processing control commands: > tag -1 pending Bug #964465 [python3-ironic-lib] python3-ironic-lib: missing Breaks+Replaces: ironic-common (<< 1:15) Added tag(s) pending. -- 964465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964465: marked as pending in python-ironic-lib
Control: tag -1 pending Hello, Bug #964465 in python-ironic-lib 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/openstack-team/libs/python-ironic-lib/-/commit/187c75544e4df251c73a2e0df606642e859edb0e Add breaks+replaces: ironic-common (<< 1:15) (Closes: #964465). (this message was generated automatically) -- Greetings https://bugs.debian.org/964465
Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote: > I'm wondering if this will require another bootstraping cycle as node-babel7 > autopkgtest is also broken and it depends on itself. If the problem is in node-lodash and gets fixed there, shouldn't this fix everything? cu Adrian
Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
I'm wondering if this will require another bootstraping cycle as node-babel7 autopkgtest is also broken and it depends on itself.
Bug#957338: closing 957338
close 957338 1.6.0-1 thanks
Processed: closing 957338
Processing commands for cont...@bugs.debian.org:
> close 957338 1.6.0-1
Bug #957338 {Done: Adrian Bunk } [src:hitch] hitch: ftbfs with
GCC-10
Ignoring request to alter fixed versions of bug #957338 to the same values
previously set
Bug #957338 {Done: Adrian Bunk } [src:hitch] hitch: ftbfs with
GCC-10
Bug 957338 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957629: marked as done (odb-api: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 16:06:02 + with message-id and subject line Bug#957629: fixed in odb-api 0.18.1-13 has caused the Debian Bug report #957629, regarding odb-api: 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.) -- 957629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:odb-api Version: 0.18.1-10 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/odb-api_0.18.1-10_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 [...] [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/getcurheap.c.o cd /<>/debian/build/odb/src/extras/ifsaux && /usr/bin/cc -DLINUX -DLITTLE -Dodbifsaux_EXPORTS -I/<>/odb/src/extras/ifsaux/include -I/usr/lib/x86_64-linux-gnu/openmpi/lib -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -O3 -DNDEBUG -fPIC -o CMakeFiles/odbifsaux.dir/utilities/getcurheap.c.o -c /<>/odb/src/extras/ifsaux/utilities/getcurheap.c [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/gethwm.c.o cd /<>/debian/build/odb/src/extras/ifsaux && /usr/bin/cc -DLINUX -DLITTLE -Dodbifsaux_EXPORTS -I/<>/odb/src/extras/ifsaux/include -I/usr/lib/x86_64-linux-gnu/openmpi/lib -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -O3 -DNDEBUG -fPIC -o CMakeFiles/odbifsaux.dir/utilities/gethwm.c.o -c /<>/odb/src/extras/ifsaux/utilities/gethwm.c [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/getpag.c.o cd /<>/debian/build/odb/src/extras/ifsaux && /usr/bin/cc -DLINUX -DLITTLE -Dodbifsaux_EXPORTS -I/<>/odb/src/extras/ifsaux/include -I/usr/lib/x86_64-linux-gnu/openmpi/lib -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -O3 -DNDEBUG -fPIC -o CMakeFiles/odbifsaux.dir/utilities/getpag.c.o -c /<>/odb/src/extras/ifsaux/utilities/getpag.c [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/getrss.c.o cd /<>/debian/build/odb/src/extras/ifsaux && /usr/bin/cc -DLINUX -DLITTLE -Dodbifsaux_EXPORTS -I/<>/odb/src/extras/ifsaux/include -I/usr/lib/x86_64-linux-gnu/openmpi/lib -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -O3 -DNDEBUG -fPIC -o CMakeFiles/odbifsaux.dir/utilities/getrss.c.o -c /<>/odb/src/extras/ifsaux/utilities/getrss.c [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/getstackusage.c.o cd /<>/debian/build/odb/src/extras/ifsaux && /usr/bin/cc -DLINUX -DLITTLE -Dodbifsaux_EXPORTS -I/<>/odb/src/extras/ifsaux/include -I/usr/lib/x86_64-linux-gnu/openmpi/lib -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -O3 -DNDEBUG -fPIC -o CMakeFiles/odbifsaux.dir/utilities/getstackusage.c.o -c /<>/odb/src/extras/ifsaux/utilities/getstackusage.c [ 3%] Building C object odb/src/extras/ifsaux/CMakeFiles/odbifsaux.dir/utilities/getstatm.c.o cd /<>/debian/build/odb/src/extras/if
Bug#957394: marked as done (jumpnbump: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 15:20:14 + with message-id and subject line Bug#957394: fixed in jumpnbump 1.61-3 has caused the Debian Bug report #957394, regarding jumpnbump: 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.) -- 957394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jumpnbump Version: 1.61-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/jumpnbump_1.61-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 [...] jnbunpack.c: In function ‘main’: jnbunpack.c:65:5: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 65 | read(fd, &num_entries, 4); | ^ jnbunpack.c:70:5: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 70 | read(fd, datafile, num_entries * sizeof(DirEntry)); | ^~ jnbunpack.c:100:2: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 100 | read(fd, buf, datafile[i].size); | ^~~ jnbunpack.c:101:2: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 101 | write(outfd, buf, datafile[i].size); | ^~~ cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbpack jnbpack.o -Wl,-z,relro -Wl,-z,now cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o -Wl,-z,relro -Wl,-z,now cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -c -o sound.o sound.c make[3]: Leaving directory '/<>/modify' make -C data make[3]: Entering directory '/<>/data' exec ../gobpack font font.gob build exec ../gobpack numbers numbers.gob build exec ../gobpack objects objects.gob build exec ../gobpack rabbit rabbit.gob build exec ../jnbpack -o jumpbump.dat bump.mod calib.dat death.smp fly.smp jump.mod jump.smp levelmap.txt level.pcx mask.pcx menu.pcx menumask.pcx font.gob numbers.gob objects.gob rabbit.gob scores.mod splash.smp spring.smp 18 files to pack Opened jumpbump.dat adding bump.mod OK adding calib.dat OK adding death.smp OK adding fly.smp OK adding jump.mod OK adding jump.smp OK adding levelmap.txt OK adding level.pcx OK adding mask.pcx OK adding menu.pcx OK adding menumask.pcx OK adding font.gob OK adding numbers.gob OK adding objects.gob OK
Bug#957968: marked as done (xaos: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 15:22:49 + with message-id and subject line Bug#957968: fixed in xaos 4.1-1 has caused the Debian Bug report #957968, regarding xaos: 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.) -- 957968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xaos Version: 3.5+ds1-3.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/xaos_3.5+ds1-3.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 [...] make[3]: Entering directory '/<>/src/util' gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o png.o png.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o catalog.o catalog.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o thread.o thread.c thread.c: In function ‘pth_init’: thread.c:122:2: warning: implicit declaration of function ‘exit’ [-Wimplicit-function-declaration] 122 | exit(1); | ^~~~ thread.c:122:2: warning: incompatible implicit declaration of built-in function ‘exit’ thread.c:6:1: note: include ‘’ or provide a declaration of ‘exit’ 5 | #include +++ |+#include 6 | #ifndef __BEOS__ thread.c:124:2: warning: incompatible implicit declaration of built-in function ‘exit’ 124 | exit(1); | ^~~~ thread.c:124:2: note: include ‘’ or provide a declaration of ‘exit’ thread.c:126:2: warning: incompatible implicit declaration of built-in function ‘exit’ 126 | exit(1); | ^~~~ thread.c:126:2: note: include ‘’ or provide a declaration of ‘exit’ thread.c:128:2: warning: incompatible implicit declaration of built-in function ‘exit’ 128 | exit(1); | ^~~~ thread.c:128:2: note: include ‘’ or provide a declaration of ‘exit’ gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o xstring.o xstring.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o help.o help.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o xerror.o xerror.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o xshl.o xshl.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o xldio.o xldio.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/<>/src/include -c -o xstdio.o xstdio.c gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_
Bug#966241: marked as done (x264 FTBFS with make 4.2)
Your message dated Sun, 26 Jul 2020 15:22:42 + with message-id and subject line Bug#966241: fixed in x264 2:0.160.3011+gitcde9a93-2 has caused the Debian Bug report #966241, regarding x264 FTBFS with make 4.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x264 Version: 2:0.159.2999+git296494a-2 Severity: serious Tags: patch Make 4.3 changed the escaping rules with the # symbol is used inside a parameter to functions like $shell. Previously it needed to be escaped, now it needs to *not* be escaped. A change was applied to the debian x264 package recently "debian/rules: Fix awk invocation" which presumablly fixed the build with make 4.3 but causes it to fail under 4.2 with the following error. dpkg-buildpackage: info: host architecture amd64 debian/rules clean debian/rules:3: *** unterminated call to function 'shell': missing ')'. Stop. dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 This has been seen on both reproducible builds and on the raspbian autoforwardporter. The upstream suggested solution to make a makefile that works with both 4.2 and 4.3 is to use a variable. I implemented that soloution and uploaded to Raspbian. The patch I used can be found at https://github.com/raspbian-packages/x264/commit/8b4de154127fdb95874d4d632431bbbabb3cbf64 If make 4.3 migrates to testing and this bug is not already fixed I will downgrade it. I still think this should be fixed even if/when bullseye gets 4.3 to make life easier for backporters. I do not have any immediate plans to NMU this, but this may change if the release gets closer and make 4.3 is still not in testing. --- End Message --- --- Begin Message --- Source: x264 Source-Version: 2:0.160.3011+gitcde9a93-2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of x264, 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 x264 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, 26 Jul 2020 16:52:56 +0200 Source: x264 Architecture: source Version: 2:0.160.3011+gitcde9a93-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 966241 Changes: x264 (2:0.160.3011+gitcde9a93-2) unstable; urgency=medium . * Team upload * Upload to unstable * debian/rules: Fix awk invocation to work with make 4.2 and 4.3 (Closes: #966241) Checksums-Sha1: 24c90aa46891cc4ac4c4d48e29e21a1df506c372 2365 x264_0.160.3011+gitcde9a93-2.dsc 6aaaefe5bc0652efe6502455e25762d1b106f985 23228 x264_0.160.3011+gitcde9a93-2.debian.tar.xz Checksums-Sha256: f2c138aa9037ca2a16104428c8495671282db8919e0063432a60e9187ec04be9 2365 x264_0.160.3011+gitcde9a93-2.dsc 4cfb4e2abd4ac11db7a3d112348aa193992e52b2eebe686d41213405dac0a09c 23228 x264_0.160.3011+gitcde9a93-2.debian.tar.xz Files: 433d71a2c2aa765e01011e99f0cdc496 2365 libs optional x264_0.160.3011+gitcde9a93-2.dsc 32ba42934b7c4da760f16caf29ba5a2b 23228 libs optional x264_0.160.3011+gitcde9a93-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8dmhUACgkQafL8UW6n GZO8dxAAjwr1ly6Jr0woW2lckfcxMIGNvWnWBCU325dKGYmUIunVzMLHbG3ywYb7 u4CWPtv/5DIFjIAkL3tcQTfoY3fpmR4AT9FrOdk+LkMWcDfW9Aorar2oYHaRenja gOjp/Eb7o9LGXlTBm2JB7+KTmjl8OX2MmcvX7l0IxIqenOo7IVz+zqmaeOeQGSn2 sygeb4el9gOiq0a+CYp5ae+Fsv7UaZgTP8RhbJInDEbGkA5W9In5QM6g/6rux8Up EJnqKdNxA8f1xI9Oq3h1witDY6pZh0V+feNSSJswN5TC8xxfofdwmxSjX2wkGq8W Hjc5bd91E4P/PV3T9OC4QtrQrX+fGwYqpfL4PbiFsjovABSOv3Xi5UKQ4t31a47N vpipQmwKzT8fM6r2UEcMj2cYcEPTs5/JZsqskzMI4PBljnEuF9ao6PGuMW7fKkRN qyoJSUYqQ+PRaP23R9XmM1sgLfy0/wsVjtaYqcVY3DT5r2mQKc0K1OOoNdUnOkZH 11H5FKlQNIGj2RITYTdYOhUR8rjzIaGbYScrECI1Fh3HVQr1xhIJYZX7/kkGs4p8 M57fZ4rkcnR8duml5v1aCDJGWT6Ni2mDRP3N9AomUdHO8pLqLP2o0xNf2e/nqI38 0//ltv5tRkglYf7sXqZ9wWfm8Tsd4KKt9b0k0aewdgzV98IQisQ= =OfvN -END PGP SIGNATURE End Message ---
Bug#957680: marked as done (phlipple: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 15:22:24 + with message-id and subject line Bug#957680: fixed in phlipple 0.8.5-5 has caused the Debian Bug report #957680, regarding phlipple: 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.) -- 957680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:phlipple Version: 0.8.5-4 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/phlipple_0.8.5-4_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 [...] make[3]: Entering directory '/<>/extra' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/extra' Making all in src make[3]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o camera.o camera.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o engine.o engine.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o game.o game.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o gfxconstants.o gfxconstants.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o gradientrenderer.o gradientrenderer.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o interpolator.o interpolator.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o levels.o levels.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -DPACKAGE_SRC_DIR=\""."\" -DPACKAGE_DATA_DIR=\""/usr/share"\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o mainscreen.o mainscreen.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAG
Processed: tagging 966301, tagging 966300
Processing commands for cont...@bugs.debian.org: > tags 966301 + ftbfs Bug #966301 [src:guile-2.2] guile oom test fails on ppc64el Added tag(s) ftbfs. > tags 966300 + ftbfs Bug #966300 [src:guile-3.0] guile oom test fails on ppc64el Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966300 966301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957394: marked as pending in jumpnbump
Control: tag -1 pending Hello, Bug #957394 in jumpnbump 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/games-team/jumpnbump/-/commit/7a3a913370edb1e176a2bcd191cf052c28b3e337 Backport post-release patch from upstream to add future gcc default -fno-common and fix code (Closes: #957394). (this message was generated automatically) -- Greetings https://bugs.debian.org/957394
Processed: Bug#957394 marked as pending in jumpnbump
Processing control commands: > tag -1 pending Bug #957394 [src:jumpnbump] jumpnbump: ftbfs with GCC-10 Added tag(s) pending. -- 957394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957493: marked as done (liquidwar: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 14:45:15 + with message-id and subject line Bug#957493: fixed in liquidwar 5.6.5-2 has caused the Debian Bug report #957493, regarding liquidwar: 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.) -- 957493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:liquidwar Version: 5.6.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/liquidwar_5.6.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 [...] Compiling palette.c (cpu=default, debug=no, asm=no) Compiling parser.c (cpu=default, debug=no, asm=no) Compiling path.c (cpu=default, debug=no, asm=no) Compiling ping.c (cpu=default, debug=no, asm=no) Compiling pion.c (cpu=default, debug=no, asm=no) Compiling play.c (cpu=default, debug=no, asm=no) Compiling profile.c (cpu=default, debug=no, asm=no) Compiling protocol.c (cpu=default, debug=no, asm=no) protocol.c: In function ‘lw_protocol_ask_who’: protocol.c:287:32: warning: this statement may fall through [-Wimplicit-fallthrough=] 287 | who->network = 1; | ~^~~ protocol.c:293:17: note: here 293 | case LW_NETMESS_CODE_LOCAL: | ^~~~ Compiling random.c (cpu=default, debug=no, asm=no) Compiling rules.c (cpu=default, debug=no, asm=no) Compiling score.c (cpu=default, debug=no, asm=no) Compiling serial.c (cpu=default, debug=no, asm=no) Compiling sock2cli.c (cpu=default, debug=no, asm=no) Compiling sockex.c (cpu=default, debug=no, asm=no) Compiling sockunix.c (cpu=default, debug=no, asm=no) Compiling sound.c (cpu=default, debug=no, asm=no) Compiling speeds.c (cpu=default, debug=no, asm=no) Compiling startinf.c (cpu=default, debug=no, asm=no) Compiling startup.c (cpu=default, debug=no, asm=no) Compiling team.c (cpu=default, debug=no, asm=no) Compiling texture.c (cpu=default, debug=no, asm=no) Compiling thrdunix.c (cpu=default, debug=no, asm=no) thrdunix.c: In function ‘lw_thread_start’: thrdunix.c:84:38: warning: cast between incompatible function types from ‘void (*)(void *)’ to ‘void * (*)(void *)’ [-Wcast-function-type] 84 | if (pthread_create (&thread, NULL, (void *(*)(void *)) func, args) == 0) | ^ Compiling ticker.c (cpu=default, debug=no, asm=no) Compiling time.c (cpu=default, debug=no, asm=no) Compiling viewport.c (cpu=default, debug=no, asm=no) Compiling volume.c (cpu=default, debug=no, asm=no) Compiling watchdog.c (cpu=default, debug=no, asm=no) Compiling wave.c (cpu=default, debug=no, asm=no) Compiling wwwcli.c (cpu=default, debug=no, asm=no) Compiling x11icon.c (cpu=default, debug=no, asm=no) Linking liquidwar (host=default, debug=no, static=no, asm=no) /usr/bin/ld: fighter.o:./src/fighter.h:62: multiple definition of `FIGHTER_MOVE_X'; autoplay.o:./src/fighter.h:62: first defined here /usr/bin/ld: fighter.o:./src/fighter.h:63: multiple definition of `FIGHTER_MOVE_Y'; autoplay.o:./src/fighter.h:63: first defined here /usr/bin/ld: game.o:./src/fighter.h:63: multiple definition of `FIGHTER_MOVE_Y'; autoplay.o:./src/fighter.h:63: first defined here /usr/bin/ld: game.o:./src/fighter.h:62: multiple definition of `FIGHTER_MOVE_X'; autoplay.o:./src/fighter.h:62: first defined here /usr/bin/ld: info.o:./src/random.h:70: multiple definition of `LW_RANDOM_ON'; game.o:./src/random.h:70: first defined here /usr/bin/ld: inf
Bug#948970: marked as done (The build isn't compatible with python3)
Your message dated Sun, 26 Jul 2020 16:44:23 +0200
with message-id
and subject line Re: The build isn't compatible with python3
has caused the Debian Bug report #948970,
regarding The build isn't compatible with python3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
948970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-freefont
Version: 20120503-9
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
The fonts-freetype build scripts use a python syntax which isn't
compatible with python3, the attached patch does the minimal work to
have the build working with newer python versions (as in current Ubuntu
focal)
Cheers,
diff -Nru fonts-freefont-20120503/debian/changelog fonts-freefont-20120503/debian/changelog
--- fonts-freefont-20120503/debian/changelog 2019-01-21 14:47:57.0 +0100
+++ fonts-freefont-20120503/debian/changelog 2020-01-15 12:50:26.0 +0100
@@ -1,3 +1,11 @@
+fonts-freefont (20120503-10) unstable; urgency=medium
+
+ * debian/patches/build_python3_syntax.patch:
+- updated the build scripts syntax to be compatible with python3,
+ fixed the build on Ubuntu focal
+
+ -- Sebastien Bacher Wed, 15 Jan 2020 12:50:26 +0100
+
fonts-freefont (20120503-9) unstable; urgency=medium
* Fix the appearance of the Slovak glyphs.
diff -Nru fonts-freefont-20120503/debian/patches/build_python3_syntax.patch fonts-freefont-20120503/debian/patches/build_python3_syntax.patch
--- fonts-freefont-20120503/debian/patches/build_python3_syntax.patch 1970-01-01 01:00:00.0 +0100
+++ fonts-freefont-20120503/debian/patches/build_python3_syntax.patch 2020-01-15 12:50:26.0 +0100
@@ -0,0 +1,76 @@
+diff --git a/tools/generate/MacTT b/tools/generate/MacTT
+index 30d19e1..f93472f 100755
+--- a/tools/generate/MacTT
b/tools/generate/MacTT
+@@ -43,7 +43,7 @@ if argc > 1:
+ f = fontforge.open( argv[i] )
+ ttfile = f.fontname + ".mac.ttf"
+ vstr = trim_version_str( f )
+- print "Generating Mac TrueType file ", ttfile, ' ', vstr
++ print("Generating Mac TrueType file ", ttfile, ' ', vstr)
+ f.selection.all()
+ f.autoHint()
+ f.autoInstr()
+@@ -51,4 +51,4 @@ if argc > 1:
+ #f.generate( ttfile, flags=('opentype','old-kern') )
+ f.close()
+ else:
+- print "Usage: " + scriptname + " font.sfd [font.sfd ...]"
++ print("Usage: " + scriptname + " font.sfd [font.sfd ...]")
+diff --git a/tools/generate/OpenType b/tools/generate/OpenType
+index 4307231..0ab7987 100755
+--- a/tools/generate/OpenType
b/tools/generate/OpenType
+@@ -42,7 +42,7 @@ if argc > 1:
+ f = fontforge.open( argv[i] )
+ otfile = f.fontname + ".otf"
+ vstr = trim_version_str( f )
+- print "Generating OpenType file ", otfile, ' ', vstr
++ print("Generating OpenType file ", otfile, ' ', vstr)
+ # Wanted to set to 'UniocdeBmp' if there were no high unicodes
+ # but all attemtps to determine that from Python failed.
+ f.encoding = 'UnicodeFull'
+@@ -51,4 +51,4 @@ if argc > 1:
+ f.generate( otfile, flags=('opentype','old-kern','round') )
+ f.close()
+ else:
+- print "Usage: " + scriptname + " font.sfd [font.sfd ...]"
++ print("Usage: " + scriptname + " font.sfd [font.sfd ...]")
+diff --git a/tools/generate/TrueType b/tools/generate/TrueType
+index 1f6cc2f..974c84f 100755
+--- a/tools/generate/TrueType
b/tools/generate/TrueType
+@@ -42,7 +42,7 @@ if argc > 1:
+ f = fontforge.open( sys.argv[i] )
+ ttfile = f.fontname + ".ttf"
+ vstr = trim_version_str( f )
+- print "Generating TrueType file ", ttfile, ' ', vstr
++ print("Generating TrueType file ", ttfile, ' ', vstr)
+ # Wanted to set to 'UniocdeBmp' if there were no high unicodes
+ # but all attemtps to determine that from Python failed.
+ f.encoding = 'UnicodeFull'
+@@ -54,4 +54,4 @@ if argc > 1:
+ f.generate( ttfile, flags=('opentype','old-kern','no-hints') )
+ f.close()
+ else:
+- print "Usage: " + scriptname + " font.sfd [font.sfd ...]"
++ print("Usage: " + scriptname + " font.sfd [font.sfd ...]")
+diff --git a/tools/generate/WOFF b/tools/generate/WOFF
+index 7a3a790..45bff0b 100755
+--- a/tools/generate/WOFF
b/tools/generate/WOFF
+@@ -153,7 +153,7 @@ if argc > 1:
+ f = fontforge.open( sys.argv[i] )
+ woff_file = f.fontname + ".woff"
+ vstr = trim_version_str( f )
+- print "Generating WOFF file ", woff_file, ' ', vstr
++ print("Generating WOFF file ", woff_file, ' ', vstr)
+ # Wanted to set to 'UniocdeBmp' if there were no high unicodes
+ # but all attemtps to deter
Bug#958010: yubikey-personalization: ftbfs with GCC-10
Hello, Any rough timeframe as to when this FTBFS is fixed? Kind regards, Shayan Doust 0x6D7D441919D02395.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#957283: marked as done (gngb: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 13:48:34 + with message-id and subject line Bug#957283: fixed in gngb 20060309-5 has caused the Debian Bug report #957283, regarding gngb: 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.) -- 957283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gngb Version: 20060309-4 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/gngb_20060309-4_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: video_std.o:./src/message.h:24: multiple definition of `hl'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_std.o:./src/message.h:24: multiple definition of `wl'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_gl.o:./src/emu.h:67: multiple definition of `conf'; cpu.o:./src/emu.h:67: first defined here /usr/bin/ld: video_gl.o:./src/vram.h:95: multiple definition of `rb_on'; emu.o:./src/vram.h:95: first defined here /usr/bin/ld: video_gl.o:./src/video_std.h:30: multiple definition of `rb_shift'; emu.o:./src/video_std.h:30: first defined here /usr/bin/ld: video_gl.o:./src/sgb.h:47: multiple definition of `sgb_mask'; emu.o:./src/sgb.h:47: first defined here /usr/bin/ld: video_gl.o:./src/vram.h:65: multiple definition of `scyoff'; emu.o:./src/vram.h:65: first defined here /usr/bin/ld: video_gl.o:./src/vram.h:65: multiple definition of `scxoff'; emu.o:./src/vram.h:65: first defined here /usr/bin/ld: video_gl.o:./src/video_std.h:32: multiple definition of `scrR'; emu.o:./src/video_std.h:32: first defined here /usr/bin/ld: video_gl.o:./src/video_std.h:31: multiple definition of `dstR'; emu.o:./src/video_std.h:31: first defined here /usr/bin/ld: video_gl.o:./src/sgb.h:45: multiple definition of `sgb_pal_map'; emu.o:./src/sgb.h:45: first defined here /usr/bin/ld: video_gl.o:./src/sgb.h:44: multiple definition of `sgb_pal'; emu.o:./src/sgb.h:44: first defined here /usr/bin/ld: video_gl.o:./src/sgb.h:42: multiple definition of `sgb'; emu.o:./src/sgb.h:42: first defined here /usr/bin/ld: video_gl.o:./src/interrupt.h:101: multiple definition of `gbtimer'; cpu.o:./src/interrupt.h:101: first defined here /usr/bin/ld: video_gl.o:./src/interrupt.h:73: multiple definition of `vram_pal_line_temp'; cpu.o:./src/interrupt.h:73: first defined here /usr/bin/ld: video_gl.o:./src/interrupt.h:71: multiple definition of `gblcdc'; cpu.o:./src/interrupt.h:71: first defined here /usr/bin/ld: video_gl.o:./src/emu.h:71: multiple definition of `key'; cpu.o:./src/emu.h:71: first defined here /usr/bin/ld: video_gl.o:./src/emu.h:69: multiple definition of `sdl_joy'; cpu.o:./src/emu.h:69: first defined here /usr/bin/ld: video_gl.o:./src/message.h:24: multiple definition of `ym'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_gl.o:./src/message.h:24: multiple definition of `xm'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_gl.o:./src/message.h:24: multiple definition of `hl'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_gl.o:./src/message.h:24: multiple definition of `wl'; emu.o:./src/message.h:24: first defined here /usr/bin/ld: video_gl.o:./src/vram.h:92: multiple definition of `gb_spr'; emu.o:./src/vram.h:92: first defined here /usr/bin/ld: menu.o:./src/emu.h:67: multiple definition of `conf'; cpu.o:./src/emu.h:67: first defined here /usr/bin/ld: menu.o:./src/message.h:24: multiple def
Bug#957625: marked as done (odb: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 13:49:24 +
with message-id
and subject line Bug#957625: fixed in odb 2.4.0-13
has caused the Debian Bug report #957625,
regarding odb: 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.)
--
957625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:odb
Version: 2.4.0-12
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/odb_2.4.0-12_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
[...]
am__tar='tar --format=ustar -chf - "$$tardir"'
am__untar='tar -xf -'
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/config/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
plugindir=''
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "odb"
#define PACKAGE_TARNAME "odb"
#define PACKAGE_VERSION "2.4.0"
#define PACKAGE_STRING "odb 2.4.0"
#define PACKAGE_BUGREPORT "odb-us...@codesynthesis.com"
#define PACKAGE_URL ""
#define PACKAGE "odb"
#define VERSION "2.4.0"
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
configure: exit 1
dh_auto_configure: error: ./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 returned exit code 1
make: *** [debian/rules:29: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: odb
Source-Version: 2.4.0-13
Done: Laszlo Boszormenyi (GCS)
We believe that the bug you reported is fixed in the latest version of
odb, 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 957...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) (supplier of updated odb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please conta
Bug#957234: marked as done (freegish: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 13:48:29 + with message-id and subject line Bug#957234: fixed in freegish 1.53+git20170110+dfsg-2 has caused the Debian Bug report #957234, regarding freegish: 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.) -- 957234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freegish Version: 1.53+git20170110+dfsg-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/freegish_1.53+git20170110+dfsg-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 [...] cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/sdl/endian.c.o -c /<>/src/sdl/endian.c [ 87%] Building C object src/CMakeFiles/freegish.dir/sdl/file.c.o [ 87%] Building C object src/CMakeFiles/freegish.dir/sdl/event.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/sdl/event.c.o -c /<>/src/sdl/event.c cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/sdl/file.c.o -c /<>/src/sdl/file.c [ 89%] Building C object src/CMakeFiles/freegish.dir/sdl/video.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/sdl/video.c.o -c /<>/src/sdl/video.c [ 91%] Building C object src/CMakeFiles/freegish.dir/video/glfunc.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/video/glfunc.c.o -c /<>/src/video/glfunc.c [ 93%] Building C object src/CMakeFiles/freegish.dir/video/opengl.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/video/opengl.c.o -c /<>/src/video/opengl.c [ 94%] Building C object src/CMakeFiles/freegish.dir/video/text.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/freegish.dir/video/text.c.o -c /<>/src/video/text.c [ 96%] Building C object src/CMakeFiles/freegish.dir/video/texture.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DDATAPATH=\"/usr/share/games/freegish\" -I/usr/include/SDL -I/usr/include/AL -g -O2
Processed: tagging 966171
Processing commands for cont...@bugs.debian.org: > tags 966171 + upstream Bug #966171 [src:ydpdict] ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 966171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964957: ugrep: Baseline violation on several architectures
Hi Adrian Thanks for your message. I have been Out Of office the last two weeks, let me take a look at this asap. Best regards On Mon, Jul 13, 2020 at 1:33 PM Adrian Bunk wrote: > > Source: ugrep > Version: 2.1.1+dfsg-1 > Severity: serious > > After looking at the build log and sources, there are several > baseline violations due to the package being built for what > is supported on the buildd instead of the architecture baseline: > - -march=native is always wrong in a distribution build > - SSE2 is part of the amd64 baseline, but not the i386 baseline > - AVX is not part of the amd64 or i386 baseline > - NEON is not part of the armhf baseline -- Ricardo Ribalda
Bug#957048: marked as done (blastem: FTBFS with gcc-10: multiple definition of vdp_regs)
Your message dated Sun, 26 Jul 2020 13:04:18 + with message-id and subject line Bug#957048: fixed in blastem 0.6.3.3-3 has caused the Debian Bug report #957048, regarding blastem: FTBFS with gcc-10: multiple definition of vdp_regs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:blastem Version: 0.6.3.3-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/blastem_0.6.3.3-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 [...] cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o vgmplay.o vgmplay.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o ym2612.o ym2612.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o psg.o psg.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o wave.o wave.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o blastem.o blastem.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/blastem'"' -DDATA_PATH='"'/usr/share/games/blastem'"' -c -o system.o system.c cc -O2 -flto -g -fPIE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/x86_64-linux-gnu/SDL2 -I/usr/include/SDL2 -std=gnu99 -Wreturn-type -Werror=return-type -Werror=implicit-function-declaration -Wno-unused-value -DHAS_PROC -DHAVE_UNISTD_H -Wno-unused-result -DX86_64 -m64 -DCONFIG_PATH='"'/etc/
Bug#957608: marked as done (nfs-utils: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 12:18:33 +
with message-id
and subject line Bug#957608: fixed in nfs-utils 1:1.3.4-4
has caused the Debian Bug report #957608,
regarding nfs-utils: 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.)
--
957608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nfs-utils
Version: 1:1.3.4-2.5
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/nfs-utils_1.3.4-2.5_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
[...]
51 | dtable_ent(mount_dump,1,void,mountlist), /* DUMP */
| ^~
../../support/include/rpcmisc.h:41:3: warning: cast between incompatible
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
41 | (xdrproc_t)xdr_##res_type, sizeof(res_type), \
| ^
mount_dispatch.c:52:2: note: in expansion of macro ‘dtable_ent’
52 | dtable_ent(mount_umnt,1,dirpath,void), /* UMNT */
| ^~
../../support/include/rpcmisc.h:40:3: warning: cast between incompatible
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
40 | (xdrproc_t)xdr_##arg_type, sizeof(arg_type), \
| ^
mount_dispatch.c:53:2: note: in expansion of macro ‘dtable_ent’
53 | dtable_ent(mount_umntall,1,void,void), /* UMNTALL */
| ^~
../../support/include/rpcmisc.h:41:3: warning: cast between incompatible
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
41 | (xdrproc_t)xdr_##res_type, sizeof(res_type), \
| ^
mount_dispatch.c:53:2: note: in expansion of macro ‘dtable_ent’
53 | dtable_ent(mount_umntall,1,void,void), /* UMNTALL */
| ^~
../../support/include/rpcmisc.h:40:3: warning: cast between incompatible
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
40 | (xdrproc_t)xdr_##arg_type, sizeof(arg_type), \
| ^
mount_dispatch.c:54:2: note: in expansion of macro ‘dtable_ent’
54 | dtable_ent(mount_export,1,void,exports), /* EXPORT */
| ^~
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall
-Wextra -Wstrict-prototypes -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\"
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-cache.o `test -f
'cache.c' || echo './'`cache.c
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall
-Wextra -Wstrict-prototypes -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\"
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-svc_run.o `test -f
'svc_run.c' || echo './'`svc_run.c
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall
-Wextra -Wstrict-prototypes
Bug#966304: marked as done (lua-readline: readline.lua not installed)
Your message dated Sun, 26 Jul 2020 12:05:56 + with message-id and subject line Bug#966304: fixed in lua-readline 2.7-3 has caused the Debian Bug report #966304, regarding lua-readline: readline.lua not installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lua-readline Version: 2.7-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, Thanks for packagging lua-readline. Unfortunately, the package installs only the binary module and is missing the `readline.lua` file. Easy fix, see attached patch. -- Regards, Kim "Zash" Alvefur PS: Yes, I've built and tested this on Stable. Please excuse my Franken-Debian. :) DS. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lua-readline depends on: ii libc6 2.28-10 ii libreadline7 7.0-5 ii lua-posix 33.4.0-3 lua-readline recommends no packages. lua-readline suggests no packages. -- no debconf information >From be1e9c73c870b2d60fec5749729520a9737e1161 Mon Sep 17 00:00:00 2001 From: Kim Alvefur Date: Sun, 26 Jul 2020 12:49:08 +0200 Subject: [PATCH] Include missing Lua source in install --- debian/lua5.1.dh-lua.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/lua5.1.dh-lua.conf b/debian/lua5.1.dh-lua.conf index 51ca5ad..802b326 100644 --- a/debian/lua5.1.dh-lua.conf +++ b/debian/lua5.1.dh-lua.conf @@ -11,7 +11,7 @@ LUA_MODNAME_CPART_UNDERSCORE=readline ### things relative to the lua library part LUA_HEADER= -LUA_SOURCES= +LUA_SOURCES=readline.lua LUA_MODNAME= LUA_TEST= -- 2.20.1 --- End Message --- --- Begin Message --- Source: lua-readline Source-Version: 2.7-3 Done: Sergei Golovan We believe that the bug you reported is fixed in the latest version of lua-readline, 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. Sergei Golovan (supplier of updated lua-readline 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, 26 Jul 2020 14:47:17 +0300 Source: lua-readline Architecture: source Version: 2.7-3 Distribution: unstable Urgency: medium Maintainer: Debian Lua Team Changed-By: Sergei Golovan Closes: 966304 Changes: lua-readline (2.7-3) unstable; urgency=medium . * Add missing readline.lua to the binary package (closes: #966304). Checksums-Sha1: 159182bc4f441bac401053e7492cf3306e8286fd 2040 lua-readline_2.7-3.dsc 95a3d5dc973f037abdfadf9056ad8f6815fa98d3 2332 lua-readline_2.7-3.debian.tar.xz a3d1e0e24fdf9ba8a18839cccf3f59ad970922bf 6573 lua-readline_2.7-3_amd64.buildinfo Checksums-Sha256: 9025eff4eb52d463d21db42b6bb973a5922708893411cedea33f3dad9a1a519d 2040 lua-readline_2.7-3.dsc 67fcc6343b302f1585a1706e7bf7bea6aee6aed2bf7fb9a2d6ab29aa5a9bc7ec 2332 lua-readline_2.7-3.debian.tar.xz 648f04b0736cb9e22ef990aaba1ba99dc17204851a372f1affe0efb0f93b69ca 6573 lua-readline_2.7-3_amd64.buildinfo Files: da899615d91cd12ce0a44c520d5d60a0 2040 interpreters optional lua-readline_2.7-3.dsc 2384f1ea9da30225681015ea05476386 2332 interpreters optional lua-readline_2.7-3.debian.tar.xz 7dd295473319f46d10cecba66bf437f5 6573 interpreters optional lua-readline_2.7-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAl8dbgcACgkQTyrk60tj 54cRsA/+JKAGIrF8YcEAVzzx1qIzS18cvG4QcxfHm53LSf+4RwXXl02qCb8mDEEt VpMVnKxC5CU3X34steZ7wgLbpKrflGaNCxJBnqpi2uRC4+gZZKquCzutVcypnEl2 mamhWMnElwV8QzH2RXfeHHTr7qwY6WhgDUdfxlE/n9SM22eP3vtAf4qofuIXi5cW eQvmGM1rtyldQ541UCw4C+r8noGP+WSEgt4NYS+qo
Bug#964231: faketime: FTBFS with glibc 2.31 due to ftime deprecation
On 2020-07-13 23:42, Aurelien Jarno wrote:
> control: severity -1 serious
>
> On 2020-07-03 23:47, Aurelien Jarno wrote:
> > Package: faketime
> > Version: 0.9.7-3
> > Severity: important
> > Tags: patch upstream
> >
> > faketime fails to build from source with glibc 2.31:
> >
> > | gcc -c -std=gnu99 -Wall -DFAKE_STAT -Werror -Wextra timetest.c
> > | ./testframe.sh functests
> > | # Begin Test Suites in functests
> > |
> > | # Begin functests/test_exclude_mono.sh
> > | # PLATFORM=linuxlike
> > | timetest.c: In function ‘main’:
> > | timetest.c:143:5: error: ‘ftime’ is deprecated
> > [-Werror=deprecated-declarations]
> > | 143 | ftime(&tb);
> > | | ^
> > | In file included from timetest.c:25:
> > | /usr/include/x86_64-linux-gnu/sys/timeb.h:39:12: note: declared here
> > |39 | extern int ftime (struct timeb *__timebuf)
> > | |^
> > | cc1: all warnings being treated as errors
> > | make[2]: *** [Makefile:12: timetest.o] Error 1
> > | make[2]: *** Waiting for unfinished jobs
> >
> >
> > The full build log is available there:
> >
> > http://qa-logs.debian.net/2020/06/24/faketime_0.9.7-3_unstable_glibc-exp.log
> >
> > In glibc 2.31, the ftime function has been marked as deprecated, though
> > it's still usable. however the tests are run with -Wall -Wextra -Werror,
> > turning causing this deprecation into an error.
> >
> > Upstream already has a fix for this issue, although the issue is wrongly
> > attributed to gcc 9 instead of glibc 2.31:
> >
> > https://github.com/wolfcw/libfaketime/commit/f19d68ea3231f1af7a6e3913dc6d3c46f73947b2
> >
> > This patch applies cleanly to the version in debian and correctly fixes
> > the issue. It would be nice if you can apply it relatively soon so that
> > we can start the transition.
>
> Note that glibc 2.31 is now in unstable. I am therefore increasing the
> severity to serious.
I have prepared an NMU for faketime (versioned as 0.9.7-3.1), fixing the
build issue with glibc 2.31. You will find the diff attached. I have
uploaded it to DELAYED/7. Please feel free to tell me if I should delay
it longer or cancel it altogether.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru faketime-0.9.7/debian/changelog faketime-0.9.7/debian/changelog
--- faketime-0.9.7/debian/changelog 2018-10-07 00:00:03.0 +
+++ faketime-0.9.7/debian/changelog 2020-07-26 11:36:15.0 +
@@ -1,3 +1,11 @@
+faketime (0.9.7-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Cherry-Pick fixes for the FTBFS with glibc 2.31 from upstream git
+repository. (Closes: #964231)
+
+ -- Aurelien Jarno Sun, 26 Jul 2020 13:36:15 +0200
+
faketime (0.9.7-3) unstable; urgency=medium
* Acknowledge NMU (thanks, Tobias!)
diff -Nru faketime-0.9.7/debian/patches/0007-Fix-make-test-build-failure-on-gcc-9.3.patch faketime-0.9.7/debian/patches/0007-Fix-make-test-build-failure-on-gcc-9.3.patch
--- faketime-0.9.7/debian/patches/0007-Fix-make-test-build-failure-on-gcc-9.3.patch 1970-01-01 00:00:00.0 +
+++ faketime-0.9.7/debian/patches/0007-Fix-make-test-build-failure-on-gcc-9.3.patch 2020-07-26 11:35:03.0 +
@@ -0,0 +1,31 @@
+From: Robin Linden
+Date: Thu, 28 May 2020 23:09:07 +0200
+Subject: [PATCH] Fix make test build failure on gcc 9.3
+
+On Ubuntu 20.04 using gcc 9.3, make test fails due to a deprecated
+function (ftime) warning in combination with -Werror in timetest.c.
+Since the warning is from a test testing that the deprecated function
+can be replaced using LD_PRELOAD, I think it's reasonable to just
+silence the warning in that case.
+---
+ test/timetest.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/test/timetest.c b/test/timetest.c
+index e9aa837..c33368c 100644
+--- a/test/timetest.c
b/test/timetest.c
+@@ -216,7 +216,10 @@ printf("%s", 0 == 1 ? argv[0] : "");
+ printf("time() : Current date and time: %s", ctime(&now));
+ printf("time(NULL) : Seconds since Epoch : %u\n", (unsigned int)time(NULL));
+
++#pragma GCC diagnostic push
++#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
+ ftime(&tb);
++#pragma GCC diagnostic pop
+ printf("ftime(): Current date and time: %s", ctime(&tb.time));
+
+ printf("(Intentionally sleeping 2 seconds...)\n");
+--
+2.27.0
+
diff -Nru faketime-0.9.7/debian/patches/series faketime-0.9.7/debian/patches/series
--- faketime-0.9.7/debian/patches/series 2018-10-06 23:53:11.0 +
+++ faketime-0.9.7/debian/patches/series 2020-07-26 11:35:16.0 +
@@ -4,3 +4,4 @@
0004-libfaketime.c-fix-strncpy-issues-raised-by-gcc-8.x.patch
0005-libfaketime.c-fix-pthread_cleanup_push-build-failure.patch
0006-faketime.c-fix-shared_objs-array-size.patch
+0007-Fix-make-test-build-failure-on-gcc-9.3.patch
signature.asc
Description: PGP signature
Bug#932725: marked as done (libunwind8: segfault on MIPS, fix needs backporting)
Your message dated Sun, 26 Jul 2020 11:47:08 +
with message-id
and subject line Bug#932725: fixed in libunwind 1.2.1-10~deb10u1
has caused the Debian Bug report #932725,
regarding libunwind8: segfault on MIPS, fix needs backporting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
932725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libunwind
Version: 1.2.1-9
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I was running i-g-t on MIPS and hit a segfault during a stack
trace dump.
I then built the package from source to reproduce it, and found a
fix upstream for it (patch attached).
Discussion on the igt-dev mailing list:
https://lists.freedesktop.org/archives/igt-dev/2019-July/015029.html
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: mips
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
>From 23ed1a35645e9e83beb2d4de0bd682c18d9fd58f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=9A=D0=BE=D1=80=D0=BE=D0=BB=D0=B5=D0=B2=20=D0=A1=D0=B5?=
=?UTF-8?q?=D1=80=D0=B3=D0=B5=D0=B9?=
Date: Wed, 22 Jun 2016 19:53:02 +0300
Subject: [PATCH] tdep_uc_addr: use +4 offset for UNW_MIPS_PC on MIPS (be)
According to mcontext_t definition its "pc" field
is also 64 bit wide and thus requires 4 byte offset
on MIPS32 (be).
---
src/mips/Ginit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mips/Ginit.c b/src/mips/Ginit.c
index 8290c408..83b100fb 100644
--- a/src/mips/Ginit.c
+++ b/src/mips/Ginit.c
@@ -59,7 +59,7 @@ tdep_uc_addr (ucontext_t *uc, int reg)
{
char *addr = uc_addr (uc, reg);
- if (reg >= UNW_MIPS_R0 && reg <= UNW_MIPS_R31
+ if (((reg >= UNW_MIPS_R0 && reg <= UNW_MIPS_R31) || reg == UNW_MIPS_PC)
&& tdep_big_endian (unw_local_addr_space)
&& unw_local_addr_space->abi == UNW_MIPS_ABI_O32)
addr += 4;
--
2.20.1
--- End Message ---
--- Begin Message ---
Source: libunwind
Source-Version: 1.2.1-10~deb10u1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
libunwind, 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 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated libunwind package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 23 Jul 2020 22:00:53 +0300
Source: libunwind
Architecture: source
Version: 1.2.1-10~deb10u1
Distribution: buster
Urgency: high
Maintainer: Adrian Bunk
Changed-By: Adrian Bunk
Closes: 923962 932725
Changes:
libunwind (1.2.1-10~deb10u1) buster; urgency=medium
.
* Rebuild on buster.
.
libunwind (1.2.1-10) unstable; urgency=high
.
* Manually enable C++ exception support only on i386 and amd64,
it is known broken on several other architectures.
Thanks to Bernhard Übelacker. (Closes: #923962)
* Backport upstream fix for segfaults on mips,
thanks to Guillaume Tucker. (Closes: #932725)
Checksums-Sha1:
469399601af62f01f6e26bf16e66fc597e2d6a21 2573 libunwind_1.2.1-10~deb10u1.dsc
9c2eab3e7e9468cb682313422db4603ab36764da 19864
libunwind_1.2.1-10~deb10u1.debian.tar.xz
Checksums-Sha256:
6b6564f9b58c0f7e3d575f18b3581cd59368c3a632e1cbff18c1c6361d77a39b 2573
libunwind_1.2.1-10~deb10u1.dsc
4de4cc32a3b8e3b285b7169124ad854b7e1074d3bd44b69fbcb47bde3e0eff9b 19864
libunwind_1.2.1-10~deb10u1.debian.tar.xz
Files:
abc24a50cd701901dd01c65e358ea99e 2573 libs optional
libunwind_1.2.1-10~deb10u1.dsc
96ae791e7dfe275f218efd254e0be5dc 19864 libs optional
libunwind_1.2.1-10~deb10u1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8Z4e0ACgkQiNJCh6LY
mLErRBAAjQbEXkQPjTtOIaP4/eKF4JqrzztWKokGfpRR8do+0Yhk0DWqszXG3TMJ
PUcMF8WyktFnDkU/Pdmz9ov
Bug#964399: Should ganglia be removed?
Hi Marcos, I overlooked this in my inbox.. On Tue, Jul 07, 2020 at 11:15:58PM +0200, Marcos Fouces wrote: > Hello Moritz > > I did some work time ago on ganglia [1] but i never get this work > published due to unactive/unresponsive uploaders. > > I also done some work on ganglia-web and ganglia-linux-modules packages > (also unpublished). > > I believe that it is still a good piece of software that deserve its > place on Debian so i would like to step up as uploader (co-uploaders > welcome!) if needed. > > I also would like to maintain it under pkg-security team umbrella. > > Please, let me know your thoughs. Do you have a plan how to deal with the plugins in Python 2? Will you port them yourself or rather drop them? Packaging it under the pkg-security umbrella feels a little off/odd, but if you think Ganglia is still useful in 2020 and want to adopt it and fix the bugs, sure please go ahead :-) Cheers, Moritz
Bug#948989: marked as done (ksh: CVE-2019-14868)
Your message dated Sun, 26 Jul 2020 11:17:10 + with message-id and subject line Bug#948989: fixed in ksh 93u+20120801-3.4+deb10u1 has caused the Debian Bug report #948989, regarding ksh: CVE-2019-14868 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ksh Version: 2020.0.0-2 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for ksh. CVE-2019-14868[0]: |environment variables on startup are interpreted as arithmetic |expression leading to code injection If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14868 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14868 [1] https://github.com/att/ast/commit/c7de8b641266bac7c77942239ac659edfee9ecd2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ksh Source-Version: 93u+20120801-3.4+deb10u1 Done: Anuradha Weeraman We believe that the bug you reported is fixed in the latest version of ksh, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anuradha Weeraman (supplier of updated ksh 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, 12 Jul 2020 11:26:07 -0400 Source: ksh Architecture: source Version: 93u+20120801-3.4+deb10u1 Distribution: buster Urgency: high Maintainer: Nicholas Bamber Changed-By: Anuradha Weeraman Closes: 948989 Changes: ksh (93u+20120801-3.4+deb10u1) buster; urgency=high . * Fix for CVE-2019-14868: in ksh version 20120801, a flaw was found in the way it evaluates certain environment variables. An attacker could use this flaw to override or bypass environment restrictions to execute shell commands. Services and applications that allow remote unauthenticated attackers to provide one of those environment variables could allow them to exploit this issue remotely. (Closes: #948989) Checksums-Sha1: 41bfe116eae6ef9c6a34ad7100017d00580eb63a 1876 ksh_93u+20120801-3.4+deb10u1.dsc c3647a3a8232b66e8f731fc34213441b2e7567e0 17576 ksh_93u+20120801-3.4+deb10u1.debian.tar.xz ef87d7639771eced1d5890013942d6c6970e4f5f 5742 ksh_93u+20120801-3.4+deb10u1_amd64.buildinfo Checksums-Sha256: 1b6ab2859bdb0adb96f2b2f7d3116008f5382f0a27871549b658103db281e941 1876 ksh_93u+20120801-3.4+deb10u1.dsc f3379767c58f9c6c1915919f05520bf56cd2429884a7b8c76576206301f2c2b0 17576 ksh_93u+20120801-3.4+deb10u1.debian.tar.xz b0deb85adc29eb2b6d7c67bf2746b2c184059c84b9da604b791ebddebeaa0570 5742 ksh_93u+20120801-3.4+deb10u1_amd64.buildinfo Files: f9f2ac68acee3d114126f43e7fb8209d 1876 shells optional ksh_93u+20120801-3.4+deb10u1.dsc 28ee52a4dcc5c7d31dc2a060d3cc2d58 17576 shells optional ksh_93u+20120801-3.4+deb10u1.debian.tar.xz 17fbb74f473b84558f336fae443def8a 5742 shells optional ksh_93u+20120801-3.4+deb10u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE9WuPFOAUze9dBH/BY221odkYYP0FAl8cl8AACgkQY221odkY YP3PnxAAqCzrBi0Z79iGei4fhbJKgKcG8ZsYu26oOan8eEKiUsNGLayu1EVmxAhF Qn38oXceYk+rQxF6iBlbv5EWPbvUU4GPobArHLNN0aW8w8wwQ4jRCR8n7h9evNMP SDYZX8TPX9fNjFYRX4Ya/CNfzPlknqwRER0nluM1Nsy/AoLYTzW51ZXX18KBvS0w De1DyoQ0nvQdlwE6DahTK9gnv2Aqhmk/FzwWrjVLdCIXzJ3MFg1IX2BDixz0S5hT ivEDMhXoaYEoC0dZvWpwAtZ/+bmF4hn1xf9cErLDhWRhc47i2Q0Wa1LoPsQFI4jr iQQo/5cy0KgGeMwtch/EzFBiXHZHmnkjlHRnNCITP6POLmuzBrza9+C8VJiuteT9 +eD5bSpE5HtZWfmDkUlSfrN6sB1gUas8bStAXO0E1Vl6gIe2Xv4h9XZzilvQjT9m EgmTeqYfH31N1k7M6bYleSFsqfhzfqHyLeqsfCgFzeTIqAqC1r1k2ooFUQX/d0GY QNPgSfdyFsAI2Mb4UsL301aINqWDRnRY05+MCGCVvhEZQUowyB1/VHXb6NpMyqpP n44FaRrCRY116hsn815ZuwBnkS1Ov0q8U/qHsovoXWrGayzY1lySugG4GVgLlK1M L5qqUcwtL1FJFM1Y7SpEUlQvy+k6h9bpwWI5vPymRHxCx27SkZc= =mZy6 -END PGP SIGNATURE End Message ---
Bug#936288: cfv: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:13:06AM +, Matthias Klose wrote: > Package: src:cfv > Version: 1.18.3-2.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal Hi Stefan, given your comment at https://github.com/cfv-project/cfv/issues/8#issuecomment-615215686, let's proceed with removal? Cheers, Moritz
Bug#966304: lua-readline: readline.lua not installed
Package: lua-readline Version: 2.7-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, Thanks for packagging lua-readline. Unfortunately, the package installs only the binary module and is missing the `readline.lua` file. Easy fix, see attached patch. -- Regards, Kim "Zash" Alvefur PS: Yes, I've built and tested this on Stable. Please excuse my Franken-Debian. :) DS. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lua-readline depends on: ii libc6 2.28-10 ii libreadline7 7.0-5 ii lua-posix 33.4.0-3 lua-readline recommends no packages. lua-readline suggests no packages. -- no debconf information >From be1e9c73c870b2d60fec5749729520a9737e1161 Mon Sep 17 00:00:00 2001 From: Kim Alvefur Date: Sun, 26 Jul 2020 12:49:08 +0200 Subject: [PATCH] Include missing Lua source in install --- debian/lua5.1.dh-lua.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/lua5.1.dh-lua.conf b/debian/lua5.1.dh-lua.conf index 51ca5ad..802b326 100644 --- a/debian/lua5.1.dh-lua.conf +++ b/debian/lua5.1.dh-lua.conf @@ -11,7 +11,7 @@ LUA_MODNAME_CPART_UNDERSCORE=readline ### things relative to the lua library part LUA_HEADER= -LUA_SOURCES= +LUA_SOURCES=readline.lua LUA_MODNAME= LUA_TEST= -- 2.20.1
Bug#966235: marked as done (phoc FTBFS with wlroots 0.11.0)
Your message dated Sun, 26 Jul 2020 10:18:45 +
with message-id
and subject line Bug#966235: fixed in phoc 0.4.1-1
has caused the Debian Bug report #966235,
regarding phoc FTBFS with wlroots 0.11.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phoc
Version: 0.1.9-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phoc.html
https://buildd.debian.org/status/package.php?p=phoc&suite=sid
...
../src/render.c: In function ‘scan_out_fullscreen_view’:
../src/render.c:281:51: error: passing argument 2 of ‘wlr_output_attach_buffer’
from incompatible pointer type [-Werror=incompatible-pointer-types]
281 | if (!wlr_output_attach_buffer(wlr_output, surface->buffer)) {
|~~~^~~~
| |
| struct
wlr_client_buffer *
In file included from /usr/include/wlr/types/wlr_surface.h:18,
from ../src/layers.h:5,
from ../src/render.c:21:
/usr/include/wlr/types/wlr_output.h:327:21: note: expected ‘struct wlr_buffer
*’ but argument is of type ‘struct wlr_client_buffer *’
327 | struct wlr_buffer *buffer);
| ~~~^~
../src/render.c:281:6: error: invalid use of void expression
281 | if (!wlr_output_attach_buffer(wlr_output, surface->buffer)) {
| ^
cc1: some warnings being treated as errors
--- End Message ---
--- Begin Message ---
Source: phoc
Source-Version: 0.4.1-1
Done: Arnaud Ferraris
We believe that the bug you reported is fixed in the latest version of
phoc, 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.
Arnaud Ferraris (supplier of updated phoc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 25 Jul 2020 10:53:43 +0200
Source: phoc
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers
Changed-By: Arnaud Ferraris
Closes: 966235
Changes:
phoc (0.4.1-1) unstable; urgency=medium
.
[ Sebastian Krzyszkowiak ]
* debian: Add sign-tags=true to gbp.conf
.
[ Arnaud Ferraris ]
* New upstream version 0.4.1 (Closes: #966235)
* d/upstream: add missing fields to metadata file.
Fixes: lintian: upstream-metadata-missing-bug-tracking
* d/install: install scale-to-fit helper
Checksums-Sha1:
6f25d1a29b5090497b7cbd62bb56f49e9ae35773 2211 phoc_0.4.1-1.dsc
7e1a12719b8270cd4601012411471cbdbb69e0bf 133056 phoc_0.4.1.orig.tar.gz
48197f400187842537ad273e34fadb57d1ea55a3 4976 phoc_0.4.1-1.debian.tar.xz
754520c8657b78622521ce8cdeb6b2b286740bf7 16105 phoc_0.4.1-1_source.buildinfo
Checksums-Sha256:
391f2b6f71a5ebbfe65c2d4c94b308a79e867d60633cebe397689c67de24b85d 2211
phoc_0.4.1-1.dsc
215a10b5c2b10bacd57c3b097cbff3b85627db0d8e633e8bb1831548f7bff730 133056
phoc_0.4.1.orig.tar.gz
4eafa142e5abf0c1681c68f9d91d7071f19a52f193430ed034e00255c30487dd 4976
phoc_0.4.1-1.debian.tar.xz
ea94c7a06360914ea57e55d50678ba41f72e05b9d8f6c4b19f55248c3177430a 16105
phoc_0.4.1-1_source.buildinfo
Files:
fdd9d0cf6b19be210b2a72f78ee45ec9 2211 x11 optional phoc_0.4.1-1.dsc
50e2cde5d44ca90e3daca95190309c7f 133056 x11 optional phoc_0.4.1.orig.tar.gz
89225c30b1fc88fd16160c79b73993b6 4976 x11 optional phoc_0.4.1-1.debian.tar.xz
8638d9154c1ed2403dc9458d4474a3bf 16105 x11 optional
phoc_0.4.1-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAl8dUvEACgkQJb+GUkr8
weNYMg//VYqX75ys2XDt/YLwuKiGWYImKLZqLthtS1N2QAXfT3V0b75mxT5MwIDE
gF9RkXggb9+RD9Gvir23S71OChwWZXx9UoCcOQ/JdAR4FWpauQ9SmKnVT8oawSxL
ApbmJHbJgLLRY6sHGHKizveuJ1zsxA+wY65uIh9/sSL0Ew4OlFuVMmfzzCh6KXNO
DB4fsBFCANfn0gLjvzIlScA1YS76XxuazVpbkZ9R11Xmr01gZnEijJkDwd+umfa3
rxAyrvFYB+Dl0uOJJI1W4l0ObtgNH+P/EKM7qvSmDsAzzu6ec7RGblolGAzJrPci
N2UyAJC+vOOg+0FvqKAdXFCs6JKdLoP5MMeI/Nql2mEZ3RQi+f/zhHZDNDUBM2Gv
Mu6ZmdLt9Cf
Bug#965153: marked as done (gscan2pdf: "fails to open device" for Epson NX100)
Your message dated Sun, 26 Jul 2020 10:05:30 +
with message-id
and subject line Bug#965153: fixed in gscan2pdf 2.8.2-1
has caused the Debian Bug report #965153,
regarding gscan2pdf: "fails to open device" for Epson NX100
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
965153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gscan2pdf
Version: 2.8.0-1, 2.8.1-1
Severity: grave
Except for a couple of times I've been able to get it to work (without knowing
what it was that made it finally work after minutes of battle)...
* when I start gscan2pdf it claims it does not see my scanner and offers to
rescan
or continue without
* rescanning sometimes get me back to this window, sometimes to main screen
* from main screen when I click the scan button, I often get the same complaint
* sometimes I get to the scan dialog with "Epson NX100" properly selected, but
then
launching the scan it complains that it "first has to open the device" (good
guess,
but I'd thought it would do that for me). After which the UI is completely
unresponsive
and I have to kill the app
Upgrading to unstable just adds me a "restart gscan2pdf" in the initial failure
dialog,
but that does not help either.
Downgrading to stable's 2.3.0-1 gets me back a fully working version.
--- End Message ---
--- Begin Message ---
Source: gscan2pdf
Source-Version: 2.8.2-1
Done: Jeffrey Ratcliffe
We believe that the bug you reported is fixed in the latest version of
gscan2pdf, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeffrey Ratcliffe (supplier of updated gscan2pdf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 25 Jul 2020 18:38:25 +0200
Source: gscan2pdf
Architecture: source
Version: 2.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Jeffrey Ratcliffe
Changed-By: Jeffrey Ratcliffe
Closes: 965153
Changes:
gscan2pdf (2.8.2-1) unstable; urgency=low
.
* New upstream release
Closes: #965153 ("fails to open device" for Epson NX100)
Checksums-Sha1:
c6f5eecd7011919a661917a2e3f471432cad 2798 gscan2pdf_2.8.2-1.dsc
b29f7efeb4bc0094bfa391df97aecd6743546163 477968 gscan2pdf_2.8.2.orig.tar.xz
47e720e5b3a352d0dd0f61d3e15863dea5069390 833 gscan2pdf_2.8.2.orig.tar.xz.asc
3a868fefc239f88a5bb32129d0d53b8c5079093a 11360 gscan2pdf_2.8.2-1.debian.tar.xz
3efb57e42dea3fe6968601851fff0b3d328470ce 5407
gscan2pdf_2.8.2-1_source.buildinfo
Checksums-Sha256:
133296315282c375a30bd0c260ce2a0be37ed774795a0af34ad6ee1285c5c166 2798
gscan2pdf_2.8.2-1.dsc
4328433f62bb9c7a9182a2c80f0d6b748f4c39b01c2e6b8a1733c34403e7df36 477968
gscan2pdf_2.8.2.orig.tar.xz
906e7d96f9418a8726c10a8f1dc20d69c0efb279e2fd770a507331895924522b 833
gscan2pdf_2.8.2.orig.tar.xz.asc
50fad11229ed65446712f67016ab2f8fa7a3fe83376f34430a8e0729f2b5b095 11360
gscan2pdf_2.8.2-1.debian.tar.xz
901317070432bcb98def7fbe6e070935cad6d4078fc72404d0ca6b3180b2a146 5407
gscan2pdf_2.8.2-1_source.buildinfo
Files:
746ae34315ba242da94a51875a24d56a 2798 utils optional gscan2pdf_2.8.2-1.dsc
81746db39fbd18df24d658bcfd2fae98 477968 utils optional
gscan2pdf_2.8.2.orig.tar.xz
83248d875bfce5215d3b6f4797bd5150 833 utils optional
gscan2pdf_2.8.2.orig.tar.xz.asc
1025ddcf58ca45199d5b99a33dfec6b7 11360 utils optional
gscan2pdf_2.8.2-1.debian.tar.xz
379a36f333d616a5da4d4651e935f760 5407 utils optional
gscan2pdf_2.8.2-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEERjKT5K4zhxhG8wInsyHyAxEPyvMFAl8dS34ACgkQsyHyAxEP
yvNumg/+OLe0t7gZzVixVj+oH4v+eTQFLkNWzpyXzMYVtG8GJhw0CZMqtX/yRrbO
wsLu64BIjVY53HgPyd8ieAauEdlnFwJOV+NRswmvJfgybB8A1WhqTvG3MKTC9dAH
D0uVF1tBJUPo1B3fNBTuehz2d19/tB2FXVZvVPrQc7v9ULefkHvUVAcUFRdwE1nc
tSzWHvux7Df5cy9QTvvuF0xkOLM4OZGREuDDGUtO2zARGH01ggC46VgRklQYKJii
NDBZWi5EXcouKs+1xOPyItq5h60EXRXHUioRJTlBwhxpjRI95MOXeXVVTZTGs6fc
m2BmQE8J2NyhcQjIXbBB2l9tVwvhoxYdH79WDC9h41aP8AAnGHjfqZW4/Dd2S6yZ
yHAjatNJBxRoJFJwrHRe/9hcw4NtJn8WPuRDMUbuLlqjrdKWb/QwG9HJx2us7IuE
8IPtbb20kT9Duwa3/IZpjCH3QXyTmnl5f/E9z/A9q2vq8vRgP2u5h5jcNudHITE1
qfmYgY1k
Bug#957447: marked as done (libixp: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 10:05:35 + with message-id and subject line Bug#957447: fixed in libixp 0.6~20121202+hg148-3 has caused the Debian Bug report #957447, regarding libixp: 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.) -- 957447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libixp Version: 0.6~20121202+hg148-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/libixp_0.6~20121202+hg148-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 [...] /bin/sh ../../util/compile "x86_64-linux-gnu-gcc" "-I. -I../../include -I/usr/include -I/usr/include -D_XOPEN_SOURCE=600 -c -Wall -W -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wtrigraphs '-DVERSION=\"0.5\"' '-DCOPYRIGHT=\"©2010 Kris Maglione\"' -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wtrigraphs -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wt rigraphs '-DVERSION=\"0.5\"' '-DCOPYRIGHT=\"©2010 Kris Maglione\"' $(pkg-config --cflags 2>/dev/null) -fPIC" map.o_pic map.c CC lib/libixp/map.o_pic /bin/sh ../../util/compile "x86_64-linux-gnu-gcc" "-I. -I../../include -I/usr/include -I/usr/include -D_XOPEN_SOURCE=600 -c -Wall -W -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wtrigraphs '-DVERSION=\"0.5\"' '-DCOPYRIGHT=\"©2010 Kris Maglione\"' -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wtrigraphs -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wt rigraphs '-DVERSION=\"0.5\"' '-DCOPYRIGHT=\"©2010 Kris Maglione\"' $(pkg-config --cflags 2>/dev/null) -fPIC" message.o_pic message.c CC lib/libixp/message.o_pic /bin/sh ../../util/compile "x86_64-linux-gnu-gcc" "-I. -I../../include -I/usr/include -I/usr/include -D_XOPEN_SOURCE=600 -c -Wall -W -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -pedantic -pipe -fno-strict-aliasing -Wall -Wimplicit -Wmissing-prototypes -Wno-comment -Wno-missing-braces -Wno-parentheses -Wno-sign-compare -Wno-switch -Wpointer-arith -Wreturn-type -Wstrict-prototypes -Wtrigraphs '-DVERSION=\"0.5\"' '-DCOPYRIGHT=\"©2010 Kris Maglione\"' -std=c99 -pedantic -pipe -f
Bug#966300: guile oom test fails on ppc64el
Package: src:guile-3.0
Version: 3.0.4-1
Severity: serious
Tags: sid bullseye
The guile testssuite fails one test on ppc64el:
[...]
wrote
`/<>/cache/guile/ccache/3.0-LE-8-4.3/<>/test-suite/standalone/test-stack-overflow.go'
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
PASS: test-stack-overflow
wrote
`/<>/cache/guile/ccache/3.0-LE-8-4.3/<>/test-suite/standalone/test-out-of-memory.go'
GC Warning: Failed to expand heap by 134348800 bytes
GC Warning: Failed to expand heap by 134217728 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
GC Warning: Failed to expand heap by 1000144896 bytes
GC Warning: Failed to expand heap by 113824 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
mmap(PROT_NONE) failed
/bin/bash: line 5: 28413 Aborted top_srcdir="../.." srcdir="."
builddir="." CHARSETALIASDIR="/<>/lib" GUILE_AUTO_COMPILE=0
"../../meta/build-env" ${dir}$tst
FAIL: test-out-of-memory
==
1 of 39 tests failed
Please report to bug-gu...@gnu.org
==
make[6]: *** [Makefile:2653: check-TESTS] Error 1
https://buildd.debian.org/status/fetch.php?pkg=guile-3.0&arch=ppc64el&ver=3.0.4-1%2Bb1&stamp=1595491909&raw=0
Apparently this is known, and already reported by Debian for 2.2:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+29464
but no update since 2017.
For some reason the test succeeds on the Ubuntu buildds.
Bug#966301: guile oom test fails on ppc64el
Package: src:guile-2.2
Version: 2.2.7+1-5.1
Severity: serious
Tags: sid bullseye
The guile testssuite fails one test on ppc64el:
[...]
wrote
`/<>/cache/guile/ccache/2.2-LE-8-3.A/<>/test-suite/standalone/test-stack-overflow.go'
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
PASS: test-stack-overflow
wrote
`/<>/cache/guile/ccache/2.2-LE-8-3.A/<>/test-suite/standalone/test-out-of-memory.go'
GC Warning: Failed to expand heap by 134348800 bytes
GC Warning: Failed to expand heap by 134217728 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
GC Warning: Failed to expand heap by 1000144896 bytes
GC Warning: Failed to expand heap by 113824 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
mmap(PROT_NONE) failed
/bin/bash: line 5: 24840 Aborted top_srcdir="../.." srcdir="."
builddir="." CHARSETALIASDIR="/<>/lib" GUILE_AUTO_COMPILE=0
"../../meta/build-env" ${dir}$tst
FAIL: test-out-of-memory
==
1 of 39 tests failed
Please report to bug-gu...@gnu.org
https://buildd.debian.org/status/fetch.php?pkg=guile-2.2&arch=ppc64el&ver=2.2.7%2B1-5.1&stamp=1595497537&raw=0
Apparently this is known, and already reported by Debian:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+29464
but no update since 2017.
For some reason the test succeeds on the Ubuntu buildds.
Bug#966182: marked as done (virtualbox FTBFS on amd64 with gsoap 2.8.104)
Your message dated Sun, 26 Jul 2020 08:46:09 + with message-id and subject line Bug#966182: fixed in virtualbox 6.1.12-dfsg-7 has caused the Debian Bug report #966182, regarding virtualbox FTBFS on amd64 with gsoap 2.8.104 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virtualbox Version: 6.1.12-dfsg-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=virtualbox&arch=amd64&ver=6.1.12-dfsg-6%2Bb1&stamp=1595581404&raw=0 ... /<>/src/VBox/Main/webservice/vboxweb.cpp: In function ‘void doQueuesLoop()’: /<>/src/VBox/Main/webservice/vboxweb.cpp:947: error: expression cannot be used as a function 947 | if (soap_socket_errno(soap.master) == SOAP_EINTR) | kmk: *** [/usr/share/kBuild/footer-pass2-compiling-targets.kmk:277: /<>/out/obj/vboxwebsrv/vboxweb.o] Error 1 --- End Message --- --- Begin Message --- Source: virtualbox Source-Version: 6.1.12-dfsg-7 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of virtualbox, 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. Gianfranco Costamagna (supplier of updated virtualbox 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, 26 Jul 2020 09:34:56 +0200 Source: virtualbox Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11 virtualbox-guest-utils Architecture: source Version: 6.1.12-dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Virtualbox Team Changed-By: Gianfranco Costamagna Description: virtualbox - x86 virtualization solution - base binaries virtualbox-dkms - x86 virtualization solution - kernel module sources for dkms virtualbox-guest-dkms - x86 virtualization solution - guest addition module source for dk virtualbox-guest-source - x86 virtualization solution - guest addition module source virtualbox-guest-utils - x86 virtualization solution - non-X11 guest utilities virtualbox-guest-x11 - x86 virtualization solution - X11 guest utilities virtualbox-qt - x86 virtualization solution - Qt based user interface virtualbox-source - x86 virtualization solution - kernel module source Closes: 966182 Changes: virtualbox (6.1.12-dfsg-7) unstable; urgency=medium . * Fix build with new gsoap (Closes: #966182) Checksums-Sha1: 8c3d4965d12c55fa3ffb5e75ad71bd3ec83ad3fb 3625 virtualbox_6.1.12-dfsg-7.dsc 10dc930c118cb75471b4a1687e252b9112e64921 99320 virtualbox_6.1.12-dfsg-7.debian.tar.xz 918a0f4b7e874bda9671615ca24fc3f9ab87ec41 26687 virtualbox_6.1.12-dfsg-7_source.buildinfo Checksums-Sha256: b2d21f93bb819563a751129cdf2b3f1ccd43cbe585a181192c0186ee2a30f3f2 3625 virtualbox_6.1.12-dfsg-7.dsc f7a72fa4956efea6f05d1bb820eb793d7aa243229bc9c82482101a0c7fe119dc 99320 virtualbox_6.1.12-dfsg-7.debian.tar.xz bd7dc2b498f447a662484bad43514e57c5a5691d2e20c3c41eab5f8a49b0c31c 26687 virtualbox_6.1.12-dfsg-7_source.buildinfo Files: d9e7e9750ffc9a56ecf5d7adac3f2d98 3625 contrib/misc optional virtualbox_6.1.12-dfsg-7.dsc 46fe81c15a330d7f03647a757a048b5b 99320 contrib/misc optional virtualbox_6.1.12-dfsg-7.debian.tar.xz b3b0814dd81a84bf163f6d941ab1dcf0 26687 contrib/misc optional virtualbox_6.1.12-dfsg-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl8dMr4ACgkQ808JdE6f XdndCw/+J16tOXAFAqQgur6EJwdRdoOrLd0CXV/lwkT2gF+aGWuAjYMY8CA8Sq0u VUtabVqJdUQdpFzFf1Vgl3L+bjgyjAu5GEKID9nlxYxo0jDiB75jcfdF1J2H00cU 0sVUaVu74BkPxeLPydb2u2ti7+7NYXSWE23A0ssmHWqeTNN1OFgYFTLRsQ9aD/h1 Wje2tvmZOb8oi7q3sTLuOjG51Vjhz1F8yZnptXFdBbfz1UJhB3+fHWPRIqYspifT CJYlSx0diWd4GWyhQKeXOaEDwaWB04r7tmrlQCM/5lZVVsOnn3iUYBa0FMmfUOie S2Vp7tG/BnWpoZ424/XThHk8QAOOz591TTqmIacaPg+vV71Fly6u05xU+z36xeHT j6u4Krl7QuXgohSXlQRIt6rUXUpQzHvlCEzXjrAbETi1dIpfd+8g8TWfMvSk9oMi +aX4OjhPqpuPhciuqJywx/ayQZM1x1y7ksRNaYYOB9IuJBdWrBh4iT3aaJTbm0LN r2J+HThX9bAgXuagKUqylDA1ECoxh8fgnpsa09zR/bKWkEhNpmc
Bug#957608: nfs-utils: ftbfs with GCC-10
Hi,
On Sun, Jul 26, 2020 at 12:20:17AM +0200, Reiner Herrmann wrote:
> Control: tags -1 + fixed-upstream
>
> Hi,
>
> this has been fixed upstream in version 2.4.3.
> This is the relevant commit:
>
> http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1eafe05616b4660fb15d106e06f0b3e18983708c
For upstream yes, but as we have a quite older version we need to fix
this slightly differently. There is as well one conf_path change
affected.
Finally for bullseye we need/should catch-up with upstream, and there
is current ongoing work for that.
Regards,
Salvatore
>From 5db7c4829c294da6c6f366f93dbbf560bcc8c040 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso
Date: Sat, 25 Jul 2020 21:24:35 +0200
Subject: [PATCH] Allow compilation to succeed with -fno-common
Closes: #957608
---
debian/changelog | 6 ++
...mpilation-to-succeed-with-fno-common.patch | 77 +++
debian/patches/series | 1 +
3 files changed, 84 insertions(+)
create mode 100644 debian/patches/Allow-compilation-to-succeed-with-fno-common.patch
diff --git a/debian/changelog b/debian/changelog
index f2d4d427a81d..4b4c2e6618b6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+nfs-utils (1:1.3.4-4) UNRELEASED; urgency=medium
+
+ * Allow compilation to succeed with -fno-common (Closes: #957608)
+
+ -- Salvatore Bonaccorso Sat, 25 Jul 2020 21:31:52 +0200
+
nfs-utils (1:1.3.4-3) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff --git a/debian/patches/Allow-compilation-to-succeed-with-fno-common.patch b/debian/patches/Allow-compilation-to-succeed-with-fno-common.patch
new file mode 100644
index ..2d5880758d38
--- /dev/null
+++ b/debian/patches/Allow-compilation-to-succeed-with-fno-common.patch
@@ -0,0 +1,77 @@
+From: NeilBrown
+Date: Fri, 7 Feb 2020 11:05:03 -0500
+Subject: Allow compilation to succeed with -fno-common
+Origin: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=1eafe05616b4660fb15d106e06f0b3e18983708c
+Bug-Debian: https://bugs.debian.org/957608
+
+When compiled with -fno-common, global variables that are declared
+multple times cause an error. With -fcommon (the default), they are
+merged.
+
+Declaring such variable multiple times is probably not a good idea, and
+is definitely not necessary.
+
+This patch changes all the global variables defined in include files to
+be explicitly "extern", and where necessary, adds the variable
+declaration to a suitable .c file.
+
+To test, run
+ CFLAGS=-fno-common ./configure
+ make
+
+Signed-off-by: NeilBrown
+Signed-off-by: Steve Dickson
+[Salvatore Bonaccorso: Backport to 1.3.4:
+ - Drop changes in utils/nfsdcld/
+ - support/nfs/conffile.c: Drop definition of conf_path
+]
+---
+ utils/mountd/v4root.c| 2 --
+ utils/nfsdcld/cld-internal.h | 10 +-
+ utils/nfsdcld/nfsdcld.c | 6 ++
+ utils/statd/statd.c | 1 +
+ utils/statd/statd.h | 2 +-
+ 5 files changed, 13 insertions(+), 8 deletions(-)
+
+--- a/utils/mountd/v4root.c
b/utils/mountd/v4root.c
+@@ -28,8 +28,6 @@
+ #include "v4root.h"
+ #include "pseudoflavors.h"
+
+-int v4root_needed;
+-
+ static nfs_export pseudo_root = {
+ .m_next = NULL,
+ .m_client = NULL,
+--- a/utils/statd/statd.c
b/utils/statd/statd.c
+@@ -66,6 +66,7 @@ static struct option longopts[] =
+ };
+
+ extern void sm_prog_1 (struct svc_req *, register SVCXPRT *);
++stat_chge SM_stat_chge;
+
+ #ifdef SIMULATIONS
+ extern void simulator (int, char **);
+--- a/utils/statd/statd.h
b/utils/statd/statd.h
+@@ -41,7 +41,7 @@ extern void load_state(void);
+ /*
+ * Host status structure and macros.
+ */
+-stat_chge SM_stat_chge;
++extern stat_chge SM_stat_chge;
+ #define MY_NAME SM_stat_chge.mon_name
+ #define MY_STATE SM_stat_chge.state
+
+--- a/support/nfs/conffile.c
b/support/nfs/conffile.c
+@@ -104,7 +104,6 @@ struct conf_binding {
+ int is_default;
+ };
+
+-char *conf_path;
+ LIST_HEAD (conf_bindings, conf_binding) conf_bindings[256];
+
+ static char *conf_addr;
diff --git a/debian/patches/series b/debian/patches/series
index 5cb2def49d02..b3c7ef297712 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -17,3 +17,4 @@ fix-glibc2.28-ftbfs.patch
0011-gssd-Duplicate-the-upcall-string-for-error-messages.patch
nfsiostat-replace-list-reserved-word.patch
statd-take-user-id-from-var-lib-nfs-sm.patch
+Allow-compilation-to-succeed-with-fno-common.patch
--
2.28.0.rc1
Bug#957491: marked as done (linux: ftbfs with GCC-10)
Your message dated Sun, 26 Jul 2020 08:10:13 + with message-id and subject line Bug#957491: fixed in linux 5.7.10-1 has caused the Debian Bug report #957491, regarding linux: 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.) -- 957491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.4.19-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/linux_5.4.19-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 -Wp,-MD,/<>/debian/build/build-tools/tools/perf/util/.probe-finder.o.d -Wp,-MT,/<>/debian/build/build-tools/tools/perf/util/probe-finder.o -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/tools/perf -I/<>/debian/build/build-tools/tools/perf -isystem /<>/debian/build/build-tools/include -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security -Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings -Wformat -Wstrict-aliasing=3 -Wshadow -DHAVE_ARCH_X86_64_SUPPORT -I/<>/debian/build/build-tools/tools/perf/arch/x86/include/generated -DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT -DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -O6 -fno-omit-frame-pointer -ggdb3 -funwi nd-tables -Wall -Wextra -std=gnu99 -fstack-protector-all -D_FORTIFY_SOURCE=2 -I/<>/tools/perf/lib/include -I/<>/tools/perf/util/include -I/<>/tools/perf/arch/x86/include -I/<>/tools/include/ -I/<>/tools/arch/x86/include/uapi -I/<>/tools/include/uapi -I/<>/tools/arch/x86/include/ -I/<>/tools/arch/x86/ -I/<>/debian/build/build-tools/tools/perf//util -I/<>/debian/build/build-tools/tools/perf/ -I/<>/tools/perf/util -I/<>/tools/perf -I/<>/tools/lib/ -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP -DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD -DHAVE_GET_CURRENT_DIR_NAME -DHAVE_DWARF_GETLOCATIONS_SUPPORT -DHAVE_GLIBC_SUPPORT -DHAVE_AIO_SUPPORT -DHAVE_SCHED_GETCPU_SUPPORT -DHAVE_SETNS_SUPPORT -DHAVE_CSTRACE_SUPPORT -DHAVE_LIBELF_SUPPORT -DHAVE_LIBELF_ MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_GELF_GETNOTE_SUPPORT -DHAVE_ELF_GETSHDRSTRNDX_SUPPORT -DHAVE_DWARF_SUPPORT -DHAVE_LIBBPF_SUPPORT -DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP -DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT -DHAVE_SLANG_SUPPORT -DHAVE_LIBPERL_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_LIBPYTHON_SUPPORT -DHAVE_CPLUS_DEMANGLE_SUPPORT -DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT -DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT -DHAVE_KVM_STAT_SUPPORT -DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 -DHAVE_LIBBABELTRACE_SUPPORT -DHAVE_AUXTRACE_SUPPORT -I/<>/debian/build/build-tools/tools/perf/ -D"BUILD_STR(s)=#s" -c -o /<>/debian/build/build-tools/tools/perf/util/probe-finder.o util/probe-finder.c gcc -Wp,-MD,/<>/debian/build/build-tools/tools/perf/util/.dwarf-aux.o.d -Wp,-MT,/<>/debian/build/build-tools/tools/perf/util/dwarf-aux.o -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/tools/perf -I/<>/debian/build/build-tools/tools/perf -isystem /<>/debian/build/build-tools/include -Wbad-function-cast -Wdeclaratio
Bug#966296: purple-xmpp-http-upload FTBFS with gcc 10
Source: purple-xmpp-http-upload Version: 0.2.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/purple-xmpp-http-upload.html ... /usr/bin/ld: /tmp/ccFPaJNw.o:/build/1st/purple-xmpp-http-upload-0.2.1/src/jabber_http_file_upload.h:19: multiple definition of `HFUJabberStreamDataTable'; /tmp/ccDLUofx.o:/build/1st/purple-xmpp-http-upload-0.2.1/src/jabber_http_file_upload.h:19: first defined here collect2: error: ld returned 1 exit status make[1]: *** [makefile:34: jabber_http_file_upload.so] Error 1
Processed: Re: virtualbox FTBFS on amd64 with gsoap 2.8.104
Processing control commands: > forwarded -1 https://www.virtualbox.org/ticket/19634 Bug #966182 [src:virtualbox] virtualbox FTBFS on amd64 with gsoap 2.8.104 Set Bug forwarded-to-address to 'https://www.virtualbox.org/ticket/19634'. -- 966182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966182: virtualbox FTBFS on amd64 with gsoap 2.8.104
control: forwarded -1 https://www.virtualbox.org/ticket/19634 On Fri, 24 Jul 2020 14:30:28 +0300 Adrian Bunk wrote: > Source: virtualbox > Version: 6.1.12-dfsg-6 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=virtualbox&arch=amd64&ver=6.1.12-dfsg-6%2Bb1&stamp=1595581404&raw=0 > > ... > /<>/src/VBox/Main/webservice/vboxweb.cpp: In function ???void > doQueuesLoop()???: > /<>/src/VBox/Main/webservice/vboxweb.cpp:947: error: expression > cannot be used as a function > 947 | if (soap_socket_errno(soap.master) == SOAP_EINTR) > | > kmk: *** [/usr/share/kBuild/footer-pass2-compiling-targets.kmk:277: > /<>/out/obj/vboxwebsrv/vboxweb.o] Error 1 will fix thanks
Processed: Re: Bug#966171: ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common
Processing commands for cont...@bugs.debian.org: > Forwarded 966171 https://github.com/wojtekka/ydpdict/issues/3 Bug #966171 [src:ydpdict] ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common Set Bug forwarded-to-address to 'https://github.com/wojtekka/ydpdict/issues/3'. > Thanks Stopping processing here. Please contact me if you need assistance. -- 966171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
