Processed: forwarded 961367 https://github.com/tome2/tome2/issues/48
Processing commands for cont...@bugs.debian.org:
> forwarded 961367 https://github.com/tome2/tome2/issues/48
Bug #961367 [src:tome] tome FTBFS on 32bit: invalid conversion from ‘uint32_t*’
{aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’}
Set Bug forwarded-to-address to 'https://github.com/tome2/tome2/issues/48'.
> --
Stopping processing here.
Please contact me if you need assistance.
--
961367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#961646: node-deep-for-each breaks node-grunt-webpack
Package: node-deep-for-each Version: 3.0.0-1 Severity: serious Control: affects -1 node-grunt-webpack Version 3.0.0 breaks node-grunt-webpack. Probably due to this change: > This library is no longer built with Babel, you must compile it > yourself within your app Revert to a version 2.x may solve this issue
Processed: node-deep-for-each breaks node-grunt-webpack
Processing control commands: > affects -1 node-grunt-webpack Bug #961646 [node-deep-for-each] node-deep-for-each breaks node-grunt-webpack Added indication that 961646 affects node-grunt-webpack -- 961646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960571: marked as done (Missing dependency on fontconfig)
Your message dated Wed, 27 May 2020 02:49:13 + with message-id and subject line Bug#960571: fixed in rst2pdf 0.97-1 has caused the Debian Bug report #960571, regarding Missing dependency on fontconfig 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.) -- 960571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rst2pdf Version: 0.93-7 Severity: serious Hi, rst2pdf calls fc-match in findfonts.py, but does not list a dependency on fontconfig. If you don't have it installed, building the document will succeed but the document itself is empty. Cheers, Thijs --- End Message --- --- Begin Message --- Source: rst2pdf Source-Version: 0.97-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of rst2pdf, 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. Sandro Tosi (supplier of updated rst2pdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 May 2020 22:33:01 -0400 Source: rst2pdf Architecture: source Version: 0.97-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Sandro Tosi Closes: 960571 Changes: rst2pdf (0.97-1) unstable; urgency=medium . * New upstream release * debian/copyright - update upstream copyright information * debian/control - add fontconfig to Depends; Closes: #960571 Checksums-Sha1: cbff5d22885c98c3119196498696b2d3b1f9e1d3 2227 rst2pdf_0.97-1.dsc c6e25b5e87fd765e34b0edc1f08d64865adb656c 7770872 rst2pdf_0.97.orig.tar.xz 75810a86b1770194a262d29b806901967f8c2257 5048 rst2pdf_0.97-1.debian.tar.xz Checksums-Sha256: 25c696ae12cd3acdcfa269aff7e2614b2dd5646cbac8491a932d9d93011ce19e 2227 rst2pdf_0.97-1.dsc c0d4fd97b7fbc693d8f38be6fb0a6533eddae4d66a86604b0ca8fd9f0d65336c 7770872 rst2pdf_0.97.orig.tar.xz 899c684fa784f6a5acde0b8498b188691cb48fc6ddd9c89035f1d50d8aa6fd1c 5048 rst2pdf_0.97-1.debian.tar.xz Files: 586cdec80c10dd5ac32661064f29d951 2227 utils optional rst2pdf_0.97-1.dsc abfff871302a9e0a360dd99ff7f107c5 7770872 utils optional rst2pdf_0.97.orig.tar.xz 70b03105c66218661b87aae3edd1d569 5048 utils optional rst2pdf_0.97-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl7N0bEACgkQh588mTgB qU/7ixAAh9NKGldIRvE8Glr2oYnD1BtSr6RDcnWztfliJ37arNEvH8WjwyjZ+x/Q 1y5I2dJ9d04Qmm8BEaS5S4U3LoHa2ske1vfMO2FxLaasWinHreCsJx9LVUStmJjl 6OX2kbOpW7IyMaq8r4GRMsQyFSIpioXV1dImfIosEUAwNOwujTtJ+/g76Uoc0VIv 3fU9M4vIENWeNI5PVrwvXBkc7trYQ+bwhu+UvBctJOBlXMEF5RYFs3iWOM95RC5l zOvN4RyYXvIjW6ibpYF4Sxy79r81IZ7BN+p6p7dH95Y7NIrlbsyUOIuPckclUIty o/6Tc0N96WEoiDsCScpKyqrpnJ3pn0V87Q6llxGiZV6rkxbIiKouFWiNEGvivIW7 DW0iD3LJYOj5aA4uh36g8A6zSAax5JNll4aGB58rtAFxx95YCFDtQ3je8qLt0HNA Dadu4sVNfN8NUZVbQW0C5z+WRPRcq80NuLZPUPE16r8Wrp1/9Wieb97CydZu/UqW SEvUCDmmqMtDpyXQisWlwQH88HJAuFcZTzqiBRK/Fv+hwVITvcxfQUbA2O0jfyiE 54AxDxOx6y0ebLMKrkctxZqlGYCEjNmCKyr1Y5gnaUuoSdQnJM7U45TGDmoKDBq4 7PNBkxsMx1S++FnvCHvr7HD7i9I+5aAfYwjXOjWs2C9wd8aKEA4= =ptYZ -END PGP SIGNATURE End Message ---
Bug#960571: marked as pending in pdfposter
Control: tag -1 pending Hello, Bug #960571 in pdfposter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/rst2pdf/-/commit/c2eed00a2e2387e08d6961a5b6433142e08e70fa add fontconfig to Depends; Closes: #960571 (this message was generated automatically) -- Greetings https://bugs.debian.org/960571
Processed: Bug#960571 marked as pending in pdfposter
Processing control commands: > tag -1 pending Bug #960571 [rst2pdf] Missing dependency on fontconfig Added tag(s) pending. -- 960571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959643:
FWIW there is a new release (1.0.7) available and that seems to fix this failure (in Ubuntu, anyway).
Bug#961490: fwupd: version in stable too old, no updates possible
Am Di., 26. Mai 2020 um 20:24 Uhr schrieb : > > > -Original Message- > > From: Ansgar > > Sent: Tuesday, May 26, 2020 8:01 AM > > To: Steffen Schreiber; 961...@bugs.debian.org > > Subject: Bug#961490: fwupd: version in stable too old, no updates possible > > > > > > [EXTERNAL EMAIL] > > > > Hi, > > > > On Tue, 2020-05-26 at 13:56 +0200, Steffen Schreiber wrote: > > > So I see you marked this bug as fixed/resolved. > > > > Someone (not the maintainer) did so, but please note that the bug > > remains open even when marked as fixed in a newer version. Debian's > > stable release team prefers bugs to be fixed in unstable/testing before > > they get fixed in (old)stable, so this is good. > > The particular circumstances of this issue are that the update in question > requires > a newer version of fwupd than is in stable. This is not a matter of just > backporting > a change or two and it works. There are daemon and plugin level changes that > have to > go together to guarantee a proper update. > > This seems incompatible with the documentation around uploading to stable. > https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable > > > > > What's the way going forward for users of stable? Installing packages > > > from testing? Are you recommending to just forget about running Debian > > > stable as is? > > > > The maintainer hasn't yet commented on how he wants to proceed. > > Reasonable options seem to be to either update stable to the version > > currently in testing (1.3.9) or to update to a later version of 1.2.X. > > > > Ansgar > > If a particular update requires a newer fwupd version I don't think it's > reasonable > to push that version to all Debian users who may not need the newer fwupd > version > and might not be willing to accept the risk of regressions in a newer version. > > "Fixes must be minimal and relevant" > > So in this circumstance if your device needs the newer version you should > probably > take the package from testing instead. Maybe talk to the release-team - they will probably not like adding a change this big, but exceptions are always possible (e.g. firefox-esr is exempt from this rule). In any case though, you could provide a backport of the latest version for easy installation by stable users as the next-best option :-) Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#955117: marked as done (extra-cmake-modules: FTBFS with Sphinx 2.4: Could not import extension ecm (exception: No module named 'sphinxcontrib'))
Your message dated Wed, 27 May 2020 01:42:49 +0200 with message-id <15767450.aELy82tfIi@tuxin> and subject line Re: Bug#955117: extra-cmake-modules: FTBFS with Sphinx 2.4: Could not import extension ecm (exception: No module named 'sphinxcontrib') has caused the Debian Bug report #955117, regarding extra-cmake-modules: FTBFS with Sphinx 2.4: Could not import extension ecm (exception: No module named 'sphinxcontrib') 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.) -- 955117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: extra-cmake-modules Version: 5.62.0-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx2.4 Hi, extra-cmake-modules fails to build with Sphinx 2.4, currently available in experimental. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 50%] sphinx-build html: see > /<>/obj-x86_64-linux-gnu/docs/build-html.log > cd /<>/obj-x86_64-linux-gnu/docs && /usr/bin/sphinx-build -c > /<>/obj-x86_64-linux-gnu/docs -d > /<>/obj-x86_64-linux-gnu/docs/doctrees -b html > /<>/docs /<>/obj-x86_64-linux-gnu/docs/html > > build-html.log > > Extension error: > Could not import extension ecm (exception: No module named 'sphinxcontrib') > make[3]: *** [docs/CMakeFiles/documentation.dir/build.make:65: > docs/doc_format_html] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/03/26/extra-cmake-modules_5.62.0-1_unstable_sphinx243.log Please see [1] for Sphinx changelog, which may give a hint of what changes in Sphinx caused this error. Also see [2] for the list of deprecated/removed APIs and possible alternatives to them. Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that happens, the severity of this bug will be bumped to serious. In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/2.0/changes.html [2]: https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 5.70.0-1 Hi, > extra-cmake-modules fails to build with Sphinx 2.4, currently available in > experimental. It is now build against Sphinx 2.4.3 successfully. hefee signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 952289 javahelper Bug #952289 [src:libquartz2-java] libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298. Bug reassigned from package 'src:libquartz2-java' to 'javahelper'. No longer marked as found in versions libquartz2-java/2.3.0-2. Ignoring request to alter fixed versions of bug #952289 to the same values previously set > forcemerge 952317 952289 Bug #952317 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952322 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952370 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952289 [javahelper] libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298. Added indication that 952289 affects libsaxon-java,tunnelx,cronometer Bug #952322 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Removed indication that 952322 affects tunnelx, cronometer, and libsaxon-java Added indication that 952322 affects libsaxon-java,tunnelx,cronometer Removed indication that 952317 affects cronometer, tunnelx, and libsaxon-java Added indication that 952317 affects libsaxon-java,tunnelx,cronometer Removed indication that 952370 affects tunnelx, cronometer, and libsaxon-java Added indication that 952370 affects libsaxon-java,tunnelx,cronometer Bug #952370 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Merged 952289 952317 952322 952370 > affects 952317 + libquartz2-java Bug #952317 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952289 [javahelper] libquartz2-java: FTBFS: Could not read manifest from /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): at /usr/bin/jh_manifest line 298. Bug #952322 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952370 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Added indication that 952317 affects libquartz2-java Added indication that 952289 affects libquartz2-java Added indication that 952322 affects libquartz2-java Added indication that 952370 affects libquartz2-java > End of message, stopping processing here. Please contact me if you need assistance. -- 952289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952289 952317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952317 952322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952322 952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 952317 javahelper Bug #952317 [src:cronometer] cronometer: FTBFS: error: No member named $memberName Bug reassigned from package 'src:cronometer' to 'javahelper'. No longer marked as found in versions cronometer/0.9.9+dfsg-3. Ignoring request to alter fixed versions of bug #952317 to the same values previously set > reassign 952322 javahelper Bug #952322 [src:libsaxon-java] libsaxon-java: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Bug reassigned from package 'src:libsaxon-java' to 'javahelper'. No longer marked as found in versions libsaxon-java/1:6.5.5-12. Ignoring request to alter fixed versions of bug #952322 to the same values previously set > reassign 952370 javahelper Bug #952370 [src:tunnelx] tunnelx: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Bug reassigned from package 'src:tunnelx' to 'javahelper'. No longer marked as found in versions tunnelx/20170928-2. Ignoring request to alter fixed versions of bug #952370 to the same values previously set > forcemerge 952317 952322 952370 Bug #952317 [javahelper] cronometer: FTBFS: error: No member named $memberName Bug #952322 [javahelper] libsaxon-java: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Bug #952370 [javahelper] tunnelx: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Merged 952317 952322 952370 > retitle 952317 javahelper: jh_manifest breaks on jar files with no manifest Bug #952317 [javahelper] cronometer: FTBFS: error: No member named $memberName Bug #952322 [javahelper] libsaxon-java: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Bug #952370 [javahelper] tunnelx: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411. Changed Bug title to 'javahelper: jh_manifest breaks on jar files with no manifest' from 'cronometer: FTBFS: error: No member named $memberName'. Changed Bug title to 'javahelper: jh_manifest breaks on jar files with no manifest' from 'libsaxon-java: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411.'. Changed Bug title to 'javahelper: jh_manifest breaks on jar files with no manifest' from 'tunnelx: FTBFS: error: No member named $memberName at /usr/share/perl5/Archive/Zip/Archive.pm line 411.'. > affects 952317 tunnelx cronometer libsaxon-java Bug #952317 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952322 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Bug #952370 [javahelper] javahelper: jh_manifest breaks on jar files with no manifest Added indication that 952317 affects tunnelx, cronometer, and libsaxon-java Added indication that 952322 affects tunnelx, cronometer, and libsaxon-java Added indication that 952370 affects tunnelx, cronometer, and libsaxon-java > End of message, stopping processing here. Please contact me if you need assistance. -- 952317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952317 952322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952322 952370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#961584: lxc-stop fails with exit code 1
Processing control commands: > severity -1 serious Bug #961584 [src:lxc] lxc-stop fails with exit code 1 Severity set to 'serious' from 'important' -- 961584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961581: pbcopper: ftbfs on ppc64el
On Tue, 26 May 2020 at 23:43, Andreas Tille wrote: > thanks for the patch. I've uploaded pbcopper to new since > it needed a soname bump and thus a new binary package name. > Thanks. I think a fixed simde has been uploaded now, so my patch might not be needed at all...
Bug#936777: k3d: Python2 removal in sid/bullseye
Hi! Em 26 de mai. de 2020 às 20:43, Moritz Mühlenhoff escreveu: > > On Wed, Sep 04, 2019 at 12:10:39AM +0200, Manuel A. Fernandez Montecelo wrote: > > Control: forwarded -1 https://github.com/K-3D/k3d/issues/38 > > > > Thanks for the report. Asking upstream about their plans and best > > course of action. > > Given upstream's reply at https://github.com/K-3D/k3d/issues/38 this > seems unlikely to get ported, let's remove k3d? Basically I'd like to extend its life in Debian and keep users using this package rather than having to build the version themselves, as long as it doesn't become a big burden for Debian -- when it does sure, let's drop it, and if the moment is now, so be it. This package is in a bad situation with Python2 and GTK dependencies, but this is not the kind of application like a media player or similar for which there are a gazillion alternatives with more or less the same features -- this is a pretty specialized piece of software and migration to some other tool can be a huge undertaking and might not always be possible. If the relevant Python2 packages are going to be removed imminently, that's OK, we can remove it now. And in any case, this package should prevent the removal of Python2 if it's one of the last dependencies. But if Python2 it's to be held for a few months/years because other important/popular packages are not migrated yet (gnat-gps, kodi?), and even if only to keep it for unstable, I'd prefer to remove this package only when Python2 is removed. Cheers and thanks for your work. -- Manuel A. Fernandez Montecelo
Bug#961636: src:galera-3: fails to migrate to testing for too long: ftbfs on armel
Source: galera-3 Version: 25.3.28-2 Severity: serious Control: close -1 25.3.29-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 958040 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:galera-3 in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=galera-3 signature.asc Description: OpenPGP digital signature
Processed: src:galera-3: fails to migrate to testing for too long: ftbfs on armel
Processing control commands:
> close -1 25.3.29-2
Bug #961636 [src:galera-3] src:galera-3: fails to migrate to testing for too
long: ftbfs on armel
Marked as fixed in versions galera-3/25.3.29-2.
Bug #961636 [src:galera-3] src:galera-3: fails to migrate to testing for too
long: ftbfs on armel
Marked Bug as done
> block -1 by 958040
Bug #961636 {Done: Paul Gevers } [src:galera-3]
src:galera-3: fails to migrate to testing for too long: ftbfs on armel
961636 was not blocked by any bugs.
961636 was not blocking any bugs.
Added blocking bug(s) of 961636: 958040
--
961636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#955695: marked as done (wala: FTBFS: DexIMethod.java:735: error: incompatible types: DexFile cannot be converted to DexEntry)
Your message dated Tue, 26 May 2020 20:36:45 + with message-id and subject line Bug#955695: fixed in wala 1.5.2-1 has caused the Debian Bug report #955695, regarding wala: FTBFS: DexIMethod.java:735: error: incompatible types: DexFile cannot be converted to DexEntry 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.) -- 955695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wala Version: 1.5.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200402 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=wala -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@24faea88 > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@24faea88 > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@26b894bd > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@7377781e > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Generating JAR file: > /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar > Generating JAR file 'gradle-api-4.4.1.jar' > Keep-alive timer started > Adding Debian repository to project 'buildSrc' > Parallel execution is an incubating feature. > Evaluating project ':buildSrc' using build file > '/<>/buildSrc/build.gradle'. > Adding Maven pom generation to project 'buildSrc' > Linking the generated javadoc to the system JDK API documentation > Selected primary task 'clean' from project : > Selected primary task 'build' from project : > Creating new cache for annotation-processors, path > /<>/buildSrc/.gradle/4.4.1/fileContent/annotation-processors.bin, > access org.gradle.cache.internal.DefaultCacheAccess@61d011e > Creating new cache for resourceHashesCache, path > /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access > org.gradle.cache.internal.DefaultCacheAccess@26b894bd > Creating new cache for taskHistory, path > /<>/buildSrc/.gradle/4.4.1/taskHistory/taskHistory.bin, access > org.gradle.cache.internal.DefaultCacheAccess@34695b23 > Creating new cache for outputFiles, path > /<>/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2548fc01 > Build cache is an incubating feature. > Using local directory build cache for build ':buildSrc' (location = > /<>/.gradle/caches/build-cache-1, targetSize = 5 GB). > :clean (Thread[Task worker for ':buildSrc',5,main]) started. > :buildSrc:clean > Putting task artifact state for task ':buildSrc:clean' into context took > 0.001 secs. > Caching disabled for task ':buildSrc:clean': Caching has not been enabled for > the task > Up-to-date check for task ':buildSrc:clean' took 0.0 secs. It is not > up-to-date because: > Task has not declared any outputs. > :buildSrc:clean UP-TO-DATE > :clean (Thread[Task worker for ':buildSrc',5,main]) completed. Took 0.034 > secs. > :compileJava
Bug#961631: libopenmpi3: causes openmpi-bin/buster to segfault
Package: libopenmpi3 Version: 4.0.3-6 Severity: serious Hi Alastair, I just managed by accident to do a partial upgrade of openmpi, i.e. openmpi-bin was still the buster version while libopenmpi3 was already upgraded to bullseye. This caused mpirun to segfault ... I could reproduce it in a minimal buster chroot, installing openmpi-bin/buster and thereafter enabling bullseye sources and upgrading libgcc-8-dev gcc-8-base libmpx2 libc6-dev libopenmpi3 to bullseye. gdb says, the segfault happened in opal_hwloc_base_get_nbobjs_by_type () from /usr/lib/x86_64-linux-gnu/libopen-pal.so.40 so this is likely because mpirun causes both libhwloc.so.5 (own dependency) and libhwloc.so.15 (libopen-rte.so.40 dependency) to be loaded in the same process. libopenmpi3 should probably break packages from buster depending on both libopenmpi3 and libhwloc5. Luckily there are not that many: gromacs-openmpi (<< 2020~beta2-2) (*) libeztrace0 (<< 1.1-8-5+b1) (**) openmpi-bin (<< 4.0.2-4+b1) (**) starpu-contrib-examples (<< 1.3.2+dfsg-2+b1) (*) starpu-examples (<< 1.3.2+dfsg-4+b1) (**) I haven't tried if they cause crashes as well ... I just tried to find the first version no longer depending on libhwloc5 (either because it switched to libhwloc15 (*) or because it just dropped the dependency (**)). So I would recomend to add these to libopenmpi3: Breaks: gromacs-openmpi (<< 2020~beta2-2), libeztrace0 (<< 1.1-8-5+b1), openmpi-bin (<< 4.0.2-4+b1), starpu-contrib-examples (<< 1.3.2+dfsg-2+b1), starpu-examples (<< 1.3.2+dfsg-4+b1) (They can go with the next soname bump or after bullseye was released). Andreas
Processed: found 955019 in 1.1.9-5
Processing commands for cont...@bugs.debian.org:
> found 955019 1.1.9-5
Bug #955019 {Done: robe...@debian.org (Roberto C. Sanchez)}
[src:php-horde-trean] php-horde-trean: CVE-2020-8865
Marked as found in versions php-horde-trean/1.1.9-5 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#936777: k3d: Python2 removal in sid/bullseye
On Wed, Sep 04, 2019 at 12:10:39AM +0200, Manuel A. Fernandez Montecelo wrote: > Control: forwarded -1 https://github.com/K-3D/k3d/issues/38 > > Thanks for the report. Asking upstream about their plans and best > course of action. Given upstream's reply at https://github.com/K-3D/k3d/issues/38 this seems unlikely to get ported, let's remove k3d? Cheers, Moritz
Bug#961490: fwupd: version in stable too old, no updates possible
> -Original Message- > From: Ansgar > Sent: Tuesday, May 26, 2020 8:01 AM > To: Steffen Schreiber; 961...@bugs.debian.org > Subject: Bug#961490: fwupd: version in stable too old, no updates possible > > > [EXTERNAL EMAIL] > > Hi, > > On Tue, 2020-05-26 at 13:56 +0200, Steffen Schreiber wrote: > > So I see you marked this bug as fixed/resolved. > > Someone (not the maintainer) did so, but please note that the bug > remains open even when marked as fixed in a newer version. Debian's > stable release team prefers bugs to be fixed in unstable/testing before > they get fixed in (old)stable, so this is good. The particular circumstances of this issue are that the update in question requires a newer version of fwupd than is in stable. This is not a matter of just backporting a change or two and it works. There are daemon and plugin level changes that have to go together to guarantee a proper update. This seems incompatible with the documentation around uploading to stable. https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable > > > What's the way going forward for users of stable? Installing packages > > from testing? Are you recommending to just forget about running Debian > > stable as is? > > The maintainer hasn't yet commented on how he wants to proceed. > Reasonable options seem to be to either update stable to the version > currently in testing (1.3.9) or to update to a later version of 1.2.X. > > Ansgar If a particular update requires a newer fwupd version I don't think it's reasonable to push that version to all Debian users who may not need the newer fwupd version and might not be willing to accept the risk of regressions in a newer version. "Fixes must be minimal and relevant" So in this circumstance if your device needs the newer version you should probably take the package from testing instead.
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Paul, Thanks for the hint. The package for mipsel is now gone, migration of quantlib-python should now resume. Leaves the second part. Come to think about it I have never written an debian/rules to _not_ build something. So maybe something like ifneq "$(findstring $(cpu), mipsel)" "" exit 1 endif in the build-arch == build-indep == build target? Are there examples I could look at? Thanks again, Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#958414: marked as pending in equivs
Control: tag -1 pending Hello, Bug #958414 in equivs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/equivs/-/commit/1f342aea93c5b2f0554439accb16eae23ea3f6b5 Don't let dpkg-buildpackage check for build-dependencies It implicitly and unconditionally adds build-essential which equivs-generated metapackages don't need in nearly any case. Closes: #958414 Thanks Johannes 'josch' Schauer! (this message was generated automatically) -- Greetings https://bugs.debian.org/958414
Bug#961622: segfault on watching any stream
Package: gnome-twitch
Version: 0.4.1-3
Severity: grave
Hi,
current gnome-twitch will segfault on any stream selected. I've tried the
gstreamer-cairo and gstreamer-opengl backend to verify it's not backend related.
It starts fine, but selecting any stream will give the following output:
$ gnome-twitch
[17:49:27] Message - GNOME-Twitch : {GtApp:370} Startup, running version '0.4.1'
[17:49:27] Message - GNOME-Twitch : {GtFollowsManager:254} Follows file at
'/home/randall/.local/share/gnome-twitch/followed-channels.json' doesn't exist
[17:49:27] Message - GNOME-Twitch : {GtApp:339} Activate
[17:49:27] Message - GNOME-Twitch : {GtPlayer:132} Loading chat settings
[17:49:29] Message - GNOME-Twitch : {GtPlayer:1287} Can't open channel, no
backend loaded
[17:49:33] Message - GNOME-Twitch : {GtPlayer:999} Loaded player backend
'GStreamer Cairo player backend'
[17:49:33] Message - GNOME-Twitch : {GtPlayerBackendGstreamerCairo:246} Init
[17:49:33] Critical - GLib-GObject : g_object_get: assertion 'G_IS_OBJECT
(object)' failed
[17:49:33] Warning - GNOME-Twitch : cannot set NULL uri
[17:49:33] Critical - Gtk : gtk_widget_add_events: assertion 'GTK_IS_WIDGET
(widget)' failed
[17:49:33] Critical - Gtk : gtk_widget_set_can_focus: assertion 'GTK_IS_WIDGET
(widget)' failed
[17:49:33] Critical - Gtk : gtk_container_add: assertion 'GTK_IS_WIDGET
(widget)' failed
[17:49:33] Warning - GLib-GObject : invalid (NULL) pointer instance
[17:49:33] Critical - GLib-GObject : g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
[17:49:33] Warning - GLib-GObject : invalid (NULL) pointer instance
[17:49:33] Critical - GLib-GObject : g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
[17:49:33] Message - GNOME-Twitch : {GtPlayer:1310} Opening stream 'asmongold'
with quality 'source'
[17:49:33] Warning - GNOME-Twitch : {GtTwitch:336} Received unsuccessful
response from url 'https://api.twitch.tv/api/channels/asmongold/access_token'
with code '410' and body '{"error":"Gone","status":410,"message":"this API has
been removed."}'
[17:49:33] Warning - GNOME-Twitch : {GtTwitch:594} Error getting stream access
token for channel 'asmongold' because: Received unsuccessful response from url
'https://api.twitch.tv/api/channels/asmongold/access_token' with code '410' and
body '{"error":"Gone","status":410,"message":"this API has been removed."}'
Segmentation fault
Regards,
Lee
-- 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.14 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-twitch depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1
ii libc62.30-8
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4
ii libglib2.0-0 2.64.2-1
ii libgtk-3-0 3.24.20-1
ii libjson-glib-1.0-0 1.4.4-2
ii libpeas-1.0-01.26.0-2
ii libsoup2.4-1 2.70.0-1
ii libwebkit2gtk-4.0-37 2.28.2-2
ii libx11-6 2:1.6.9-2+b1
Versions of packages gnome-twitch recommends:
ii gnome-twitch-player-backend-gstreamer-cairo 0.4.1-3
gnome-twitch suggests no packages.
-- no debconf information
Processed: Bug#958414 marked as pending in equivs
Processing control commands: > tag -1 pending Bug #958414 [equivs] Latest equivs version 2.3.0 breaks mk-build-deps Added tag(s) pending. -- 958414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961572: marked as done (r-bioc-mutationalpatterns: autopkgtest regression)
Your message dated Tue, 26 May 2020 17:48:40 +
with message-id
and subject line Bug#961572: fixed in r-bioc-mutationalpatterns 2.0.0-2
has caused the Debian Bug report #961572,
regarding r-bioc-mutationalpatterns: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
961572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-mutationalpatterns
Version: 2.0.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 2.0.0-1, r-bioc-mutationalpatterns has been
failing its own autopkgtests [1]. This now prevents the migration of
r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/testing/amd64/
> test_check("MutationalPatterns")
── 1. Error: (unknown) (@test_mut_matrix_stranded.R#3)
there is no package called ‘TxDb.Hsapiens.UCSC.hg19.knownGene’
Backtrace:
1. base::library("TxDb.Hsapiens.UCSC.hg19.knownGene")
── 2. Error: (unknown) (@test_mut_matrix.R#5) ─
there is no package called ‘BSgenome.Hsapiens.UCSC.hg19’
Backtrace:
1. base::library(ref_genome, character.only = TRUE)
── 3. Error: (unknown) (@test_read_vcfs_as_granges.R#5) ───
there is no package called ‘BSgenome.Hsapiens.UCSC.hg19’
Backtrace:
1. base::library(ref_genome, character.only = TRUE)
══ testthat results ═══
[ OK: 0 | SKIPPED: 0 | WARNINGS: 0 | FAILED: 3 ]
1. Error: (unknown) (@test_mut_matrix_stranded.R#3)
2. Error: (unknown) (@test_mut_matrix.R#5)
3. Error: (unknown) (@test_read_vcfs_as_granges.R#5)
Error: testthat unit tests failed
Execution halted
autopkgtest [09:41:10]: test pkg-r-autopkgtest: ---]
autopkgtest [09:41:10]: test pkg-r-autopkgtest: - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-bioc-mutationalpatterns
Source-Version: 2.0.0-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?=
We believe that the bug you reported is fixed in the latest version of
r-bioc-mutationalpatterns, 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.
Dylan Aïssi (supplier of updated r-bioc-mutationalpatterns
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 26 May 2020 19:12:49 +0200
Source: r-bioc-mutationalpatterns
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Dylan Aïssi
Closes: 961572
Changes:
r-bioc-mutationalpatterns (2.0.0-2) unstable; urgency=medium
.
* Team upload.
* Add patch to skip tests requiring packages not in Debian (Closes: #961572)
Checksums-Sha1:
b4ab1ac53dc4dc4551b4586fcb433517656ded32 2545
r-bioc-mutationalpatterns_2.0.0-2.dsc
d73326aa2c11bd094e51b1edfc56f067ed9361b3 3168
r-bioc-mutationalpatterns_2.0.0-2.debian.tar.xz
2a1cc86e76af73c459b4aee8bba1643eb676b9c7 12472
r-bioc-mutationalpatterns_2.0.0-2_amd64.buildinfo
Checksums-Sha256:
a1935ffb280fc1b9a7911120ebcbd04de03c08ca6167c0351a439b0e0e8229d3 2545
r-bioc-mutationalpatterns_2.0.0-2.dsc
8095c33d48a257bfc6ed66a36ce6d698020c524e2bea58a7c20757d1770121e1 3168
r-bioc-mutationalpatterns_2.0.0-2.debian.tar.xz
5a1edb95ff2fabfe3b6abc64911b59339d50618d045251360480f0d1128f84df 12472
r-bioc-mutationalpatterns_2.0.0-2_amd64.buildinfo
Files:
9b66675855f7895139b5d4f441b0e954 2545 gnu-r optional
r-bioc-mutationalpatterns_2.0.0-2.dsc
b774861c55d3421716383c494b4c54c4 3168 gnu-r optional
r-bioc-mutationalpatterns_2.0.0-2.debian.tar.xz
d2bab7ceeed78766ecc82b1c8f4b99da 12472 gnu-r optional
r-bioc-mutationalpatterns_2.0.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl7NUlUACgkQYS7xYT4F
Bug#961561: marked as done (gazebo: Build-Depends on cruft package ttf-dejavu-core)
Your message dated Tue, 26 May 2020 17:33:38 + with message-id and subject line Bug#961561: fixed in gazebo 11.0.0+dfsg1-3 has caused the Debian Bug report #961561, regarding gazebo: Build-Depends on cruft 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.) -- 961561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gazebo Version: 11.0.0+dfsg1-2 Severity: serious As the subject says: src:gazebo has a Build-Depends on ttf-dejavu-core which is no longer built as of src:fonts-dejavu version 2.37-2. As a result, it will only be possible to build on sid using an obsolete binary package, and it won't be possible at all on testing once fonts-dejavu 2.37-2 migrates to testing. -- Daniel Schepler --- End Message --- --- Begin Message --- Source: gazebo Source-Version: 11.0.0+dfsg1-3 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of gazebo, 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. Jochen Sprickerhof (supplier of updated gazebo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 May 2020 19:15:48 +0200 Source: gazebo Architecture: source Version: 11.0.0+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 961561 Changes: gazebo (11.0.0+dfsg1-3) unstable; urgency=medium . * Team upload. * Update build dependency (Closes: #961561) Checksums-Sha1: e5175ae56b776ab39098049d3d2cca0caff77796 3725 gazebo_11.0.0+dfsg1-3.dsc 093c30fd23f6854a0378ed6ba15c87cc78bb30e8 15940 gazebo_11.0.0+dfsg1-3.debian.tar.xz e7e8688ae9279412a6ba3992987df94f95372c8a 8711 gazebo_11.0.0+dfsg1-3_source.buildinfo Checksums-Sha256: e4bb1c21e0925a9a3850b5f35604c65b7f5e6f3bfcfad93d9eb193bf8e6093a5 3725 gazebo_11.0.0+dfsg1-3.dsc a96533f4719ff4ab662dcad3191b0e35d46100691ebf8b88d1e89e5208d77f2c 15940 gazebo_11.0.0+dfsg1-3.debian.tar.xz b2456692edfa3b21a9e879ce90455500092991156dc25ba25aef414ca071f3a1 8711 gazebo_11.0.0+dfsg1-3_source.buildinfo Files: bc99aa589ccc87395122d023b65bf687 3725 science optional gazebo_11.0.0+dfsg1-3.dsc eb951769d4b0673efe595cfaad10e11c 15940 science optional gazebo_11.0.0+dfsg1-3.debian.tar.xz 8fa60389179afd23807a67f4875f97da 8711 science optional gazebo_11.0.0+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl7NTx4ACgkQW//cwljm lDO3mxAAlnzPuTkWnhcIY16NUtxR5fjB+H4ctkcQwyCzJLm43wFiWGyxMiLrAc45 OBUMuPUAMmjywgJJphaNEYDHfIpWgO7mZxrwON0nNJRkoo7kKi1/lyk8mlDVDAVU 5nUkHOAzlcjCEAPiDJquqlUgE1Kod4dKC+fvMoeuN85+NTq8rvu2UN5eu9aCMpkX 9IV/Jr3nViSwdSyyQe6I5YGmuIYPP7GRRs/TkGqhm7CjFzI1bvMK9zQ5MUYN95CA EZN2PtECNnTbA5aMZalf+0ZgSyn2QuayGml8ZoxGDbPSJ17QtAVX3bZfLnoUAEaI 1rYkIvcCgPvSAxhh9l6NvZqkkvcbz8bOFbM57q4Hy+JZgA2q4v8eLz2q4MyMCvJ7 UUtVL8wXVhl2G6fkuJFPUIkUwD713I2tfMzSkJqdWHzJDpNrk7yLSankX2D4KK7i ADF8sShTYXbhl7uIWJ2765HIEcolTIYYugpdUsa+DiWJPdn+5nm3yPoSZX6ku8z2 RXFWdYsiBBVsYsle1/DPKTn87xLhMCZWVEMAe9dBx0aJAyoE9JkDm15vjDjAFAEa LXVrIV7vH3q/fNwRr2hcaAUoS1ohNJ/OE5/ecjmP79PwVqLny2kGIVj8OChqy7Gb p5h23USciVRXE64mtPStDlthqcJWhzRd3/VT3Rbh1luET50vqmI= =iaA9 -END PGP SIGNATURE End Message ---
Bug#937621: marked as done (python-box2d: Python2 removal in sid/bullseye)
Your message dated Tue, 26 May 2020 17:24:06 + with message-id and subject line Bug#961617: Removed package(s) from unstable has caused the Debian Bug report #937621, regarding python-box2d: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-box2d Version: 2.3.2~dfsg-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-box2d If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.3.2~dfsg-2+rm Dear submitter, as the package python-box2d has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/961617 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938610: marked as done (swap-cwm: Python2 removal in sid/bullseye)
Your message dated Tue, 26 May 2020 17:23:35 + with message-id and subject line Bug#961607: Removed package(s) from unstable has caused the Debian Bug report #938610, regarding swap-cwm: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:swap-cwm Version: 1.2.1-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:swap-cwm If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.2.1-7+rm Dear submitter, as the package swap-cwm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/961607 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#952010: marked as done (flask-oauthlib: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.7" returned exit code 13)
Your message dated Tue, 26 May 2020 17:23:14 +
with message-id
and subject line Bug#961586: Removed package(s) from unstable
has caused the Debian Bug report #952010,
regarding flask-oauthlib: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.8 3.7" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
952010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-oauthlib
Version: 0.9.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config
> running config
> I: pybuild base:217: python3.7 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.8 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/__init__.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/client.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/utils.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib
> creating
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider
> copying flask_oauthlib/provider/oauth1.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider
> copying flask_oauthlib/provider/__init__.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider
> copying flask_oauthlib/provider/oauth2.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/provider
> creating
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib
> copying flask_oauthlib/contrib/cache.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib
> copying flask_oauthlib/contrib/apps.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib
> copying flask_oauthlib/contrib/__init__.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib
> copying flask_oauthlib/contrib/oauth2.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib
> creating
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/application.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/__init__.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/descriptor.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/exceptions.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/signals.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> copying flask_oauthlib/contrib/client/structure.py ->
> /<>/.pybuild/cpython3_3.8_flask-oauthlib/build/flask_oauthlib/contrib/client
> running egg_info
> creating Flask_OAuthlib.egg-info
> writing Flask_OAuthlib.egg-info/PKG-INFO
> writing dependency_links to Flask_OAuthlib.egg-info/dependency_links.txt
> writing requirements to Flask_OAuthlib.egg-info/requires.txt
> writing top-level names to Flask_OAuthlib.egg-info/top_level.txt
> writing manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt'
> reading manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'Flask_OAuthlib.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/__init__.py ->
> /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/client.py ->
> /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib
> copying flask_oauthlib/utils.py ->
> /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib
> creating
> /<>/.pybuild/cpython3_3.7_flask-oauthlib/build/flask_oauthlib/provider
>
Bug#961571: marked as done (r-cran-vctrs: autopkgtest regression)
Your message dated Tue, 26 May 2020 17:18:27 +
with message-id
and subject line Bug#961571: fixed in r-cran-vctrs 0.3.0-2
has caused the Debian Bug report #961571,
regarding r-cran-vctrs: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
961571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-vctrs
Version: 0.3.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.3.0-1, r-cran-vctrs has been failing its own
autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-vctrs/unstable/amd64/
> library(testthat)
> library(vctrs)
>
> if (requireNamespace("xml2")) {
+ test_check("vctrs", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"),
CheckReporter$new(
+ } else {
+ test_check("vctrs")
+ }
Loading required namespace: xml2
Failed with error: ‘there is no package called ‘xml2’’
── 1. Error: grouped-df is proxied and restored (@test-type-dplyr.R#7)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 2. Error: can take the common type of grouped tibbles and tibbles (@test-type
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 3. Error: the common type of grouped tibbles includes the union of grouping v
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 4. Error: can cast to and from `grouped_df` (@test-type-dplyr.R#45)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 5. Error: casting to `grouped_df` doesn't require grouping variables (@test-t
there is no package called ‘dplyr’
Backtrace:
1. testthat::expect_identical(...)
5. dplyr::group_by
6. base::getExportedValue(pkg, name)
7. base::asNamespace(ns)
8. base::getNamespace(ns)
9. base::loadNamespace(name)
10. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
11. base:::withOneRestart(expr, restarts[[1L]])
12. base:::doWithOneRestart(return(expr), restart)
── 6. Error: casting to `grouped_df` handles `drop` (@test-type-dplyr.R#82) ───
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 7. Error: can cbind grouped data frames (@test-type-dplyr.R#87)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 8. Error: rowwise can be proxied and restored (@test-type-dplyr.R#107) ─
there is no package called ‘dplyr’
Backtrace:
1. dplyr::rowwise
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi josch,
Johannes Schauer wrote:
> > If it's similar as with mk-ci-build-deps above, this is likely a bug in
> > mk-build-deps then, just triggered by equivs.
>
> Again, I don't want to be confrontational here.
Ok. Already forgotten. :-)
> I don't understand as much
> about equivs as you do. But what I tested is completely independent from
> mk-build-deps. What I tried was running:
>
> equivs-build /usr/share/doc/equivs/examples/webserver.ctl
>
> And I got the same error as Otto ("Unmet build dependencies:
> build-essential:native")
Sorry, it took me quite a while to realise that I couldn't reproduce
the problem because even in the "clean" pbuilder chroot (which is
meant for building packages) build-essential is pre-installed and
hence the build succeeds. I of course also have it installed
everywhere else where I work on equivs, too.
Then again, a hard dependency on build-essential which pulls in gcc
and g++ is definitely way too much for equivs which is aimed to be
quick and lightweight.
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.
Will first implement this.
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.
Will likely implement this afterwards.
Will then also merge your autopkgtest checks as they should show as
well that (or if ;-) this variant works.
P.S.: The workaround for now is to install build-essential even if not
used in the end.
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#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Quoting Otto Kekäläinen (2020-05-26 15:56:04) > Yes, installing build-essential manually has been the work-around I've > been using. So that is now the permanent solution? No, I think that now that equivs always uses dpkg-buildpackage instead of manually invoking debian/rules it *must* depend on build-essential because unless you tell dpkg-buildpackage to skip checking build dependencies, the build-essential packages is required due to its call to dpkg-checkbuilddeps. So as a workaround you could either: - install packages with recommends enabled (this will install build-essential because dpkg-dev recommends it) - or install build-essential manually But the long-term solution is probably to add build-essential to the Depends of equivs. signature.asc Description: signature
Bug#961606: sklearn-pandas: FTBFS: doctest error
Source: sklearn-pandas
Version: 1.8.0-1
Severity: grave
Justification: FTBFS
X-Debbugs-CC: m...@cbaines.net feder...@debian.org
Dear Debian sklearn-pandas maintainers,
During a rebuild of your package, I found that your package currently
fails to build from source.
1 items had failures:
5 of 63 in README.rst
63 tests in 1 items.
58 passed and 5 failed.
***Test Failed*** 5 failures.
E: pybuild pybuild:352: test: plugin distutils failed with: exit
code=1: cd /<>/.pybuild/cpython3_3.8_sklearn-pandas/build;
python3.8 -m pytest ; cd {dir}; python{version} -m doctest -v
README.rst
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.8 returned exit code 13
make: *** [debian/rules:7: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2
The full buildlog can be found in the attachment.
--
Regards,
Boyuan Yang
sbuild (Debian sbuild) 0.79.1 (22 April 2020) on hosiet-vm-home
+==+
| sklearn-pandas 1.8.0-1 (amd64) Tue, 26 May 2020 15:17:20 + |
+==+
Package: sklearn-pandas
Version: 1.8.0-1
Source Version: 1.8.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-03b399fa-6319-4a5f-82b3-6239d9035e87'
with '<>'
I: NOTICE: Log filtering will replace
'build/sklearn-pandas-9jnbV1/resolver-Zf4TNH' with '<>'
+--+
| Update chroot|
+--+
Hit:1 http://deb.debian.org/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+--+
| Fetch source files |
+--+
Local sources
-
/dev/shm/sklearn-pandas_1.8.0-1.dsc exists in /dev/shm; copying to chroot
I: NOTICE: Log filtering will replace
'build/sklearn-pandas-9jnbV1/sklearn-pandas-1.8.0' with '<>'
I: NOTICE: Log filtering will replace 'build/sklearn-pandas-9jnbV1' with
'<>'
+--+
| Install package build dependencies |
+--+
Setup apt archive
-
Merged Build-Depends: debhelper-compat (= 12), build-essential, fakeroot,
dh-python, python3-all, python3-setuptools, python3-mock, python3-pytest,
python3-numpy, python3-pandas, python3-sklearn
Filtered Build-Depends: debhelper-compat (= 12), build-essential, fakeroot,
dh-python, python3-all, python3-setuptools, python3-mock, python3-pytest,
python3-numpy, python3-pandas, python3-sklearn
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [420 B]
Get:5 copy:/<>/apt_archive ./ Packages [501 B]
Fetched 1878 B in 0s (148 kB/s)
Reading package lists...
Reading package lists...
Install main build dependencies (apt-based resolver)
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdmainutils debhelper
dh-autoreconf dh-python dh-strip-nondeterminism dwz file gettext
gettext-base groff-base intltool-debian libarchive-zip-perl libblas3 libbsd0
libcroco3 libdebhelper-perl libelf1 libexpat1
libfile-stripnondeterminism-perl libgfortran5 libglib2.0-0 libicu63
liblapack3 liblbfgsb0 libmagic-mgc libmagic1 libmpdec2 libncurses6
libncursesw6 libpipeline1 libprocps8 libpython3-stdlib libpython3.8-minimal
libpython3.8-stdlib libreadline8 libsigsegv2 libsqlite3-0 libssl1.1
libsub-override-perl libtool libuchardet0 libxml2 m4 man-db mime-support
po-debconf procps python3 python3-all python3-atomicwrites python3-attr
python3-dateutil python3-decorator python3-distutils
python3-importlib-metadata python3-joblib python3-lib2to3 python3-minimal
python3-mock python3-more-itertools python3-numpy python3-packaging
python3-pandas python3-pandas-lib python3-pbr python3-pkg-resources
python3-pluggy
Bug#961602: castle-game-engine-doc: Depends on removed ttf-dejavu packages
Package: castle-game-engine-doc Severity: grave Version: 6.4+dfsg1-3 Tags: sid bullseye X-Debbugs-CC: abou.almonta...@sfr.fr elb...@debian.org Dear Debian castle-game-engine packagers, Recent changes in Debian fonts-dejavu package (2.37-2) dropped the old transitional package ttf-dejavu, ttf-dejavu-core and ttf-dejavu-extra. [1][2] Your package still depends on them, thus will become uninstallable. As you can see in https://codesearch.debian.net/search?q=package%3Acastle-game-engine+ttf-dejavu=0 , your package is using hardcoded paths that points to the lagacy location of the font. Please make another upload and use the new paths provided by fonts-dejavu package. [1] https://tracker.debian.org/news/1146775/accepted-fonts-dejavu-237-2-source-into-unstable/ [2] https://bugs.debian.org/872809 -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#948087: future of aufs in Debian.
Dear Peter, I am in general still active but due to private stuff I was quite bad maintaining aufs the last months, I am really sorry. I will try to take a look into the package at the weekend. Additionally, I will create a RFH bug, maybe somebody wants to help me so there is no single point of failure in the future. Best, Jan On 26.05.20 15:18, peter green wrote: > The aufs package last saw a maintainer upload in September 2019 and was > last-updated (by a NMU) in October 2019. It has had broken > build-dependencies in testing for half a year now (since Linux 5.3.9-3 > migrated to testing in November 2019). > > According to dak rm the aufs source-package has two > reverse-dependencies, aufs-tools and fsprotect neither of which has any > reverse-dependencies. > > Adrian filed a rc bug in November 2019 which received no maintainer > response, however the package was not autoremoved from testing due to > aufs and aufs-tools being considered a "key packages" due to high > popcon. This popcon actually seems to be growing in both absolute and > percentage terms. I presume the high popcon is due to some deriviative > (hence debian-derivatives and debian-live in cc) using aufs in their > live image builds (as far as I can tell debian's own live images seem to > use overlayfs instead nowadays). > > aufs does seem to still be maintained upstream with upstream claiming > support for Linux 5.6. > > According to contributors.debian.net Jan Luca Naumann (the aufs > maintainer) was last active in September 2019. Jan: are you still > around? and if so do you still intend to maintain the aufs package? if > not is someone else going to step up to the plate? or should these > packages be removed from testing?
Bug#952292: marked as done (libgroovycsv-java: outdated opencsv groupId in the pom)
Your message dated Tue, 26 May 2020 14:34:08 + with message-id and subject line Bug#952292: fixed in groovycsv 1.3-2 has caused the Debian Bug report #952292, regarding libgroovycsv-java: outdated opencsv groupId in the pom 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.) -- 952292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: graxxia Version: 1.0~20150714-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=gradle --with maven-repo-helper >dh_update_autotools_config -O--buildsystem=gradle >dh_auto_configure -O--buildsystem=gradle >dh_auto_build -O--buildsystem=gradle > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=graxxia -Dfile.encoding=UTF-8 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@48c35007 > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@48c35007 > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4b4dd216 > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@109f8c7e > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file not found (/<>/settings.gradle) > Root project name not defined in settings.gradle, defaulting to > 'graxxia' instead of the name of the root directory 'graxxia-1.0~20150714' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'graxxia'] > Keep-alive timer started > Adding Debian repository to project 'graxxia' > Evaluating root project 'graxxia' using build file > '/<>/build.gradle'. > Compiling build file '/<>/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/build.gradle' using > BuildScriptTransformer. > The Task.leftShift(Closure) method has been deprecated and is scheduled to be > removed in Gradle 5.0. Please use Task.doLast(Action) instead. > at org.gradle.api.internal.AbstractTask.leftShift(AbstractTask.java:618) > at org.gradle.api.Task$leftShift.call(Unknown Source) > at > org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47) > at > org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) > at > org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128) > at build_16bxdbb0pkgn7irvu3tz8ifl1.run(/<>/build.gradle:32) > at > org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:199) > at > org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) > at > org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:204) > at >
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Yes, installing build-essential manually has been the work-around I've been using. So that is now the permanent solution?
Bug#948087: future of aufs in Debian.
On Tue, May 26, 2020 at 02:18:48PM +0100, peter green wrote: >... > Adrian filed a rc bug in November 2019 which received no maintainer response, > however the package was not autoremoved from testing due to aufs and > aufs-tools being considered a "key packages" due to high popcon. This popcon > actually seems to be growing in both absolute and percentage terms. I presume > the high popcon is due to some deriviative (hence debian-derivatives and > debian-live in cc) using aufs in their live image builds (as far as I can > tell debian's own live images seem to use overlayfs instead nowadays). >... It doesn't have to be a derivative, one webhoster who installs popcon by default is enough. phpmyadmin in stretch was a similar case, it went up to 10% popcon despite nothing in Debian installing it by default and no reverse dependencies (only a Suggests from a package with single-digit popcon). When the release team went through RC bugs key packages closer to the freeze phpmyadmin was removed from testing (and is not in buster). cu Adrian
Processed: Re: Bug#961563: crash: Build failure due to parallel execution
Processing control commands: > severity -1 normal Bug #961563 [src:crash] crash: Build failure due to parallel execution Severity set to 'normal' from 'serious' > tags -1 - ftbfs Bug #961563 [src:crash] crash: Build failure due to parallel execution Removed tag(s) ftbfs. -- 961563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#952292 marked as pending in groovycsv
Processing control commands: > tag -1 pending Bug #952292 [libgroovycsv-java] libgroovycsv-java: outdated opencsv groupId in the pom Added tag(s) pending. -- 952292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961563: crash: Build failure due to parallel execution
Control: severity -1 normal Control: tags -1 - ftbfs On Tue, May 26, 2020 at 11:58:19AM +0900, Benjamin Poirier wrote: > Source: crash > Severity: serious > Tags: upstream patch ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > The crash package sometimes fails to build when dpkg-buildpackage is > invoked with -j > 1: > > # dpkg-buildpackage -us -uc -j4 >... You are not the first person to fall into this trap. -j, --jobs[=jobs|auto] Number of jobs allowed to be run simultaneously, number of jobs matching the number of online processors if auto is specified (since dpkg 1.17.10), or unlimited number if jobs is not specified, equivalent to the make(1) option of the same name (since dpkg 1.14.7, long option since dpkg 1.18.8). Will add itself to the MAKEFLAGS environment variable, which should cause all subsequent make invocations to inherit the option, thus forcing the parallel setting on the packaging (and possibly the upstream build system if that uses make) regardless of their support for parallel builds, which might cause build failures. -J is the correct dpkg-buildpackage option. > This is because crash's configure rewrites Makefile via a temporary file > (Makefile.new) and it is now getting invoked multiple times in parallel. > This is a problem upstream. Correct. > It can be avoided with the following change: > --- a/debian/rules > +++ b/debian/rules > @@ -12,8 +12,7 @@ include /usr/share/dpkg/buildflags.mk > dh $@ > > override_dh_auto_build: > - dh_auto_build > - $(MAKE) extensions lzo snappy > + dh_auto_build -- all extensions lzo snappy >... This would fix only the "dpkg-buildpackage -j1" case, "dh $@ --parallel" would still fail due to make -j4 all extensions lzo snappy The correct workaround to enable parallel building is: %: dh $@ --parallel override_dh_auto_build: $(MAKE) $(MAKE) extensions $(MAKE) lzo $(MAKE) snappy cu Adrian
Processed: retitle 952292 to libgroovycsv-java: outdated opencsv groupId in the pom
Processing commands for cont...@bugs.debian.org: > retitle 952292 libgroovycsv-java: outdated opencsv groupId in the pom Bug #952292 [libgroovycsv-java] graxxia: FTBFS: No cached version of net.sf.opencsv:opencsv:debian available for offline mode. Changed Bug title to 'libgroovycsv-java: outdated opencsv groupId in the pom' from 'graxxia: FTBFS: No cached version of net.sf.opencsv:opencsv:debian available for offline mode.'. > thanks Stopping processing here. Please contact me if you need assistance. -- 952292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952292: marked as pending in groovycsv
Control: tag -1 pending Hello, Bug #952292 in groovycsv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/groovycsv/-/commit/0cea0e079f09240a98099224ebfd70382ee155cf Updated the opencsv groupId in the pom (Closes: #952292) (this message was generated automatically) -- Greetings https://bugs.debian.org/952292
Bug#855837: closing 855837
# stetch shipped ages ago close 855837 thanks -- ð±ð»Jonathan Dowland â j...@dow.land ðhttps://jmtd.net
Bug#936146: archivemail - Python 3 porting
On Thu, May 14, 2020 at 03:31:31PM -0400, Scott Talbert wrote: archivemail seems to be a good candidate to RM due to dead upstream. However, it still has a relatively high popcon, so people seem to be using it. I'm willing to take a stab at porting to Python 3 if anyone is available to test it? The port effort doesn't look that bad at first glance, but I don't use this package. I'm happy to test anything you produce, but I'd warn you that I think it's quite a significant piece of work. From what I remember when I last looked at hacking a feature into it (#736327), archivemail uses the older of two different APIs provided by the python "mailbox" library, and only the newer one was carried forward to Python 3. So moving away from that older API is a big part of the work. -- Jonathan Dowland ✎j...@debian.org https://jmtd.net
Processed: tagging 936173, tagging 961506, found 961507 in 0.1.8-2
Processing commands for cont...@bugs.debian.org:
> tags 936173 + experimental
Bug #936173 {Done: Simon McVittie } [src:avahi] avahi: Python2
removal in sid/bullseye
Added tag(s) experimental.
> tags 961506 + sid bullseye
Bug #961506 {Done: Xavier Guimard } [src:vows] vows:
unmaintained in Debian
Added tag(s) sid and bullseye.
> found 961507 0.1.8-2
Bug #961507 [src:eyes.js] eyes.js: unmaintained in Debian
Marked as found in versions eyes.js/0.1.8-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936173
961506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961506
961507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 855837
Processing commands for cont...@bugs.debian.org: > # stetch shipped ages ago > close 855837 Bug #855837 [golang-petname] golang-petname: Do not include in stretch at request of maintainer Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 855837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948087: future of aufs in Debian.
The aufs package last saw a maintainer upload in September 2019 and was last-updated (by a NMU) in October 2019. It has had broken build-dependencies in testing for half a year now (since Linux 5.3.9-3 migrated to testing in November 2019). According to dak rm the aufs source-package has two reverse-dependencies, aufs-tools and fsprotect neither of which has any reverse-dependencies. Adrian filed a rc bug in November 2019 which received no maintainer response, however the package was not autoremoved from testing due to aufs and aufs-tools being considered a "key packages" due to high popcon. This popcon actually seems to be growing in both absolute and percentage terms. I presume the high popcon is due to some deriviative (hence debian-derivatives and debian-live in cc) using aufs in their live image builds (as far as I can tell debian's own live images seem to use overlayfs instead nowadays). aufs does seem to still be maintained upstream with upstream claiming support for Linux 5.6. According to contributors.debian.net Jan Luca Naumann (the aufs maintainer) was last active in September 2019. Jan: are you still around? and if so do you still intend to maintain the aufs package? if not is someone else going to step up to the plate? or should these packages be removed from testing?
Processed: severity of 960656 is important
Processing commands for cont...@bugs.debian.org: > severity 960656 important Bug #960656 [src:sdpb] sdpb: FTBFS on mipsel Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 960656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 952292
Processing commands for cont...@bugs.debian.org: > affects 952292 graxxia Bug #952292 [libgroovycsv-java] graxxia: FTBFS: No cached version of net.sf.opencsv:opencsv:debian available for offline mode. Added indication that 952292 affects graxxia > thanks Stopping processing here. Please contact me if you need assistance. -- 952292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 952292 to libgroovycsv-java
Processing commands for cont...@bugs.debian.org: > reassign 952292 libgroovycsv-java Bug #952292 [src:graxxia] graxxia: FTBFS: No cached version of net.sf.opencsv:opencsv:debian available for offline mode. Bug reassigned from package 'src:graxxia' to 'libgroovycsv-java'. No longer marked as found in versions graxxia/1.0~20150714-2. Ignoring request to alter fixed versions of bug #952292 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 952292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961490: fwupd: version in stable too old, no updates possible
Hi, On Tue, 2020-05-26 at 13:56 +0200, Steffen Schreiber wrote: > So I see you marked this bug as fixed/resolved. Someone (not the maintainer) did so, but please note that the bug remains open even when marked as fixed in a newer version. Debian's stable release team prefers bugs to be fixed in unstable/testing before they get fixed in (old)stable, so this is good. > What's the way going forward for users of stable? Installing packages > from testing? Are you recommending to just forget about running Debian > stable as is? The maintainer hasn't yet commented on how he wants to proceed. Reasonable options seem to be to either update stable to the version currently in testing (1.3.9) or to update to a later version of 1.2.X. Ansgar
Bug#936173: marked as done (avahi: Python2 removal in sid/bullseye)
Your message dated Tue, 26 May 2020 12:33:38 + with message-id and subject line Bug#936173: fixed in avahi 0.8-3 has caused the Debian Bug report #936173, regarding avahi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:avahi Version: 0.7-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:avahi If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: avahi Source-Version: 0.8-3 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of avahi, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated avahi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 May 2020 11:33:06 +0100 Source: avahi Architecture: source Version: 0.8-3 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Simon McVittie Closes: 853239 936173 Changes: avahi (0.8-3) unstable; urgency=medium . * Team upload * Upload python3-avahi to unstable * d/control: Add comments about why some packages are Arch: any. At first glance these packages seem like they should be Architecture: all, but in fact they cannot. * d/control, d/shlibs.local: Tighten interdependencies within src:avahi. Co-installation of binary packages built from different versions of the same source package is error-prone, because parts of the same source package typically make assumptions about non-public exported symbols, implementation details or precise behaviour beyond what's in the public API. Upstream developers are also unlikely to be willing to support such installations or make
Bug#961592: r-bioc-gviz: autopkgtest regression
Source: r-bioc-gviz
Version: 1.32.0+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 1.32.0+dfsg-1, r-bioc-gviz has been failing its
own autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-gviz/unstable/amd64/
> test_check("Gviz")
Error in library(BSgenome.Hsapiens.UCSC.hg19) :
there is no package called 'BSgenome.Hsapiens.UCSC.hg19'
Calls: test_check ... source_dir -> lapply -> FUN -> eval -> eval -> library
Execution halted
autopkgtest [15:02:19]: test pkg-r-autopkgtest: ---]
autopkgtest [15:02:19]: test pkg-r-autopkgtest: - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
Bug#961591: r-bioc-graph: autopkgtest regression
Source: r-bioc-graph
Version: 1.66.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 1.66.0-1, r-bioc-graph has been failing its own
autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-graph/unstable/amd64/
> BiocGenerics:::testPackage("graph", pattern="_test.R")
Attaching package: ‘BiocGenerics’
The following objects are masked from ‘package:parallel’:
clusterApply, clusterApplyLB, clusterCall, clusterEvalQ,
clusterExport, clusterMap, parApply, parCapply, parLapply,
parLapplyLB, parRapply, parSapply, parSapplyLB
The following objects are masked from ‘package:stats’:
IQR, mad, sd, var, xtabs
The following objects are masked from ‘package:base’:
anyDuplicated, append, as.data.frame, basename, cbind, colnames,
dirname, do.call, duplicated, eval, evalq, Filter, Find, get, grep,
grepl, intersect, is.unsorted, lapply, Map, mapply, match, mget,
order, paste, pmax, pmax.int, pmin, pmin.int, Position, rank,
rbind, Reduce, rownames, sapply, setdiff, sort, table, tapply,
union, unique, unsplit, which, which.max, which.min
Timing stopped at: 0.002 0 0.002
Error in checkEquals("not a node: 'not-a-node'", conditionMessage(ans)) :
1 string mismatch
RUNIT TEST PROTOCOL -- Tue May 26 07:01:18 2020
***
Number of test functions: 206
Number of errors: 0
Number of failures: 1
1 Test Suite :
graph RUnit Tests - 206 test functions, 0 errors, 1 failure
FAILURE in testInEdges: Error in checkEquals("not a node:
'not-a-node'", conditionMessage(ans)) :
1 string mismatch
Test files with failing tests
graphNEL_test.R
testInEdges
Error in BiocGenerics:::testPackage("graph", pattern = "_test.R") :
unit tests failed for package graph
Execution halted
autopkgtest [07:01:18]: test pkg-r-autopkgtest: ---]
autopkgtest [07:01:18]: test pkg-r-autopkgtest: - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
Bug#961501: remmina is calling home for update notifications
On Di 26 Mai 2020 10:00:56 CEST, Antenore Gatta wrote: [...] Thanks for your understanding on this issue, Antenore. Much appreciated. I prefere to relase a clean and cleaned 1.4.6 version than playing with workaround patches that may introduce other bugs Yeah, I think getting this fixed in the next upstream release is fair enough. Thanks a lot, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpU0ykxhGp5U.pgp Description: Digitale PGP-Signatur
Bug#959588: marked as done (flask-assets: FTBFS: FAIL: Test how we resolve file references through the Flask static)
Your message dated Tue, 26 May 2020 12:03:50 +
with message-id
and subject line Bug#959588: fixed in flask-assets 2.0-1
has caused the Debian Bug report #959588,
regarding flask-assets: FTBFS: FAIL: Test how we resolve file references
through the Flask static
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.)
--
959588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-assets
Version: 0.12-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated
> (level 9 in use)
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying src/flask_assets.py ->
> /<>/.pybuild/cpython3_3.8_flask-assets/build
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
> in use)
> I: pybuild base:217: cd
> /<>/.pybuild/cpython3_3.8_flask-assets/build; python3.8 -m nose
> -v tests
> Custom config values are relayed to the Flask config as.is. ... ok
> Ensure that the webassets defaults do not override existing ... ok
> Setting a value in the Flask config works. ... ok
> Setting a config value on the environment works. ... ok
> We may set defaults even without an application, however. ... ok
> KeyError is raised if a config value doesn't exist. ... ok
> Each app has it's own separate configuration. ... ok
> Without an application bound, we can't do much. ... ok
> Python configuration module gets loaded ... ok
> YAML configuration gets loaded ...
> /usr/lib/python3/dist-packages/webassets/loaders.py:162: YAMLLoadWarning:
> calling yaml.load() without Loader=... is deprecated, as the default Loader
> is unsafe. Please read https://msg.pyyaml.org/load for full details.
> obj = self.yaml.load(f) or {}
> ok
> Jinja tag has been made available. ... ok
> Test dealing with a blueprint without a static folder. ... ok
> [Regression] Output can point to a blueprint's static ... ok
> Urls to blueprint files are generated correctly. ... ok
> Make sure cssrewrite works with Blueprints. ... ok
> tests.test_integration.TestBuild.test_build ... ok
> [Regression] The cache directory is created in the Flask ... ok
> tests.test_integration.TestUrlAndDirectory.test_config_values_not_set_by_default
> ... ok
> Custom directory/url are configured - this will affect how ... ok
> A custom load_path is configured - this will affect how ... ok
> Test how we resolve file references through the Flask static ... FAIL
> [Regression] Check for a bug where the url generation code of ... ok
> Make sure url generation works with globs. ... ok
> Test how urls are generated via the Flask static system ... ok
> Make sure the "url" and "directory" config values are ... ok
> tests.test_integration.test_import ... ok
> tests.test_script.TestScript.test_call ... ok
> Regression test: Passing the environment to the ManageAssets command ... ok
> Test the --parse-templates option. ... ok
>
> ==
> FAIL: Test how we resolve file references through the Flask static
> --
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> File
> "/<>/.pybuild/cpython3_3.8_flask-assets/build/tests/test_integration.py",
> line 69, in test_directory_auto
> assert get_all_bundle_files(Bundle('foo'), self.env) == ['/foo']
> AssertionError
>
> --
> Ran 29 tests in 0.073s
>
> FAILED (failures=1)
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.8_flask-assets/build; python3.8 -m nose
> -v tests
> dh_auto_test: error: pybuild --test --test-nose -i
Bug#952348: marked as done (backupchecker: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Seq
Your message dated Tue, 26 May 2020 12:03:37 + with message-id and subject line Bug#952348: fixed in backupchecker 1.7-2 has caused the Debian Bug report #952348, regarding backupchecker: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 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.) -- 952348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: backupchecker Version: 1.7-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean --with python3 > dh: error: unable to load addon python3: Can't locate > Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the > Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 > /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 > /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) > line 1. > BEGIN failed--compilation aborted at (eval 10) line 1. > > make: *** [debian/rules:6: clean] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/02/22/backupchecker_1.7-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: backupchecker Source-Version: 1.7-2 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of backupchecker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated backupchecker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 May 2020 11:05:44 + Source: backupchecker Architecture: source Version: 1.7-2 Distribution: unstable Urgency: medium Maintainer: Carl Chenet Changed-By: Jelmer Vernooij Closes: 952348 Changes: backupchecker (1.7-2) unstable; urgency=medium . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python3-Version field * Use debhelper-compat instead of debian/compat. . [ Nilesh Patra ] * Add dh-python to build depends (Closes: #952348) * Update debian/upstream/metadata. . [ Jelmer Vernooij ] * Trim trailing whitespace. * Bump debhelper from deprecated 9 to 12. * Fix day-of-week for changelog entry 1.1-1. Checksums-Sha1: 256c1340d35872e1972a9d5f4a0bfd5b484d20b2 2025 backupchecker_1.7-2.dsc 741ecd3c70c54bdc31c25731dbbeff32da344fbb 2288 backupchecker_1.7-2.debian.tar.xz 280221c5723fd5fb00f204430c93bd8323da515c 5862 backupchecker_1.7-2_amd64.buildinfo Checksums-Sha256: b7826ace47ec9a082990eddf57ded34c0d84387c97f73ed5bb6b1a0df2c31bd4 2025 backupchecker_1.7-2.dsc 4c6b38b188491230fa4318b6c7b4fce6ec403f8b746551f30acec711ba4bbda6 2288 backupchecker_1.7-2.debian.tar.xz fe7d2c3af8281e7cd3454d33c95e958261bce6a697508437d4a261f3e43ac7ad 5862 backupchecker_1.7-2_amd64.buildinfo Files: f1e90a0e8f7d1e357a2bc9b6747578ca 2025 python optional backupchecker_1.7-2.dsc d618a7a6f7c0dc018171f2c7ec9ff8b6 2288 python optional
Bug#961490: fwupd: version in stable too old, no updates possible
Dear Maintainer So I see you marked this bug as fixed/resolved. I understand that the problem is solved with a newer version of fwupd, but to my understanding, the bug is still relevant for stable, and it renders fwupd useless for all users of stable. What's the way going forward for users of stable? Installing packages from testing? Are you recommending to just forget about running Debian stable as is? When current testing becomes the new stable, how can you be sure, that upstream will not break compatibility again, making the package in stable useless again one day after the release? I would have hoped for a little more communication when users take care to report bugs. Best Regards, Steffen
Bug#961588: user-mode-linux, build-depends on obsolete package
Source: user-mode-linux Version: 5.5um1 Severity: serious user-mode-linux build-depends on linux-source-5.5 which is no longer available in testing.
Bug#961581: pbcopper: ftbfs on ppc64el
Control: tags -1 pending Hi Michael, thanks for the patch. I've uploaded pbcopper to new since it needed a soname bump and thus a new binary package name. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#961581: pbcopper: ftbfs on ppc64el
Processing control commands: > tags -1 pending Bug #961581 [src:pbcopper] pbcopper: ftbfs on ppc64el Added tag(s) pending. -- 961581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi Otto, On Tue, 21 Apr 2020 21:54:57 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > I noticed my builds started failing today with error message: > > Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i > control -t 'apt-get -y -o Debug::pkgProblemResolver=yes > --no-install-recommends' > ---> Running in 912092c7ebbd > dpkg-buildpackage: info: source package mariadb-10.5-build-deps > dpkg-buildpackage: info: source version 1.0 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by root > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > dpkg-checkbuilddeps: error: Unmet build dependencies: build-essential:native > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > Error in the build process: exit status 3 > dpkg: error: cannot access archive > 'mariadb-10.5-build-deps_1.0_amd64.deb': No such file or directory > mk-build-deps: dpkg --unpack failed > The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive mk-build-deps > -r -i control -t 'apt-get -y -o Debug::pkgProblemResolver=yes > --no-install-recommends'' returned a non-zero code: 2 > > I am pretty sure this is related to the recent equivs 2.3.0 release, > but I have not figured out the details yet. > > > Run the attached Dockerfile to reproduce. could you try adding the package build-essential to the "apt-get install" command in your Dockerfile and see if the problem persists? I think the trivial reason for this issue is, that equivs now always uses dpkg-buildpackage (see #880165 or commit c1f8ba) but it didn't add a dependency on build-essential. The build-essential package is only a Recommends of dpkg-dev and thus it is not guaranteed to be installed just by depending on dpkg-dev. Thanks! cheers, josch signature.asc Description: signature
Bug#961501: remmina is calling home for update notifications
Hi Mike, Thanks for your detailed answer. On Monday, May 25, 2020 11:55:00 PM CEST Mike Gabriel wrote: > Debian users expect from Debian, to be a safe harbour, so all package > maintainers are requested to patch out code that does unwanted / > uncontrollable connections to the internet for stats collections and > such. I perfectly understand your point, we are working to fix this and it will take some days of work (in our limited free overnight time). > While I understand the interest in usage statistics, in Debian we > cannot have that part of the phoning-home code. I am sorry. This widget is not about usage statistics, that are already opt-in only. This widget informs the user about new Remmina versions and changes. No more no less. Just to clarify ;-) > > > Remmina on a regular basis verify if there's a new file or if the file of > > the version requested (the PHP parameter) has been changed/updated. > > Thanks for the explanation of the mechanism. > > > We do this to notify users about new versions, especially when there are > > important bugs that have been fixed. > > This is not helpful in a GNU distribution using a conservative-style > release model (not sure if this is the correct term) like Debian does. > Imagine Debian stable and oldstable users being reminded of their > software being out of date on every upstream release. Of course, their > software is out of date, as they use remmina from Debian (old)stable > (not testing/unstable). They get those notifications but cannot do > anything about it (except upgrading to Debian testing). This is a good point. I agree. > > So, also from a usability point of view, those notification windows > will be a disturbance to the users of Debian. > > > Libreoffice does something similar for instance and other software, > > in Debian, > > as well. > > Really? Than this must be considered as a bug. Which other packages > have you observed doing this? Regarding Libreoffice I see is not the case anymore since a long time, sorry. I don't have evidence of other software at the moment, if I find any I'll fill a bug as well. > > > I understand it may be quite annoying and we can add an opt-out option, > > would that be enough? > > Nope. I'd vote for a build-time switch that disables that code. I am > sorry. Another option could be a disabled-by-default (via build-time > option) update notification feature. A new remmina user should not be > bothered by update notification popups they won't be able to install > (because their Debian version won't have that update). Yes, understood. > I hope, you are ok with the above and the strictness of the policy. The news widget does other stuff than just showing the release notes, so we have to take out those functionalities. We need time and in the meanwhile 1.4.5 is already out, so please be flexible for this time. I prefere to relase a clean and cleaned 1.4.6 version than playing with workaround patches that may introduce other bugs > > light+love > Mike Regards Antenore signature.asc Description: This is a digitally signed message part.
Processed: Bug#952348 marked as pending in backupchecker
Processing control commands: > tag -1 pending Bug #952348 [src:backupchecker] backupchecker: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 1. Ignoring request to alter tags of bug #952348 to the same tags previously set -- 952348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952348: marked as pending in backupchecker
Control: tag -1 pending Hello, Bug #952348 in backupchecker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/backupchecker/-/commit/fb813ddef7b5ebbcb83d20b1a2ace77e46350f16 Merge branch 'debian/master' into 'debian/master' Add dh-python to build depends (Closes: #952348) See merge request python-team/applications/backupchecker!1 (this message was generated automatically) -- Greetings https://bugs.debian.org/952348
Processed: Bug#952348 marked as pending in backupchecker
Processing control commands: > tag -1 pending Bug #952348 [src:backupchecker] backupchecker: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 1. Added tag(s) pending. -- 952348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952348: marked as pending in backupchecker
Control: tag -1 pending Hello, Bug #952348 in backupchecker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/backupchecker/-/commit/b1a032d933318ba4d2c68c3acdb5774564479b58 Add dh-python to build depends (Closes: #952348) (this message was generated automatically) -- Greetings https://bugs.debian.org/952348
Bug#961253: marked as done (libmecab-perl: Can't load Perl module)
Your message dated Tue, 26 May 2020 10:18:33 + with message-id and subject line Bug#961253: fixed in mecab 0.996-13 has caused the Debian Bug report #961253, regarding libmecab-perl: Can't load Perl module 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.) -- 961253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmecab-perl Version: 0.996-12 Severity: grave Dear Maintainer, I can't load and use mecab perl module. I use the simlest perl script. % cat /tmp/mecab.pl #!/usr/bin/perl -w use MeCab; But, I fail to run this script. % /tmp/mecab.pl Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/MeCab/MeCab.so' for module MeCab: /usr/lib/x86_64-linux-gnu/perl5/5.30/auto/MeCab/MeCab.so: undefined symbol: _ZN5MeCab6Tagger6createEiPPc at /usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193. at /usr/lib/x86_64-linux-gnu/perl5/5.30/MeCab.pm line 11. Compilation failed in require at /tmp/mecab.pl line 3. BEGIN failed--compilation aborted at /tmp/mecab.pl line 3. After downgrading libmecab-perl to 0.99.6-2+b4 (got from snapshot.debian.org), it's working fine. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmecab-perl depends on: ii libc6 2.30-8 ii libgcc-s1 [libgcc1] 10.1.0-1 ii libgcc1 1:10.1.0-1 ii libmecab2 0.996-12 ii libstdc++6 10.1.0-1 ii perl5.30.2-1 ii perl-base [perlapi-5.30.0] 5.30.2-1 libmecab-perl recommends no packages. libmecab-perl suggests no packages. -- no debconf information OHURA Makoto: oh...@debian.org(Debian Project) oh...@netfort.gr.jp(LILO/Netfort) pgpuEmkd6DcOE.pgp Description: OpenPGP Digital Signature --- End Message --- --- Begin Message --- Source: mecab Source-Version: 0.996-13 Done: Hideki Yamane We believe that the bug you reported is fixed in the latest version of mecab, 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. Hideki Yamane (supplier of updated mecab package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 May 2020 18:44:07 +0900 Source: mecab Architecture: source Version: 0.996-13 Distribution: unstable Urgency: medium Maintainer: Natural Language Processing (Japanese) Changed-By: Hideki Yamane Closes: 961253 Changes: mecab (0.996-13) unstable; urgency=medium . * debian/control - Set perl related dependency as same as previous libmecab-perl source package - Add Build-Depends: chrpath * debian/clean - Fix to work with directories * debian/rules - Simplify rules - Reorder to make perl configureation properly (Closes: #961253) - Use chrpath to fix "binary-or-shlib-defines-rpath" error * debian/tests/control - Exec autopkgtest for libmecab-perl Checksums-Sha1: 6eaf3c88559e2484bd71651d06754ad2cccf590f 2599 mecab_0.996-13.dsc 53763b153dd476273b210c9b6c4467c663e13c0e 12576 mecab_0.996-13.debian.tar.xz 49aa3ce5f3f8f8ebd55f694b47ffe12d3884cec7 15267 mecab_0.996-13_amd64.buildinfo Checksums-Sha256: 13b5e39a702e7693e04a10189dca18ffcea1b342a6c81105e701df6c7a5df525 2599 mecab_0.996-13.dsc c295ce82680c728a4fc489de2c96464bff471c952b85b62f5c446d17932f28a7 12576 mecab_0.996-13.debian.tar.xz dd032dc123d6527fd4da1adc728ba603fb6d6e5ebbea7f2a708db9dda14d2035 15267 mecab_0.996-13_amd64.buildinfo Files: c3c4877d316f570aa1898f293264dcfd 2599 misc optional mecab_0.996-13.dsc 1f083120ad08eba4276d21ad1b160a1f 12576 misc optional mecab_0.996-13.debian.tar.xz 4e29f27d398ce1f563db0695c77da67f
Bug#961234:
On Tue, May 26, 2020 at 10:44:49AM +0200, Dylan Aïssi wrote: > I think we should not spend time to try to fix this FTBFS as treescape > is depreciated in favor of treespace (already in Debian). Because > treescape has still some users (popcon 82), I will ask to remove only > the ppc64el binary to avoid a missing build. Fully ACK, Andreas. -- http://fam-tille.de
Bug#952587: marked as done (FTBFS with Ruby2.7: CSV.parse() doesn't parse CVS source file as expected)
Your message dated Tue, 26 May 2020 10:04:11 + with message-id and subject line Bug#952587: fixed in ruby-espeak 1.0.4-2 has caused the Debian Bug report #952587, regarding FTBFS with Ruby2.7: CSV.parse() doesn't parse CVS source file as expected 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.) -- 952587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rspeak Version: 1.0.4-1 Severity: serious Justification: FTBFS on amd64 Tags: sid Usertags: ruby2.7-transition Hi there, the newly accepted ruby-espeak fails to test successfully with Ruby2.7. The reason seems that CSV.parse() has a behavior change. It does not parse the file test/fixtures/voices.txt anymore as it did. It seems using col_sep: ' ' is now interpreted literally. So fields separated by more then one space are not parsed as columns in a row. To demonstrate consider this line: > Pty Language Age/Gender VoiceName FileOther Langs > 5 af M afrikaans af With ruby2.5 it is parsed like this: > # "File":"af" "Other":nil "Langs":nil> and with ruby2.7 like this: > # nil:nil nil:nil nil:nil nil:nil nil:nil "File":nil nil:nil nil:nil nil:nil > nil:nil nil:nil nil:"M" nil:nil "Other":"afrikaans" "Langs":nil nil:nil > nil:nil nil:nil nil:nil nil:nil nil:nil nil:nil nil:"af" nil:nil nil:nil > nil:nil nil:nil nil:nil nil:nil nil:nil nil:nil nil:nil nil:nil> This seems intentional: https://github.com/ruby/csv/issues/67 https://github.com/ruby/csv/commit/7798df60fed87251b26c1202eb251a7894b55469#diff-fd263cdff2717a557bddf1592762dba3R16 The file format is determined by the output of `espeak --voices` and cannot be changed. Does anybody know, how to easily fix this, or is anybody up to add some magic to lib/espeak/voice.rb to deal with this? Regards, Daniel signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: ruby-espeak Source-Version: 1.0.4-2 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-espeak, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-espeak package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 May 2020 14:11:48 +0530 Source: ruby-espeak Architecture: source Version: 1.0.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Utkarsh Gupta Closes: 952587 Changes: ruby-espeak (1.0.4-2) unstable; urgency=medium . * Source-only upload * Add myself as an uploader * Disable tests as a temporary workaround (Closes: #952587) - This is a change in CSV. And the upstream is dead. * Bump debhelper-compat to 13 Checksums-Sha1: 1f2376f0de5573c04315b115fc915c4abc8a6d33 2154 ruby-espeak_1.0.4-2.dsc df3834b8e3501e2569ccf7a8a0f8c3312338a396 2640 ruby-espeak_1.0.4-2.debian.tar.xz e414fabaa93ebaf2bca978fd782e06a96d243346 9193 ruby-espeak_1.0.4-2_amd64.buildinfo Checksums-Sha256: 7cc6a220a1c6bbe02f93cad6fad9e93fa14f6d3124973b0f90a0e6ab98e1cfff 2154 ruby-espeak_1.0.4-2.dsc c7c948eef75fba7256600e40162887a006050f412b54277d976eb17ee6bbb828 2640 ruby-espeak_1.0.4-2.debian.tar.xz 3fc05dbca014b6b062e1f55a19403328f852f716ccd218cbd64de41a94756dcf 9193 ruby-espeak_1.0.4-2_amd64.buildinfo Files: 467284284cdb23079bd14fb23c844209 2154 ruby optional ruby-espeak_1.0.4-2.dsc 49fe1c8cdba1413bb3c3e4c1e62a8fad 2640 ruby optional ruby-espeak_1.0.4-2.debian.tar.xz 3c7c4d0b4f11b44e020a3c10088195d9 9193 ruby optional ruby-espeak_1.0.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl7M5cgTHHV0a2Fyc2hA ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlgO0EAC38dIusBh81d1RzsV8PH2TXZiixbBw NdaT8qzheWitbF8VmYwvgpGEQeVRMYI5Y4O6VolxvqlRaC2N+iZryP4x2KHMhbe+ nULJXjeIjDiAArqLFqtkFnwyaPUGqzbmG8kXJjMBS2Fduc3GesY9LmuceopRLhxr 8TCBWIyGefTVzKsF1StonBhMHwzRtmZfncAlLGlnttGO01oXcd6yIV9sVjtNqgCp
Bug#961499: marked as done (r-cran-sjmisc: missing test dependency on r-cran-haven)
Your message dated Tue, 26 May 2020 10:04:00 + with message-id and subject line Bug#961499: fixed in r-cran-sjmisc 2.8.4-3 has caused the Debian Bug report #961499, regarding r-cran-sjmisc: missing test dependency on r-cran-haven 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.) -- 961499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-sjmisc Version: 2.8.4-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-sjmisc/5633123/log.gz ... ── 1. Error: (unknown) (@test-frq_whitespace.R#10) Package 'haven' required for this function. Please install it. Backtrace: 1. sjmisc::rec(dat, y.char, suffix = "_r", as.num = TRUE, rec = "Category1 = 1 [Label 1]; Category2 = 2 [Label 2]; Category3 = 3 [Label 3];") 2. sjmisc:::rec.default(...) 3. sjmisc:::rec_core_fun(...) 4. sjmisc:::rec_helper(...) 7. sjlabelled::set_labels(x = new_var, labels = val_lab) 8. sjlabelled:::set_labels_helper(...) ... r-cran-sjlabelled no longer depends on r-cran-haven. --- End Message --- --- Begin Message --- Source: r-cran-sjmisc Source-Version: 2.8.4-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-cran-sjmisc, 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. Nilesh Patra (supplier of updated r-cran-sjmisc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 May 2020 10:57:37 +0530 Source: r-cran-sjmisc Architecture: source Version: 2.8.4-3 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 961499 Changes: r-cran-sjmisc (2.8.4-3) unstable; urgency=medium . * Team Upload. * Update Test Depends (Closes: #961499) * Bump debhelper-compat version to 13 Checksums-Sha1: bed7944aa6949cd191bdb247a0aefae180d6b7e8 2265 r-cran-sjmisc_2.8.4-3.dsc d3571125443cec699f671bef95688fc2ade14dde 2732 r-cran-sjmisc_2.8.4-3.debian.tar.xz 02cf6e3f4cb38b451df6b7474eeab24260741dea 9302 r-cran-sjmisc_2.8.4-3_amd64.buildinfo Checksums-Sha256: 80df368990da270709d1e234fa46405a7e8bf48f0ec6137826f79b5f701cffb5 2265 r-cran-sjmisc_2.8.4-3.dsc 8da525c2a77eee003a78434271638fb4bc6589003c2ebf4bef3931b84349c439 2732 r-cran-sjmisc_2.8.4-3.debian.tar.xz e5c0f73d43752facbf4f3afecb5122e59d15d7165f7d534c7fcffca1f86b0faa 9302 r-cran-sjmisc_2.8.4-3_amd64.buildinfo Files: 38e5e575ad3780b584a2ef282d65d93e 2265 gnu-r optional r-cran-sjmisc_2.8.4-3.dsc a797baa0460c767533e70d09dbd9a29c 2732 gnu-r optional r-cran-sjmisc_2.8.4-3.debian.tar.xz 6947cb4a96a8b7e57f25ca02d3984762 9302 gnu-r optional r-cran-sjmisc_2.8.4-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7M5BkRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEA9A/9Egm37d+JtiP738CdF+5dB7pV5I5rqGWx oDazkcBvoEJsFFg3zK+mL6WcgZKKgKEPTmop2nxK82n/cxTCYctxUPTY6a9mKRPo vNBRjRckTcnYnvQ5KWo9K7MJWfMwwAmZN9T6YCyvfd+OKNan1diGu2SpFYBQV4Qd V5yLlIsLqX/sR7H372EOre7qsdpzsm95HQReKsKzekHrLH/FH/+fN5BLfGoFD426 yx2tozDKjXDqhzPfNODkuqfBTtBDp4GOqTz0FmBdqHJvRLESZ5GWirpmaIlGIb4O i8mZqDA0fr65zqWZaJeFWlBg0pDz8dlP2XGdCJhnZaZ27P7Bm9Cr816nou2rg3pJ kiG37qdfwkewEknO/PQ+zVHWDWF2unLmPkzmXHMhMlWlaHNSyPnNFTHQ/E75FIEr sDzl4CMxaeWZDGd5BPDQD+zH6k2pxxB6j65cF37/EUN23Fx7rKoosxNV15FBLH7+ hC3a97VQK+u1H/JE0/ZfTAPe5Uv9LIJ9EKz6O6pVpm+N2m685M4mJWy2u7hgHEP9 gtG72uyX6hiydq2eF/7PJSRnpVfDqapcstw59Qx2yN6xby6O/ASO0unONLHQ6Uif Z7uZ/uRR4BjXYfJCrp2L5zBGMvQ+XNTwgU4mtV0D6VlgVRUco1TnsUj9hg5c6y/r zxquPm03Btc= =u9Nr -END PGP SIGNATURE End Message ---
Bug#961498: marked as done (r-cran-sjplot: missing test dependency on r-cran-haven)
Your message dated Tue, 26 May 2020 10:04:06 +
with message-id
and subject line Bug#961498: fixed in r-cran-sjplot 2.8.3-3
has caused the Debian Bug report #961498,
regarding r-cran-sjplot: missing test dependency on r-cran-haven
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.)
--
961498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sjplot
Version: 2.8.3-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-sjplot/5625656/log.gz
...
> library(testthat)
> library(sjPlot)
>
> if (length(strsplit(packageDescription("sjPlot")$Version, "\\.")[[1]]) > 3) {
+ Sys.setenv("RunAllsjPlotTests" = "yes")
+ }
>
> test_check("sjPlot")
── 1. Error: (unknown) (@test-plot_model_std.R#15)
Package 'haven' required for this function. Please install it.
Backtrace:
1. sjmisc::to_factor(efc, e42dep, c172code, c161sex)
2. sjmisc:::to_fac_helper(.dat[[i]], add.non.labelled, ref.lvl)
5. sjlabelled::set_labels(...)
6. sjlabelled:::set_labels_helper(...)
══ testthat results ═══
[ OK: 2 | SKIPPED: 0 | WARNINGS: 12 | FAILED: 1 ]
...
r-cran-sjlabelled no longer depends on r-cran-haven.
--- End Message ---
--- Begin Message ---
Source: r-cran-sjplot
Source-Version: 2.8.3-3
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
r-cran-sjplot, 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.
Nilesh Patra (supplier of updated r-cran-sjplot package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 26 May 2020 11:21:29 +0530
Source: r-cran-sjplot
Architecture: source
Version: 2.8.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Nilesh Patra
Closes: 961498
Changes:
r-cran-sjplot (2.8.3-3) unstable; urgency=medium
.
* Team Upload.
* Update upstream/metadata
* Bump debhelper-compat version to 13
* Update Test Depends (Closes: #961498)
Checksums-Sha1:
b276c35eaf7a582bd7471a7b336713c579474275 2458 r-cran-sjplot_2.8.3-3.dsc
076884319e1fe239f46ac58683d87579fa2e6cc1 3428
r-cran-sjplot_2.8.3-3.debian.tar.xz
0fb9b33afbf8b7c5be09d9ffd8c6e70d0e0a3bff 11691
r-cran-sjplot_2.8.3-3_amd64.buildinfo
Checksums-Sha256:
11de090497f80ec6c89c43845d31998b10a51058b6b36c085b80a43f0f7e2d7d 2458
r-cran-sjplot_2.8.3-3.dsc
b10edff0fc88ea5b183f4a11e1a4ce639fd7ff5324b4524de0fe7ec6f1037926 3428
r-cran-sjplot_2.8.3-3.debian.tar.xz
f806373ea49a6abe5ba71d9a0ec9533921eca21f55f47a6ea3873ac49f733723 11691
r-cran-sjplot_2.8.3-3_amd64.buildinfo
Files:
443caa30a50936d54d9dc9e102deebcd 2458 gnu-r optional r-cran-sjplot_2.8.3-3.dsc
d46eba6ed26b153d247efe114090c4a2 3428 gnu-r optional
r-cran-sjplot_2.8.3-3.debian.tar.xz
8c662883fe5a5b46e434b8c533875060 11691 gnu-r optional
r-cran-sjplot_2.8.3-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7M5UMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFOwA/8CKVbqwOm77zzqXA5MKCloSUy4XeUi/bS
phC5yJiwsOHL0cil7Qxu18pgDIYaR9JaSeAfIeFwgruEWwvU+qgN9cft0tm0tDif
016hD+8bZy3tb2kVVDqv36W0WacBlLYjLRthIUMT1hPurdTFUPdKJqZ9/cBpBl2V
OPzAkyYEcBdWZbSYHvP0r15P6cidkLkJj3LyaTSS6LMNCfAD1T28vZpkfLBMj1mz
n4lJV/G3QBmViKAv/UdSDRLV1Xm4/LubKHAwYnl+iU94IdySJKnMyt0LkfY0ejtu
5qQ2a1RJ77KWDMEfu+AkNZmQxfLOKu7nDaRwwheq6mpSRMM++s9tb84vt+zKMPqn
6fLub+HG+6J0cR0PNb+3qU39BygaIP6BSrE8B2y82Zs3Oo+K9j+IFomgmb632/LX
97AH7Xe5j4UNtznQE3wGTrKT6oknkT6NmIT4F3/ZoSjkjctZkuknKCO8lE0LOyhG
YeFETnE7mWMrKqQ1BK7WvywHtljTIUKhfhEDFpAobOiIhVpl0K24+tCChZhqIZr1
pnJFUrXeYyUwMQCVJq/TjaBAK6eEw3p7WxXYqLXLwxxzZt0ulHRXKjJ/ghap5Xoy
TuT3X/w4NPF4+KjFpxfVMuHW8dDiJ3mP3e5/196AgNGlDUVTrAsUGl+sWtvEWRvK
gAeuC3fGsco=
=Hoq7
-END PGP SIGNATURE End Message ---
Bug#961581: pbcopper: ftbfs on ppc64el
Source: pbcopper Version: 1.6.0+dfsg-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, As can be seen on https://buildd.debian.org/status/logs.php?pkg=pbcopper=ppc64el pbcopper currently ftbfs on pcp64el. I think this is a bug in simde: https://github.com/nemequ/simde/issues/325 but anyway, I'm attaching the workaround I just uploaded to Ubuntu. Cheers, mwh -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-31-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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 --- a/src/align/cssw/ssw.c +++ b/src/align/cssw/ssw.c @@ -35,6 +35,9 @@ * */ +#ifdef __powerpc64__ +#define SIMDE_NO_NATIVE +#endif #define SIMDE_ENABLE_NATIVE_ALIASES #include "simde/x86/sse2.h" #include --- a/src/align/cssw/ssw.h +++ b/src/align/cssw/ssw.h @@ -11,6 +11,9 @@ #ifndef SSW_H #define SSW_H +#ifdef __powerpc64__ +#define SIMDE_NO_NATIVE +#endif #define SIMDE_ENABLE_NATIVE_ALIASES #include "simde/x86/sse2.h" #include
Bug#961499: [RFS] r-cran-sjplot and r-cran-sjmisc
Hi Nilesh, On Tue, May 26, 2020 at 02:16:35PM +0530, Nilesh Patra wrote: > > same as for r-cran-sjplot: In commit d2c969cc you move a file out of > > help system to doc and I'm not convinced that this is not dangerous. > > Ahh, righty! > I didn't realise the help system thing while moving it, and this was indeed > a careless mistake. Apologies. Really no need to apologise - mistakes just happen. > I've reverted the commit and pushed for both the packages. > Please consider to upload. First package uploaded, second just building. Thanks a lot for your contribution Andreas. -- http://fam-tille.de
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 961234 with 961576 Bug #961234 [src:r-cran-treescape] r-cran-treescape: FTBFS on ppc64el:Segmentation fault 961234 was not blocked by any bugs. 961234 was not blocking any bugs. Added blocking bug(s) of 961234: 961576 > thanks Stopping processing here. Please contact me if you need assistance. -- 961234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961570: marked as done (r-cran-mice: autopkgtest regression)
Your message dated Tue, 26 May 2020 08:52:01 +
with message-id
and subject line Bug#961570: fixed in r-cran-mice 3.9.0-2
has caused the Debian Bug report #961570,
regarding r-cran-mice: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
961570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-mice
Version: 3.9.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 3.9.0-1, r-cran-mice has been failing its own
autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-mice/unstable/amd64/
> library(testthat)
> library(mice)
Attaching package: ‘mice’
The following objects are masked from ‘package:base’:
cbind, rbind
>
> test_check("mice")
── 1. Error: (unknown) (@test-D3.R#9) ─
there is no package called ‘lmtest’
Backtrace:
1. lmtest::lrtest
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
══ testthat results ═══
[ OK: 282 | SKIPPED: 1 | WARNINGS: 0 | FAILED: 1 ]
1. Error: (unknown) (@test-D3.R#9)
Error: testthat unit tests failed
Execution halted
autopkgtest [19:10:15]: test run-unit-test: ---]
autopkgtest [19:10:15]: test run-unit-test: - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-cran-mice
Source-Version: 3.9.0-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-mice, 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.
Andreas Tille (supplier of updated r-cran-mice package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 26 May 2020 10:11:38 +0200
Source: r-cran-mice
Architecture: source
Version: 3.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 961570
Changes:
r-cran-mice (3.9.0-2) unstable; urgency=medium
.
* Test-Depends: r-cran-lmtest
Closes: #961570
Checksums-Sha1:
8909425ab7073020bb4489a390273cee37319726 2472 r-cran-mice_3.9.0-2.dsc
107b01a3d0d25911875b2449523ac22b36a7ecaf 3436 r-cran-mice_3.9.0-2.debian.tar.xz
5e46765b1e2ea0e0bf0a8cbed4f8686fee85c336 9813
r-cran-mice_3.9.0-2_amd64.buildinfo
Checksums-Sha256:
a060d4fa85d29f92b5c0c1953759caa6584df29ee1e449f3f2d20dd700fb961d 2472
r-cran-mice_3.9.0-2.dsc
657ca944478eb99813981474f71df09870158e8399ec4efe42d4735ce353d0d7 3436
r-cran-mice_3.9.0-2.debian.tar.xz
79d539e637e78af9b7630e42a97aa9493b6a717e3caed21b06731a380068f303 9813
r-cran-mice_3.9.0-2_amd64.buildinfo
Files:
32e97b7b316685772ecf476713f44c65 2472 gnu-r optional r-cran-mice_3.9.0-2.dsc
00694d93deaebab787f3d0ac77cd6c58 3436 gnu-r optional
r-cran-mice_3.9.0-2.debian.tar.xz
51651f50f7aa1a48400f8c02b0146e36 9813 gnu-r optional
r-cran-mice_3.9.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7M064RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE4RhAAjxekeDCgbL6oJ150tcNGZ3+YiD81D+dP
gtXvnWluC+G6CjfGSY+st8mj2m32slnZdrzMy/5fN95bkiDT6fnVG1YjugBkH+jC
DSg4Qzz9Rxm+JkvE3WboXkoJWffS3/qzBCB/q6jVhx9O2GjZmVCQ6EkTrUgrxpJi
rKf4/FfOsElwtvxWuDhCMGi3MvLANroRqAfrx4T2K3HaTDotLtcz3Ig27xanr9OP
ZlPfmlsDeBrlVLpdM4avWHGuSWBWPHnwMByuCYV6TiHZtsi/+8MQASqKWYV/vSif
N5kE+O6pzmWPWHA9hdnlPIxPpmYLgyn5/b+X6o/UbIG9vWJY9wq1rFAHn0DZ4VzV
rS0arHdLPoYBcTiSIDweqUueuVymJhRuPeEJmvspSOOVCKsOU7ykI8cwC2ICVfS9
hK+wzm7XPObg3GPmjxU7cGTCjo89POkaDdfB85be8AxelmHLdWa3MIqRYk/wMvVT
Bug#961499: [RFS] r-cran-sjplot and r-cran-sjmisc
Hi On Tue, 26 May 2020, 13:26 Andreas Tille, wrote: > Hi Nilesh, > > same as for r-cran-sjplot: In commit d2c969cc you move a file out of > help system to doc and I'm not convinced that this is not dangerous. > Ahh, righty! I didn't realise the help system thing while moving it, and this was indeed a careless mistake. Apologies. I've reverted the commit and pushed for both the packages. Please consider to upload. Regards, Nilesh
Bug#961234:
Hi, I think we should not spend time to try to fix this FTBFS as treescape is depreciated in favor of treespace (already in Debian). Because treescape has still some users (popcon 82), I will ask to remove only the ppc64el binary to avoid a missing build. Best, Dylan
Bug#961501: remmina is calling home for update notifications
Hi Mike, Thanks for your detailed answer. On Monday, May 25, 2020 11:55:00 PM CEST Mike Gabriel wrote: > Debian users expect from Debian, to be a safe harbour, so all package > maintainers are requested to patch out code that does unwanted / > uncontrollable connections to the internet for stats collections and > such. I perfectly understand your point, we are working to fix this and it will take some days of work (in our limited free overnight time). > While I understand the interest in usage statistics, in Debian we > cannot have that part of the phoning-home code. I am sorry. This widget is not about usage statistics, that are already opt-in only. This widget informs the user about new Remmina versions and changes. No more no less. Just to clarify ;-) > > > Remmina on a regular basis verify if there's a new file or if the file of > > the version requested (the PHP parameter) has been changed/updated. > > Thanks for the explanation of the mechanism. > > > We do this to notify users about new versions, especially when there are > > important bugs that have been fixed. > > This is not helpful in a GNU distribution using a conservative-style > release model (not sure if this is the correct term) like Debian does. > Imagine Debian stable and oldstable users being reminded of their > software being out of date on every upstream release. Of course, their > software is out of date, as they use remmina from Debian (old)stable > (not testing/unstable). They get those notifications but cannot do > anything about it (except upgrading to Debian testing). This is a good point. I agree. > > So, also from a usability point of view, those notification windows > will be a disturbance to the users of Debian. > > > Libreoffice does something similar for instance and other software, > > in Debian, > > as well. > > Really? Than this must be considered as a bug. Which other packages > have you observed doing this? Regarding Libreoffice I see is not the case anymore since a long time, sorry. I don't have evidence of other software at the moment, if I find any I'll fill a bug as well. > > > I understand it may be quite annoying and we can add an opt-out option, > > would that be enough? > > Nope. I'd vote for a build-time switch that disables that code. I am > sorry. Another option could be a disabled-by-default (via build-time > option) update notification feature. A new remmina user should not be > bothered by update notification popups they won't be able to install > (because their Debian version won't have that update). Yes, understood. > I hope, you are ok with the above and the strictness of the policy. The news widget does other stuff than just showing the release notes, so we have to take out those functionalities. We need time and in the meanwhile 1.4.5 is already out, so please be flexible for this time. I prefere to relase a clean and cleaned 1.4.6 version than playing with workaround patches that may introduce other bugs > > light+love > Mike Regards Antenore
Processed: Re: Bug#946225: FTBFS related to Boost.Python
Processing control commands: > reassign -1 src:boost1.67 Bug #946225 [src:k3d] FTBFS related to Boost.Python Bug reassigned from package 'src:k3d' to 'src:boost1.67'. No longer marked as found in versions k3d/0.8.0.6-8. Ignoring request to alter fixed versions of bug #946225 to the same values previously set > affects -1 src:k3d Bug #946225 [src:boost1.67] FTBFS related to Boost.Python Added indication that 946225 affects src:k3d > close -1 1.67.0-16 Bug #946225 [src:boost1.67] FTBFS related to Boost.Python Marked as fixed in versions boost1.67/1.67.0-16. Bug #946225 [src:boost1.67] FTBFS related to Boost.Python Marked Bug as done -- 946225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946225: FTBFS related to Boost.Python
Control: reassign -1 src:boost1.67 Control: affects -1 src:k3d Control: close -1 1.67.0-16 On Thu, Dec 05, 2019 at 09:58:37PM +0100, Joachim Reichel wrote: > Source: k3d > Version: 0.8.0.6-8 > Severity: serious > Tags: ftbfs > > Hi, > > your package FTBFS: > > CMake Error at > /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 > (message): > Could NOT find Boost (missing: python) (found suitable version "1.67.0", > minimum required is "1.42") > Call Stack (most recent call first): > /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 > (_FPHSA_FAILURE_MESSAGE) > /usr/share/cmake-3.15/Modules/FindBoost.cmake:2161 > (find_package_handle_standard_args) > cmake/modules/K3DFindBoost.cmake:9 (FIND_PACKAGE) > CMakeLists.txt:254 (INCLUDE) >... This has been fixed in boost: boost1.67 (1.67.0-16) unstable; urgency=medium ... * Actually fix python test case using correct CMake syntax. ... cu Adrian
Processed (with 1 error): Re: Bug#961336: prboom-plus FTBFS on big endian
Processing control commands: > tags -1 confirmed pending fixed-upstream Bug #961336 [src:prboom-plus] prboom-plus FTBFS on big endian Added tag(s) confirmed, pending, and fixed-upstream. > forwarded -1 Unknown command or malformed arguments to command. -- 961336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961336: prboom-plus FTBFS on big endian
Control: tags -1 confirmed pending fixed-upstream Control: forwarded -1 https://github.com/coelckers/prboom-plus/commit/29320630c9ae878e537f451f173dbf9007d6786b
Bug#961507: [Pkg-javascript-devel] Bug#961507: eyes.js: unmaintained in Debian
Le 25/05/2020 à 14:42, Jonas Smedegaard a écrit : > Source: eyes.js > Severity: grave > Justification: renders package unusable > > eyes.js is not really maintained in Debian, and largely unmaintained upstream. > > Either someone in the JavaScript team take over from me in looking after it, > or it should be dropped from Debian. > > As is, I I consider it unsuitable for inclusion in a stable release of Debian. > > - Jonas vows is the only one reverse dependency of eyes.js. Versions 0.9~beta and 1.0~alpha dropped this dependency. So we could ROM-RM eyes.js after next vows release.
Bug#961572: r-bioc-mutationalpatterns: autopkgtest regression
Source: r-bioc-mutationalpatterns
Version: 2.0.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 2.0.0-1, r-bioc-mutationalpatterns has been
failing its own autopkgtests [1]. This now prevents the migration of
r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/testing/amd64/
> test_check("MutationalPatterns")
── 1. Error: (unknown) (@test_mut_matrix_stranded.R#3)
there is no package called ‘TxDb.Hsapiens.UCSC.hg19.knownGene’
Backtrace:
1. base::library("TxDb.Hsapiens.UCSC.hg19.knownGene")
── 2. Error: (unknown) (@test_mut_matrix.R#5) ─
there is no package called ‘BSgenome.Hsapiens.UCSC.hg19’
Backtrace:
1. base::library(ref_genome, character.only = TRUE)
── 3. Error: (unknown) (@test_read_vcfs_as_granges.R#5) ───
there is no package called ‘BSgenome.Hsapiens.UCSC.hg19’
Backtrace:
1. base::library(ref_genome, character.only = TRUE)
══ testthat results ═══
[ OK: 0 | SKIPPED: 0 | WARNINGS: 0 | FAILED: 3 ]
1. Error: (unknown) (@test_mut_matrix_stranded.R#3)
2. Error: (unknown) (@test_mut_matrix.R#5)
3. Error: (unknown) (@test_read_vcfs_as_granges.R#5)
Error: testthat unit tests failed
Execution halted
autopkgtest [09:41:10]: test pkg-r-autopkgtest: ---]
autopkgtest [09:41:10]: test pkg-r-autopkgtest: - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
Bug#961499: [RFS] r-cran-sjplot and r-cran-sjmisc
Hi Nilesh, same as for r-cran-sjplot: In commit d2c969cc you move a file out of help system to doc and I'm not convinced that this is not dangerous. Kind regards Andreas. On Tue, May 26, 2020 at 11:31:32AM +0530, Nilesh Patra wrote: > Hi, > Currently r-cran-sjplot, r-cran-sjmisc have failing tests, and have RC bugs > - #961498 and #961499 filed against them. > I have fixed these and pushed my changes to the team repos here[1] and > here[2]. > Need review and sponsorship. > > [1]: https://salsa.debian.org/r-pkg-team/r-cran-sjplot > [2]: https://salsa.debian.org/r-pkg-team/r-cran-sjmisc > > Thanks and regards > Nilesh -- http://fam-tille.de
Bug#961571: r-cran-vctrs: autopkgtest regression
Source: r-cran-vctrs
Version: 0.3.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.3.0-1, r-cran-vctrs has been failing its own
autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-vctrs/unstable/amd64/
> library(testthat)
> library(vctrs)
>
> if (requireNamespace("xml2")) {
+ test_check("vctrs", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"),
CheckReporter$new(
+ } else {
+ test_check("vctrs")
+ }
Loading required namespace: xml2
Failed with error: ‘there is no package called ‘xml2’’
── 1. Error: grouped-df is proxied and restored (@test-type-dplyr.R#7)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 2. Error: can take the common type of grouped tibbles and tibbles (@test-type
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 3. Error: the common type of grouped tibbles includes the union of grouping v
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 4. Error: can cast to and from `grouped_df` (@test-type-dplyr.R#45)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 5. Error: casting to `grouped_df` doesn't require grouping variables (@test-t
there is no package called ‘dplyr’
Backtrace:
1. testthat::expect_identical(...)
5. dplyr::group_by
6. base::getExportedValue(pkg, name)
7. base::asNamespace(ns)
8. base::getNamespace(ns)
9. base::loadNamespace(name)
10. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
11. base:::withOneRestart(expr, restarts[[1L]])
12. base:::doWithOneRestart(return(expr), restart)
── 6. Error: casting to `grouped_df` handles `drop` (@test-type-dplyr.R#82) ───
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 7. Error: can cbind grouped data frames (@test-type-dplyr.R#87)
there is no package called ‘dplyr’
Backtrace:
1. dplyr::group_by
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 8. Error: rowwise can be proxied and restored (@test-type-dplyr.R#107) ─
there is no package called ‘dplyr’
Backtrace:
1. dplyr::rowwise
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 9. Error: can take the common type of rowwise tibbles and tibbles (@test-type
there is no package called ‘dplyr’
Backtrace:
1. dplyr::rowwise
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
── 10. Error: can cast to and from `rowwise_df` (@test-type-dplyr.R#124) ──
there is no package called ‘dplyr’
Backtrace:
1. vctrs:::unrownames(dplyr::rowwise(bare_mtcars))
2.
Bug#961569: libdolfinx-dev is binary-all but contains amd64 specific contents
Package: libdolfinx-dev Version: 2019.2.0~git20200420.6043d6d-5 Severity: serious /usr/share/dolfinx/cmake/DOLFINXTargets.cmake: INTERFACE_LINK_LIBRARIES "Boost::boost;Boost::timer;MPI::MPI_CXX;PETSC::petsc;/usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so;/usr/lib/x86_64-linux-gnu/libsz.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so;SLEPC::slepc"
Bug#961570: r-cran-mice: autopkgtest regression
Source: r-cran-mice
Version: 3.9.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 3.9.0-1, r-cran-mice has been failing its own
autopkgtests [1]. This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-mice/unstable/amd64/
> library(testthat)
> library(mice)
Attaching package: ‘mice’
The following objects are masked from ‘package:base’:
cbind, rbind
>
> test_check("mice")
── 1. Error: (unknown) (@test-D3.R#9) ─
there is no package called ‘lmtest’
Backtrace:
1. lmtest::lrtest
2. base::getExportedValue(pkg, name)
3. base::asNamespace(ns)
4. base::getNamespace(ns)
5. base::loadNamespace(name)
6. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
7. base:::withOneRestart(expr, restarts[[1L]])
8. base:::doWithOneRestart(return(expr), restart)
══ testthat results ═══
[ OK: 282 | SKIPPED: 1 | WARNINGS: 0 | FAILED: 1 ]
1. Error: (unknown) (@test-D3.R#9)
Error: testthat unit tests failed
Execution halted
autopkgtest [19:10:15]: test run-unit-test: ---]
autopkgtest [19:10:15]: test run-unit-test: - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
Bug#961498: [RFS] r-cran-sjplot and r-cran-sjmisc
Hi Nilesh, when checking 18ceae69 --- a/debian/rules +++ b/debian/rules @@ -2,3 +2,7 @@ %: dh $@ --buildsystem R + +override_dh_installdocs: + dh_installdocs + mv debian/r-cran-sjplot/usr/lib/R/site-library/sjPlot/help/figures debian/r-cran-sjplot/usr/share/doc/r-cran-sjplot I wonder whether this should be rather a symlink than a move. I'm not using sjplot personally and don't know how the help system works but moveing a file that resides under /usr/.../help/ away to /usr/share/doc makes me wonder whether the help system will continue to work. Kind regards Andreas. On Tue, May 26, 2020 at 11:31:32AM +0530, Nilesh Patra wrote: > Hi, > Currently r-cran-sjplot, r-cran-sjmisc have failing tests, and have RC bugs > - #961498 and #961499 filed against them. > I have fixed these and pushed my changes to the team repos here[1] and > here[2]. > Need review and sponsorship. > > [1]: https://salsa.debian.org/r-pkg-team/r-cran-sjplot > [2]: https://salsa.debian.org/r-pkg-team/r-cran-sjmisc > > Thanks and regards > Nilesh -- http://fam-tille.de
Bug#960720: marked as done (node-co: autopkgtest regression: no such file or directory, open 'LICENSE')
Your message dated Tue, 26 May 2020 06:03:42 +
with message-id
and subject line Bug#960720: fixed in node-co 4.6.0-3
has caused the Debian Bug report #960720,
regarding node-co: autopkgtest regression: no such file or directory, open
'LICENSE'
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.)
--
960720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-co
Version: 4.6.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of node-co the autopkgtest of node-co fails in
testing when that autopkgtest is run with the binary packages of node-co
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
node-cofrom testing4.6.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration 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=node-co
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-co/5444788/log.gz
39 passing (803ms)
4 failing
1) co(* -> yield [])
should aggregate several thunks:
Error: ENOENT: no such file or directory, open 'LICENSE'
2) co(* -> yield {})
should aggregate several thunks:
Error: ENOENT: no such file or directory, open 'LICENSE'
3) co() recursion
should aggregate arrays within arrays:
Error: ENOENT: no such file or directory, open 'LICENSE'
4) co() recursion
should aggregate objects within objects:
Error: ENOENT: no such file or directory, open 'LICENSE'
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-co
Source-Version: 4.6.0-3
Done: Xavier Guimard
We believe that the bug you reported is fixed in the latest version of
node-co, 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.
Xavier Guimard (supplier of updated node-co package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 26 May 2020 07:36:42 +0200
Source: node-co
Architecture: source
Version: 4.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 960720
Changes:
node-co (4.6.0-3) unstable; urgency=medium
.
* Team upload
* Disable some test incompatible with debci machines (Closes: #960720)
Checksums-Sha1:
c5ea2c820a803fe1c788d223322db49cb73e71e9 1994 node-co_4.6.0-3.dsc
aa720b973c86db0b000a6e5f0e32ccb51b96 5468 node-co_4.6.0-3.debian.tar.xz
Checksums-Sha256:
a4ae13a11b890d29b4186de94741db9a960ef09d4a02bdf51518fe4a56b14d1c 1994
node-co_4.6.0-3.dsc
293ca9ac52f7835f8d845c07a4722e702a93546de9540c1f1f35330755ca4448 5468
node-co_4.6.0-3.debian.tar.xz
Files:
49ed382a7f754ec9d85a0a2da958c26a 1994 javascript optional node-co_4.6.0-3.dsc
7a17febf2f6225e7fe3672c03cdd2267 5468 javascript optional
node-co_4.6.0-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl7MrHUACgkQ9tdMp8mZ
7ulfww/9EQ6IczmghQ55xG5MwgUlTztbO7EM4smu5877A6V/mjmHfafkNmAZLFbg
FT8R6Cj7C7QWt9T2V0Cqcf6kf0YMPQPwLku/rcXWxVCbW5hXSjfCqJJHmTZ+A5/o
hM+fjZo0zWgdSX98IgB62C2t3Q9/yRU/6viS0nZ79ddlc7Y1fIYQlOOwJEZijg4y
lXj/AvcLbhzYlUOhS1/UdCHxA79fTXBgAoWaKTtdGzkpkVPsc3WdYdDF4o2DmZ/1
w8ZQzyKDNjDP+P8eLOXIPvGS8Z1c22jsdcULeKzH1mvChFS5QHTJJY7kc7hpII1M
Q+QOXV/hDTwkGOR9IHWUHLNr21W1g7ejrcDtNrPSO5064pmu9Sbh6FSFKtewg5a8
bt78HLYNUPOlnfJbBxzcxOBYTmlYbtYdyn20aJ8dAhtW6K8jrjOpKIsEgZ6OhxO0
l/d9gc0ral/tSFtGbZNuwAsN7Jhw0IIRWkBLysyV6UbvyagOi5maGRQ5GH+lJXTn
DUPuGT5cUK1YFtR9sbeYVbDUZA1GsNGg5kZrwNJP3OCCU7nbSGnODu/1k94xEVC9
8C7BkmTbn2nhvH2l4Jxd8bCJQtGztLgzAknaUjRlMGVtWn90Co5yN/3BegdaQcDS
