Processed: limit source to fava, tagging 918641
Processing commands for cont...@bugs.debian.org: > limit source fava Limiting to bugs with field 'source' containing at least one of 'fava' Limit currently set to 'source':'fava' > tags 918641 + pending Bug #918641 [python3-fava] pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 918641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#790584: marked as done (gjots2: depends on python-gnome2 which is deprecated)
Your message dated Tue, 08 Jan 2019 06:34:12 + with message-id and subject line Bug#790584: fixed in gjots2 3.0.2-0.1 has caused the Debian Bug report #790584, regarding gjots2: depends on python-gnome2 which is deprecated 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.) -- 790584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gjots2 Severity: important Tags: sid stretch User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-gnome2 gnome-python Hi, gjots2 depends on python-gnome2, which is long deprecated and going to be removed from the archive. gjots2 should be ported away from it. The way forward is to port your app to use GObject Introspection bindings. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Stretch release as we're going to try to remove python-gnome2 this cycle. If you have any question don't hesitate to ask. Emilio [1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection [2] https://wiki.gnome.org/action/show/Projects/PyGObject --- End Message --- --- Begin Message --- Source: gjots2 Source-Version: 3.0.2-0.1 We believe that the bug you reported is fixed in the latest version of gjots2, 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 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gjots2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Dec 2018 00:30:33 -0500 Source: gjots2 Binary: gjots2 Architecture: source Version: 3.0.2-0.1 Distribution: unstable Urgency: medium Maintainer: Rolf Leggewie Changed-By: Jeremy Bicha Description: gjots2 - Simple jotter (outline processor) for X11/gtk-gnome Closes: 790584 Changes: gjots2 (3.0.2-0.1) unstable; urgency=medium . * Non-maintainer upload * Imported Upstream version 3.0.2 * Depend on python-gi and gir1.2-gtk-3.0 instead of python-glade2 (Closes: #790584) * Recommend gir1.2-gtksourceview-3.0 instead of python-gtksourceview2 * Refresh patches * Add 60_dont-import-gconf.patch * Add 70_dont-install-missing-xml-scripts.patch * Add 80_adjust-lib-install-directory.patch Checksums-Sha1: 9c85ca88f6cb9d060269f6ef4b3a2516235d214e 1809 gjots2_3.0.2-0.1.dsc ac1fb747cdef2231df217ca17567e93e099372b4 357675 gjots2_3.0.2.orig.tar.gz d45608d883da900f6f9e139686260c15b3e8cd35 7444 gjots2_3.0.2-0.1.debian.tar.xz 03955d5d596fbd416d7e9044e6371dee66ebf4cd 6499 gjots2_3.0.2-0.1_source.buildinfo Checksums-Sha256: a3d8691d3f9f6a0610d68e31d5b5db93671599f769b36bb2ee94b08059360a44 1809 gjots2_3.0.2-0.1.dsc ffc253970004eca277ed7a70eed0bf8b3805ae7d59f9c85972d8df1554ab48c1 357675 gjots2_3.0.2.orig.tar.gz 8b0a47e5f7cb875dff60a89153182c3fdc409a01f3415f042c3a4f830a96ba1e 7444 gjots2_3.0.2-0.1.debian.tar.xz 5713327c2af157cfe2f7dc72d84ad67213622da746f224d91e6e64b602a6cfb4 6499 gjots2_3.0.2-0.1_source.buildinfo Files: 6fa1ae283e652decb0f0b6e09f6dc4e2 1809 gnome optional gjots2_3.0.2-0.1.dsc bce0270e409cd67b17bc5ef27fedae99 357675 gnome optional gjots2_3.0.2.orig.tar.gz cecf62e652daa8bea5232037a8e8223f 7444 gnome optional gjots2_3.0.2-0.1.debian.tar.xz bab2c9353159c60afc7c9872611f9844 6499 gnome optional gjots2_3.0.2-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlwgby4ACgkQ5mx3Wuv+ bH1sFQ//Z5U/cytay7mIUGSkgGIxhnyZ9BURleOOVmjzTzrwg7MNH6OlFsLRrcfl wbLb9GGMP+uKvhMD2mq5uHI+nCzHWxMaqBqVe/mNAM6naszaDLnNzGBRunYPlDow Bku2gPR/cIAnXsNa9y1LBeXMir8zucJOtqOp47Cqp6t6+MEq0IQ9xWjFyOAowTCN TGeatbZtRYoMtmN4pzEjh9TcS4JAKPAvSpYmFqlWRFLHcc6jlaiY7bBg7Lh2w6oM M9GKc5whZCfgawdDfnEDUQ8iQbTNn3ll4x9hyTykyz6Ak37rXiGhkEHd3O2i0Iuo 8m1lmB0IC9HvqbTzdHo/n5r584M+PjupFm/UTNptWeO69n967Pq/S9i72ZJLB5xG a50cePVR92pIgItQcT5BjqVh9QdBGo6JUWu/s3g635u2I1fEvT19+yev2C3M3V3n GFAogubGqOs8Ljz3qvChsDl4phoRvmfvZon5MnYu+VReGbt+ZAi5VHk0bAV9p3kp YR9RFOZPfYP+AUdJxNJCotW/7rdccad9hllZcnXFVYQsFOlQIo5FFeL4DyEFSAFZ E9oUwN39qv1FE4XPDNPTap43wVHzgv21fBZWzhz/0L4d5Bbjwx9+ar6n6nUd0qxr
Bug#918443: marked as done (sl-modem: ftbfs on i386: undefined reference to `minor')
Your message dated Tue, 08 Jan 2019 04:49:52 + with message-id and subject line Bug#918443: fixed in sl-modem 2.9.11~20110321-15 has caused the Debian Bug report #918443, regarding sl-modem: ftbfs on i386: undefined reference to `minor' 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.) -- 918443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sl-modem Version: 2.9.11~20110321-14 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, sl-modem FTBFS on i386 (but succeeds on amd64): [...] gcc -m32 -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o -Wl,-z,relro -lasound /usr/bin/ld: modem_main.o: in function `mdm_device_setup': ./modem/modem_main.c:642: undefined reference to `minor' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:48: slmodemd] Error 1 Full log attached. Check https://bugs.debian.org/908160 for the solution of the same issue in another package. Andreas sl-modem_2.9.11~20110321-14.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sl-modem Source-Version: 2.9.11~20110321-15 We believe that the bug you reported is fixed in the latest version of sl-modem, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. أحمد المحمودي (Ahmed El-Mahmoudy) (supplier of updated sl-modem 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, 08 Jan 2019 05:01:59 +0100 Source: sl-modem Binary: sl-modem-dkms sl-modem-daemon Architecture: source amd64 i386 Version: 2.9.11~20110321-15 Distribution: unstable Urgency: medium Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: sl-modem-daemon - SmartLink software modem daemon sl-modem-dkms - SmartLink software modem driver - module building source Closes: 918443 Changes: sl-modem (2.9.11~20110321-15) unstable; urgency=medium . * Add fix-glibc-2.28-ftbfs.diff patch to fix FTBFS with glibc 2.28. Thanks to Ben Hutchings (Closes: #918443) Checksums-Sha1: 4b94cf90828d581e8060eb26ad2bce1c351ab93d 1871 sl-modem_2.9.11~20110321-15.dsc f14c0337baa7c26c1c74f5c9cfa4da975ad9 34736 sl-modem_2.9.11~20110321-15.debian.tar.xz e3db564afe5a1399fd01be216ffe9f6f524e634f 468700 sl-modem-daemon_2.9.11~20110321-15_i386.deb a912469a45d572249555bba99cd481462e033f54 205812 sl-modem-dkms_2.9.11~20110321-15_i386.deb 8c33b6060524164e588e6af69af689a4ed90d5af 205808 sl-modem-dkms_2.9.11~20110321-15_amd64.deb Checksums-Sha256: 17a7d6de09355462b96dafbadd1dbee391b7dbdee95f0327b12f77bbedbd97b3 1871 sl-modem_2.9.11~20110321-15.dsc 4f71862cad3a09a56a18882aa4d916a908bdb8afa78c15762e819cbc9c1c5b20 34736 sl-modem_2.9.11~20110321-15.debian.tar.xz ebc52e1f110c4bf6653ff0e567c900ee26b691b07fffe6e5441bcf8745d196f2 468700 sl-modem-daemon_2.9.11~20110321-15_i386.deb 336c8b0b9dfc4262963dfd0998a69fad02505a0c76fbe6c4334a9c9fb8b63f70 205812 sl-modem-dkms_2.9.11~20110321-15_i386.deb b1d79ef68a57ed64d4a2edcf779a4aee7fe08b4bbf263b65f9fc108b1a982c1c 205808 sl-modem-dkms_2.9.11~20110321-15_amd64.deb Files: cfe14acbb3062e67bc1281376e620a11 1871 non-free/misc optional sl-modem_2.9.11~20110321-15.dsc 6cde494834b699674b07708169471b04 34736 non-free/misc optional sl-modem_2.9.11~20110321-15.debian.tar.xz 33588be040787a1ca62b3a657679f209 468700 non-free/misc optional sl-modem-daemon_2.9.11~20110321-15_i386.deb 6990e039ff658a407f6041ecd889e2f8 205812 non-free/kernel optional sl-modem-dkms_2.9.11~20110321-15_i386.deb 091c442c994d5c87aecaf21292d46423 205808 non-free/kernel optional sl-modem-dkms_2.9.11~20110321-15_amd64.deb -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJcNCZnAAoJELwZapTt3aG3lysH/3G6DHkgFfwCaUpH9GN/t9KD s8RSGN6fL/AXCa1TGxqpftf6TxHSj+/8B7VWBS3dG7UA7pK5LFS1E20w2EBjy3I0
Bug#918516: marked as done (git-lfs FTBFS with Go 1.11)
Your message dated Tue, 08 Jan 2019 04:04:25 + with message-id and subject line Bug#918516: fixed in git-lfs 2.6.1-3 has caused the Debian Bug report #918516, regarding git-lfs FTBFS with Go 1.11 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.) -- 918516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-lfs Version: 2.6.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/git-lfs.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/git-lfs-2.6.1' cd obj-x86_64-linux-gnu/src/github.com/git-lfs/git-lfs && go generate ./commands go: disabling cache (/nonexistent/first-build/.cache/go-build) due to initialization failure: mkdir /nonexistent: permission denied go: cannot use modules with build cache disabled make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: git-lfs Source-Version: 2.6.1-3 We believe that the bug you reported is fixed in the latest version of git-lfs, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Gelman (supplier of updated git-lfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 21:40:31 -0600 Source: git-lfs Binary: git-lfs Architecture: source Version: 2.6.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Stephen Gelman Description: git-lfs- Git Large File Support Closes: 918516 Changes: git-lfs (2.6.1-3) unstable; urgency=medium . * Use DH_GOLANG_GO_GENERATE instead of running it separately (Closes: #918516) Checksums-Sha1: 9469cbba46b1a7d9269f8ef97199d4cf39368e00 2522 git-lfs_2.6.1-3.dsc 514350d958d61ebcf2f1cc6faff9d05b05eeea30 4188 git-lfs_2.6.1-3.debian.tar.xz 5e9427bde4b520ad05e0de98cc684d3c8efb7340 1 git-lfs_2.6.1-3_amd64.buildinfo Checksums-Sha256: 5b4a88bf5516c5e9ce17314b2e3f4cef93a16d88800ca467623e8b3491f7ecf5 2522 git-lfs_2.6.1-3.dsc bbd31356eb4c3766f1cc16a56762bc6f41f89c4135b94363186472091dc74923 4188 git-lfs_2.6.1-3.debian.tar.xz dc17113cf6974af20785329a30ed5d98ed282ad1d871490ca6d94e400e449cc5 1 git-lfs_2.6.1-3_amd64.buildinfo Files: 7423daa3e39cfc3a66081ad9b2a6a1f3 2522 vcs optional git-lfs_2.6.1-3.dsc 4e090fac7ecba2eb73878317f63ece79 4188 vcs optional git-lfs_2.6.1-3.debian.tar.xz 66e186e598690ca38705ec29b89c17c3 1 vcs optional git-lfs_2.6.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPwDop1BN06KlsbfijqM4hED8f1wFAlw0G+ESHHNzZ2VsbUBk ZWJpYW4ub3JnAAoJEI6jOIRA/H9c/DkQAKAlPFTnL85FVk6dqbbrERTNTeZExFB1 L2e8vn6IFvdCQqBlv7AjIU/hgk+yFh5iTJwRPMj9R4dRnM0dwTXRYE7mH+4S5Ju2 4Jg+rznSVsFs3ETxjiDLngUIFz/rCKtsvK4fasGUVw6gY/a8Wsag1ZqnpWmStVnJ tUoOarbQOq4VqBq8Li110RGAfLUeRVVPxLWPAProDAamLSLH/dB8o+H2oEdrxOoj RYU5raq+lxio8RRUsfrJ8o0tZnb350Kw90E03OFjA1yVcyOHM4aedyA/YJLJLc0V 9uqnHQnd0C6d1WG3ejHD90KWJmwy8CJmEP1AqbrR9d4MES/auetTF0cAJk52GTG0 CPjz/e3L6lTRSnQuA63y5iGcYAqwDaIFhyGYRYTLK46ZLBPYfUjRXSITFoTtNt78 7h0midiRn9xstHwniwHIgLndRl05G4Gnof/2GmARdJgw+wrbWIe1hH1lh0qyhtZX 6nENxAtpHL/nWtKqbLKFP10rYA6/XLDb8HkB6w2LT9h7eqcwdvmNlmSXQtOTrH9f gQdSl9HtBKXkZqSPQuPctE5Tc8hYZzqz0i2XKzKIk/ftE3EWHPJhtZN+8kjFgIrp cnySQmH8EzkA2womo6b9eh4XKPGek1UZAdk0kVrwhWMbrdh9s7MrxCNdqN8xTy8C uHKZHjQVlwjV =Hw3l -END PGP SIGNATURE End Message ---
Bug#918516: marked as done (git-lfs FTBFS with Go 1.11)
Your message dated Tue, 08 Jan 2019 02:40:36 + with message-id and subject line Bug#918516: fixed in git-lfs 2.6.1-2 has caused the Debian Bug report #918516, regarding git-lfs FTBFS with Go 1.11 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.) -- 918516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-lfs Version: 2.6.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/git-lfs.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/git-lfs-2.6.1' cd obj-x86_64-linux-gnu/src/github.com/git-lfs/git-lfs && go generate ./commands go: disabling cache (/nonexistent/first-build/.cache/go-build) due to initialization failure: mkdir /nonexistent: permission denied go: cannot use modules with build cache disabled make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: git-lfs Source-Version: 2.6.1-2 We believe that the bug you reported is fixed in the latest version of git-lfs, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Gelman (supplier of updated git-lfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 19:30:31 -0600 Source: git-lfs Binary: git-lfs Architecture: source Version: 2.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Stephen Gelman Description: git-lfs- Git Large File Support Closes: 918516 Changes: git-lfs (2.6.1-2) unstable; urgency=medium . * Move go cache from $HOME into build directory (Closes: #918516) * Bump standards version to 4.3.0 Checksums-Sha1: 377d00d32cbf32b14c5657808e2f1ef177992f5b 2522 git-lfs_2.6.1-2.dsc 2789375662a0406b111e533263d4000456bf59c5 3944 git-lfs_2.6.1-2.debian.tar.xz 7b399f83148eef930ce5cbdfa9dec614f8fd1952 1 git-lfs_2.6.1-2_amd64.buildinfo Checksums-Sha256: 9095e5275e95f21664327ce6bd26b3742973b19e7faa33b2b5f9f762da3be082 2522 git-lfs_2.6.1-2.dsc b9e61cb64185a515de8d9ff2e4290047b64e0537a5afa43e20a5ad61c54d5665 3944 git-lfs_2.6.1-2.debian.tar.xz 98171eab72931e9ab16bf5c408b94c0455cda73939d3e7ace6643af46abb8da5 1 git-lfs_2.6.1-2_amd64.buildinfo Files: b4c50ea8c7e96f942db8599299052bb6 2522 vcs optional git-lfs_2.6.1-2.dsc 72395b20edb459466e8c7fc16e6354fb 3944 vcs optional git-lfs_2.6.1-2.debian.tar.xz 27fd6cb8b5bcdf529e22c8282f996bec 1 vcs optional git-lfs_2.6.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPwDop1BN06KlsbfijqM4hED8f1wFAlwz/3ISHHNzZ2VsbUBk ZWJpYW4ub3JnAAoJEI6jOIRA/H9c2lIP/jn+md8GzaoyCVitB1HHmIS64+KwODwz ekxh99iJle4jmsPGO/YHJqTJa5zLLHefUEguKitBJWBTvz5kpMYrzIq2UKSyjoBI h6j5Efsz5BNSnipGbx6N+dDW1o/fsRTJFPEkpNIyx5DXEirUkOZ88If6DQij3cu0 E4/7uEWNaEu4/LGracXCbPdDVvzoo2d1rqxYskM33p3g+uoP+Kz9DpbaN1do/nW1 ibwIQmeMFb7pzgr7AAAlMukOUd5AMT2szBBGQE9JaRNYL5u3TDMSoAUc8835gbMP fSFTZNcZAC+QaXJyvnKBEUPGhjHwywORvKFoCklNgJ7G2EyNQzNvbrdorNIoUSnG 8vNpd2nF96RU62dLFQRfP7lwW8YVnloFLtdCu0T1VoIXxZ5bTKTAGoaLjCDRKTow oxHVMUfe/ya/WGQi7UHZPfJWUObOj9AX5qJOpn1OfeiNuseX6s2bdd/oJ38dxoJR OIwKcAZ6YyQy7layNqTFvRhUuFAzku1sru+huMYjQPRKmF9OBjUqzKwEp4E+etEJ L4RSJ8X7eMJ/fUFiua+zbxsT5Uy3OjnSs8TOFuS1Brf1RbxhZ+RJcHJEwa64msAa D2jnqKURCNe8jZGflH4T7f+oK4WAkNdNkqRNca/M+5laoOo/l9o+ipf/tpDyYrYI EPvUHu0dIz+s =Jge5 -END PGP SIGNATURE End Message ---
Processed: Bug #918516 in git-lfs marked as pending
Processing control commands: > tag -1 pending Bug #918516 [src:git-lfs] git-lfs FTBFS with Go 1.11 Added tag(s) pending. -- 918516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918516: Bug #918516 in git-lfs marked as pending
Control: tag -1 pending Hello, Bug #918516 in git-lfs 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/go-team/packages/git-lfs/commit/c05aa080fdf9a05d09f2a3c26a1a9f201a79ddfd Update package for 2.6.1-2 release * Move go cache from $HOME into build directory (Closes: #918516) * Bump standards version to 4.3.0 (this message was generated automatically) -- Greetings https://bugs.debian.org/918516
Bug#859675: marked as done (radsecproxy: Please migrate to openssl1.1 in Buster)
Your message dated Tue, 08 Jan 2019 01:34:08 + with message-id and subject line Bug#859675: fixed in radsecproxy 1.7.2-1 has caused the Debian Bug report #859675, regarding radsecproxy: Please migrate to openssl1.1 in Buster 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.) -- 859675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: radsecproxy Version: 1.6.7-1 Severity: important Tags: sid buster fixed-upstream User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1-trans control: forwarded -1 https://project.nordu.net/browse/RADSECPROXY-66 Please migrate to libssl-dev in the Buster cycle. The bug report about the FTBFS is #828527. The log of the FTBFS can be found at https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/radsecproxy_1.6.7-1_amd64-20160529-1530 Sebastian --- End Message --- --- Begin Message --- Source: radsecproxy Source-Version: 1.7.2-1 We believe that the bug you reported is fixed in the latest version of radsecproxy, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Faidon Liambotis (supplier of updated radsecproxy 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, 08 Jan 2019 03:16:13 +0200 Source: radsecproxy Binary: radsecproxy Architecture: source Version: 1.7.2-1 Distribution: unstable Urgency: medium Maintainer: Faidon Liambotis Changed-By: Faidon Liambotis Description: radsecproxy - RADIUS protocol proxy supporting RadSec Closes: 859675 872888 Changes: radsecproxy (1.7.2-1) unstable; urgency=medium . * New upstream release. * Bump Build-Depends to OpenSSL 1.1.0 (libssl-dev), as the new upstream version is now compatible with it. (Closes: #859675) * Remove --enable-fticks from configure, as it's now default and non-optional. * Update the shipped /etc/radsecproxy.conf with new (commented out) upstream directives. * Use a dedicated "radsecproxy" user to run the daemon instead of root. (Closes: #872888) * Remove dependency on docbook2x since this version ships the pregenerated manpages by default. These are now the preferred source of modification upstream, and the XMLs were removed entirely in a subsequent commit. Also adjust our path-correction patch to patch the manpages directly. * Update debian/upstream/signing-key.asc with the new upstream's key. * Update debian/control, debian/copyright and debian/watch with the project's new homepage on GitHub. * Update debian/copyright with an additional copyright author (SWITCH) and to reflect the license change, i.e. to remove GPLv2+ and update to a generic 3-clause BSD. * Add Vcs-* to point to the package's git at salsa.debian.org. * Bump debhelper compat to 11. * Bump Standards-Version to 4.3.0. Checksums-Sha1: 2e545340393826fca7e838b855b8f8666460626c 2132 radsecproxy_1.7.2-1.dsc f5d71744be53ac5dabbbef4613dae4928e814d27 327759 radsecproxy_1.7.2.orig.tar.gz 4349190fb76230ebd1cd33416b74ef0b31f0a0ee 873 radsecproxy_1.7.2.orig.tar.gz.asc 9b5e103c042a5e4f84492807e66ccfab3ede5e2a 11184 radsecproxy_1.7.2-1.debian.tar.xz 1e53257bcb6fd91c275538b1f2cad00a4def03df 5358 radsecproxy_1.7.2-1_source.buildinfo Checksums-Sha256: a253d0031ccb2b335d01d5bda1049e791b588d5227e18e1e635350aa4f4eb096 2132 radsecproxy_1.7.2-1.dsc 2cf23e618ab9275221350acf5a97bce4ff18aee472045f8a3b4c7673491079d2 327759 radsecproxy_1.7.2.orig.tar.gz 2b68da300c218817529a191b38ec898d0c27cc22b9f6067b904d8242c9c89e14 873 radsecproxy_1.7.2.orig.tar.gz.asc 4f56f9bee3c60b506ceaec170c1a2b1d47f3103105514f803e59f236dedd8a65 11184 radsecproxy_1.7.2-1.debian.tar.xz a8174ce0f4a31c7d7573b851eaa05d8b91c32e0c85a6ba5ebf7f7666a06a697d 5358 radsecproxy_1.7.2-1_source.buildinfo Files: 7b808d0e6d9402688c4353046b59fc89 2132 net optional radsecproxy_1.7.2-1.dsc 6b8538216310f1965fc0636044c757c9 327759 net optional radsecproxy_1.7.2.orig.tar.gz 84bbbe4e23bb591377ff5a69029de74d 873 net optional radsecproxy_1.7.2.orig.tar.gz.asc
Bug#918650: marked as done (python3-pdfminer: missing Breaks+Replaces: python-pdfminer (<< 20181108))
Your message dated Tue, 08 Jan 2019 00:20:15 + with message-id and subject line Bug#918650: fixed in pdfminer 20181108+dfsg-2 has caused the Debian Bug report #918650, regarding python3-pdfminer: missing Breaks+Replaces: python-pdfminer (<< 20181108) 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.) -- 918650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pdfminer Version: 20181108+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-pdfminer_20181108+dfsg-1_all.deb ... Unpacking python3-pdfminer (20181108+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-pdfminer_20181108+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/bin/dumppdf', which is also in package python-pdfminer 20140328+dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-pdfminer_20181108+dfsg-1_all.deb cheers, Andreas python-pdfminer=20140328+dfsg-2_python3-pdfminer=20181108+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pdfminer Source-Version: 20181108+dfsg-2 We believe that the bug you reported is fixed in the latest version of pdfminer, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniele Tricoli (supplier of updated pdfminer 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, 08 Jan 2019 00:34:56 +0100 Source: pdfminer Binary: python-pdfminer python3-pdfminer pdfminer-data Architecture: source all Version: 20181108+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Daniele Tricoli Description: pdfminer-data - PDF parser and analyser (encoding data) python-pdfminer - PDF parser and analyser (Python2) python3-pdfminer - PDF parser and analyser (Python3) Closes: 918650 Changes: pdfminer (20181108+dfsg-2) unstable; urgency=medium . * Add Breaks+Replaces: python-pdfminer (<< 20181108) for python3-pdfminer. (Closes: #918650) Many thanks to Andreas Beckmann for the report. Checksums-Sha1: f3bee7c5b7f648e4b29f868f817a591c9c844478 2561 pdfminer_20181108+dfsg-2.dsc 8f9ee05ae23ba18ac1422eae5121934b5f2ad54d 10684 pdfminer_20181108+dfsg-2.debian.tar.xz 7ac66fe07f3272e3e0873232454a68cf2eeb0940 3984560 pdfminer-data_20181108+dfsg-2_all.deb df0b5f4c8bea348ece82ca86917e109e77601eb7 7369 pdfminer_20181108+dfsg-2_amd64.buildinfo e97e367bff5757464dd60f5b003d2fc3aca79a02 96076 python-pdfminer_20181108+dfsg-2_all.deb 97d4610a9f3991a769caa84f2c763855777c80b4 4074012 python3-pdfminer_20181108+dfsg-2_all.deb Checksums-Sha256: 71d56fece68abc6544e16218449efea9ad73a21f9ec0bddb5a09587b0070205a 2561 pdfminer_20181108+dfsg-2.dsc d5a7240f2d47de35a0b583fcbe78479f757b3293da4b3e0796afb51cba427810 10684 pdfminer_20181108+dfsg-2.debian.tar.xz 583d06044de1227e10092821f7c83ec82532f8738305c0a0bf07b1dbef83b8f2 3984560 pdfminer-data_20181108+dfsg-2_all.deb 4e261c9c84102d0b2bf62c43e1ece565e313ef9d1d2e7fbdcb9795a0b638fcc9 7369 pdfminer_20181108+dfsg-2_amd64.buildinfo 2f0d59c84587d8050d76d2eda6d8bea1d1706a377ca566a3c2e8a891ca1ccb4c 96076 python-pdfminer_20181108+dfsg-2_all.deb 154c3313f6811dc72352a5fe9139231bec93b81609507c0cb9dcccbae7406472 4074012 python3-pdfminer_20181108+dfsg-2_all.deb Files: c6802e88d7c6fc02126826c666f989c7 2561 python optional pdfminer_20181108+dfsg-2.dsc 25a8bb538792467c2a482ac27b755f2c 10684 python optional pdfminer_20181108+dfsg-2.debian.tar.xz
Bug#918004: marked as done (node-inline-source-map FTBFS: test failures)
Your message dated Tue, 08 Jan 2019 00:05:12 +
with message-id
and subject line Bug#918004: fixed in node-inline-source-map 0.6.2~git-2
has caused the Debian Bug report #918004,
regarding node-inline-source-map FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-inline-source-map
Version: 0.6.2~git-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-inline-source-map=all=0.6.2~git-1=1546379862=0
...
17 passing (2s)
9 failing
1) test/source-content.js generated mappings one file with source content
includes source content:
Error: includes source content
+ expected - actual
"sources": [
"foo.js"
]
"sourcesContent": [
-"function foo () {
+"function foo() {
var hello = 'hello';
var world = 'world';
console.log('%s %s', hello, world);
}"
at Test. (test/source-content.js:32:7)
at Test. (test/source-content.js:27:5)
at Object. (test/source-content.js:25:1)
2) test/source-content.js generated mappings one file with source content
encodes generated mappings including source content:
Error: encodes generated mappings including source content
+ expected - actual
-{"version":3,"sources":["foo.js"],"names":[],"mappings":";AACA;AACA;AACA;AACA","file":"","sourceRoot":"","sourcesContent":["function
foo () {\n var hello = 'hello';\n var world = 'world';\n console.log('%s
%s', hello, world);\n}"]}
+{"version":3,"sources":["foo.js"],"names":[],"mappings":";AACA;AACA;AACA;AACA","file":"","sourceRoot":"","sourcesContent":["function
foo() {\n var hello = 'hello';\n var world = 'world';\n console.log('%s
%s', hello, world);\n}"]}
at Test. (test/source-content.js:49:7)
at Test. (test/source-content.js:27:5)
at Object. (test/source-content.js:25:1)
3) test/source-content.js generated mappings one file with source content
returns correct inline mapping url including source content:
Error: returns correct inline mapping url including source content
+ expected - actual
-//#
sourceMappingURL=data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbImZvby5qcyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQTtBQUNBO0FBQ0E7QUFDQTtBQUNBIiwiZmlsZSI6IiIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzQ29udGVudCI6WyJmdW5jdGlvbiBmb28gKCkge1xuICB2YXIgaGVsbG8gPSAnaGVsbG8nO1xuICB2YXIgd29ybGQgPSAnd29ybGQnO1xuICBjb25zb2xlLmxvZygnJXMgJXMnLCBoZWxsbywgd29ybGQpO1xufSJdfQ==
+//#
sourceMappingURL=data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbImZvby5qcyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQTtBQUNBO0FBQ0E7QUFDQTtBQUNBIiwiZmlsZSI6IiIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzQ29udGVudCI6WyJmdW5jdGlvbiBmb28oKSB7XG4gIHZhciBoZWxsbyA9ICdoZWxsbyc7XG4gIHZhciB3b3JsZCA9ICd3b3JsZCc7XG4gIGNvbnNvbGUubG9nKCclcyAlcycsIGhlbGxvLCB3b3JsZCk7XG59Il19
at Test. (test/source-content.js:54:7)
at Test. (test/source-content.js:27:5)
at Object. (test/source-content.js:25:1)
4) test/source-content.js generated mappings two files with source content
includes source content for both files:
Error: includes source content for both files
+ expected - actual
"foo.js"
"bar.js"
]
"sourcesContent": [
-"function foo () {
+"function foo() {
var hello = 'hello';
var world = 'world';
console.log('%s %s', hello, world);
}"
-"function bar () {
+"function bar() {
console.log('yes?');
}"
]
"version": 3
at Test. (test/source-content.js:69:7)
at Test. (test/source-content.js:62:5)
at Object. (test/source-content.js:25:1)
5) test/source-content.js generated mappings two files with source content
encodes generated mappings including source content:
Error: encodes generated mappings including source content
+ expected - actual
-{"version":3,"sources":["foo.js","bar.js"],"names":[],"mappings":"ACAA,ADAA;ACCA,ADAA;ACCA,ADAA;AACA;AACA","file":"","sourceRoot":"","sourcesContent":["function
foo () {\n var hello = 'hello';\n var world = 'world';\n console.log('%s
%s', hello, world);\n}","function bar () {\n console.log('yes?');\n}"]}
Bug#914804: marked as done (pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lboost_python-py27)
Your message dated Mon, 07 Jan 2019 23:35:28 +
with message-id
and subject line Bug#914804: fixed in pycuda 2018.1.1-2
has caused the Debian Bug report #914804,
regarding pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find
-lboost_python-py27
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.)
--
914804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycuda
Version: 2018.1.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
I tried to manually binNMU pycuda for boost1.67, but it failed with
[...]
x86_64-linux-gnu-g++ -pthread -shared -Wl,-Bsymbolic-functions -Wl,-z,relro
-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
-Wl,-z,now -g -O2 -fdebug-prefix-map=/build/pycuda-2018.1.1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/src/cpp/cuda.o
build/temp.linux-amd64-2.7/src/cpp/bitlog.o
build/temp.linux-amd64-2.7/src/wrapper/wrap_cudadrv.o
build/temp.linux-amd64-2.7/src/wrapper/mempool.o
build/temp.linux-amd64-2.7/src/wrapper/wrap_cudagl.o
build/temp.linux-amd64-2.7/src/wrapper/wrap_curand.o -L/usr/lib/stubs
-L/usr/lib64/stubs -L/usr/lib/stubs -L/usr/lib64/stubs -lboost_python-py27
-lboost_thread -lcuda -lcurand -o
/build/pycuda-2018.1.1/.pybuild/cpython2_2.7/build/pycuda/_driver.so
/usr/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1:
/usr/bin/python setup.py build
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:26: binary-arch] Error 25
(there may have been earlier errors, I unfortunately do not have
the full log, only the last screen)
Andreas
--- End Message ---
--- Begin Message ---
Source: pycuda
Source-Version: 2018.1.1-2
We believe that the bug you reported is fixed in the latest version of
pycuda, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Tomasz Rybak (supplier of updated pycuda package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 07 Jan 2019 23:27:54 +0100
Source: pycuda
Binary: python3-pycuda python3-pycuda-dbg python-pycuda python-pycuda-dbg
python-pycuda-doc
Architecture: source amd64 all
Version: 2018.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Tomasz Rybak
Description:
python-pycuda - Python module to access Nvidia‘s CUDA parallel computation API
python-pycuda-dbg - Python module to access Nvidia‘s CUDA API (debug
extensions)
python-pycuda-doc - module to access Nvidia‘s CUDA computation API
(documentation)
python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation
API
python3-pycuda-dbg - Python 3 module to access Nvidia‘s CUDA API (debug
extensions)
Closes: 914804
Changes:
pycuda (2018.1.1-2) unstable; urgency=medium
.
* Fix FTBFS with Boost 1.67 (Closes: #914804)
* Patch from Ubuntu by Gianfranco Costamagna
* Add abort-on-upstream-changes to d/source/local-options.
* Add more hardening options to d/rules.
* Add lintian override for lack of autopkgtest.
* Add DEB_BUILD_OPTIONS terse.
* Update Standards-Version to 4.3.0; no changes necessary.
* Set compatibility level to 12; no changes necessary.
Checksums-Sha1:
3f034252035f5f80c4c567ea37adaf14341dffe9 2715 pycuda_2018.1.1-2.dsc
e9f1a7772b5cf33942503c9cfed9aab88f4212ff 10832 pycuda_2018.1.1-2.debian.tar.xz
fc9a23bcac0462623162a9cd5c35985aa4f88a63 13243
pycuda_2018.1.1-2_amd64.buildinfo
af62ed0afd5694a7af3906a6a49062eaf7aca1a9 6104324
python-pycuda-dbg_2018.1.1-2_amd64.deb
3cc377079231fd8469c60d41d092efa2ad17ff9f 122076
python-pycuda-doc_2018.1.1-2_all.deb
Bug#918654: libnvidia-egl-wayland1: file installation conflict with nvidia-egl-wayland-common
Package: libnvidia-egl-wayland1 Version: 1:1.1.1-1 Severity: serious Tags: patch Dear Maintainer, nvidia-egl-wayland-common in stable and libnvidia-egl-wayland1 in unstable both install: /usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json https://packages.debian.org/stretch/amd64/nvidia-egl-wayland-common/filelist https://packages.debian.org/sid/amd64/libnvidia-egl-wayland1/filelist But the latter does not declare a Conflicts+Replaces on the latter, so upgrading fails: $ sudo apt install libnvidia-egl-wayland1=1:1.1.1-1+b1 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libnvidia-egl-wayland1 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/18.0 kB of archives. After this operation, 66.6 kB of additional disk space will be used. Selecting previously unselected package libnvidia-egl-wayland1:amd64. (Reading database ... 438463 files and directories currently installed.) Preparing to unpack .../libnvidia-egl-wayland1_1%3a1.1.1-1+b1_amd64.deb ... Unpacking libnvidia-egl-wayland1:amd64 (1:1.1.1-1+b1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-egl-wayland1_1%3a1.1.1-1+b1_amd64.deb (--unpack): trying to overwrite '/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json', which is also in package nvidia-egl-wayland-common 384.130-1 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-egl-wayland1_1%3a1.1.1-1+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Setting the severity to delay the migration to buster. The trivial fix is provided on Salsa: https://salsa.debian.org/debian/egl-wayland/merge_requests/1 -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: retitle 918499 to [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1
Processing commands for cont...@bugs.debian.org: > retitle 918499 [libreoffice] libreoffice: fails with ERROR 4 forking process > with apparmor << 2.13.1 Bug #918499 [libreoffice] [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1 Ignoring request to change the title of bug#918499 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 918499 to [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1
Processing commands for cont...@bugs.debian.org: > retitle 918499 [libreoffice] libreoffice: fails with ERROR 4 forking process > with apparmor << 2.13.1 Bug #918499 [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor Changed Bug title to '[libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1' from 'libreoffice: fails with ERROR 4 forking process with apparmor'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918653: egl-wayland: misplaced Conflicts+Replaces
Source: egl-wayland Version: 1:1.1.1-1 Severity: serious Hi, the Conflicts+Replaces need to be added to the library package, not to the -dev package. The library package contains the files that were placed in other packages, too. I'm not sure about the Ubuntu packages, in case they shipped a .so link, they should have a C+R in the -dev package too. The Debian packages should never have shipped a .so symlink. Andreas
Processed: found 918583 in 2.28-2
Processing commands for cont...@bugs.debian.org: > found 918583 2.28-2 Bug #918583 [libc6] libc6: version in nocache Breaks is incorrect Marked as found in versions glibc/2.28-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 918583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918491: marked as done (coffeescript: FTBFS with nodejs 10.x (The "error/message" argument is ambiguous))
Your message dated Mon, 07 Jan 2019 23:19:12 +
with message-id
and subject line Bug#918491: fixed in coffeescript 1.12.8~dfsg-3
has caused the Debian Bug report #918491,
regarding coffeescript: FTBFS with nodejs 10.x (The "error/message" argument is
ambiguous)
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.)
--
918491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:coffeescript
Version: 1.12.8~dfsg-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules binary-indep
CDBS WARNING: copyright-check disabled - licensecheck is missing.
test -x debian/rules
dh_testroot
dh_prep
dh_installdirs -A
mkdir -p "."
Scanning upstream source for new/changed copyright notices...
set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive
--copyright --deb-fmt --ignore
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * |
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: /usr/bin/licensecheck: not found
0 combinations of copyright and licensing found.
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
mkdir -p "debian/upstream-cruft"
cp -a "lib" "debian/upstream-cruft/lib";
touch debian/stamp-upstream-cruft
mkdir -p docs/v1/browser-compiler
chmod +x bin/cake
bin/cake build
bin/cake build
bin/cake build:browser
bin/cake test
[0;31mfailed 1 and passed 855 tests in 10.37 seconds[0m[0m
[0;31m basic exception throwing[0m
[0;31m TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is
ambiguous. The error "error" is identical to the message.
at expectsError (assert.js:1:1)
at throws (assert.js:1:1)
at Function.
(/<>/test/exception_handling.coffee:1:1)
at global.test (/<>/Cakefile:1:1)
at Object. (/<>/test/exception_handling.coffee:1:1)
at Object. (/<>/test/exception_handling.coffee:1:1)
at Module._compile (internal/modules/cjs/loader.js:1:1)
at Object.exports.run
(/<>/lib/coffee-script/coffee-script.js:1:1)
at runTests (/<>/Cakefile:1:1)
at Object.action (/<>/Cakefile:1:1)
at invoke (/<>/lib/coffee-script/cake.js:1:1)
at Object.exports.run (/<>/lib/coffee-script/cake.js:1:1)
at Object. (/<>/bin/cake:1:1)
at Module._compile (internal/modules/cjs/loader.js:1:1)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1:1)
at Module.load (internal/modules/cjs/loader.js:1:1)
at tryModuleLoad (internal/modules/cjs/loader.js:1:1)
at Function.Module._load (internal/modules/cjs/loader.js:1:1)
at Function.Module.runMain (internal/modules/cjs/loader.js:1:1)
at startup (internal/bootstrap/node.js:1:1)
at bootstrapNodeJSCore (internal/bootstrap/node.js:1:1)
[0m
function() {
return throws((function() {
throw 'error';
}), 'error');
}
make: *** [debian/rules:37: debian/stamp-build] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/coffeescript.html
where you can get a full build log if you need it.
[ Note: It fails in sid but it builds ok in buster ]
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: coffeescript
Source-Version: 1.12.8~dfsg-3
We believe that the bug you reported is fixed in the latest version of
coffeescript, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated coffeescript package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 07 Jan
Bug#918652: leaflet: fails to clean after build: rm: cannot remove './debian/js': Is a directory
Source: leaflet Version: 1.0.3~dfsg-2 Severity: serious Hi, leaflet fails to build twice in a row because cleaning afte rthe first build errors out: debian/rules clean dh clean dh_clean rm: cannot remove './debian/js': Is a directory dh_clean: rm -f -- debian/libjs-leaflet.substvars ./debian/js debian/files returned exit code 1 make: *** [debian/rules:4: clean] Error 1 You probably need to add a trailing slash to directory trees to be removed via debian/clean. Andreas leaflet_1.0.3~dfsg-2_twice.log.gz Description: application/gzip
Processed: Re: Bug#918648: watcher: FTBFS (autobuilder hangs)
Processing commands for cont...@bugs.debian.org: > severity 918648 serious Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs when built with eatmydata) Severity set to 'serious' from 'normal' > retitle 918648 watcher: FTBFS (autobuilder hangs) Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs when built with eatmydata) Changed Bug title to 'watcher: FTBFS (autobuilder hangs)' from 'watcher: FTBFS (autobuilder hangs when built with eatmydata)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #918499 in libreoffice marked as pending
Processing control commands: > tag -1 pending Bug #918499 [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor Ignoring request to alter tags of bug #918499 to the same tags previously set -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918499: Bug #918499 in libreoffice marked as pending
Control: tag -1 pending Hello, Bug #918499 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/0ee5e7ce3c4dac09fa92f23218f66375194d7c83 bump recommends for apparmor to >= 2.13.1 and conflict against apparmor (<< 2.13.1~) (closes: #918499) (this message was generated automatically) -- Greetings https://bugs.debian.org/918499
Processed: tagging 918647
Processing commands for cont...@bugs.debian.org: > tags 918647 + buster sid Bug #918647 [src:morfologik-stemming] morfologik-stemming: FTBFS (cannot find symbol IntIntOpenHashMap) Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 918647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 918499 to libreoffice: fails with ERROR 4 forking process with apparmor ...
Processing commands for cont...@bugs.debian.org: > retitle 918499 libreoffice: fails with ERROR 4 forking process with apparmor Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Changed Bug title to 'libreoffice: fails with ERROR 4 forking process with apparmor' from 'libreoffice: fails with 'ERROR 4 forking process''. > found 918499 1:6.1.3-2 Bug #918499 [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor Ignoring request to alter found versions of bug #918499 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 918499 in 1:6.2.0~beta1-1
Processing commands for cont...@bugs.debian.org: > found 918499 1:6.2.0~beta1-1 Bug #918499 [libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor Marked as found in versions libreoffice/1:6.2.0~beta1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918499: libreoffice: fails with 'ERROR 4 forking process'
severity 918499 serious tag 918499 - unreproducible tag 918499 - moreinfo tag 918499 + confirmed tag 918499 + pending thanks Hi, On Mon, Jan 07, 2019 at 09:20:12PM +0700, Tunggul Arif Siswoyo wrote: > On Mon, 7 Jan 2019 20:46:28 +0700 Tunggul Arif Siswoyo > wrote: > > [skip] > > I think it is related with apparmor configs. I'm not sure what caused it Ah, good point. [...] > 1 profiles are in complain mode. > > >libreoffice-oopslash > > Note that this in complain mode only. But where is soffice.bin? ... > Jan 07 20:13:09 ikigai apparmor[430]: AppArmor parser error for > /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in > /etc/apparmor.d/usr.lib.libreoffice.pr…ractions/mesa' > Jan 07 20:13:09 ikigai apparmor[430]: failed! > Jan 07 20:13:09 ikigai systemd[1]: apparmor.service: Main process exited, > code=exited, status=123/n/a > Jan 07 20:13:09 ikigai systemd[1]: apparmor.service: Failed with result > 'exit-code'. > Jan 07 20:13:09 ikigai systemd[1]: Failed to start Load AppArmor profiles. > Hint: Some lines were ellipsized, use -l to show in full. > > Error message above caused by invalid config in apparmor profile for > soffice.bin in line 90 : .. ah. here... :( > root@ikigai:~# aa-remove-unknown > AppArmor parser error for > /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in > /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin at line 90: Could not > open 'abstrac > tions/mesa' Aha. :-( But this is present in testings apparmor rene@frodo:~$ dpkg -S /etc/apparmor.d/abstractions/mesa dpapparmor: /etc/apparmor.d/abstractions/mesa rene@frodo:~$ dpkg -l apparmor Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++-==---== ii apparmor 2.13.1-3+b1 amd64user-space parser utility for AppArmor In your other mail you (well, reportbug...) writes: | Versions of packages libreoffice-common recommends: | ii apparmor2.13-8 Why that old version of apparmor? Testing has 2.13.1 since last year November, actually even a newer one migrated today. See https://packages.qa.debian.org/a/apparmor.html But indeed the Recommends is not strict enough, according to http://bugs.debian.org/918499 this must be >= 2.13.1 instead of just >= 2.13. Will fix. (And add a conflicts against older apparmors.) But you should properly upgrade your system nevertheless. Regards, Rene
Bug#918642: imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in)
control: fowarded -1 https://github.com/ImageMagick/ImageMagick/issues/1442 Thanks On Mon, Jan 7, 2019 at 10:57 PM Cédric Boutillier wrote: > > Package: imagemagick > Version: 8:6.9.10.23+dfsg-1 > Severity: serious > Tags: upstream > > Dear Maintainer, > > After the upgrade from 6.9.10.14 to 6.9.10.23, I noticed that the > autopkgtests for the package ruby-mini-magick is failing due to one test > about checking units to show the size of the image in cm and inches. > > I could isolate the problem by running the `identify` command on a test > image (rgb.png in the spec/fixtures directory of the ruby-mini-magick > source package). > > Running: > identify -verbose -units PixelsPerInch rgb.png > output_in.txt > identify -verbose -units PixelsPerCentimeter rgb.png > output_cm.txt > diff -u output_in.txt output_cm.txt > > gives me the following with 8:6.9.10-14 from testing: > > --- /tmp/output_cm.txt 2019-01-07 22:32:49.257702663 +0100 > +++ /tmp/output_in.txt 2019-01-07 22:32:40.457055525 +0100 > @@ -3,9 +3,9 @@ >Mime type: image/png >Class: PseudoClass >Geometry: 16x12+0+0 > - Resolution: 118.11x118.11 > - Print size: 0.135467x0.1016 > - Units: PixelsPerCentimeter > + Resolution: 300x300 > + Print size: 0.053x0.04 > + Units: PixelsPerInch >Colorspace: sRGB >Type: Palette >Base type: Undefined > @@ -118,12 +118,11 @@ > signature: > 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd >Artifacts: > filename: rgb.png > -units: PixelsPerCentimeter > +units: PixelsPerInch > verbose: true >Tainted: False >Filesize: 359B >Number pixels: 192 > - Pixels per second: 19200B > - User time: 0.010u > - Elapsed time: 0:01.010 > + User time: 0.000u > + Elapsed time: 0:01.000 >Version: ImageMagick 6.9.10-14 Q16 x86_64 20181023 https://imagemagick.org > > whereas it gives the following with 8:6.9.10-23 (with a suffix -23 to > the text files). > > --- /tmp/output_cm-23.txt 2019-01-07 22:34:38.136761722 +0100 > +++ /tmp/output_in-23.txt 2019-01-07 22:34:45.201163917 +0100 > @@ -5,7 +5,7 @@ >Geometry: 16x12+0+0 >Resolution: 118.11x118.11 >Print size: 0.135467x0.1016 > - Units: PixelsPerCentimeter > + Units: PixelsPerInch >Colorspace: sRGB >Type: Palette >Base type: Undefined > @@ -118,7 +118,7 @@ > signature: > 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd >Artifacts: > filename: rgb.png > -units: PixelsPerCentimeter > +units: PixelsPerInch > verbose: true >Tainted: False >Filesize: 359B > > Maybe it was induced by this change? > https://github.com/ImageMagick/ImageMagick6/commit/8c7648a1adf7bba35594074f191affd3ff3263bb > > Attaching the reference image and the full output files. > > I am setting severity serious, as it breaks the testsuite of > ruby-mini-magick and provides wrong data when identifying images. > > Thank you in advance > > Cédric > > > > -- Package-specific info: > ImageMagick program version > --- > animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > convert: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > composite: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > conjure: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > display: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > identify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > import: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > mogrify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > montage: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > stream: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), > (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages imagemagick depends on: > ii imagemagick-6.q16 8:6.9.10.23+dfsg-1 > > imagemagick recommends no packages. > > imagemagick suggests no packages. > > -- no debconf information
Bug#918499: Bug #918499 in libreoffice marked as pending
Control: tag -1 pending Hello, Bug #918499 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/0ee5e7ce3c4dac09fa92f23218f66375194d7c83 bump recommends for apparmor to >= 2.13.1 and conflict against apparmor (<< 2.13.1~) (closes: #918499) (this message was generated automatically) -- Greetings https://bugs.debian.org/918499
Bug#918491: Bug #918491 in coffeescript marked as pending
Control: tag -1 pending Hello, Bug #918491 in coffeescript reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/coffeescript/commit/3a9b352f82ad313e24b18e9b6ed9012f1ec5d53f Add workaround patch Closes: #918491 (this message was generated automatically) -- Greetings https://bugs.debian.org/918491
Processed: Bug #918491 in coffeescript marked as pending
Processing control commands: > tag -1 pending Bug #918491 [src:coffeescript] coffeescript: FTBFS with nodejs 10.x (The "error/message" argument is ambiguous) Added tag(s) pending. -- 918491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #918499 in libreoffice marked as pending
Processing control commands: > tag -1 pending Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Ignoring request to alter tags of bug #918499 to the same tags previously set -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#918499: libreoffice: fails with 'ERROR 4 forking process'
Processing commands for cont...@bugs.debian.org: > severity 918499 serious Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Severity set to 'serious' from 'important' > tag 918499 - unreproducible Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Removed tag(s) unreproducible. > tag 918499 - moreinfo Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Removed tag(s) moreinfo. > tag 918499 + confirmed Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Added tag(s) confirmed. > tag 918499 + pending Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 918642
Processing commands for cont...@bugs.debian.org: > affects 918642 ruby-mini-magick Bug #918642 [imagemagick] imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in) Added indication that 918642 affects ruby-mini-magick > thanks Stopping processing here. Please contact me if you need assistance. -- 918642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 918642 in imagemagick/8:6.9.10.14+dfsg-7
Processing commands for cont...@bugs.debian.org: > notfound 918642 imagemagick/8:6.9.10.14+dfsg-7 Bug #918642 [imagemagick] imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in) Ignoring request to alter found versions of bug #918642 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 918642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918650: python3-pdfminer: missing Breaks+Replaces: python-pdfminer (<< 20181108)
Package: python3-pdfminer Version: 20181108+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-pdfminer_20181108+dfsg-1_all.deb ... Unpacking python3-pdfminer (20181108+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-pdfminer_20181108+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/bin/dumppdf', which is also in package python-pdfminer 20140328+dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-pdfminer_20181108+dfsg-1_all.deb cheers, Andreas python-pdfminer=20140328+dfsg-2_python3-pdfminer=20181108+dfsg-1.log.gz Description: application/gzip
Bug#918646:
Maybe this helps? http://lists.gnu.org/r/emacs-diffs/2018-12/msg00377.html
Processed: Re: Bug#918499: libreoffice: fails with 'ERROR 4 forking process'
Processing commands for cont...@bugs.debian.org: > tag 918499 + moreinfo Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Added tag(s) moreinfo. > tag 918499 + unreproducible Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Added tag(s) unreproducible. > severity 918499 important Bug #918499 [libreoffice] libreoffice: fails with 'ERROR 4 forking process' Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#918584: os-autoinst FTBFS on i386: FAIL: 01-test_needle.t
Processing control commands: > forwarded -1 https://progress.opensuse.org/issues/45782 Bug #918584 [src:os-autoinst] os-autoinst FTBFS on i386: FAIL: 01-test_needle.t Set Bug forwarded-to-address to 'https://progress.opensuse.org/issues/45782'. -- 918584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918584: os-autoinst FTBFS on i386: FAIL: 01-test_needle.t
control: forwarded -1 https://progress.opensuse.org/issues/45782 On Mon, 07 Jan 2019 17:48:40 +0200 Adrian Bunk wrote: > not ok 14 - found area is the original one too > # Failed test 'found area is the original one too' > # at ./01-test_needle.t line 73. > # got: '944' > # expected: '108' Thanks, I got same result with upstream master, forwarded to them. -- Hideki Yamane
Processed: Re: Bug#915112 closed by Alastair McKinstry (fixed in 2.1.0-3)
Processing control commands:
> reopen -1
Bug #915112 {Done: Alastair McKinstry } [src:glew] pymol:
FTBFS with glew 2.1
Bug reopened
Ignoring request to alter fixed versions of bug #915112 to the same values
previously set
> retitle -1 glew: incompatible with glext.h from current mesa
Bug #915112 [src:glew] pymol: FTBFS with glew 2.1
Changed Bug title to 'glew: incompatible with glext.h from current mesa' from
'pymol: FTBFS with glew 2.1'.
--
915112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915112: closed by Alastair McKinstry (fixed in 2.1.0-3)
Control: reopen -1 Control: retitle -1 glew: incompatible with glext.h from current mesa On 2019-01-07 22:45, Debian Bug Tracking System wrote: > fixed 2.1.0-3 Nope. Andreas
Bug#918647: morfologik-stemming: FTBFS (cannot find symbol IntIntOpenHashMap)
Package: src:morfologik-stemming Version: 1.9.0+dfsg-0.1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep test -x debian/rules mkdir -p "." /usr/share/maven-debian-helper/copy-repo.sh /<>/morfologik-stemming-1.9.0+dfsg/debian mh_patchpoms -plibmorfologik-stemming-java --debian-build --keep-pom-version --maven-repo=/<>/morfologik-stemming-1.9.0+dfsg/debian/maven-repo --build-no-docs touch debian/stamp-poms-patched # before-build target may be used to unpatch the pom files, so we need to check if # patching the pom files is needed here, normally not if [ ! -f pom.xml.save ]; then \ /usr/bin/make -f debian/rules patch-poms; \ fi cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar: -Dproperties.file.manual=/<>/morfologik-stemming-1.9.0+dfsg/debian/maven.properties -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<>/morfologik-stemming-1.9.0+dfsg org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Dmaven.repo.local=/<>/morfologik-stemming-1.9.0+dfsg/debian/maven-repo package -DskipTests WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) [... snipped ...] [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSA5Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSA5Serializer.java:[72,13] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSA5Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSAInfo.java:[55,60] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSAInfo.FinalStateVisitor [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSAUtils.java:[184,15] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSAUtils [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSAUtils.java:[184,47] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSAUtils [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/CFSA2Serializer.java:[63,45] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.CFSA2Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/CFSA2Serializer.java:[68,45] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.CFSA2Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/CFSA2Serializer.java:[219,15] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.CFSA2Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/CFSA2Serializer.java:[386,9] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.CFSA2Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/CFSA2Serializer.java:[386,45] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.CFSA2Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSA5Serializer.java:[67,45] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSA5Serializer [[1;31mERROR[m] /<>/morfologik-stemming-1.9.0+dfsg/morfologik-fsa/src/main/java/morfologik/fsa/FSA5Serializer.java:[72,45] cannot find symbol [[1;31mERROR[m] symbol: class IntIntOpenHashMap [[1;31mERROR[m] location: class morfologik.fsa.FSA5Serializer [[1;31mERROR[m] -> [1m[Help 1][m [[1;31mERROR[m] [[1;31mERROR[m] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch. [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full debug logging. [[1;31mERROR[m] [[1;31mERROR[m] For more
Bug#918645: dfwinreg: FTBFS (failing tests)
Package: src:dfwinreg Version: 20181214-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with=python2,python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/cpython2_2.7_dfwinreg/build/dfwinreg [... snipped ...] warning: no files found matching '*.py' under directory 'examples' writing manifest file 'dfwinreg.egg-info/SOURCES.txt' copying dfwinreg/dtfabric.yaml -> /<>/.pybuild/cpython2_2.7_dfwinreg/build/dfwinreg I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/key_paths.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/interface.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/fake.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/py2to3.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/definitions.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/__init__.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/glob2regex.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/decorators.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/errors.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/virtual.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/regf.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/registry.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg copying dfwinreg/registry_searcher.py -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg running egg_info writing dfwinreg.egg-info/PKG-INFO writing dependency_links to dfwinreg.egg-info/dependency_links.txt writing top-level names to dfwinreg.egg-info/top_level.txt reading manifest file 'dfwinreg.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching '.gitignore' warning: no previously-included files found matching '*.pyc' warning: no previously-included files matching '*.pyc' found under directory 'dfwinreg' warning: no files found matching '*.py' under directory 'examples' writing manifest file 'dfwinreg.egg-info/SOURCES.txt' copying dfwinreg/dtfabric.yaml -> /<>/.pybuild/cpython3_3.7_dfwinreg/build/dfwinreg debian/rules override_dh_auto_test make[1]: Entering directory '/<>' python run_tests.py Using Python version 2.7.15+ (default, Nov 28 2018, 16:27:22) [GCC 8.2.0] Checking availability and versions of dependencies. [OK]dfdatetime version: 20181025 [OK]dtfabric version: 20180808 [OK]pyregf version: 20170130 [FAILURE] missing: yaml make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:10: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dfwinreg.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#918646: emacs: FTBFS (failing tests)
Package: src:emacs Version: 1:26.1+1-3 Severity: serious Tags: ftbfs Hello Rob. I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --parallel debian/rules override_dh_testdir make[1]: Entering directory '/<>/emacs-26.1+1' dh_testdir debian/emacsVAR.postinst make[1]: Leaving directory '/<>/emacs-26.1+1' debian/rules override_dh_auto_build make[1]: Entering directory '/<>/emacs-26.1+1' rm -rf debian/build-src debian/build-gtk debian/build-lucid debian/build-nox mkdir debian/build-src cp -a $(ls -A | egrep -v '^(\.git|\.pc|debian)$') debian/build-src cp -a /usr/share/misc/config.guess /usr/share/misc/config.sub \ debian/build-src cd debian/build-src && ./autogen.sh [... snipped ...] ELC /<>/emacs-26.1+1/debian/build-src/test/src/process-tests.elc GEN src/process-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/regex-tests.elc GEN src/regex-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/syntax-tests.elc GEN src/syntax-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/textprop-tests.elc GEN src/textprop-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/thread-tests.elc GEN src/thread-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/undo-tests.elc In toplevel form: ../../build-src/test/src/undo-tests.el:262:6:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. ../../build-src/test/src/undo-tests.el:317:6:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. ../../build-src/test/src/undo-tests.el:353:47:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. ../../build-src/test/src/undo-tests.el:370:13:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. ../../build-src/test/src/undo-tests.el:394:19:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. ../../build-src/test/src/undo-tests.el:433:11:Warning: `delete-forward-char' is for interactive use only; use `delete-char' instead. GEN src/undo-tests.log ELC /<>/emacs-26.1+1/debian/build-src/test/src/xml-tests.elc GEN src/xml-tests.log make[5]: Leaving directory '/<>/emacs-26.1+1/debian/build-lucid/test' make[4]: [Makefile:263: check-doit] Error 2 (ignored) SUMMARY OF TEST RESULTS --- Files examined: 185 Ran 2563 tests, 2513 results as expected, 1 unexpected, 49 skipped 1 files contained unexpected results: lisp/eshell/em-ls-tests.log make[4]: *** [Makefile:264: check-doit] Error 1 make[4]: Leaving directory '/<>/emacs-26.1+1/debian/build-lucid/test' make[3]: *** [Makefile:239: check] Error 2 make[3]: Leaving directory '/<>/emacs-26.1+1/debian/build-lucid/test' make[2]: *** [Makefile:946: check] Error 2 make[2]: Leaving directory '/<>/emacs-26.1+1/debian/build-lucid' make[1]: *** [debian/rules:340: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>/emacs-26.1+1' make: *** [debian/rules:204: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/emacs.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#915025: marked as done (libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2)
Your message dated Mon, 07 Jan 2019 22:21:12 + with message-id and subject line Bug#915025: fixed in openmpi 3.1.3-8 has caused the Debian Bug report #915025, regarding libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi-dev Version: 3.1.3-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log (scroll to the bottom...): [...] Selecting previously unselected package libopenmpi3:amd64. Preparing to unpack .../45-libopenmpi3_3.1.3-2_amd64.deb ... Unpacking libopenmpi3:amd64 (3.1.3-2) ... Preparing to unpack .../46-libopenmpi-dev_3.1.3-2_amd64.deb ... dpkg: error processing archive /tmp/apt-dpkg-install-zyVlIE/46-libopenmpi-dev_3.1.3-2_amd64.deb (--unpack): new libopenmpi-dev package pre-installation script subprocess returned error exit status 2 update-alternatives: using /usr/lib/x86_64-linux-gnu/openmpi/include to provide /usr/include/mpi (mpi) in auto mode Preparing to unpack .../47-openmpi-common_3.1.3-2_all.deb ... Unpacking openmpi-common (3.1.3-2) over (2.0.2-2) ... Selecting previously unselected package openmpi-bin. dpkg: considering deconfiguration of libopenmpi-dev, which would be broken by installation of openmpi-bin ... dpkg: yes, will deconfigure libopenmpi-dev (broken by openmpi-bin) Preparing to unpack .../48-openmpi-bin_3.1.3-2_amd64.deb ... De-configuring libopenmpi-dev (2.0.2-2) ... Unpacking openmpi-bin (3.1.3-2) ... Replacing files in old package libopenmpi-dev (2.0.2-2) ... Preparing to unpack .../49-multiarch-support_2.27-8_amd64.deb ... Unpacking multiarch-support (2.27-8) over (2.24-11+deb9u3) ... Errors were encountered while processing: /tmp/apt-dpkg-install-zyVlIE/46-libopenmpi-dev_3.1.3-2_amd64.deb cheers, Andreas libopenmpi-dev_3.1.3-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 3.1.3-8 We believe that the bug you reported is fixed in the latest version of openmpi, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2019 21:19:05 + Source: openmpi Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc Architecture: source amd64 all Version: 3.1.3-8 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libopenmpi-dev - high performance message passing library -- header files libopenmpi3 - high performance message passing library -- shared library openmpi-bin - high performance message passing library -- binaries openmpi-common - high performance message passing library -- common files openmpi-doc - high performance message passing library -- man pages Closes: 915025 918000 Changes: openmpi (3.1.3-8) unstable; urgency=medium . * dh-fortran-mod >= 0.11 to properly remove files on purge. Closes: #918000, #915025. * Use internal pmix until pmix pkg works. Checksums-Sha1: 233bd359e3d870bb51e8d60262357926b7638fe6 2640 openmpi_3.1.3-8.dsc 7fd6b31e5dbc9351431ea5aae0d590898d602986 63588 openmpi_3.1.3-8.debian.tar.xz 8d8633fc0593879c73945bda0b25fb376c0127f4 973844 libopenmpi-dev_3.1.3-8_amd64.deb 5e704a5cec729e106e9f75aab9068dc39b32810e 33416388 libopenmpi3-dbgsym_3.1.3-8_amd64.deb cdf46aa5dacbe41b4d9166bf18abc3eca0cb160b 2173940 libopenmpi3_3.1.3-8_amd64.deb cf9bde65dc397d23b75d29ce607ad772e7bccde3 226476 openmpi-bin-dbgsym_3.1.3-8_amd64.deb dead7e5e1aa95e71a35703cff0203ba0ca97a849 200160 openmpi-bin_3.1.3-8_amd64.deb
Bug#918000: marked as done (openmpi postinst failure due to missing space in script)
Your message dated Mon, 07 Jan 2019 22:21:12 + with message-id and subject line Bug#918000: fixed in openmpi 3.1.3-8 has caused the Debian Bug report #918000, regarding openmpi postinst failure due to missing space in script 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.) -- 918000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi3 Version: 3.1.3-7 Severity: serious Dear maintainer, You missed a space in the script, which resulted in The following packages will be upgraded: libopenmpi3 openmpi-common 2 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 210 not fully installed or removed. Need to get 0 B/2338 kB of archives. After this operation, 16.4 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 168982 files and directories currently installed.) Preparing to unpack .../libopenmpi3_3.1.3-7_amd64.deb ... Unpacking libopenmpi3:amd64 (3.1.3-7) over (3.1.3-5) ... rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file or directory rm: cannot remove 'End': No such file or directory rm: cannot remove 'automatically': No such file or directory rm: cannot remove 'added': No such file or directory rm: cannot remove 'section': No such file or directory dpkg: warning: old libopenmpi3:amd64 package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/libopenmpi3_3.1.3-7_amd64.deb (--unpack): there is no script in the new version of the package - giving up Preparing to unpack .../openmpi-common_3.1.3-7_all.deb ... Unpacking openmpi-common (3.1.3-7) over (3.1.3-5) ... rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file or directory rm: cannot remove 'End': No such file or directory rm: cannot remove 'automatically': No such file or directory rm: cannot remove 'added': No such file or directory rm: cannot remove 'section': No such file or directory dpkg: warning: old openmpi-common package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/openmpi-common_3.1.3-7_all.deb (--unpack): cat /var/lib/dpkg/info/libopenmpi3:amd64.postrm | tail -n1 [ -d /usr/lib/$multiarch/fortran/$base ] && rm /usr/lib/$multiarch/fortran/$cmplr# End automatically added section ^missing space here --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 3.1.3-8 We believe that the bug you reported is fixed in the latest version of openmpi, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2019 21:19:05 + Source: openmpi Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc Architecture: source amd64 all Version: 3.1.3-8 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libopenmpi-dev - high performance message passing library -- header files libopenmpi3 - high performance message passing library -- shared library openmpi-bin - high performance message passing library -- binaries openmpi-common - high performance message passing library -- common files openmpi-doc - high performance message passing library -- man pages Closes: 915025 918000 Changes: openmpi (3.1.3-8) unstable; urgency=medium . * dh-fortran-mod >= 0.11 to properly remove files on purge. Closes: #918000, #915025. * Use internal pmix until pmix pkg works. Checksums-Sha1: 233bd359e3d870bb51e8d60262357926b7638fe6 2640 openmpi_3.1.3-8.dsc 7fd6b31e5dbc9351431ea5aae0d590898d602986 63588 openmpi_3.1.3-8.debian.tar.xz 8d8633fc0593879c73945bda0b25fb376c0127f4 973844
Bug#918508: Should golang-1.10 be shpped in buster?
Am 06.01.2019 um 21:11 schrieb Adrian Bunk: > Source: golang-1.10 > Severity: serious > > With golang-1.11 as default now, should golang-1.10 > be shipped in buster? Hi Adrian, probably not, but I'd like to keep it in buster for a little longer, just to make sure that golang-1.11 is a sane default. If everything breaks apart, we could still use golang-1.10 ... :-) I'll make sure to remove it from unstable (and testing) before we're deep into the freeze. Regards, Tobias signature.asc Description: OpenPGP digital signature
Processed: Bug #918583 in glibc marked as pending
Processing control commands: > tag -1 pending Bug #918583 [libc6] libc6: version in nocache Breaks is incorrect Added tag(s) pending. -- 918583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918583: Bug #918583 in glibc marked as pending
Control: tag -1 pending Hello, Bug #918583 in glibc 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/glibc-team/glibc/commit/fd8b13cb1bc71e29115e757646c8499f12cae74c debian/control.in/libc: fix nocache Breaks, set it to (<< 1.1-1~). Closes: #918583. (this message was generated automatically) -- Greetings https://bugs.debian.org/918583
Bug#918642: imagemagick: identify 6.9.10-23 doesn't convert units (pixels per cm/in)
Package: imagemagick Version: 8:6.9.10.23+dfsg-1 Severity: serious Tags: upstream Dear Maintainer, After the upgrade from 6.9.10.14 to 6.9.10.23, I noticed that the autopkgtests for the package ruby-mini-magick is failing due to one test about checking units to show the size of the image in cm and inches. I could isolate the problem by running the `identify` command on a test image (rgb.png in the spec/fixtures directory of the ruby-mini-magick source package). Running: identify -verbose -units PixelsPerInch rgb.png > output_in.txt identify -verbose -units PixelsPerCentimeter rgb.png > output_cm.txt diff -u output_in.txt output_cm.txt gives me the following with 8:6.9.10-14 from testing: --- /tmp/output_cm.txt 2019-01-07 22:32:49.257702663 +0100 +++ /tmp/output_in.txt 2019-01-07 22:32:40.457055525 +0100 @@ -3,9 +3,9 @@ Mime type: image/png Class: PseudoClass Geometry: 16x12+0+0 - Resolution: 118.11x118.11 - Print size: 0.135467x0.1016 - Units: PixelsPerCentimeter + Resolution: 300x300 + Print size: 0.053x0.04 + Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined @@ -118,12 +118,11 @@ signature: 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd Artifacts: filename: rgb.png -units: PixelsPerCentimeter +units: PixelsPerInch verbose: true Tainted: False Filesize: 359B Number pixels: 192 - Pixels per second: 19200B - User time: 0.010u - Elapsed time: 0:01.010 + User time: 0.000u + Elapsed time: 0:01.000 Version: ImageMagick 6.9.10-14 Q16 x86_64 20181023 https://imagemagick.org whereas it gives the following with 8:6.9.10-23 (with a suffix -23 to the text files). --- /tmp/output_cm-23.txt 2019-01-07 22:34:38.136761722 +0100 +++ /tmp/output_in-23.txt 2019-01-07 22:34:45.201163917 +0100 @@ -5,7 +5,7 @@ Geometry: 16x12+0+0 Resolution: 118.11x118.11 Print size: 0.135467x0.1016 - Units: PixelsPerCentimeter + Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined @@ -118,7 +118,7 @@ signature: 0d23f0078b8f89ca473e67bb38773cb94fd8ec5591e4207e83ff95cb27a6a0dd Artifacts: filename: rgb.png -units: PixelsPerCentimeter +units: PixelsPerInch verbose: true Tainted: False Filesize: 359B Maybe it was induced by this change? https://github.com/ImageMagick/ImageMagick6/commit/8c7648a1adf7bba35594074f191affd3ff3263bb Attaching the reference image and the full output files. I am setting severity serious, as it breaks the testsuite of ruby-mini-magick and provides wrong data when identifying images. Thank you in advance Cédric -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org compare: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org convert: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org composite: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org conjure: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org display: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org identify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org import: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org mogrify: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org montage: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org stream: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick depends on: ii imagemagick-6.q16 8:6.9.10.23+dfsg-1 imagemagick recommends no packages. imagemagick suggests no packages. -- no debconf information Image: rgb.png Format: PNG (Portable Network Graphics) Mime type: image/png Class: PseudoClass Geometry: 16x12+0+0 Resolution: 118.11x118.11 Print size: 0.135467x0.1016 Units: PixelsPerCentimeter Colorspace: sRGB Type: Palette Base type: Undefined Endianess: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 192 Red: min: 0 (0) max: 255 (1) mean: 138.167 (0.54183) standard deviation: 121.923 (0.47813) kurtosis: -1.89124 skewness: -0.166463 entropy: 0.835989 Green: min: 0 (0) max: 255 (1) mean: 127.667 (0.500654) standard deviation: 104.376 (0.409317) kurtosis: -1.51558 skewness: -0.0047654 entropy: 1
Bug#917681: ibus-table-others: FTBFS: FileExistsError: [Errno 17] File exists: '/<>/debian/fakehome/.local/share/ibus-table'
Control: tag -1 + moreinfo unreproducible help Control: severity -1 important X-Debbugs-CC: lu...@debian.org Hi Lucas, I could not reproduce this problem locally either using debuild or using sbuild. Could you please provide with more information on it? Besides, I just prepared 1.3.9-4 upload which disables parallel build. Please let me know if that fixes the problem. -- Thanks, Boyuan Yang On Sat, 29 Dec 2018 22:43:21 +0100 Lucas Nussbaum wrote: > Source: ibus-table-others > Version: 1.3.9-3 > Severity: serious > Justification: FTBFS on amd64 > Tags: buster sid > Usertags: ftbfs-20181229 ftbfs-buster > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[2]: Entering directory '/<>/tables' > > /usr/bin/ibus-table-createdb -n compose.db -s compose.txt > > /usr/bin/ibus-table-createdb -n ipa-x-sampa.db -s ipa-x-sampa.txt > > Traceback (most recent call last): > > File "/usr/share/ibus-table/engine/tabcreatedb.py", line 455, in > > main() > > File "/usr/share/ibus-table/engine/tabcreatedb.py", line 175, in main > > create_database=True) > > File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 262, in __init__ > > import ibus_table_location > > File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in > > __module_init = __ModuleInitializer() > > File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in __init__ > > _init() > > File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in _init > > os.makedirs(IBUS_TABLE_LOCATION['data_home']) > > File "/usr/lib/python3.7/os.py", line 221, in makedirs > > mkdir(name, mode) > > FileExistsError: [Errno 17] File exists: '/<>/debian/fakehome/.local/share/ibus-table' > > make[2]: *** [Makefile:519: ipa-x-sampa.db] Error 1 > > The full build log is available from: > http://aws-logs.debian.net/2018/12/29/ibus-table-others_1.3.9-3_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. > > signature.asc Description: This is a digitally signed message part
Processed: Re: ibus-table-others: FTBFS: FileExistsError: [Errno 17] File exists: '/<>/debian/fakehome/.local/share/ibus-table'
Processing control commands: > tag -1 + moreinfo unreproducible help Bug #917681 [src:ibus-table-others] ibus-table-others: FTBFS: FileExistsError: [Errno 17] File exists: '/<>/debian/fakehome/.local/share/ibus-table' Added tag(s) help, unreproducible, and moreinfo. > severity -1 important Bug #917681 [src:ibus-table-others] ibus-table-others: FTBFS: FileExistsError: [Errno 17] File exists: '/<>/debian/fakehome/.local/share/ibus-table' Severity set to 'important' from 'serious' -- 917681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sl-modem: ftbfs on i386: undefined reference to `minor'
Processing control commands: > tag -1 patch Bug #918443 [src:sl-modem] sl-modem: ftbfs on i386: undefined reference to `minor' Added tag(s) patch. -- 918443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918443: sl-modem: ftbfs on i386: undefined reference to `minor'
Control: tag -1 patch I just ran into this and am attaching a patch for it. Ben. -- Ben Hutchings Design a system any fool can use, and only a fool will want to use it. From: Ben Hutchings Date: Mon, 07 Jan 2019 21:21:23 + Subject: modem_main: Fix build with glibc 2.28 Starting with glibc 2.28, the major() and minor() macros are defined in which is not included by another header. does not exist in older glibc versions, so we shouldn't include it unconditionally. Add a check for availability of the header to the Makefile and define a macro to tell modem_main.c the result. --- --- a/modem/Makefile +++ b/modem/Makefile @@ -44,6 +44,10 @@ CFLAGS+= -DSUPPORT_ALSA=1 LDFLAGS+= -lasound endif +ifeq ($(shell echo '\#include ' | $(CC) $(CFLAGS) $(CPPFLAGS) $(EXTRA_CFLAGS) -E -x c -o /dev/null - 2>&1),) +CFLAGS+= -DHAVE_SYS_SYSMACROS_H +endif + slmodemd: $(CC) -o slmodemd modem_main.o $(all-objs) $(LDFLAGS) --- a/modem/modem_main.c +++ b/modem/modem_main.c @@ -55,6 +55,9 @@ #include #include #include +#ifdef HAVE_SYS_SYSMACROS_H +#include +#endif #include #include #include signature.asc Description: This is a digitally signed message part
Bug#915112: marked as done (pymol: FTBFS with glew 2.1)
Your message dated Mon, 7 Jan 2019 21:41:53 + with message-id <9ebd31a4-3d65-3b47-cca0-261c15a5e...@debian.org> and subject line fixed in 2.1.0-3 has caused the Debian Bug report #915112, regarding pymol: FTBFS with glew 2.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.) -- 915112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glew Version: 2.1.0-2 Severity: serious Control: affects -1 + src:pymol Hi, I just noticed that pymol stated to FTBFS, this seems to be caused by glew (which was updated recently, while libglvnd hasn't seen changes for some time): In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, const GLfloat *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, GLfloat* params); ^~~~ In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12068:103: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, const GLint*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, const GLint *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18736:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, GLint*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, GLint* params); ^~~~ and so on... Full log attached. This happens with both pymol in sid and experimental. Andreas pymol_2.2.0+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- fixed 2.1.0-3 thanks -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.--- End Message ---
Processed: pysph: diff for NMU version 0~20180411.git1ae58e1-2.1
Processing control commands: > tags 915514 + pending Bug #915514 [pysph] pysph: Missing build-dependency on python-pytest-runner, Debian builds pulling source from network? Added tag(s) pending. -- 915514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: This is also being fixed through #911995
Processing commands for cont...@bugs.debian.org:
> severity 916572 normal
Bug #916572 {Done: Andreas Tille } [mauve-aligner]
mauve-aligner: (build-)depends on obsolete icedtea-netx-common
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915514: pysph: diff for NMU version 0~20180411.git1ae58e1-2.1
Control: tags 915514 + pending Dear maintainer, I've prepared an NMU for pysph (versioned as 0~20180411.git1ae58e1-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru pysph-0~20180411.git1ae58e1/debian/changelog pysph-0~20180411.git1ae58e1/debian/changelog --- pysph-0~20180411.git1ae58e1/debian/changelog 2018-05-20 18:43:24.0 +0300 +++ pysph-0~20180411.git1ae58e1/debian/changelog 2019-01-07 23:30:08.0 +0200 @@ -1,3 +1,13 @@ +pysph (0~20180411.git1ae58e1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add the missing build dependencies on python-pytest +and python-pytest-runner, thanks to Steve Langasek. +(Closes: #915514) + * Update Homepage: to the current upstream location. + + -- Adrian Bunk Mon, 07 Jan 2019 23:30:08 +0200 + pysph (0~20180411.git1ae58e1-2) unstable; urgency=medium * Team upload. diff -Nru pysph-0~20180411.git1ae58e1/debian/control pysph-0~20180411.git1ae58e1/debian/control --- pysph-0~20180411.git1ae58e1/debian/control 2018-05-20 18:43:05.0 +0300 +++ pysph-0~20180411.git1ae58e1/debian/control 2019-01-07 23:30:08.0 +0200 @@ -11,6 +11,8 @@ python-mock, python-nose, python-numpy, + python-pytest, + python-pytest-runner, python-sphinx, python-sphinx-rtd-theme, python-traits, @@ -18,7 +20,7 @@ Standards-Version: 4.1.4 Vcs-Browser: https://salsa.debian.org/science-team/pysph Vcs-Git: https://salsa.debian.org/science-team/pysph.git -Homepage: http://pysph.googlecode.com +Homepage: https://github.com/pypr/pysph Package: python-pysph Architecture: any
Bug#918517: marked as done (grib-api: fails to remove packages)
Your message dated Mon, 07 Jan 2019 21:34:48 + with message-id and subject line Bug#918517: fixed in grib-api 1.28.0-2 has caused the Debian Bug report #918517, regarding grib-api: fails to remove packages 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.) -- 918517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grib-api Version: 1.28.0-1 Severity: grave Hi, Your packages fail to remove: (Reading database ... 4458 files and directories currently installed.) Purging configuration files for python-gribapi (1.28.0-1) ... rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15': No such file or directory dpkg: error processing package python-gribapi (--purge): installed python-gribapi package post-removal script subprocess returned error exit status 1 This also happens with other packages from src:grib-api, see https://piuparts.debian.org/sid/source/g/grib-api.html Emilio --- End Message --- --- Begin Message --- Source: grib-api Source-Version: 1.28.0-2 We believe that the bug you reported is fixed in the latest version of grib-api, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated grib-api package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2019 19:46:25 + Source: grib-api Binary: libgrib-api0 libgrib-api-dev libgrib-api-tools libgrib-api-doc python-gribapi python3-gribapi Architecture: source amd64 all Version: 1.28.0-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libgrib-api-dev - GRIB decoding/encoding software library (development) libgrib-api-doc - GRIB decoding/encoding software (documentation) libgrib-api-tools - GRIB decoding/encoding software (utilities) libgrib-api0 - GRIB decoding/encoding software library python-gribapi - Python module for the ECMWF GRIB API library python3-gribapi - Python3 module for the ECMWF GRIB API library Closes: 918517 Changes: grib-api (1.28.0-2) unstable; urgency=medium . * Standards-Version: 4.3.0 * Build with dh-fortran-mod (>= 0.11) to clean up on pkg removal. Closes: #918517 Checksums-Sha1: 4731ca5f36e45a6279fac3e0785beb74552b8baa 2914 grib-api_1.28.0-2.dsc f973d209c36481ad524a8a704e38b60c0e0b 37484 grib-api_1.28.0-2.debian.tar.xz 2305af8fec3941d99940e39cf85cfb459233cea4 11364 grib-api_1.28.0-2_amd64.buildinfo ff3beaa0d33df45292d0fb4232eb0fa58b497939 537924 libgrib-api-dev_1.28.0-2_amd64.deb f99275f8161fb67c1fc4edccfc4753e0ca0a50ac 74928 libgrib-api-doc_1.28.0-2_all.deb e9a7632d15b6c8186a864ca8e2634cd411991795 935852 libgrib-api-tools-dbgsym_1.28.0-2_amd64.deb 1b21765fca9ff3e9b05c87310ff2ed57749cbfb6 177652 libgrib-api-tools_1.28.0-2_amd64.deb 55a684abb08b3e17050815c02c9cacfdcee68cb9 1340672 libgrib-api0-dbgsym_1.28.0-2_amd64.deb a52176d4da11fc4b96e16108098739ccd7e3d472 325688 libgrib-api0_1.28.0-2_amd64.deb f833c06fb914393dcd004baa841656fa01d5324a 224668 python-gribapi-dbgsym_1.28.0-2_amd64.deb f4b54155c68de8852ed6072d7ca4d6ad2e226a2e 67052 python-gribapi_1.28.0-2_amd64.deb f46db637ab514ff078f3c0edcada898749dc6029 225256 python3-gribapi-dbgsym_1.28.0-2_amd64.deb 98fa08bf3a58a08dff09d06df4807a66ead80d12 67636 python3-gribapi_1.28.0-2_amd64.deb Checksums-Sha256: 4001c57497e8e90332df4a6634faff325e08df141459fa75b72429f3f5ff49ff 2914 grib-api_1.28.0-2.dsc 03a37e50f45ff756d8fe2b3bf216b69b210ee4f53a65de7b434eb079f153c17a 37484 grib-api_1.28.0-2.debian.tar.xz ea4647b0d1c45f1d19bf7ba83ee065a500ec9a7665c909f317644a1a3f64a928 11364 grib-api_1.28.0-2_amd64.buildinfo b12d7cfe84ab7980ba68cb83a45c063028f79ac99d7d905a6f498975978b40a1 537924 libgrib-api-dev_1.28.0-2_amd64.deb 3f7d92eced0aff0d808c08d848770e8692c4f854c0534974cc66c622f29fa297 74928 libgrib-api-doc_1.28.0-2_all.deb ba9e75fc01bf14609d1fc595f6ff2a71d312c2f12fdfc073de563730a2d0df51 935852 libgrib-api-tools-dbgsym_1.28.0-2_amd64.deb
Processed: found 918641 in 1.9-2
Processing commands for cont...@bugs.debian.org: > found 918641 1.9-2 Bug #918641 [python3-fava] pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava Marked as found in versions fava/1.9-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 918641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 915768
Processing commands for cont...@bugs.debian.org: > tags 915768 + patch Bug #915768 [src:mangler] mangler: B-D libg15-dev libg15daemon-client-dev are no longer available Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 915768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 916106 with 918497
Processing commands for cont...@bugs.debian.org: > block 916106 with 918497 Bug #916106 [arptables] arptables provides the same executables as iptables packages without using alternatives 916106 was blocked by: 913883 916106 was not blocking any bugs. Added blocking bug(s) of 916106: 918497 > thanks Stopping processing here. Please contact me if you need assistance. -- 916106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 916416 is forwarded to https://github.com/hzbd/kazam/pull/21
Processing commands for cont...@bugs.debian.org: > forwarded 916416 https://github.com/hzbd/kazam/pull/21 Bug #916416 [kazam] kazam unable to start: ValueError: Invalid section name: 'DEFAULT' Set Bug forwarded-to-address to 'https://github.com/hzbd/kazam/pull/21'. > thanks Stopping processing here. Please contact me if you need assistance. -- 916416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918641: pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava
Package: python3-fava Version: 1.9-3 Severity: serious As per subject, running fava fails with the following traceback: Traceback (most recent call last): File "/usr/bin/fava", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3126, in @_call_aside File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3110, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3139, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 581, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 898, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 784, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'cheroot' distribution was not found and is required by fava this should ideally be fixed by having cheroot ship an egg-info dir, but it's being filed against fava for now to avoid testing migration. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-fava depends on: ii python3 3.7.1-3 ii python3-babel2.6.0+dfsg.1-1 ii python3-beancount2.1.3+hg20181225-3 ii python3-click6.7+git20180829-1 ii python3-flask1.0.2-3 ii python3-flask-babel 0.11.2-2 ii python3-jinja2 2.10-1 ii python3-markdown22.3.7-1 ii python3-ply 3.11-3 ii python3-simplejson 3.15.0-1+b1 python3-fava recommends no packages. python3-fava suggests no packages. -- no debconf information
Processed: pelican BTS info
Processing control commands: > tag -1 confirmed Bug #918447 [src:pelican] pelican: fails to build: wrong dependency? Added tag(s) confirmed. -- 918447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918447: pelican BTS info
Control: tag -1 confirmed On Sun, Jan 06, 2019 at 12:46:59AM -0500, Jeremy Bicha wrote: > Source: pelican > Version: 3.7.1+dfsg-2 > > pelican fails to build. I notice that a dependency on python3-feedparser > was added, but pelican appears to be a Python2 package. Acknowledge. The upload for version: 3.7.1+dfsg-2 was only for fixing VCS fields ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917468 ) However, the latest VCS changes are temporary at https://salsa.debian.org/stappers/pelican The plan for fixing this #918447 is with #875255, provide version of packege under Python 3, and #913875, new upstream version. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875255 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913875 Groeten Geert Stappers -- Leven en laten leven
Bug#917534: marked as done (ifupdown2 fails to start network configuration)
Your message dated Mon, 07 Jan 2019 21:19:20 + with message-id and subject line Bug#917534: fixed in ifupdown2 1.2.3-1 has caused the Debian Bug report #917534, regarding ifupdown2 fails to start network configuration 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.) -- 917534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown2 Version: 1.2.2-1 Severity: serious Justification: renders system unusable Hello, with this package and this version, my system comes up without any networking configured, giving an error message at startup Fri Dec 28 10:38:52 2018: networking: Configuring network interfaces Fri Dec 28 10:38:52 2018: Traceback (most recent call last): Fri Dec 28 10:38:52 2018: File "/sbin/ifup", line 26, in Fri Dec 28 10:38:52 2018: from ifupdown.log import log Fri Dec 28 10:38:52 2018: File "/usr/share/ifupdown2/ifupdown/log.py", line 163, in Fri Dec 28 10:38:52 2018: log = Log() Fri Dec 28 10:38:52 2018: File "/usr/share/ifupdown2/ifupdown/log.py", line 65, in __init__ Fri Dec 28 10:38:52 2018: self.syslog_handler = logging.handlers.SysLogHandler(address=address, facility=facility) Fri Dec 28 10:38:52 2018: File "/usr/lib/python2.7/logging/handlers.py", line 761, in __init__ Fri Dec 28 10:38:52 2018: self._connect_unixsocket(address) Fri Dec 28 10:38:52 2018: File "/usr/lib/python2.7/logging/handlers.py", line 804, in _connect_unixsocket Fri Dec 28 10:38:52 2018: self.socket.connect(address) Fri Dec 28 10:38:52 2018: File "/usr/lib/python2.7/socket.py", line 228, in meth Fri Dec 28 10:38:52 2018: return getattr(self._sock,name)(*args) Fri Dec 28 10:38:52 2018: socket.error: [Errno 2] No such file or directory My system is running on sysvinit. An acceptable proposal would be to log to stderr until /dev/log has been setup The init script used looks as follows: ## BEGIN INIT INFO # Provides: networking ifupdown # Required-Start:mountkernfs $local_fs urandom $syslog # Required-Stop: $local_fs # Default-Start: S # Default-Stop: 0 6 # Short-Description: Raise network interfaces. # Description: Prepare /run/network directory, ifstate file and raise network interfaces, or take them down. ### END INIT INFO exec /usr/share/ifupdown2/sbin/start-networking "$@" Bye, Joerg signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ifupdown2 Source-Version: 1.2.3-1 We believe that the bug you reported is fixed in the latest version of ifupdown2, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Fortin (supplier of updated ifupdown2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 30 Dec 2018 23:42:42 +0700 Source: ifupdown2 Binary: ifupdown2 Architecture: source all Version: 1.2.3-1 Distribution: unstable Urgency: medium Maintainer: Julien Fortin Changed-By: Julien Fortin Description: ifupdown2 - Network Interface Management tool similar to ifupdown Closes: 917534 Changes: ifupdown2 (1.2.3-1) unstable; urgency=medium . * Fix: log: use stderr if syslog initialization fails (closes: #917534) Checksums-Sha1: e42d34f00d1d7a80dcd3764275e9f8bd480e83db 1803 ifupdown2_1.2.3-1.dsc 5933f3a6573b7344c4af93616d123e3ba3f8d693 281668 ifupdown2_1.2.3.orig.tar.xz 57b4af15ef6016a5132eaf47391f7f0d40611b03 6508 ifupdown2_1.2.3-1.debian.tar.xz 5c82d08ae4ff5595fdc198b12e49afbe0cf2dc4b 194808 ifupdown2_1.2.3-1_all.deb 72fdb1a5e9712b8e85a54890f2b00d432beff1f1 6518 ifupdown2_1.2.3-1_amd64.buildinfo Checksums-Sha256: 28eec11af0d1a6a11e2b5af95087e78cb76b8b719460733c5d4aee0d28e46369 1803 ifupdown2_1.2.3-1.dsc 92256669cf287b65f2423780c46e275311efcc94264bcd25a6b9e6e730c2cc80 281668 ifupdown2_1.2.3.orig.tar.xz 30b01e947ec4f30603e2462935d32778d8cc07ed23b3f187f7d9426c549bdbdb 6508 ifupdown2_1.2.3-1.debian.tar.xz ca6b52ab3213715564b4b4660a01cb46318c6106c4c518ab02c9fa27056dde53 194808 ifupdown2_1.2.3-1_all.deb
Bug#843926: marked as done (jemalloc uses a hard coded page size detected during build)
Your message dated Mon, 07 Jan 2019 21:04:26 + with message-id and subject line Bug#843926: fixed in jemalloc 5.1.0-2 has caused the Debian Bug report #843926, regarding jemalloc uses a hard coded page size detected during build 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.) -- 843926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.0 Version: 10.0.26-0+deb8u1 Severity: serious Justification: FTBFS Hi The recent mariadb-10.0 upload of 10.0.26-0+deb8u1 for jessie-security FTBFS on powerpc. I have attached the build log from buildd and the hanging build was reproducible on porterbox partch.debian.org for powerpc. Regards, Salvatore mariadb-10.0_10.0.26-0+deb8u1_powerpc-20160726-0537.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: jemalloc Source-Version: 5.1.0-2 We believe that the bug you reported is fixed in the latest version of jemalloc, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Faidon Liambotis (supplier of updated jemalloc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 20:56:52 +0200 Source: jemalloc Binary: libjemalloc-dev libjemalloc2 Architecture: source Version: 5.1.0-2 Distribution: unstable Urgency: medium Maintainer: Stig Sandbeck Mathisen Changed-By: Faidon Liambotis Description: libjemalloc-dev - development files and documentation for jemalloc libjemalloc2 - general-purpose scalable concurrent malloc(3) implementation Closes: 843926 Changes: jemalloc (5.1.0-2) unstable; urgency=medium . * Upload to unstable. * Bump debhelper compatibility level to 11. * Bump Standards-Version to 4.3.0, no changes needed. * Update debian/copyright: - Include years 2018 and 2019. - Use https to point to debian.org. * Add Build-Depends-Package to libjemalloc2.symbols. * autopkgtest: remove embedded code copy of sharness. (Closes: #843926) Checksums-Sha1: 7b073788562613f17248ddce0d605ccf03d8259d 2031 jemalloc_5.1.0-2.dsc 96be12f24b12bc28d123b8ef105902b07f09d45a 8284 jemalloc_5.1.0-2.debian.tar.xz da61832fafb2ab9d20069ed9e346069f7370fdff 5280 jemalloc_5.1.0-2_source.buildinfo Checksums-Sha256: 46eb3155b57c07bf66cef4c439377e4e518d21ce8e8ff52abeac80fdeff9acb1 2031 jemalloc_5.1.0-2.dsc bb774db819ada6d3bdf7759bc029f2e74317b7b93cea13ac0975e86d207d2dc0 8284 jemalloc_5.1.0-2.debian.tar.xz bb47531a405ea30bd1ccbd817bc3cec5cd921cef7648e4d4d2ed944ad8733287 5280 jemalloc_5.1.0-2_source.buildinfo Files: 565aed3f9af50ccb5b162d95cf4938b5 2031 libs optional jemalloc_5.1.0-2.dsc 7d98ced641a80a26fb107c22d0d0ff3b 8284 libs optional jemalloc_5.1.0-2.debian.tar.xz ef61a7adf9b364f67fdcb12ea9def468 5280 libs optional jemalloc_5.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAlwzuZwACgkQnQteWx7s jw6Mgg/9EodP9x9QU5wxPuMY7Mp6LQ9UA4J05RBdvRsaUtW+d+rcdLsOIll51GOJ uHanVxX8O+WxMHq/a3j2kBkRiTVHWIBFHVremGbh2tfmeg4SnTjgAOsOcFhzLGsX lXdFMduSPXZ7o3bOCXSM8HqqWiGWzPY02618FCDgKJUz41xB6Bu/rjWzdx+bqeGD OufShsTRcohUKNeiqnGwk2rily/rnoQ6BUAANzC4rvK5D1q/fpqJfPI5S/LiP3mo ggFYzStmTxquzNXvYj8Gm/sdyHiiIFsx5qHMtEWsy/oZRCyFP+eSag6o6vjdc5jB syI/YPAFMD1NZ8vuvrx6d33oz7+KF07m782vwPp0gW1lS+FN1ptnazsWA0ImUSDX QDAR+A6l0nqpVZY1a5TJ6NnV+y4HB5ec8jdzibzzeVRDOMNo2TTeNbHVvBFIVwiD 1V/8lSsHJ7Pv8xnH47F4NfwwPEwpKCcBTaOXzVJc7tjK9jLyhA88HcBhC662AQY8 V0wmBqji2UG/vdhJdC7t1Ss+EldBlRH4dBcA+V+8fqiF+Uw8VL9RNy3NDAOHF7BI /xmrwOraL/vfcEoa66W4mPPjyOP6nUCppKyn9lgIXSWf1wsAUvf1A1Q1Wa6KVvvj 8qYfdT89aKvJVW0C8l0cjSEvaLWlWfmvVqnpaIWeOoE3diYM7QQ= =f5Bt -END PGP SIGNATURE End Message ---
Bug#908492: marked as done (nat-rtsp-dkms: fails to build on new 4.18 kernels)
Your message dated Mon, 07 Jan 2019 21:04:56 + with message-id and subject line Bug#908492: fixed in nat-rtsp 0.7+4.18-0.1 has caused the Debian Bug report #908492, regarding nat-rtsp-dkms: fails to build on new 4.18 kernels 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.) -- 908492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nat-rtsp-dkms Version: 0.7+1.g2ea3cb6-1 Severity: important Current kernel version has been bumped up in sid from 4.17 to 4.18. After this upgrade unfortunately the kernel module fails to build, due to changes in the definition of kernel structures that the module uses. Please update the nat-rtsp source code to follow these changes. Thanks, best regards Giacomo Mulas -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nat-rtsp-dkms depends on: ii dkms 2.6.1-1 nat-rtsp-dkms recommends no packages. nat-rtsp-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nat-rtsp Source-Version: 0.7+4.18-0.1 We believe that the bug you reported is fixed in the latest version of nat-rtsp, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated nat-rtsp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 20:38:10 + Source: nat-rtsp Binary: nat-rtsp-dkms Architecture: source Version: 0.7+4.18-0.1 Distribution: unstable Urgency: medium Maintainer: Julien Muchembled Changed-By: Ben Hutchings Description: nat-rtsp-dkms - Connection tracking and NAT support for RTSP Closes: 908492 Changes: nat-rtsp (0.7+4.18-0.1) unstable; urgency=medium . * Non-maintainer upload * New upstream release: - Add support to linux 4.18 (Closes: #908492) * Update to policy version 4.3.0: - debian/copyright: Use https: URL for copyright format - debian/control: Change priority to optional - debian/control: Set Rules-Requires-Root: no * debian/source/options: Delete as redundant * Use debhelper compatibility level 12 Checksums-Sha1: c9ea3522c01a364a430c1e6c80c1a585173bbe04 1758 nat-rtsp_0.7+4.18-0.1.dsc 912f639b5450cec72eabca1aac0c4eb36def5162 11600 nat-rtsp_0.7+4.18.orig.tar.xz 08282e4b7aaff4044cbb4476bc33bbbfb4048dcc 3008 nat-rtsp_0.7+4.18-0.1.debian.tar.xz d93a7ff09c6d78344126bbc86b094383350c7afa 5175 nat-rtsp_0.7+4.18-0.1_source.buildinfo Checksums-Sha256: f284ae6305b87308099dc3a32b2c5c489d834e972dfaa861548fd4aeb57b7926 1758 nat-rtsp_0.7+4.18-0.1.dsc aad6ac785f8d2ebd48e7c83044efbf7ab0e22ce2e77bcc6d10c86f54a6ac 11600 nat-rtsp_0.7+4.18.orig.tar.xz 2f1cc12447ff1b7bcaf746115f7b332c6ac32c9be1976f5b04183b6709ec2195 3008 nat-rtsp_0.7+4.18-0.1.debian.tar.xz 3d61c0ad2ba518c46a9495210b4063d29b249ed58454e7e67ace5743b525005f 5175 nat-rtsp_0.7+4.18-0.1_source.buildinfo Files: 9f00c163a86638aceca6aa13c9a2dbcb 1758 kernel optional nat-rtsp_0.7+4.18-0.1.dsc 0e153dedcd841907586d51109919ed26 11600 kernel optional nat-rtsp_0.7+4.18.orig.tar.xz 5636305db0b5cabe16f346308fb36e4a 3008 kernel optional nat-rtsp_0.7+4.18-0.1.debian.tar.xz c7aa37dc15862eeb17e21b4a27189514 5175 kernel optional nat-rtsp_0.7+4.18-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlwzuSoACgkQ57/I7JWG EQk+Ug/9EGRBSED7FuIkpfshw47BshCNMRihjaOnzBI0kuxjXT6CHxPhyEvF8nux DveEWdgZOHMxClIt+Vn9EYlfkB4pW5EvCUMusYryJc9mpaAQGgtPVU/a7nu2WZ1v wRF2TTwMjy5KBMY5G2EbJGQzWgJJHxErgJTbNH/mFwrGO/dz30regwUgw+T3nHTk
Processed: severity of 918623 is serious
Processing commands for cont...@bugs.debian.org: > severity 918623 serious Bug #918623 [dizzy] dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 918623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918559: marked as done (octave-geometry FTBFS: dh_dwz returned exit code 1)
Your message dated Mon, 07 Jan 2019 21:05:04 + with message-id and subject line Bug#918559: fixed in octave-geometry 3.0.0-9 has caused the Debian Bug report #918559, regarding octave-geometry FTBFS: dh_dwz returned exit code 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.) -- 918559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-geometry Version: 3.0.0-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=octave-geometry=sid ... dh_dwz -a -O--buildsystem=octave dh_dwz: dwz -q -- debian/octave-geometry/usr/lib/aarch64-linux-gnu/octave/packages/geometry-3.0.0/aarch64-unknown-linux-gnu-api-v52/clipper.mex returned exit code 1 make: *** [debian/rules:5: binary-arch] Error 1 --- End Message --- --- Begin Message --- Source: octave-geometry Source-Version: 3.0.0-9 We believe that the bug you reported is fixed in the latest version of octave-geometry, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissiere (supplier of updated octave-geometry package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2019 13:45:11 -0200 Source: octave-geometry Binary: octave-geometry Architecture: source Version: 3.0.0-9 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissiere Description: octave-geometry - geometric computing functions for Octave Closes: 918559 Changes: octave-geometry (3.0.0-9) unstable; urgency=medium . * d/p/do-not-strip-debugging-symbols.patch: New patch (Closes: #918559) * Migrate to Python 3 + d/control: Depend and build-depend on python3 and python3-lxml + d/p/use-python3.patch: New patch + d/rules: Adjust code for deletion of byte-compiled files * d/octave-geometry.lintian-overrides: Remove unused override Checksums-Sha1: 5fc596296c8543431ef3cf32fa762317861afc76 2071 octave-geometry_3.0.0-9.dsc 297284f25aaba58b71a45203fd2fe19d70a80540 5916 octave-geometry_3.0.0-9.debian.tar.xz 3a26ae4d3032bc7884450357cdf835f6313a8641 16311 octave-geometry_3.0.0-9_amd64.buildinfo Checksums-Sha256: f6c2d3f465fecf0f48f258c1d7981bf69965451e9ddf5baf7dc6bd00395d74e0 2071 octave-geometry_3.0.0-9.dsc 5577e307a0692dfb813b3d01558a59c761a3bad879524653c2ff8785d65ac4fc 5916 octave-geometry_3.0.0-9.debian.tar.xz 57616638037535e7e9914433b80b5f9713fd765157df5069b01426e079976c71 16311 octave-geometry_3.0.0-9_amd64.buildinfo Files: e41e747c74ddc3d5438fcb0d180be558 2071 math optional octave-geometry_3.0.0-9.dsc 63252b3bfcd92b4818e00251fc57ea73 5916 math optional octave-geometry_3.0.0-9.debian.tar.xz ee1cf03adeb80af85a0144569af4e8cc 16311 math optional octave-geometry_3.0.0-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlwzuP8ACgkQISSqGYN4 XJB2Vg//bg+0SG9PkXFRc5Ss60KcZNU9x5lyhNxru5YhwL8oKw46Z/Jbuadc5f2V rQcCUnZ1e7XBcwekQBN4L4MuvsVmIt55oRD/DJa8iJUYaQpFJbWJfy+zikrSnvol GthL+8lTjPpxSfy5w7MelTH1fWNrKCmpDvNHHC98hSVahTvDSf3F4cGQaJcEurNl 9vtwHll9kmhRVaj2wauZOpNxH3Mr668I05ai2cWEbeARr/Jvdt0Yq6PdtPAsWT39 ELBLwJaCR5n22rPNBlFJ46jHMC0U9SjiZ+GEKhuChciiyGFIbChgJdrN1Jdu/dGI aIb1Wpx5K4iFWNkLYF4YiLp4nVA6yNoBAAvIv2dGoEm7fxsbgZxBEQKxIWCDE9zD VrCbqCiYyay7WJ6yKw1wtqkL1u7w3aHh0WWpoJ2ynQIZydU2cDX0Viy3oaAYTp8l hNIlg5985VPQ13wf9eTe3JEg6lqmU9qt9Pid4g4tQNvtwGRdG38dOkRfuUMp2zF4 foji0nIwgrGFuj9kw2OdDTCJQ/Fqv/OAEh14lrdXOIfCAz1pAxXwnCqx7Sa/N1tN huaf1T3+LClJwFB6CvUHhiHlXKfMZWxqJonW3/vo4Pbv0hiNkuLogTy3ifyqQReF cPxjRzXc3TJWD4Eesa5iiD2Qr9j6F4URx2Y//51+8XwAfuGgpQo= =3vTJ -END PGP SIGNATURE End Message ---
Bug#897076: marked as done (libjemalloc1: Version 3.6.0-11(unstable) error : Error in munmap(): Invalid argument)
Your message dated Mon, 07 Jan 2019 21:04:26 + with message-id and subject line Bug#843926: fixed in jemalloc 5.1.0-2 has caused the Debian Bug report #843926, regarding libjemalloc1: Version 3.6.0-11(unstable) error : Error in munmap(): Invalid argument 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.) -- 843926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjemalloc1 Version: 3.6.0-11(unstable) Severity: important Dear Maintainer, When attempting to run a program which requires libjemalloc1 the error: ": Error in munmap(): Invalid argument" appears. This error is isolated to the Debian build 3.6.0-11(unastable). I downloaded and installed the Ubuntu version 3.6.0-9ubuntu1 and no longer receive the error, and Blender now runs. -- System Information: Debian Release: buster/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (500, 'unstable') Architecture: powerpc (ppc64) Kernel: Linux 4.17.0-rc2_A-EON_A1-X5000 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libjemalloc1 depends on: ii libc6 2.27-3 libjemalloc1 recommends no packages. libjemalloc1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: jemalloc Source-Version: 5.1.0-2 We believe that the bug you reported is fixed in the latest version of jemalloc, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Faidon Liambotis (supplier of updated jemalloc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 20:56:52 +0200 Source: jemalloc Binary: libjemalloc-dev libjemalloc2 Architecture: source Version: 5.1.0-2 Distribution: unstable Urgency: medium Maintainer: Stig Sandbeck Mathisen Changed-By: Faidon Liambotis Description: libjemalloc-dev - development files and documentation for jemalloc libjemalloc2 - general-purpose scalable concurrent malloc(3) implementation Closes: 843926 Changes: jemalloc (5.1.0-2) unstable; urgency=medium . * Upload to unstable. * Bump debhelper compatibility level to 11. * Bump Standards-Version to 4.3.0, no changes needed. * Update debian/copyright: - Include years 2018 and 2019. - Use https to point to debian.org. * Add Build-Depends-Package to libjemalloc2.symbols. * autopkgtest: remove embedded code copy of sharness. (Closes: #843926) Checksums-Sha1: 7b073788562613f17248ddce0d605ccf03d8259d 2031 jemalloc_5.1.0-2.dsc 96be12f24b12bc28d123b8ef105902b07f09d45a 8284 jemalloc_5.1.0-2.debian.tar.xz da61832fafb2ab9d20069ed9e346069f7370fdff 5280 jemalloc_5.1.0-2_source.buildinfo Checksums-Sha256: 46eb3155b57c07bf66cef4c439377e4e518d21ce8e8ff52abeac80fdeff9acb1 2031 jemalloc_5.1.0-2.dsc bb774db819ada6d3bdf7759bc029f2e74317b7b93cea13ac0975e86d207d2dc0 8284 jemalloc_5.1.0-2.debian.tar.xz bb47531a405ea30bd1ccbd817bc3cec5cd921cef7648e4d4d2ed944ad8733287 5280 jemalloc_5.1.0-2_source.buildinfo Files: 565aed3f9af50ccb5b162d95cf4938b5 2031 libs optional jemalloc_5.1.0-2.dsc 7d98ced641a80a26fb107c22d0d0ff3b 8284 libs optional jemalloc_5.1.0-2.debian.tar.xz ef61a7adf9b364f67fdcb12ea9def468 5280 libs optional jemalloc_5.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAlwzuZwACgkQnQteWx7s jw6Mgg/9EodP9x9QU5wxPuMY7Mp6LQ9UA4J05RBdvRsaUtW+d+rcdLsOIll51GOJ uHanVxX8O+WxMHq/a3j2kBkRiTVHWIBFHVremGbh2tfmeg4SnTjgAOsOcFhzLGsX lXdFMduSPXZ7o3bOCXSM8HqqWiGWzPY02618FCDgKJUz41xB6Bu/rjWzdx+bqeGD OufShsTRcohUKNeiqnGwk2rily/rnoQ6BUAANzC4rvK5D1q/fpqJfPI5S/LiP3mo ggFYzStmTxquzNXvYj8Gm/sdyHiiIFsx5qHMtEWsy/oZRCyFP+eSag6o6vjdc5jB syI/YPAFMD1NZ8vuvrx6d33oz7+KF07m782vwPp0gW1lS+FN1ptnazsWA0ImUSDX QDAR+A6l0nqpVZY1a5TJ6NnV+y4HB5ec8jdzibzzeVRDOMNo2TTeNbHVvBFIVwiD 1V/8lSsHJ7Pv8xnH47F4NfwwPEwpKCcBTaOXzVJc7tjK9jLyhA88HcBhC662AQY8
Bug#917457: marked as done (libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...))
Your message dated Mon, 07 Jan 2019 21:04:18 + with message-id and subject line Bug#917457: fixed in ilmbase 2.3.0-5 has caused the Debian Bug report #917457, regarding libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...) 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.) -- 917457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libilmbase23 Version: 2.3.0-3 Severity: critical Justification: breaks unrelated software ldd /usr/bin/digikam | grep libIlmImf-2_2.so.23 libIlmImf-2_2.so.23 => not found ldd /usr/bin/digikam | grep 'not found' libImath-2_2.so.23 => not found libIlmImf-2_2.so.23 => not found libIex-2_2.so.23 => not found libHalf.so.23 => not found libIlmThread-2_2.so.23 => not found I think gimp is also affected... valette@tri-yann4:~$ dpkg -L libilmbase23 /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libHalf.so.24.0.0 /usr/lib/x86_64-linux-gnu/libIex-2_3.so.24.0.0 /usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24.0.0 /usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24.0.0 /usr/lib/x86_64-linux-gnu/libImath-2_3.so.24.0.0 /usr/share /usr/share/doc /usr/share/doc/libilmbase23 /usr/share/doc/libilmbase23/AUTHORS /usr/share/doc/libilmbase23/NEWS.gz /usr/share/doc/libilmbase23/README.md.gz /usr/share/doc/libilmbase23/changelog.Debian.gz /usr/share/doc/libilmbase23/changelog.gz /usr/share/doc/libilmbase23/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libilmbase23 /usr/lib/x86_64-linux-gnu/libHalf.so.24 /usr/lib/x86_64-linux-gnu/libIex-2_3.so.24 /usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24 /usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24 /usr/lib/x86_64-linux-gnu/libImath-2_3.so.24 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.90 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libilmbase23 depends on: ii libc6 2.28-3 ii libgcc1 1:8.2.0-13 ii libstdc++6 8.2.0-13 libilmbase23 recommends no packages. libilmbase23 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: ilmbase Source-Version: 2.3.0-5 We believe that the bug you reported is fixed in the latest version of ilmbase, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated ilmbase package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 21:41:21 +0100 Source: ilmbase Binary: libilmbase24 libilmbase-dev Architecture: source Version: 2.3.0-5 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Description: libilmbase-dev - development files for IlmBase libilmbase24 - several utility libraries from ILM used by OpenEXR Closes: 917457 Changes: ilmbase (2.3.0-5) experimental; urgency=medium . * debian/overrides: Update libilmbase24 * debian/control: Provide a clean upgrade path. Closes: #917457 Checksums-Sha1: 2699292f116382774cc2abfc1fc8796bf12889e6 2338 ilmbase_2.3.0-5.dsc 1a396e2fee04950f908a487bd2ce85e5660aa29e 14192 ilmbase_2.3.0-5.debian.tar.xz 44c64ad8e9dcfeb752edffed2af2732faff01efa 4976 ilmbase_2.3.0-5_source.buildinfo Checksums-Sha256: 5b2693532ca359b037b8c552bf0b2c0a58272a9279bfac4ea091857187390f56 2338 ilmbase_2.3.0-5.dsc 45691ba62efaa9ad5f184dff3bac40a4bfda3cc23df608e5c1b6c6fcb3898c9b 14192 ilmbase_2.3.0-5.debian.tar.xz 7ea18393c1496f517e4ca7b7c40448f62ff61c60b5320a3c11f83164bb984155 4976 ilmbase_2.3.0-5_source.buildinfo Files: 63f1ae246a316891f0e4eec20dac37b7 2338 libs optional ilmbase_2.3.0-5.dsc ea0bcabc6d1583f41f8eababc5f4f472 14192 libs optional ilmbase_2.3.0-5.debian.tar.xz
Processed: tagging 918623
Processing commands for cont...@bugs.debian.org: > tags 918623 + buster sid Bug #918623 [dizzy] dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 918623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918633: why3-coq: package should Depend on a specific Coq version
Package: why3-coq Version: 1.1.1-1 Severity: serious why3-coq Depends on coq, but it contains compiled .vo files that can only be read by Coq 8.6. (In general, Coq .vo files are tied to the minor version of Coq that produced them.) why3-coq should Depend on the minor version of Coq that compiled it (like 8.6 or 8.8).
Bug#917750: marked as done (node-redis: FTBFS: tests failed)
Your message dated Mon, 07 Jan 2019 20:46:09 + with message-id and subject line Bug#917750: fixed in node-redis 2.8.0-1 has caused the Debian Bug report #917750, regarding node-redis: FTBFS: tests failed 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.) -- 917750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-redis Version: 0.12.1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > NODE_DISABLE_COLORS=1 nodejs test.js > [redis-server] 31493:C 29 Dec 2018 13:29:06.704 # oO0OoO0OoO0Oo Redis is > starting oO0OoO0OoO0Oo > 31493:C 29 Dec 2018 13:29:06.704 # Redis version=5.0.3, bits=64, > commit=, modified=0, pid=31493, just started > 31493:C 29 Dec 2018 13:29:06.704 # Configuration loaded > 31493:M 29 Dec 2018 13:29:06.705 * Running mode=standalone, port=6379. > 31493:M 29 Dec 2018 13:29:06.705 # WARNING: The TCP backlog setting of 511 > cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower > value of 128. > 31493:M 29 Dec 2018 13:29:06.705 # Server initialized > 31493:M 29 Dec 2018 13:29:06.705 # WARNING overcommit_memory is set to 0! > Background save may fail under low memory condition. To fix this issue add > 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the > command 'sysctl vm.overcommit_memory=1' for this to take effect. > 31493:M 29 Dec 2018 13:29:06.705 # WARNING you have Transparent Huge Pages > (THP) support enabled in your kernel. This will create latency and memory > usage issues with Redis. To fix this issue run the command 'echo never > > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your > /etc/rc.local in order to retain the setting after a reboot. Redis must be > restarted after THP is disabled. > 31493:M 29 Dec 2018 13:29:06.705 * Ready to accept connections > 31493:M 29 Dec 2018 13:29:06.705 * The server is now ready to accept > connections at /tmp/redis.sock > > Connected to 127.0.0.1:6379, Redis server version 5.0.3 > > Using reply parser javascript > - ipv4:(node:31487) [DEP0026] DeprecationWarning: util.print is deprecated. > Use console.log instead. > Connected to 127.0.0.1:6379, Redis server version 5.0.3 > > Using reply parser javascript > - ipv6:Connected to ::1:6379, Redis server version 5.0.3 > > Using reply parser javascript > - unix_socket:Connected to /tmp/redis.sock, Redis server version 5.0.3 > > Using reply parser javascript > - flushdb: 1 ms > - incr: 0 ms > - multi_1: 2 ms > - multi_2: 0 ms > - multi_3: 1 ms > - multi_4: 0 ms > - multi_5: 1 ms > - multi_6: 0 ms > - multi_7: 1 ms > - multi_exception_1: 1 ms > - multi_8: 1 ms > - fwd_errors_1:incoming > 151 ms > - eval_1: 5 ms > - script_load: 0 ms > - client_list:id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=N db=15 > sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r > cmd=exec > id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 > multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select > id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0 > multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe > id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 > multi=-1 qbuf=26 qbuf-free=32742 obl=0 oll=0 omem=0 events=r cmd=client > > id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0 > multi=1 qbuf=14 qbuf-free=32754 obl=4 oll=0 omem=0 events=r cmd=exec > id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 > multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select > id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0 > multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe > id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 > multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client > > id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0 > multi=1 qbuf=55 qbuf-free=32713 obl=18 oll=0 omem=0 events=r cmd=exec > id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 > multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select > id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0
Bug#917660: NMU of pyhamcrest to fix FTBFS in vim-youcompleteme
Hi, On Mon, Dec 31, 2018 at 12:06:53AM +0100, David Kalnischkies wrote: > As the freeze is drawing near I would appreciate a reply in the next > week so that we can proceed accordingly – I am e.g. happy to sponsor > uploads if need be. On the other hand, if I get no reply I plan to > upload at least a no-change -2 revision soon to resolve at least the I just uploaded -1.1 to DELAYED/2 as I wanted to wait for the 5 year anniversary of the last upload. ;) It's a strange diff in the binary python3-hamcrest package causing a FTBFS (and hence serious) bug in at least one package I care about fixed just by a rebuild, not a patch, so I hope its okay that I was waiting only 7 (+2) days in between years before NMUing. Feel free to drop me a line if I should cancel the upload OR override with an upload of your own – I am also happy to sponsor an upload if need be! Debdiff attached – which beside my changelog-only change includes also the so far not uploaded trivial changes in the VCS as it seemed like a good idea to point to an existing VCS (even if I have no access as I am not a member of python modules team) and correcting b-d. I have a branch locally with the NMU if you would prefer that. Best regards David Kalnischkies diff -Nru pyhamcrest-1.8.0/debian/changelog pyhamcrest-1.8.0/debian/changelog --- pyhamcrest-1.8.0/debian/changelog 2014-01-09 22:27:04.0 +0100 +++ pyhamcrest-1.8.0/debian/changelog 2019-01-07 18:49:27.0 +0100 @@ -1,3 +1,20 @@ +pyhamcrest (1.8.0-1.1) unstable; urgency=medium + + [ David Kalnischkies ] + * No-change non-maintainer upload to have python3-hamcrest rebuild without +the use of deprecated collections ABI usage causing FTBFS in at least +src:vim-youcompleteme (Closes: #917660) + + [ Ondřej Nový ] + * Fixed VCS URL (https) + * d/control: Set Vcs-* to salsa.debian.org + * Convert git repository from git-dpm to gbp layout + + [ Piotr Ożarowski ] + * Add dh-python to Build-Depends + + -- David Kalnischkies Mon, 07 Jan 2019 18:49:27 +0100 + pyhamcrest (1.8.0-1) unstable; urgency=low * New release diff -Nru pyhamcrest-1.8.0/debian/control pyhamcrest-1.8.0/debian/control --- pyhamcrest-1.8.0/debian/control 2014-01-09 22:27:04.0 +0100 +++ pyhamcrest-1.8.0/debian/control 2019-01-07 18:49:27.0 +0100 @@ -5,14 +5,15 @@ Uploaders: Debian Python Modules Team Build-Depends: debhelper (>= 7.0.50), + dh-python, python-all (>= 2.6.6-3), python-setuptools (>= 0.6b3), python3-all, python3-setuptools Standards-Version: 3.9.5 Homepage: http://code.google.com/p/hamcrest -Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/pyhamcrest/trunk/ -Vcs-Browser: http://anonscm.debian.org/viewvc/python-modules/packages/pyhamcrest/trunk/ +Vcs-Git: https://salsa.debian.org/python-team/modules/pyhamcrest.git +Vcs-Browser: https://salsa.debian.org/python-team/modules/pyhamcrest Package: python-hamcrest Architecture: all signature.asc Description: PGP signature
Bug#908492: NMU diff for nat-rtsp 0.7+4.18-0.1
I made an NMU fixing this issue (with a new upstream version). I also
updated the package to follow current policy and to fix some other
lintian complaints.
The new version is exported from the upstream tag 4.18 (commit
3a4a4866890e7daee96010291feb72396a99d9ed) so I used the upstream
version 0.7+4.18.
Ben.
--
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/debian/changelog nat-rtsp-0.7+4.18/debian/changelog
--- nat-rtsp-0.7+1.g2ea3cb6/debian/changelog 2013-12-12 16:56:57.0 +
+++ nat-rtsp-0.7+4.18/debian/changelog 2019-01-07 20:38:10.0 +
@@ -1,3 +1,17 @@
+nat-rtsp (0.7+4.18-0.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * New upstream release:
+- Add support to linux 4.18 (Closes: #908492)
+ * Update to policy version 4.3.0:
+- debian/copyright: Use https: URL for copyright format
+- debian/control: Change priority to optional
+- debian/control: Set Rules-Requires-Root: no
+ * debian/source/options: Delete as redundant
+ * Use debhelper compatibility level 12
+
+ -- Ben Hutchings Mon, 07 Jan 2019 20:38:10 +
+
nat-rtsp (0.7+1.g2ea3cb6-1) unstable; urgency=low
* Initial release (Closes: #732026)
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/debian/compat nat-rtsp-0.7+4.18/debian/compat
--- nat-rtsp-0.7+1.g2ea3cb6/debian/compat 2013-12-07 00:26:35.0 +
+++ nat-rtsp-0.7+4.18/debian/compat 2019-01-07 20:16:43.0 +
@@ -1 +1 @@
-8
+12
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/debian/control nat-rtsp-0.7+4.18/debian/control
--- nat-rtsp-0.7+1.g2ea3cb6/debian/control 2013-12-13 14:31:08.0 +
+++ nat-rtsp-0.7+4.18/debian/control 2019-01-07 20:35:53.0 +
@@ -1,10 +1,11 @@
Source: nat-rtsp
Section: kernel
-Priority: extra
+Priority: optional
Maintainer: Julien Muchembled
-Build-Depends: debhelper (>= 8.0.0), dkms
-Standards-Version: 3.9.5
+Build-Depends: debhelper (>= 12~), dkms
+Standards-Version: 4.3.0
Homepage: https://github.com/maru-sama/rtsp-linux
+Rules-Requires-Root: no
Package: nat-rtsp-dkms
Architecture: all
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/debian/copyright nat-rtsp-0.7+4.18/debian/copyright
--- nat-rtsp-0.7+1.g2ea3cb6/debian/copyright 2013-12-12 16:21:45.0 +
+++ nat-rtsp-0.7+4.18/debian/copyright 2019-01-07 20:25:23.0 +
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: rtsp-linux
Source: https://github.com/maru-sama/rtsp-linux
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/debian/source/options nat-rtsp-0.7+4.18/debian/source/options
--- nat-rtsp-0.7+1.g2ea3cb6/debian/source/options 2013-12-11 13:14:28.0 +
+++ nat-rtsp-0.7+4.18/debian/source/options 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-compression = xz
diff -Nru nat-rtsp-0.7+1.g2ea3cb6/nf_nat_rtsp.c nat-rtsp-0.7+4.18/nf_nat_rtsp.c
--- nat-rtsp-0.7+1.g2ea3cb6/nf_nat_rtsp.c 2013-04-03 18:22:19.0 +0100
+++ nat-rtsp-0.7+4.18/nf_nat_rtsp.c 2018-08-22 20:00:35.0 +0100
@@ -534,7 +534,9 @@
static void nf_nat_rtsp_expected(struct nf_conn* ct, struct nf_conntrack_expect *exp)
{
-#if LINUX_VERSION_CODE < KERNEL_VERSION(3,3,0) || LINUX_VERSION_CODE >= KERNEL_VERSION(3,7,0)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,18,0)
+ struct nf_nat_range2 range;
+#elif LINUX_VERSION_CODE < KERNEL_VERSION(3,3,0) || LINUX_VERSION_CODE >= KERNEL_VERSION(3,7,0)
struct nf_nat_range range;
#else
struct nf_nat_ipv4_range range;
signature.asc
Description: This is a digitally signed message part
Bug#916703: marked as done (mando FTBFS with Python 3.7)
Your message dated Mon, 07 Jan 2019 20:45:09 +
with message-id
and subject line Bug#916703: fixed in mando 0.6.4-4
has caused the Debian Bug report #916703,
regarding mando FTBFS with Python 3.7
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.)
--
916703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mando
Version: 0.6.4-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mando.html
...
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/build/1st/mando-0.6.4/.pybuild/cpython3_3.7_mando/build; python3.7 -m pytest
= test session starts ==
platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/mando-0.6.4, inifile:
collected 0 items
= no tests ran in 0.00 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=5: cd
/build/1st/mando-0.6.4/.pybuild/cpython3_3.7_mando/build; python3.7 -m pytest
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned
exit code 13
make: *** [debian/rules:18: build] Error 25
--- End Message ---
--- Begin Message ---
Source: mando
Source-Version: 0.6.4-4
We believe that the bug you reported is fixed in the latest version of
mando, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Neil Williams (supplier of updated mando package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 07 Jan 2019 19:51:54 +
Source: mando
Binary: python3-mando python-mando-doc
Architecture: source all
Version: 0.6.4-4
Distribution: unstable
Urgency: medium
Maintainer: Neil Williams
Changed-By: Neil Williams
Description:
python-mando-doc - command line argument parser for python3 (common
documentation)
python3-mando - command line argument parser for python3
Closes: 916703
Changes:
mando (0.6.4-4) unstable; urgency=medium
.
* Fix in-build tests command. (Closes: #916703)
Checksums-Sha1:
85f34b3e0c5e15c7633677b96fd1fd9512f464bc 1970 mando_0.6.4-4.dsc
930d3be9b624969cdb1fff3a1a45f6684d8201e5 3392 mando_0.6.4-4.debian.tar.xz
6f1c9bb567a39659b1dbed85b85264f18902a21a 7411 mando_0.6.4-4_amd64.buildinfo
6d8446485dfe94f5aefd2b0709bd68ed612e1f16 39240 python-mando-doc_0.6.4-4_all.deb
55a02e86a61853882cbea38edb0658b8ab6e7eab 22860 python3-mando_0.6.4-4_all.deb
Checksums-Sha256:
c7e84fef6889544b8da766f8d1f0f69423478df98346d6b260234f01523c14d6 1970
mando_0.6.4-4.dsc
59bf760eb233d5ec42ba561559550879183b021f93c147f251cf084846feee70 3392
mando_0.6.4-4.debian.tar.xz
bfa90de2ed94aaa70be11e9addf3eaabf3564e9885573fda63e08037011a113d 7411
mando_0.6.4-4_amd64.buildinfo
d1e44193b7e48024d8eb40d04ae7f46186e378a81356b9a96f92744ae4fd1bd0 39240
python-mando-doc_0.6.4-4_all.deb
c33b09f1b5c25f1270cf5540cc9dcda7be02631712ecfdd3af80c6f3cd98c890 22860
python3-mando_0.6.4-4_all.deb
Files:
5202b3420651e520e351638fe2c077b1 1970 python optional mando_0.6.4-4.dsc
aee656e5fe7ef8d7e31c50f19c372f01 3392 python optional
mando_0.6.4-4.debian.tar.xz
6ae70b72fc54bcd4fc97b25d59c3b11e 7411 python optional
mando_0.6.4-4_amd64.buildinfo
12022049f5a17e577df550430c692713 39240 doc optional
python-mando-doc_0.6.4-4_all.deb
a9e9e6502ab29e596db86ee4af310d64 22860 python optional
python3-mando_0.6.4-4_all.deb
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEf3HB6ceOc10DYMbM8WfkPIFDtoIFAlwzsZcACgkQ8WfkPIFD
toL8zhAAiclddCLS1iY7UvOXEoo+FsWaVIgGnydvYI9cAHckjbvtydA8rFneRO1N
gZmvyCDetvxaEimKww9Q957T2tqcN3TunU5irdcbCgNEY3Fd+9RXxZoEKbWtUrfG
IjOOF9MW5oA9QFCXqo2onBM9/Te//wq7RxQ7YDXc3PX00X/T8oro4qw0ld6d8C9d
EJvhVp41gO28GI43jAeT1TMoNgGLm77474r5Xx7GQEvu7Gsox/Tgsnv8t9zFSdcJ
Fg8wAXW6qCcTjyt+WLt7Hb4NVo9Tnj7286F5k6HvRoI2hwPA9eB44GwThl89UL4P
gSCc/Yu+T0Y6kQQEaCNwxL4glmE8vTj+7m4suiL/SncfMAy+Tn5eBEXqILgPcM7H
QIN8mwOUTVBpj/QOCBQjbHLqa4DYyLvUTgxORQ19ICByCAvP33jZga7oM0LhtOuG
rvJxcWAV2lukO32L78y3qHkY8U5bcM3QheSDiJcpnYRnwI/nBKWF9HJmbGaAw0qp
Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)
Followup-For: Bug #917457 Hi, this seems to be fixed in 2.3.0-4 by introducing a libilmbase24 package, but this lacks Breaks+Replaces: libilmbase23 (>= 2.3) to properly upgrade from the buggy package in case someone installed libilmbase23 from experimental. Apparently people did ... and found this bug. Andreas
Bug#918629: dnscrypt-proxy FTBFS with Go 1.11
Source: dnscrypt-proxy Version: 2.0.19+ds1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dnscrypt-proxy.html ... github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy # github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy github.com/aead/chacha20/chacha.supportsAVX2: relocation target runtime.support_avx not defined github.com/aead/chacha20/chacha.supportsAVX2: relocation target runtime.support_avx2 not defined github.com/aead/poly1305.supportsAVX2: relocation target runtime.support_avx2 not defined dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/build/1st/dnscrypt-proxy-2.0.19\+ds1/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/build/1st/dnscrypt-proxy-2.0.19\+ds1/obj-x86_64-linux-gnu/src\" -v -p 15 github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy returned exit code 2 make: *** [debian/rules:12: build] Error 2
Bug#918628: node-stream-splicer FTBFS with nodejs 10.15.0
Source: node-stream-splicer Version: 2.0.0-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-stream-splicer.html ... 76 passing (3m) 3 failing 1) test/nested.js should be equivalent: Error: should be equivalent at Error: should be equivalent at at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:235:54) at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10) at at Test.bound [as deepEqual] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at test/nested.js:29:11 at at ConcatStream. (/usr/lib/nodejs/concat-stream/index.js:37:43) at at finishMaybe (_stream_writable.js:641:14) at at endWritable (_stream_writable.js:649:3) at at ConcatStream.Writable.end (_stream_writable.js:589:5) 2) test/nested_middle.js should be equivalent: Error: should be equivalent at Error: should be equivalent at at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:235:54) at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10) at at Test.bound [as deepEqual] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at test/nested_middle.js:35:11 at at ConcatStream. (/usr/lib/nodejs/concat-stream/index.js:37:43) at at finishMaybe (_stream_writable.js:641:14) at at endWritable (_stream_writable.js:649:3) at at ConcatStream.Writable.end (_stream_writable.js:589:5) 3) test/pop.js should be equivalent: Error: should be equivalent at Error: should be equivalent at at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:235:54) at at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at Test.tapeDeepEqual (/usr/lib/nodejs/tape/lib/test.js:432:10) at at Test.bound [as deepEqual] (/usr/lib/nodejs/tape/lib/test.js:87:32) at at test/pop.js:38:11 at at ConcatStream. (/usr/lib/nodejs/concat-stream/index.js:37:43) at at finishMaybe (_stream_writable.js:641:14) at at endWritable (_stream_writable.js:649:3) at at ConcatStream.Writable.end (_stream_writable.js:589:5) make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
Bug#918627: node-cacache FTBFS with nodejs 10.15.0
Source: node-cacache Version: 10.0.4-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cacache.html ... 270 passing (1m) 7 pending 2 failing 1) test/content.write.js Cannot call write after a stream was destroyed: Error: Cannot call write after a stream was destroyed at WriteStream.end (/usr/lib/nodejs/flush-write-stream/index.js:43:41) 2) test/put.js errors if input stream errors returns the error from input stream: Error: returns the error from input stream at pipe.then.catch.err (test/put.js:138:7) at tryCatcher (/usr/lib/nodejs/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/usr/lib/nodejs/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/usr/lib/nodejs/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/usr/lib/nodejs/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/usr/lib/nodejs/bluebird/js/release/promise.js:689:18) at Async._drainQueue (/usr/lib/nodejs/bluebird/js/release/async.js:133:16) at Async._drainQueues (/usr/lib/nodejs/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/nodejs/bluebird/js/release/async.js:17:14) make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
Bug#918626: node-loader-utils FTBFS with nodejs 10.15.0
Source: node-loader-utils Version: 1.1.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-loader-utils.html ... 89 passing (476ms) 1 failing 1) parseQuery() when passed string is any other string not starting with ? should throw an error: TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is ambiguous. The error message "A valid query string passed to parseQuery should begin with '?'" is identical to the message. at expectsError (assert.js:629:15) at Function.throws (assert.js:690:3) at Context.it (test/parseQuery.test.js:76:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Processed: found 905214 in 1.4.0.P1-2
Processing commands for cont...@bugs.debian.org: > found 905214 1.4.0.P1-2 Bug #905214 [src:isc-kea] isc-kea: Incomplete debian/copyright? Marked as found in versions isc-kea/1.4.0.P1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 905214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918312: marked as done (salt-{master,minion} fail to purge)
Your message dated Mon, 07 Jan 2019 19:50:41 +
with message-id
and subject line Bug#918312: fixed in salt 2018.3.3+dfsg1-2
has caused the Debian Bug report #918312,
regarding salt-{master,minion} fail to purge
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.)
--
918312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: salt
Version: 2018.3.3+dfsg1-1
Severity: serious
Control: affects -1 salt-master salt-minion
https://piuparts.debian.org/sid/source/s/salt.html
Purging configuration files for salt-master (2018.3.3+dfsg1-1) ...
rmdir: failed to remove '/var/lib/salt/pki': No such file or directory
dpkg: error processing package salt-master (--purge):
installed salt-master package post-removal script subprocess returned error
exit status 1
Errors were encountered while processing:
salt-master
Purging configuration files for salt-minion (2018.3.3+dfsg1-1) ...
rmdir: failed to remove '/var/lib/salt/pki': No such file or directory
rmdir: failed to remove '/var/lib/salt': No such file or directory
dpkg: error processing package salt-minion (--purge):
installed salt-minion package post-removal script subprocess returned error
exit status 1
Errors were encountered while processing:
salt-minion
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-2
We believe that the bug you reported is fixed in the latest version of
salt, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Benjamin Drung (supplier of updated salt
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 07 Jan 2019 15:30:51 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc
salt-cloud salt-api salt-proxy
Architecture: source
Version: 2018.3.3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team
Changed-By: Benjamin Drung
Description:
salt-api - Generic, modular network access system
salt-cloud - public cloud VM management system
salt-common - shared libraries that salt requires for all packages
salt-doc - additional documentation for salt, the distributed remote executi
salt-master - remote manager to administer servers via salt
salt-minion - client package for salt, the distributed remote execution system
salt-proxy - Proxy client package for salt stack
salt-ssh - remote manager to administer servers via Salt SSH
salt-syndic - master-of-masters for salt, the distributed remote execution syst
Closes: 918312 918377
Changes:
salt (2018.3.3+dfsg1-2) unstable; urgency=medium
.
* Check existence before removing /var/lib/salt/pki on purge (Closes:
#918312)
* Don't import obsolete Directive class from Sphinx to fix build failure with
Sphinx 1.8. Thanks to Dmitry Shachnev. (Closes: #918377)
* Bump Standards-Version to 4.3.0 (no changes are required)
Checksums-Sha1:
c40ad90b53b8ea89da8cb6e8051c557268655681 4046 salt_2018.3.3+dfsg1-2.dsc
b848b2912243be2687601bd2c0ef47a3d3eb2bf3 65400
salt_2018.3.3+dfsg1-2.debian.tar.xz
f95c09cdbc27dd66ec061910b2e87b6d713e7720 8542
salt_2018.3.3+dfsg1-2_source.buildinfo
Checksums-Sha256:
4050da8fc294e2f6cb379ee1bb833ed6c7c81df4e4e114f893ebfe77cd774db3 4046
salt_2018.3.3+dfsg1-2.dsc
20c5e82026a6a4da8ace1fc1dc1da6df346dd57a49a2d516566bb481bcae1dc4 65400
salt_2018.3.3+dfsg1-2.debian.tar.xz
2389f9e3ed33c1e25b9f885e62317baaa07b02eb909b18a208504ffc15c1eaa2 8542
salt_2018.3.3+dfsg1-2_source.buildinfo
Files:
78206975d35d3052ce0986735f76b75a 4046 admin optional salt_2018.3.3+dfsg1-2.dsc
0a8a23e6f331f31048bf6c1a78e78fcd 65400 admin optional
salt_2018.3.3+dfsg1-2.debian.tar.xz
12bdb7ba8137e10f0dc0db8ee8212b93 8542 admin optional
salt_2018.3.3+dfsg1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAlwzpi4ACgkQFZ61xO/I
d0yr2A/9EM6E9nl3ObcznNMGZv/n886GrMzIV5v/kwOQ/axhlPoF7J3IdydAxORK
CNbrwrMolFosSbXOwmZRBs47XnLAN7Zgv0fvwXzNF3KXTZ6NiObjerbsevcDZ/6p
Bug#917860: marked as done (Fails to build for non-current kernel version)
Your message dated Mon, 07 Jan 2019 19:49:37 + with message-id and subject line Bug#917860: fixed in kpatch 0.6.0-0.2 has caused the Debian Bug report #917860, regarding Fails to build for non-current kernel version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kpatch-dkms Version: 2.0.93-0.10 Severity: serious When running kernel version 4.18.0-3-amd64 and building for 4.19.0-1-amd64, the build fails: ... Setting up kpatch-dkms (0.6.0-0.1) ... Loading new kpatch-0.6.0 DKMS files... Building for 4.19.0-1-amd64 Building initial module for 4.19.0-1-amd64 Makefile:7: *** /lib/modules/4.18.0-3-amd64/build doesn\'t exist. Try installing the kernel-devel-4.18.0-3-amd64 RPM or linux-headers-4.18.0-3-amd64 DEB.. Stop. make: *** [Makefile:27: clean] Error 2 ... The problem is that the CLEAN command specified in dkms.conf doesn't set the KPATCH_BUILD variable, like the MAKE command does. Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kpatch-dkms depends on: pn dkms ii linux-headers-amd64 4.19+101 kpatch-dkms recommends no packages. kpatch-dkms suggests no packages. --- End Message --- --- Begin Message --- Source: kpatch Source-Version: 0.6.0-0.2 We believe that the bug you reported is fixed in the latest version of kpatch, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated kpatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 19:39:23 + Source: kpatch Binary: kpatch kpatch-dkms kpatch-build Architecture: source Version: 0.6.0-0.2 Distribution: unstable Urgency: medium Maintainer: Chris J Arges Changed-By: Ben Hutchings Description: kpatch - Runtime tools for Kpatch kpatch-build - Build Tools for Kpatch and Livepatch kpatch-dkms - DKMS module for Kpatch Closes: 917860 917861 Changes: kpatch (0.6.0-0.2) unstable; urgency=medium . * Non-maintainer upload * kmod: Fix symbol lookup on Linux 4.19 (Closes: #917861) * dkms: Pass target kernel version to the upstream clean target (Closes: #917860) * kpatch-build: Fix clean target Checksums-Sha1: 5b177f1428e0623e16b678ba57d777a008a98895 1982 kpatch_0.6.0-0.2.dsc d4afd851922f5d92d8178247432431e8249c2c47 7868 kpatch_0.6.0-0.2.debian.tar.xz 5ff574247c6b56130357b868b29233d1d7c7f5f7 5446 kpatch_0.6.0-0.2_source.buildinfo Checksums-Sha256: 5f5f09ea6713d15e9f156ad9fdeb4f5f8faf559474fc259f789a32a22117d226 1982 kpatch_0.6.0-0.2.dsc 9334cd7d69c8c15548f69d95285b71927943f1d541ba46a6a3dcb973b3fed8a1 7868 kpatch_0.6.0-0.2.debian.tar.xz b569dcac78cf652d61e8970d9f898ca333a61fa5d47322a0097b7dd24a7f5a3d 5446 kpatch_0.6.0-0.2_source.buildinfo Files: df0d31ccd0fb0432f5a5188418dfd4d2 1982 kernel optional kpatch_0.6.0-0.2.dsc 49239d7070c7c87af7999150e528031c 7868 kernel optional kpatch_0.6.0-0.2.debian.tar.xz dc1065fe83dc87a99a4bf5ab3147aa88 5446 kernel optional kpatch_0.6.0-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlwzq6YACgkQ57/I7JWG EQkjFw/+IEHhr22n8m+JjLljZ1UUBpWzhhy0qspNOaOpUPcUggHLb3SRGalFehnh KqxGcddAIM/MRCNfMCTagp7b9x6z1jZ43AxidoEA/M0uVb9B6qc6pVET6y3tPIcr unvSkSKkKI77IgxaJKWr4XM2Gsjtr00GuLvpVcHwsxtGCni7rf+aAC2TxN9Uk21E n30BaekNGf3l4o4rFXjpiR0+jf2WsEHe6/JaeJOSTPBsDODNWGPgQCwUtxKABSVu H42aWUZrBownAZnzYxqvyVy/H1ric1msHahuJUIsiQk0hxwCC6I/d5H+mPrrGLLq e8FdJmtrcVmtroBnKlbZrj/LuP8wSVLD9TVwJBDzd8Z4hEUiy62eJUuNOJGaH2ZQ
Bug#917861: marked as done (Fails to build against Linux 4.19)
Your message dated Mon, 07 Jan 2019 19:49:37 + with message-id and subject line Bug#917861: fixed in kpatch 0.6.0-0.2 has caused the Debian Bug report #917861, regarding Fails to build against Linux 4.19 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.) -- 917861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kpatch-dkms Version: 0.6.0-0.1 Severity: grave kpatch in testing/unstable fails to build a module for Linux 4.19, which is the current kernel version in these suites and the version that will be included in Debian 10 "buster": CC [M] /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c: In function 'kpatch_find_external_symbol': /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:654:14: error: 'const struct kernel_symbol' has no member named 'value' *addr = sym->value; ^~ Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kpatch-dkms depends on: pn dkms ii linux-headers-amd64 4.19+101 kpatch-dkms recommends no packages. kpatch-dkms suggests no packages. --- End Message --- --- Begin Message --- Source: kpatch Source-Version: 0.6.0-0.2 We believe that the bug you reported is fixed in the latest version of kpatch, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated kpatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jan 2019 19:39:23 + Source: kpatch Binary: kpatch kpatch-dkms kpatch-build Architecture: source Version: 0.6.0-0.2 Distribution: unstable Urgency: medium Maintainer: Chris J Arges Changed-By: Ben Hutchings Description: kpatch - Runtime tools for Kpatch kpatch-build - Build Tools for Kpatch and Livepatch kpatch-dkms - DKMS module for Kpatch Closes: 917860 917861 Changes: kpatch (0.6.0-0.2) unstable; urgency=medium . * Non-maintainer upload * kmod: Fix symbol lookup on Linux 4.19 (Closes: #917861) * dkms: Pass target kernel version to the upstream clean target (Closes: #917860) * kpatch-build: Fix clean target Checksums-Sha1: 5b177f1428e0623e16b678ba57d777a008a98895 1982 kpatch_0.6.0-0.2.dsc d4afd851922f5d92d8178247432431e8249c2c47 7868 kpatch_0.6.0-0.2.debian.tar.xz 5ff574247c6b56130357b868b29233d1d7c7f5f7 5446 kpatch_0.6.0-0.2_source.buildinfo Checksums-Sha256: 5f5f09ea6713d15e9f156ad9fdeb4f5f8faf559474fc259f789a32a22117d226 1982 kpatch_0.6.0-0.2.dsc 9334cd7d69c8c15548f69d95285b71927943f1d541ba46a6a3dcb973b3fed8a1 7868 kpatch_0.6.0-0.2.debian.tar.xz b569dcac78cf652d61e8970d9f898ca333a61fa5d47322a0097b7dd24a7f5a3d 5446 kpatch_0.6.0-0.2_source.buildinfo Files: df0d31ccd0fb0432f5a5188418dfd4d2 1982 kernel optional kpatch_0.6.0-0.2.dsc 49239d7070c7c87af7999150e528031c 7868 kernel optional kpatch_0.6.0-0.2.debian.tar.xz dc1065fe83dc87a99a4bf5ab3147aa88 5446 kernel optional kpatch_0.6.0-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlwzq6YACgkQ57/I7JWG EQkjFw/+IEHhr22n8m+JjLljZ1UUBpWzhhy0qspNOaOpUPcUggHLb3SRGalFehnh KqxGcddAIM/MRCNfMCTagp7b9x6z1jZ43AxidoEA/M0uVb9B6qc6pVET6y3tPIcr unvSkSKkKI77IgxaJKWr4XM2Gsjtr00GuLvpVcHwsxtGCni7rf+aAC2TxN9Uk21E n30BaekNGf3l4o4rFXjpiR0+jf2WsEHe6/JaeJOSTPBsDODNWGPgQCwUtxKABSVu H42aWUZrBownAZnzYxqvyVy/H1ric1msHahuJUIsiQk0hxwCC6I/d5H+mPrrGLLq e8FdJmtrcVmtroBnKlbZrj/LuP8wSVLD9TVwJBDzd8Z4hEUiy62eJUuNOJGaH2ZQ yztdPPslXnl07R+ggnLdwIUOiiNEKU+gFuiCn+YueTCJfr3vo9+2z7/owSwbffIF
Bug#918622: ruby-leaflet-rails FTBFS with rails 5.2
Source: ruby-leaflet-rails Version: 0.7.7-1 Severity: serious Tags: ftbfs buster sid Control: close -1 1.3.1-1 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-leaflet-rails.html ... ┌──┐ │ Run tests for ruby2.5 from debian/ruby-tests.rake│ └──┘ RUBYLIB=. GEM_PATH=debian/ruby-leaflet-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all ruby2.5 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation config.eager_load is set to nil. Please update your config/environments/*.rb files accordingly: * development - set it to false * test - set it to false (unless you use a tool that preloads your test environment) * production - set it to true An error occurred while loading ./spec/view_helpers_spec.rb. Failure/Error: app.config.assets.precompile += %w(layers-2x.png layers.png marker-icon-2x.png marker-icon.png marker-shadow.png) NoMethodError: undefined method `assets' for # Did you mean? asset_host # ./lib/leaflet-rails.rb:13:in `block in ' # ./spec/spec_helper.rb:31:in `' # ./spec/view_helpers_spec.rb:1:in `' No examples found. Finished in 0.00066 seconds (files took 2.7 seconds to load) 0 examples, 0 failures, 1 error occurred outside of examples /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /build/1st/ruby-leaflet-rails-0.7.7/debian/ruby-leaflet-rails returned exit code 1 make: *** [debian/rules:7: binary] Error 1 This is fixed in the package in experimental.
Bug#917861: NMU diff for kpatch 0.6.0-0.2
I made an NMU fixing this and the other RC bug, plus a double-build
failure I noticed while preparing it.
Ben.
--
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.
diff -Nru kpatch-0.6.0/debian/changelog kpatch-0.6.0/debian/changelog
--- kpatch-0.6.0/debian/changelog 2018-06-15 23:23:46.0 +0100
+++ kpatch-0.6.0/debian/changelog 2019-01-07 19:39:23.0 +
@@ -1,3 +1,13 @@
+kpatch (0.6.0-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * kmod: Fix symbol lookup on Linux 4.19 (Closes: #917861)
+ * dkms: Pass target kernel version to the upstream clean target
+(Closes: #917860)
+ * kpatch-build: Fix clean target
+
+ -- Ben Hutchings Mon, 07 Jan 2019 19:39:23 +
+
kpatch (0.6.0-0.1) unstable; urgency=medium
[Simon Ruderich]
diff -Nru kpatch-0.6.0/debian/kpatch-dkms.dkms kpatch-0.6.0/debian/kpatch-dkms.dkms
--- kpatch-0.6.0/debian/kpatch-dkms.dkms 2018-06-15 23:23:46.0 +0100
+++ kpatch-0.6.0/debian/kpatch-dkms.dkms 2019-01-07 19:24:43.0 +
@@ -2,7 +2,7 @@
BUILT_MODULE_NAME="kpatch"
BUILT_MODULE_LOCATION="kmod/core"
DEST_MODULE_LOCATION="/updates/dkms"
-CLEAN="make -C kmod/ clean"
+CLEAN="make -C kmod/ KPATCH_BUILD=/lib/modules/${kernelver}/build clean"
PACKAGE_NAME="kpatch"
PACKAGE_VERSION=#MODULE_VERSION#
REMAKE_INITRD="no"
diff -Nru kpatch-0.6.0/debian/patches/kmod-fix-symbol-lookup-on-linux-4.19.patch kpatch-0.6.0/debian/patches/kmod-fix-symbol-lookup-on-linux-4.19.patch
--- kpatch-0.6.0/debian/patches/kmod-fix-symbol-lookup-on-linux-4.19.patch 1970-01-01 01:00:00.0 +0100
+++ kpatch-0.6.0/debian/patches/kmod-fix-symbol-lookup-on-linux-4.19.patch 2019-01-07 19:38:41.0 +
@@ -0,0 +1,41 @@
+From: Ben Hutchings
+Date: Mon, 07 Jan 2019 19:19:42 +
+Subject: kmod: Fix symbol lookup on Linux 4.19
+
+Since Linux 4.19, symbols may contain either an absolute address or a
+self-relative offset, depending on
+CONFIG_HAVE_ARCH_PREL32_RELOCATIONS. The function to resolve the
+address is unfortunately not inline or exported, so copy it here.
+
+Since the configuration symbol didn't exist before, we don't need to
+add an explicit kernel version check.
+
+---
+--- a/kmod/core/core.c
b/kmod/core/core.c
+@@ -636,6 +636,16 @@ static int kpatch_find_object_symbol(con
+ return -EINVAL;
+ }
+
++/* Copied from kernel/module.c */
++static unsigned long kernel_symbol_value(const struct kernel_symbol *sym)
++{
++#ifdef CONFIG_HAVE_ARCH_PREL32_RELOCATIONS
++ return (unsigned long)offset_to_ptr(>value_offset);
++#else
++ return sym->value;
++#endif
++}
++
+ /*
+ * External symbols are located outside the parent object (where the parent
+ * object is either vmlinux or the kmod being patched).
+@@ -651,7 +661,7 @@ static int kpatch_find_external_symbol(c
+ sym = find_symbol(name, NULL, NULL, true, true);
+ preempt_enable();
+ if (sym) {
+- *addr = sym->value;
++ *addr = kernel_symbol_value(sym);
+ return 0;
+ }
+
diff -Nru kpatch-0.6.0/debian/patches/kpatch-build-fix-clean-target.patch kpatch-0.6.0/debian/patches/kpatch-build-fix-clean-target.patch
--- kpatch-0.6.0/debian/patches/kpatch-build-fix-clean-target.patch 1970-01-01 01:00:00.0 +0100
+++ kpatch-0.6.0/debian/patches/kpatch-build-fix-clean-target.patch 2019-01-07 19:38:19.0 +
@@ -0,0 +1,17 @@
+From: Ben Hutchings
+Date: Mon, 07 Jan 2019 19:37:04 +
+Subject: kpatch-build: Fix clean target
+
+The clean target uses brace-expansion which is a bash extension not
+supported by e.g. dash. Force use of bash for this target.
+
+---
+--- a/kpatch-build/Makefile
b/kpatch-build/Makefile
+@@ -43,5 +43,6 @@ uninstall:
+ $(RM) -R $(LIBEXECDIR)
+ $(RM) $(BINDIR)/kpatch-build
+
++clean: SHELL = /bin/bash
+ clean:
+ $(RM) $(TARGETS) *.{o,d} insn/*.{o,d} gcc-plugins/*.{so,d}
diff -Nru kpatch-0.6.0/debian/patches/series kpatch-0.6.0/debian/patches/series
--- kpatch-0.6.0/debian/patches/series 2018-06-15 23:23:46.0 +0100
+++ kpatch-0.6.0/debian/patches/series 2019-01-07 19:38:32.0 +
@@ -1,2 +1,4 @@
kpatch-build-adjust-dirs.patch
Fix-build-err-by-Werror-maybe-uninitialized.patch
+kmod-fix-symbol-lookup-on-linux-4.19.patch
+kpatch-build-fix-clean-target.patch
signature.asc
Description: This is a digitally signed message part
Processed: affects 918515
Processing commands for cont...@bugs.debian.org: > affects 918515 src:golang-github-jedisct1-xsecretbox Bug #918515 [src:golang-github-aead-chacha20] golang-github-aead-chacha20 FTBFS: relocation target runtime.support_avx not defined Added indication that 918515 affects src:golang-github-jedisct1-xsecretbox > thanks Stopping processing here. Please contact me if you need assistance. -- 918515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ruby-leaflet-rails FTBFS with rails 5.2
Processing control commands: > close -1 1.3.1-1 Bug #918622 [src:ruby-leaflet-rails] ruby-leaflet-rails FTBFS with rails 5.2 Marked as fixed in versions ruby-leaflet-rails/1.3.1-1. Bug #918622 [src:ruby-leaflet-rails] ruby-leaflet-rails FTBFS with rails 5.2 Marked Bug as done -- 918622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
Hello! gregor herrmann kirjoitti pe 4. tammikuuta 2019 klo 1.23: > On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote: > > > Just checking: are you Georg or Gregor currently working on this > > issue, and do you have any estimate when we could expect either a > > patch to MariaDB Connector C or a new upload of DBD-mysql so this > > issue would be resolved? > > I had a look at DBD::mysql and DBD::MariaDB but without any success. > I hope that someone with a better understanding than me from the > Debian perl Group can try and find a solution. > > I've now pinged the upstream issue at: > https://github.com/perl5-dbi/DBD-mysql/issues/275 Thanks Gregor for working with upstreams to fix this. Nice Eric Herman was also involved ;) Georg Richter, I hope you can review https://github.com/MariaDB/mariadb-connector-c/pull/95 shortly, thanks! >
Bug#918619: golang-github-go-errors-errors FTBFS with Go 1.11
Source: golang-github-go-errors-errors
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-go-errors-errors.html
...
=== RUN TestStackFormat
--- FAIL: TestStackFormat (0.00s)
error_test.go:33: Stack trace does not contain source line: 'a: b(5)'
error_test.go:34:
/build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:21
(0x4f5f35)
TestStackFormat.func1: e, expected := Errorf("hi"), callers()
/usr/lib/go-1.11/src/runtime/asm_amd64.s:522 (0x455b3b)
call32: CALLFN(·call32, 32)
/usr/lib/go-1.11/src/runtime/panic.go:513 (0x429df9)
gopanic: reflectcall(nil, unsafe.Pointer(d.fn), deferArgs(d),
uint32(d.siz), uint32(d.siz))
/build/1st/golang-github-go-errors-errors-1.0.1/obj-x86_64-linux-gnu/src/github.com/go-errors/errors/error_test.go:245
(0x4f38ff)
TestStackFormat: panic('a')
/usr/lib/go-1.11/src/testing/testing.go:827 (0x4b573f)
tRunner: fn(t)
/usr/lib/go-1.11/src/runtime/asm_amd64.s:1333 (0x4576d1)
goexit: BYTE$0x90 // NOP
...
Bug#918618: golang-github-grpc-ecosystem-grpc-gateway FTBFS: github.com/grpc-ecosystem/grpc-gateway/runtime [build failed]
Source: golang-github-grpc-ecosystem-grpc-gateway Version: 1.3.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-grpc-gateway.html ... # github.com/grpc-ecosystem/grpc-gateway/runtime_test [github.com/grpc-ecosystem/grpc-gateway/runtime.test] src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:71:46: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:72:47: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:73:46: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:74:46: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:75:47: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:76:47: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:77:45: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:78:47: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:118:46: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:119:47: too few values in literal src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:119:47: too many errors FAILgithub.com/grpc-ecosystem/grpc-gateway/runtime [build failed] ? github.com/grpc-ecosystem/grpc-gateway/runtime/internal [no test files]
Processed: RM: revelation -- RoQA; unmaintained, depends on gnome-python
Processing control commands: > severity -1 normal Bug #917210 [src:revelation] revelation: Intent to remove from Debian Severity set to 'normal' from 'serious' > tags -1 -sid -buster Bug #917210 [src:revelation] revelation: Intent to remove from Debian Removed tag(s) sid. Bug #917210 [src:revelation] revelation: Intent to remove from Debian Removed tag(s) buster. > retitle -1 RM: revelation -- RoQA; unmaintained, depends on gnome-python Bug #917210 [src:revelation] revelation: Intent to remove from Debian Changed Bug title to 'RM: revelation -- RoQA; unmaintained, depends on gnome-python' from 'revelation: Intent to remove from Debian'. > reassign -1 ftp.debian.org Bug #917210 [src:revelation] RM: revelation -- RoQA; unmaintained, depends on gnome-python Bug reassigned from package 'src:revelation' to 'ftp.debian.org'. No longer marked as found in versions revelation/0.4.14-3. Ignoring request to alter fixed versions of bug #917210 to the same values previously set -- 917210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918559: Bug #918559 in octave-geometry marked as pending
Control: tag -1 pending Hello, Bug #918559 in octave-geometry 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/pkg-octave-team/octave-geometry/commit/8a46637b83e51be34cc6c5a7eb89fa4ceb824e86 d/p/do-not-strip-debugging-symbols.patch: New patch Closes: #918559 (this message was generated automatically) -- Greetings https://bugs.debian.org/918559
Processed: Bug #918559 in octave-geometry marked as pending
Processing control commands: > tag -1 pending Bug #918559 [src:octave-geometry] octave-geometry FTBFS: dh_dwz returned exit code 1 Added tag(s) pending. -- 918559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917210: RM: revelation -- RoQA; unmaintained, depends on gnome-python
Control: severity -1 normal Control: tags -1 -sid -buster Control: retitle -1 RM: revelation -- RoQA; unmaintained, depends on gnome-python Control: reassign -1 ftp.debian.org Please remove revelation from Debian. Thank you, Jeremy Bicha
Bug#918312: Bug #918312 in salt marked as pending
Control: tag -1 pending
Hello,
Bug #918312 in salt 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/salt-team/salt/commit/ce65a66162ea33cdb20a5839c6fe5027cc57b1ca
Check existence before removing /var/lib/salt/pki on purge
salt-{master,minion} fails to purge, when '/var/lib/salt/pki' does not exist.
Therefore check for the presence of the directories before trying to remove
them.
Closes: #918312
Signed-off-by: Benjamin Drung
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/918312
Processed: Bug #918312 in salt marked as pending
Processing control commands:
> tag -1 pending
Bug #918312 [src:salt] salt-{master,minion} fail to purge
Added tag(s) pending.
--
918312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
