Processed: closing 968076
Processing commands for cont...@bugs.debian.org: > close 968076 11.4-1 Bug #968076 [src:bind-dyndb-ldap] bind-dyndb-ldap FTBFS on 32bit: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’ Marked as fixed in versions bind-dyndb-ldap/11.4-1. Bug #968076 [src:bind-dyndb-ldap] bind-dyndb-ldap FTBFS on 32bit: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’ Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 968076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968076: closing 968076
close 968076 11.4-1 thanks
Bug#970570: llvm-toolchain-11: autopkgtest failure: Should find 3 warnings
Source: llvm-toolchain-11 Version: 1:11.0.0~+rc2-5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added a new package with an autopkgtest, great. However, the autopkgest fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=llvm-toolchain-11 https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-11/6878994/log.gz clang-$VERSION -cc1 -analyze -analyzer-constraints=range -analyzer-checker=core,debug.ExprInspection foo.c &> foo.log if ! grep -q "3 warnings generated." foo.log; then echo "Should find 3 warnings" exit 1 fi Should find 3 warnings signature.asc Description: OpenPGP digital signature
Processed: tagging 957265
Processing commands for cont...@bugs.debian.org: > # Haven't actually uploaded the NMU yet > tags 957265 - pending Bug #957265 [src:geekcode] geekcode: ftbfs with GCC-10 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 957265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Processing control commands: > reassign -1 cowdancer 0.88 Bug #970555 [src:ncurses] ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) Bug reassigned from package 'src:ncurses' to 'cowdancer'. No longer marked as found in versions ncurses/6.2+20200912-1. Ignoring request to alter fixed versions of bug #970555 to the same values previously set Bug #970555 [cowdancer] ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) Marked as found in versions cowdancer/0.88. > retitle -1 cowdancer: needlessly links with ncurses Bug #970555 [cowdancer] ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) Changed Bug title to 'cowdancer: needlessly links with ncurses' from 'ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)'. > severity -1 important Bug #970555 [cowdancer] cowdancer: needlessly links with ncurses Severity set to 'important' from 'serious' -- 970555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Control: reassign -1 cowdancer 0.88 Control: retitle -1 cowdancer: needlessly links with ncurses Control: severity -1 important On 2020-09-18 18:22 +0200, Sebastiaan Couwenberg wrote: > Control: tags -1 - moreinfo > > On 9/18/20 6:13 PM, Sven Joachim wrote: >> On 2020-09-18 16:55 +0200, Bas Couwenberg wrote: >>> Upgrading sid & experimental pbuilder chroots fails due to the new ncurses: >>> >>> Preparing to unpack .../libncursesw6_6.2+20200912-1_amd64.deb ... >>> Unpacking libncursesw6:amd64 (6.2+20200912-1) over (6.2-1) ... >>> Preparing to unpack .../libncurses6_6.2+20200912-1_amd64.deb ... >>> Unpacking libncurses6:amd64 (6.2+20200912-1) over (6.2-1) ... >>> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version >>> `NCURSES6_TINFO_6.2.current' not found (required by >>> /lib/x86_64-linux-gnu/libncurses.so.6) >>> dpkg: error while cleaning up: >>> rm command for cleanup subprocess returned error exit status 1 >>> dpkg-split: /lib/x86_64-linux-gnu/libtinfo.so.6: version >>> `NCURSES6_TINFO_6.2.current' not found (required by >>> /lib/x86_64-linux-gnu/libncurses.so.6) >>> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version >>> `NCURSES6_TINFO_6.2.current' not found (required by >>> /lib/x86_64-linux-gnu/libncurses.so.6) >>> dpkg: error processing archive >>> /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb (--unpack): >>> rm command for cleanup subprocess returned error exit status 1 >>> Errors were encountered while processing: >>> /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb >>> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> I cannot reproduce this, but my pbuilder chroots do not have libncurses6 >> installed at all. > > What about cowbuilder chroots? Thanks for the hint, I do not use cowbuilder but had a look at the manpage where I found this option: , | --no-cowdancer-update | Do not use cowdancer on cowbuilder update. Please use this | option when cowdancer is interfering with upgrade process, | or cowdancer itself is being upgraded within chroot. ` Apparently this is what you need to use, for cowdancer seems to bring libncurses.so.6 into the address space of every binary on the system, which is "interfering with upgrade process". >> What is this rm binary in your chroot, apparently it >> is linked to libncurses.so.6? > > # which rm > /bin/rm > # dpkg -S /bin/rm > coreutils: /bin/rm > # ldd /bin/rm > linux-vdso.so.1 (0x7ffea75fb000) > /usr/lib/cowdancer/libcowdancer.so (0x7f2e6a6db000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f2e6a512000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f2e6a50c000) > libncurses.so.6 => /lib/x86_64-linux-gnu/libncurses.so.6 > (0x7f2e6a4e3000) > libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 > (0x7f2e6a4b4000) > /lib64/ld-linux-x86-64.so.2 (0x7f2e6a6f9000) > # aptitude why libncurses6 > i cowdancer Depends libncurses6 (>= 6) It seems that cowdancer should not link with ncurses in the first place, as it only uses the tinfo library. In fact, rebuilding cowbuilder with a current toolchain that defaults to the "--as-needed" linker flag causes cowbuilder and cowdancer to depend on libtinfo6 only. Cheers, Sven
Bug#957265: [PATCH] Re: Bug#957265: geekcode: ftbfs with GCC-10
Control: tag -1 + pending patch Hi Eric, Matthias Klose wrote: > 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. I've submitted a merge request for this bug report at https://salsa.debian.org/eric/geekcode/-/merge_requests/2/diffs based on the current state of your git repository (and not the current state of the package in Debian Unstable). I'm also thinking about NMU'ing this issue given how long this has been open. But since you merged another MR about two months ago or so, I assume and hope that providing a bite-sized patch will speed up things. :-) Didn't fix more lintian issues. though, as this MR is intended to work as NMU, too. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: [PATCH] Re: Bug#957265: geekcode: ftbfs with GCC-10
Processing control commands: > tag -1 + pending patch Bug #957265 [src:geekcode] geekcode: ftbfs with GCC-10 Added tag(s) pending and patch. -- 957265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 970567
Processing commands for cont...@bugs.debian.org: > tags 970567 + buster Bug #970567 [src:pyzmq] pyzmq: TestAsyncioAuthentication::test_blacklist hanging after CVE-2020-15166 bugfix for zeromq3 Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 970567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pyzmq: TestAsyncioAuthentication::test_blacklist hanging after CVE-2020-15166 bugfix for zeromq3
Processing control commands: > fixed -1 19.0.2-2 Bug #970567 [src:pyzmq] pyzmq: TestAsyncioAuthentication::test_blacklist hanging after CVE-2020-15166 bugfix for zeromq3 Marked as fixed in versions pyzmq/19.0.2-2. > affects -1 + release.debian.org,security.debian.org Bug #970567 [src:pyzmq] pyzmq: TestAsyncioAuthentication::test_blacklist hanging after CVE-2020-15166 bugfix for zeromq3 Added indication that 970567 affects release.debian.org and security.debian.org -- 970567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970567: pyzmq: TestAsyncioAuthentication::test_blacklist hanging after CVE-2020-15166 bugfix for zeromq3
Source: pyzmq Version: 17.1.2-2 Severity: serious Tags: upstream,patch,fixed-upstream Justification: FTBFS Forwarded: https://github.com/zeromq/pyzmq/issues/1418 X-Debbugs-Cc: car...@debian.org,t...@security.debian.org,bl...@debian.org,g...@debian.org Control: fixed -1 19.0.2-2 Control: affects -1 + release.debian.org,security.debian.org Hi After the CVE-2020-15166 fix in zeromq3 the upstream test TestAsyncioAuthentication::test_blacklist will hang, cf [1]. This was already fixed in unstable. For stable this would cause an issue when pyzmq would need to be rebuild. It though does not warrant a regression update via security because. The test was actually relying on the broken behaviour afaiu. [1] https://github.com/zeromq/pyzmq/issues/1418 [2] https://github.com/zeromq/pyzmq/commit/afd72820946f544790c6f70d90ba50eb29f1c6e1 Regards, Salvatore
Processed: tagging 957265, tagging 957686, tagging 957100
Processing commands for cont...@bugs.debian.org: > tags 957265 + ftbfs Bug #957265 [src:geekcode] geekcode: ftbfs with GCC-10 Added tag(s) ftbfs. > tags 957686 + ftbfs Bug #957686 [src:pinfo] pinfo: ftbfs with GCC-10 Added tag(s) ftbfs. > tags 957100 + ftbfs Bug #957100 [src:cool-retro-term] cool-retro-term: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957100 957265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957265 957686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970565: python-duckpy: autopkgtest failure: No module named 'bs4'
Source: python-duckpy Version: 2.1.1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package python-duckpy, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? Paul [1] https://qa.debian.org/excuses.php?package=python-duckpy https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-duckpy/6300451/log.gz signature.asc Description: OpenPGP digital signature
Bug#969837: marked as done (lebiniou: autopkgtest should be marked superficial)
Your message dated Fri, 18 Sep 2020 18:49:30 + with message-id and subject line Bug#969837: fixed in lebiniou 3.43.1-2 has caused the Debian Bug report #969837, regarding lebiniou: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lebiniou Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'lebiniou' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'lebiniou'. -- Sudip --- End Message --- --- Begin Message --- Source: lebiniou Source-Version: 3.43.1-2 Done: Olivier Girondel We believe that the bug you reported is fixed in the latest version of lebiniou, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Girondel (supplier of updated lebiniou package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 18 Sep 2020 14:25:49 +0200 Source: lebiniou Architecture: source Version: 3.43.1-2 Distribution: unstable Urgency: low Maintainer: Olivier Girondel Changed-By: Olivier Girondel Closes: 969837 Changes: lebiniou (3.43.1-2) unstable; urgency=low . * debian/tests/control: Add Restrictions: superficial (Closes: #969837). Checksums-Sha1: 93fa66a535313cc1f454bbb6052a4f1241d89044 2078 lebiniou_3.43.1-2.dsc 86d44ed90120a69114a86657a107c64e205cf3a7 4184 lebiniou_3.43.1-2.debian.tar.xz 960c2b464ae0e322c36da1066ea3ccf97b6cf451 13835 lebiniou_3.43.1-2_source.buildinfo Checksums-Sha256: cda67e608edeef81c612081e727f4c07582e96acd782cda0d08ed56ed1be0f87 2078 lebiniou_3.43.1-2.dsc 1b0bb354781ae4dd68f15dc639ef7731c4b3e3b268e5792f6549decd317600af 4184 lebiniou_3.43.1-2.debian.tar.xz 591867d9769ecfe506cb63b28c7eec0896072b410e46dd91fd54ab4c01c18fb2 13835 lebiniou_3.43.1-2_source.buildinfo Files: b337cde570f0d1eb8599c23c56e54452 2078 graphics optional lebiniou_3.43.1-2.dsc 40f7aa400125c2f18d0380275922a01b 4184 graphics optional lebiniou_3.43.1-2.debian.tar.xz b58274b5290ebfc1c0205c835aa97537 13835 graphics optional lebiniou_3.43.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9k+ZUACgkQweDZLphv fH7CuxAAuaPCBkCYL6Dg7VzbhkpMzqsPIEZ4ljmNh7FEk/0U6mHpi1sTUKtEqwAB Tz8FIxIvwZBOhvzUUyytczhzioTl/Sd2JYsh1OjUIiCGGmCcNGs9p+h3z8N+KCgj hnnVNYsmV1fD1bO3fxl9pttWRmDNNC04ZTVopIvXnN5CE++oTpNspJDoeGABDeRM L5xbgRy1zwv2pN+kbaKC1FmfVfR4MTGmWsb0nvGD0XiI5nMNFtaVhlFACixMC3uu oIoTQ3JKwJjfF3ZsCONQeQRv5qKrHvcQRnozfQmxKMCWyctIpikhGYByXOBO+1Ag eTtuC5c1ohHXEMQ4DF0e7GAEGTSnrqPzgA9ZQRQ+JcoqBfvSpXUcDjyMyvwx3Jyp NgNIIUymbRz148wgR9EcyCzfn7TAYzwGWBUnnlBVPltvLjEBqY+QITlc/J50oEU0 rb/2UyuF5Y/KBtZIMnBwXh8n6aNqDgjwlp6kNTl+UGdm2pvuPDNbwm0lMv8vE1gW +KKkaS7EMWaZRSA74MH2TaY2A34CMs30rFTME7yVyf/0xvYpH7hI/mxVo0B3pYrD dsX4f70ok0Zz+rR/5VPISwh4GbbEzMCHRLA/d7fKAs1mEsb2boMCihpvmaYqP/FH cMs1Xu65iELUSqhiyT3kM9v0QLbaYoYt+FZVfg0J84px9/bRlAw= =14/N -END PGP SIGNATURE End Message ---
Processed: Add affects diaspora
Processing commands for cont...@bugs.debian.org: > affects 970550 diaspora Bug #970550 [ruby-autoprefixer-rails] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Added indication that 970550 affects diaspora > -- Stopping processing here. Please contact me if you need assistance. -- 970550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958584: marked as done (carbon-c-relay: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Fri, 18 Sep 2020 18:04:39 +
with message-id
and subject line Bug#958584: fixed in carbon-c-relay 3.7-1
has caused the Debian Bug report #958584,
regarding carbon-c-relay: Build-Depends on deprecated dh-systemd which is going
away
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
958584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: carbon-c-relay
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package carbon-c-relay declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.
For bullseye we intend to drop this empty transitional package.
Once we drop dh-systemd, this bug report will become RC.
Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).
Regards,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: carbon-c-relay
Source-Version: 3.7-1
Done: Bernd Zeimetz
We believe that the bug you reported is fixed in the latest version of
carbon-c-relay, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernd Zeimetz (supplier of updated carbon-c-relay package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 Sep 2020 19:18:41 +0200
Source: carbon-c-relay
Architecture: source
Version: 3.7-1
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz
Changed-By: Bernd Zeimetz
Closes: 857518 913021 958584
Changes:
carbon-c-relay (3.7-1) unstable; urgency=medium
.
[ Bernd Zeimetz ]
* [e63edac] Updating debian/.gitlab-ci.yml
.
[ Debian Janitor ]
* [11bd265] Use secure copyright file specification URI.
Fixes: lintian: insecure-copyright-format-uri
See-also:
https://lintian.debian.org/tags/insecure-copyright-format-uri.html
* [7640b46] Remove unnecessary X-Python{,3}-Version field in debian/control.
Fixes: lintian: ancient-python-version-field
See-also: https://lintian.debian.org/tags/ancient-python-version-field.html
* [a6a83b6] Depend on newer debhelper (>= 9.20160709) rather than dh-systemd.
Fixes: lintian: build-depends-on-obsolete-package
See-also:
https://lintian.debian.org/tags/build-depends-on-obsolete-package.html
Closes: #958584
* [c423094] Set upstream metadata fields: Bug-Database, Bug-Submit,
Repository, Repository-Browse.
Fixes: lintian: upstream-metadata-file-is-missing
See-also:
https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html
Fixes: lintian: upstream-metadata-missing-bug-tracking
See-also:
https://lintian.debian.org/tags/upstream-metadata-missing-bug-tracking.html
Fixes: lintian: upstream-metadata-missing-repository
See-also:
https://lintian.debian.org/tags/upstream-metadata-missing-repository.html
* [0393352] Drop unnecessary dh arguments: --with=systemd.
Fixes: lintian: debian-rules-uses-unnecessary-dh-argument
See-also:
https://lintian.debian.org/tags/debian-rules-uses-unnecessary-dh-argument.html
.
[ Bernd Zeimetz ]
* [ce1294e] New upstream version 3.7
Closes: #913021
* [cdabad7] install carbon-c-relay.md instead of a symlink. (Closes: #857518)
* [c96faf7] Updating changelog
* [482a755] Ship ChangeLog.md
* [0d9b06c] really rename the relay binary to carbon-c-relay.
Don't ship both files.
Also use manpage from upstream.
* [b329190] Updating changelog
* [93befb8] Find next free port in regressiontests
* [d50d7ba] don't test all ports if not needed
Checksums-Sha1:
f2816bb6f3f1611b213215f8a7ac4a0cc183bbdb 1910 carbon-c-relay_3.7-1.dsc
1aac580bd9bb16c453bd1e64469db9c984ee76bb 351792 carbon-c-relay_3.7.orig.tar.xz
b54737542ab330e43eca6bbee7a186fe4f951f5a 6384
carbon-c-relay_3.7-1.debian.tar.xz
Bug#970545: dpkg FTBFS: KEY_EVENT undeclared
On Fri, 2020-09-18 at 18:26:34 +0200, Sven Joachim wrote:
> Am 18.09.2020 um 13:43 schrieb Helmut Grohne:
> > Source: dpkg
> > Version: 1.20.5
> > Severity: serious
> > Tags: ftbfs
> >
> > dpkg FTBFS as of today:
> >
> > | In file included from ../../dselect/curkeys.cc:30:
> > | ./curkeys.h:168:5: error: ‘KEY_EVENT’ was not declared in this scope; did
> > you mean ‘KEY_OPEN’?
> > | 168 | { KEY_EVENT, "Event" },
> > | | ^
> > | | KEY_OPEN
> > I suppose this is connected to a ncurses upload.
> Quoting the ncurses NEWS file:
>
> ,
> | 20200817
> | + prevent KEY_EVENT from appearing in curses.h unless the configure
> | option --enable-wgetch-events is used (report by Werner Fink).
> `
Right, thanks for the confirmation, that's along the lines of what I
had gathered from checking the header. Even though the problem here
is that the macro is there, but just behind a conditional, I suppose
that's still expected?
> See the thread at
> https://lists.gnu.org/archive/html/bug-ncurses/2020-08/threads.html#00017
> for a discussion that motivated this change.
I'll check this later, but no matter what, I think it is still worth
fixing the dpkg build system to handle this kind of case more robustly.
I've prepared the attached patch which seems to work with gcc and clang,
and I'll try to upload either later today or tomorrow.
Thanks,
Guillem
diff --git i/dselect/Makefile.am w/dselect/Makefile.am
index 9206603a2..8195fe414 100644
--- i/dselect/Makefile.am
+++ w/dselect/Makefile.am
@@ -57,18 +57,14 @@ dselect_LDADD = \
EXTRA_DIST = keyoverride mkcurkeys.pl
-CLEANFILES = curkeys.h
+CLEANFILES = curkeys.hpp curkeys.h
curkeys.$(OBJEXT): curkeys.h
-curkeys.h: $(srcdir)/keyoverride $(srcdir)/mkcurkeys.pl
- $(AM_V_GEN) cursesfile=`echo '#include "dselect-curses.h"' | \
- $(CPP) $(CPPFLAGS) -I$(top_builddir) -I $(srcdir) - | \
- grep '[^-]curses\.h' | head -n 1 | \
- sed -e 's/^[^"]*"//; s/".*$$//'`; \
- if [ "$$cursesfile" = "" ]; then \
- echo "can't find curses file"; exit 1; \
- fi; \
- $(PERL) $(srcdir)/mkcurkeys.pl $< $$cursesfile >$@
+curkeys.hpp: dselect-curses.h
+ $(AM_V_GEN) echo '#include "dselect-curses.h"' | \
+ $(CPP) -dD $(CPPFLAGS) -I$(top_builddir) -I $(srcdir) - > $@
+curkeys.h: $(srcdir)/keyoverride $(srcdir)/mkcurkeys.pl curkeys.hpp
+ $(PERL) $(srcdir)/mkcurkeys.pl $< curkeys.hpp >$@
install-data-local:
$(MKDIR_P) $(DESTDIR)$(pkgconfdir)/dselect.cfg.d
Bug#966951: marked as done (libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found)
Your message dated Fri, 18 Sep 2020 16:33:28 + with message-id and subject line Bug#966951: fixed in libpeas 1.28.0-2 has caused the Debian Bug report #966951, regarding libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpeas Version: 1.26.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > HOME=/<> xvfb-run -a dh_auto_test > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test > [0/1] Running all tests. > [1;31m1/8 test-engine FAIL 0.02s (killed by signal 6 > SIGABRT)[0m > [1;31m2/8 test-extension-c FAIL 0.01s (killed by signal 6 > SIGABRT)[0m > [1;31m3/8 test-extension-setFAIL 0.01s (killed by signal 6 > SIGABRT)[0m > [1;31m4/8 test-plugin-info FAIL 0.01s (killed by signal 6 > SIGABRT)[0m > [1;31m5/8 test-extension-py FAIL 0.01s (killed by signal 6 > SIGABRT)[0m > 6/8 test-plugin-manager OK 0.17s > 7/8 test-plugin-manager-store OK 0.22s > 8/8 test-plugin-manager-view OK 0.22s > > Ok: 3 > Expected Fail: 0 > Fail: 5 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > > > The output from the failed tests: > > 1/8 test-engine FAIL 0.02s (killed by signal 6 > SIGABRT) > > --- command --- > 17:26:39 NO_AT_BRIDGE='1' GSETTINGS_BACKEND='memory' G_DEBUG='gc-friendly' > MALLOC_CHECK_='2' /<>/obj-x86_64-linux-gnu/tests/libpeas/engine > --- stdout --- > # random seed: R02S24bd2039e5be9936225c32c9afe1adbd > Bail out! ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion > failed (error == NULL): Typelib file for namespace 'Introspection', version > '1.0' not found (g-irepository-error-quark, 0) > --- stderr --- > ** > ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion failed > (error == NULL): Typelib file for namespace 'Introspection', version '1.0' > not found (g-irepository-error-quark, 0) > --- > > 2/8 test-extension-c FAIL 0.01s (killed by signal 6 > SIGABRT) > > --- command --- > 17:26:39 NO_AT_BRIDGE='1' GSETTINGS_BACKEND='memory' G_DEBUG='gc-friendly' > MALLOC_CHECK_='2' > /<>/obj-x86_64-linux-gnu/tests/libpeas/extension-c > --- stdout --- > # random seed: R02S35e63bb219e9bc5c0ba2fb0f4d465e51 > Bail out! ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion > failed (error == NULL): Typelib file for namespace 'Introspection', version > '1.0' not found (g-irepository-error-quark, 0) > --- stderr --- > ** > ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion failed > (error == NULL): Typelib file for namespace 'Introspection', version '1.0' > not found (g-irepository-error-quark, 0) > --- > > 3/8 test-extension-setFAIL 0.01s (killed by signal 6 > SIGABRT) > > --- command --- > 17:26:39 NO_AT_BRIDGE='1' GSETTINGS_BACKEND='memory' G_DEBUG='gc-friendly' > MALLOC_CHECK_='2' > /<>/obj-x86_64-linux-gnu/tests/libpeas/extension-set > --- stdout --- > # random seed: R02S74612be6e60fad0516038e18f9c67589 > Bail out! ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion > failed (error == NULL): Typelib file for namespace 'Introspection', version > '1.0' not found (g-irepository-error-quark, 0) > --- stderr --- > ** > ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion failed > (error == NULL): Typelib file for namespace 'Introspection', version '1.0' > not found (g-irepository-error-quark, 0) > --- > > 4/8 test-plugin-info FAIL 0.01s (killed by signal 6 > SIGABRT) > > --- command --- > 17:26:39 NO_AT_BRIDGE='1' GSETTINGS_BACKEND='memory' G_DEBUG='gc-friendly' > MALLOC_CHECK_='2' > /<>/obj-x86_64-linux-gnu/tests/libpeas/plugin-info > --- stdout --- > # random seed: R02S1c83a50e9dd243feb0c45ac92f39a129 > Bail out! ERROR:../tests/libpeas/testing/testing.c:54:testing_init: assertion > failed (error == NULL): Typelib file for namespace 'Introspection', version > '1.0' not found
Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Control: tags -1 - moreinfo On 9/18/20 6:13 PM, Sven Joachim wrote: > On 2020-09-18 16:55 +0200, Bas Couwenberg wrote: >> Upgrading sid & experimental pbuilder chroots fails due to the new ncurses: >> >> Preparing to unpack .../libncursesw6_6.2+20200912-1_amd64.deb ... >> Unpacking libncursesw6:amd64 (6.2+20200912-1) over (6.2-1) ... >> Preparing to unpack .../libncurses6_6.2+20200912-1_amd64.deb ... >> Unpacking libncurses6:amd64 (6.2+20200912-1) over (6.2-1) ... >> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version >> `NCURSES6_TINFO_6.2.current' not found (required by >> /lib/x86_64-linux-gnu/libncurses.so.6) >> dpkg: error while cleaning up: >> rm command for cleanup subprocess returned error exit status 1 >> dpkg-split: /lib/x86_64-linux-gnu/libtinfo.so.6: version >> `NCURSES6_TINFO_6.2.current' not found (required by >> /lib/x86_64-linux-gnu/libncurses.so.6) >> rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version >> `NCURSES6_TINFO_6.2.current' not found (required by >> /lib/x86_64-linux-gnu/libncurses.so.6) >> dpkg: error processing archive >> /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb (--unpack): >> rm command for cleanup subprocess returned error exit status 1 >> Errors were encountered while processing: >> /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb >> E: Sub-process /usr/bin/dpkg returned an error code (1) > > I cannot reproduce this, but my pbuilder chroots do not have libncurses6 > installed at all. What about cowbuilder chroots? > What is this rm binary in your chroot, apparently it > is linked to libncurses.so.6? # which rm /bin/rm # dpkg -S /bin/rm coreutils: /bin/rm # ldd /bin/rm linux-vdso.so.1 (0x7ffea75fb000) /usr/lib/cowdancer/libcowdancer.so (0x7f2e6a6db000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f2e6a512000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f2e6a50c000) libncurses.so.6 => /lib/x86_64-linux-gnu/libncurses.so.6 (0x7f2e6a4e3000) libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x7f2e6a4b4000) /lib64/ld-linux-x86-64.so.2 (0x7f2e6a6f9000) # aptitude why libncurses6 i cowdancer Depends libncurses6 (>= 6) Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Processing control commands: > tags -1 - moreinfo Bug #970555 [src:ncurses] ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) Removed tag(s) moreinfo. -- 970555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970545: dpkg FTBFS: KEY_EVENT undeclared
Am 18.09.2020 um 13:43 schrieb Helmut Grohne:
> Source: dpkg
> Version: 1.20.5
> Severity: serious
> Tags: ftbfs
>
> dpkg FTBFS as of today:
>
> | g++ -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\"
> | -DADMINDIR=\"/var/lib/dpkg\" -DLIBDIR=\"/usr/lib/dpkg\"
> | -DLOCALLIBDIR=\"/usr/local/lib/dpkg\" -idirafter ../../lib/compat
> | -iquote . -I.. -I../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti
> | -fno-exceptions -Wall -Wextra -Wcast-align -Wduplicated-branches
> | -Wduplicated-cond -Wformat -Wformat-security -Wformat=2 -Winit-self
> | -Wlogical-not-parentheses -Wlogical-op -Wmissing-declarations
> | -Wmissing-format-attribute -Wno-missing-field-initializers
> | -Wno-nonnull-compare -Wno-unused-parameter -Wnull-dereference
> | -Wpointer-arith -Wredundant-decls -Wregister -Wrestrict -Wshadow
> | -Wshift-negative-value -Wsizeof-array-argument -Wswitch-bool -Wvla
> | -Wwrite-strings -Wc++11-compat -Wcast-qual -Wold-style-cast
> | -Wzero-as-null-pointer-constant -g -O2
> | -fdebug-prefix-map=/<>=. -fstack-protector-strong
> | -Wformat -Werror=format-security -Wall -Wextra
> | -Wno-missing-field-initializers -Wno-nonnull-compare
> | -Wno-unused-parameter -MT curkeys.o -MD -MP -MF .deps/curkeys.Tpo -c
> | -o curkeys.o ../../dselect/curkeys.cc
> | mv -f .deps/pkgdisplay.Tpo .deps/pkgdisplay.Po
> | mv -f .deps/pkginfo.Tpo .deps/pkginfo.Po
> | mv -f .deps/pkgcmds.Tpo .deps/pkgcmds.Po
> | In file included from ../../dselect/curkeys.cc:30:
> | ./curkeys.h:168:5: error: ‘KEY_EVENT’ was not declared in this scope; did
> you mean ‘KEY_OPEN’?
> | 168 | { KEY_EVENT, "Event" },
> | | ^
> | | KEY_OPEN
> | make[4]: *** [Makefile:617: curkeys.o] Error 1
> | make[4]: *** Waiting for unfinished jobs
> | mv -f .deps/pkgdepcon.Tpo .deps/pkgdepcon.Po
> | mv -f .deps/pkgsublist.Tpo .deps/pkgsublist.Po
> | mv -f .deps/pkgtop.Tpo .deps/pkgtop.Po
> | mv -f .deps/pkglist.Tpo .deps/pkglist.Po
> | make[4]: Leaving directory '/<>/build-tree/dselect'
> | make[3]: *** [Makefile:650: all-recursive] Error 1
> | make[3]: Leaving directory '/<>/build-tree/dselect'
> | make[2]: *** [Makefile:743: all-recursive] Error 1
> | make[2]: Leaving directory '/<>/build-tree'
> | make[1]: *** [Makefile:609: all] Error 2
> | make[1]: Leaving directory '/<>/build-tree'
> | make: *** [debian/rules:74: build] Error 2
> | dpkg-buildpackage: error: debian/rules binary subprocess returned exit
> status 2
>
> I suppose this is connected to a ncurses upload.
Quoting the ncurses NEWS file:
,
| 20200817
| + prevent KEY_EVENT from appearing in curses.h unless the configure
| option --enable-wgetch-events is used (report by Werner Fink).
`
See the thread at
https://lists.gnu.org/archive/html/bug-ncurses/2020-08/threads.html#00017
for a discussion that motivated this change.
Cheers,
Sven
Processed: Bug#966951 marked as pending in libpeas
Processing control commands: > tag -1 pending Bug #966951 [libpeas] libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found Ignoring request to alter tags of bug #966951 to the same tags previously set -- 966951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966951: marked as pending in libpeas
Control: tag -1 pending Hello, Bug #966951 in libpeas 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/gnome-team/libpeas/-/commit/8c8a5825dd6c6eba60ef0f472c993b32c8bad220 Add proposed patch to fix FTBFS with Meson 0.55.0 Closes: #966951 (this message was generated automatically) -- Greetings https://bugs.debian.org/966951
Processed: Re: Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Processing control commands: > tags -1 moreinfo Bug #970555 [src:ncurses] ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) Added tag(s) moreinfo. -- 970555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Control: tags -1 moreinfo On 2020-09-18 16:55 +0200, Bas Couwenberg wrote: > Source: ncurses > Version: 6.2+20200912-1 > Severity: serious > Justification: makes the package in question unusable or mostly so > > Dear Maintainer, > > Upgrading sid & experimental pbuilder chroots fails due to the new ncurses: > > Preparing to unpack .../libncursesw6_6.2+20200912-1_amd64.deb ... > Unpacking libncursesw6:amd64 (6.2+20200912-1) over (6.2-1) ... > Preparing to unpack .../libncurses6_6.2+20200912-1_amd64.deb ... > Unpacking libncurses6:amd64 (6.2+20200912-1) over (6.2-1) ... > rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version > `NCURSES6_TINFO_6.2.current' not found (required by > /lib/x86_64-linux-gnu/libncurses.so.6) > dpkg: error while cleaning up: > rm command for cleanup subprocess returned error exit status 1 > dpkg-split: /lib/x86_64-linux-gnu/libtinfo.so.6: version > `NCURSES6_TINFO_6.2.current' not found (required by > /lib/x86_64-linux-gnu/libncurses.so.6) > rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version > `NCURSES6_TINFO_6.2.current' not found (required by > /lib/x86_64-linux-gnu/libncurses.so.6) > dpkg: error processing archive > /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb (--unpack): > rm command for cleanup subprocess returned error exit status 1 > Errors were encountered while processing: > /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) I cannot reproduce this, but my pbuilder chroots do not have libncurses6 installed at all. What is this rm binary in your chroot, apparently it is linked to libncurses.so.6? Cheers, Sven
Bug#970556: vulkan-validationlayers-dev: ships /usr/include/xxhash.h already provided by libxxhash-dev
Package: vulkan-validationlayers-dev Version: 1.2.148.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../vulkan-validationlayers-dev_1.2.148.0-1_amd64.deb ... Unpacking vulkan-validationlayers-dev:amd64 (1.2.148.0-1) ... dpkg: error processing archive /var/cache/apt/archives/vulkan-validationlayers-dev_1.2.148.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/xxhash.h', which is also in package libxxhash-dev:amd64 0.8.0-1 Errors were encountered while processing: /var/cache/apt/archives/vulkan-validationlayers-dev_1.2.148.0-1_amd64.deb cheers, Andreas libxxhash-dev=0.8.0-1_vulkan-validationlayers-dev=1.2.148.0-1.log.gz Description: application/gzip
Bug#970555: ncurses: Upgrade fails: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)
Source: ncurses Version: 6.2+20200912-1 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, Upgrading sid & experimental pbuilder chroots fails due to the new ncurses: Preparing to unpack .../libncursesw6_6.2+20200912-1_amd64.deb ... Unpacking libncursesw6:amd64 (6.2+20200912-1) over (6.2-1) ... Preparing to unpack .../libncurses6_6.2+20200912-1_amd64.deb ... Unpacking libncurses6:amd64 (6.2+20200912-1) over (6.2-1) ... rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) dpkg: error while cleaning up: rm command for cleanup subprocess returned error exit status 1 dpkg-split: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) rm: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6) dpkg: error processing archive /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb (--unpack): rm command for cleanup subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libtinfo6_6.2+20200912-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Kind Regards, Bas
Processed: this is a bug in ruby-autoprefixer-rails
Processing control commands: > reassign -1 ruby-autoprefixer-rails Bug #970550 [diaspora] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Bug reassigned from package 'diaspora' to 'ruby-autoprefixer-rails'. No longer marked as found in versions 0.7.14.0-2. Ignoring request to alter fixed versions of bug #970550 to the same values previously set > found -1 8.6.5+dfsg-3 Bug #970550 [ruby-autoprefixer-rails] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Marked as found in versions ruby-autoprefixer-rails/8.6.5+dfsg-3. -- 970550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970550: this is a bug in ruby-autoprefixer-rails
Control: reassign -1 ruby-autoprefixer-rails Control: found -1 8.6.5+dfsg-3 After replacing sass-rails, execjs and autoprefixer-rails (taking clues from the error log) with versions from rubygems.org, I found autoprefixer-rails version installed from rubygems.org fixes this issue, so the bug is in ruby-autoprefixer-rails.
Bug#970134: libweston-9-dev: missing (unversioned) Breaks+Replaces: libweston-8-dev
Hello, On Sat, 12 Sep 2020 at 11:21, Andreas Beckmann wrote: > > Package: libweston-9-dev > Version: 9.0.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > >From the attached log (scroll to the bottom...): > > Preparing to unpack .../libweston-9-dev_9.0.0-1_amd64.deb ... > Unpacking libweston-9-dev (9.0.0-1) ... > dpkg: error processing archive > /var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb (--unpack): >trying to overwrite '/usr/lib/x86_64-linux-gnu/weston/libexec_weston.so', > which is also in package libweston-8-dev 8.0.0-1 > Errors were encountered while processing: >/var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb > > Since libweston-8-dev is gone, the Breaks+Replaces can be unversioned. Thanks for the report, I have been investigating a bit this issue, libexec_weston was introduced in weston_8, it was created for the purpose of the reset of the test suite so it doesn't need to exec() but just load libexec_weston.so. libexec_weston is not something anyone else should develop against, it is only needed by weston binary. I'll look into dropping /usr/lib/x86_64-linux-gnu/weston/libexec_weston.so since weston is linked to /usr/lib/x86_64-linux-gnu/weston/libexec_weston.so.0 which should be shipped in the weston package. Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Bug#957998: marked as done (xserver-xorg-video-ati: ftbfs with GCC-10)
Your message dated Fri, 18 Sep 2020 13:19:30 + with message-id and subject line Bug#957998: fixed in xserver-xorg-video-ati 1:19.1.0-2 has caused the Debian Bug report #957998, regarding xserver-xorg-video-ati: 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.) -- 957998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xserver-xorg-video-ati Version: 1:19.1.0-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/xserver-xorg-video-ati_19.1.0-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o evergreen_shader.lo ../../src/evergreen_shader.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../src/evergreen_shader.c -fPIC -DPIC -o .libs/evergreen_shader.o /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o evergreen_textured_videofuncs.lo ../../src/evergreen_textured_videofuncs.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../src/evergreen_textured_videofuncs.c -fPIC -DPIC -o .libs/evergreen_textured_videofuncs.o /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o cayman_accel.lo ../../src/cayman_accel.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../src/cayman_accel.c -fPIC -DPIC -o .libs/cayman_accel.o /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/libdrm -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o cayman_shader.lo
Processed: severity of 960650 is serious
Processing commands for cont...@bugs.debian.org: > # raising to RC severity as stable will get an update and there should be > ideally not stable- regression > severity 960650 serious Bug #960650 [inspircd] InspIRCd Security Advisories 2019-02 and 2020-01 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 960650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 960650 is grave
Processing commands for cont...@bugs.debian.org: > severity 960650 grave Bug #960650 [inspircd] InspIRCd Security Advisories 2019-02 and 2020-01 Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 960650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 970356, severity of 970356 is grave
Processing commands for cont...@bugs.debian.org: > # me too > tags 970356 + confirmed Bug #970356 [mssh] assertion failed in vte_terminal_spawn_with_fds_async Added tag(s) confirmed. > # makes the package in question unusable > severity 970356 grave Bug #970356 [mssh] assertion failed in vte_terminal_spawn_with_fds_async Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 970356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 970379
Processing commands for cont...@bugs.debian.org: > tags 970379 + pending Bug #970379 [cpp-hocon] FTBFS: cpp-hocon fails to build against boost1.71 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 970379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970550: diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined
Package: diaspora Version: 0.7.14.0-2 Severity: grave Using packages from https://wiki.debian.org/Diaspora#Buster_Fasttrack.2Fpersonal_repo (as rails 5 in not available in unstable/experimental) installation fails with Bundle complete! 101 Gemfile dependencies, 223 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Setting up secret_token... Checking if the database is empty... diaspora_production database is not empty, skipping database setup Running migrations... Precompiling assets... rake aborted! ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined /usr/share/diaspora/app/assets/config/manifest.js:9 (execjs):150:23 (execjs):76:3 (execjs):77:2 (execjs):8643:14 (execjs):1:40 Object. ((execjs):1:58) Module._compile (internal/modules/cjs/loader.js:778:30) Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) Module.load (internal/modules/cjs/loader.js:653:32) tryModuleLoad (internal/modules/cjs/loader.js:593:12) /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:153:in `runtime' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:37:in `process' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:20:in `run' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:14:in `call' /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package diaspora (--configure): installed diaspora package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: diaspora E: Sub-process /usr/bin/dpkg returned an error code (1)
Bug#970545: dpkg FTBFS: KEY_EVENT undeclared
Source: dpkg
Version: 1.20.5
Severity: serious
Tags: ftbfs
dpkg FTBFS as of today:
| g++ -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\"
-DADMINDIR=\"/var/lib/dpkg\" -DLIBDIR=\"/usr/lib/dpkg\"
-DLOCALLIBDIR=\"/usr/local/lib/dpkg\" -idirafter ../../lib/compat -iquote .
-I.. -I../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti -fno-exceptions
-Wall -Wextra -Wcast-align -Wduplicated-branches -Wduplicated-cond -Wformat
-Wformat-security -Wformat=2 -Winit-self -Wlogical-not-parentheses -Wlogical-op
-Wmissing-declarations -Wmissing-format-attribute
-Wno-missing-field-initializers -Wno-nonnull-compare -Wno-unused-parameter
-Wnull-dereference -Wpointer-arith -Wredundant-decls -Wregister -Wrestrict
-Wshadow -Wshift-negative-value -Wsizeof-array-argument -Wswitch-bool -Wvla
-Wwrite-strings -Wc++11-compat -Wcast-qual -Wold-style-cast
-Wzero-as-null-pointer-constant -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra
-Wno-missing-field-initializers -Wno-nonnull-compare -Wno-unused-parameter -MT
curkeys.o -MD -MP -MF .deps/curkeys.Tpo -c -o curkeys.o ../../dselect/curkeys.cc
| mv -f .deps/pkgdisplay.Tpo .deps/pkgdisplay.Po
| mv -f .deps/pkginfo.Tpo .deps/pkginfo.Po
| mv -f .deps/pkgcmds.Tpo .deps/pkgcmds.Po
| In file included from ../../dselect/curkeys.cc:30:
| ./curkeys.h:168:5: error: ‘KEY_EVENT’ was not declared in this scope; did you
mean ‘KEY_OPEN’?
| 168 | { KEY_EVENT, "Event" },
| | ^
| | KEY_OPEN
| make[4]: *** [Makefile:617: curkeys.o] Error 1
| make[4]: *** Waiting for unfinished jobs
| mv -f .deps/pkgdepcon.Tpo .deps/pkgdepcon.Po
| mv -f .deps/pkgsublist.Tpo .deps/pkgsublist.Po
| mv -f .deps/pkgtop.Tpo .deps/pkgtop.Po
| mv -f .deps/pkglist.Tpo .deps/pkglist.Po
| make[4]: Leaving directory '/<>/build-tree/dselect'
| make[3]: *** [Makefile:650: all-recursive] Error 1
| make[3]: Leaving directory '/<>/build-tree/dselect'
| make[2]: *** [Makefile:743: all-recursive] Error 1
| make[2]: Leaving directory '/<>/build-tree'
| make[1]: *** [Makefile:609: all] Error 2
| make[1]: Leaving directory '/<>/build-tree'
| make: *** [debian/rules:74: build] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
I suppose this is connected to a ncurses upload.
Helmut
Bug#966951: libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1
Control: clone -1 -2 Control: retitle -1 libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found Control: reassign -1 libpeas 1.26.0-2 Control: tags -1 = ftbfs pending Control: severity -2 normal Control: retitle -2 meson: gnome module stopped generating uninstalled typelib depended on by an executable Control: reassign -2 meson 0.55.0-2 Control: forwarded -2 https://github.com/mesonbuild/meson/issues/7756 Control: tags -2 = upstream On Mon, 03 Aug 2020 at 13:09:55 +0100, Simon McVittie wrote: > I've confirmed that this succeeds in a pure bullseye chroot and fails if > I upgrade meson (only) to the version from unstable. I'm not completely > sure whether this is a straightforward regression in meson, or whether > libpeas is holding it wrong. I'm still not sure whose bug this is, but I've found a workaround that libpeas can use (or a fix that can be applied, depending whether this is considered to be a bug in Meson or in libpeas). I'll close the original FTBFS report by fixing or working around this in libpeas; I'm cloning it as a non-RC Meson bug report for investigation of whether Meson is doing the wrong thing. Please see the upstream Meson bug for more details and a somewhat minimal reproducer. Thanks, smcv
Processed: Re: Bug#966951: libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1
Processing control commands: > clone -1 -2 Bug #966951 [libpeas,meson] libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 Bug 966951 cloned as bug 970543 > retitle -1 libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace > 'Introspection', version '1.0' not found Bug #966951 [libpeas,meson] libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 Changed Bug title to 'libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found' from 'libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1'. > reassign -1 libpeas 1.26.0-2 Bug #966951 [libpeas,meson] libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found Bug reassigned from package 'libpeas,meson' to 'libpeas'. No longer marked as found in versions libpeas/1.26.0-2 and meson/0.55.0-2. Ignoring request to alter fixed versions of bug #966951 to the same values previously set Bug #966951 [libpeas] libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found There is no source info for the package 'libpeas' at version '1.26.0-2' with architecture '' Unable to make a source version for version '1.26.0-2' Marked as found in versions 1.26.0-2. > tags -1 = ftbfs pending Bug #966951 [libpeas] libpeas: FTBFS with Meson >= 0.55.0: Typelib file for namespace 'Introspection', version '1.0' not found Added tag(s) pending; removed tag(s) bullseye and sid. > severity -2 normal Bug #970543 [libpeas,meson] libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 Severity set to 'normal' from 'serious' > retitle -2 meson: gnome module stopped generating uninstalled typelib > depended on by an executable Bug #970543 [libpeas,meson] libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 Changed Bug title to 'meson: gnome module stopped generating uninstalled typelib depended on by an executable' from 'libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1'. > reassign -2 meson 0.55.0-2 Bug #970543 [libpeas,meson] meson: gnome module stopped generating uninstalled typelib depended on by an executable Bug reassigned from package 'libpeas,meson' to 'meson'. No longer marked as found in versions meson/0.55.0-2 and libpeas/1.26.0-2. Ignoring request to alter fixed versions of bug #970543 to the same values previously set Bug #970543 [meson] meson: gnome module stopped generating uninstalled typelib depended on by an executable Marked as found in versions meson/0.55.0-2. > forwarded -2 https://github.com/mesonbuild/meson/issues/7756 Bug #970543 [meson] meson: gnome module stopped generating uninstalled typelib depended on by an executable Set Bug forwarded-to-address to 'https://github.com/mesonbuild/meson/issues/7756'. > tags -2 = upstream Bug #970543 [meson] meson: gnome module stopped generating uninstalled typelib depended on by an executable Added tag(s) upstream; removed tag(s) ftbfs, bullseye, and sid. -- 966951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966951 970543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958000: marked as done (xserver-xorg-video-openchrome: ftbfs with GCC-10)
Your message dated Fri, 18 Sep 2020 10:05:35 + with message-id and subject line Bug#958000: fixed in xserver-xorg-video-openchrome 1:0.6.0-4 has caused the Debian Bug report #958000, regarding xserver-xorg-video-openchrome: 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.) -- 958000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xserver-xorg-video-openchrome Version: 1:0.6.0-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/xserver-xorg-video-openchrome_0.6.0-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: .libs/via_driver.o:./build/src/../../src/via_vt1632.h:47: multiple definition of `via_vt1632_funcs'; .libs/via_analog.o:./build/src/../../src/via_vt1632.h:47: first defined here /usr/bin/ld: .libs/via_i2c.o:./build/src/../../src/via_driver.h:398: multiple definition of `iga2_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:398: first defined here /usr/bin/ld: .libs/via_i2c.o:./build/src/../../src/via_driver.h:397: multiple definition of `iga1_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:397: first defined here /usr/bin/ld: .libs/via_i2c.o:./build/src/../../src/via_vt1632.h:47: multiple definition of `via_vt1632_funcs'; .libs/via_analog.o:./build/src/../../src/via_vt1632.h:47: first defined here /usr/bin/ld: .libs/via_id.o:./build/src/../../src/via_driver.h:398: multiple definition of `iga2_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:398: first defined here /usr/bin/ld: .libs/via_id.o:./build/src/../../src/via_driver.h:397: multiple definition of `iga1_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:397: first defined here /usr/bin/ld: .libs/via_id.o:./build/src/../../src/via_vt1632.h:47: multiple definition of `via_vt1632_funcs'; .libs/via_analog.o:./build/src/../../src/via_vt1632.h:47: first defined here /usr/bin/ld: .libs/via_fp.o:./build/src/../../src/via_driver.h:398: multiple definition of `iga2_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:398: first defined here /usr/bin/ld: .libs/via_fp.o:./build/src/../../src/via_driver.h:397: multiple definition of `iga1_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:397: first defined here /usr/bin/ld: .libs/via_fp.o:./build/src/../../src/via_vt1632.h:47: multiple definition of `via_vt1632_funcs'; .libs/via_analog.o:./build/src/../../src/via_vt1632.h:47: first defined here /usr/bin/ld: .libs/via_memcpy.o:./build/src/../../src/via_driver.h:398: multiple definition of `iga2_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:398: first defined here /usr/bin/ld: .libs/via_memcpy.o:./build/src/../../src/via_driver.h:397: multiple definition of `iga1_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:397: first defined here /usr/bin/ld: .libs/via_memcpy.o:./build/src/../../src/via_vt1632.h:47: multiple definition of `via_vt1632_funcs'; .libs/via_analog.o:./build/src/../../src/via_vt1632.h:47: first defined here /usr/bin/ld: .libs/via_memmgr.o:./build/src/../../src/via_driver.h:398: multiple definition of `iga2_crtc_funcs'; .libs/via_analog.o:./build/src/../../src/via_driver.h:398: first defined here /usr/bin/ld: .libs/via_memmgr.o:./build/src/../../src/via_driver.h:397: multiple definition of `iga1_crtc_funcs';
Processed: bug 968875 is forwarded to https://github.com/rss2email/rss2email/issues/134
Processing commands for cont...@bugs.debian.org:
> forwarded 968875 https://github.com/rss2email/rss2email/issues/134
Bug #968875 {Done: gustavo panizzo } [rss2email] rss2email
forges envelope sender
Ignoring request to change the forwarded-to-address of bug#968875 to the same
value
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#969288: marked as done (src:r-cran-htmltools: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Fri, 18 Sep 2020 09:33:47 + with message-id and subject line Bug#969288: fixed in r-cran-htmltools 0.5.0-2 has caused the Debian Bug report #969288, regarding src:r-cran-htmltools: fails to migrate to testing for too long: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-htmltools Version: 0.4.0-2 Severity: serious Control: close -1 0.5.0-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:r-cran-htmltools in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-htmltools signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: r-cran-htmltools Source-Version: 0.5.0-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-htmltools, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-htmltools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Sep 2020 11:12:04 +0200 Source: r-cran-htmltools Architecture: source Version: 0.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 969288 Changes: r-cran-htmltools (0.5.0-2) unstable; urgency=medium . * Make autopkgtest work Closes: #969288 Checksums-Sha1: a177c311e2276afc142fe50f21c2a92cbf3fd192 2187 r-cran-htmltools_0.5.0-2.dsc 4435b17f58b5194efb6f9330e10c511a55502b63 2872 r-cran-htmltools_0.5.0-2.debian.tar.xz 49d27518e7b18bc6712a0bfc90f4825a009c8382 8833 r-cran-htmltools_0.5.0-2_amd64.buildinfo Checksums-Sha256: c5375a95c10c42f2af79a3fe990be18bedf142a100b769ea37075db6b774b463 2187 r-cran-htmltools_0.5.0-2.dsc 98d4cb79731115b80408aa0c392758019c3e8544629775938ddaa47ff9d15828 2872 r-cran-htmltools_0.5.0-2.debian.tar.xz 1a7e577cb2bb3861dbe1ebd5e7a8abaa8a0e91d153e1238f0d2447e6fde83dd5 8833 r-cran-htmltools_0.5.0-2_amd64.buildinfo Files: d454aaccbe93865276deeb69d446abd4 2187 gnu-r optional r-cran-htmltools_0.5.0-2.dsc 5516fd243ca372ff64df09789b331396 2872 gnu-r optional r-cran-htmltools_0.5.0-2.debian.tar.xz 80f21e43a32504e0d9791dd99f8ea243 8833 gnu-r optional r-cran-htmltools_0.5.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9kep4RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFrDw/zBApaTO645TGbviMnOBFuBNmrY65OV3Yn Ttwhk+QqxcKamwCAxedWBPnLufKxBvv+0FU/bWo0bwaoQ8mOB5CkApqq8yH2DuGd
Bug#969881: marked as done (wmforecast: autopkgtest should be marked superficial)
Your message dated Fri, 18 Sep 2020 09:05:54 + with message-id and subject line Bug#969881: fixed in wmforecast 1.4-2 has caused the Debian Bug report #969881, regarding wmforecast: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmforecast Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'wmforecast' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'wmforecast'. -- Sudip --- End Message --- --- Begin Message --- Source: wmforecast Source-Version: 1.4-2 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of wmforecast, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated wmforecast 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, 17 Sep 2020 07:29:51 -0400 Source: wmforecast Architecture: source Version: 1.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Window Maker Team Changed-By: Doug Torrance Closes: 969881 Changes: wmforecast (1.4-2) unstable; urgency=medium . * debian/tests/control - Add Restrictions: superficial (Closes: #969881). Checksums-Sha1: 8184988ba9a7ecd3c970dfa95c7b8b128559c59c 2248 wmforecast_1.4-2.dsc b6cf7fc85185270303c3ddf5e5a09dc5c9dff32c 14296 wmforecast_1.4-2.debian.tar.xz Checksums-Sha256: 406afe04a52e1f3415dcd07921ac9d92350ab1d14b9e00fe925da7b4651d2525 2248 wmforecast_1.4-2.dsc 56543008cd2f03750ab33f543fa8a96d8875880c5d371bba50614903cf847879 14296 wmforecast_1.4-2.debian.tar.xz Files: 47b586a25c2f319877da2388d0413cbf 2248 utils optional wmforecast_1.4-2.dsc 61ecc74ebc5f8c36b504e8baadf98fbb 14296 utils optional wmforecast_1.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl9kdC4ACgkQpU8BhUOC FIQzWxAAo0u6eUMQPdggbKSMc6r3hcu9Mbpt4tb4WHmzJwgXSN2SPGsK5h4pjcQ9 rScJis2u7jkjrG9d8O8Nk6mcwWQ+0HY6/2MrBlpcjvCaMPhxUKj7c6H2OZ5MjtVc VDcnrWBIcN3CPYQmdk+v9Oz2AE5+3E1t4eu6PkM6U23ceKrf/uHS5LGpBOvKe1um X2ThefN2IV6PrLDEHUySSNh2jxSt6qrsGmTUOSVa0e60NrSfQmQpbNg0umLQgKjf +IL/FKX+gX3Uy2QMc3TUgmQdUxOes5l7vBBrDuBJ18SS9yRLuAnlZCwvIydlN+FW GvfPTl95U+TTR1Y+hhb9KQ20N5yN0hI1Xo3xtIdQ79AJrz6/QEz8RalBHJrhMp95 Wdo3oRHASQjlxur9JGC1iFz/axrK+vn78vuo1xKjMRpP/IyMxybCgLJWfPkajR0F 03tnRrS6miyLlZuV2x7gVG1QL1/wV09H1wLlb3jse2q6RJHFq/OztgNn21CH8/5d 7EBDzQyTNguPRtaCp3DJe9nyskwlp1EUkoccX1c1deTaw2ETqrXOvsyAuloITLbe qxMmLUEpq3Q6oL1W0q5eIvWowT8PDYgesxLxibsaAylIdCD4YO1/7swl61iNnWEP H10kblBau9OEvOrb+WVQKdbvi2x0707/xRj4/91rTLcA11lGq8c= =Ex3q -END PGP SIGNATURE End Message ---
Bug#969882: marked as done (wmxres: autopkgtest should be marked superficial)
Your message dated Fri, 18 Sep 2020 09:05:59 + with message-id and subject line Bug#969882: fixed in wmxres 1.4-2 has caused the Debian Bug report #969882, regarding wmxres: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmxres Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'wmxres' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'wmxres'. -- Sudip --- End Message --- --- Begin Message --- Source: wmxres Source-Version: 1.4-2 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of wmxres, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated wmxres 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, 17 Sep 2020 07:31:51 -0400 Source: wmxres Architecture: source Version: 1.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Window Maker Team Changed-By: Doug Torrance Closes: 969882 Changes: wmxres (1.4-2) unstable; urgency=medium . * debian/tests/control - Add Restrictions: superficial (Closes: #969882). Checksums-Sha1: 4237e108891c885f50bec1b18810f511352206f9 1964 wmxres_1.4-2.dsc ca93a386d2707d8895583f2527091959a2e21cdb 3500 wmxres_1.4-2.debian.tar.xz Checksums-Sha256: 6bc86d642fec1f77d037bb19e65f79dacf50235721bf52c95f7feda10af4a67f 1964 wmxres_1.4-2.dsc e8df8139b4cf0f2d97bb3ec0fd9ff97c9e40f079c94aea70aac9552734989202 3500 wmxres_1.4-2.debian.tar.xz Files: 68532138987c0d3e561c090626346046 1964 x11 optional wmxres_1.4-2.dsc 35eadd0daa0963b6ca7edd62a9b21bb9 3500 x11 optional wmxres_1.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl9kdFIACgkQpU8BhUOC FIRjRhAAnKDJZcJCScTVfQpgAxUVCjJnzgrqZePcaSFWBmu+IHfz62y0Jke3b9PT IpuO2+M3O66EFuTXJC8N9bC3VKchWTKeROW3zVl/B1twWOLRq/3AbUXETcU8IagT ScBqikSwm3hniuCUwpQay75ymz2wqnTQ+70FP27sPEZiZuXUh91LpsPqUn2MhnB5 3XXUhH0n9gX6S5GZfrjkLygyzQTCwjEP0zuofcivzw0aTNVPiPvEfHkBvv75lTH9 O/J+9SYUBE/wmnuycGl2Tfxo/3HZnT+SxxKVduIuZ8NOGMux2IKxqKNfLCOFFhUb Em6To81eq7BBEIGPBgE7aZK3Psr9MkoXNXOODd0033DleQDFYEaev+LwDRXaIB+f eBvhJOaHkvXAH7aOj2W7M1BVnXeijlGC9V/UCzXUBXE6lMXZY8YFKWoghMMrXH7B NMuhgfC5ryEs89dnTAJELRu9fuQptcQJAY9UUEpk5CkBSzaA1p8ftSMSfQsC373k Rgefj5Bh0j7H0KI6XQHc1sZVtp4Ygb0WMK66/c0Rh+6xa+r5+pd5ihv0Ngx7ZZuT Hy8meo9AsFx2L60pXqMCUXleaLlYeUVIaBu0vV6M1AwQGyE5JT/nqRsX5V1R5ZwY gZM2W620rAqwc4FUm025QtbVJYAW9dw3jajS3K5Si1ETdHmA9VI= =lKTP -END PGP SIGNATURE End Message ---
Bug#954513: marked as done (gcc-9-cross: FTBFS: checking whether .eh_frame section should be read-only... /usr/bin/x86_64-linux-gnu-ld: /usr/x86_64-linux-gnu/lib/../lib/libpthread.so.0: undefined refe
Your message dated Fri, 18 Sep 2020 10:50:35 +0200 with message-id and subject line Re: gcc-9-cross: FTBFS: checking ... has caused the Debian Bug report #954513, regarding gcc-9-cross: FTBFS: checking whether .eh_frame section should be read-only... /usr/bin/x86_64-linux-gnu-ld: /usr/x86_64-linux-gnu/lib/../lib/libpthread.so.0: undefined reference to `__libc_vfork@GLIBC_PRIVATE' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 19 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem > /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include > -isystem /<>/gcc/build/sys-include-DHAVE_CONFIG_H -I. > -I../../../../src/libgfortran -iquote../../../../src/libgfortran/io > -I../../../../src/libgfortran/../gcc > -I../../../../src/libgfortran/../gcc/config > -I../../../../src/libgfortran/../libquadmath -I../../.././gcc > -I../../../../src/libgfortran/../libgcc -I../../libgcc > -I../../../../src/libgfortran/../libbacktrace -I../../libbacktrace > -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wold-style-definition -Wextra -Wwrite-strings > -Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules > -ffunction-sections -fdata-sections -g -O2 -m32 -MT pow_r10_i8.lo -MD -MP > -MF .deps/pow_r10_i8.Tpo -c -o pow_r10_i8.lo `test -f > '../../../../src/libgfortran/generated/pow_r10_i8.c' || echo > '../../../../src/libgfortran/'`../../../../src/libgfortran/generated/pow_r10_i8.c > yes > checking assembler supports pc related relocs... yes > checking toolchain supports unwind section type... libtool: compile: > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem > /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include > -isystem /<>/gcc/build/sys-include -DHAVE_CONFIG_H -I. > -I../../../../src/libgfortran -iquote../../../../src/libgfortran/io > -I../../../../src/libgfortran/../gcc > -I../../../../src/libgfortran/../gcc/config > -I../../../../src/libgfortran/../libquadmath -I../../.././gcc > -I../../../../src/libgfortran/../libgcc -I../../libgcc > -I../../../../src/libgfortran/../libbacktrace -I../../libbacktrace > -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wold-style-definition -Wextra -Wwrite-strings > -Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules > -ffunction-sections -fdata-sections -g -O2 -m32 -MT pow_r10_i8.lo -MD -MP -MF > .deps/pow_r10_i8.Tpo -c ../../../../src/libgfortran/generated/pow_r10_i8.c > -fPIC -DPIC -o .libs/pow_r10_i8.o > yes > checking whether .eh_frame section should be read-only... > /usr/bin/x86_64-linux-gnu-ld: > /usr/x86_64-linux-gnu/lib/../lib/libpthread.so.0: undefined reference to > `__libc_vfork@GLIBC_PRIVATE' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/03/21/gcc-9-cross_19_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 --- That built with a new build.--- End Message ---
Bug#970536: linux-image-5.8.0-1-amd64: ethernet (dhcp) fails to work after reboot
Package: src:linux Version: 5.8.7-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: olau...@gmail.com step to reproduce : - install debian testing a bit old (2020-08) with 5.7 kernel -> ethernet works normally - do the upgrades (which installs 5.8 kernel) - reboot to 5.8 -> ethernet works normally - reboot again on 5.8 -> ethernet not working (device is there, but dhcp fails) strange facts : as you can see, only the 2nd boot to 5.8 is bugged. - coming from a cold start or from windows make the 5.8 ethernet work again - after cold start / coming from windows, 5.7 booting and rebooting works great (so it seems really related to 5.8 kernel) - after 1 (or many) 5.8 boot, 5.7 is also affected. of course, all of that is resetted with a cold start / windows boot so 5.8 seems to put the ethernet chipset in a bad state. -- Package-specific info: ** Version: Linux version 5.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-1-amd64 root=UUID=20450dbb-67a2-4dea-9910-c5decc925848 ro quiet splash ** Not tainted ** Kernel log: [5.619159] EDAC amd64: Node 0: DRAM ECC disabled. [5.623118] snd_hda_intel :07:00.1: Disabling MSI [5.623126] snd_hda_intel :07:00.1: Handle vga_switcheroo audio client [5.623231] snd_hda_intel :09:00.3: enabling device ( -> 0002) [5.626494] systemd[1]: Mounted /boot/efi. [5.626579] systemd[1]: Reached target Local File Systems. [5.627182] systemd[1]: Starting Load AppArmor profiles... [5.627757] systemd[1]: Starting Set console font and keymap... [5.628685] systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... [5.628744] systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped. [5.628796] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. [5.631241] systemd[1]: Finished Set console font and keymap. [5.637181] snd_hda_intel :07:00.1: bound :07:00.0 (ops nv50_audio_component_bind_ops [nouveau]) [5.639860] systemd[1]: Received SIGRTMIN+20 from PID 371 (plymouthd). [5.641494] systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. [5.641948] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [5.641950] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [5.641952] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [5.641953] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [5.641953] snd_hda_codec_realtek hdaudioC1D0:dig-out=0x11/0x0 [5.641954] snd_hda_codec_realtek hdaudioC1D0:inputs: [5.641956] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 [5.641957] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 [5.641958] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a [5.642244] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input16 [5.642306] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input17 [5.642359] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input18 [5.642414] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input19 [5.642467] input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input20 [5.642517] input: HDA NVidia HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input21 [5.642568] input: HDA NVidia HDMI/DP,pcm=12 as /devices/pci:00/:00:03.1/:07:00.1/sound/card0/input22 [5.646055] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. [5.646258] systemd[1]: Condition check resulted in FUSE Control File System being skipped. [5.646363] systemd[1]: Condition check resulted in Kernel Configuration File System being skipped. [5.646460] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [5.646538] systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped. [5.646620] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [5.646671] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. [5.646705] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [5.649972] audit: type=1400 audit(1600417105.054:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=585 comm="apparmor_parser" [5.650300] audit: type=1400 audit(1600417105.054:3): apparmor="STATUS"
Bug#966872: marked as done (ncl: FTBFS: ld: cannot find -lncarg_c)
Your message dated Fri, 18 Sep 2020 07:05:44 + with message-id and subject line Bug#966872: fixed in ncl 6.6.2-3 has caused the Debian Bug report #966872, regarding ncl: FTBFS: ld: cannot find -lncarg_c to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ncl Version: 6.6.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -DACCEPT_USE_OF_DEPRECATED_PROJ_API_H=1 > -I/usr/include/hdf5/serial -o rgb rgb.o > -L../../../.././common/src/libncarg_c -lncarg_c > -L/<>/debian/tmp//lib-lgfortran > /usr/bin/ld: cannot find -lncarg_c > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/08/02/ncl_6.6.2-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: ncl Source-Version: 6.6.2-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of ncl, 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. Alastair McKinstry (supplier of updated ncl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Sep 2020 21:38:22 +0100 Source: ncl Architecture: source Version: 6.6.2-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 966872 Changes: ncl (6.6.2-3) unstable; urgency=medium . * Use external spherepack lib now it has double-precision support * Set d/gbp.conf to point to the new DEP-14 branch names * Ensure fortran/$(FC) page is in libdir path in d/rules * Fix bug in gfortran-10 conditional that FTBFS. Closes: #966872 * patch gcc10.patch for invalid BOZ constants. * Move to debhelper level 13 * Add -Wl,-z,muldefs , needed for stricter ld linking * Add d/not-installed; install extra manpages due to dh_missing audit Checksums-Sha1: d9f2a97698e07cf4333011977309c56a2231fb49 2742 ncl_6.6.2-3.dsc cd1a03d32eea560695ead16cd18b07d5f88bee40 56680 ncl_6.6.2-3.debian.tar.xz Checksums-Sha256: b64e421b2a467be14b909a9fabcefefe4aac8cc1d43f4d60f83cdecae08bf1c9 2742 ncl_6.6.2-3.dsc 65373bdc27191b6d84e2af9d707cb8350865e7ee0895ba16d287538b06ede559 56680 ncl_6.6.2-3.debian.tar.xz Files: 3d8622cb58afd38ee8989f11c55e327b 2742 science optional ncl_6.6.2-3.dsc 068d1d1ff6735394c0df4f3028cab9e0 56680 science optional ncl_6.6.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl9kVXkACgkQy+a7Tl2a 06VJvw//f+KwujwgD7KcZcW5k9fyEIwEwX0VY75Wo3w4Vd8TV+WPvzz/SbKPMm4e 1fkOwFhfQburaIof6ncF5G/7FnTQsDZ2u5JjPq4EtER29H2TmOyAeMMnq7LwLOqw HP8mT0ZZZ7j0FQYR0VmMPIEs0xdlL60bOOzysrD4V6fCAMKVb//S7m1NPZc2GwyT 5DJjzgZucqztZMrlZ/uxxndg4Mld+bSIPD455pGf2SNfCoDs+YJeXiV3lUnsysqc nSr+aqfyjIll9nbI6YG7yg1NpINlZcr7ndPtTO2PFKK8rSJ1V1fHQeqAI+ByU+n0 6D3hS7132o3OY9MzM83KL4U0haZCMHCjtTVovr2FRbMFt+3Kg5PX8ydCHPLamQq+ Kl+yg6Da0ALRZPGNorg3WN68f7yu6Ubik0f7vVegt8zxzpoQR/P0PRKQB88maegq SA69g9jw2RK9IDGcgZsqjIVh7B1XKAX5Buc2m8BlEK671PNMlRvzAml7yc7Fd2E+ 8/RN6cA7Mfkh4xaC3Lk67J2PKpAYxPnK6e4HT9q69t33ySjEgT0KUZmmcFufo30R p2AAvqSnkWBj9MGV/5pPjn/COXd5Ws/4jeSfIe4CBbO8YE+c4q8YOHCKkyMtwqNz 0+mURs+LnNC83gQotKBvkXta2Sn65s+iUAPmpWZZi7bGTC1XzTE= =5aI3 -END PGP SIGNATURE End Message ---
Bug#968885: marked as done (bandage: binary-any FTBFS)
Your message dated Fri, 18 Sep 2020 06:48:35 +
with message-id
and subject line Bug#968885: fixed in bandage 0.8.1-4
has caused the Debian Bug report #968885,
regarding bandage: binary-any FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
968885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bandage
Version: 0.8.1-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=bandage=sid
...
debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
find debian/bandage-examples/usr/share/doc/bandage/examples -type f
-executable -exec chmod -x \{\} \;
find: ‘debian/bandage-examples/usr/share/doc/bandage/examples’: No such file or
directory
make[1]: *** [debian/rules:26: override_dh_fixperms] Error 1
--- End Message ---
--- Begin Message ---
Source: bandage
Source-Version: 0.8.1-4
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
bandage, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated bandage package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Sep 2020 11:20:12 +0200
Source: bandage
Architecture: source
Version: 0.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 968885
Changes:
bandage (0.8.1-4) unstable; urgency=medium
.
* Make sure architecture any builds will not fail
Closes: #968885
Checksums-Sha1:
959c2fa3906b9562059ab7245b6ff7d13902742b 2088 bandage_0.8.1-4.dsc
a789dc14d2198e7e2bb1863b70b88b1bc530f196 7504 bandage_0.8.1-4.debian.tar.xz
8034d86e372b6c13ed3e8c2712de1a516103dde2 9798 bandage_0.8.1-4_amd64.buildinfo
Checksums-Sha256:
a1b4f9d14fb94d7d594a98210c46fcbf20cc0e3250cf4eb4c46137f2713a32b9 2088
bandage_0.8.1-4.dsc
8081e49277792affb8058d38e0f85d62fd6da8d22a393b42dfa4be092da7e891 7504
bandage_0.8.1-4.debian.tar.xz
2228f573fe2c1c7d5f8e8141ea678227b6176f483652c5733afc8beaadcc2888 9798
bandage_0.8.1-4_amd64.buildinfo
Files:
90f9d8897dcd0135f51e4859459e0426 2088 science optional bandage_0.8.1-4.dsc
eb9b94d1c960ac7a38878f5d5376629c 7504 science optional
bandage_0.8.1-4.debian.tar.xz
dc6ca43451cbea48fdaa67e772b3a23d 9798 science optional
bandage_0.8.1-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9kVQMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHd1hAAmzVKPrysdlqdiw9ZrjcqvS9O6E0R6OtO
KduxLrLuFdZz7J2arEMIzbBjTE9vbJXj0QlcypVum7UXnaVZNA9QnsCFMb0owQwA
nA1rt5Wv5L72B1zjJl0gm49hibPcBhA47uxEm3YJvRL2IZv7HHwAvDHCur0j6jel
6YiN+bPIDf2vFv9ucp4k8+6oxXVV4Josnk6Wlc1CoAqOdqMCwvBXweoVNCavmNwr
L08syGb13fkBZAV5djLYZt1at9BZzAtKamoqRMNdb0125K6fqwfebsrUexzPVJut
zUFipYe7LBiMdTT7DjnHPpsYJgJVRUEtUEo3kJhhpjMcn3I7AQ6yACFdCYuOJPJp
cyhacAka92yOd+4C3m2MB+UvOqCLU/o92+g24/YsSHvb9CaawL3X3vHbYzaHEOjc
YFubi9NgblZ9o51wDwO/qd6MtFp+SNvjZIUPIaNa0ni8lmN/1H6sDMi6d6FExAyu
P902DfTiqzS8AlhaowmTnRNKapewgIJogHtiYq4hSH0CJcmKA1qSu7X6UTEphsw5
hLd7f0TVvSt2ZIU9aQhnEJeTO+PQDLiw7u/YAAf335yrujZUAYoBb5Tod7ZNPzsd
eJyjSlZdH3GtmbGNSPWf3rI1gJlvzGzkIwH/OC/v3wmkbt5thNNXd/p2bEshL7yE
dAvCcg2mxt4=
=CAeO
-END PGP SIGNATURE End Message ---
