Processed: severity of 962629 is serious
Processing commands for cont...@bugs.debian.org: > severity 962629 serious Bug #962629 [rainloop] rainloop: Rainloop stores passwords in cleartext in logfile Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868190: gatling: diff for NMU version 0.13-6.1
Control: tags 868190 + pending Dear maintainer, I've prepared an NMU for gatling (versioned as 0.13-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or cancel my upload. Regards, Fabio diff -Nru gatling-0.13/debian/changelog gatling-0.13/debian/changelog --- gatling-0.13/debian/changelog 2016-01-16 13:13:21.0 -0200 +++ gatling-0.13/debian/changelog 2020-06-08 22:41:54.0 -0300 @@ -1,3 +1,12 @@ +gatling (0.13-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * debian/patches/11-silently-ignore-uid-as-username-fix.patch: fix when using + -u parameter with username rather then a numeric user id. Thanks to Thomas + Kremer . (Closes: #868190) + + -- Fabio Dos Santos Mendes Mon, 08 Jun 2020 22:41:54 -0300 + gatling (0.13-6) unstable; urgency=medium * Added 10-mbedtls.patch to switch from polarssl to mbedtls, Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland.
Bug#962253: marked as done (esys-particle: Broken section number in manpage)
Your message dated Thu, 11 Jun 2020 06:18:44 + with message-id and subject line Bug#962253: fixed in esys-particle 2.3.5+dfsg2-1 has caused the Debian Bug report #962253, regarding esys-particle: Broken section number in manpage 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.) -- 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debhelper Version: 13.1 Severity: serious Control: affects -1 src:esys-particle Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=esys-particle ... dh_installman -a dh_installman: warning: Section for ./debian/esysparticle.1 is computed as "2012-12-30", which is not a valid section dh_installman: error: Could not determine section for ./debian/esysparticle.1 dh_installman: error: Aborting due to earlier error make: *** [debian/rules:15: binary-arch] Error 25 debhelper (13.1) unstable; urgency=low ... * dh_installman: Improve error messages and handling of broken section numbers. Notably ignore (with a warning) sections from manpages that look suspiciously like a version number. Thanks to Paul Gevers for reporting the bug. (Closes: #958343) ... --- End Message --- --- Begin Message --- Source: esys-particle Source-Version: 2.3.5+dfsg2-1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of esys-particle, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated esys-particle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 22:57:41 +0200 Source: esys-particle Architecture: source Version: 2.3.5+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 962253 Changes: esys-particle (2.3.5+dfsg2-1) unstable; urgency=medium . [ Adrian Bunk ] * [a2a3461] Fix the manpage section number. (Closes: #962253) . [ Anton Gladky ] * [79195f3] Set upstream metadata fields: Repository, Repository-Browse. * [bd11b4b] Drop unnecessary dependency on dh-autoreconf. * [9be1eac] Drop unnecessary dh arguments: --parallel * [994720f] Update standards version to 4.5.0, no changes needed. * [758e80e] Minor patch update * [2bf0c70] Add .gitlab-ci.yml * [08bdd6a] New upstream version 2.3.5+dfsg2 Checksums-Sha1: 38ff97351aaa0963f786835b13ac5f4e4d431919 2348 esys-particle_2.3.5+dfsg2-1.dsc f3070e5a3f6c01dc26a5e435a6422ed12fab6303 3790140 esys-particle_2.3.5+dfsg2.orig.tar.xz b913af0a9969ee130d402871cd41bddba47b3c13 565960 esys-particle_2.3.5+dfsg2-1.debian.tar.xz 636d23db236073fd363ca1919ed82f0d773a2819 18943 esys-particle_2.3.5+dfsg2-1_source.buildinfo Checksums-Sha256: 769fca8f525eb0621addc2fc0525db3849412b748e43b6c1b10e8983f6fc053b 2348 esys-particle_2.3.5+dfsg2-1.dsc ea2746adc860ee7febd410c5eaf97052ee8fbfd2577ed0eaa1ab2c45c297e585 3790140 esys-particle_2.3.5+dfsg2.orig.tar.xz 561d6b7cdc896f8c867f52f0b8bbbfe9094c2a51e92d09bdddf604008d277136 565960 esys-particle_2.3.5+dfsg2-1.debian.tar.xz ea45f5a515334fc25efbb5b5e0530a9fb79eb0ce33da5abfa60879c36bb5b9a5 18943 esys-particle_2.3.5+dfsg2-1_source.buildinfo Files: 70346d254823cf3f66366b4dc9ec161f 2348 science optional esys-particle_2.3.5+dfsg2-1.dsc 0f405f201b9780647994dc3cdf6f 3790140 science optional esys-particle_2.3.5+dfsg2.orig.tar.xz 3bf307ec17e139b07dcf6f1d941d9797 565960 science optional esys-particle_2.3.5+dfsg2-1.debian.tar.xz e623daa0a9eaffaf7daf203655caadd3 18943 science optional esys-particle_2.3.5+dfsg2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl7hyDEACgkQ0+Fzg8+n /wajUg/+OQmg4Vj9wKcqOU5vukzy/7f02WMCmzBMT5YWJg3Z7kFTD2SwslxqOlCc oWO/hyxfx8TcNDeTe/4a2ZjgThqpAd8nMiUTqtSUJ2SaRRpM2tFJ+3muuP1M3quF lWJadG6FnDdZBwI4QRHNHVD8QHRT/WjGJn97i7PzL4rmTv33OUi5pr1D7iVjNN3s TDnrba85CB3E2glLTeBrUjYp7sDUO1MrbJL+B8zaE7CW+eqWDqJot3iWCSk6ylWo DhB65O34zcEf5sifVGaAZdEf5FzlWN402GhFl9/54TYUuxbKRQ5p3ADjbEzf12iN bUBpvQRUf3Z+iXs4V2krZJl1qg+
Bug#962643: cunit: broken NMU does FTBFS
On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote: >... > The diffstat of this NMU is > 510 files changed, 139791 insertions(+), 3 deletions(-) > > It is the responsibility of the sponsor (Cc'ed) to verify that > sponsored uploads are not broken: > https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F I have to take that back, it is actually likely that this went wrong on the sponsor side due to verifying the package: The debdiff in #960715 looks OK. Building a source package for upload after having done a testbuild can cause this kind of problems, when the source tree is not clean many unwanted changes might end up in the new source package. cu Adrian
Bug#962158: lintian: New very problematic --fail-on default value
Felix Lechner wrote: > It would also give me more time to understand the possibly > unreasonable burden on Lintian users across Debian and the derivative > ecosystem. Simon may receive feedback from Ubuntu, a significant > derivative. If there are real problems, I am happy to discuss a > solution that reverts the default to Lintian's old setting. Without rehashing the details here, if Ubuntu's CI would prefer a different exit code, it would seem more sensible to keep the default the same and ask Ubuntu to specify a different --fail-on=. That would appear to limit require one change (and potential "fallout") to one place, and indeed in a place that has the ability to be changed. > Now the best course of action, I think, is to downgrade the severity > again to Guillem's original setting of 'important'. That will allow > the change to remain in testing. It is, after all, what the testing > distribution is for. Ah, yeah, I had forgotten about autoremovals. Sigh. > At the same time, the change was widely released two weeks ago. Simon > Quigley from Ubuntu announced it on debian-devel on May 25 [1], while > I advertised the change repeatedly on IRC and added a note to DevNews. Just as an aside, it feels like a slight stretch to assume that every Lintian user reads debian-devel, lurks on IRC or can be expected to come across this in another way. In the event that this default change stays, using the NEWS mechanism might be appropriate to explain concisely and exactly what a user may need to change (eg. "if you were relying on X, you should do Y".) We should also consider bumping the major version number of Lintian itself if we are strictly following the semver.org versioning scheme. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#962645: qbittorrent-nox: Qbittorrent-nox is barely usable after the upgrade to 4.2.4-1+b1
Package: qbittorrent-nox Version: 4.2.4-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Qbittorrent-nox has become unusable on both amd64 and i386 since the last binary update (4.2.4-1 to 4.2.4-1+b1) which was 7 days ago. It worked as it should before that update, on both systems. On my amd64 system (testing + unstable with xorg). I add a torrent, it shows up on the list, it downloads as it should and when the download is complete, it crashes with this output https://paste.debian.net/1151529/ Exiting it with ctrl+c pops up this https://paste.debian.net/1151532/ On the i386 system (unstable without xorg), things are a bit different. Once it is started, this line comes up again and again until I exit it with ctrl+c Caught exception in void BitTorrent::Session::handleAlert(const libtorrent::alert*) : "std::bad_alloc" And once it exits, this comes up https://paste.debian.net/1151531/ -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qbittorrent-nox depends on: ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libqt5core5a5.12.5+dfsg-10+b1 ii libqt5network5 5.12.5+dfsg-10+b1 ii libqt5xml5 5.12.5+dfsg-10+b1 ii libssl1.1 1.1.1g-1 ii libstdc++6 10.1.0-3 ii libtorrent-rasterbar10 1.2.5-1+b1 ii zlib1g 1:1.2.11.dfsg-2 qbittorrent-nox recommends no packages. Versions of packages qbittorrent-nox suggests: pn qbittorrent-dbg -- no debconf information
Bug#962643: cunit: broken NMU does FTBFS
Source: cunit Version: 2.1-3-dfsg-2.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cunit&suite=sid ... Making all in Framework make[6]: Entering directory '/<>/debian/build/CUnit/Sources/Framework' /bin/bash ../../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -DRELEASE=@RELEASE@ -Wall -W -pedantic -Wshadow -ansi -I/<>/debian/build/CUnit/Headers -std=c99 -Wl,-z,relro -Wl,-z,defs -L/<>/debian/build/CUnit/Sources -o libcunitfmk.la CUError.lo MyMem.lo TestDB.lo TestRun.lo Util.lo -lc libtool: link: ar cr .libs/libcunitfmk.a .libs/CUError.o .libs/MyMem.o .libs/TestDB.o .libs/TestRun.o .libs/Util.o ar: .libs/CUError.o: No such file or directory make[6]: *** [Makefile:397: libcunitfmk.la] Error 1 I can reproduce the problem just by trying to build the package. The diffstat of this NMU is 510 files changed, 139791 insertions(+), 3 deletions(-) It is the responsibility of the sponsor (Cc'ed) to verify that sponsored uploads are not broken: https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F
Bug#960715: marked as done (cunit: autopkgtest failure: gcc: not found)
Your message dated Thu, 11 Jun 2020 04:33:34 + with message-id and subject line Bug#960715: fixed in cunit 2.1-3-dfsg-2.1 has caused the Debian Bug report #960715, regarding cunit: autopkgtest failure: gcc: 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.) -- 960715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cunit Version: 2.1-3-dfsg-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? You seem to be missing a test dependency. The release team has announced [1] that failing autopkgtest are now considered RC in testing. Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/c/cunit/5496014/log.gz autopkgtest [18:13:13]: test test.sh: [--- /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 7: gcc: not found /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/autopkgtest_tmp/test: not found /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 7: gcc: not found /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/build.P6n/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.k5r5ej6m/downtmp/autopkgtest_tmp/test: not found autopkgtest [18:13:13]: test test.sh: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cunit Source-Version: 2.1-3-dfsg-2.1 Done: Regis Fernandes Gontijo We believe that the bug you reported is fixed in the latest version of cunit, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Regis Fernandes Gontijo (supplier of updated cunit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jun 2020 04:49:43 + Source: cunit Architecture: source Version: 2.1-3-dfsg-2.1 Distribution: unstable Urgency: medium Maintainer: Azat Khuzhin Changed-By: Regis Fernandes Gontijo Closes: 960715 Changes: cunit (2.1-3-dfsg-2.1) unstable; urgency=medium . * Non-maintainer upload. * debian/tests/: (Closes: #960715) - control: set 'Depends: gcc' because autopkgtest needs to build a binary to run the CI test. - test.sh: fixed gcc build command. Checksums-Sha1: 183eaad94553a254dcb3ea72ca13d1eb6389ee71 2209 cunit_2.1-3-dfsg-2.1.dsc 8fbb8eb7d1cfac76e35f3974c7c71accaf439043 164904 cunit_2.1-3-dfsg-2.1.debian.tar.xz 91f361fb83c69dbd40131dadd6ee8a4a6dec4949 5445 cunit_2.1-3-dfsg-2.1_source.buildinfo Checksums-Sha256: c9adb4e27c2939e22dafcc755bfd0b0da1b80e3488d007eaa5a9230c97d685c3 2209 cunit_2.1-3-dfsg-2.1.dsc 2aa4404e78c32b8c6e522f7e145f57deef991bb70df0839bc10b438789114188 164904 cunit_2.1-3-dfsg-2.1.debian.tar.xz 70cb3b46ec2e414793d336f170f3fe13c0a7391183313f6249459dfe81bee1a2 5445 cunit_2.1-3-dfsg-2.1_source.buildinfo Files: acd40f27ae469519e2610b64a181473c 2209 libs optional cunit_2.1-3-dfsg-2.1.dsc 8fa7b5679369451d575b4a938797aee1 164904 libs optional cunit_2.1-3-dfsg-2.1.debian.tar.xz 2171220ef23733258866ae8b86da00b0 5445 libs optional cunit_2.1-3-dfsg-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7fB8sACgkQ3mO5xwTr 6e/5pQ/+N8utXkii6kVq75k3lWYjuMh+8b2EECr3ZIljIG2/opfzS9qqY84ebSOi /S3bnQv1uSi58nTR1RZ43oFgmhdvZIa8vYAEgybHSsMZS3V5otFhFelnANjgqnEq 8tLhamsDwVK3AGglcCN34CZWXHqaNpVcQkCM5tnuiowh98jbB6rRDB53tks2LwJr 3+eQv5ah6tZWy4LpL1q3tgYBipVw9Ji0DyyXT6FWLtPvHgXGxlKAvGE53/Nizwuj fY40maPgaXYe4x6BQj+aEVAU4bc5LNc+JBmzQCliUZpQXy8Xy8dlgiGaB0QMj94R NLgn2QJfaIxZyS+dCC4Z/sFSrC2zMugaNdtpraoVDcKwGv4acTbuJFAdHWELqNJ7 uLaSa2B/ricdEcXluoMO9VpOnrr4w+QnG37dc9V8WCTCFAnVrOaLF2H2pjSkiIGk d+037O8g55alnQvRhhwKsesmD52qIOBEw5QMy0Aj/qYGwQZmq4RFMBJwsDmD/Gno HQ3OKUuNFvcrazCYu42
Processed: tagging 962641
Processing commands for cont...@bugs.debian.org: > tags 962641 + ftbfs Bug #962641 [src:qgis] qgis: FTBFS with SIP 4.19.23 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: qgis: FTBFS with SIP 4.19.23
Processing control commands: > forwarded -1 https://github.com/qgis/QGIS/issues/37098 Bug #962641 [src:qgis] qgis: FTBFS with SIP 4.19.23 Set Bug forwarded-to-address to 'https://github.com/qgis/QGIS/issues/37098'. > block 960495 by -1 Bug #960495 [release.debian.org] transition: gdal 960495 was blocked by: 953138 960369 960495 was not blocking any bugs. Added blocking bug(s) of 960495: 962641 -- 960495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960495 962641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962641: qgis: FTBFS with SIP 4.19.23
Source: qgis Version: 3.10.5+dfsg-2 Severity: serious Tags: upstream Justification: makes the package in question unusable or mostly so Control: forwarded -1 https://github.com/qgis/QGIS/issues/37098 Control: block 960495 by -1 QGIS FTBFS since the update of sip4 to 4.19.23+dfsg-1: [3799/4686 81%]cd /<>/debian/build/python && /usr/bin/cmake -E echo && /usr/bin/cmake -E touch /<>/debian/build/python/server/sip_serverpart0.cpp /<>/debian/build/python/server/sip_serverpart1.cpp /<>/debian/build/python/server/sip_serverpart2.cpp /<>/debian/build/python/server/sip_serverpart3.cpp && /usr/bin/sip -w -e -x TESTS -x ANDROID -x ARM -x MOBILITY_LOCATION -n sip -t WS_X11 -t Qt_5_12_4 -g -o -a /<>/debian/build/python/qgis.server.api -n sip -y /<>/debian/build/output/python/qgis/_server.pyi -j 4 -c /<>/debian/build/python/server -I /<>/debian/build/python/server -I /usr/share/sip/PyQt5 -I /<>/python /<>/debian/build/python/server/server.sip FAILED: python/server/sip_serverpart0.cpp python/server/sip_serverpart1.cpp python/server/sip_serverpart2.cpp python/server/sip_serverpart3.cpp cd /<>/debian/build/python && /usr/bin/cmake -E echo && /usr/bin/cmake -E touch /<>/debian/build/python/server/sip_serverpart0.cpp /<>/debian/build/python/server/sip_serverpart1.cpp /<>/debian/build/python/server/sip_serverpart2.cpp /<>/debian/build/python/server/sip_serverpart3.cpp && /usr/bin/sip -w -e -x TESTS -x ANDROID -x ARM -x MOBILITY_LOCATION -n sip -t WS_X11 -t Qt_5_12_4 -g -o -a /<>/debian/build/python/qgis.server.api -n sip -y /<>/debian/build/output/python/qgis/_server.pyi -j 4 -c /<>/debian/build/python/server -I /<>/debian/build/python/server -I /usr/share/sip/PyQt5 -I /<>/python /<>/debian/build/python/server/server.sip sip: core/conversions.sip:1440: %MappedType template for this type has already been defined This has been reported upstream in: https://github.com/qgis/QGIS/issues/37098 Hopefully a fix will be available before the next point release on the 19th.
Bug#962630: Acknowledgement (dovecot: FTBFS: test failures on 32-bit ARM)
Initial testing suggests that adding libunwind-dev to build-deps resolves this issue.
Bug#956028: marked as done (wine-development: FTBFS on arm64, armel, armhf)
Your message dated Thu, 11 Jun 2020 02:34:37 + with message-id and subject line Bug#956028: fixed in wine-development 5.5-4 has caused the Debian Bug report #956028, regarding wine-development: FTBFS on arm64, armel, armhf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 956028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wine-development Version: 5.5-3 Severity: serious Hello, the 5.5-3 fixed amd64, but there still is a FTBFS because of install failure on arm* architectures. following a snippet of the build log: make[1]: Leaving directory '/<>' dh_install -a -O--parallel install -d debian/.debhelper/generated/wine-development install -d debian/.debhelper/generated/wine32-development install -d debian/wine64-development//usr/lib/wine-development cp --reflink=auto -a debian/tmp/usr/lib/wine-development/wine64 debian/wine64-development//usr/lib/wine-development/ cp --reflink=auto -a ./debian/tmp/wineserver64 debian/wine64-development/usr/lib/wine-development/ install -d debian/.debhelper/generated/wine64-development install -d debian/.debhelper/generated/wine32-development-preloader install -d debian/wine64-development-preloader//usr/lib/wine-development cp --reflink=auto -a debian/tmp/usr/lib/wine-development/wine64-preloader debian/wine64-development-preloader//usr/lib/wine-development/ install -d debian/.debhelper/generated/wine64-development-preloader install -d debian/.debhelper/generated/wine32-development-tools install -d debian/wine64-development-tools//usr/lib/wine-development cp --reflink=auto -a debian/tmp/usr/lib/wine-development/widl debian/tmp/usr/lib/wine-development/winebuild debian/tmp/usr/lib/wine-development/winecpp debian/tmp/usr/lib/wine-development/winedump debian/tmp/usr/lib/wine-development/wineg\+\+ debian/tmp/usr/lib/wine-development/winegcc debian/tmp/usr/lib/wine-development/winemaker debian/tmp/usr/lib/wine-development/wmc debian/tmp/usr/lib/wine-development/wrc debian/wine64-development-tools//usr/lib/wine-development/ install -d debian/wine64-development-tools/usr/bin cp --reflink=auto -a ./debian/tmp/winegcc-development debian/tmp/usr/lib/wine-development/function_grep.pl debian/wine64-development-tools/usr/bin/ dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.com" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.com dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.dll" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.dll dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.drv" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.drv dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.exe" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.exe dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.acm" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.acm dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.cpl" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.cpl dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.ocx" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.ocx dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.sys" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.sys dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/lib/*/*/*.tlb" (tried in ., debian/tmp) dh_install: warning: libwine-development missing files: debian/tmp/usr/lib/*/*/*.tlb dh_install: error: missing files, aborting install -d debian/.debhelper/generated/wine64-development-tools install -d debian/.debhelper/generated/libwine-development install -d debian/.debhelper/generated/libwine-development-dev make: *** [debian/rules:122: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 --
Processed: gatling: diff for NMU version 0.13-6.1
Processing control commands: > tags 868190 + pending Bug #868190 [gatling] gatling: -u is silently ignored if is a username rather than a numeric user id Added tag(s) pending. -- 868190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
Hi Steve, On Wed, Jun 10, 2020 at 11:39 AM Olek Wojnar wrote: > On Mon, Jun 8, 2020 at 2:03 PM Moritz Mühlenhoff wrote: > >> Has there been any update wrt lightyears/Py3 being moved to the Debian >> Games >> Team? >> > > I haven't heard anything although I'm still willing to sponsor once we > verify that the Python Applications Packaging Team is ok with transferring > this package to the Games Team. > > Any word, Steve? > I've moved the package under the games-team [1]. I was going to give you access to it but I can't find a Salsa account for you. If you don't have an account yet, you can easily create one [2] and let me know your username. I'll then give you access to the repository and you can make all of your changes. Once you're happy with it, I'll review and upload. Let me know if you have any questions! -Olek [1] https://salsa.debian.org/games-team/lightyears [2] https://salsa.debian.org/users/sign_in
Bug#960760: Fixed Bug#960760: tree-puzzle FTBFS on !amd64: test failures
Hi, I've pushed a patch for tree-puzzle to fix #960760. Please review. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960760 https://salsa.debian.org/med-team/tree-puzzle Regards, Pranav ᐧ
Bug#962615: sylfilter: glib error prevent filter working
Hi, On Wed, 10 Jun 2020 20:02:27 +0200 Xavier Brochard wrote: > Sylfilter doesn't work anymore in Sylpheed. > Sylpheed log contains these lines each time sylfilter is launched: > GLib-DEBUG: posix_spawn avoided (fd close requested) > ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127 Which logfile, could you provide a filename, please? >* What led up to the situation? > System update, but user notify me long time after problem start. From which version to version? Could you try to invoke sylpfiter with terminal and get output like below? $ sylfilter -c lspci.txt -d xfilter_bayes_db_init: init database xfilter_bayes_db_init: path: /home/henrich/.sylfilter xfilter_bayes_db_init: making directory: /home/henrich/.sylfilter xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/junk.db xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/clean.db xfilter_bayes_db_init: opening data file: /home/henrich/.sylfilter/status.dat filter-manager.c: xfilter_manager_run: run filter chain exec filter: text-content [content filter] in data type: message/rfc822 exec filter: text-content: status 3: out data type: text/plain exec filter: wordsep [content filter] in data type: text/plain exec filter: wordsep: status 3: out data type: text/plain exec filter: bayes-learn-clean [content filter] in data type: text/plain learning clean message xfilter_update_status: writing status to file xfilter_update_status: done exec filter: bayes-learn-clean: status 4: out data type: text/plain xfilter_bayes_db_init: close database And how about trying to rename ~/.sylfilter directory and create new db temporary? Does it work? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Processed: sword: diff for NMU version 1.8.1+dfsg-8.1
Processing control commands: > tags 962265 + pending Bug #962265 [src:sword] sword silently loses ICU support when built with ICU without icu-config Added tag(s) pending. -- 962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962265: sword: diff for NMU version 1.8.1+dfsg-8.1
Control: tags 962265 + pending Dear maintainer, I've prepared an NMU for sword (versioned as 1.8.1+dfsg-8.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards, Gleisson diff -Nru sword-1.8.1+dfsg/debian/changelog sword-1.8.1+dfsg/debian/changelog --- sword-1.8.1+dfsg/debian/changelog 2018-11-12 14:05:48.0 -0200 +++ sword-1.8.1+dfsg/debian/changelog 2020-06-08 21:39:54.0 -0300 @@ -1,3 +1,11 @@ +sword (1.8.1+dfsg-8.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fixed ICU checking. Thanks to László Böszörményi . +(Closes: #962265) + + -- Gleisson Jesuino Joaquim Cardoso Mon, 08 Jun 2020 21:39:54 -0300 + sword (1.8.1+dfsg-8) unstable; urgency=medium * Breaks/Replaces on libsword11v5 >= 1.8, Closes: #913407 diff -Nru sword-1.8.1+dfsg/debian/patches/series sword-1.8.1+dfsg/debian/patches/series --- sword-1.8.1+dfsg/debian/patches/series 2018-11-12 14:05:48.0 -0200 +++ sword-1.8.1+dfsg/debian/patches/series 2020-06-08 21:39:54.0 -0300 @@ -5,3 +5,4 @@ 0006-powerpc64.patch 0007-gbfwordjs.patch sword_ICU_63.1.patch +sword_ICU_67.1.patch diff -Nru sword-1.8.1+dfsg/debian/patches/sword_ICU_67.1.patch sword-1.8.1+dfsg/debian/patches/sword_ICU_67.1.patch --- sword-1.8.1+dfsg/debian/patches/sword_ICU_67.1.patch1969-12-31 21:00:00.0 -0300 +++ sword-1.8.1+dfsg/debian/patches/sword_ICU_67.1.patch2020-06-08 21:39:54.0 -0300 @@ -0,0 +1,33 @@ +Description: fix ICU checking + Let still search for icu-config but use pkg-config method after that. +Forwarded: no +Author: Laszlo Boszormenyi (GCS) +Last-Update: 2020-06-05 + +--- + +--- sword-1.8.1+dfsg.orig/configure.ac sword-1.8.1+dfsg/configure.ac +@@ -238,9 +238,19 @@ if test x$with_icu = xyes; then + AM_CXXFLAGS="$AM_CXXFLAGS -D_ICU_" + AM_CFLAGS="$AM_CFLAGS -D_ICU_" + else +- echo "*** The icu-config script installed by icu could not be found" +- echo "*** compiling without ICU support" +- with_icu=no ++ PKG_CHECK_MODULES([ICU], [icu-i18n >= 63.1], [found_icu=yes]) ++ if test "$found_icu" = "yes"; then ++PKG_CHECK_MODULES([ICU_IO], [icu-io >= 63.1]) ++ICU_IOLIBS="$ICU_IO_LIBS" ++with_icu=yes ++LIBS="$LIBS $ICU_LIBS $ICU_IOLIBS" ++AM_CXXFLAGS="$AM_CXXFLAGS -D_ICU_" ++AM_CFLAGS="$AM_CFLAGS -D_ICU_" ++ else ++echo "*** The icu-config script installed by icu could not be found" ++echo "*** compiling without ICU support" ++with_icu=no ++ fi + fi + fi +
Bug#925672: efivar: diff for NMU version 37-2.1
On Wed, Jun 10, 2020 at 07:32:36PM +, mario.limoncie...@dell.com wrote: > I don't have a concern to this, but would you mind also submitting > it to Salsa and linking back so we can get it into VCS? > I have sent a merge request [1] on Salsa with the changes included on the NMU. I branched it from cf16f73, as there was an unreleased debian/changelog entry on a newer commit. [1] https://salsa.debian.org/efi-team/efivar/-/merge_requests/2
Bug#962630: dovecot: FTBFS: test failures on 32-bit ARM
Package: src:dovecot
Version: 1:2.3.10.1+dfsg1-1
Severity: serious
Justification: FTBFS on armel and armhf
Tags: sid
Dovecot currently fails to to build on 32-bit arm architectures.
The failure is in the upstream test suite, with the following output:
test-backtrace.c:19: Assert failed: backtrace_append(bt) == 0
test-backtrace.c:21: Assert failed: strstr(str_c(bt), "main") != NULL
backtrace_append . : FAILED
test-backtrace.c:43: Assert failed: backtrace_get(&bt) == 0
/bin/bash: line 1: 15381 Segmentation fault ./$bin
make[5]: *** [Makefile:3409: check-local] Error 1
make[5]: Leaving directory '/<>/src/lib'
make[4]: *** [Makefile:2796: check-am] Error 2
make[4]: Leaving directory '/<>/src/lib'
make[3]: *** [Makefile:2798: check] Error 2
make[3]: Leaving directory '/<>/src/lib'
make[2]: *** [Makefile:563: check-recursive] Error 1
make[2]: Leaving directory '/<>/src'
make[1]: *** [Makefile:681: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:79: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
The specific failing test is:
static void test_backtrace_get(void)
{
test_begin("backtrace_get");
const char *bt = NULL;
#if (defined(HAVE_LIBUNWIND))
test_assert(backtrace_get(&bt) == 0);
/* Check that there's a usable function in the backtrace.
Note that this function may be inlined, so don't check for
test_backtrace_get() */
test_assert(strstr(bt, "test_backtrace") != NULL);
/* make sure the backtrace_get is not */
test_assert(strstr(bt, " backtrace_get") == NULL);
#elif (defined(HAVE_BACKTRACE_SYMBOLS) && defined(HAVE_EXECINFO_H)) || \
(defined(HAVE_WALKCONTEXT) && defined(HAVE_UCONTEXT_H))
test_assert(backtrace_get(&bt) == 0);
/* it should have some kind of main in it */
test_assert(strstr(bt, "main") != NULL);
#else
/* should not work in this context */
test_assert(backtrace_get(&bt) == -1);
#endif
test_end();
}
The assertion failure and segfault happen in the second conditional
preprocessor block. Do we execute the first block on systems where this
passes? I wonder if backtrace_get() works at all in the second case?
Bug#962620: marked as done (stress-ng: flaky arm64 autopkgtest on ci.debian.net: bash: fork: retry: Resource temporarily unavailable)
Your message dated Wed, 10 Jun 2020 22:35:00 + with message-id and subject line Bug#962620: fixed in stress-ng 0.11.13-1 has caused the Debian Bug report #962620, regarding stress-ng: flaky arm64 autopkgtest on ci.debian.net: bash: fork: retry: Resource temporarily unavailable 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.) -- 962620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stress-ng Version: 0.11.01-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of stress-ng turned up a couple of times on our list of unfinished tests on the ci.debian.net arm64 infrastructure. I looked into the history of your autopkgtest and it fails regularly on arm64 [1][2]. Looking at the purpose of this package, is it possible that it's a bit too aggressive for the workers of ci.debian.net? Especially if you consider that we run several autopkgtest instances in parallel on the same host? Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Furthermore, I have the (not further substantiated) impression it's impacting our ci service. I copied the output at the bottom of this report. Not all the failing tests [1][2] that I inspected fail at the same position. Please do get in touch if we need to dive into this together. Paul [1] https://ci.debian.net/packages/s/stress-ng/unstable/arm64/ [2] https://ci.debian.net/packages/s/stress-ng/testing/arm64/ https://ci.debian.net/data/autopkgtest/testing/arm64/s/stress-ng/5493119/log.gz daemon at Fri May 15 13:24:41 UTC 2020 stress-ng: 13:24:41.91 debug: [8318] 32 processors online, 32 processors configured stress-ng: 13:24:41.91 info: [8318] dispatching hogs: 4 daemon stress-ng: 13:24:41.91 debug: [8318] cache allocate: using defaults, can't determine cache details from sysfs stress-ng: 13:24:41.91 debug: [8318] cache allocate: default cache size: 2048K stress-ng: 13:24:41.91 debug: [8318] starting stressors stress-ng: 13:24:41.91 debug: [8319] stress-ng-daemon: started [8319] (instance 0) stress-ng: 13:24:41.91 debug: [8318] 4 stressors spawned stress-ng: 13:24:41.91 debug: [8320] stress-ng-daemon: started [8320] (instance 1) stress-ng: 13:24:41.91 debug: [8322] stress-ng-daemon: started [8322] (instance 3) stress-ng: 13:24:41.91 debug: [8321] stress-ng-daemon: started [8321] (instance 2) stress-ng: 13:24:42.91 debug: [8319] stress-ng-daemon: exited [8319] (instance 0) stress-ng: 13:24:42.91 debug: [8320] stress-ng-daemon: exited [8320] (instance 1) stress-ng: 13:24:42.91 debug: [8322] stress-ng-daemon: exited [8322] (instance 3) stress-ng: 13:24:42.91 debug: [8318] process [8319] terminated stress-ng: 13:24:42.91 debug: [8318] process [8320] terminated stress-ng: 13:24:42.91 debug: [8321] stress-ng-daemon: exited [8321] (instance 2) stress-ng: 13:24:42.91 debug: [8318] process [8321] terminated stress-ng: 13:24:42.91 debug: [8318] process [8322] terminated stress-ng: 13:24:42.91 info: [8318] successful run completed in 1.00s daemon PASSED /tmp/autopkgtest-lxc.aq8hcycy/downtmp/build.0Fb/src/debian/tests/fast-test-all: 58: Cannot fork bash: fork: retry: Resource temporarily unavailable autopkgtest [13:24:46]: test fast-test-all: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: stress-ng Source-Version: 0.11.13-1 Done: Colin King We believe that the bug you reported is fixed in the latest version of stress-ng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin King (supplier of updated stress-ng 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, 10 Jun 2020 23:55:23 +0100 Source: stress-ng Architecture: source Versio
Processed: notfound 962616 in 2.82.2-2, found 962616 in 2.28.2-2, tagging 962201
Processing commands for cont...@bugs.debian.org:
> notfound 962616 2.82.2-2
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
The source 'webkit2gtk' and version '2.82.2-2' do not appear to match any
binary packages
No longer marked as found in versions webkit2gtk/2.82.2-2.
> found 962616 2.28.2-2
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
Marked as found in versions webkit2gtk/2.28.2-2.
> tags 962201 + sid bullseye
Bug #962201 {Done: Samuel Thibault } [src:natbraille]
natbraille: depends on dummy transitional package ttf-dejavu-core
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
962201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962201
962616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: mlpy: diff for NMU version 3.5.0+ds-1.1
Processing control commands: > tags 956019 + patch Bug #956019 [mlpy] mlpy: needs a source-only upload Added tag(s) patch. > tags 956019 + pending Bug #956019 [mlpy] mlpy: needs a source-only upload Added tag(s) pending. -- 956019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959437: marked as done (FTBFS with Boost 1.71)
Your message dated Wed, 10 Jun 2020 22:05:18 +
with message-id
and subject line Bug#959437: fixed in sslsniff 0.8-8.1
has caused the Debian Bug report #959437,
regarding FTBFS with Boost 1.71
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.)
--
959437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sslsniff
Version: 0.8-8
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Dear Maintainer,
your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:
deb https://people.debian.org/~gio/reprepro gio main
This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.
More specifically, your package fails building because it uses some
retired API from Boost.Asio. The attached patch should fix the bug.
Thanks and all the best, Giovanni.
--
Giovanni Mascellani
Postdoc researcher - Université Libre de Bruxelles
From a53724afc0bb86f3551f981e386576eb060d8c78 Mon Sep 17 00:00:00 2001
From: Giovanni Mascellani
Date: Sat, 2 May 2020 11:25:41 +0200
Subject: [PATCH] Fix FTBFS with Boost 1.71.
---
debian/changelog | 7 +
.../patches/Fix-FTBFS-with-Boost-1.71.patch | 181 ++
debian/patches/series | 1 +
3 files changed, 189 insertions(+)
create mode 100644 debian/patches/Fix-FTBFS-with-Boost-1.71.patch
diff --git a/debian/changelog b/debian/changelog
index 123d278..196c6b4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sslsniff (0.8-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with Boost 1.71.
+
+ -- Giovanni Mascellani Sat, 02 May 2020 11:25:51 +0200
+
sslsniff (0.8-8) unstable; urgency=medium
* Fix build with wl,asneeded (Closes: #849695)
diff --git a/debian/patches/Fix-FTBFS-with-Boost-1.71.patch b/debian/patches/Fix-FTBFS-with-Boost-1.71.patch
new file mode 100644
index 000..80cba0d
--- /dev/null
+++ b/debian/patches/Fix-FTBFS-with-Boost-1.71.patch
@@ -0,0 +1,181 @@
+From: Giovanni Mascellani
+Date: Sat, 2 May 2020 11:24:55 +0200
+Subject: Fix FTBFS with Boost 1.71.
+
+---
+ RawBridge.hpp | 21 +
+ SSLConnectionManager.cpp | 6 +++---
+ http/HttpBridge.hpp| 25 +
+ http/HttpConnectionManager.cpp | 4 ++--
+ 4 files changed, 51 insertions(+), 5 deletions(-)
+
+diff --git a/RawBridge.hpp b/RawBridge.hpp
+index 9206faa..7a1255e 100644
+--- a/RawBridge.hpp
b/RawBridge.hpp
+@@ -36,6 +36,16 @@ private:
+ ip::tcp::socket serverSocket;
+ ip::tcp::endpoint destination;
+
++#if BOOST_VERSION >= 107000
++ const boost::asio::executor &executor;
++
++ RawBridge(boost::shared_ptr clientSocket,
++ ip::tcp::endpoint& destination,
++ const boost::asio::executor & executor) :
++clientSocket(clientSocket), serverSocket(executor),
++executor(executor), destination(destination), closed(0)
++ {}
++#else
+ boost::asio::io_service &io_service;
+
+ RawBridge(boost::shared_ptr clientSocket,
+@@ -44,6 +54,7 @@ private:
+ clientSocket(clientSocket), serverSocket(io_service),
+ io_service(io_service), destination(destination), closed(0)
+ {}
++#endif
+
+ void handleConnect(Bridge::ptr bridge, const boost::system::error_code &error) {
+ if (!error) Bridge::shuttle(&(*clientSocket), &serverSocket);
+@@ -55,6 +66,15 @@ protected:
+
+ public:
+
++#if BOOST_VERSION >= 107000
++ static ptr create(boost::shared_ptr clientSocket,
++ ip::tcp::endpoint& destination,
++ const boost::asio::executor & executor)
++
++ {
++return ptr(new RawBridge(clientSocket, destination, executor));
++ }
++#else
+ static ptr create(boost::shared_ptr clientSocket,
+ ip::tcp::endpoint& destination,
+ boost::asio::io_service & io_service)
+@@ -62,6 +82,7 @@ public:
+ {
+ return ptr(new RawBridge(clientSocket, destination, io_service));
+ }
++#endif
+
+ virtual ip::tcp::socket& getClientSocket() {
+ return *clientSocket;
+diff --git a/SSLConnectionManager.cpp b/SSLConnectionManager.cpp
+index 9beed10..6087f65 100644
+--- a/SSLConnectionManager.cpp
b/SSLConnectionManager.cpp
+@@ -44,7 +44,7 @@ SSLConnectionManager::SSLConnectionManager(io_service &io_service,
+ }
+
Bug#955579: marked as done (FTBFS with Boost 1.71)
Your message dated Wed, 10 Jun 2020 22:04:39 + with message-id and subject line Bug#955579: fixed in sinfo 0.0.48-2.1 has caused the Debian Bug report #955579, regarding FTBFS with Boost 1.71 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.) -- 955579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sinfo Version: 0.0.48-2 Severity: wishlist Tags: patch User: team+bo...@tracker.debian.org Usertags: boost1.71 Dear Maintainer, your package fails to build with boost1.71. If you want to attempt the build yourself, an updated version of boost-defaults which brings in boost1.71 dependencies can be found adding this line to your sources.list file: deb https://people.debian.org/~gio/reprepro gio main This bug has severity whishlist for the moment, but it will raised to RC as soon as version 1.71 of Boost is promoted to default. More specifically, your package fails building because it depends on package libboost-signals-dev, which is going to disappear. The attached patch should fix the bug. Thanks and all the best, Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles From 8c2c9f8e5ad42007996dc8d600ba51e0e26dfc16 Mon Sep 17 00:00:00 2001 From: Giovanni Mascellani Date: Thu, 2 Apr 2020 21:00:25 +0200 Subject: [PATCH] Fix FTBFS with Boost 1.71. --- debian/changelog | 7 +++ debian/control | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index a79d5c9..a77f3c5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +sinfo (0.0.48-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove dependency on libboost-signals-dev, which was removed. + + -- Giovanni Mascellani Thu, 02 Apr 2020 21:00:07 +0200 + sinfo (0.0.48-2) unstable; urgency=medium * [38b4d44] pt_BR debconf template translation (Closes: #844667) diff --git a/debian/control b/debian/control index 539f799..ca7c097 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Section: net Priority: optional Maintainer: Jürgen Rinas Uploaders: Gaudenz Steinlin -Build-Depends: debhelper (>= 9.20160709~), autotools-dev, libncurses5-dev, libboost-dev, libboost-signals-dev, libboost-regex-dev, libboost-system-dev, po-debconf, groff +Build-Depends: debhelper (>= 9.20160709~), autotools-dev, libncurses5-dev, libboost-dev, libboost-regex-dev, libboost-system-dev, po-debconf, groff Standards-Version: 4.2.1 Vcs-Git: https://salsa.debian.org/debian/sinfo.git Vcs-Browser: https://salsa.debian.org/debian/sinfo -- 2.26.0 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sinfo Source-Version: 0.0.48-2.1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of sinfo, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated sinfo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jun 2020 23:29:50 +0200 Source: sinfo Architecture: source Version: 0.0.48-2.1 Distribution: unstable Urgency: medium Maintainer: Jürgen Rinas Changed-By: Sebastian Ramacher Closes: 955579 Changes: sinfo (0.0.48-2.1) unstable; urgency=medium . * Non-maintainer upload. . [ Giovanni Mascellani ] * Remove dependency on libboost-signals-dev, which was removed. (Closes: #955579) Checksums-Sha1: da6100b8f4c130e511c00b2ad2df95ea6daf111b 1973 sinfo_0.0.48-2.1.dsc 78e42bf44f40e29d8a7699183982e074c2e2a463 17012 sinfo_0.0.48-2.1.debian.tar.xz Checksums-Sha256: 7ace60d62dd72ca4953845b8e9ad96577c6176273ae780e60bd5ff19b72afb0a 1973 sinfo_0.0.48-2.1.dsc a9353a195c1a5636071c8633a0b6ab7789c0bf7121788029f36cbb4c4cf07b28 17012 sinfo_0.0.48-2.1.debian.tar.xz Files: 1fc52a3036680eaf6e73b40284ebf28b 1973 net optional sinfo_0.0.48-2.1.dsc a8c90df599d5b98c67b445fd3324857e 17012 net optional sinfo_0.0.48-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sU
Bug#962619: marked as done (libsrt-gnutls-dev: pkg-config in wrong multiarch path (i686 not i386))
Your message dated Wed, 10 Jun 2020 21:35:20 + with message-id and subject line Bug#962619: fixed in srt 1.4.1-3 has caused the Debian Bug report #962619, regarding libsrt-gnutls-dev: pkg-config in wrong multiarch path (i686 not i386) 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.) -- 962619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsrt-gnutls-dev Version: 1.4.1-2 Severity: serious Justification: Policy 9.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libsrt-gnutls-dev on i386 provide librares below /usr/lib/i386-linux-gnu but pkgconfig files wrongly below /usr/lib/i686-linux-gnu - leading to failure linking from other packages. See https://packages.debian.org/sid/i386/libsrt-gnutls-dev/filelist for the wrong paths, and https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=i386&ver=7%3A4.2.2-3&stamp=1591806471&raw=0 for an example of a failed build caused by this issue. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7hLIEACgkQLHwxRsGg ASHPaxAAnVHcql5W1WvtZ7MIrgyNElDB09xa9g2Lan2ZAC35amrK7JoHTCDYeiXo g7BfB7wjwRZ3U1r8dzqrz2lawHEn9maUydnyZHK8KuLCl9ga+B4Y8xjBiTZ8BgIL Bjyo7f8MYT0nEEner5tDYdw4RauuOPIcANwbdJX7veNsWLOwmsewdV63lDWfMK1U Pztj8R6049McuvRlbCr34prdEgJYHM5vqt4YIPXHEx6QO/AXyjKF8tQ6xij9HdLb B0irPrifsjg8nVRYKPVCIWCgZELjCV05mnvvSrkg656zvk8UTUGjqASqLVriV4nV Y208DWa3yczrs/vYFfbGvu3jEpdbfaNM6+/nItiRG/EcaiyaQZcMRGZYid5oZB7q uAfF+GNk2mOcUHVe6PbZLwqFLuBghEv0ZwuinnEtJ8VJoLkT+gMFq+QaTvkJpZzW ebK+/yyfbfL3RLIzVxg2r6bjHdVb+2difCOx+myV/OLoskjn4JQ1a1atWWdajomf 42zlkIBiQKjV5h3n/nXifsxSaic/I5qTxUVnW+/5G7RvE/ZlKs5lHDA3UaHnYx6G zPkma6VZiTkJ9m9njrrvPWCKw1OLtBo485VGL4YmaafVsQVER0ZszMesio/tHnkv uPGrYjLAkW10UIv4EVJu7tjP3UH0Ayrezsjv1WC9EUakc8K7kno= =yiac -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: srt Source-Version: 1.4.1-3 Done: Federico Ceratto We believe that the bug you reported is fixed in the latest version of srt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto (supplier of updated srt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 20:33:17 +0100 Source: srt Binary: libsrt-doc libsrt-gnutls-dev libsrt-openssl-dev libsrt1-gnutls libsrt1-gnutls-dbgsym libsrt1-openssl libsrt1-openssl-dbgsym srt-tools srt-tools-dbgsym Architecture: source all amd64 Version: 1.4.1-3 Distribution: unstable Urgency: medium Maintainer: Federico Ceratto Changed-By: Federico Ceratto Description: libsrt-doc - Secure Reliable Transport UDP streaming library libsrt-gnutls-dev - Secure Reliable Transport UDP streaming library libsrt-openssl-dev - Secure Reliable Transport UDP streaming library libsrt1-gnutls - Secure Reliable Transport UDP streaming library (GnuTLS flavour) libsrt1-openssl - Secure Reliable Transport UDP streaming library (OpenSSL flavour) srt-tools - Secure Reliable Transport UDP streaming library Closes: 962619 Changes: srt (1.4.1-3) unstable; urgency=medium . [ Jonas Smedegaard ] * fix multiarch paths (Closes: #962619) Checksums-Sha1: 10bc0966c00192ef85d945f8ffc2b8809b5a4839 2195 srt_1.4.1-3.dsc 4964851422a7f57c436968ed78e0d464609c8cf0 8792 srt_1.4.1-3.debian.tar.xz efc4fa59c5be7311078d1da4617e7ac3b53c62db 6956 libsrt-doc_1.4.1-3_all.deb f355d8745102271538ca7c2631aa80f985750d1b 268832 libsrt-gnutls-dev_1.4.1-3_amd64.deb 30727ef4e01166064137f4f2184ea81fbba7cf22 267900 libsrt-openssl-dev_1.4.1-3_amd64.deb 67ed4f76087c346a1ddd3564d5116e05e0a7b6ad 2536272 libsrt1-gnutls-dbgsym_1.4.1-3_amd64.deb 39ede25899a83ab13ccc65955ff04b1700175248 237928 libsrt1-gnutls_1.4.1-3_amd64.deb 90b04195a9375fc3dc70f560744352f70e5d60fc 2534208 libsrt1-openssl-dbgsym_1.4.1-3_amd64.deb 52b15f9525060ba1142589066182a1bc88ac9362 238048 libsrt1-openssl_1.4.1-3_amd64.deb 84e7f1a964951d24cdb6a92440d92122f583c871 8847284 srt-tools-dbgsym_1.4.1-3_amd64.deb c8ba7bb9355986fa66bd9d532305f5586c28e83d 480016 srt-tools_1.4.1-3_amd64.deb 16319c1488d59a8abb5613f4ef839046e
Processed: alsa-lib: diff for NMU version 1.2.2-2.2
Processing control commands: > tags 953568 + pending Bug #953568 [alsa-lib] alsa-lib: FTBFS in testing Added tag(s) pending. -- 953568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953568: alsa-lib: diff for NMU version 1.2.2-2.2
Control: tags 953568 + pending Dear maintainer, I've prepared an NMU for alsa-lib (versioned as 1.2.2-2.2) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. diff -Nru alsa-lib-1.2.2/debian/changelog alsa-lib-1.2.2/debian/changelog --- alsa-lib-1.2.2/debian/changelog 2020-03-07 18:21:22.0 + +++ alsa-lib-1.2.2/debian/changelog 2020-06-10 06:26:40.0 + @@ -1,3 +1,11 @@ +alsa-lib (1.2.2-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/python3.8.diff: + - Updated as upstream commit '1654f38', fixed FTBFS. (Closes: #953568) + + -- Francisco Vilmar Cardoso Ruviaro Wed, 10 Jun 2020 06:26:40 + + alsa-lib (1.2.2-2.1) unstable; urgency=medium [ Matthias Klose ] diff -Nru alsa-lib-1.2.2/debian/patches/python3.8.diff alsa-lib-1.2.2/debian/patches/python3.8.diff --- alsa-lib-1.2.2/debian/patches/python3.8.diff2020-03-04 08:23:20.0 + +++ alsa-lib-1.2.2/debian/patches/python3.8.diff2020-06-10 05:49:04.0 + @@ -1,16 +1,21 @@ -# Description: fixes the build with python 3.8 -# Upstream: https://github.com/alsa-project/alsa-lib/issues/33 -# Author: Matthias Klose -Index: b/configure.ac -=== a/configure.ac -+++ b/configure.ac -@@ -423,7 +423,7 @@ if test "$build_python" = "yes" -a "$bui +Description: fixes the build with python 3.8 +Upstream: https://github.com/alsa-project/alsa-lib/issues/33 +Author: Matthias Klose +Bug-Debian: https://bugs.debian.org/953568 +Reviewed-By: Francisco Vilmar Cardoso Ruviaro +Last-Update: 2020-06-10 + +--- alsa-lib-1.2.2.orig/configure.ac alsa-lib-1.2.2/configure.ac +@@ -423,7 +423,10 @@ if test "$build_python" = "yes" -a "$bui pythonlibs0= pythoninc0= if test "$build_python2" != "yes"; then -pythonlibs0=$(python3-config --libs) -+pythonlibs0=$(python3-config --libs --embed) ++pythonlibs0=$(python3-config --libs --embed 2> /dev/null) ++if test -z "$pythonlibs0"; then ++ pythonlibs0=$(python3-config --libs) ++fi pythoninc0=$(python3-config --includes) fi if test -z "$pythonlibs0"; then -- Francisco Vilmar Cardoso Ruviaro 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00
Bug#960418: libkolabxml: diff for NMU version 1.1.6-6.1
Control: tags 960418 + patch Control: tags 960418 + pending Dear maintainer, I've prepared an NMU for libkolabxml (versioned as 1.1.6-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru libkolabxml-1.1.6/debian/changelog libkolabxml-1.1.6/debian/changelog --- libkolabxml-1.1.6/debian/changelog 2019-11-27 22:56:30.0 +0200 +++ libkolabxml-1.1.6/debian/changelog 2020-06-11 00:08:22.0 +0300 @@ -1,3 +1,11 @@ +libkolabxml (1.1.6-6.1) unstable; urgency=high + + * Non-maintainer upload. + * libkolabxml1v5.symbols: Removed symbols that disappeared when +rebuilding with Boost 1.71. (Closes: #960418) + + -- Adrian Bunk Thu, 11 Jun 2020 00:08:22 +0300 + libkolabxml (1.1.6-6) unstable; urgency=medium * Update symbols from buildds for 1.1.6 (Closes: #945420) diff -Nru libkolabxml-1.1.6/debian/libkolabxml1v5.symbols libkolabxml-1.1.6/debian/libkolabxml1v5.symbols --- libkolabxml-1.1.6/debian/libkolabxml1v5.symbols 2019-11-27 16:47:14.0 +0200 +++ libkolabxml-1.1.6/debian/libkolabxml1v5.symbols 2020-06-11 00:08:14.0 +0300 @@ -5927,9 +5927,6 @@ (optional=gccinternal|arch=!armel !armhf)_ZN5boost6system12system_errorD0Ev@Base 1.1.1 (optional=gccinternal|arch=!armel !armhf)_ZN5boost6system12system_errorD1Ev@Base 1.1.1 (optional=gccinternal|arch=!armel !armhf)_ZN5boost6system12system_errorD2Ev@Base 1.1.1 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZN5boost6system14error_category12std_categoryD0Ev@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZN5boost6system14error_category12std_categoryD1Ev@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZN5boost6system14error_category12std_categoryD2Ev@Base 1.1.6 _ZN5boost7numeric16bad_numeric_castD0Ev@Base 1.1.0 _ZN5boost7numeric16bad_numeric_castD1Ev@Base 1.1.0 _ZN5boost7numeric16bad_numeric_castD2Ev@Base 1.1.0 @@ -8308,11 +8305,6 @@ (optional=inline|arch=!armel !armhf)_ZNK5boost6system12system_error4whatEv@Base 1.1.1 (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category10equivalentERKNS0_10error_codeEi@Base 1.1.6 (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category10equivalentEiRKNS0_15error_conditionE@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category12std_category23default_error_conditionEi@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category12std_category4nameEv@Base 1.1.6 - (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category12std_category7messageB5cxx11Ei@Base 1.1.6 (arch=amd64 arm64 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32)_ZNK5boost6system14error_category23default_error_conditionEi@Base 1.1.6 _ZNK5boost7numeric16bad_numeric_cast4whatEv@Base 1.1.0 _ZNK5boost7numeric17negative_overflow4whatEv@Base 1.1.0 @@ -8970,8 +8962,6 @@ (optional|arch=alpha hppa hurd-i386 kfreebsd-amd64 kfreebsd-i386 mips powerpcspe)_ZTIN5boost16exception_detail19error_info_injectorISt16invalid_argumentEE@Base 1.1.0 _ZTIN5boost16exception_detail20error_info_containerE@Base 1.1.0 _ZTIN5boost16exception_detail25error_info_container_implE@Base 1.1.0 - _ZTIN5boost19thread_specific_ptrI16XMLParserWrapperE11delete_dataE@Base 1.1.0 - _ZTIN5boost19thread_specific_ptrIN5Kolab5Utils6GlobalEE11delete_dataE@Base 1.1.0 (arch=!alpha !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !mips !powerpcspe)_ZTIN5boost5uuids13entropy_errorE@Base 1.1.6 (optional=gccinternal|arch=armel armhf)_ZTIN5boost6detail14do_heap_deleteINS_19thread_specific_ptrI16XMLParserWrapperE11delete_dataEEE@Base 1.1.1 (optional=gccinternal|arch=armel armhf)_ZTIN5boost6detail14do_heap_deleteINS_19thread_specific_ptrIN5Kolab5Utils6GlobalEE11delete_dataEEE@Base 1.1.1 @@ -8992,11 +8982,7 @@ _ZTIN5boost6detail17sp_counted_impl_pINS_16exception_detail10clone_implINS2_14bad_exception_E@Base 1.1.0 (arch=!alpha !hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !mips !powerpcspe)_ZTIN5boost6detail17sp_counted_impl_pINS_16exception_detail15error_info_baseEEE@Base 1.1.6 (subst|optional
Processed: libkolabxml: diff for NMU version 1.1.6-6.1
Processing control commands: > tags 960418 + patch Bug #960418 [src:libkolabxml] libkolabxml: FTBFS with boost 1.71 Added tag(s) patch. > tags 960418 + pending Bug #960418 [src:libkolabxml] libkolabxml: FTBFS with boost 1.71 Added tag(s) pending. -- 960418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911832: marked as done (php-symfony-polyfill: ftbfs since php 7.3 is the default)
Your message dated Wed, 10 Jun 2020 21:00:14 + with message-id and subject line Bug#911832: fixed in php-symfony-polyfill 1.17.0-1 has caused the Debian Bug report #911832, regarding php-symfony-polyfill: ftbfs since php 7.3 is the default 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.) -- 911832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-defaults, php-symfony-polyfill Control: found -1 php-defaults/66 Control: found -1 php-symfony-polyfill/1.9.0-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of php-defaults the autopkgtest of php-symfony-polyfill fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing66 php-symfony-polyfill from testing1.9.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of php-defaults to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. 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=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-symfony-polyfill/1204104/log.gz autopkgtest [04:33:54]: test command1: phpunit --bootstrap /usr/share/php/Symfony/Polyfill/autoload.php autopkgtest [04:33:54]: test command1: [--- PHPUnit 7.4.0 by Sebastian Bergmann and contributors. SSS 63 / 836 ( 7%) ... 126 / 836 ( 15%) ... 189 / 836 ( 22%) ... 252 / 836 ( 30%) .FEEF.. 315 / 836 ( 37%) ... 378 / 836 ( 45%) SSS.SSS 441 / 836 ( 52%) ... 504 / 836 ( 60%) ... 567 / 836 ( 67%) ... 630 / 836 ( 75%) ... 693 / 836 ( 82%) ..FEE.. 756 / 836 ( 90%) SSS 819 / 836 ( 97%) . 836 / 836 (100%) Time: 6.08 seconds, Memory: 20.00MB There were 4 errors: 1) Symfony\Polyfill\Tests\Intl\Normalizer\NormalizerTest::testIsNormalized Normalizer::NONE is obsolete with ICU 56 and above and will be removed in later PHP versions /tmp/autopkgtest-lxc.fc3esx1k/downtmp/build.62R/src/tests/Intl/Normalizer/NormalizerTest.php:46 2) Symfony\Polyfill\Tests\Intl\Normalizer\NormalizerTest::testNormalize Normalizer::NONE is obsolete with ICU 56 and above and will be removed in later PHP versions /tmp/autopkgtest-lxc.fc3esx1k/downtmp/build.62R/src/tests/Intl/Normalizer/NormalizerTest.php:67 3) Symfony\Polyfill\Tests\Intl\Normalizer\NormalizerTest::testIsNormalized Polyfills enabled, Normalizer::NONE is obsolete with ICU 56 and above and will be removed in later PHP versions /tmp/autopkgtest-lxc.fc3esx1k/downtmp/build.62R/src/tests/Intl/Normalizer/NormalizerTest.php:46 4) Symfony\Polyfill\Tests\Intl\Normalizer\NormalizerTest::testNormalize Polyfills enabled, Normalizer::NONE is obsolete with ICU 56 and above and will be removed in later PHP versions /tmp/autopkgtest-lxc.fc3esx1k/downtmp/build.62R/src/tests/Intl/Normalizer/NormalizerTest.php:67 -- There were 3 failures: 1) Symfony\Polyfill\Tests\Intl\Normalizer\NormalizerTest::testConstants Failed asserting that two arrays are identical. --- Expected +++ Actual @@ @@ Array &0 ( -'FORM_C' => 16 -'FORM_D' => 4 -'FORM_KC' => 32 -'FORM_KC_CF' => 48 -'FORM_KD
Bug#962253: esys-particle: diff for NMU version 2.3.5+dfsg1-4.1
On Wed, Jun 10, 2020 at 10:39:29PM +0200, Anton Gladky wrote: > Hello Adrian, Hi Anton, > thanks a lot for the patch and NMU. > > I am preparing a new upload of esys-particle and I will integrate your > changes. > Could you please then cancel yout upload to prevent the race condition? done. > Thanks > > Anton Thanks Adrian
Bug#962253: esys-particle: diff for NMU version 2.3.5+dfsg1-4.1
Hello Adrian, thanks a lot for the patch and NMU. I am preparing a new upload of esys-particle and I will integrate your changes. Could you please then cancel yout upload to prevent the race condition? Thanks Anton Am Mi., 10. Juni 2020 um 15:09 Uhr schrieb Adrian Bunk : > > Control: tags 962253 + patch > Control: tags 962253 + pending > > Dear maintainer, > > I've prepared an NMU for esys-particle (versioned as 2.3.5+dfsg1-4.1) > and uploaded it to DELAYED/2. Please feel free to tell me if I should > cancel it. > > cu > Adrian > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#962624: libsrt1-openssl: missing Breaks+Replaces
Package: libsrt1-openssl Version: 1.4.1-2 Severity: serious When installing libsrt1-openssl if libsrt1 is already installed: Preparing to unpack .../libsrt1-openssl_1.4.1-2_amd64.deb ... Unpacking libsrt1-openssl:amd64 (1.4.1-2) ... dpkg: error processing archive /var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libsrt.so.1.4.1', which is also in package libsrt1:amd64 1.4.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libsrt-openssl-dev:amd64. Preparing to unpack .../libsrt-openssl-dev_1.4.1-2_amd64.deb ... Same issue for libsrt-openssl-dev if libsrt-dev is already installed: Unpacking libsrt-openssl-dev:amd64 (1.4.1-2) ... dpkg: error processing archive /var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb (--unpack): trying to overwrite '/usr/include/srt/logging_api.h', which is also in package libsrt-dev:amd64 1.4.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsrt1-openssl_1.4.1-2_amd64.deb /var/cache/apt/archives/libsrt-openssl-dev_1.4.1-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#961457: marked as done (idle3-tools: autopkgtest regression: idle3ctl: command not found)
Your message dated Wed, 10 Jun 2020 20:35:09 + with message-id and subject line Bug#961457: fixed in idle3-tools 0.9.1-5 has caused the Debian Bug report #961457, regarding idle3-tools: autopkgtest regression: idle3ctl: command 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.) -- 961457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: idle3-tools Version: 0.9.1-4 X-Debbugs-CC: debian...@lists.debian.org, leandrora...@debxp.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of idle3-tools the autopkgtest of idle3-tools fails in testing when that autopkgtest is run with the binary packages of idle3-tools from unstable. It passes when run with only packages from testing. In tabular form: passfail idle3-toolsfrom testing0.9.1-4 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that either you need the needs-root restriction or need to provide the full path to /usr/sbin/idle3ctl. Without needs-root, the test is run as a regular user. Please also mark this test as superficial. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=idle3-tools https://ci.debian.net/data/autopkgtest/testing/amd64/i/idle3-tools/5507695/log.gz autopkgtest [03:18:58]: test command1: idle3ctl -V | grep idle autopkgtest [03:18:58]: test command1: [--- bash: idle3ctl: command not found autopkgtest [03:18:58]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: idle3-tools Source-Version: 0.9.1-5 Done: Fabio Augusto De Muzio Tobich We believe that the bug you reported is fixed in the latest version of idle3-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Augusto De Muzio Tobich (supplier of updated idle3-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 15:18:58 -0300 Source: idle3-tools Architecture: source Version: 0.9.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Fabio Augusto De Muzio Tobich Closes: 961457 Changes: idle3-tools (0.9.1-5) unstable; urgency=medium . * QA upload. * debian/tests/control: adjusted to run CI tests as regular user and marked as superficial. Thanks to Paul Gevers. (Closes: #961457) Checksums-Sha1: b67cb0d2df157207ff9d40f47f6bf9beef3af066 1772 idle3-tools_0.9.1-5.dsc 602e02609298b11a4eb789e8841516519b8f07d1 3088 idle3-tools_0.9.1-5.debian.tar.xz 41d10fc06cc7bacd885105937f4e2268a3d6bc9b 5271 idle3-tools_0.9.1-5_source.buildinfo Checksums-Sha256: 16507b47d52c4643ff098e3810ef628ce182a4feca11f9fd7a69fb36d1574698 1772 idle3-tools_0.9.1-5.dsc 574d3c9433d6afa88cb4f0f8114363c1362f410436cf42b7e4ed762925dfecf9 3088 idle3-tools_0.9.1-5.debian.tar.xz 82312393539d05d5f1032c3d2742b1af620a3307fd19fc73834baee344108de4 5271 idle3-tools_0.9.1-5_source.buildinfo Files: 7609b32852f30e2a6794228bccb60197 1772 admin optional idle3-tools_0.9.1-5.dsc 48e78d5757a85cea42667f057e28e74f 3088 admin optional idle3-tools_0.9.1-5.debian.tar.xz b6dad181017e31f3c75b4ba0425dc742 5271 admin optional idle3-tools_0.9.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7hPvsACgkQ3mO5xwTr 6e+iuA/+OPc7PhWCwdXxnIbIy1ilMyh1cGngdSThMoFBCHR/43fpXBmlHcIhL5rO ER44bquiqQkNRTInMrtpmPqCRRf5ZaLbZYxbkT7yL5E9otQBUORNk/DgrqSRHpdK tAkkMo0jlF9osi8jgWXUOE56T7OC3S/RB1GL2hdpIZU3CHq0/okihj//L6lzwD3l 8kI6Kj8v1JqhVm1i5P1QQanJUZPu10mb1DowFUejDVCctbkrhTMSfGW6GktO6xAm ycB9YHlV9mRNwg0fWRvIBiA0ayX3tmRDhzFpDXniJogK3yC2Xb8
Bug#925672: efivar: diff for NMU version 37-2.1
I don't have a concern to this, but would you mind also submitting it to Salsa and linking back so we can get it into VCS? > -Original Message- > From: David da Silva Polverari > Sent: Wednesday, June 10, 2020 12:06 AM > To: 925...@bugs.debian.org > Subject: Bug#925672: efivar: diff for NMU version 37-2.1 > > > [EXTERNAL EMAIL] > > Control: tags 925672 + pending > > Dear maintainer, > > I've prepared an NMU for efivar (versioned as 37-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer or cancel the NMU. > > Regards, > > David Polverari.
Bug#962623: ImportError: cannot import name 'parse_qs' from 'cgi' (/usr/lib/python3.8/cgi.py)
Package: graphite-web
Version: 1.1.4-5
Severity: grave
Justification: renders package unusable
Hi,
When initially setting up graphite-web I ran the following (per
/usr/share/doc/graphite-carbon/README.Debian):
# su -s /bin/bash _graphite -c 'graphite-manage migrate --run-syncdb'
/usr/lib/python3/dist-packages/graphite/settings.py:334: UserWarning:
SECRET_KEY is set to an unsafe default. This should be set in local_settings.py
for better security
warn('SECRET_KEY is set to an unsafe default. This should be set in
local_settings.py for better security')
Traceback (most recent call last):
(...52 lines of stack trace removed...)
File "/usr/lib/python3/dist-packages/graphite/render/urls.py", line 16, in
from . import views
File "/usr/lib/python3/dist-packages/graphite/render/views.py", line 23, in
from cgi import parse_qs
ImportError: cannot import name 'parse_qs' from 'cgi'
(/usr/lib/python3.8/cgi.py)
This also happens when connecting to the dashboard via HTTP: I installed
libapache2-mod-wsgi-py3, configured the VirtualHost and when connecting I get a
500 on the browser and a similar stack trace on the error log. I didn't check
it all but the last 2 entries are same as above.
When looking into this I found what seems to be a dependency issue. The release
notes for graphite 1.1.6 [1] state "Python 3.8 and Django 2.x support". That
makes me speculate that graphite 1.1.4 doesn't support python 3.8, and is thus
broken on debian testing/sid.
I believe we'd need graphite-web 1.1.6 on debian.
[1] https://graphite.readthedocs.io/en/latest/releases/1_1_6.html
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages graphite-web depends on:
ii adduser 3.118
ii python3 3.8.2-3
ii python3-cairo 1.16.2-3
ii python3-cairocffi 0.9.0-4
ii python3-django 2:2.2.13-1
ii python3-django-tagging 1:0.4.5-3
ii python3-pyparsing 2.4.7-1
ii python3-simplejson 3.17.0-1
ii python3-six 1.15.0-1
ii python3-tz 2020.1-1
ii python3-urllib3 1.25.9-1
ii python3-whisper 1.1.4-2
graphite-web recommends no packages.
Versions of packages graphite-web suggests:
ii graphite-carbon 1.1.4-2
ii libapache2-mod-wsgi-py3 4.6.8-1+b1
pn python3-ldap
pn python3-memcache
pn python3-mysqldb
-- no debconf information
Bug#952431: symfony: FTBFS: test failures with PHP 7.4
Followup-For: Bug #952431 Control: retitle -1 symfony: FTBFS: test failures with PHP 7.4 Control: found -1 5.0.4-1 The same errors (and some more) are happening in experimental, too. Andreas symfony_5.0.4-1.log.gz Description: application/gzip
Processed: Re: symfony: FTBFS: test failures with PHP 7.4
Processing control commands:
> retitle -1 symfony: FTBFS: test failures with PHP 7.4
Bug #952431 {Done: =?utf-8?q?David_Pr=C3=A9vot?= }
[src:symfony] symfony: FTBFS: test failure in sid
Changed Bug title to 'symfony: FTBFS: test failures with PHP 7.4' from
'symfony: FTBFS: test failure in sid'.
> found -1 5.0.4-1
Bug #952431 {Done: =?utf-8?q?David_Pr=C3=A9vot?= }
[src:symfony] symfony: FTBFS: test failures with PHP 7.4
Marked as found in versions symfony/5.0.4-1 and reopened.
--
952431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962616: webkit2gtk: FTBFS on mipsel
On 2020-06-10 20:46:21 +0200, Alberto Garcia wrote: > On Wed, Jun 10, 2020 at 08:08:27PM +0200, Sebastian Ramacher wrote: > > | Exception: gtkdoc-scangobj produced a non-zero return code 250 > > | Command: > > | gtkdoc-scangobj --module=webkit2gtk-4.0 > > | Error output: > > | > > | > > | ninja: build stopped: subcommand failed. > > I've seen this several times, and it seems to happen randomly, and > only on mipsel. I haven't been able to reproduce it in a buildd. > > I suspect it's a bug in gtk-doc-tools ? That could be the case. The last three builds failed with this issue. And so did builds of 2.28.1-1 and 2.28.2-1 before. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#962620: stress-ng: flaky arm64 autopkgtest on ci.debian.net: bash: fork: retry: Resource temporarily unavailable
Source: stress-ng Version: 0.11.01-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of stress-ng turned up a couple of times on our list of unfinished tests on the ci.debian.net arm64 infrastructure. I looked into the history of your autopkgtest and it fails regularly on arm64 [1][2]. Looking at the purpose of this package, is it possible that it's a bit too aggressive for the workers of ci.debian.net? Especially if you consider that we run several autopkgtest instances in parallel on the same host? Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Furthermore, I have the (not further substantiated) impression it's impacting our ci service. I copied the output at the bottom of this report. Not all the failing tests [1][2] that I inspected fail at the same position. Please do get in touch if we need to dive into this together. Paul [1] https://ci.debian.net/packages/s/stress-ng/unstable/arm64/ [2] https://ci.debian.net/packages/s/stress-ng/testing/arm64/ https://ci.debian.net/data/autopkgtest/testing/arm64/s/stress-ng/5493119/log.gz daemon at Fri May 15 13:24:41 UTC 2020 stress-ng: 13:24:41.91 debug: [8318] 32 processors online, 32 processors configured stress-ng: 13:24:41.91 info: [8318] dispatching hogs: 4 daemon stress-ng: 13:24:41.91 debug: [8318] cache allocate: using defaults, can't determine cache details from sysfs stress-ng: 13:24:41.91 debug: [8318] cache allocate: default cache size: 2048K stress-ng: 13:24:41.91 debug: [8318] starting stressors stress-ng: 13:24:41.91 debug: [8319] stress-ng-daemon: started [8319] (instance 0) stress-ng: 13:24:41.91 debug: [8318] 4 stressors spawned stress-ng: 13:24:41.91 debug: [8320] stress-ng-daemon: started [8320] (instance 1) stress-ng: 13:24:41.91 debug: [8322] stress-ng-daemon: started [8322] (instance 3) stress-ng: 13:24:41.91 debug: [8321] stress-ng-daemon: started [8321] (instance 2) stress-ng: 13:24:42.91 debug: [8319] stress-ng-daemon: exited [8319] (instance 0) stress-ng: 13:24:42.91 debug: [8320] stress-ng-daemon: exited [8320] (instance 1) stress-ng: 13:24:42.91 debug: [8322] stress-ng-daemon: exited [8322] (instance 3) stress-ng: 13:24:42.91 debug: [8318] process [8319] terminated stress-ng: 13:24:42.91 debug: [8318] process [8320] terminated stress-ng: 13:24:42.91 debug: [8321] stress-ng-daemon: exited [8321] (instance 2) stress-ng: 13:24:42.91 debug: [8318] process [8321] terminated stress-ng: 13:24:42.91 debug: [8318] process [8322] terminated stress-ng: 13:24:42.91 info: [8318] successful run completed in 1.00s daemon PASSED /tmp/autopkgtest-lxc.aq8hcycy/downtmp/build.0Fb/src/debian/tests/fast-test-all: 58: Cannot fork bash: fork: retry: Resource temporarily unavailable autopkgtest [13:24:46]: test fast-test-all: ---] signature.asc Description: OpenPGP digital signature
Processed: affects 962619
Processing commands for cont...@bugs.debian.org: > affects 962619 ffmpeg Bug #962619 [libsrt-gnutls-dev] libsrt-gnutls-dev: pkg-config in wrong multiarch path (i686 not i386) Added indication that 962619 affects ffmpeg > thanks Stopping processing here. Please contact me if you need assistance. -- 962619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi Guillem, Guillem Jover wrote: > > A maybe a bit safer variant would be to call dpkg-checkbuilddeps > > beforehand and filter out build-essential if it appears. That way > > around it should hurt way less to hardcode the package name. > > You can simply use --ignore-builtin-builddeps. :) Argh! It could have been so simple! Thanks! Unfortunately I just uploaded a new equivs version less than a day ago. Will convert this from -d to this anyway with the next upload. Will though probably wait until the current version has been migrated to testing due to the RC bug fix. (Although this is the better fix for that issue.) 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
Bug#962619: libsrt-gnutls-dev: pkg-config in wrong multiarch path (i686 not i386)
Package: libsrt-gnutls-dev Version: 1.4.1-2 Severity: serious Justification: Policy 9.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libsrt-gnutls-dev on i386 provide librares below /usr/lib/i386-linux-gnu but pkgconfig files wrongly below /usr/lib/i686-linux-gnu - leading to failure linking from other packages. See https://packages.debian.org/sid/i386/libsrt-gnutls-dev/filelist for the wrong paths, and https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=i386&ver=7%3A4.2.2-3&stamp=1591806471&raw=0 for an example of a failed build caused by this issue. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7hLIEACgkQLHwxRsGg ASHPaxAAnVHcql5W1WvtZ7MIrgyNElDB09xa9g2Lan2ZAC35amrK7JoHTCDYeiXo g7BfB7wjwRZ3U1r8dzqrz2lawHEn9maUydnyZHK8KuLCl9ga+B4Y8xjBiTZ8BgIL Bjyo7f8MYT0nEEner5tDYdw4RauuOPIcANwbdJX7veNsWLOwmsewdV63lDWfMK1U Pztj8R6049McuvRlbCr34prdEgJYHM5vqt4YIPXHEx6QO/AXyjKF8tQ6xij9HdLb B0irPrifsjg8nVRYKPVCIWCgZELjCV05mnvvSrkg656zvk8UTUGjqASqLVriV4nV Y208DWa3yczrs/vYFfbGvu3jEpdbfaNM6+/nItiRG/EcaiyaQZcMRGZYid5oZB7q uAfF+GNk2mOcUHVe6PbZLwqFLuBghEv0ZwuinnEtJ8VJoLkT+gMFq+QaTvkJpZzW ebK+/yyfbfL3RLIzVxg2r6bjHdVb+2difCOx+myV/OLoskjn4JQ1a1atWWdajomf 42zlkIBiQKjV5h3n/nXifsxSaic/I5qTxUVnW+/5G7RvE/ZlKs5lHDA3UaHnYx6G zPkma6VZiTkJ9m9njrrvPWCKw1OLtBo485VGL4YmaafVsQVER0ZszMesio/tHnkv uPGrYjLAkW10UIv4EVJu7tjP3UH0Ayrezsjv1WC9EUakc8K7kno= =yiac -END PGP SIGNATURE-
Bug#960414: marked as done (gatbcore: FTBFS with boost 1.71)
Your message dated Wed, 10 Jun 2020 18:50:00 + with message-id and subject line Bug#960414: fixed in gatb-core 1.4.2+dfsg-2 has caused the Debian Bug report #960414, regarding gatbcore: FTBFS with boost 1.71 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.) -- 960414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gatb-core Version: 1.4.2+dfsg-1 Severity: important User: team+bo...@tracker.debian.org Usertags: boost1.71 gatb-core fails to build with boost 1.71: | dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below | dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libgatbcore3/DEBIAN/symbols doesn't match completely debian/libgatbcore3.symbols.amd64 | --- debian/libgatbcore3.symbols.amd64 (libgatbcore3_1.4.2+dfsg-1_amd64) | +++ dpkg-gensymbols5eI09d 2020-05-12 11:26:11.679095008 + | @@ -161,8 +161,8 @@ | _ZN19AbstractHeaderCoderD2Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN3dag10dag_vector9push_backEm@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN3dag11rank_vector9add_blockEv@Base 1.4.1+git20190813.a73b6dd+dfsg | - _ZN3dag11rank_vectorC1ERKS0_@Base 1.4.1+git20190813.a73b6dd+dfsg | - _ZN3dag11rank_vectorC2ERKS0_@Base 1.4.1+git20190813.a73b6dd+dfsg | +#MISSING: 1.4.2+dfsg-1# _ZN3dag11rank_vectorC1ERKS0_@Base 1.4.1+git20190813.a73b6dd+dfsg | +#MISSING: 1.4.2+dfsg-1# _ZN3dag11rank_vectorC2ERKS0_@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN3dag11rank_vectorD1Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN3dag11rank_vectorD2Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4Leon10STR_NOQUALE@Base 1.4.1+git20190813.a73b6dd+dfsg | @@ -2373,7 +2373,7 @@ | _ZN4gatb4core5tools11collections4impl21BloomNeighborCoherentINS1_4math8LargeIntILi4D0Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl21BloomNeighborCoherentINS1_4math8LargeIntILi4D1Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE5flushEv@Base 1.4.1+git20190813.a73b6dd+dfsg | - _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE5writeEhS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | +#MISSING: 1.4.2+dfsg-1# _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE5writeEhS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE6insertEPKS9_m@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE6insertERKS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm128EE5CountEE6insertERKSt6vectorIS9_SaIS9_EEm@Base 1.4.1+git20190813.a73b6dd+dfsg | @@ -2387,14 +2387,14 @@ | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm32EE5CountEED0Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm32EE5CountEED1Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE5flushEv@Base 1.4.1+git20190813.a73b6dd+dfsg | - _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE5writeEhS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | +#MISSING: 1.4.2+dfsg-1# _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE5writeEhS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE6insertEPKS9_m@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE6insertERKS9_@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEE6insertERKSt6vectorIS9_SaIS9_EEm@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEED0Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11collections4impl22BagCountCompressedFileINS0_4kmer4impl4KmerILm64EE5CountEED1Ev@Base 1.4.1+git20190813.a73b6dd+dfsg | _ZN4gatb4core5tools11c
Processed: Bug#961380: fixed in guitarix 0.39.0+dfsg1-3.1
Processing control commands: > tags 961380 + patch Bug #961380 [src:guitarix] guitarix: baseline violation on i386 Added tag(s) patch. > tags 961380 + pending Bug #961380 [src:guitarix] guitarix: baseline violation on i386 Added tag(s) pending. -- 961380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961380: fixed in guitarix 0.39.0+dfsg1-3.1
Control: tags 961380 + patch Control: tags 961380 + pending Dear maintainer, I've prepared an NMU for guitarix (versioned as 0.39.0+dfsg1-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. diff -Nru guitarix-0.39.0+dfsg1/debian/changelog guitarix-0.39.0+dfsg1/debian/changelog --- guitarix-0.39.0+dfsg1/debian/changelog 2020-05-21 13:43:50.0 -0300 +++ guitarix-0.39.0+dfsg1/debian/changelog 2020-06-10 08:50:55.0 -0300 @@ -1,3 +1,11 @@ +guitarix (0.39.0+dfsg1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Added --disable-sse parameter to fix port baseline in i386. +Thanks to Adrian Bunk . (Closes: #961380) + + -- Daniel Lenharo de Souza Wed, 10 Jun 2020 08:50:55 -0300 + guitarix (0.39.0+dfsg1-3) unstable; urgency=medium * Fix LV2 types (Closes: #960250) diff -Nru guitarix-0.39.0+dfsg1/debian/rules guitarix-0.39.0+dfsg1/debian/rules --- guitarix-0.39.0+dfsg1/debian/rules 2020-01-21 16:04:58.0 -0300 +++ guitarix-0.39.0+dfsg1/debian/rules 2020-06-09 15:39:39.0 -0300 @@ -16,7 +16,7 @@ --cxxflags="$(shell dpkg-buildflags --get CXXFLAGS) \ $(shell dpkg-buildflags --get CPPFLAGS)" \ --ldflags="$(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed" -v \ - --shared-lib --lib-dev --glade-support --enable-lfs --ladspa + --shared-lib --lib-dev --glade-support --enable-lfs --ladspa --disable-sse override_dh_makeshlibs: dh_makeshlibs -V -- Daniel Lenharo de Souza Curitiba - Brasil signature.asc Description: OpenPGP digital signature
Bug#962616: webkit2gtk: FTBFS on mipsel
On Wed, Jun 10, 2020 at 08:08:27PM +0200, Sebastian Ramacher wrote: > | Exception: gtkdoc-scangobj produced a non-zero return code 250 > | Command: > | gtkdoc-scangobj --module=webkit2gtk-4.0 > | Error output: > | > | > | ninja: build stopped: subcommand failed. I've seen this several times, and it seems to happen randomly, and only on mipsel. I haven't been able to reproduce it in a buildd. I suspect it's a bug in gtk-doc-tools ? Berto
Bug#948281: marked as done ([anytun] FTBFS with boost1.71)
Your message dated Wed, 10 Jun 2020 18:33:55 +
with message-id
and subject line Bug#948281: fixed in anytun 0.3.7-1.2
has caused the Debian Bug report #948281,
regarding [anytun] FTBFS with boost1.71
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.)
--
948281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: anytun
Version: 0.3.7-1.1
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Dear Maintainer,
your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:
deb https://people.debian.org/~gio/reprepro gio main
This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.
More specifically, your package fails building because of some API
changes occurred in Boost.ASIO in Boost 1.70. The attached patch should
fix the FTBFS, but I did not test the resulting executable. Please
ensure that the program works correctly before uploading.
Thanks and all the best, Giovanni.
--
Giovanni Mascellani
Postdoc researcher - Université Libre de Bruxelles
From 66cbdc31563b384fad95ecc6e653973f5c8a2e24 Mon Sep 17 00:00:00 2001
From: Giovanni Mascellani
Date: Mon, 6 Jan 2020 12:25:45 +0100
Subject: [PATCH] Fix build with Boost 1.71.
---
.../0003-Fix-build-with-Boost-1.71.patch | 83 +++
debian/patches/series | 1 +
2 files changed, 84 insertions(+)
create mode 100644 debian/patches/0003-Fix-build-with-Boost-1.71.patch
diff --git a/debian/patches/0003-Fix-build-with-Boost-1.71.patch b/debian/patches/0003-Fix-build-with-Boost-1.71.patch
new file mode 100644
index 000..9d1d0df
--- /dev/null
+++ b/debian/patches/0003-Fix-build-with-Boost-1.71.patch
@@ -0,0 +1,83 @@
+From: Giovanni Mascellani
+Date: Mon, 6 Jan 2020 12:25:03 +0100
+Subject: Fix build with Boost 1.71.
+
+get_io_service() was deprecated in favour of get_executor() starting
+from Boost 1.70.
+---
+ src/syncServer.cpp| 4
+ src/syncTcpConnection.cpp | 8
+ src/syncTcpConnection.h | 10 ++
+ 3 files changed, 22 insertions(+)
+
+diff --git a/src/syncServer.cpp b/src/syncServer.cpp
+index 1e6e352..21302c2 100644
+--- a/src/syncServer.cpp
b/src/syncServer.cpp
+@@ -125,7 +125,11 @@ void SyncServer::start_accept()
+ std::list::iterator it = acceptors_.begin();
+ for(; it != acceptors_.end(); ++it) {
+ if(!it->started_) {
++#if BOOST_VERSION >= 107000
++ SyncTcpConnection::pointer new_connection = SyncTcpConnection::create(it->acceptor_->get_executor());
++#else
+ SyncTcpConnection::pointer new_connection = SyncTcpConnection::create(it->acceptor_->get_io_service());
++#endif
+ conns_.push_back(new_connection);
+ it->acceptor_->async_accept(new_connection->socket(),
+ boost::bind(&SyncServer::handle_accept, this, new_connection, boost::asio::placeholders::error, it));
+diff --git a/src/syncTcpConnection.cpp b/src/syncTcpConnection.cpp
+index 027c775..9fe3dba 100644
+--- a/src/syncTcpConnection.cpp
b/src/syncTcpConnection.cpp
+@@ -66,10 +66,18 @@ void SyncTcpConnection::Send(std::string message)
+boost::asio::placeholders::error,
+boost::asio::placeholders::bytes_transferred));
+ }
++
++#if BOOST_VERSION >= 107000
++SyncTcpConnection::SyncTcpConnection(const boost::asio::executor& executor)
++ : socket_(executor)
++{
++}
++#else
+ SyncTcpConnection::SyncTcpConnection(boost::asio::io_service& io_service)
+ : socket_(io_service)
+ {
+ }
++#endif
+
+ void SyncTcpConnection::handle_write(const boost::system::error_code& /*error*/,
+ size_t /*bytes_transferred*/)
+diff --git a/src/syncTcpConnection.h b/src/syncTcpConnection.h
+index a188610..d5f6ef1 100644
+--- a/src/syncTcpConnection.h
b/src/syncTcpConnection.h
+@@ -60,9 +60,15 @@ public:
+ typedef boost::shared_ptr pointer;
+ typedef boost::asio::ip::tcp proto;
+
++#if BOOST_VERSION >= 107000
++ static pointer create(const boost::asio::executor& executor) {
++return pointer(new SyncTcpConnection(executor));
++ };
++#else
+ static pointer create(boost::asio::io_service& io_service) {
+ return pointer(new SyncTcpConnection(io_service));
+ };
Bug#953727: fixed in xdebug 2.9.6+2.8.1+2.5.5-1
Hi Ondřej, On 10-06-2020 09:22, Debian FTP Masters wrote: > xdebug (2.9.6+2.8.1+2.5.5-1) unstable; urgency=medium > . >* New upstream version 2.9.6+2.8.1+2.5.5 >* Add Breaks: php-defaults (<= 69~) to unbreak php-codecoverage ^ is one character too much. The idea was to add a breaks to the version currently in testing. So, either break <= 69 or breaks << 70~. Paul signature.asc Description: OpenPGP digital signature
Processed: retitle 951722 to dovecot should support systemd sd_notify facility, severity of 951722 is normal
Processing commands for cont...@bugs.debian.org: > retitle 951722 dovecot should support systemd sd_notify facility Bug #951722 [src:dovecot] autopkgtest suite flaky on arm64 Bug #953576 [src:dovecot] dovecot: flaky arm64 autopkgtest: debian/tests/usage/00_setup exited with return code 75 Changed Bug title to 'dovecot should support systemd sd_notify facility' from 'autopkgtest suite flaky on arm64'. Changed Bug title to 'dovecot should support systemd sd_notify facility' from 'dovecot: flaky arm64 autopkgtest: debian/tests/usage/00_setup exited with return code 75'. > severity 951722 normal Bug #951722 [src:dovecot] dovecot should support systemd sd_notify facility Bug #953576 [src:dovecot] dovecot should support systemd sd_notify facility Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 951722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951722 953576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962616: webkit2gtk: FTBFS on mipsel
Source: webkit2gtk
Version: 2.82.2-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
The rebuild of webkit2gtk for the icu transition has failed on mipsel:
| 2020-06-10 14:02:24,288:scangobj.py:execute_command:1199:WARNING:Running
scanner failed: -6, command: ./webkit2gtk-4.0-scan
| Traceback (most recent call last):
| File "/<>/Tools/gtkdoc/generate-gtkdoc", line 254, in
| build_gtkdoc_for_wkgtk(arguments)
| File "/<>/Tools/gtkdoc/generate-gtkdoc", line 224, in
build_gtkdoc_for_wkgtk
| saw_warnings = generate_documentation(webkit2_generator)
| File "/<>/Tools/gtkdoc/generate-gtkdoc", line 158, in
generate_documentation
| return generate_doc(generator, arguments.skip_html)
| File "/<>/Tools/gtkdoc/generate-gtkdoc", line 145, in
generate_doc
| generator.generate(not skip_html)
| File "/<>/Tools/gtkdoc/gtkdoc.py", line 147, in generate
| self._run_gtkdoc_scangobj()
| File "/<>/Tools/gtkdoc/gtkdoc.py", line 337, in
_run_gtkdoc_scangobj
| self._run_command(['gtkdoc-scangobj', '--module=%s' % self.module_name],
| File "/<>/Tools/gtkdoc/gtkdoc.py", line 218, in _run_command
| raise Exception(('%s produced a non-zero return code %i\n'
| Exception: gtkdoc-scangobj produced a non-zero return code 250
| Command:
| gtkdoc-scangobj --module=webkit2gtk-4.0
| Error output:
|
|
| ninja: build stopped: subcommand failed.
See
https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk&arch=mipsel&ver=2.28.2-2%2Bb1&stamp=1591797766&raw=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#960963: marked as done (dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967)
Your message dated Wed, 10 Jun 2020 18:03:34 + with message-id and subject line Bug#960963: fixed in dovecot 1:2.3.10.1+dfsg1-1 has caused the Debian Bug report #960963, regarding dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967 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.) -- 960963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dovecot Version: 1:2.3.7.2-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1:2.3.4.1-5+deb10u1 Control: found -1 1:2.3.2-1 Hi, The following vulnerabilities were published for dovecot. CVE-2020-10957[0]: | In Dovecot before 2.3.10.1, unauthenticated sending of malformed | parameters to a NOOP command causes a NULL Pointer Dereference and | crash in submission-login, submission, or lmtp. CVE-2020-10958[1]: | In Dovecot before 2.3.10.1, a crafted SMTP/LMTP message triggers an | unauthenticated use-after-free bug in submission-login, submission, or | lmtp, and can lead to a crash under circumstances involving many | newlines after a command. CVE-2020-10967[2]: | In Dovecot before 2.3.10.1, remote unauthenticated attackers can crash | the lmtp or submission process by sending mail with an empty | localpart. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-10957 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10957 [1] https://security-tracker.debian.org/tracker/CVE-2020-10958 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10958 [2] https://security-tracker.debian.org/tracker/CVE-2020-10967 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10967 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: dovecot Source-Version: 1:2.3.10.1+dfsg1-1 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of dovecot, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated dovecot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 10:41:37 -0700 Source: dovecot Architecture: source Version: 1:2.3.10.1+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Dovecot Maintainers Changed-By: Noah Meyerhans Closes: 960963 Changes: dovecot (1:2.3.10.1+dfsg1-1) unstable; urgency=medium . * New upstream release addresses multiple security issues - CVE-2020-10957 - CVE-2020-10958 - CVE-2020-10967 (Closes: #960963) * Refresh patches * Strip non-DFSG-compliant docs from .orig archives * Incorporate a number of improvements to debian/ metadata contributed by Christian Göttsche * Add no...@debian.org to Uploaders * Work around flakiness in autopkgtest suite * Suppress library-not-linked-against-libc lintian warnings some plugins as false-positives Checksums-Sha1: 9d07f495c47cb7b107a39a8fd7a5ac71655ce34b 3696 dovecot_2.3.10.1+dfsg1-1.dsc af67a770b536f7abbcb8b3fefbf43a46dd771308 874992 dovecot_2.3.10.1+dfsg1.orig-pigeonhole.tar.xz 7bd4f98aec6f2e2d335288d520baff6584173d3a 4290460 dovecot_2.3.10.1+dfsg1.orig.tar.xz 6588a1a600d631b87d8fd681c7567831effec425 57356 dovecot_2.3.10.1+dfsg1-1.debian.tar.xz ab144f345a8812410d1dd6aeddf7a5a1fee4d5cd 8075 dovecot_2.3.10.1+dfsg1-1_source.buildinfo Checksums-Sha256: 5c9667c6aabe92cd34d51249e38fb679aa723131ea61d6e38f8cfe6a19b63a7a 3696 dovecot_2.3.10.1+dfsg1-1.dsc 6db82a650d9579aa729bd7cd1b410942b329c7c6166af67e1f1c0e4ea877ff3f 874992 dovecot_2.3.10.1+dfsg1.orig-pigeonhole.tar.xz 8d07fa6bda091d2865e385cff08cb8bd076bcb459d88c2f84bb6282694a203e7 4290460 dovecot_2.3.10.1+dfsg1.orig.tar.xz 706147dff6edc12637527fdc9066f4929362b0fa37933b166c22248f29871d45 57356 dovecot_2.3.10.1+dfsg1-1.debian.tar.xz 0c5f31073480d7e4bca1e41ed5e4b544603fe4301aa52281840e11
Bug#962615: sylfilter: glib error prevent filter working
Package: sylfilter Version: 0.8-6 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, Sylfilter doesn't work anymore in Sylpheed. Sylpheed log contains these lines each time sylfilter is launched: GLib-DEBUG: posix_spawn avoided (fd close requested) ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127 * What led up to the situation? System update, but user notify me long time after problem start. * What exactly did you do (or not do) that was effective (or ineffective)? Other junk mail filter (Bogofilter) works -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylfilter depends on: ii libc6 2.28-10 ii libglib2.0-0 2.58.3-2+deb10u2 ii libqdbm14 1.8.78-9+b1 ii libsqlite3-0 3.27.2-3 ii libsylfilter0 0.8-6 sylfilter recommends no packages. sylfilter suggests no packages. -- no debconf information
Bug#962606: csound: Build-depends on removed package ttf-dejavu
Control: severity -1 serious On 2020-06-10 13:15:13 -0400, Boyuan Yang wrote: > Source: csound > Severity: grave > Version: 1:6.14.0~dfsg-5 > X-Debbugs-CC: fsate...@debian.org forrest.cah...@gmail.com > > > Dear Debian csound maintainers, > > Your package csound build-depends on package ttf-dejavu, which is a > transitional package that has been removed since the upload of fonts- > dejavu/2.37-2. > > Please adjust the build-dependency information and use package name > fonts-dejavu. Please note that ttf-dejavu and fonts-dejavu provides the > fonts under *different* paths. Please review your package and make sure > that the hardcoded paths (if any) have been updated accordingly. Adjusting the severity accordingly. Build issues are serious. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#962606: csound: Build-depends on removed package ttf-dejavu
Processing control commands: > severity -1 serious Bug #962606 [src:csound] csound: Build-depends on removed package ttf-dejavu Severity set to 'serious' from 'grave' -- 962606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961878: marked as done (libuv1: autopkgtest regression: ./gyp_uv.py: No such file or directory)
Your message dated Wed, 10 Jun 2020 17:48:30 + with message-id and subject line Bug#961878: fixed in libuv1 1.38.0-2 has caused the Debian Bug report #961878, regarding libuv1: autopkgtest regression: ./gyp_uv.py: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libuv1 Version: 1.38.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libuv1 the autopkgtest of libuv1 fails in testing when that autopkgtest is run with the binary packages of libuv1 from unstable. It passes when run with only packages from testing. In tabular form: passfail libuv1 from testing1.38.0-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=libuv1 https://ci.debian.net/data/autopkgtest/testing/amd64/libu/libuv1/5693343/log.gz autopkgtest [04:08:19]: test run-tests: [--- creating makefile for tests /tmp/autopkgtest-lxc.kbt8395b/downtmp/build.cIp/src/debian/tests/run-tests: line 6: ./gyp_uv.py: No such file or directory autopkgtest [04:08:19]: test run-tests: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libuv1 Source-Version: 1.38.0-2 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of libuv1, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated libuv1 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 19:18:03 +0200 Source: libuv1 Architecture: source Version: 1.38.0-2 Distribution: unstable Urgency: medium Maintainer: Dominique Dumont Changed-By: Dominique Dumont Closes: 961878 Changes: libuv1 (1.38.0-2) unstable; urgency=medium . * use cmake instead of autotools to build libuv. As a consequence: * control: add cmake build dep * archive lib is now libuv_a.a * remove all internal symbols from symbol file * rules is updated to not run tests in parallel * remove autopkgtest (Closes: 961878) Checksums-Sha1: c13c2cbb52ca1c14ab934fb1e150c36b2f48606d 1997 libuv1_1.38.0-2.dsc 01b2249c7c7f97ea0dc0de7cfd66488311c7a3b3 22132 libuv1_1.38.0-2.debian.tar.xz ed1bf568e70a277dc61f64a7ce4e7a35a5becb40 6815 libuv1_1.38.0-2_source.buildinfo Checksums-Sha256: c5603ca17be0cabbcd2deaa615eaf407d8c4e3371931c62b5f6614cab2055859 1997 libuv1_1.38.0-2.dsc 42d85bcecfacb12ad37839fbf8e97bb17e49eba6aae1953e98100e240c9ab241 22132 libuv1_1.38.0-2.debian.tar.xz e567320cdf32e50def5e7c8a3ab94e0c7178d5bf28d27df15ce69cf12f65fd79 6815 libuv1_1.38.0-2_source.buildinfo Files: c873769df0b0aa947804b343fe7677c8 1997 libs optional libuv1_1.38.0-2.dsc c9db9e19896b73970328fa10276efb5c 22132 libs optional libuv1_1.38.0-2.debian.tar.xz 339ead5fcd2fad230f7fd1b77d34c928 6815 libs optional libuv1_1.38.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAl7hGAkACgkQwx9P2Umr K2yomQ//TCGPLgOlw7CGXWHcvYG6gL9TW5gAjxVMDilYd6GRfkOCsiQPQUXKzKxG Sj+rfSo7VYp3MJghbBkCYfA6qONi00ED4fpJ5u35qieEu+KyqlGocvypfTjzM9d9 fxtStvR0Sg49sUlKybHut1DBiiQ0eD+pm5oEfY6Q7pFUljyWKmvo3CDPZkQ7Nzex mNiHEXEXM9SECWsLC11CLg+WSlIq4I9bdAELhcErTFVi7m9XdPNP8k4l1oqJpNQN AwIbUOgjFCOToJlwPhz8rLqXlrWfll699P36qPrXKmm00bSBYFFTlB7pVJO+IFi0 U3idPpVE4vCFp/GXBT+VBs3O/nBKkaYu9a5ZVDOvt1+3V3DJhQONmzIOlzMraYoJ Fb14YZU9sK8RdPaKfNKR+nuxh8hqzt4M
Bug#962606: csound: Build-depends on removed package ttf-dejavu
Source: csound Severity: grave Version: 1:6.14.0~dfsg-5 X-Debbugs-CC: fsate...@debian.org forrest.cah...@gmail.com Dear Debian csound maintainers, Your package csound build-depends on package ttf-dejavu, which is a transitional package that has been removed since the upload of fonts- dejavu/2.37-2. Please adjust the build-dependency information and use package name fonts-dejavu. Please note that ttf-dejavu and fonts-dejavu provides the fonts under *different* paths. Please review your package and make sure that the hardcoded paths (if any) have been updated accordingly. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#961878: libuv1: autopkgtest regression: ./gyp_uv.py: No such file or directory
On mardi 9 juin 2020 20:24:38 CEST you wrote: > autopkgtest is meant to test the *installed* version of your package. It > seems to me you meant here that you're testing a just built artifact > instead of the system version. Then autopkgtest doesn't make much sense. Indeed. As libuv is a only a library, I don't think that patching the build system to test an installed library is worth the effort, so I'm going to remove autopkgtest from libuv I'm sorry that I did not realize sooner what was going on inside libuv build system. All the best Dod
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
On Wednesday, June 10, 2020 12:02:48 PM EDT Olek Wojnar wrote: > On Wed, Jun 10, 2020 at 11:48 AM Scott Kitterman > > wrote: > > The only one who ever uploaded the package does not appear to be active in > > Debian any longer, so I would suggest you go ahead. > > Thanks, Scott! (PS Removed said inactive person from this email thread) > > Python Apps Team: If you have no objections, I would like to transfer this > repo [1] from Python Apps Team to Games Team since Steve Cotton wants to > take over maintaining it. Please let me know if you have any concerns! > > -Olek > > [1] https://salsa.debian.org/python-team/applications/lightyears As a practical matter the package is orphaned. Please go ahead. Scott K signature.asc Description: This is a digitally signed message part.
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
On Wed, Jun 10, 2020 at 11:48 AM Scott Kitterman wrote: > > The only one who ever uploaded the package does not appear to be active in > Debian any longer, so I would suggest you go ahead. > Thanks, Scott! (PS Removed said inactive person from this email thread) Python Apps Team: If you have no objections, I would like to transfer this repo [1] from Python Apps Team to Games Team since Steve Cotton wants to take over maintaining it. Please let me know if you have any concerns! -Olek [1] https://salsa.debian.org/python-team/applications/lightyears
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
On Wednesday, June 10, 2020 11:39:31 AM EDT Olek Wojnar wrote: > On Mon, Jun 8, 2020 at 2:03 PM Moritz Mühlenhoff wrote: > > Has there been any update wrt lightyears/Py3 being moved to the Debian > > Games > > Team? > > I haven't heard anything although I'm still willing to sponsor once we > verify that the Python Applications Packaging Team is ok with transferring > this package to the Games Team. > > Any word, Steve? > > -Olek The only one who ever uploaded the package does not appear to be active in Debian any longer, so I would suggest you go ahead. Scott K signature.asc Description: This is a digitally signed message part.
Bug#960899: paramiko: diff for NMU version 2.7.1-1.1
Control: tags 960899 + patch Control: tags 960899 + pending Dear maintainer, I've prepared an NMU for paramiko (versioned as 2.7.1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel the NMU. Regards. Cesar Tulio diff -Nru paramiko-2.7.1/debian/changelog paramiko-2.7.1/debian/changelog --- paramiko-2.7.1/debian/changelog 2020-05-11 22:49:58.0 -0300 +++ paramiko-2.7.1/debian/changelog 2020-06-09 14:04:36.0 -0300 @@ -1,3 +1,11 @@ +paramiko (2.7.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/: added add-configs-dir to +include tests/configs/ directory. (Closes: 960899) + + -- Cesar Tulio Albuquerque de Almeida Tue, 09 Jun 2020 14:04:36 -0300 + paramiko (2.7.1-1) unstable; urgency=medium * Team upload diff -Nru paramiko-2.7.1/debian/patches/add-configs-dir paramiko-2.7.1/debian/patches/add-configs-dir --- paramiko-2.7.1/debian/patches/add-configs-dir 1969-12-31 21:00:00.0 -0300 +++ paramiko-2.7.1/debian/patches/add-configs-dir 2020-06-09 14:04:36.0 -0300 @@ -0,0 +1,524 @@ +Description: add tests/configs/ directory + Since version 2.7.0, tests/configs/ directory is present in upstream source code + but for some reason it is not in Debian package. +Author: Cesar Tulio Albuquerque de Almeida +Origin: https://github.com/paramiko/paramiko +Bug-Debian: https://bugs.debian.org/960899 +Last-Update: 2020-06-09 + +Index: paramiko-2.7.1/tests/configs/basic +=== +--- /dev/null paramiko-2.7.1/tests/configs/basic +@@ -0,0 +1,4 @@ ++CanonicalDomains paramiko.org ++ ++Host www.paramiko.org ++User rando +Index: paramiko-2.7.1/tests/configs/canon +=== +--- /dev/null paramiko-2.7.1/tests/configs/canon +@@ -0,0 +1,8 @@ ++CanonicalizeHostname yes ++CanonicalDomains paramiko.org ++ ++IdentityFile base.key ++ ++Host www.paramiko.org ++User rando ++IdentityFile canonicalized.key +Index: paramiko-2.7.1/tests/configs/canon-always +=== +--- /dev/null paramiko-2.7.1/tests/configs/canon-always +@@ -0,0 +1,5 @@ ++CanonicalDomains paramiko.org ++CanonicalizeHostname always ++ ++Host www.paramiko.org ++User rando +Index: paramiko-2.7.1/tests/configs/canon-ipv4 +=== +--- /dev/null paramiko-2.7.1/tests/configs/canon-ipv4 +@@ -0,0 +1,6 @@ ++CanonicalDomains paramiko.org ++CanonicalizeHostname yes ++AddressFamily inet ++ ++Host www.paramiko.org ++User rando +Index: paramiko-2.7.1/tests/configs/canon-local +=== +--- /dev/null paramiko-2.7.1/tests/configs/canon-local +@@ -0,0 +1,6 @@ ++Host www.paramiko.org ++User rando ++ ++Host www ++CanonicalDomains paramiko.org ++CanonicalizeHostname yes +Index: paramiko-2.7.1/tests/configs/canon-local-always +=== +--- /dev/null paramiko-2.7.1/tests/configs/canon-local-always +@@ -0,0 +1,6 @@ ++Host www.paramiko.org ++User rando ++ ++Host www ++CanonicalDomains paramiko.org ++CanonicalizeHostname always +Index: paramiko-2.7.1/tests/configs/deep-canon +=== +--- /dev/null paramiko-2.7.1/tests/configs/deep-canon +@@ -0,0 +1,11 @@ ++CanonicalizeHostname yes ++CanonicalDomains paramiko.org ++ ++Host www.paramiko.org ++User rando ++ ++Host sub.www.paramiko.org ++User deep ++ ++Host subber.sub.www.paramiko.org ++User deeper +Index: paramiko-2.7.1/tests/configs/deep-canon-maxdots +=== +--- /dev/null paramiko-2.7.1/tests/configs/deep-canon-maxdots +@@ -0,0 +1,12 @@ ++CanonicalizeHostname yes ++CanonicalDomains paramiko.org ++CanonicalizeMaxDots 2 ++ ++Host www.paramiko.org ++User rando ++ ++Host sub.www.paramiko.org ++User deep ++ ++Host subber.sub.www.paramiko.org ++User deeper +Index: paramiko-2.7.1/tests/configs/empty-canon +=== +--- /dev/null paramiko-2.7.1/tests/configs/empty-canon +@@ -0,0 +1,6 @@ ++CanonicalizeHostname yes ++CanonicalDomains ++AddressFamily inet ++ ++Host www.paramiko.org ++User rando +Index: paramiko-2.7.1/tests/configs/fallback-no +=== +--- /dev/null paramiko-2.7.1/tests/configs/fallback-no +@@ -0,0 +1,6 @@ ++CanonicalizeHostname yes ++CanonicalDomains paramiko.org ++CanonicalizeFallbackLocal no ++ ++Host www.paramiko.org ++User rando +Index: paramiko-2.7.1/tests/configs/fallback-yes +=== +--- /dev/null paramiko-2.7.1/tests/configs/fallback-yes
Processed: paramiko: diff for NMU version 2.7.1-1.1
Processing control commands: > tags 960899 + patch Bug #960899 [src:paramiko] paramiko: autopkgtests failures Added tag(s) patch. > tags 960899 + pending Bug #960899 [src:paramiko] paramiko: autopkgtests failures Added tag(s) pending. -- 960899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943450: marked as done (openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental)
Your message dated Wed, 10 Jun 2020 18:39:12 +0300
with message-id <20200610153912.GA30354@localhost>
and subject line Fixed in 2.5.0+cleaned1-1
has caused the Debian Bug report #943450,
regarding openms-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental
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.)
--
943450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openms-doc
Version: 2.4.0-real-1
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]pdfTeX warning (ext4): de
stination with the same identifier (name{page.1}) has been already used, duplic
ate ignored
\relax
l.58
[1] (./tutorial.tex
Underfull \hbox (badness 1) in paragraph at lines 3--4
...
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [doc/CMakeFiles/doc_tutorials.dir/build.make:65:
doc/CMakeFiles/doc_tutorials] Error 1
make[4]: Leaving directory '/<>/debian/build'
make[3]: *** [CMakeFiles/Makefile2:34194: doc/CMakeFiles/doc_tutorials.dir/all]
Error 2
make[3]: Leaving directory '/<>/debian/build'
make[2]: *** [CMakeFiles/Makefile2:34206:
doc/CMakeFiles/doc_tutorials.dir/rule] Error 2
make[2]: Leaving directory '/<>/debian/build'
make[1]: *** [Makefile:11056: doc_tutorials] Error 2
make[1]: Leaving directory '/<>/debian/build'
make: *** [debian/rules:76: build-arch-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
More details can be found in the file
debian/build/doc/OpenMS_tutorial/latex_output/refman.log at the end of the
build.
I attach it.
Paolo
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openms-doc depends on:
ii libjs-jquery 3.3.1~dfsg-3
openms-doc recommends no packages.
Versions of packages openms-doc suggests:
pn libopenms2.4.0
pn topp
-- no debconf information
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2019.10.14) 24 OCT 2019 22:10
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**refman.tex
(./refman.tex
LaTeX2e <2018-12-01>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
)
\c@part=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
)
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
Package: geometry 2018/04/16 v5.8 Page Geometry
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks14
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty
Package: ifpdf 2018/09/07 v3.3 Provides the ifpdf switch
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty
Package: ifvtex 2016/05/16 v1.6 Detect VTeX and its facilities (HO)
Package ifvtex Info: VTeX not detected.
)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
Package: ifxetex 2010/09/12 v0.6 Provides ifxetex conditional
)
\Gm@cnth=\count88
\Gm@cntv=\count89
\c@Gm@tempcnt=\count90
\Gm@bindingoffset=\dimen103
\Gm@wd@mp=\dimen104
\Gm@odd@mp=\dimen105
\Gm@even@mp=\dimen106
\Gm@layoutwidth=\dimen107
\Gm@layoutheight=\dimen108
\Gm@layouthoffset=\dimen109
\Gm@layoutvoffset=\dimen110
\Gm@dimlist=\toks15
)
(/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty
Package: makeidx 2014/09/29 v1.0m Standard LaTeX package
)
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty
Package: fancyhdr 2019/01/31 v3.10 Extensive control of page headers and footer
s
\f@nch@headwidth=\skip43
\f@nch@O@elh=\skip44
\f@nch@O@erh=\skip45
\f@nch@O@olh=\skip46
\f@
Bug#962158: lintian: New very problematic --fail-on default value
Hi Chris, On Tue, Jun 9, 2020 at 11:15 PM Chris Lamb wrote: > > Felix, can you help out? I am not in a position to contribute to this > discussion itself. Well, I wish I could. Guillem makes many alarmist statements, but fails to explain why the change is an undue burden. I also do not know how to engage productively with visceral and absolute responses such as: > Err… > it does not make any sense whatsoever > does not match reality > it does not even make sense within a Debian-centric view > I'll have to very much disagree > you have still not explained what this default change really accomplishes > besides inducing tons of work and breakage > No, they did not. It's amazing how much time and energy Guillem expended on this issue here, on IRC, and in #962157 while dpkg has more open bugs than Lintian. As you know from my past behavior with 'md5sums -z' or the odd contributor on Salsa, I am not opposed to compromise when it brings peace. In the present case, such a compromise could be a value 'none' to disable the default Guillem likes (and which I would like to remove). At the same time, the change was widely released two weeks ago. Simon Quigley from Ubuntu announced it on debian-devel on May 25 [1], while I advertised the change repeatedly on IRC and added a note to DevNews. Some users may have already adapted their systems. [1] https://lists.debian.org/debian-devel/2020/05/msg00239.html Now the best course of action, I think, is to downgrade the severity again to Guillem's original setting of 'important'. That will allow the change to remain in testing. It is, after all, what the testing distribution is for. It would also give me more time to understand the possibly unreasonable burden on Lintian users across Debian and the derivative ecosystem. Simon may receive feedback from Ubuntu, a significant derivative. If there are real problems, I am happy to discuss a solution that reverts the default to Lintian's old setting. Kind regards Felix Lechner
Bug#942622: Would the Games Team adopt Lightyears (pygame based, Python 3 port available)?
On Mon, Jun 8, 2020 at 2:03 PM Moritz Mühlenhoff wrote: > Has there been any update wrt lightyears/Py3 being moved to the Debian > Games > Team? > I haven't heard anything although I'm still willing to sponsor once we verify that the Python Applications Packaging Team is ok with transferring this package to the Games Team. Any word, Steve? -Olek
Bug#958958: libtorrent-rasterbar: diff for NMU version 1.2.5-1.1
Control: tags 958958 + patch Control: tags 958958 + pending Control: tags 962090 + patch Control: tags 962090 + pending Dear maintainer, I've prepared an NMU for libtorrent-rasterbar (versioned as 1.2.5-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru libtorrent-rasterbar-1.2.5/debian/changelog libtorrent-rasterbar-1.2.5/debian/changelog --- libtorrent-rasterbar-1.2.5/debian/changelog 2020-03-10 02:41:03.0 +0200 +++ libtorrent-rasterbar-1.2.5/debian/changelog 2020-06-10 17:37:20.0 +0300 @@ -1,3 +1,12 @@ +libtorrent-rasterbar (1.2.5-1.1) unstable; urgency=high + + * Non-maintainer upload. + * Link against libatomic on armel/mipsel/m68k/powerpc/sh4. +(Closes: #958958) + * Build depend on python, which reopens #936927 but closes: #962090. + + -- Adrian Bunk Wed, 10 Jun 2020 17:37:20 +0300 + libtorrent-rasterbar (1.2.5-1) unstable; urgency=medium * New upstream release (Closes: #952447). diff -Nru libtorrent-rasterbar-1.2.5/debian/control libtorrent-rasterbar-1.2.5/debian/control --- libtorrent-rasterbar-1.2.5/debian/control 2020-03-10 02:30:54.0 +0200 +++ libtorrent-rasterbar-1.2.5/debian/control 2020-06-10 17:37:20.0 +0300 @@ -11,6 +11,7 @@ libboost-random-dev, libssl-dev, pkg-config, + python, python3-docutils, python3-all-dev, python3-all-dbg, diff -Nru libtorrent-rasterbar-1.2.5/debian/rules libtorrent-rasterbar-1.2.5/debian/rules --- libtorrent-rasterbar-1.2.5/debian/rules 2020-03-10 02:39:23.0 +0200 +++ libtorrent-rasterbar-1.2.5/debian/rules 2020-06-10 17:37:16.0 +0300 @@ -5,6 +5,10 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed +ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel m68k powerpc sh4)) + export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed +endif + PYTHON3=$(shell py3versions -vr) ALLPY=$(PYTHON3) $(PYTHON3:%=%-dbg)
Processed: libtorrent-rasterbar: diff for NMU version 1.2.5-1.1
Processing control commands: > tags 958958 + patch Bug #958958 [libtorrent-rasterbar10] libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4 Ignoring request to alter tags of bug #958958 to the same tags previously set > tags 958958 + pending Bug #958958 [libtorrent-rasterbar10] libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4 Ignoring request to alter tags of bug #958958 to the same tags previously set > tags 962090 + patch Bug #962090 [src:libtorrent-rasterbar] libtorrent-rasterbar: Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. Ignoring request to alter tags of bug #962090 to the same tags previously set > tags 962090 + pending Bug #962090 [src:libtorrent-rasterbar] libtorrent-rasterbar: Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. Ignoring request to alter tags of bug #962090 to the same tags previously set -- 958958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958958 962090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libtorrent-rasterbar: diff for NMU version 1.2.5-1.1
Processing control commands: > tags 958958 + patch Bug #958958 [libtorrent-rasterbar10] libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4 Added tag(s) patch. > tags 958958 + pending Bug #958958 [libtorrent-rasterbar10] libtorrent-rasterbar must be linked against libatomic on armel/mipsel/m68k/powerpc/sh4 Added tag(s) pending. > tags 962090 + patch Bug #962090 [src:libtorrent-rasterbar] libtorrent-rasterbar: Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. Added tag(s) patch. > tags 962090 + pending Bug #962090 [src:libtorrent-rasterbar] libtorrent-rasterbar: Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. Added tag(s) pending. -- 958958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958958 962090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960385: marked as done (dds: FTBFS with boost 1.71)
Your message dated Wed, 10 Jun 2020 15:18:44 + with message-id and subject line Bug#960385: fixed in dds 2.9.0-7.1 has caused the Debian Bug report #960385, regarding dds: FTBFS with boost 1.71 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.) -- 960385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dds Version: 2.9.0-7 Severity: important Tags: patch User: team+bo...@tracker.debian.org Usertags: boost1.71 dds fails to build with boost 1.17: | dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below | dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libdds0/DEBIAN/symbols doesn't match completely debian/libdds0.symbols | --- debian/libdds0.symbols (libdds0_2.9.0-7_amd64) | +++ dpkg-gensymbolsVBKipe 2020-05-12 07:09:32.187660112 + | @@ -131,6 +131,11 @@ | _ZGVN5boost16exception_detail37exception_ptr_static_exception_objectINS0_14bad_exception_EE1eE@Base 0 | _ZGVZN5boost16exception_detail27get_static_exception_objectINS0_10bad_alloc_EEENS_13exception_ptrEvE2ep@Base 0 | _ZGVZN5boost16exception_detail27get_static_exception_objectINS0_14bad_exception_EEENS_13exception_ptrEvE2ep@Base 0 | + _ZGVZN5boost6system15system_categoryEvE24system_category_instance@Base 2.9.0-7 | + _ZGVZN5boost6system16generic_categoryEvE25generic_category_instance@Base 2.9.0-7 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE15system_instance@Base 2.9.0-7 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE16generic_instance@Base 2.9.0-7 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE4map_@Base 2.9.0-7 | _ZN10TimerGroup13DifferentiateEv@Base 0 | _ZN10TimerGroup3EndEj@Base 0 | _ZN10TimerGroup5ResetEv@Base 0 | @@ -427,6 +432,7 @@ | _ZTI10TransTable@Base 0 | _ZTI11TransTableL@Base 0 | _ZTI11TransTableS@Base 0 | + _ZTIN5boost10wrapexceptINS_21thread_resource_errorEEE@Base 2.9.0-7 | _ZTIN5boost16exception_detail10bad_alloc_E@Base 0 | _ZTIN5boost16exception_detail10clone_baseE@Base 0 | _ZTIN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0 | @@ -440,12 +446,17 @@ | _ZTIN5boost21thread_resource_errorE@Base 0 | _ZTIN5boost6detail15sp_counted_baseE@Base 0 | _ZTIN5boost6system12system_errorE@Base 0 | - _ZTIN5boost6system14error_category12std_categoryE@Base 0 | +#MISSING: 2.9.0-7# _ZTIN5boost6system14error_category12std_categoryE@Base 0 | + _ZTIN5boost6system14error_categoryE@Base 2.9.0-7 | + _ZTIN5boost6system6detail12std_categoryE@Base 2.9.0-7 | + _ZTIN5boost6system6detail21system_error_categoryE@Base 2.9.0-7 | + _ZTIN5boost6system6detail22generic_error_categoryE@Base 2.9.0-7 | _ZTIN5boost9exceptionE@Base 0 | _ZTS10TransTable@Base 0 | _ZTS11TransTableL@Base 0 | _ZTS11TransTableS@Base 0 | _ZTSN5boost10error_infoINS_27tag_original_exception_typeEPKSt9type_infoEE@Base 0 | + _ZTSN5boost10wrapexceptINS_21thread_resource_errorEEE@Base 2.9.0-7 | _ZTSN5boost16exception_detail10bad_alloc_E@Base 0 | _ZTSN5boost16exception_detail10clone_baseE@Base 0 | _ZTSN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0 | @@ -465,15 +476,29 @@ | _ZTSN5boost6detail17sp_counted_impl_pINS_16exception_detail10clone_implINS2_14bad_exception_E@Base 0 | _ZTSN5boost6detail17sp_counted_impl_pINS_16exception_detail15error_info_baseEEE@Base 0 | _ZTSN5boost6system12system_errorE@Base 0 | - _ZTSN5boost6system14error_category12std_categoryE@Base 0 | +#MISSING: 2.9.0-7# _ZTSN5boost6system14error_category12std_categoryE@Base 0 | + _ZTSN5boost6system14error_categoryE@Base 2.9.0-7 | + _ZTSN5boost6system6detail12std_categoryE@Base 2.9.0-7 | + _ZTSN5boost6system6detail21system_error_categoryE@Base 2.9.0-7 | + _ZTSN5boost6system6detail22generic_error_categoryE@Base 2.9.0-7 | _ZTSN5boost9exceptionE@Base 0 | _ZTSNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFviEjEE@Base 0 | _ZTV11TransTableL@Base 0 | _ZTV11TransTableS@Base 0 | (arch=!armel !armhf)_ZTVN5boost6system12system_errorE@Base 0 | - _ZTVN5boost6system14error_category12std_categoryE@Base 0 | +#MISSING: 2.9.0-7# _ZTVN5boost6system14error_category12std_categoryE@Base 0 | + _ZTVN5boost6system14error_categoryE@Base 2.9.0-7 | + _ZTVN5boost6system6detail12std_categoryE@Base 2.9.0-7 | + _ZTVN5boost6system6detail21system_error_categoryE@Base 2.9.0-7 | + _ZTVN5boost6system6detail22generic_error_categoryE@Base 2.9.0-7 | _ZZN5boost16except
Bug#962196: marked as done (singularity: depends on dummy transitional package ttf-dejavu-core)
Your message dated Wed, 10 Jun 2020 15:07:46 + with message-id and subject line Bug#962196: fixed in singularity 1.0b1-2.1 has caused the Debian Bug report #962196, regarding singularity: depends on dummy transitional package ttf-dejavu-core 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.) -- 962196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: singularity Version: 1.0b1-2 Severity: normal Dear Maintainer, singularity depends on dummy transitional package ttf-dejavu-core, which was removed in fonts-dejavu 2.37-2 (#872809). The dependency name should be updated to fonts-dejavu-core. -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages singularity depends on: ii python3 3.8.2-0ubuntu2 ii python3-numpy1:1.17.4-5ubuntu3 pn python3-polib pn python3-pygame ii ttf-dejavu-core 2.37-1 Versions of packages singularity recommends: pn singularity-music Versions of packages singularity suggests: pn timidity --- End Message --- --- Begin Message --- Source: singularity Source-Version: 1.0b1-2.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of singularity, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated singularity package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 10:38:15 -0400 Source: singularity Architecture: source Version: 1.0b1-2.1 Distribution: unstable Urgency: high Maintainer: Kari Pahula Changed-By: Boyuan Yang Closes: 962196 Changes: singularity (1.0b1-2.1) unstable; urgency=high . * Non-maintainer upload. * debian/control: Replace transitional package ttf-dejavu-core with fonts-dejavu-core in package dependency. (Closes: #962196) * debian/rules: Update DejaVu font link path accordingly. Checksums-Sha1: 6d7930e0b5d93ee0bf71cccb073c9f6f8edcbf73 1797 singularity_1.0b1-2.1.dsc c9f896420f0669c3483f589785ba1c0b7aa8f558 14856 singularity_1.0b1-2.1.debian.tar.xz db1a0278907143118c3b566bba5ffa49b8bf0604 6117 singularity_1.0b1-2.1_amd64.buildinfo Checksums-Sha256: f7abf1c10d71b05a8d6c1385725ec68591855e7b9a18f007f8dfaa97fc8fa0e5 1797 singularity_1.0b1-2.1.dsc 3d0e1d5153372ff3ec0b4af83699f49280c5e0f6e7632dd405892ce2564773b7 14856 singularity_1.0b1-2.1.debian.tar.xz 788fee7cfa798e9c03a093af516013d3fcb32bdcaf4e43c56a6aa204a25bf4d6 6117 singularity_1.0b1-2.1_amd64.buildinfo Files: e266faa418c4e9e4939e8c7e91de47b2 1797 games optional singularity_1.0b1-2.1.dsc 329ad054f17a5f22471362bcbfb0cf18 14856 games optional singularity_1.0b1-2.1.debian.tar.xz 1a6b802c28e3e0b3dc34dc90da6d3ce0 6117 games optional singularity_1.0b1-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl7g8LUACgkQwpPntGGC Ws41fg//UJcT8r6geTd5jqJVbysISzxvNo+fhqWP4W/jv2pgfdmP/1aMad1FpXEP VG6tuXDSwoJ0isj9/7ogkPMwjqPJB6COmwyDa148tqP9FJhlzlUc/fTeI9NpGD8r AHTX5DduNyIRjPEpPS8G6p4A9kikMA/vt0/uVTw0OMoHeIN2pfFj44COsVXP5vgy 0f2RRY4lRY/qACFWh/NgQd2kNwYm0zn8qErsy8ZNMjEIoqMLsaH7f3FjgNjzvnGa /08YkDJwHRyZ83Ogbhq3YDobQxbB2tBIklg4wp/WJSW9jfNLxzgw+LEl1ldT5oxR iXPezz5a+Bantjyep6XBhklJaHsVe9f8hGCraIE7WfdGIP7ccWpf8oNwIPlDSZ9w pyNd77d9Wp9B3CDTYLyWSmYVQUvq3dlAyi3dEIjmUCqVrWuYVv+OkpxeNdK3uv6p RMhTajZURBjHyB7lwUvKkYC2faA5QsvRxBmE2zH2cBxIPFqpMyI6Hqxm8p1GLKDB 2wJQdVk76zL+AVMYmibCD2Rz5q7OGi3bu8t/Ag5mNSQ7LU63Xaqb6YoLYt8N656T 6rwBPiCwmy6uIsCeVUrjWnAE2kTAhAyfr2O90CHYyH7wY8EAnSfqWWSkhPwo95fp TuzjRo0mcDdV1JqNHcj5o269qxT8ciXg41JuYs+gqGii/TK
Bug#960385: dds: diff for NMU version 2.9.0-7.1
Re: Bruno Naibert de Campos > I've prepared an NMU for dds (versioned as 2.9.0-7.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks! I rescheduled it for immediate release. Christoph
Bug#960385: dds: diff for NMU version 2.9.0-7.1
Control: tags 960385 + pending Dear maintainer, I've prepared an NMU for dds (versioned as 2.9.0-7.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru dds-2.9.0/debian/changelog dds-2.9.0/debian/changelog --- dds-2.9.0/debian/changelog 2019-02-25 06:31:36.0 -0300 +++ dds-2.9.0/debian/changelog 2020-06-09 23:23:03.0 -0300 @@ -1,3 +1,11 @@ +dds (2.9.0-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Bumped symbols for boost1.71. Thanks to Dimitri John Ledkov +. (Closes: #960385) + + -- Bruno Naibert de Campos Tue, 09 Jun 2020 23:23:03 -0300 + dds (2.9.0-7) unstable; urgency=medium [ Helmut Grohne ] diff -Nru dds-2.9.0/debian/libdds0.symbols dds-2.9.0/debian/libdds0.symbols --- dds-2.9.0/debian/libdds0.symbols2019-01-30 11:20:40.0 -0200 +++ dds-2.9.0/debian/libdds0.symbols2020-06-09 23:23:03.0 -0300 @@ -131,6 +131,11 @@ _ZGVN5boost16exception_detail37exception_ptr_static_exception_objectINS0_14bad_exception_EE1eE@Base 0 _ZGVZN5boost16exception_detail27get_static_exception_objectINS0_10bad_alloc_EEENS_13exception_ptrEvE2ep@Base 0 _ZGVZN5boost16exception_detail27get_static_exception_objectINS0_14bad_exception_EEENS_13exception_ptrEvE2ep@Base 0 + _ZGVZN5boost6system15system_categoryEvE24system_category_instance@Base 0 + _ZGVZN5boost6system16generic_categoryEvE25generic_category_instance@Base 0 + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE15system_instance@Base 0 + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE16generic_instance@Base 0 + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE4map_@Base 0 _ZN10TimerGroup13DifferentiateEv@Base 0 _ZN10TimerGroup3EndEj@Base 0 _ZN10TimerGroup5ResetEv@Base 0 @@ -427,6 +432,7 @@ _ZTI10TransTable@Base 0 _ZTI11TransTableL@Base 0 _ZTI11TransTableS@Base 0 + _ZTIN5boost10wrapexceptINS_21thread_resource_errorEEE@Base 0 _ZTIN5boost16exception_detail10bad_alloc_E@Base 0 _ZTIN5boost16exception_detail10clone_baseE@Base 0 _ZTIN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0 @@ -440,12 +446,16 @@ _ZTIN5boost21thread_resource_errorE@Base 0 _ZTIN5boost6detail15sp_counted_baseE@Base 0 _ZTIN5boost6system12system_errorE@Base 0 - _ZTIN5boost6system14error_category12std_categoryE@Base 0 + _ZTIN5boost6system14error_categoryE@Base 0 + _ZTIN5boost6system6detail12std_categoryE@Base 0 + _ZTIN5boost6system6detail21system_error_categoryE@Base 0 + _ZTIN5boost6system6detail22generic_error_categoryE@Base 0 _ZTIN5boost9exceptionE@Base 0 _ZTS10TransTable@Base 0 _ZTS11TransTableL@Base 0 _ZTS11TransTableS@Base 0 _ZTSN5boost10error_infoINS_27tag_original_exception_typeEPKSt9type_infoEE@Base 0 + _ZTSN5boost10wrapexceptINS_21thread_resource_errorEEE@Base 0 _ZTSN5boost16exception_detail10bad_alloc_E@Base 0 _ZTSN5boost16exception_detail10clone_baseE@Base 0 _ZTSN5boost16exception_detail10clone_implINS0_10bad_alloc_EEE@Base 0 @@ -465,15 +475,27 @@ _ZTSN5boost6detail17sp_counted_impl_pINS_16exception_detail10clone_implINS2_14bad_exception_E@Base 0 _ZTSN5boost6detail17sp_counted_impl_pINS_16exception_detail15error_info_baseEEE@Base 0 _ZTSN5boost6system12system_errorE@Base 0 - _ZTSN5boost6system14error_category12std_categoryE@Base 0 + _ZTSN5boost6system14error_categoryE@Base 0 + _ZTSN5boost6system6detail12std_categoryE@Base 0 + _ZTSN5boost6system6detail21system_error_categoryE@Base 0 + _ZTSN5boost6system6detail22generic_error_categoryE@Base 0 _ZTSN5boost9exceptionE@Base 0 _ZTSNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFviEjEE@Base 0 _ZTV11TransTableL@Base 0 _ZTV11TransTableS@Base 0 (arch=!armel !armhf)_ZTVN5boost6system12system_errorE@Base 0 - _ZTVN5boost6system14error_category12std_categoryE@Base 0 + _ZTVN5boost6system14error_categoryE@Base 0 + _ZTVN5boost6system6detail12std_categoryE@Base 0 + _ZTVN5boost6system6detail21system_error_categoryE@Base 0 + _ZTVN5boost6system6detail22generic_error_categoryE@Base 0 _ZZN5boost16exception_detail27get_static_exception_objectINS0_10bad_alloc_EEENS_13exception_ptrEvE2ep@Base 0 _ZZN5boost16exception_detail27get_static_exception_objectINS0_14bad_exception_EEENS_13exception_ptrEvE2ep@Base 0 + _ZZN5boost6system15system_categoryEvE24system_category_instance@Base 0 + _ZZN5boost6system16generic_categoryEvE25generic_category_instance@Base 0 + _ZZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE15system_instance@Base 0 + _ZZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE16generic_instance@Base 0 + _ZZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE4map_@Base 0 + _ZZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE7map_mx_@Base 0 _initialized@Base 0 bitMapRank@Base 0 cardHand@Base 0
Processed: dds: diff for NMU version 2.9.0-7.1
Processing control commands: > tags 960385 + pending Bug #960385 [src:dds] dds: FTBFS with boost 1.71 Added tag(s) pending. -- 960385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962575: marked as done (mit-scheme binary-any FTBFS: mit-scheme missing files: /usr/share/man/man1/mit-scheme.1)
Your message dated Wed, 10 Jun 2020 14:42:50 + with message-id and subject line Bug#962575: fixed in mit-scheme 10.1.11-2 has caused the Debian Bug report #962575, regarding mit-scheme binary-any FTBFS: mit-scheme missing files: /usr/share/man/man1/mit-scheme.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mit-scheme Version: 10.1.11-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=mit-scheme&suite=sid ... debian/rules override_dh_install-arch make[1]: Entering directory '/<>' dh_install dh_install: warning: Cannot find (any matches for) "/usr/share/man/man1/mit-scheme.1" (tried in ., debian/tmp) dh_install: warning: mit-scheme missing files: /usr/share/man/man1/mit-scheme.1 dh_install: error: missing files, aborting make[1]: *** [debian/rules:71: override_dh_install-arch] Error 25 --- End Message --- --- Begin Message --- Source: mit-scheme Source-Version: 10.1.11-2 Done: b...@debian.org (Barak A. Pearlmutter) We believe that the bug you reported is fixed in the latest version of mit-scheme, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated mit-scheme package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 14:21:47 +0100 Source: mit-scheme Architecture: source Version: 10.1.11-2 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 962575 Changes: mit-scheme (10.1.11-2) unstable; urgency=medium . * Use dh_link support file *.links instead of override_: * mit-scheme(1) belongs in the binary package, but is auto-installed when the documentation package is built. Instead of laboriously working around this just install manually (closes: #962575) Checksums-Sha1: bc0c97c2254576881744740a81f2bc915eb43a4d 2204 mit-scheme_10.1.11-2.dsc e0361e825780ef1ae852f0d10b930b068d2b8d58 36812 mit-scheme_10.1.11-2.debian.tar.xz 6b1542d2bf6dde2a237c18226bbab1a6c2ff532d 9285 mit-scheme_10.1.11-2_source.buildinfo Checksums-Sha256: 4b44bfefcc0dff14f2327077d9772988dc19a41591022faeadb4fedb9485147e 2204 mit-scheme_10.1.11-2.dsc 447d239704b6d423c0ce706e0c4b1ab765305a33045f4d9e83b0670d83a4faad 36812 mit-scheme_10.1.11-2.debian.tar.xz 808e1affa631ec4930c07150fc431b49a717e0c1112992171668372cc640ddeb 9285 mit-scheme_10.1.11-2_source.buildinfo Files: 22ac69c208fd0b80db887ab4494933ca 2204 lisp optional mit-scheme_10.1.11-2.dsc 1bc3eb208d35630cfe6431fbc4f8c1b7 36812 lisp optional mit-scheme_10.1.11-2.debian.tar.xz d38b6f9315e14dc28485d58222080fb3 9285 lisp optional mit-scheme_10.1.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl7g5sUPHGJhcEBkZWJp YW4ub3JnAAoJEBJbV0deGQ0Y0QgP/RSNOUdDBx9D8DeyP/QMpTJWowCQm1Pzmj4j rkgkWrwUyy4SHSyVrl2M84V4rGp7NoTqBoOCEEnsO6dRaD+H32mRF2iZ5+zYmb8c zK+w+s3XjAbDdLfWv3aow9+7KoS9Dk186zXsZaW6aPBVRyWBv/KYc9kdQ/NoLIMY 28rUDfZrVHb16wNiPO8EotB76SKlnryKUOEt4GkRPVv7uyHTg9K49ImSFwp5sgHN wHbz0OXIaWZfciZqKxC2Vcb/HdzDm9VI62+u01+XL4J4izs2cgLcWFkl+7bFaBxY vik/SwFNsmjNicUg28lJx0y0IwCtTsrVII193o21P+X5FI6EgEbjdC4Jc7ahmAqm HT08NSqxcecp2FAW44IYHYiPx5tt/an4NvIiOqAW1zjXff/RhbqGJI/uVU6OJDgc j9T2PPGW/85mvMrBjYJcM/MMTN3c6gfLREtD67hTmR+vcYepCdjsvuPDrh1NmfAQ DuaEp/2imyuboNx4x6o4+856T6BJt+TmcI+qFCq+KYu1D8KKsYKKdXfyVIEYDHXf 3PHkdbt4eaKuACIPcF1d4vKmLgFyVGh+fCWOuQPzZDjIr/DocIPPP5wE2DK7gNTP 2t9Kz4u7CwTdeaYhTBCBfccH56qUNr4Ass6x2NFUefgczdgzuGA3JlGtz/lG1jkP ZvIOAO+g =ZBKR -END PGP SIGNATURE End Message ---
Processed: rdkit: diff for NMU version 201909.1-4.1
Processing control commands: > tags 954351 + patch Bug #954351 [rdkit] FTBFS with Boost 1.71 Added tag(s) patch. > tags 954351 + pending Bug #954351 [rdkit] FTBFS with Boost 1.71 Added tag(s) pending. -- 954351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954351: rdkit: diff for NMU version 201909.1-4.1
Control: tags 954351 + patch
Control: tags 954351 + pending
Dear maintainer,
I've prepared an NMU for rdkit (versioned as 201909.1-4.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru rdkit-201909.1/debian/changelog rdkit-201909.1/debian/changelog
--- rdkit-201909.1/debian/changelog 2020-05-12 13:21:19.0 +0300
+++ rdkit-201909.1/debian/changelog 2020-06-10 16:07:07.0 +0300
@@ -1,3 +1,10 @@
+rdkit (201909.1-4.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add patch for FTBFS with Boost 1.71. (Closes: #954351)
+
+ -- Adrian Bunk Wed, 10 Jun 2020 16:07:07 +0300
+
rdkit (201909.1-4) unstable; urgency=medium
* Team upload.
diff -Nru rdkit-201909.1/debian/patches/fix-ftbfs.patch rdkit-201909.1/debian/patches/fix-ftbfs.patch
--- rdkit-201909.1/debian/patches/fix-ftbfs.patch 1970-01-01 02:00:00.0 +0200
+++ rdkit-201909.1/debian/patches/fix-ftbfs.patch 2020-06-10 16:06:58.0 +0300
@@ -0,0 +1,307 @@
+Description: fix all of boost detections
+Author: Dimitri John Ledkov
+
+
+--- rdkit-201909.1.orig/CMakeLists.txt
rdkit-201909.1/CMakeLists.txt
+@@ -223,6 +223,12 @@ if(RDK_BUILD_INCHI_SUPPORT)
+ find_package(Inchi)
+ endif(RDK_BUILD_INCHI_SUPPORT)
+
++find_package(Boost 1.56.0 COMPONENTS "python${PYTHON_VERSION_MAJOR}${PYTHON_VERSION_MINOR}" system serialization iostreams regex REQUIRED)
++add_definitions("-DRDKIT_USE_BOOST_REGEX")
++add_definitions("-DBOOST_IOSTREAMS_DYN_LINK")
++ADD_DEFINITIONS("-DRDK_USE_BOOST_IOSTREAMS")
++
++
+ if(RDK_BUILD_PYTHON_WRAPPERS)
+ #---
+ # pull in python:
+@@ -240,29 +246,6 @@ if(RDK_BUILD_PYTHON_WRAPPERS)
+ find_package(NumPy REQUIRED)
+ target_include_directories(rdkit_base INTERFACE ${PYTHON_NUMPY_INCLUDE_PATH})
+
+- if(PYTHON_VERSION_MAJOR EQUAL 3)
+-# Find boost-python3 using name specified as command line option then fall back to commonly used names
+-set(RDK_BOOST_PYTHON3_NAME "python3" CACHE STRING "Name of the boost python3 library. If installed as libboost_python-xxx.so, use python-xxx.")
+-list(APPEND Boost_Python_Names "${RDK_BOOST_PYTHON3_NAME}" "python-py3${PYTHON_VERSION_MINOR}" "python3")
+- endif(PYTHON_VERSION_MAJOR EQUAL 3)
+-
+- # Boost 1.67+ uses a version suffix like "python36" or "python27"
+- list(APPEND Boost_Python_Names "python${PYTHON_VERSION_MAJOR}${PYTHON_VERSION_MINOR}")
+-
+- # Try each potential boost-python name until one works
+- foreach(Boost_Python_Lib ${Boost_Python_Names})
+-find_package(Boost 1.56.0 COMPONENTS "${Boost_Python_Lib}" QUIET)
+-if(Boost_FOUND)
+- break()
+-endif()
+- endforeach()
+-
+- # Finally just try "python" and hope it is a compatible version
+- if(NOT Boost_FOUND)
+-find_package(Boost 1.56.0 COMPONENTS python REQUIRED)
+- endif()
+-
+-
+ if(RDK_INSTALL_INTREE)
+ set(RDKit_PythonDir "${CMAKE_SOURCE_DIR}/rdkit")
+ else(RDK_INSTALL_INTREE)
+@@ -322,8 +305,6 @@ if(RDK_BUILD_PYTHON_WRAPPERS)
+ message("PYTHON Py_ENABLE_SHARED: ${Py_ENABLE_SHARED}")
+ message("PYTHON USING LINK LINE: ${PYTHON_LDSHARED}")
+ endif()
+-else(RDK_BUILD_PYTHON_WRAPPERS)
+- find_package(Boost 1.56.0 REQUIRED)
+ endif(RDK_BUILD_PYTHON_WRAPPERS)
+
+ # Detect clang, which masquerades as gcc. CMake 2.6 doesn't know how to
+@@ -357,11 +338,7 @@ else()
+ endif()
+
+ if(RDK_USE_BOOST_SERIALIZATION)
+-set(T_LIBS ${Boost_LIBRARIES})
+-find_package(Boost 1.56.0 COMPONENTS serialization)
+-if (Boost_SERIALIZATION_LIBRARY)
+- set(Boost_LIBRARIES ${T_LIBS} ${Boost_LIBRARIES})
+-endif()
++
+ endif()
+
+
+@@ -369,7 +346,7 @@ endif()
+ target_include_directories(rdkit_base INTERFACE
+$
+$
+- ${Boost_INCLUDE_DIR}
++ ${Boost_INCLUDE_DIRS}
+)
+ target_link_libraries(rdkit_base INTERFACE ${BOOST_LIBRARIES})
+
+--- rdkit-201909.1.orig/Code/GraphMol/FileParsers/CMakeLists.txt
rdkit-201909.1/Code/GraphMol/FileParsers/CMakeLists.txt
+@@ -2,35 +2,11 @@
+ remove_definitions(-DRDKIT_GRAPHMOL_BUILD)
+ add_definitions(-DRDKIT_FILEPARSERS_BUILD)
+
+-if(RDK_USE_BOOST_IOSTREAMS)
+-if(WIN32)
+- find_package(Boost 1.56.0 COMPONENTS system iostreams REQUIRED)
+- find_package(Boost 1.56.0 COMPONENTS zlib)
+- set (link_iostreams ${Boost_LIBRARIES})
+- if (NOT Boost_USE_STATIC_LIBS)
+- add_definitions("-DBOOST_IOSTREAMS_DYN_LINK")
+- endif()
+-else()
+- find_package(Boost 1.56.0 COMPONENTS system iostreams REQUIRED)
+- set (link_iostreams ${Boost_LIBRARIES})
+- if (NOT Boost_USE_STATIC_LIBS)
+- add_definitions("-DBOOST_IOSTREAMS_DYN_LINK")
+- endif()
+-endif()
+-ADD_DEFINITIONS("-DRDK_USE_BOOST_IOSTREAMS")
+-endif(RDK_USE_BOOST_IOSTREAMS)
+-
+ if(RDK_BUILD_COORDGEN_SUPPORT)
+ include_directories(${maeparser_INCLUDE_DIRS})
+ set (maesupplier MaeMolSupplier.cpp)
+ endif()
+
+-if(RDK_USE_BOOST_REGEX)
+- add_
Processed: Re: singularity: depends on dummy transitional package ttf-dejavu-core
Processing control commands: > severity -1 grave Bug #962196 [singularity] singularity: depends on dummy transitional package ttf-dejavu-core Severity set to 'grave' from 'normal' -- 962196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 962585 is forwarded to https://0xacab.org/schleuder/schleuder/-/issues/472
Processing commands for cont...@bugs.debian.org: > forwarded 962585 https://0xacab.org/schleuder/schleuder/-/issues/472 Bug #962585 [src:schleuder] schleuder: build fails on IPv6-only buildds Set Bug forwarded-to-address to 'https://0xacab.org/schleuder/schleuder/-/issues/472'. > thanks Stopping processing here. Please contact me if you need assistance. -- 962585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962253: esys-particle: diff for NMU version 2.3.5+dfsg1-4.1
Control: tags 962253 + patch Control: tags 962253 + pending Dear maintainer, I've prepared an NMU for esys-particle (versioned as 2.3.5+dfsg1-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru esys-particle-2.3.5+dfsg1/debian/changelog esys-particle-2.3.5+dfsg1/debian/changelog --- esys-particle-2.3.5+dfsg1/debian/changelog 2019-12-26 16:20:58.0 +0200 +++ esys-particle-2.3.5+dfsg1/debian/changelog 2020-06-10 15:42:57.0 +0300 @@ -1,3 +1,10 @@ +esys-particle (2.3.5+dfsg1-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix the manpage section number. (Closes: #962253) + + -- Adrian Bunk Wed, 10 Jun 2020 15:42:57 +0300 + esys-particle (2.3.5+dfsg1-4) unstable; urgency=medium * Team upload. diff -Nru esys-particle-2.3.5+dfsg1/debian/esysparticle.1 esys-particle-2.3.5+dfsg1/debian/esysparticle.1 --- esys-particle-2.3.5+dfsg1/debian/esysparticle.1 2019-12-26 16:20:58.0 +0200 +++ esys-particle-2.3.5+dfsg1/debian/esysparticle.1 2020-06-10 15:42:57.0 +0300 @@ -1,4 +1,4 @@ -.TH ESyS-Particle "2012-12-30" +.TH ESyS-Particle "1" .SH NAME .B ESyS-Particle \- HPC Discrete Element Modelling Software.
Processed: esys-particle: diff for NMU version 2.3.5+dfsg1-4.1
Processing control commands: > tags 962253 + patch Bug #962253 [esys-particle] esys-particle: Broken section number in manpage Added tag(s) patch. > tags 962253 + pending Bug #962253 [esys-particle] esys-particle: Broken section number in manpage Added tag(s) pending. -- 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960421: libpwiz: diff for NMU version 3.0.18342-2.1
Control: tags 960421 + patch
Control: tags 960421 + pending
Dear maintainer,
I've prepared an NMU for libpwiz (versioned as 3.0.18342-2.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru libpwiz-3.0.18342/debian/changelog libpwiz-3.0.18342/debian/changelog
--- libpwiz-3.0.18342/debian/changelog 2019-02-02 00:38:03.0 +0200
+++ libpwiz-3.0.18342/debian/changelog 2020-06-10 14:53:05.0 +0300
@@ -1,3 +1,10 @@
+libpwiz (3.0.18342-2.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add patch for FTBFS with Boost 1.71. (Closes: #960421)
+
+ -- Adrian Bunk Wed, 10 Jun 2020 14:53:05 +0300
+
libpwiz (3.0.18342-2) unstable; urgency=low
* Improve header path (move pwiz to proteowizard) to ease with nested
diff -Nru libpwiz-3.0.18342/debian/patches/fix-ftbfs.patch libpwiz-3.0.18342/debian/patches/fix-ftbfs.patch
--- libpwiz-3.0.18342/debian/patches/fix-ftbfs.patch 1970-01-01 02:00:00.0 +0200
+++ libpwiz-3.0.18342/debian/patches/fix-ftbfs.patch 2020-06-10 14:53:05.0 +0300
@@ -0,0 +1,70 @@
+Description: New gcc/boost fail to cast tribool to bool, force it.
+Author: Dimitri John Ledkov
+
+
+Index: libpwiz-3.0.18342/pwiz/data/identdata/IdentData.cpp
+===
+--- libpwiz-3.0.18342.orig/pwiz/data/identdata/IdentData.cpp
libpwiz-3.0.18342/pwiz/data/identdata/IdentData.cpp
+@@ -1047,7 +1047,7 @@ PWIZ_API_DECL proteome::DigestedPeptide
+ BOOST_FOREACH(CVID cleavageAgent, cleavageAgents)
+ {
+ if (!findPeptideEvidenceWithRegex(pe, peptide, peptideSequenceInContext, cleavageAgent, "",
+- sip.enzymes.independent, nTerminusIsSpecific, cTerminusIsSpecific,
++ (bool) sip.enzymes.independent, nTerminusIsSpecific, cTerminusIsSpecific,
+ bestSpecificity, bestResult))
+ break;
+ }
+@@ -1055,7 +1055,7 @@ PWIZ_API_DECL proteome::DigestedPeptide
+ BOOST_FOREACH(const string& regex, cleavageAgentRegexes)
+ {
+ if (!findPeptideEvidenceWithRegex(pe, peptide, peptideSequenceInContext, CVID_Unknown, regex,
+- sip.enzymes.independent, nTerminusIsSpecific, cTerminusIsSpecific,
++ (bool) sip.enzymes.independent, nTerminusIsSpecific, cTerminusIsSpecific,
+ bestSpecificity, bestResult))
+ break;
+ }
+@@ -1109,7 +1109,7 @@ PWIZ_API_DECL vector
Processed: libpwiz: diff for NMU version 3.0.18342-2.1
Processing control commands: > tags 960421 + patch Bug #960421 [src:libpwiz] libpwiz: FTBFS with boost 1.71 Added tag(s) patch. > tags 960421 + pending Bug #960421 [src:libpwiz] libpwiz: FTBFS with boost 1.71 Added tag(s) pending. -- 960421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi!
On Tue, 2020-05-26 at 17:59:33 +0200, Axel Beckert wrote:
> Johannes Schauer wrote:
> > And I got the same error as Otto ("Unmet build dependencies:
> > build-essential:native")
> One idea was to add some logic to automatically decide if we can use
> dpkg-buildpackage or not and if not, fall back to the old method by
> calling debian/rules directly which would partially reopen #880165.
>
> It seems as if build-essential gets automatically added to the build
> dependencies by Dpkg::Vendor::Debian. So this might even be different
> in other derivative distributions, hence we should neither hardcode it
> as dependency nor should we test of it being installed or not.
>
> But since equivs nearly never compiles stuff but is for metapackages,
> the simple solution is probably to run dpkg-buildpackage always with
> --no-check-builddeps.
[…]
> A maybe a bit safer variant would be to call dpkg-checkbuilddeps
> beforehand and filter out build-essential if it appears. That way
> around it should hurt way less to hardcode the package name.
You can simply use --ignore-builtin-builddeps. :)
Thanks,
Guillem
Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences
On Tue, 9 Jun 2020 21:08:25 +0100, Simon McVittie wrote:
> On Tue, 09 Jun 2020 at 15:21:37 -0400, Olek Wojnar wrote:
> > On Tue, Jun 9, 2020 at 6:12 AM Adrian Bunk <[1]b...@debian.org> wrote:
> > > I wonder if the real fix shouldn't be for cegui-mk2 to stop
> > > exporting a
> > pile
> > > of Boost symbols...
> >
> >
> > I would love that. Any advice on a reasonably easy/straightforward way of
> > doing that?
>
> *If* your upstream is on board with this, my understanding is that
> the main way to do this is to build with -fvisibility=hidden,
> and decorate each intentionally-public class/function/thing
> with a macro that (when building with gcc or clang) expands to
> __attribute__((__visibility__("hidden"))).
>
> Some upstreams will be doing something similar already, because they are
> portable to Windows and need to decorate public symbols with
> __declspec(dllexport) on Windows.
See
https://salsa.debian.org/debian/fcml/-/blob/master/debian/patches/visibility.patch
for a quick-and-dirty example of both of these approaches (and
https://salsa.debian.org/debian/fcml/-/commit/22d753b1c820ea339b6b52cbc1cdf6e05229fbf9#34a4bacbb5ecf973fa5f481819228c77da389f43
for the resulting symbols file simplification).
Regards,
Stephen
pgpk2c5j6uPEd.pgp
Description: OpenPGP digital signature
Bug#962588: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright
Package: linux-image-amd64 Version: 5.6.14-2 Severity: serious Justification: Policy 2.3 tglase@tglase:~ $ ll /usr/share/doc/linux-image-amd64/ total 0 tglase@tglase:~ $ ll -d /usr/share/doc/linux-image-amd64 drwxr-xr-x 2 root root 4096 Okt 21 2019 /usr/share/doc/linux-image-amd64/ -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.5.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages linux-image-amd64:amd64 depends on: ii linux-image-5.6.0-2-amd64 5.6.14-2 linux-image-amd64:amd64 recommends no packages. linux-image-amd64:amd64 suggests no packages. -- no debconf information
Bug#962262: opendmarc fails many emails without apparent reason
Control: severity -1 normal Decreasing the severity to ‘normal’, as I understand this is a configuration problem.
Bug#962497: r-base breaks r-cran-data.table autopkgtest: 'origin' must be supplied
It would be nice if we could hear from team r-cran-data.table on this matter. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#962275: snort: Failed to start LSB
Javier Fernandez-Sanguino writes: Could you please confirm if the 'eth0' interface is available in the system? One possible reason for startup failing is that the interface is not the correct one (administrator should configure the proper one via debconf). Dear Javier, the 'eth0' interface is available: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 74:d4:35:f8:9a:70 brd ff:ff:ff:ff:ff:ff altname enp0s25 inet 192.168.1.27/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 27084sec preferred_lft 27084sec inet6 fe80::76d4:35ff:fef8:9a70/64 scope link valid_lft forever preferred_lft forever Best regards Toto
Processed: Re: re: lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`?
Processing control commands: > tags -1 pending Bug #961986 [src:lix] lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`? Added tag(s) pending. -- 961986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961986: re: lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`?
control: tags -1 pending
in deferred/2
thanks
Gianfranco
diff -Nru lix-0.9.29/debian/changelog lix-0.9.29/debian/changelog
--- lix-0.9.29/debian/changelog 2019-12-10 09:02:16.0 +0100
+++ lix-0.9.29/debian/changelog 2020-06-10 13:11:32.0 +0200
@@ -1,3 +1,13 @@
+lix (0.9.29-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Peter Michael Green ]
+ * Add patch from upstream pull request to fix build with new libphobos
+(Closes: 961986)
+
+ -- Gianfranco Costamagna Wed, 10 Jun 2020
13:11:32 +0200
+
lix (0.9.29-1) unstable; urgency=medium
* New upstream version. (Closes: #941390)
diff -Nru lix-0.9.29/debian/patches/phobos-2.091.patch
lix-0.9.29/debian/patches/phobos-2.091.patch
--- lix-0.9.29/debian/patches/phobos-2.091.patch1970-01-01
01:00:00.0 +0100
+++ lix-0.9.29/debian/patches/phobos-2.091.patch2020-06-10
13:11:09.0 +0200
@@ -0,0 +1,39 @@
+Patch taken from
https://github.com/Abscissa/SDLang-D/pull/70/commits/90e5bdad1d803a507b34d46c5ecf82cb1feb7cd4
+with paths adjusted to apply to the Debian lix package.
+
+commit 90e5bdad1d803a507b34d46c5ecf82cb1feb7cd4
+Author: Steven Schveighoffer
+Date: Fri Mar 20 17:26:58 2020 -0400
+
+Remove FracSec usage if not available in Phobos (2.091+) Fixes #68.
+
+diff --git a/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
b/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
+index 593746c..074c705 100644
+--- a/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
b/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
+@@ -24,9 +24,11 @@ struct DateTimeFrac
+ {
+ DateTime dateTime;
+ Duration fracSecs;
+- deprecated("Use fracSecs instead.") {
++ static if(is(FracSec)) {
++ deprecated("Use fracSecs instead.") {
+ @property FracSec fracSec() const { return
FracSec.from!"hnsecs"(fracSecs.total!"hnsecs"); }
+ @property void fracSec(FracSec v) { fracSecs = v.hnsecs.hnsecs;
}
++ }
+ }
+ }
+
+@@ -44,9 +46,11 @@ struct DateTimeFracUnknownZone
+ {
+ DateTime dateTime;
+ Duration fracSecs;
+- deprecated("Use fracSecs instead.") {
++ static if(is(FracSec)) {
++ deprecated("Use fracSecs instead.") {
+ @property FracSec fracSec() const { return
FracSec.from!"hnsecs"(fracSecs.total!"hnsecs"); }
+ @property void fracSec(FracSec v) { fracSecs = v.hnsecs.hnsecs;
}
++ }
+ }
+ string timeZone;
+
diff -Nru lix-0.9.29/debian/patches/series lix-0.9.29/debian/patches/series
--- lix-0.9.29/debian/patches/series2018-12-04 10:55:25.0 +0100
+++ lix-0.9.29/debian/patches/series2020-06-10 13:11:09.0 +0200
@@ -1 +1,2 @@
dub-i-dub-i-dub-dub-dub
+phobos-2.091.patch
Bug#960481: marked as done (syslog-ng FTBFS with bison 3.6.1)
Your message dated Wed, 10 Jun 2020 11:00:24 +
with message-id
and subject line Bug#960481: fixed in syslog-ng 3.27.1-1
has caused the Debian Bug report #960481,
regarding syslog-ng FTBFS with bison 3.6.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
960481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.25.1-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/syslog-ng.html
...
lib/pragma-grammar.y: In function 'pragma_parse':
lib/pragma-grammar.y:402:73: error: 'YYEMPTY' undeclared (first use in this
function)
402 | stmt_and_eol { if (yychar !=
YYEMPTY) { cfg_lexer_unput_token(lexer, &yylval); } PRAGMA_END(); YYACCEPT; }
|
^~~
lib/pragma-grammar.y:402:73: note: each undeclared identifier is reported only
once for each function it appears in
make[3]: *** [Makefile:15459: lib/libsyslog_ng_la-pragma-grammar.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.27.1-1
Done: Laszlo Boszormenyi (GCS)
We believe that the bug you reported is fixed in the latest version of
syslog-ng, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) (supplier of updated syslog-ng
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 17 May 2020 14:41:30 +0200
Source: syslog-ng
Binary: syslog-ng syslog-ng-core syslog-ng-dbg syslog-ng-dev
syslog-ng-mod-add-contextual-data syslog-ng-mod-amqp syslog-ng-mod-examples
syslog-ng-mod-extra syslog-ng-mod-geoip2 syslog-ng-mod-getent
syslog-ng-mod-graphite syslog-ng-mod-http syslog-ng-mod-map-value-pairs
syslog-ng-mod-mongodb syslog-ng-mod-python syslog-ng-mod-rdkafka
syslog-ng-mod-redis syslog-ng-mod-riemann syslog-ng-mod-smtp syslog-ng-mod-snmp
syslog-ng-mod-sql syslog-ng-mod-stardate syslog-ng-mod-stomp
syslog-ng-mod-xml-parser
Architecture: source amd64 all
Version: 3.27.1-1
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers
Changed-By: Laszlo Boszormenyi (GCS)
Description:
syslog-ng - Enhanced system logging daemon (metapackage)
syslog-ng-core - Enhanced system logging daemon (core)
syslog-ng-dbg - Enhanced system logging daemon (debug symbols)
syslog-ng-dev - Enhanced system logging daemon (development files)
syslog-ng-mod-add-contextual-data - Enhanced system logging daemon
(add-contextual-data plugin)
syslog-ng-mod-amqp - Enhanced system logging daemon (AMQP plugin)
syslog-ng-mod-examples - Enhanced system logging daemon (example plugins)
syslog-ng-mod-extra - Enhanced system logging daemon (extra plugins)
syslog-ng-mod-geoip2 - Enhanced system logging daemon (GeoIP2 plugin)
syslog-ng-mod-getent - Enhanced system logging daemon (getent plugin)
syslog-ng-mod-graphite - Enhanced system logging daemon (graphite plugin)
syslog-ng-mod-http - Enhanced system logging daemon (HTTP destination)
syslog-ng-mod-map-value-pairs - Enhanced system logging daemon
(map-value-pairs plugin)
syslog-ng-mod-mongodb - Enhanced system logging daemon (MongoDB plugin)
syslog-ng-mod-python - Enhanced system logging daemon (Python plugin)
syslog-ng-mod-rdkafka - Enhanced system logging daemon (Kafka destination,
based on librd
syslog-ng-mod-redis - Enhanced system logging daemon (Redis plugin)
syslog-ng-mod-riemann - Enhanced system logging daemon (Riemann destination)
syslog-ng-mod-smtp - Enhanced system logging daemon (SMTP plugin)
syslog-ng-mod-snmp - Enhanced system logging daemon (SNMP plugin)
syslog-ng-mod-sql - Enhanced system logging daemon (SQL plugin)
syslog-ng-mod-stardate - Enhanced system logging daemon (stardate plugin)
syslog-ng-mod-stomp - Enhanced system logging daemon (STOMP plugin)
syslog-ng-mod-xml-parser - Enhanced system logging daemon (xml parser plugin)
Closes: 913754 960481
Changes:
syslog-ng (3.27.1-1) unstable; urgency=medium
Bug#960439: marked as done (libopenexr-dev: missing Breaks+Replaces: libilmbase-dev (<< ???))
Your message dated Wed, 10 Jun 2020 11:00:14 + with message-id and subject line Bug#960439: fixed in openexr 2.5.1-1 has caused the Debian Bug report #960439, regarding libopenexr-dev: missing Breaks+Replaces: libilmbase-dev (<< ???) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenexr-dev Version: 2.5.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 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libopenexr-dev_2.5.0-1_amd64.deb ... Unpacking libopenexr-dev (2.5.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libopenexr-dev_2.5.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package libilmbase-dev:amd64 2.3.0-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopenexr-dev_2.5.0-1_amd64.deb There is no libilmbase-dev upload, yet, that does not ship /usr/include/OpenEXR/Iex.h Please use the version (+ suffix '~') of such an upload for the B+R. cheers, Andreas libilmbase-dev=2.3.0-6_libopenexr-dev=2.5.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openexr Source-Version: 2.5.1-1 Done: m...@debian.org (Matteo F. Vescovi) We believe that the bug you reported is fixed in the latest version of openexr, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated openexr 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, 21 May 2020 23:05:36 +0200 Source: openexr Binary: libopenexr-dev libopenexr25 libopenexr25-dbgsym openexr openexr-dbgsym openexr-doc Architecture: source amd64 all Version: 2.5.1-1 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Description: libopenexr-dev - development files for the OpenEXR image library libopenexr25 - runtime files for the OpenEXR image library openexr- command-line tools for the OpenEXR image format openexr-doc - documentation and examples for the OpenEXR image format Closes: 960439 Changes: openexr (2.5.1-1) experimental; urgency=medium . * New upstream release (Closes: #960439) - debian/control: SONAME bump 24 -> 25 * debian/rules: set cmake as build system Checksums-Sha1: dfa1fcec9115447a939c944b32ab6b7ef79ecdd3 2683 openexr_2.5.1-1.dsc 8932db230598ccc4092e9038517da412df5f187c 27669939 openexr_2.5.1.orig.tar.gz 6f997712a29713d935524f191b45326308e7cb06 287 openexr_2.5.1.orig.tar.gz.asc 3694af7e7b669b527f087c23a966e9b88c344a25 21364 openexr_2.5.1-1.debian.tar.xz 34026f64f8b5f678f6a85322230d33b5c74b54bf 152168 libopenexr-dev_2.5.1-1_amd64.deb 4e2eeb91d883dd23e4c0606643f2671856581da5 3743508 libopenexr25-dbgsym_2.5.1-1_amd64.deb 29ebecbe5ba685dbe4a6bc3b0f1cb1c16cf71105 669080 libopenexr25_2.5.1-1_amd64.deb 171a1c5b56f4ba49246efd5a4bcdf780d458a3a7 1044332 openexr-dbgsym_2.5.1-1_amd64.deb 6285eb7abe25afbd58b3d74848a3d8a03c3c635a 2116280 openexr-doc_2.5.1-1_all.deb 9c55236a57d2a77bd1892828639b6d2cfcf29177 8022 openexr_2.5.1-1_amd64.buildinfo 469e429e33592dbfaceac3900a06275cd47303b6 182604 openexr_2.5.1-1_amd64.deb Checksums-Sha256: c3e4306477b68ac4c83e3d81e27107c9b775bbd7b64446af1b795c00288c4658 2683 openexr_2.5.1-1.dsc ecae7bbfa05eb21a84ae6bc45f41287ae15f02b13b1f5c07df0ae15d8d4d66c2 27669939 openexr_2.5.1.orig.tar.gz 5e1eb79671cac79d5142fd50757740b133b614ab23732992c617a47088ad3aa9
Bug#962275: snort: Failed to start LSB
On Fri, 5 Jun 2020 at 15:09, Thorsten Bonow wrote: > Package: snort > Version: 2.9.15.1-2 > Severity: grave > > Dear Maintainer, > > installation of 'snort' fails with a subprocess error (fresh install, > /etc/snort doesn't exist before installation. Accepting the propose > d network settings: 192.168.0.0/16). Aptitude output: > Dear Thorsten, Thank you for your report. The Snort package appears to be configured with the following values: snort/address_range: 192.168.0.0/16 * snort/interface: eth0 Could you please confirm if the 'eth0' interface is available in the system? One possible reason for startup failing is that the interface is not the correct one (administrator should configure the proper one via debconf). Best regards Javier
Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences
On Tue, Jun 09, 2020 at 09:08:25PM +0100, Simon McVittie wrote:
> On Tue, 09 Jun 2020 at 15:21:37 -0400, Olek Wojnar wrote:
> > On Tue, Jun 9, 2020 at 6:12 AM Adrian Bunk <[1]b...@debian.org> wrote:
> > > I wonder if the real fix shouldn't be for cegui-mk2 to stop exporting
> > a
> > pile
> > > of Boost symbols...
> >
> >
> > I would love that. Any advice on a reasonably easy/straightforward way of
> > doing
> > that?
>
> *If* your upstream is on board with this, my understanding is that
> the main way to do this is to build with -fvisibility=hidden,
> and decorate each intentionally-public class/function/thing
> with a macro that (when building with gcc or clang) expands to
> __attribute__((__visibility__("hidden"))).
"default", not "hidden"
> Some upstreams will be doing something similar already, because they are
> portable to Windows and need to decorate public symbols with
> __declspec(dllexport) on Windows.
>
> See: https://gcc.gnu.org/wiki/Visibility
Please add something like what you wrote in this email to
https://wiki.debian.org/UsingSymbolsFiles
> smcv
Thanks
Adrian
Bug#962585: schleuder: build fails on IPv6-only buildds
Source: schleuder
Version: 3.5.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=schleuder&arch=all&ver=3.5.2-1&stamp=1591750657&raw=0
...
Failures:
1) cli #refresh_keys updates keys from the keyserver for only a specific list
Failure/Error: raise "sks-mock.rb failed to start, cannot continue: #{exc}"
RuntimeError:
sks-mock.rb failed to start, cannot continue: Failed to open TCP
connection to 127.0.0.1: (Connection refused - connect(2) for "127.0.0.1"
port )
# ./spec/spec_helper.rb:96:in `rescue in with_sks_mock'
# ./spec/spec_helper.rb:88:in `with_sks_mock'
# ./spec/schleuder/integration/cli_spec.rb:187:in `block (3 levels) in
'
# ./spec/spec_helper.rb:47:in `block (3 levels) in '
# ./spec/spec_helper.rb:46:in `block (2 levels) in '
# --
# --- Caused by: ---
# Errno::ECONNREFUSED:
# Connection refused - connect(2) for "127.0.0.1" port
# ./spec/spec_helper.rb:90:in `with_sks_mock'
...
Finished in 32 minutes 16 seconds (files took 2.5 seconds to load)
431 examples, 14 failures
Failed examples:
rspec ./spec/schleuder/integration/cli_spec.rb:175 # cli #refresh_keys updates
keys from the keyserver for only a specific list
rspec ./spec/schleuder/integration/cli_spec.rb:152 # cli #refresh_keys updates
keys from the keyserver
rspec ./spec/schleuder/unit/list_spec.rb:536 # Schleuder::List#fetch_keys
fetches one key by email address
rspec ./spec/schleuder/unit/list_spec.rb:519 # Schleuder::List#fetch_keys
fetches one key by URL
rspec ./spec/schleuder/unit/list_spec.rb:553 # Schleuder::List#fetch_keys does
not import non-self-signatures if gpg >= 2.1.15; or else sends a warning
rspec ./spec/schleuder/unit/list_spec.rb:502 # Schleuder::List#fetch_keys
fetches one key by fingerprint
rspec ./spec/schleuder/integration/keywords_spec.rb:1678 # user sends keyword
x-fetch-key with fingerprint
rspec ./spec/schleuder/integration/keywords_spec.rb:1599 # user sends keyword
x-fetch-key with invalid URL
rspec ./spec/schleuder/integration/keywords_spec.rb:1560 # user sends keyword
x-fetch-key with URL
rspec ./spec/schleuder/integration/keywords_spec.rb:1482 # user sends keyword
x-fetch-key with email address
rspec ./spec/schleuder/integration/keywords_spec.rb:1756 # user sends keyword
x-fetch-key without arguments
rspec ./spec/schleuder/integration/keywords_spec.rb:1717 # user sends keyword
x-fetch-key with fingerprint of unchanged key
rspec ./spec/schleuder/integration/keywords_spec.rb:1521 # user sends keyword
x-fetch-key with unknown email-address
rspec ./spec/schleuder/integration/keywords_spec.rb:1639 # user sends keyword
x-fetch-key with unknown fingerprint
Randomized with seed 8043
/usr/bin/ruby2.7
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec --format
documentation failed
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/schleuder
returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
See #962019 for discussion of a similar problem in a different package.
Bug#960391: fixed in experimental
yes, I'll definitely do it this week. Just swamped at work right now.
Bug#960271: marked as done (version 4.19.118-2 breaks userspace builds (e.g. QEMU) - 'BITS_PER_LONG' wrongly used)
Your message dated Wed, 10 Jun 2020 09:03:13 + with message-id and subject line Bug#960271: fixed in linux 4.19.118-2+deb10u1 has caused the Debian Bug report #960271, regarding version 4.19.118-2 breaks userspace builds (e.g. QEMU) - 'BITS_PER_LONG' wrongly used 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.) -- 960271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-libc-dev Version: 4.19.118-2 Severity: important Dear maintainer, QEMU doesn't build since 4.19.118-2, the error has been discussed at length on the Ubuntu bugtracker: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877123/ The upstream kernel includes a fix, it has also been backported by the Ubuntu team (see links above). Since this breaks userspace functionality (e.g. QEMU and some systemd builds from what I gather), including the fix here too would be nice. ~ Stefan -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.34-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.118-2+deb10u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jun 2020 17:42:22 +0200 Source: linux Architecture: source Version: 4.19.118-2+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 960271 Changes: linux (4.19.118-2+deb10u1) buster-security; urgency=high . [ Salvatore Bonaccorso ] * selinux: properly handle multiple messages in selinux_netlink_send() (CVE-2020-10751) * fs/namespace.c: fix mountpoint reference counter race (CVE-2020-12114) * USB: core: Fix free-while-in-use bug in the USB S-Glibrary (CVE-2020-12464) * [x86] KVM: SVM: Fix potential memory leak in svm_cpu_init() (CVE-2020-12768) * scsi: sg: add sg_remove_request in sg_write (CVE-2020-12770) * USB: gadget: fix illegal array access in binding with UDC (CVE-2020-13143) * netlabel: cope with NULL catmap (CVE-2020-10711) * fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info() (CVE-2020-10732) * kernel/relay.c: handle alloc_percpu returning NULL in relay_open (CVE-2019-19462) * mm: Fix mremap not considering huge pmd devmap (CVE-2020-10757) * [x86] KVM: nVMX: Always sync GUEST_BNDCFGS when it comes from vmcs01 * KVM: Introduce a new guest mapping API * [arm64] kvm: fix compilation on aarch64 * [s390x] kvm: fix compilation on s390 * [s390x] kvm: fix compile on s390 part 2 * KVM: Properly check if "page" is valid in kvm_vcpu_unmap * [x86] kvm: Introduce kvm_(un)map_gfn() (CVE-2019-3016) * [x86] kvm: Cache gfn to pfn translation (CVE-2019-3016) * [x86] KVM: Make sure KVM_VCPU_FLUSH_TLB flag is not missed (CVE-2019-3016) * [x86] KVM: Clean up host's steal time structure (CVE-2019-3016) * include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for swap (Closes: #960271) . [ Ben Hutchings ] * propagate_one(): mnt_set_mountpoint() needs mount_lock * [x86] Add support for mitigation of Special Register Buffer Data Sampling (SRBDS) (CVE-2020-0543): - x86/cpu: Add 'table' argument to cpu_matches() - x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigatio
