Bug#979451: marked as done (dtkgui FTCBFS: hard codes the build architecture pkg-config)
Your message dated Tue, 12 Jan 2021 07:18:24 +
with message-id
and subject line Bug#979451: fixed in dtkgui 5.2.2.4-2
has caused the Debian Bug report #979451,
regarding dtkgui FTCBFS: hard codes the build architecture pkg-config
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.)
--
979451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dtkgui
Version: 5.2.2.4-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
dtkgui fails to cross build from source, because src/src.pro hard codes
the build architecture pkg-config. Please use the detected pkg-config
instead. I'm attaching a patch for your convenience.
Helmut
--- dtkgui-5.2.2.4.orig/src/src.pro
+++ dtkgui-5.2.2.4/src/src.pro
@@ -58,7 +58,7 @@
linux* {
# don't link library
-QMAKE_CXXFLAGS += $$system(pkg-config --cflags-only-I librsvg-2.0)
+QMAKE_CXXFLAGS += $$system($$pkgConfigExecutable() --cflags-only-I librsvg-2.0)
HEADERS += \
$$PWD/dregionmonitor.h
--- End Message ---
--- Begin Message ---
Source: dtkgui
Source-Version: 5.2.2.4-2
Done: Arun Kumar Pariyar
We believe that the bug you reported is fixed in the latest version of
dtkgui, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arun Kumar Pariyar (supplier of updated dtkgui 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, 12 Jan 2021 00:21:00 +0545
Source: dtkgui
Architecture: source
Version: 5.2.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Arun Kumar Pariyar
Changed-By: Arun Kumar Pariyar
Closes: 979451
Changes:
dtkgui (5.2.2.4-2) unstable; urgency=medium
.
* debian/patches:
+ Use detected pkg-config to fix cross build (Closes: #979451).
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
Checksums-Sha1:
75a94a22a16d648c09a1b5f89fe6ca1d56897a93 2212 dtkgui_5.2.2.4-2.dsc
b3f3c321008460c9ca455f3a13f52c8896592816 3852 dtkgui_5.2.2.4-2.debian.tar.xz
94f30a2b090d7f6de31eaec71166628ab122d34b 14255 dtkgui_5.2.2.4-2_amd64.buildinfo
Checksums-Sha256:
ac6687b745f2f743f253c7bf344c63492619b8568de06d7671a83b895befd2bd 2212
dtkgui_5.2.2.4-2.dsc
d8030181c87f62f3ff512f4acd28c01d259aec14bfc3e70ea860447669a51ccd 3852
dtkgui_5.2.2.4-2.debian.tar.xz
c39f46767e8274df2acb83a413eb5158e89771db79feb55428a9b87e21ecf197 14255
dtkgui_5.2.2.4-2_amd64.buildinfo
Files:
e9ac26978ef6110c74c85f79804937b8 2212 libs optional dtkgui_5.2.2.4-2.dsc
93d0a915009947d90935e92e4c8ee627 3852 libs optional
dtkgui_5.2.2.4-2.debian.tar.xz
ab41ea94737c7af40e30feb1fd974d7f 14255 libs optional
dtkgui_5.2.2.4-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAl/9RzoACgkQS1Qq9wT3
RRb49g/+MewFk/lAfjf83Oyal+QODDpsK9YcxB3z0qjg0twuGak6X8gIUYSrA6Xo
swY7TNCQx0Crf+d2mNdElITs/mf9FXUlQ0Pz+hEXNAXnmAMJBJ0k6KkWXnm0KXzn
3qUD7CjDZU3BBlkaxtVVwkaJnsDAg2HogbdOiXHpT/64ciMgL6YQsgrCYGcUhWGv
2SLWEbhg7Asvre0wLnFcyISqSUQqOp2fWbQZR2tQ8rk9mULUL3gxONH/bU1zuasy
Cwa3rHxxJAqGV/bO17D3Dykc4RFeOyPxDgDUIHEDVMzXO26JKh5Me8jYjDIKfKyj
Yl/6T/X9fvsK9aYCza2r/XZqhyO1z7XA2qadJ3VTiYrw/WTLNX+sMDfYf/Y5pIdd
Ru6RcSPhPpVul073MgD7gr6rHj5upzchSq82KwL0j+yZRm8ZwN6itYWw61V5PNCm
wFOAsVG/E3ttBDkLGXwkpaHX1zCjKe1Mhg/xssO1dup7okjGj2z1ey3tHobeZK3U
tuVAVe45v+aWYxMPZErXt/J8qOAlBcVidENi7nIbUPamhYMHw8LQePi+TX2rysJJ
/pIba7Uy36XQJrXyQUEMOlsjitV660/hyxt+NP058ZWBotaGw/Z40P12dIKvkiZt
1CWtVPkuxj6VxDJXjpkqO++qFf2cbZGZ5HREOfilvZCljU+/Nz0=
=MLd2
-END PGP SIGNATURE End Message ---
Bug#887231: marked as done (dnssec-trigger should recommend e2fsprogs)
Your message dated Tue, 12 Jan 2021 07:18:19 + with message-id and subject line Bug#887231: fixed in dnssec-trigger 0.17+repack-5 has caused the Debian Bug report #887231, regarding dnssec-trigger should recommend e2fsprogs 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.) -- 887231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnssec-trigger Version: 0.13-6 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. dnssec-trigger was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/lib/dnssec-trigger/dnssec-trigger-script contains chattr. According to file it is a Python script, UTF-8 Unicode text executable /usr/sbin/dnssec-triggerd contains chattr. According to file it is a ELF 64-bit LSB shared object, x86-64, version 1 (SYSV) Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- Source: dnssec-trigger Source-Version: 0.17+repack-5 Done: Diane Trout We believe that the bug you reported is fixed in the latest version of dnssec-trigger, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Diane Trout (supplier of updated dnssec-trigger 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, 11 Jan 2021 21:30:22 -0800 Source: dnssec-trigger Architecture: source Version: 0.17+repack-5 Distribution: unstable Urgency: medium Maintainer: dnssec-trigger packagers Changed-By: Diane Trout Closes: 887231 Changes: dnssec-trigger (0.17+repack-5) unstable; urgency=medium . * Recommend e2fsprogs (Closes: #887231) dnssec-trigger tries to call chattr to protect files it updated. * small-key test fix: Make sure dnssec-trigger directory exists before writing to it. * small-key test fix: downgrade error messages from installer to stdout Checksums-Sha1: 3c2130ec7e2ba198308d62823c172c2531b0aac5 2197 dnssec-trigger_0.17+repack-5.dsc 97120f73fa8c6c38aa5103917829759ae66f3bfa 16236 dnssec-trigger_0.17+repack-5.debian.tar.xz 29d133493dcb9f0e4e36abf93f0a87d21cf304b9 11287 dnssec-trigger_0.17+repack-5_source.buildinfo Checksums-Sha256: ca461dae18abefde27f10c89f9f751b923636e5ba08672830395c41b0ba8929c 2197 dnssec-trigger_0.17+repack-5.dsc 11be96a47811d06391b241a5c75269ba60043ff0ee85415275fc0ff565ede342 16236 dnssec-trigger_0.17+repack-5.debian.tar.xz 1de7ab3a0194afb766128f28cbee8f412e34ba0ebabf9372fe32e8a2d729256e 11287 dnssec-trigger_0.17+repack-5_source.buildinfo Files: 58cfd188090709f1a7058138745eb4f7 2197 net optional dnssec-trigger_0.17+repack-5.dsc 02893e49eb6d692599a5455a8f2fb0d1 16236 net optional dnssec-trigger_0.17+repack-5.debian.tar.xz 521cf171e4b7874dbd05a5ecda57c198 11287 net optional dnssec-trigger_0.17+repack-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAl/9STQACgkQmQ04NnM0 13AbnA//X/vX2PcC4YQIZy+rIt0Q0WCZOyhW86CHjzAu126Y4PaSrqxHTgLcZRs7 GN/1TkE4UZXpBBxDVo8b5TfipzoQJcqy+qmP7f59SvBCbOSWorQUWRwtUTI2K9lR 16s5/qnK7zob8vHd52W5gjW7JVHA0LNmAbUh4y9N69srnJIxd4yzwYqN8Qv2G6IX GOydvKZ1LCIPR1lh/WidEKeNt6vW6IaM3a4FJAkFv/MFBK+mnKQGNT0MQXFfuCch eePa7Wj6xo
Bug#979823: marked as done (catch2: Needs source-only upload)
Your message dated Tue, 12 Jan 2021 07:33:16 +0100 with message-id <27ecbd49-0cd1-4a13-83b3-d92d8b155...@frost.de> and subject line Re: Bug#979823: catch2: diff for NMU version 2.13.4-1.1 has caused the Debian Bug report #979823, regarding catch2: Needs source-only upload 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.) -- 979823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:catch2 Version: 2.13.4-1 Severity: source Dear Maintainer, as the tracker says, catch2 needs a source-only upload to migrate to testing. (I maybe do an NMU targeting DELAYED/2 later) -- tobi --- End Message --- --- Begin Message --- Am 11. Januar 2021 21:48:47 MEZ schrieb Mathieu Mirmont : >On Mon, Jan 11, 2021 at 07:27:24PM +0100, Tobias Frost wrote: >>Dear maintainer, > >Hi Tobias, > >>I've prepared an NMU for catch2 (versioned as 2.13.4-1.1) and >>uploaded it to DELAYED/2. Please feel free to tell me if I >>should delay it longer. > >Thanks for fixing this! However I noticed a bug in version 2.13.4-1 and >I am preparing a new upload. We can keep the NMU, but the new upload >will render it moot. > >Cheers, thanks for takin care, Mathieu! closing this then -- cheers tobi--- End Message ---
Bug#960158: marked as done (libemail-mime-contenttype-perl: denial-of-service via OOM)
Your message dated Tue, 12 Jan 2021 06:18:19 + with message-id and subject line Bug#960158: fixed in libemail-mime-contenttype-perl 1.026-1 has caused the Debian Bug report #960158, regarding libemail-mime-contenttype-perl: denial-of-service via OOM 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.) -- 960158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libemail-mime-contenttype-perl Version: 1.022-1 Severity: important Tags: upstream, security It's possible to easily craft a message which triggers out-of-memory error. Upstream has been notified and working on the issue. --- End Message --- --- Begin Message --- Source: libemail-mime-contenttype-perl Source-Version: 1.026-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of libemail-mime-contenttype-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated libemail-mime-contenttype-perl 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, 12 Jan 2021 06:54:14 +0100 Source: libemail-mime-contenttype-perl Architecture: source Version: 1.026-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Salvatore Bonaccorso Closes: 960158 Changes: libemail-mime-contenttype-perl (1.026-1) unstable; urgency=medium . * Team upload. * Import upstream version 1.026. - Don't use more memory than necessary to store parts of an encoded parameter (Closes: #960158) * Declare compliance with Debian policy 4.5.1 Checksums-Sha1: e103e2b063eb67505007621b6327bfe800668712 2493 libemail-mime-contenttype-perl_1.026-1.dsc 3c7651b7c133f05eca52290ff712ecc5ad60469a 23063 libemail-mime-contenttype-perl_1.026.orig.tar.gz 92dd4916b7cf4fbc373565aee80fc733370e86d2 3116 libemail-mime-contenttype-perl_1.026-1.debian.tar.xz Checksums-Sha256: 929fe56a52ce8067ed6af76dafc08b52944c61d7e4d5dc1207ac714098331813 2493 libemail-mime-contenttype-perl_1.026-1.dsc 74491930b7a93b8e7fda812bf669eee66ec8b9519958e5b01dcf8ccf92a9507d 23063 libemail-mime-contenttype-perl_1.026.orig.tar.gz 464f920f1a37184db99c2b68dcb9321401ecba5205c1e3c16c6b97f8c5b0bf24 3116 libemail-mime-contenttype-perl_1.026-1.debian.tar.xz Files: 66995f3f55b8a84ecf7ab4c9db01bb4b 2493 perl optional libemail-mime-contenttype-perl_1.026-1.dsc f228124902edfd3c4518017117d7684a 23063 perl optional libemail-mime-contenttype-perl_1.026.orig.tar.gz f6fca50ef4e1d0ce51fd70fd980f182e 3116 perl optional libemail-mime-contenttype-perl_1.026-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl/9Oj9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EE8QP/20xzuGfsSD87hthOmVQ0lHXbUB3NMbR ofXJxTWM3N/8cAbCrE4puH5aK89yt1kGc5rccRmBBiSJRLQyw0FJ6CgbWyogTlYz uRjwwKL/uS2+pqltv8RmDg95ZbQvyp/dc91VjTtF/aoIfUJY0BebIG0NNODqaF3W XiWs/GCowvOPlX5WO43xh3cTE/XOlUQq1X+BnlQqxX/6C8ls0EtSLMkteoi1JCxj oVW2PnLvesLq9KHi4OMuQ7I8k4TL4VQsWvWAE8956TbnKjz4Nl7Z1jr7gQT29QOb gqvwpZ6G6D1BnotHCfVepdl0SP8KXgZQYwJ1DfVIMxeYhMyBYb7Ku35qy+gRN7FF qf7+TlmDz1NFkNoaP9Y94dV5zQvEQO/Lc9jZnvEubjFwy0mW9wlA/b3E5KuzYAlc 0wxzsZczETc81yYgIa+5ZJadEh5PTQpsCna1JQdGddSUlZxr/sShoXNa9zdF+42F fzv1XiZPQPV9UX4jF8UBEgBEXkTImLCg76xeh4h08r0hjbsZxwLMk8d2Nd9Zf0c1 hh0w9MuYl51qulR00S/EqLYP4UhMa0rYt7OGvyTUbZCLi7M1k2o2dBXPKoIRaOvH Fi3MqUJuRaRyuV5YizIopT+eTCzQLna8EeFmdXmR0ruKgB7uCQkfsiURwDkxDRZC RwJT6UcyI5dv =zhrL -END PGP SIGNATURE End Message ---
Bug#977655: marked as done (m2crypto: FTBFS with OpenSSL 1.1.1i)
Your message dated Tue, 12 Jan 2021 06:03:28 + with message-id and subject line Bug#954402: fixed in m2crypto 0.37.1-1 has caused the Debian Bug report #954402, regarding m2crypto: FTBFS with OpenSSL 1.1.1i 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.) -- 954402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: m2crypto Version: 0.36.0-1 Severity: serious Forwarded: https://gitlab.com/m2crypto/m2crypto/-/issues/289 Hi, m2crypto is failing to build since the 1.1.1i version of OpenSSL, see the upstream bug report for more details. Kurt --- End Message --- --- Begin Message --- Source: m2crypto Source-Version: 0.37.1-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of m2crypto, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated m2crypto package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 00:53:00 -0500 Source: m2crypto Architecture: source Version: 0.37.1-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 954402 Changes: m2crypto (0.37.1-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Sandro Tosi ] * New upstream release * Use the new Debian Python Team contact name and address * debian/copyright - extend packaging copyright years * debian/control - bump Standards-Version to 4.5.1 (no changes needed) - add parameterized to b-d, needed by tests * debian/patches/0001-import-inspect-in-urllib-2.patch - refresh patch * debian/patches/MR261.patch - fix compatibility with openssl/1.1.1i+; Closes: #954402 Checksums-Sha1: 685d70a8e5ee7cb03de6d5bee591fee7d97660a5 2334 m2crypto_0.37.1-1.dsc 7e7e74e5e7acf78371c3320e7141d68b3e385cf4 464528 m2crypto_0.37.1.orig.tar.xz 5610f331fa2f2fb359b18230d2e69e681b44c675 58908 m2crypto_0.37.1-1.debian.tar.xz 4f79eb520b3131efe667ab2f4a0365a29c87b91b 8275 m2crypto_0.37.1-1_source.buildinfo Checksums-Sha256: 10129e7e34d3b19df6cfffa594f801f902c5e8e0e0ac696db989b46c85541dc6 2334 m2crypto_0.37.1-1.dsc cc0ace6a3fe24e6d3ad78fe1eb507d67b74ae757b01c8c9651d268e67fd7b34c 464528 m2crypto_0.37.1.orig.tar.xz b7d6c575d349ec7738c225212b9bec456328334e372fe02bcc333ee35d7a185b 58908 m2crypto_0.37.1-1.debian.tar.xz 1a9e89abffa10605ddae3815d68a50d5a3e1c0d6d6e843bf975dbcafb471aedf 8275 m2crypto_0.37.1-1_source.buildinfo Files: 8c343ff5629302c2cfca41d34681398b 2334 python optional m2crypto_0.37.1-1.dsc 6205f08f2d61b6e87386b69caf6b2b47 464528 python optional m2crypto_0.37.1.orig.tar.xz 0236bbec39f8e18791da981c02e8e9ae 58908 python optional m2crypto_0.37.1-1.debian.tar.xz b903237a72913fe519a8215534d0b6f3 8275 python optional m2crypto_0.37.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl/9OVYACgkQh588mTgB qU8Jyw//XkEhAEf6kY1rM35WGe5Jpy/hDwq+zmnBwsNz3/uKRh3FUbrmvoBjZSgZ 4XJKbf/mwMth6S9YY5hYD4nqUX0SQuA456EdpJIhFbYyqFcmU/YvlFXp0sshLNea yPgxnWHnxPi+JZU/xpOu374Vv4XcWydhXjw7iLsiQ3wHnNzfqNMa5XHvwBEUkEHG JB6Lpn5TNFRsa1Xiei2u6h3gjBpBZmbaf67HrM34UmIoomuOpbe4fB8Y5lBk9+fx CMDJaOIfBfdctmyeot5fiS0jCE1U55L49ZZvILWocRps55eaWbdDuYLERTnP3Lfp vHQnsgnVRMTX35UXxELnMyS9+7h6tAS0nNf4GHYXlXNsjibvDEuGSh2qQR45iU/0 IDdcBgbzgbfWwaCLMqJfOVNNiQ1sFhQ6UVuT84y4BWBRoOOZH5nLB8STXByRmFyk GD/XVOEmvrLkq8vjMLap6ATpxvuoFR74dGDljm6GL7+rADWi9YD8y6P8fg1NZUhn dTXHJJ6c04WICdA8S19LkaVhqP/RxlRrhQiefIg8KOGFZBFV8O8MPrW7gaTbDEIC WuPFKbLIS+UGRLx6WIkJgQV1jUwtPAQdUeGQWJQ6/lXGfuc+1NO/d9wF8pqBVzak EJUB0IP8rmZmgF67yvlMarL5gKy04xr+X+NTUP+Sey5cZjPNANU= =gUcx -END PGP SIGNATURE End Message ---
Bug#977070: marked as done (m2crypto FTBFS with pytest 6)
Your message dated Tue, 12 Jan 2021 06:03:28 +
with message-id
and subject line Bug#954402: fixed in m2crypto 0.37.1-1
has caused the Debian Bug report #954402,
regarding m2crypto FTBFS with pytest 6
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.)
--
954402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: m2crypto
Version: 0.36.0-1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
m2crypto FTBFS with pytest 6 in experimental.
The error log below has more details.
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_m2crypto/build; python3.9 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> collected 302 items
>
> tests/test_aes.py [
> 1%]
> tests/test_asn1.py [
> 3%]
> tests/test_authcookie.py ... [
> 10%]
> tests/test_bio.py . [
> 10%]
> tests/test_bio_file.py ... [
> 12%]
> tests/test_bio_iobuf.py [
> 15%]
> tests/test_bio_membuf.py .. [
> 18%]
> tests/test_bio_ssl.py ...[
> 21%]
> tests/test_bn.py ... [
> 22%]
> tests/test_dh.py .. [
> 24%]
> tests/test_dsa.py ...[
> 27%]
> tests/test_ec_curves.py .. [
> 28%]
> tests/test_ecdh.py ... [
> 29%]
> tests/test_ecdsa.py ... [
> 31%]
> tests/test_engine.py .. [
> 33%]
> tests/test_err.py . [
> 34%]
> tests/test_evp.py [
> 42%]
> tests/test_obj.py .. [
> 44%]
> tests/test_rand.py ..[
> 46%]
> tests/test_rc4.py .. [
> 46%]
> tests/test_rsa.py .. [
> 55%]
> tests/test_smime.py .[
> 62%]
> tests/test_ssl.py ...s.FFF.F...s [
> 80%]
> ... [
> 81%]
> tests/test_ssl_offline.py . [
> 82%]
> tests/test_threading.py .. [
> 83%]
> tests/test_timeout.py ...[
> 88%]
> tests/test_util.py [
> 91%]
> tests/test_x509.py ...
> [100%]
>
> === FAILURES
> ===
> ___ MiscSSLClientTestCase.test_verify_cb_new
> ___
>
> self =
>
> def test_verify_cb_new(self):
> pid = self.start_server(self.args)
> try:
> ctx = SSL.Context()
> ctx.set_verify(SSL.verify_peer | SSL.verify_fail_if_no_peer_cert,
>9, self.verify_cb_new)
> s = SSL.Connection(ctx)
> try:
>> s.connect(self.srv_addr)
>
> tests/test_ssl.py:521:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self =
> addr = ('localhost', 43785)
>
> def connect(self, addr):
> # type: (util.AddrType) -> int
> """Overloading socket.connect()
>
> :param addr: addresses have various depending on their type
>
> :return:status of ssl_connect()
> """
> self.socket.connect(addr)
> self.addr = addr
> self.setup_ssl()
> self.set_connect_state()
>> ret = self.connect_ssl()
>
> M2Crypto/SSL/Connection.py:327:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#954402: marked as done (m2crypto: FTBFS since openssl 1.1.1e)
Your message dated Tue, 12 Jan 2021 06:03:28 +
with message-id
and subject line Bug#954402: fixed in m2crypto 0.37.1-1
has caused the Debian Bug report #954402,
regarding m2crypto: FTBFS since openssl 1.1.1e
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.)
--
954402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: m2crypto
Version: 0.31.0-9
Severity: serious
The package FTBFS since openssl has been updated to 1.1.1e because the
testsuite fails. The failure is due to commit db943f43a60d ("Detect EOF
while reading in libssl") [0] in openssl. There an issue ticket [1]
which introduced the changed behaviour.
[0] https://github.com/openssl/openssl/pull/10882
[1] https://github.com/openssl/openssl/issues/10880
Sebastian
--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.37.1-1
Done: Sandro Tosi
We believe that the bug you reported is fixed in the latest version of
m2crypto, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi (supplier of updated m2crypto package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Jan 2021 00:53:00 -0500
Source: m2crypto
Architecture: source
Version: 0.37.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi
Changed-By: Sandro Tosi
Closes: 954402
Changes:
m2crypto (0.37.1-1) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Sandro Tosi ]
* New upstream release
* Use the new Debian Python Team contact name and address
* debian/copyright
- extend packaging copyright years
* debian/control
- bump Standards-Version to 4.5.1 (no changes needed)
- add parameterized to b-d, needed by tests
* debian/patches/0001-import-inspect-in-urllib-2.patch
- refresh patch
* debian/patches/MR261.patch
- fix compatibility with openssl/1.1.1i+; Closes: #954402
Checksums-Sha1:
685d70a8e5ee7cb03de6d5bee591fee7d97660a5 2334 m2crypto_0.37.1-1.dsc
7e7e74e5e7acf78371c3320e7141d68b3e385cf4 464528 m2crypto_0.37.1.orig.tar.xz
5610f331fa2f2fb359b18230d2e69e681b44c675 58908 m2crypto_0.37.1-1.debian.tar.xz
4f79eb520b3131efe667ab2f4a0365a29c87b91b 8275
m2crypto_0.37.1-1_source.buildinfo
Checksums-Sha256:
10129e7e34d3b19df6cfffa594f801f902c5e8e0e0ac696db989b46c85541dc6 2334
m2crypto_0.37.1-1.dsc
cc0ace6a3fe24e6d3ad78fe1eb507d67b74ae757b01c8c9651d268e67fd7b34c 464528
m2crypto_0.37.1.orig.tar.xz
b7d6c575d349ec7738c225212b9bec456328334e372fe02bcc333ee35d7a185b 58908
m2crypto_0.37.1-1.debian.tar.xz
1a9e89abffa10605ddae3815d68a50d5a3e1c0d6d6e843bf975dbcafb471aedf 8275
m2crypto_0.37.1-1_source.buildinfo
Files:
8c343ff5629302c2cfca41d34681398b 2334 python optional m2crypto_0.37.1-1.dsc
6205f08f2d61b6e87386b69caf6b2b47 464528 python optional
m2crypto_0.37.1.orig.tar.xz
0236bbec39f8e18791da981c02e8e9ae 58908 python optional
m2crypto_0.37.1-1.debian.tar.xz
b903237a72913fe519a8215534d0b6f3 8275 python optional
m2crypto_0.37.1-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl/9OVYACgkQh588mTgB
qU8Jyw//XkEhAEf6kY1rM35WGe5Jpy/hDwq+zmnBwsNz3/uKRh3FUbrmvoBjZSgZ
4XJKbf/mwMth6S9YY5hYD4nqUX0SQuA456EdpJIhFbYyqFcmU/YvlFXp0sshLNea
yPgxnWHnxPi+JZU/xpOu374Vv4XcWydhXjw7iLsiQ3wHnNzfqNMa5XHvwBEUkEHG
JB6Lpn5TNFRsa1Xiei2u6h3gjBpBZmbaf67HrM34UmIoomuOpbe4fB8Y5lBk9+fx
CMDJaOIfBfdctmyeot5fiS0jCE1U55L49ZZvILWocRps55eaWbdDuYLERTnP3Lfp
vHQnsgnVRMTX35UXxELnMyS9+7h6tAS0nNf4GHYXlXNsjibvDEuGSh2qQR45iU/0
IDdcBgbzgbfWwaCLMqJfOVNNiQ1sFhQ6UVuT84y4BWBRoOOZH5nLB8STXByRmFyk
GD/XVOEmvrLkq8vjMLap6ATpxvuoFR74dGDljm6GL7+rADWi9YD8y6P8fg1NZUhn
dTXHJJ6c04WICdA8S19LkaVhqP/RxlRrhQiefIg8KOGFZBFV8O8MPrW7gaTbDEIC
WuPFKbLIS+UGRLx6WIkJgQV1jUwtPAQdUeGQWJQ6/lXGfuc+1NO/d9wF8pqBVzak
EJUB0IP8rmZmgF67yvlMarL5gKy04xr+X+NTUP+Sey5cZjPNANU=
=gUcx
-END PGP SIGNATURE End Message ---
Bug#969983: marked as done (Updating the netsniff-ng Uploaders list)
Your message dated Tue, 12 Jan 2021 04:04:35 + with message-id and subject line Bug#969983: fixed in netsniff-ng 0.6.8-2 has caused the Debian Bug report #969983, regarding Updating the netsniff-ng Uploaders list 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.) -- 969983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netsniff-ng Version: 0.6.5-1 0.6.6-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Tobias Klauser wishes no longer to be uploader of netsniff-ng. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: netsniff-ng Source-Version: 0.6.8-2 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of netsniff-ng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated netsniff-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 09:11:58 +0530 Source: netsniff-ng Architecture: source Version: 0.6.8-2 Distribution: unstable Urgency: medium Maintainer: Daniel Borkmann Changed-By: Kartik Mistry Closes: 969983 Changes: netsniff-ng (0.6.8-2) unstable; urgency=medium . * debian/control: + Updated Uploaders as per MIA team request (Closes: #969983) Checksums-Sha1: 5365570ca9ee0e9108be2f3c4c465580d642db96 2381 netsniff-ng_0.6.8-2.dsc 765e5dcb853b74535f25e4a2af9aa5089a9a51bd 7160 netsniff-ng_0.6.8-2.debian.tar.xz Checksums-Sha256: f1631376cd86db3207c59fafee42080a10e68c715984a9560f89b1a86ad09f64 2381 netsniff-ng_0.6.8-2.dsc 313fbd53ef90199b3264b17b0049b38a48478f0e6acc19cad1bbf0d017ac91b5 7160 netsniff-ng_0.6.8-2.debian.tar.xz Files: ef5cb51ebfa190e6f83aaff76ade5957 2381 net optional netsniff-ng_0.6.8-2.dsc b0f9e62c4580d4f37f0defe30452a8b2 7160 net optional netsniff-ng_0.6.8-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl/9G1UACgkQAsHT8ng6 pN4wQhAA1JZsyn1yxX/RPiVRmHIRObMAvVA3IQ0aIgYwnGhlFbP4lkQAKtgpEuoL iXzzkcpDOm9UWjKzgL12YClmuFFlMJiuvJU/B81okSjZMG/2cH9jwzi4aH9LjFDy s054S14DSk8CDagh4rFi+4sjgyy3Rn2c+jRV9E0s9Cr4tb9JkFbVj7NJECIb/lFs bwlyTPptvRA3/WfUnRBunCK7DUKB0U2Nf10XSmGEvm9ISPdrmdtUCG7hWl5Rgi4C MH5ABdllykKcyH+i0j/9Lb+2/ZKtZJBCJXHDAugTsW6ixiOPWTqkxf9fk/rvCsLj HhMU7k+MZtMSaUMi2KEHmTX4k8F2TTP37IfbS6MLxwOZN8MjT/mVRxUJ5iRJe9A5 9V+ZmlKMi8n5YUVOnK3levQMtEIL2z4Y1JZ3pAZTG3vyRpNQwJ2cDbvfn6jGQAGT ccamO61YQB7SPNSTxRzMR8uslPcveppgD11WHD8C89cV6etiqCqSLb50m4Y5CrYs Tkuzn7E8rpWFMknVylLnT4AYHHx21g/gLCabTXd0N8Qo/EHhqk04vBZvlZbHtAzQ BsLEC1tRuwvQ7oOh4wIjoVm8Kbqj7xGPEBQZLO+/RX7x1LdmhATkKO1C2mSeDYR3 7tTumNQkg29DIJe4VSs9XDclLMQSKHlgfyAJR4iOapVYoIYDPaQ= =diBh -END PGP SIGNATURE End Message ---
Bug#969859: marked as done (python-mido: autopkgtest should be marked superficial)
Your message dated Tue, 12 Jan 2021 03:18:38 + with message-id and subject line Bug#969859: fixed in python-mido 1.2.9-3 has caused the Debian Bug report #969859, regarding python-mido: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-mido Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'python-mido' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'python-mido'. -- Sudip --- End Message --- --- Begin Message --- Source: python-mido Source-Version: 1.2.9-3 Done: Josue Ortega We believe that the bug you reported is fixed in the latest version of python-mido, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated python-mido 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, 11 Jan 2021 19:40:09 -0600 Source: python-mido Architecture: source Version: 1.2.9-3 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Closes: 969859 Changes: python-mido (1.2.9-3) unstable; urgency=medium . * Add autopkgtest runtime test in order to drop the previous supercial test. Closes: #969859 * debian/control: Document Rules-Requires-Root as 'no' * debian/watch: Bump file standard version to 4 * Bump debhelper-compat to use (=13) * Bump Standards-Version to 4.5.1. No changes required * debian/patches/*.patch: Document Forwarded field Checksums-Sha1: fd7b9e4f99a7541555ad5de4c00ee588e03b1fe0 1971 python-mido_1.2.9-3.dsc 49801920280cbdae6329d0435c630f0518eb27e0 4556 python-mido_1.2.9-3.debian.tar.xz 78808461af6e911d55fc24ad7564b221c02ba863 6638 python-mido_1.2.9-3_amd64.buildinfo Checksums-Sha256: 859f2829aaf6465e2850215dea48723cefeae1a07710fc0859807601572ec3a9 1971 python-mido_1.2.9-3.dsc e144c27d124bbdb992ad69c9e313d123f0baae126849804f1bd902d036b26b26 4556 python-mido_1.2.9-3.debian.tar.xz 7fd331bf0f55ad187cdcd05853e5c5d2708a73d60920dbb9e1053d7b1e7bea8f 6638 python-mido_1.2.9-3_amd64.buildinfo Files: abaff102dbcbefa60ef3b79ab915e366 1971 python optional python-mido_1.2.9-3.dsc 962b57219b2adc8bdaa9b148d9da3653 4556 python optional python-mido_1.2.9-3.debian.tar.xz 48986ed5908732a5d6ed3b43a1bcee57 6638 python optional python-mido_1.2.9-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl/9ELURHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T9bLRAArnsQfvuGuGthjpXpHluHkKBszqwIGTqH wRAKIOm7QP7am1Jtoc9lGOamxEq0XXEWq0nPShrJ/dqWWALDrUfNwcATbjRpGNOW 2VihYU2nK/Hbm3l2VmwztWdUsz43uKWE09SPUJQBHFDafHyssD8oOAowrESD2X/u XGkxOFApwbbPjvP31AcVPh38xwigMSDsZzXeTK/cqDgW4yuUqEt1nboaDTH2qqu6 ZYSCf7mwEs50MlHgchiBVcaqt+nPn4U/03+Qd8493LrTxK+ly6aoMbVzrhBu4O9f PV+JJE9pHFNmJLUFZOPPj4IM1KX/MobN/X3mFwTv2mVlRROSauoqNx6QN8AQLElR DOJ+8eP2rcv7715E7zZtGvesp4PEaFZp73M40sDO+rKO2dIDtPQYA5OjvFtOVNVA 0xfVMJMrlPBPmbwYjGm/TnE/n8RYjAP99AL7WXiTpeRm/K1UaAabThPWjLFs4r/y v+1al2uGj0WRyU4088jcy4zc+KA2RTcJsCujqj2dw6LDzjMyglydogI3k+Ec+QYY l/PYsZgA58XIdbyli0YiTTXAcfduxkyuYEXxPIXNDOEOhVUYiMfrMmt6k+y88Pcc XUxHm6dmsnhvdiSoJWeJdwI4fRp49bO3LKeJ28SiJbNtUE25qKCNZ+ST2W3SVHVK BGrIa6dKmTQ= =5mqm -END PGP SIGNATURE End Message
Bug#979288: marked as done (ffc autopkgtests fail with pytest 6)
Your message dated Tue, 12 Jan 2021 02:33:40 + with message-id and subject line Bug#979288: fixed in ffc 2019.2.0~git20200123.6b621eb-4 has caused the Debian Bug report #979288, regarding ffc autopkgtests fail with pytest 6 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.) -- 979288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ffc Version: 2019.2.0~git20200123.6b621eb-3 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, ffc autopkgtests with pytest 6 in unstable because it uses a deprecated feature that will be removed soon, and that, by default, considered an error in pytest 6. The fragment of the CI the error log below has more details. > ERRORS > > ERROR collecting test session > _ > /usr/lib/python3.9/importlib/__init__.py:127: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > :1030: in _gcd_import > ??? > :1007: in _find_and_load > ??? > :986: in _find_and_load_unlocked > ??? > :680: in _load_unlocked > ??? > /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:170: in > exec_module > exec(co, module.__dict__) > uflacs/crosslanguage/conftest.py:234: in > ??? > /usr/lib/python3/dist-packages/_pytest/fixtures.py:1358: in fixture > warnings.warn(FIXTURE_POSITIONAL_ARGUMENTS, stacklevel=2) > E pytest.PytestDeprecationWarning: Passing arguments to pytest.fixture() as > positional arguments is deprecated - pass them as a keyword argument instead. > === short test summary info > > ERROR .. - pytest.PytestDeprecationWarning: Passing arguments to > pytest.fixtu... > Interrupted: 1 error during collection > > === 1 error in 0.42s > === --- End Message --- --- Begin Message --- Source: ffc Source-Version: 2019.2.0~git20200123.6b621eb-4 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of ffc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated ffc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 13:01:32 +1100 Source: ffc Architecture: source Version: 2019.2.0~git20200123.6b621eb-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 979288 Changes: ffc (2019.2.0~git20200123.6b621eb-4) unstable; urgency=medium . * Standards-Version: 4.5.1 * debian patch fix_pytest6_fixtures.patch fixes the fixture signature for pytest6 (arguments must now be provided by keyname) Closes: #979288. * remove deprecated lintian overrides Checksums-Sha1: 552e1018a75d6add61b60901f197e1c5888a3991 2278 ffc_2019.2.0~git20200123.6b621eb-4.dsc 09094f83ad27dd578a3f5d01760cc1d3ecceb2ec 9776 ffc_2019.2.0~git20200123.6b621eb-4.debian.tar.xz Checksums-Sha256: 85635edaae0867632b604e15cf06e2e7190d3003d37e7b32b24d7d9ffeaff789 2278 ffc_2019.2.0~git20200123.6b621eb-4.dsc 636139e424034ea30e87432b9363b7170ab62498ceed5f6b7a45d61ef81047c6 9776 ffc_2019.2.0~git20200123.6b621eb-4.debian.tar.xz Files: 3c664935d7ae73dbe256eda6dcb7623e 2278 python optional ffc_2019.2.0~git20200123.6b621eb-4.dsc 09fb9fadb9aa085c41301e868a832a9a 9776 python optional ffc_2019.2.0~git20200123.6b621eb-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl/9BDcACgkQVz7x5L1a AfrxYw//cnZF6Ym2+VPksYfYTGFeii8bu5bzNR3PukC0vGPxnRQhHL2adCnLHJGf t5SBKeUhJ1svVaBsiKdrB14vwSG8kE9Atn4ngkceL703klA3tpxMheUmiuAV8q/7 ITqJI14n0C4cD2iWXAU1x4XUCwO0RkMdEVXFPqlW20LQ7izI/9UlDLy2awr/2psx yfx1Ryvh/V4d6s5ynDB2gUnwfilTxxgwxVIAOPCs1XurfEgqbpj9HcHJlmww04JI EMKkGEQ4wSpwHFNwvDd1xLBIGE81xJVIeXbMx9lnDxBIDZulBewKhoNxim8wYr0N ar+lXeqjh81EsEaTDVfBmcPxUlDKAgtCs8o9u648NtTJsa5ObRuFpBxRL/89ltEp ToZgf
Bug#925669: marked as done (dewalls: ftbfs with GCC-9)
Your message dated Tue, 12 Jan 2021 02:23:10 + with message-id and subject line Bug#925669: fixed in dewalls 1.0.0+ds1-8 has caused the Debian Bug report #925669, regarding dewalls: ftbfs with GCC-9 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.) -- 925669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dewalls Version: 1.0.0+ds1-7 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/dewalls_1.0.0+ds1-7_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5ServiceSupport.prl' for module 'QtServiceSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5LinuxAccessibilitySupport.prl' for module 'QtLinuxAccessibilitySupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5VulkanSupport.prl' for module 'QtVulkanSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5Bootstrap.prl' for module 'QtBootstrap' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5KmsSupport.prl' for module 'QtKmsSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5GlxSupport.prl' for module 'QtGlxSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5AccessibilitySupport.prl' for module 'QtAccessibilitySupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5EventDispatcherSupport.prl' for module 'QtEventDispatcherSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5FbSupport.prl' for module 'QtFbSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Could not open prl file '/usr/lib/x86_64-linux-gnu/libQt5PlatformCompositorSupport.prl' for module 'QtPlatformCompositorSupport' (No such file or directory), and failed to deduce the library file path. This module will likely not be usable by qbs. Creating profile 'deb'. Setting profile 'gcc' as the base profile for this profile. # choose gcc as if clang is installed too you have to pick one qbs config --settings-dir /tmp profiles.deb.baseProfile gcc qbs config --settings-dir /tmp profiles.deb.qbs.installPrefix 'usr/' qbs config --settings-dir /tmp profiles.deb.cpp.debugInformation true qbs config --settings-dir /tmp profiles.deb.cpp.
Bug#955567: marked as done (kalgebra: Output is always blank)
Your message dated Tue, 12 Jan 2021 10:58:09 +0900 with message-id and subject line Re: Bug#955567: kalgebra: Output is always blank has caused the Debian Bug report #955567, regarding kalgebra: Output is always blank 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.) -- 955567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kalgebra Version: 4:17.08.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, KAlgebra shows nothing in its output screen. This only applies to the algebraic displays, the graphs and dictionary tabs seem to work fine. Reproduce: Enter any equation into the input text box and press enter. Expected: The result of the equation and the equation inputted should be visible. Actual: Nothing appears. Even the border of the frame appears missing. Also: Right clicking on the empty area causes a context menu to appear in the wrong place. I'm not sure if that's related. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kalgebra depends on: ii kalgebra-common 4:17.08.3-2 ii kio 5.54.1-1 ii libanalitza8 4:17.08.3-2+b3 ii libanalitzagui8 4:17.08.3-2+b3 ii libanalitzaplot8 4:17.08.3-2+b3 ii libanalitzawidgets8 4:17.08.3-2+b3 ii libc62.28-10 ii libkf5configcore55.54.0-1+deb10u1 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5gui5 5.11.3+dfsg1-1+deb10u3 ii libqt5webenginewidgets5 5.11.3+dfsg-2+deb10u1 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libreadline7 7.0-5 ii libstdc++6 8.3.0-6 kalgebra recommends no packages. kalgebra suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 4:20.12.1-1 Hi Charles, I don't know really which version it fixed it between 17.08 and current 20.12, but I close this bug as fixed at least in 20.12.1, since I cannot reproduce it anyway. If you can reproduce it with current version (20.12.1), then please reopen. Thanks Norbert On Thu, 02 Apr 2020, Charles Samuels wrote: > Version: 4:17.08.3-2 -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#968281: marked as done (I cannot export alarms in Kalarm)
Your message dated Tue, 12 Jan 2021 10:51:40 +0900 with message-id and subject line Re: Bug#968281: I cannot export alarms in Kalarm has caused the Debian Bug report #968281, regarding I cannot export alarms in Kalarm 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.) -- 968281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kalarm Version: 4:16.04.3-4~deb9u1 Severity: serious Tags: d-i I use only Xfce desktop. To install Kalarm I need to install the following additional dependencies: plasma-workspace and kdepim-runtime. Kalarm works well, except I cannot export selected alarms. Is some dependency missing? What is the dependency? Even I installed KDE, but it was the same - I was unable to export alarms. In Debian 10, the package Kalarm also lacks some dependencies. -- System Information: Debian Release: 9.13 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-13-amd64 (SMP w/2 CPU cores) Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.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) Versions of packages kalarm depends on: ii kf5-kdepimlibs-kio-plugins 4:16.04.2-2 ii kio 5.28.0-2 ii libc6 2.24-11+deb9u4 ii libgcc1 1:6.3.0-18+deb9u1 ii libkf5akonadicontact5 4:16.04.2-2 ii libkf5akonadicore5 4:16.04.3-4 ii libkf5akonadimime5 4:16.04.2-2 ii libkf5akonadiwidgets5 4:16.04.3-4 ii libkf5alarmcalendar516.04.2-2 ii libkf5auth5 5.28.0-2+deb9u1 ii libkf5calendarcore5 4:16.04.2-1 ii libkf5calendarutils516.04.3-1 ii libkf5codecs5 5.28.0-1+b2 ii libkf5completion5 5.28.0-1 ii libkf5configcore5 5.28.0-2+deb9u1 ii libkf5configgui55.28.0-2+deb9u1 ii libkf5configwidgets55.28.0-2 ii libkf5contacts5 16.04.2-1 ii libkf5coreaddons5 5.28.0-2 ii libkf5dbusaddons5 5.28.0-1 ii libkf5guiaddons55.28.0-1 ii libkf5holidays5 16.04.2-1 ii libkf5i18n5 5.28.0-2 ii libkf5iconthemes5 5.28.0-2 ii libkf5identitymanagement5 16.04.2-1 ii libkf5itemmodels5 5.28.0-2 ii libkf5jobwidgets5 5.28.0-2 ii libkf5kdelibs4support5 5.28.0-1 ii libkf5kiocore5 5.28.0-2 ii libkf5kiofilewidgets5 5.28.0-2 ii libkf5kiowidgets5 5.28.0-2 ii libkf5libkdepim-plugins 4:16.04.2-3 ii libkf5libkdepim54:16.04.2-3 ii libkf5mailtransport516.04.2-3 ii libkf5mime5 16.04.2-1 ii libkf5notifications55.28.0-1 ii libkf5pimcommon-plugins 4:16.04.2-2 ii libkf5pimcommon54:16.04.2-2 ii libkf5pimtextedit5 16.04.2-1 ii libkf5service-bin 5.28.0-1 ii libkf5service5 5.28.0-1 ii libkf5textwidgets5 5.28.0-1 ii libkf5widgetsaddons55.28.0-3 ii libkf5windowsystem5 5.28.0-2 ii libkf5xmlgui5 5.28.0-1 ii libphonon4qt5-4 4:4.9.0-4 ii libqt5core5a5.7.1+dfsg-3+deb9u2 ii libqt5dbus5 5.7.1+dfsg-3+deb9u2 ii libqt5gui5 5.7.1+dfsg-3+deb9u2 ii libqt5network5 5.7.1+dfsg-3+deb9u2 ii libqt5widgets5 5.7.1+dfsg-3+deb9u2 ii libstdc++6 6.3.0-18+deb9u1 ii perl5.24.1-3+deb9u7 ii phonon4qt5 4:4.9.0-4 kalarm recommends no packages. Versions of packages kalarm suggests: pn jovie -- no debconf information --- End Message --- --- Begin Message --- Version: 4:17.08.3-1 All the below is fixed in either newer upstream versions or the current Debian packaging. Closing it with some version back in time. Thanks David for reporting the upstream bug and fix. Best Norbert On Wed, 12 Aug 2020, Luis Duarte wrote: > Version: 4:16.04.3-4~deb9u1 > I use only Xfce desktop. To install Kalarm I need to install the following > additional dependencies: plasma-workspace and kdepim-runtime. Kalarm works > well, except I cannot export selected alarms. Is some dependency missing? What > is the dependency? > > Even I installed KDE, but it was the same - I was unable to export alarms. > > In Debian 10, the package Kalarm also lacks some dependencies. On Wed, 12 Aug 2020, David Jarvie wrote: > This bug description looks like htt
Bug#979734: marked as done (calibre: remove python3-crypto from (Build-)Depends)
Your message dated Tue, 12 Jan 2021 01:33:29 + with message-id and subject line Bug#979734: fixed in calibre 5.9.0+dfsg-3 has caused the Debian Bug report #979734, regarding calibre: remove python3-crypto from (Build-)Depends 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.) -- 979734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calibre Version: 5.8.1+dfsg+fontFix-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 972184 by -1 Control: block 979318 by -1 We will remove python3-crypto from bullseye. It is unmaintained and a replacement is available via python3-pycryptodome. calibre only uses any module from python3-crypto in src/calibre/test_build.py to check if is installed. No other code in calibre uses python3-crypto. So I recommend to simply remove this check and drop the dependencies. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: calibre Source-Version: 5.9.0+dfsg-3 Done: YOKOTA Hiroshi We believe that the bug you reported is fixed in the latest version of calibre, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YOKOTA Hiroshi (supplier of updated calibre 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, 12 Jan 2021 09:49:49 +0900 Source: calibre Architecture: source Version: 5.9.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Calibre maintainer team Changed-By: YOKOTA Hiroshi Closes: 979734 Changes: calibre (5.9.0+dfsg-3) unstable; urgency=medium . [ Norbert Preining ] * Remove one more appearance of python3-crypto (Closes: #979734) Checksums-Sha1: c7a24c586b19c34b5cf97ff30d4b6f6bc60fa2c9 3325 calibre_5.9.0+dfsg-3.dsc eb02e0605f3e388f9c894e72cbd0760ced38ecd7 4411420 calibre_5.9.0+dfsg-3.debian.tar.xz 0c937dc4503d5a9a190739fc76e55f5db85d5990 19749 calibre_5.9.0+dfsg-3_source.buildinfo Checksums-Sha256: 643ba8955a954054665a567b148c0370aa8eb2f1278226df75f0c44c4ef1a0bb 3325 calibre_5.9.0+dfsg-3.dsc fb77606bb0ed2447d444dff35daab4568a21dc4ddb85f2c80051c24159875796 4411420 calibre_5.9.0+dfsg-3.debian.tar.xz 53b4b2646f71576ed79fd8c5cf50c3aa23e9d3acc589938710a4e0d25b03 19749 calibre_5.9.0+dfsg-3_source.buildinfo Files: 648c71d0e8da27ecb45b93c74432cae5 3325 text optional calibre_5.9.0+dfsg-3.dsc 7054d49de829a9325f54066d617a9aab 4411420 text optional calibre_5.9.0+dfsg-3.debian.tar.xz 858f2cac21aaa94361b0d30dab08570c 19749 text optional calibre_5.9.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEErjlfKHqxT11VFyPEqem2T5LebcoFAl/89/oWHHlva290YS5o Z21sQGdtYWlsLmNvbQAKCRCp6bZPkt5tyoXoD/9VSn2QgNEF4dEnOt2hZAkTZNFC aPcrVVTlHMbiZJRx/MNpEXDn8ErTw8LyERYJxGe0+9pcFKDNqeHAC0Ea3tZRvc9i qX0HnCBMkA6gkt6wrnjR8X9E2ijZ+hFVtJiCjRBmEEWNNdSZJYG9nsoy+g3FLvCy MYDjCMJKHimqILXNwZyxZh5aFq7CyMRZZYha4KdpAdxGtNzjg6lzaBqTCv9kLDi+ 87QdsmLO7mbFOJ/iIpD9Bo2eku0BT6LyPTA6GehUfu9nxGDkTScLKa1WOaqfsvE7 cjsHdQtrUwnBZCCaLItgxB1RIaQVq5h7i6GqP8CtCn5y6gbc3zB1GCNLqcbb9VNs EgrckERQquvdohDDNTBnSqUMFOvbffdmuMn8jMsS9WCy5oh5aGbkWSdAh2WzjTPJ 3UCdgSruPlSB01A6///n9N/1Uy/zbE22x7r4Ncmz3d8pYvsWdMscyQ0KgWH/IJC4 zQI3WNADEAytoYua5BH8y+zO8zyQCz7hR5V0qCDMjw91lAq7GoLYswjTvYknT8MU qBjfCAykrhfgsevg1i3z7XBHDvNjewaPiaJVkXjrs3W2jPis/5wEXx8zm7j6Gi4k S39dsqwQ7jstfqEd3V23sh+MTJWlpbmD/mEy+Ho6AvmeaL/6m4hPbit4fXKD+Tov RRbBGAgHFFqi2oIMMg== =OEWH -END PGP SIGNATURE End Message ---
Bug#979290: marked as done (pytest-mpi autopkgtests fail with pytest 6)
Your message dated Tue, 12 Jan 2021 01:21:12 + with message-id and subject line Bug#979290: fixed in pytest-mpi 0.4-3 has caused the Debian Bug report #979290, regarding pytest-mpi autopkgtests fail with pytest 6 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.) -- 979290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-mpi Version: 0.4-2 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, pytest-mpi autopkgtests fail with pytest 6 in unstable. From the CI log below, for some reason, the test gets aborted at some point: > Testing with python3.9: > = test session starts > == > platform linux -- Python 3.9.1, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 > rootdir: /tmp/autopkgtest.zQV9kC/build.XJA/src > plugins: mpi-0+unknown > collected 13 items > > docs/markers.rst . [ > 7%] > docs/usage.rst ..[ > 23%] > tests/test_fixtures.py ... [ > 46%] > tests/test_markers.py .FF..Fatal Python error: Aborted > > Current thread 0x7fa7514af740 (most recent call first): > File "/usr/lib/python3.9/subprocess.py", line 1752 in _execute_child > File "/usr/lib/python3.9/subprocess.py", line 947 in __init__ > File "/usr/lib/python3/dist-packages/_pytest/pytester.py", line 1193 in > popen > File "/usr/lib/python3/dist-packages/_pytest/pytester.py", line 1234 in run > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/conftest.py", line 44 in > runpytest_subprocess > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/conftest.py", line 52 in > runpytest > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/test_markers.py", line > 113 in test_mpi_xfail_under_mpi > File "/usr/lib/python3/dist-packages/_pytest/python.py", line 180 in > pytest_pyfunc_call > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1570 in > runtest > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 153 in > pytest_runtest_call > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 247 in > > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 294 in > from_call > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 246 in > call_runtest_hook > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 207 in > call_and_report > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 117 in > runtestprotocol > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 100 in > pytest_runtest_protocol > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 321 in > pytest_runtestloop > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 296 in _main > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 240 in > wrap_session > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 289 in > pytest_cmdline_main > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy
Bug#975817: marked as done (mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Tue, 12 Jan 2021 01:04:17 + with message-id and subject line Bug#975817: fixed in mom 0.6.0-2 has caused the Debian Bug report #975817, regarding mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 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.) -- 975817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mom Version: 0.6.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/tests' > srcdir="." "./run_tests_local.sh" "."/*.py > nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] > testMultiplePolicies (GeneralTests.ConfigTests) ... ERROR > testMultiplePolicies (GeneralTests.GeneralTests) ... ERROR > testPolicyAPI (GeneralTests.GeneralTests) ... ERROR > testQuery (GeneralTests.GeneralTests) ... ERROR > testBigNumbersInStats (GeneralTests.RpcTests) ... ok > test_get (OptionalTests.OptionalTests) ... ok > test_get_default (OptionalTests.OptionalTests) ... ok > test_get_default_item (OptionalTests.OptionalTests) ... ok > test_item (OptionalTests.OptionalTests) ... ok > test_iter (OptionalTests.OptionalTests) ... ok > test_map (OptionalTests.OptionalTests) ... ok > test_missing (OptionalTests.OptionalTests) ... ok > test_missing_else (OptionalTests.OptionalTests) ... ok > test_missing_get (OptionalTests.OptionalTests) ... ok > test_missing_item (OptionalTests.OptionalTests) ... ok > test_missing_iter (OptionalTests.OptionalTests) ... ok > test_missing_map (OptionalTests.OptionalTests) ... ok > test_missing_none (OptionalTests.OptionalTests) ... ok > test_missing_raise (OptionalTests.OptionalTests) ... ok > test_raise (OptionalTests.OptionalTests) ... ok > test_value (OptionalTests.OptionalTests) ... ok > test_bad_arity (ParserTests.TestEval) ... 2020-11-25 16:35:11,097 - mom - > ERROR - Unable to import hypervisor interface: libvirt > ok > test_bad_arity_def (ParserTests.TestEval) ... 2020-11-25 16:35:11,097 - mom - > ERROR - Unable to import hypervisor interface: libvirt > ok > test_bad_syntax_number (ParserTests.TestEval) ... ok > test_basic_math (ParserTests.TestEval) ... 2020-11-25 16:35:11,097 - mom - > ERROR - Unable to import hypervisor interface: libvirt > ok > test_comments (ParserTests.TestEval) ... ok > test_compare (ParserTests.TestEval) ... ok > test_debug (ParserTests.TestEval) ... ok > test_entities (ParserTests.TestEval) ... ok > test_entity_write (ParserTests.TestEval) ... ok > test_extended_logic (ParserTests.TestEval) ... ok > test_externals (ParserTests.TestEval) ... ok > test_funcs (ParserTests.TestEval) ... Exception in thread Thread-3: > Traceback (most recent call last): > File "/usr/lib/python3.9/threading.py", line 950, in _bootstrap_inner > ok > test_if (ParserTests.TestEval) ... ok > test_let (ParserTests.TestEval) ... ok > test_logic (ParserTests.TestEval) ... ok > test_minmax (ParserTests.TestEval) ... self.run() > File "/usr/lib/python3.9/threading.py", line 888, in run > ok > test_multi_statements (ParserTests.TestEval) ... ok > test_multi_statements_lisp (ParserTests.TestEval) ... ok > test_multiple_defvar (ParserTests.TestEval) ... ok > test_nil_attribute (ParserTests.TestEval) ... ok > test_not_enough_arguments (ParserTests.TestEval) ... > self._target(*self._args, **self._kwargs) > File "/<>/mom/__init__.py", line 68, in run > ok > test_not_null (ParserTests.TestEval) ... 2020-11-25 16:35:11,151 - mom - > ERROR - Unable to import hypervisor interface: libvirt > ok > test_null (ParserTests.TestEval) ... 2020-11-25 16:35:11,151 - mom - ERROR - > Unable to import hypervisor interface: libvirt > ok > test_parse_error (ParserTests.TestEval) ... ok > test_scope (ParserTests.TestEval) ... self._wait_for_thread(rpc_server, 5) > ok > test_setq (ParserTests.TestEval) ... ok > test_string (ParserTests.TestEval) ... File > "/<>/mom/__init__.py", line 225, in _wait_for_thread > ok > test_syntax_error (ParserTests.TestEval) ... ok > test_valid (ParserTests.TestEval) ... ok > test_valid_nil_attribute (ParserTests.TestEval) ... ok > test_vars (ParserTests.TestEval) ... 2020-11-25 16:35:11,151 - mom - ERROR - > Unable to import hypervisor interface: libvirt > ok > test_whitespace (ParserTests.TestEval) ... if t.isAlive(): > AttributeError: 'RPCServer' object has no attribute 'isAlive' > ok > test_with
Bug#964717: marked as done (cpio: Please make another source-only upload for testing migration)
Your message dated Mon, 11 Jan 2021 19:48:13 -0500 with message-id <14d3bf3c9fa87ac725613385663fac352f0ab73c.ca...@debian.org> and subject line Re: cpio: Please make another source-only upload for testing migration has caused the Debian Bug report #964717, regarding cpio: Please make another source-only upload for testing migration 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.) -- 964717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cpio Version: 2.13+dfsg-3 Severity: important Tags: sid Dear Debian cpio maintainers, The latest upload cpio/2.13+dfsg-3 was not a source-only upload and contains an arch:all package. As a result, this version will not migrate to Debian Testing. Please make another source-only upload to allow testing migration. For details, please see https://wiki.debian.org/SourceOnlyUpload . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 2.13+dfsg-4 On Thu, 09 Jul 2020 09:30:22 -0400 Boyuan Yang wrote: > Source: cpio > Version: 2.13+dfsg-3 > Severity: important > Tags: sid > > Dear Debian cpio maintainers, > > The latest upload cpio/2.13+dfsg-3 was not a source-only upload and > contains an arch:all package. As a result, this version will not > migrate to Debian Testing. > > Please make another source-only upload to allow testing migration. For > details, please see https://wiki.debian.org/SourceOnlyUpload . This bug is fixed in the latest upload. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#911523: marked as done (kbibtex: Translations not included in the binary package)
Your message dated Tue, 12 Jan 2021 00:34:07 + with message-id and subject line Bug#911523: fixed in kbibtex 0.9.90-1 has caused the Debian Bug report #911523, regarding kbibtex: Translations not included in the binary package 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.) -- 911523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kbibtex Version: 0.8.1-1 Severity: normal Tags: l10n Dear Maintainer, the kbibtex binary package does not contain the translations for both the program and the documentation. While the kbibtex git snapshots of the source code used previously did not contain those translations files, the proper upstream tarballs available since the first release of 0.8(.0) ships all the translations. Please include them in the package (probably kbibtex-data). -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (850, 'testing'), (800, 'unstable'), (750, 'experimental'), (750, 'stable'), (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'buildd-unstable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kbibtex depends on: ii kbibtex-data 0.8.1-1 ii kio5.49.0-1 ii libc6 2.27-6 ii libicu60 60.2-6 ii libkf5completion5 5.49.0-1 ii libkf5configcore5 5.49.0-1 ii libkf5configgui5 5.49.0-1 ii libkf5configwidgets5 5.49.0-1 ii libkf5coreaddons5 5.49.0-1 ii libkf5crash5 5.49.0-1 ii libkf5i18n55.49.0-1 ii libkf5iconthemes5 5.49.0-1 ii libkf5itemviews5 5.49.0-1 ii libkf5jobwidgets5 5.49.0-1 ii libkf5kiocore5 5.49.0-1 ii libkf5kiofilewidgets5 5.49.0-1 ii libkf5kiowidgets5 5.49.0-1 ii libkf5parts5 5.49.0-1 ii libkf5service-bin 5.49.0-1 ii libkf5service5 5.49.0-1 ii libkf5textwidgets5 5.49.0-1 ii libkf5widgetsaddons5 5.49.0-1 ii libkf5xmlgui5 5.49.0-1 ii libpoppler-qt5-1 0.69.0-2 ii libqt5core5a 5.11.1+dfsg-9 ii libqt5dbus55.11.1+dfsg-9 ii libqt5gui5 5.11.1+dfsg-9 ii libqt5network5 5.11.1+dfsg-9 ii libqt5widgets5 5.11.1+dfsg-9 ii libqt5xml5 5.11.1+dfsg-9 ii libqt5xmlpatterns5 5.11.1-3 ii libstdc++6 8.2.0-8 Versions of packages kbibtex recommends: pn biber ii texlive-bibtex-extra 2018.20181009-1 Versions of packages kbibtex suggests: pn bibtex2html pn latex2rtf ii texlive-latex-base 2018.20181009-1 -- no debconf information --- End Message --- --- Begin Message --- Source: kbibtex Source-Version: 0.9.90-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kbibtex, 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 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kbibtex 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, 12 Jan 2021 01:04:01 +0100 Source: kbibtex Architecture: source Version: 0.9.90-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Pino Toscano Closes: 911523 Changes: kbibtex (0.9.90-1) unstable; urgency=medium . * New upstream release: - since we use the release tarballs now, the translations are available (Closes: #911523) * Add myself to Uploaders. * Update the patches: - upstream_cmake-use-the-right-variable-for-man-page-install-de.patch: drop, backported from upstream * Update install files. Checksums-Sha1: 829a35373743717425d92564b32d5b9612a4c5e0 2733 kbibtex_0.9.90-1.dsc 272c72309fbba57ded15abd4be56c8c43dd42561 3836360 kbibtex_0.9.90.orig.tar.xz a14d31418bf51b9ef1cf7f6717885a42bca330e5 13388 kbibtex_0.9.90-
Bug#978358: marked as done (transmission-remote-gtk: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.
Your message dated Mon, 11 Jan 2021 23:35:47 +
with message-id
and subject line Bug#978358: fixed in transmission-remote-gtk 1.4.1-5
has caused the Debian Bug report #978358,
regarding transmission-remote-gtk: FTBFS: error: gettext infrastructure
mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf
macros are from gettext version 0.20
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.)
--
978358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transmission-remote-gtk
Version: 1.4.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/po'
> sed -e '/^#/d' remove-potcdate.sin > t-remove-potcdate.sed
> mv t-remove-potcdate.sed remove-potcdate.sed
> package_gnu=""; \
> test -n "$package_gnu" || { \
> if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \
>LC_ALL=C find -L .. -maxdepth 1 -type f \
> -size -1000c -exec grep 'GNU
> transmission-remote-gtk' \
> /dev/null '{}' ';' 2>/dev/null; \
>else \
>LC_ALL=C grep 'GNU transmission-remote-gtk' ../* 2>/dev/null; \
>fi; \
> } | grep -v 'libtool:' >/dev/null; then \
> package_gnu=yes; \
>else \
> package_gnu=no; \
>fi; \
> }; \
> if test "$package_gnu" = "yes"; then \
> package_prefix='GNU '; \
> else \
> package_prefix=''; \
> fi; \
> if test -n '' || test
> 'https://github.com/transmission-remote-gtk/transmission-remote-gtk/issues' =
> '@'PACKAGE_BUGREPORT'@'; then \
> msgid_bugs_address=''; \
> else \
>
> msgid_bugs_address='https://github.com/transmission-remote-gtk/transmission-remote-gtk/issues';
> \
> fi; \
> case `/usr/bin/xgettext --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \
> '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \
> /usr/bin/xgettext --default-domain=transmission-remote-gtk --directory=..
> \
> --add-comments=TRANSLATORS: --from-code=UTF-8 --keyword=_ --keyword=N_
> --keyword=C_:1c,2 --keyword=NC_:1c,2 --keyword=g_dngettext:2,3 --add-comments
> \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> *) \
> /usr/bin/xgettext --default-domain=transmission-remote-gtk --directory=..
> \
> --add-comments=TRANSLATORS: --from-code=UTF-8 --keyword=_ --keyword=N_
> --keyword=C_:1c,2 --keyword=NC_:1c,2 --keyword=g_dngettext:2,3 --add-comments
> \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --package-name="${package_prefix}transmission-remote-gtk" \
> --package-version='1.4.1' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> esac
> /usr/bin/xgettext: warning: a fallback ITS rule file
> '/usr/share/gettext-0.21/its/metainfo.its' is used; it may not be in sync
> with the upstream
> test ! -f transmission-remote-gtk.po || { \
> if test -f ./transmission-remote-gtk.pot-header; then \
> sed -e '1,/^#$/d' < transmission-remote-gtk.po >
> transmission-remote-gtk.1po && \
> cat ./transmission-remote-gtk.pot-header transmission-remote-gtk.1po >
> transmission-remote-gtk.po; \
> rm -f transmission-remote-gtk.1po; \
> fi; \
> if test -f ./transmission-remote-gtk.pot; then \
> sed -f remove-potcdate.sed < ./transmission-remote-gtk.pot >
> transmission-remote-gtk.1po && \
> sed -f remove-potcdate.sed < transmission-remote-gtk.po >
> transmission-remote-gtk.2po && \
> if cmp transmission-remote-gtk.1po transmission-remote-gtk.2po >/dev/null
> 2>&1; then \
> rm -f transmission-remote-gtk.1po transmission-remote-gtk.2po
> transmission-remote-gtk.po; \
> else \
> rm -f transmission-remote-gtk.1po transmission-remote-gtk.2po
> ./transmission-remote-gtk.pot && \
> mv transmission-remote-gtk.po ./transmission-remote-gtk.pot; \
> fi; \
> else \
> mv transmission-remote-gtk.po ./transmission-remote-gtk.pot; \
> fi; \
> }
> make[4]: Leaving directory '/<>/po'
> *** error: gettext infrastructure mismatch: using a Makefile.in.in from
> gettext version 0.19 but the autoconf macros are from gettext version 0.20
> make[3]: *** [Makefile:265: stamp-po] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/transmission-remote-gtk_1.4.1
Bug#972797: marked as done (imagemagick: CVE-2020-27560: Division by Zero in function OptimizeLayerFrames)
Your message dated Mon, 11 Jan 2021 23:34:09 + with message-id and subject line Bug#972797: fixed in imagemagick 8:6.9.11.57+dfsg-1 has caused the Debian Bug report #972797, regarding imagemagick: CVE-2020-27560: Division by Zero in function OptimizeLayerFrames 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.) -- 972797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.24+dfsg-1 Severity: important Tags: security upstream Forwarded: https://github.com/ImageMagick/ImageMagick/pull/2743 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 8:6.9.10.23+dfsg-2.1+deb10u1 Control: found -1 8:6.9.10.23+dfsg-2.1 Hi, The following vulnerability was published for imagemagick. CVE-2020-27560[0]: | ImageMagick 7.0.10-34 allows Division by Zero in OptimizeLayerFrames | in MagickCore/layer.c, which may cause a denial of service. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-27560 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27560 [1] https://github.com/ImageMagick/ImageMagick/pull/2743 [2] https://github.com/ImageMagick/ImageMagick6/commit/6e3b13c7ef94d72b40fba91987897c4326717a46 Regards, Salvatore --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.57+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of imagemagick, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated imagemagick 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, 11 Jan 2021 22:14:26 + Source: imagemagick Architecture: source Version: 8:6.9.11.57+dfsg-1 Distribution: unstable Urgency: medium Maintainer: ImageMagick Packaging Team Changed-By: Bastien Roucariès Closes: 971216 972797 977205 Changes: imagemagick (8:6.9.11.57+dfsg-1) unstable; urgency=medium . * New upstream version: - Bug fix: "CVE-2020-29599", imagemagick mishandles the -authenticate option, which allows setting a password for password-protected PDF files. The user-controlled password was not properly escaped/sanitized and it was therefore possible to inject additional shell commands via coders/pdf.c. Thanks to Salvatore Bonaccorso (Closes: #977205). - Bug fix: "CVE-2020-27560: Division by Zero in function OptimizeLayerFrames", thanks to Salvatore Bonaccorso (Closes: #972797). * Fix dh_doxygen FTBFS (Closes: #971216) Checksums-Sha1: 98043226f8d2a24a7f1057380adb9c6867cf54ed 5079 imagemagick_6.9.11.57+dfsg-1.dsc 8420160075e75cde28a09a0b9b7cff725cee9db9 9392580 imagemagick_6.9.11.57+dfsg.orig.tar.xz abbd21d51c0d56aceb902c602c0fc0cf477603e6 245888 imagemagick_6.9.11.57+dfsg-1.debian.tar.xz 944dad89fa48f440ea2391cfd5f9afc1b2b613c3 11973 imagemagick_6.9.11.57+dfsg-1_source.buildinfo Checksums-Sha256: df60159c4f67c2a30fa5b979b82d7202bd9d45225c98348078886c420ccd1d61 5079 imagemagick_6.9.11.57+dfsg-1.dsc 383ed545dc93d34ebefa54623cb7c43e8b32d3076c14d9d93561307c97ed27a7 9392580 imagemagick_6.9.11.57+dfsg.orig.tar.xz 3cf0c4d05a08b3b68f2fa2548f9fd0f20aaa946c8c93a9c4159d8b78173a3a1b 245888 imagemagick_6.9.11.57+dfsg-1.debian.tar.xz 72400364af7ef08008c7182caad793d4cf98aa82427c647f776c7684a80a6da0 11973 imagemagick_6.9.11.57+dfsg-1_source.buildinfo Files: dec3c27f46285b416d8b93bf62c08fed 5079 graphics optional imagemagick_6.9.11.57+dfsg-1.dsc 51d0045050a717cd2d43a6773439aae6 9392580 graphics optional imagemagick_6.9.11.57+dfsg.orig.tar.xz 8666e98765c9a4ad83f7b7e6ba46ed8a 245888 graphics optional imagemagick_6.9.11.57+dfsg-1.debian.tar.xz 7baf9b5debd6ebbae9aba1eaca2dae39 11973 graphics optional imagemagick_6.9.11.57+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaL
Bug#977205: marked as done (imagemagick: CVE-2020-29599)
Your message dated Mon, 11 Jan 2021 23:34:09 + with message-id and subject line Bug#977205: fixed in imagemagick 8:6.9.11.57+dfsg-1 has caused the Debian Bug report #977205, regarding imagemagick: CVE-2020-29599 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.) -- 977205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.24+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for imagemagick. A very extensive blogpost[1] explains the issue, and note that the provided POC though does only work so far in ImageMagick7 the issue is present as well in legacy ImageMagick 6, affected versions should be around 6.9.8-1 onwards. The required fixes for ImageMagick6 are referenced in the security-tracker. As a side node: For buster the issue is mitigated as the recent DSA included the 200-disable-ghostscript-formats.patch patch and disables ghostscript handled formats. As a hardening measure against those issue it might be ideal to ship the disabling as well in bullseye. CVE-2020-29599[0]: | ImageMagick before 6.9.11-40 and 7.x before 7.0.10-40 mishandles the | -authenticate option, which allows setting a password for password- | protected PDF files. The user-controlled password was not properly | escaped/sanitized and it was therefore possible to inject additional | shell commands via coders/pdf.c. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-29599 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29599 [1] https://insert-script.blogspot.com/2020/11/imagemagick-shell-injection-via-pdf.html Regards, Salvatore -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-rc6-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.57+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of imagemagick, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated imagemagick 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, 11 Jan 2021 22:14:26 + Source: imagemagick Architecture: source Version: 8:6.9.11.57+dfsg-1 Distribution: unstable Urgency: medium Maintainer: ImageMagick Packaging Team Changed-By: Bastien Roucariès Closes: 971216 972797 977205 Changes: imagemagick (8:6.9.11.57+dfsg-1) unstable; urgency=medium . * New upstream version: - Bug fix: "CVE-2020-29599", imagemagick mishandles the -authenticate option, which allows setting a password for password-protected PDF files. The user-controlled password was not properly escaped/sanitized and it was therefore possible to inject additional shell commands via coders/pdf.c. Thanks to Salvatore Bonaccorso (Closes: #977205). - Bug fix: "CVE-2020-27560: Division by Zero in function OptimizeLayerFrames", thanks to Salvatore Bonaccorso (Closes: #972797). * Fix dh_doxygen FTBFS (Closes: #971216) Checksums-Sha1: 98043226f8d2a24a7f1057380adb9c6867cf54ed 5079 imagemagick_6.9.11.57+dfsg-1.dsc 8420160075e75cde28a09a0b9b7cff725cee9db9 9392580 imagemagick_6.9.11.57+dfsg.orig.tar.xz abbd21d51c0d56aceb902c602c0fc0cf477603e6 245888 imagemagick_6.9.11.57+dfsg-1.debian.tar.xz 944dad89fa48f440ea2391cfd5f9afc1b2b613c3 11973 imagemagick_6.9.11.57+dfsg-1_source.buildinfo Checksums-Sha256: df60159c4f67c2
Bug#971216: marked as done (imagemagick: FTBFS: dh_doxygen: error: Doxygen documentation not found)
Your message dated Mon, 11 Jan 2021 23:34:09 + with message-id and subject line Bug#971216: fixed in imagemagick 8:6.9.11.57+dfsg-1 has caused the Debian Bug report #971216, regarding imagemagick: FTBFS: dh_doxygen: error: Doxygen documentation not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.24+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # special source imagemagick-*-common > dh_install --package=imagemagick-6-common > install -d debian/imagemagick-6-common// > cp --reflink=auto -a ./debian/tmp-indep/etc/ > debian/imagemagick-6-common/// > install -d debian/imagemagick-6-common//usr/share/ > cp --reflink=auto -a ./debian/tmp-indep/usr/share/ImageMagick-6 > debian/imagemagick-6-common//usr/share// > install -d debian/imagemagick-6-common//usr/share/doc/ > cp --reflink=auto -a > ./debian/prebuilt/usr/share/doc/imagemagick-6-common > debian/imagemagick-6-common//usr/share/doc// > # remaining package > dh_install --indep --remaining-packages --sourcedir=debian/tmp-indep > --autodest > install -d > debian/imagemagick-6-doc//usr/share/doc/imagemagick-6-common/html > cp --reflink=auto -a > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/images > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/index.html > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/www > debian/imagemagick-6-doc//usr/share/doc/imagemagick-6-common/html/ > install -d debian/libmagickcore-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a debian/tmp-indep/usr/include/ImageMagick-6/magick > debian/libmagickcore-6-headers//usr/include/ImageMagick-6/ > install -d debian/libmagickwand-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a debian/tmp-indep/usr/include/ImageMagick-6/wand > debian/libmagickwand-6-headers//usr/include/ImageMagick-6/ > install -d debian/libmagick\+\+-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a > debian/tmp-indep/usr/include/ImageMagick-6/Magick\+\+ > debian/tmp-indep/usr/include/ImageMagick-6/Magick\+\+.h > debian/libmagick\+\+-6-headers//usr/include/ImageMagick-6/ > cp --reflink=auto -a debian/tmp-indep/usr/share/perl5 > debian/libimage-magick-perl//usr/share/ > install -d debian/libimage-magick-perl//usr/share/man/man3 > cp --reflink=auto -a > debian/tmp-indep/usr/share/man/man3/Image::Magick.3pm > debian/libimage-magick-perl//usr/share/man/man3/ > # fix doxygen problem > ./debian/scripts/dh_doxygen --indep --package=imagemagick-6-doc > dh_doxygen: error: Doxygen documentation not found > make[1]: *** [debian/rules:722: override_dh_install-indep] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/09/26/imagemagick_6.9.11.24+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.57+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of imagemagick, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated imagemagick 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, 11 Jan 2021 22:14:26 + Source: imagemagick Architecture: source Version: 8:6.9.11.57+dfsg-1 Distribution: unst
Bug#928266: marked as done (perceptualdiff: build logs lack compiler invocations)
Your message dated Mon, 11 Jan 2021 23:21:26 + with message-id and subject line Bug#928266: fixed in perceptualdiff 2.1-1 has caused the Debian Bug report #928266, regarding perceptualdiff: build logs lack compiler invocations 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.) -- 928266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perceptualdiff Version: 1.2-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap perceptualdiff fails to cross build from source, but diagnosing why that happens is next to impossible, because the build log isn't verbose. The attached patch fixes the verbosity problem. Please consider applying it. Helmut diff -u perceptualdiff-1.2/debian/changelog perceptualdiff-1.2/debian/changelog --- perceptualdiff-1.2/debian/changelog +++ perceptualdiff-1.2/debian/changelog @@ -1,3 +1,10 @@ +perceptualdiff (1.2-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Let dh_auto_configure create verbose build logs. (Closes: #-1) + + -- Helmut Grohne Tue, 30 Apr 2019 21:54:34 +0200 + perceptualdiff (1.2-2) unstable; urgency=medium * Fix build problem diff -u perceptualdiff-1.2/debian/rules perceptualdiff-1.2/debian/rules --- perceptualdiff-1.2/debian/rules +++ perceptualdiff-1.2/debian/rules @@ -36,7 +36,7 @@ dh_testdir # Add here commands to compile the package. - cmake . -DCMAKE_INSTALL_PREFIX=/usr + dh_auto_configure --builddirectory=. #docbook-to-man debian/perceptualdiff.sgml > perceptualdiff.1 touch build-stamp --- End Message --- --- Begin Message --- Source: perceptualdiff Source-Version: 2.1-1 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of perceptualdiff, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated perceptualdiff 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, 11 Jan 2021 22:47:03 + Source: perceptualdiff Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Jeff Breidenbach Changed-By: Barak A. Pearlmutter Closes: 836777 928266 965773 Changes: perceptualdiff (2.1-1) unstable; urgency=medium . * Update packaging scripts * Trivial debian/rules makes logs verbose (closes: #928266) * Trim trailing whitespace. * Explicitly specify source format. * Bump debhelper to 13. (closes: #965773) * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add debian/changelog close clause colons * Add debian/watch uscan support file * Bump policy * New upstream release - checks --output error, see 9dffbb97 "Failed to save" (closes: #836777) Checksums-Sha1: 2b523ef24709dc8340f939ee6c25ffe5caa32a24 2008 perceptualdiff_2.1-1.dsc 20d6e88d191b1362723011a8cb5aa7f627a1a05b 773496 perceptualdiff_2.1.orig.tar.xz a07bf7e6fc2180bda285faac52279da6b308df19 3376 perceptualdiff_2.1-1.debian.tar.xz 72888e698588953af1e180910610569a2cfb22f1 7658 perceptualdiff_2.1-1_source.buildinfo Checksums-Sha256: 5d5f90f610b6d762896bd3fe84411109f11cb32f0142c6955fe083a3fb58f774 2008 perceptualdiff_2.1-1.dsc 277cd5a88271f918e6acadb1b7a1973fca6a6a25a650398be374a0c693024294 773496 perceptualdiff_2.1.orig.tar.xz ce402065b689fd7022ebc678458c5587fa8a6af3ade24ee486d154eebfa4e850 3376 perceptualdiff_2.1-1.debian.tar.xz b93d6317bd0dc97209a3b5422276b2453ad538210b5c43d5c6d5c52031101f52 7658 perceptualdiff_2.1-1_source.buildinfo Files: d4ec5cf4c913f61dbd63d1a3ec436c05 2008 utils optional perceptualdiff_2.1-1.dsc 512e5351a39d1cbb2b7ff31d163b419c 773496 utils optional perceptualdiff_2.1.orig.tar.xz 9bbcce5cd1bef9dcaf69847d0010369e 3376 utils optional perceptualdiff_2.1-1.debian.tar.xz c2d9cb1b8f5233db80ac1bf24b06609f 7658 utils optional perceptualdiff_2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gF
Bug#965773: marked as done (perceptualdiff: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 11 Jan 2021 23:21:26 + with message-id and subject line Bug#965773: fixed in perceptualdiff 2.1-1 has caused the Debian Bug report #965773, regarding perceptualdiff: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perceptualdiff Version: 1.2-2 Severity: normal Usertags: compat-5-6-removal Hi, The package perceptualdiff uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: perceptualdiff Source-Version: 2.1-1 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of perceptualdiff, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated perceptualdiff 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, 11 Jan 2021 22:47:03 + Source: perceptualdiff Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Jeff Breidenbach Changed-By: Barak A. Pearlmutter Closes: 836777 928266 965773 Changes: perceptualdiff (2.1-1) unstable; urgency=medium . * Update packaging scripts * Trivial debian/rules makes logs verbose (closes: #928266) * Trim trailing whitespace. * Explicitly specify source format. * Bump debhelper to 13. (closes: #965773) * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add debian/changelog close clause colons * Add debian/watch uscan support file * Bump policy * New upstream release - checks --output error, see 9dffbb97 "Failed to save" (closes: #836777) Checksums-Sha1: 2b523ef24709dc8340f939ee6c25ffe5caa32a24 2008 perceptualdiff_2.1-1.dsc 20d6e88d191b1362723011a8cb5aa7f627a1a05b 773496 perceptualdiff_2.1.orig.tar.xz a07bf7e6fc2180bda285faac52279da6b308df19 3376 perceptualdiff_2.1-1.debian.tar.xz 72888e698588953af1e180910610569a2cfb22f1 7658 perceptualdiff_2.1-1_source.buildinfo Checksums-Sha256: 5d5f90f610b6d762896bd3fe84411109f11cb32f0142c6955fe083a3fb58f774 2008 perceptualdiff_2.1-1.dsc 277cd5a88271f918e6acadb1b7a1973fca6a6a25a650398be374a0c693024294 773496 perceptualdiff_2.1.orig.tar.xz ce402065b689fd7022ebc678458c5587fa8a6af3ade24ee486d154eebfa4e850 3376 perceptualdiff_2.1-1.debian.tar.xz b93d6317bd0dc97209a3b5422276b2453ad538210b5c43d5c6d5c52031101f52 7658 perceptualdiff_2.1-1_source.buildinfo Files: d4ec5cf4c913f61dbd63d1a3ec436c05 2008 utils optional perceptualdiff_2.1-1.dsc 512e5351a39d1cbb2b7ff31d163b419c 773496 utils optional perceptualdiff_2.1.orig.tar.xz 9bbcce5cd1bef9dcaf69847d0010369e 3376 utils optional perceptualdiff_2.1-1.debian.tar.xz c2d9cb1b8f5233db80ac1bf24b06609f 7658 utils optional perceptualdiff_2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAl/81
Bug#921142: marked as done (mark synfig Multi-Arch: foreign)
Your message dated Mon, 11 Jan 2021 23:21:55 +
with message-id
and subject line Bug#921142: fixed in synfig 1.4.0+dfsg-1
has caused the Debian Bug report #921142,
regarding mark synfig Multi-Arch: foreign
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.)
--
921142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synfig
Version: 1.2.2-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:synfigstudio
synfigstudio fails to cross build from source, because it fails running
synfig with an "Exec format error". Usually, that means a dependency was
(in this case synfig) was installed for the wrong architecture. In this
case, it makes sense to fix the problem on the synfig side. Since synfig
works with architecture-independent file formats (.sif, which is xml
based and various image formats), it is correct to mark synfig
Multi-Arch: foreign. Doing so makes the synfigstudio build proceed.
While at it, the attached patch also adds the relevant Multi-Arch
annotations for libsynfig0a and synfig-examples. Please consider
applying it.
Helmut
diff --minimal -Nru synfig-1.2.2/debian/changelog synfig-1.2.2/debian/changelog
--- synfig-1.2.2/debian/changelog 2019-01-31 07:41:06.0 +0100
+++ synfig-1.2.2/debian/changelog 2019-02-02 08:59:23.0 +0100
@@ -1,3 +1,12 @@
+synfig (1.2.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark synfig Multi-Arch: foreign (Closes: #-1).
+ * Mark libsynfig0a Multi-Arch: same.
+ * Mark synfig-examples Multi-Arch: foreign.
+
+ -- Helmut Grohne Sat, 02 Feb 2019 08:59:23 +0100
+
synfig (1.2.2-1) unstable; urgency=medium
[ Alexis Bienvenüe ]
diff --minimal -Nru synfig-1.2.2/debian/control synfig-1.2.2/debian/control
--- synfig-1.2.2/debian/control 2019-01-31 07:41:06.0 +0100
+++ synfig-1.2.2/debian/control 2019-02-02 08:59:20.0 +0100
@@ -33,6 +33,7 @@
Package: synfig
Architecture: any
+Multi-Arch: foreign
Depends: ${shlibs:Depends},
${misc:Depends}
Suggests: synfigstudio,
@@ -47,6 +48,7 @@
Package: libsynfig0a
Section: libs
Architecture: any
+Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
${misc:Depends},
@@ -76,6 +78,7 @@
Package: synfig-examples
Architecture: all
+Multi-Arch: foreign
Suggests: synfigstudio
Conflicts: libsynfig-doc
Replaces: libsynfig-doc
--- End Message ---
--- Begin Message ---
Source: synfig
Source-Version: 1.4.0+dfsg-1
Done: Dmitry Smirnov
We believe that the bug you reported is fixed in the latest version of
synfig, 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 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Smirnov (supplier of updated synfig 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, 11 Jan 2021 22:58:48 +1100
Source: synfig
Architecture: source
Version: 1.4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dmitry Smirnov
Closes: 921142
Changes:
synfig (1.4.0+dfsg-1) unstable; urgency=medium
.
* New upstream release.
* No longer build with '--with-opengl' due to FTBFS.
* Marked synfig "Multi-Arch: foreign" (Closes: #921142).
Thanks, Helmut Grohne.
* Rules-Requires-Root: no
* rules: removed "--as-needed".
* Build-Depends:
+ libavcodec-dev
+ libavformat-dev
+ libavutil-dev
+ libswscale-dev
Checksums-Sha1:
273e8be6390cc1d85a3fa28da790f58e1589bf12 2502 synfig_1.4.0+dfsg-1.dsc
063d332fc963a5a7c221914c4ce7a05aebfdc6db 2796216 synfig_1.4.0+dfsg.orig.tar.xz
08514e1444cef66faae7040d9329425834cde8d9 9044 synfig_1.4.0+dfsg-1.debian.tar.xz
f98f9cce88a01992ae1362369b2daae074bb4a0c 24770
synfig_1.4.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
dd51d286f04db9d3dcd2c538e7f6a7f391f9da6c68773da6379d02048b0b8373 2502
synfig_1.4.0+dfsg-1.dsc
e9b710e2901598a2088ad979631694aca5849a5544b515a17192a982f56dcab0 2796216
synfig_1.4.0+dfsg.orig.tar.xz
4c8a92437dd014b9c511c8d9f58dc69115830a2adb319756c3c38cbe4fa8fa67 9044
synfig_1.
Bug#836777: marked as done (perceptualdiff: does not catch disk-full condition, creates 0-size diffs)
Your message dated Mon, 11 Jan 2021 23:21:26 + with message-id and subject line Bug#836777: fixed in perceptualdiff 2.1-1 has caused the Debian Bug report #836777, regarding perceptualdiff: does not catch disk-full condition, creates 0-size diffs 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.) -- 836777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: perceptualdiff Version: 1.2-2 -output will always create a file, but when the disk is full its size is 0 and we don't get an error message. --- End Message --- --- Begin Message --- Source: perceptualdiff Source-Version: 2.1-1 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of perceptualdiff, 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 836...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated perceptualdiff 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, 11 Jan 2021 22:47:03 + Source: perceptualdiff Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Jeff Breidenbach Changed-By: Barak A. Pearlmutter Closes: 836777 928266 965773 Changes: perceptualdiff (2.1-1) unstable; urgency=medium . * Update packaging scripts * Trivial debian/rules makes logs verbose (closes: #928266) * Trim trailing whitespace. * Explicitly specify source format. * Bump debhelper to 13. (closes: #965773) * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add debian/changelog close clause colons * Add debian/watch uscan support file * Bump policy * New upstream release - checks --output error, see 9dffbb97 "Failed to save" (closes: #836777) Checksums-Sha1: 2b523ef24709dc8340f939ee6c25ffe5caa32a24 2008 perceptualdiff_2.1-1.dsc 20d6e88d191b1362723011a8cb5aa7f627a1a05b 773496 perceptualdiff_2.1.orig.tar.xz a07bf7e6fc2180bda285faac52279da6b308df19 3376 perceptualdiff_2.1-1.debian.tar.xz 72888e698588953af1e180910610569a2cfb22f1 7658 perceptualdiff_2.1-1_source.buildinfo Checksums-Sha256: 5d5f90f610b6d762896bd3fe84411109f11cb32f0142c6955fe083a3fb58f774 2008 perceptualdiff_2.1-1.dsc 277cd5a88271f918e6acadb1b7a1973fca6a6a25a650398be374a0c693024294 773496 perceptualdiff_2.1.orig.tar.xz ce402065b689fd7022ebc678458c5587fa8a6af3ade24ee486d154eebfa4e850 3376 perceptualdiff_2.1-1.debian.tar.xz b93d6317bd0dc97209a3b5422276b2453ad538210b5c43d5c6d5c52031101f52 7658 perceptualdiff_2.1-1_source.buildinfo Files: d4ec5cf4c913f61dbd63d1a3ec436c05 2008 utils optional perceptualdiff_2.1-1.dsc 512e5351a39d1cbb2b7ff31d163b419c 773496 utils optional perceptualdiff_2.1.orig.tar.xz 9bbcce5cd1bef9dcaf69847d0010369e 3376 utils optional perceptualdiff_2.1-1.debian.tar.xz c2d9cb1b8f5233db80ac1bf24b06609f 7658 utils optional perceptualdiff_2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAl/81hYPHGJhcEBkZWJp YW4ub3JnAAoJEJnrHqTSM3uIiKgP/2rZQ2zcL7b1EMoaIiPGCj2YEaeUQf65UTkk Umw8Z7H0HPDNV4cOORs5oAdG6JmN9RrJ4l8OkGsgXspTZn+N2dUWMZM4hQtNSeyE /uZ+xTLBpsDVWMJnhssNIMKt1935+uucmrYSonzCSh2MNCpsWA6I/H6zoLPLGkR9 JPHFKUhvHrwODCkAIPrbch9TwO27Qeyh/cJVjhDGWq7O6GPMG6u8EOF/Iq72X1W3 6yrar5HTOJTff7LUCoN+4HIKh/oKbQB8jUiN8U6WckFeXh5VWzKJFR60AarSJJBO x2s4lXvd/1YDWk1mv8Lg7PzGSCliD8IpH3SgcnE/dbs7GJjVUhHK38nBYSYtV5j5 5J/SSr9r/a0GEf2Oz+k2fZ8h81eJmAhaNRcQNd/h50x1LhPeatIEJY0ZZHb8XkxS dh/cxrsGa0vkil+07mOzCuOjKPC7n16qFhWro+V4MjoENItR9nh9lJHGH1ea8aEc oaNR742L4080B03/1lPbvAWUyB9XymSu3pOHOD3IYc/vxmhPmcWtdN2f1RHmIRn5 xJcW2deANYiWX+TCMcFV1akfKdc77taT981uksZGUrfL5IJp/56CwuHEsRI28WBb r2ivMhkDW4sivWxFn0swbjeZlPJBdooJa3/BwPIm5KIm7wt3w14++8Vk5mWU4Udf pQJEq4ph =pOZm -END PGP SIGNATURE End Message ---
Bug#964526: marked as done (epoptes-client: replace transitional bsdmainutils dependency)
Your message dated Mon, 11 Jan 2021 23:03:31 + with message-id and subject line Bug#964526: fixed in epoptes 21.01-1 has caused the Debian Bug report #964526, regarding epoptes-client: replace transitional bsdmainutils dependency 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.) -- 964526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: epoptes-client Version: 20.01-1 Severity: important Dear Maintainer, your package currently Depends on bsdmainutils, which has become a transitional package. Please change the dependency to one of the replacement packages: * bsdutils * bsdextrautils * calendar * ncal * vacation Thanks, Chris --- End Message --- --- Begin Message --- Source: epoptes Source-Version: 21.01-1 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of epoptes, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian (supplier of updated epoptes 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, 11 Jan 2021 14:47:37 -0800 Source: epoptes Architecture: source Version: 21.01-1 Distribution: unstable Urgency: medium Maintainer: Epoptes Developers Changed-By: Vagrant Cascadian Closes: 964526 Changes: epoptes (21.01-1) unstable; urgency=medium . [ Alkis Georgopoulos ] * Allow specifying thumbshot interval * Create .config/epoptes when launching epoptes (#116) * Lowercase LTSP5 MAC addresses (#123) * Import translations from launchpad * Don't focus remote assistance connect button (#120) * Call mute_sound for SESSION pulseaudio (#119) * Remove bsdmainutils dependency (Closes: #964526) * Introduce POTFILES.in . [ Vagrant Cascadian ] * debian/rules: Add override for dh_installinit, as epoptes does not ship init scripts. Checksums-Sha1: 9ebcc8c4ced016d9b954bd1c0dcaa979c0f79585 1434 epoptes_21.01-1.dsc fe905c4c8b8f538a11f06a18493bf19a63be9270 344539 epoptes_21.01.orig.tar.gz 275e9d6630cb021a7006ca8e4508636464a3b6c6 9964 epoptes_21.01-1.debian.tar.xz b4d2b6e688d1920e468fdf60963ae28dd3788b86 6755 epoptes_21.01-1_amd64.buildinfo Checksums-Sha256: a3e15a93fbafd6b8e456af37cbcdfc54e03d1047c4e5268284190c77b808abd5 1434 epoptes_21.01-1.dsc 24f08f77ba2c88869abaaa9c0eaf1be1b6f5a7e11df29ce7377530ee6b442fa4 344539 epoptes_21.01.orig.tar.gz 448380055e1698431d462148631353e968eef3716b657c13149c0e7a3d95f203 9964 epoptes_21.01-1.debian.tar.xz 266527d397479f6bb53df6fbb3b876f12307237cd0aaccadce546473913df1a7 6755 epoptes_21.01-1_amd64.buildinfo Files: 2956054f99fea4f9d72e920d2620bbc2 1434 admin optional epoptes_21.01-1.dsc eaf3cea3818f10366bd75a8716d245a6 344539 admin optional epoptes_21.01.orig.tar.gz 22d6ee5d5a05891addb61813a3425024 9964 admin optional epoptes_21.01-1.debian.tar.xz 43e69d118cfc3fe102face49f982cc29 6755 admin optional epoptes_21.01-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCX/zWURMcdmFncmFudEBk ZWJpYW4ub3JnAAoJENxRj8h/lxaqMXQA/0VaSYG4s1XUidZKV//BMNmbYCwqVhFe jIh8tjhZ9EJaAQD0GRPXw4DkU48VWhVM4E32s4GMa6cv2UIZ7dP/ZHbyDA== =E7kg -END PGP SIGNATURE End Message ---
Bug#906918: marked as done (fdisk: document cfdisk resize command and shortcut)
Your message dated Mon, 11 Jan 2021 23:04:47 + with message-id and subject line Bug#915971: fixed in util-linux 2.36.1-5 has caused the Debian Bug report #915971, regarding fdisk: document cfdisk resize command and shortcut 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.) -- 915971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fdisk Version: 2.32.1-0.1 Severity: minor Tags: upstream Dear Maintainer, the resize command for cfdisk is not documented in the cfdisk(8) man page, nor in the online help dialog of the tool (shown pressing 'h' or '?' or selecting [ Help ]). The shortcut 'r' for resizing is actually working but it's not documented either. Regards. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 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 fdisk depends on: ii libc6 2.27-5 ii libfdisk1 2.32.1-0.1 ii libmount1 2.32.1-0.1 ii libncursesw6 6.1+20180714-1 ii libsmartcols1 2.32.1-0.1 ii libtinfo6 6.1+20180714-1 fdisk recommends no packages. fdisk suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.36.1-5 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Jan 2021 22:03:06 + Source: util-linux Architecture: source Version: 2.36.1-5 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 906918 915971 Changes: util-linux (2.36.1-5) unstable; urgency=medium . * hwclock-set: remove useless source /etc/default/rcS * hwclock-set: remove stamp file. Since initramfs-tools 0.119 (jessie), hwclock-set is not installed in the initramfs anymore. This was the original reason for having the stamp file. * man cfdisk: Add upstream patch documenting resize command. Thanks to Vincent McIntyre (Closes: #915971, #906918) Checksums-Sha1: 71df18b228f245242d75b0bc9c79c610b732200e 4337 util-linux_2.36.1-5.dsc 1ca8c1883a63e84ad118f4bdc6ad4fe769b3bbce 97020 util-linux_2.36.1-5.debian.tar.xz c3105e0815ecdea3cf0b6319727b3087ced498fe 7051 util-linux_2.36.1-5_source.buildinfo Checksums-Sha256: 68a251f76b34cc5042d8c5637e353f6676582dc345ac997257af718849afbc32 4337 util-linux_2.36.1-5.dsc 251172b217691f15d96273ae22f34906d1e14310c9a56062a4be109047dda94e 97020 util-linux_2.36.1-5.debian.tar.xz 8a03fef72e390a6f2c9f3a4069ce654292c1d184b2b68c0044d8f665628dbabc 7051 util-linux_2.36.1-5_source.buildinfo Files: fc7a2b248618385afa43dff234276aa2 4337 base required util-linux_2.36.1-5.dsc 8fdf5e6fb41c66640fc4bcba37392682 97020 base required util-linux_2.36.1-5.debian.tar.xz c83c6a326384ab007df396681c1dd712 7051 base required util-linux_2.36.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl/81YoACgkQXBPW25MF LgP8Vg/+LKEgGTDznEA24SbCEPvmjgYg+MEakAkd5kzx8iNxKQ8WMZvnDIKq68A+ pVWnxRyKsCvIoqU45Aok2xUkYFQdakaa/pvPWwA8OhfU6d0KcSUZiGWvwjtPBUaU iVWYB6J1SrakBM8qb+Huv0xBzKGOarU8TS2aBff1C0vy2QddF+RxScZ7PXbgODUD 5y30Eh94Dq+BLNHXgL+bXjJQ9QeZGePlKs9F6IQnCyYlZ/Baisyt4qYk0Jd1GMmY wbTGk2dxL4gOLuZA2uXhttQbl84x+qbN+1FCCodTqzw1CqJcA3ZV+n+Blhk6J9NY NwkRQHP0M18CzUDHR/mf/UVkKYKKGFVWp/FfsgVSzVae/n/WOsptPux05QBo1vgm ga5u3201CQoetbnCNK7WrfBHzVZpgSsJLWUOJgn52whmR435QG+4RBoyP50FCCMb MuWpjz7WxkYRulbVX+KaDqp80VyMaCcxTxjGnb7qkf9ZKEhpatHvOEtMle3EVpkD aoeo7r2QH9ODSn/kDOiB5Q4nfA/UK/x4TKQjP3Tb00Q09LCGo2BkgYjCU101GQ7b Z5r5mKNfvM1mHpAYWc/jK4ArHcBCNAuT3KC3+uZv5c
Bug#915971: marked as done (Document Resize on man page)
Your message dated Mon, 11 Jan 2021 23:04:47 + with message-id and subject line Bug#915971: fixed in util-linux 2.36.1-5 has caused the Debian Bug report #915971, regarding Document Resize on man page 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.) -- 915971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fdisk Version: 2.33-0.2 File: /sbin/cfdisk User choses Resize, and resizes a partition from 300 GB to 60 GB. But then when he tries to mount it, # mount /dev/sda5 /mnt/usb/thumb/ mount: /mnt/usb/thumb: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. # journalctl -f Dec 09 03:27:41 jidanni5 kernel: EXT4-fs (sda5): bad geometry: block count 103356160 exceeds size of device (15805440 blocks) So remove Resize or make it warn that any filesystems present will no longer be mountable if used. --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.36.1-5 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Jan 2021 22:03:06 + Source: util-linux Architecture: source Version: 2.36.1-5 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 906918 915971 Changes: util-linux (2.36.1-5) unstable; urgency=medium . * hwclock-set: remove useless source /etc/default/rcS * hwclock-set: remove stamp file. Since initramfs-tools 0.119 (jessie), hwclock-set is not installed in the initramfs anymore. This was the original reason for having the stamp file. * man cfdisk: Add upstream patch documenting resize command. Thanks to Vincent McIntyre (Closes: #915971, #906918) Checksums-Sha1: 71df18b228f245242d75b0bc9c79c610b732200e 4337 util-linux_2.36.1-5.dsc 1ca8c1883a63e84ad118f4bdc6ad4fe769b3bbce 97020 util-linux_2.36.1-5.debian.tar.xz c3105e0815ecdea3cf0b6319727b3087ced498fe 7051 util-linux_2.36.1-5_source.buildinfo Checksums-Sha256: 68a251f76b34cc5042d8c5637e353f6676582dc345ac997257af718849afbc32 4337 util-linux_2.36.1-5.dsc 251172b217691f15d96273ae22f34906d1e14310c9a56062a4be109047dda94e 97020 util-linux_2.36.1-5.debian.tar.xz 8a03fef72e390a6f2c9f3a4069ce654292c1d184b2b68c0044d8f665628dbabc 7051 util-linux_2.36.1-5_source.buildinfo Files: fc7a2b248618385afa43dff234276aa2 4337 base required util-linux_2.36.1-5.dsc 8fdf5e6fb41c66640fc4bcba37392682 97020 base required util-linux_2.36.1-5.debian.tar.xz c83c6a326384ab007df396681c1dd712 7051 base required util-linux_2.36.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl/81YoACgkQXBPW25MF LgP8Vg/+LKEgGTDznEA24SbCEPvmjgYg+MEakAkd5kzx8iNxKQ8WMZvnDIKq68A+ pVWnxRyKsCvIoqU45Aok2xUkYFQdakaa/pvPWwA8OhfU6d0KcSUZiGWvwjtPBUaU iVWYB6J1SrakBM8qb+Huv0xBzKGOarU8TS2aBff1C0vy2QddF+RxScZ7PXbgODUD 5y30Eh94Dq+BLNHXgL+bXjJQ9QeZGePlKs9F6IQnCyYlZ/Baisyt4qYk0Jd1GMmY wbTGk2dxL4gOLuZA2uXhttQbl84x+qbN+1FCCodTqzw1CqJcA3ZV+n+Blhk6J9NY NwkRQHP0M18CzUDHR/mf/UVkKYKKGFVWp/FfsgVSzVae/n/WOsptPux05QBo1vgm ga5u3201CQoetbnCNK7WrfBHzVZpgSsJLWUOJgn52whmR435QG+4RBoyP50FCCMb MuWpjz7WxkYRulbVX+KaDqp80VyMaCcxTxjGnb7qkf9ZKEhpatHvOEtMle3EVpkD aoeo7r2QH9ODSn/kDOiB5Q4nfA/UK/x4TKQjP3Tb00Q09LCGo2BkgYjCU101GQ7b Z5r5mKNfvM1mHpAYWc/jK4ArHcBCNAuT3KC3+uZv5c3l+Qs9IT57yEXBhqyJz8B0 DzTdc65mMwqIsh6yfmbx+sWPV6ww2rKqor19iFarmVzrEOegZAM= =zLqr -END PGP SIGNATURE End Message ---
Bug#906918: marked as done (fdisk: document cfdisk resize command and shortcut)
Your message dated Mon, 11 Jan 2021 23:04:47 + with message-id and subject line Bug#906918: fixed in util-linux 2.36.1-5 has caused the Debian Bug report #906918, regarding fdisk: document cfdisk resize command and shortcut 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.) -- 906918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fdisk Version: 2.32.1-0.1 Severity: minor Tags: upstream Dear Maintainer, the resize command for cfdisk is not documented in the cfdisk(8) man page, nor in the online help dialog of the tool (shown pressing 'h' or '?' or selecting [ Help ]). The shortcut 'r' for resizing is actually working but it's not documented either. Regards. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 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 fdisk depends on: ii libc6 2.27-5 ii libfdisk1 2.32.1-0.1 ii libmount1 2.32.1-0.1 ii libncursesw6 6.1+20180714-1 ii libsmartcols1 2.32.1-0.1 ii libtinfo6 6.1+20180714-1 fdisk recommends no packages. fdisk suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.36.1-5 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Jan 2021 22:03:06 + Source: util-linux Architecture: source Version: 2.36.1-5 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 906918 915971 Changes: util-linux (2.36.1-5) unstable; urgency=medium . * hwclock-set: remove useless source /etc/default/rcS * hwclock-set: remove stamp file. Since initramfs-tools 0.119 (jessie), hwclock-set is not installed in the initramfs anymore. This was the original reason for having the stamp file. * man cfdisk: Add upstream patch documenting resize command. Thanks to Vincent McIntyre (Closes: #915971, #906918) Checksums-Sha1: 71df18b228f245242d75b0bc9c79c610b732200e 4337 util-linux_2.36.1-5.dsc 1ca8c1883a63e84ad118f4bdc6ad4fe769b3bbce 97020 util-linux_2.36.1-5.debian.tar.xz c3105e0815ecdea3cf0b6319727b3087ced498fe 7051 util-linux_2.36.1-5_source.buildinfo Checksums-Sha256: 68a251f76b34cc5042d8c5637e353f6676582dc345ac997257af718849afbc32 4337 util-linux_2.36.1-5.dsc 251172b217691f15d96273ae22f34906d1e14310c9a56062a4be109047dda94e 97020 util-linux_2.36.1-5.debian.tar.xz 8a03fef72e390a6f2c9f3a4069ce654292c1d184b2b68c0044d8f665628dbabc 7051 util-linux_2.36.1-5_source.buildinfo Files: fc7a2b248618385afa43dff234276aa2 4337 base required util-linux_2.36.1-5.dsc 8fdf5e6fb41c66640fc4bcba37392682 97020 base required util-linux_2.36.1-5.debian.tar.xz c83c6a326384ab007df396681c1dd712 7051 base required util-linux_2.36.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl/81YoACgkQXBPW25MF LgP8Vg/+LKEgGTDznEA24SbCEPvmjgYg+MEakAkd5kzx8iNxKQ8WMZvnDIKq68A+ pVWnxRyKsCvIoqU45Aok2xUkYFQdakaa/pvPWwA8OhfU6d0KcSUZiGWvwjtPBUaU iVWYB6J1SrakBM8qb+Huv0xBzKGOarU8TS2aBff1C0vy2QddF+RxScZ7PXbgODUD 5y30Eh94Dq+BLNHXgL+bXjJQ9QeZGePlKs9F6IQnCyYlZ/Baisyt4qYk0Jd1GMmY wbTGk2dxL4gOLuZA2uXhttQbl84x+qbN+1FCCodTqzw1CqJcA3ZV+n+Blhk6J9NY NwkRQHP0M18CzUDHR/mf/UVkKYKKGFVWp/FfsgVSzVae/n/WOsptPux05QBo1vgm ga5u3201CQoetbnCNK7WrfBHzVZpgSsJLWUOJgn52whmR435QG+4RBoyP50FCCMb MuWpjz7WxkYRulbVX+KaDqp80VyMaCcxTxjGnb7qkf9ZKEhpatHvOEtMle3EVpkD aoeo7r2QH9ODSn/kDOiB5Q4nfA/UK/x4TKQjP3Tb00Q09LCGo2BkgYjCU101GQ7b Z5r5mKNfvM1mHpAYWc/jK4ArHcBCNAuT3KC3+uZv5c
Bug#915971: marked as done (Document Resize on man page)
Your message dated Mon, 11 Jan 2021 23:04:47 + with message-id and subject line Bug#906918: fixed in util-linux 2.36.1-5 has caused the Debian Bug report #906918, regarding Document Resize on man page 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.) -- 906918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fdisk Version: 2.33-0.2 File: /sbin/cfdisk User choses Resize, and resizes a partition from 300 GB to 60 GB. But then when he tries to mount it, # mount /dev/sda5 /mnt/usb/thumb/ mount: /mnt/usb/thumb: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. # journalctl -f Dec 09 03:27:41 jidanni5 kernel: EXT4-fs (sda5): bad geometry: block count 103356160 exceeds size of device (15805440 blocks) So remove Resize or make it warn that any filesystems present will no longer be mountable if used. --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.36.1-5 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Jan 2021 22:03:06 + Source: util-linux Architecture: source Version: 2.36.1-5 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 906918 915971 Changes: util-linux (2.36.1-5) unstable; urgency=medium . * hwclock-set: remove useless source /etc/default/rcS * hwclock-set: remove stamp file. Since initramfs-tools 0.119 (jessie), hwclock-set is not installed in the initramfs anymore. This was the original reason for having the stamp file. * man cfdisk: Add upstream patch documenting resize command. Thanks to Vincent McIntyre (Closes: #915971, #906918) Checksums-Sha1: 71df18b228f245242d75b0bc9c79c610b732200e 4337 util-linux_2.36.1-5.dsc 1ca8c1883a63e84ad118f4bdc6ad4fe769b3bbce 97020 util-linux_2.36.1-5.debian.tar.xz c3105e0815ecdea3cf0b6319727b3087ced498fe 7051 util-linux_2.36.1-5_source.buildinfo Checksums-Sha256: 68a251f76b34cc5042d8c5637e353f6676582dc345ac997257af718849afbc32 4337 util-linux_2.36.1-5.dsc 251172b217691f15d96273ae22f34906d1e14310c9a56062a4be109047dda94e 97020 util-linux_2.36.1-5.debian.tar.xz 8a03fef72e390a6f2c9f3a4069ce654292c1d184b2b68c0044d8f665628dbabc 7051 util-linux_2.36.1-5_source.buildinfo Files: fc7a2b248618385afa43dff234276aa2 4337 base required util-linux_2.36.1-5.dsc 8fdf5e6fb41c66640fc4bcba37392682 97020 base required util-linux_2.36.1-5.debian.tar.xz c83c6a326384ab007df396681c1dd712 7051 base required util-linux_2.36.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl/81YoACgkQXBPW25MF LgP8Vg/+LKEgGTDznEA24SbCEPvmjgYg+MEakAkd5kzx8iNxKQ8WMZvnDIKq68A+ pVWnxRyKsCvIoqU45Aok2xUkYFQdakaa/pvPWwA8OhfU6d0KcSUZiGWvwjtPBUaU iVWYB6J1SrakBM8qb+Huv0xBzKGOarU8TS2aBff1C0vy2QddF+RxScZ7PXbgODUD 5y30Eh94Dq+BLNHXgL+bXjJQ9QeZGePlKs9F6IQnCyYlZ/Baisyt4qYk0Jd1GMmY wbTGk2dxL4gOLuZA2uXhttQbl84x+qbN+1FCCodTqzw1CqJcA3ZV+n+Blhk6J9NY NwkRQHP0M18CzUDHR/mf/UVkKYKKGFVWp/FfsgVSzVae/n/WOsptPux05QBo1vgm ga5u3201CQoetbnCNK7WrfBHzVZpgSsJLWUOJgn52whmR435QG+4RBoyP50FCCMb MuWpjz7WxkYRulbVX+KaDqp80VyMaCcxTxjGnb7qkf9ZKEhpatHvOEtMle3EVpkD aoeo7r2QH9ODSn/kDOiB5Q4nfA/UK/x4TKQjP3Tb00Q09LCGo2BkgYjCU101GQ7b Z5r5mKNfvM1mHpAYWc/jK4ArHcBCNAuT3KC3+uZv5c3l+Qs9IT57yEXBhqyJz8B0 DzTdc65mMwqIsh6yfmbx+sWPV6ww2rKqor19iFarmVzrEOegZAM= =zLqr -END PGP SIGNATURE End Message ---
Bug#972298: marked as done (okteta: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 22:55:57 + with message-id and subject line Bug#972298: fixed in okteta 5:0.26.4-2 has caused the Debian Bug report #972298, regarding okteta: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: okteta Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), okteta fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/okteta_0.26.4-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining okteta! live well, vagrant From f31c64a3960214e4b35f0d7b08bdcb53d81de2b3 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:35:14 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index c948de6..a5d0afc 100755 --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,9 @@ TESTS_HOME=$(CURDIR)/debian/tests.home +# Disable fixfilepath, as it causes build failures. +export DEB_BUILD_MAINT_OPTIONS = reproducible=-fixfilepath + l10npkgs_firstversion_ok := 4:16.04.3-7~ include /usr/share/pkg-kde-tools/qt-kde-team/2/l10n-packages.mk -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: okteta Source-Version: 5:0.26.4-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of okteta, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated okteta 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, 11 Jan 2021 23:28:57 +0100 Source: okteta Architecture: source Version: 5:0.26.4-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972298 Changes: okteta (5:0.26.4-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972298) . [ Aurélien COUDERC ] * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Refresh upstream metadata. * Update project homepage. * Removed George Kiagiadakis, Maximiliano Curia, Modestas Vainius from the uploaders, thanks for your work on the package! * Added myself to the uploaders. * Build with hardening=+all build hardening flag. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. Checksums-Sha1: eac29a894b6445af5c534dc61e69f107643ea496 3700 okteta_0.26.4-2.dsc fb3b22b9456448dbb2c9f712da11c6340753c5c7 29968 okteta_0.26.4-2.debian.tar.xz 81b32202423b003c5e3a440394f5254703c2c739 28640 okteta_0.26.4-2_
Bug#947603: marked as done (sysvinit service calls wrong binary path)
Your message dated Mon, 11 Jan 2021 22:56:26 + with message-id and subject line Bug#947603: fixed in vmtouch 1.3.1-2 has caused the Debian Bug report #947603, regarding sysvinit service calls wrong binary path 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.) -- 947603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vmtouch Version: 1.3.1-1 And: 1.3.0-1 Hey guys, this is a very embarrassing bug, did nobody actually test the service before merging this into stable repository? __ root@VM-Buster:~# grep '^DAEMON=' /etc/init.d/vmtouch DAEMON=/usr/sbin/vmtouch root@VM-Buster:~# which -a vmtouch /usr/bin/vmtouch /bin/vmtouch __ This is especially nasty since the service does not report any error in such case, so users will probably not even recognise that it failed: __ root@VM-Buster:~# systemctl restart vmtouch root@VM-Buster:~# systemctl status vmtouch ● vmtouch.service - LSB: Start vmtouch daemon Loaded: loaded (/etc/init.d/vmtouch; generated) Active: active (exited) since Sat 2019-12-28 14:56:02 CET; 9s ago Docs: man:systemd-sysv-generator(8) Process: 19876 ExecStart=/etc/init.d/vmtouch start (code=exited, status=0/SUCCESS) Dec 28 14:56:02 VM-Buster systemd[1]: Starting LSB: Start vmtouch daemon... Dec 28 14:56:02 VM-Buster systemd[1]: Started LSB: Start vmtouch daemon. root@VM-Buster:~# pgrep vmtouch __ Solution: __ root@VM-Buster:~# sed -i 's|/usr/sbin/vmtouch|/usr/bin/vmtouch|' /etc/init.d/vmtouch root@VM-Buster:~# systemctl daemon-reload root@VM-Buster:~# systemctl restart vmtouch root@VM-Buster:~# systemctl status vmtouch ● vmtouch.service - LSB: Start vmtouch daemon Loaded: loaded (/etc/init.d/vmtouch; generated) Active: active (running) since Sat 2019-12-28 14:57:35 CET; 10s ago Docs: man:systemd-sysv-generator(8) Process: 19907 ExecStart=/etc/init.d/vmtouch start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 2387) Memory: 828.0K CGroup: /system.slice/vmtouch.service └─19911 /usr/bin/vmtouch -d -l -m 1 /boot/dietpi Dec 28 14:57:35 VM-Buster systemd[1]: Starting LSB: Start vmtouch daemon... Dec 28 14:57:35 VM-Buster vmtouch[19907]: Starting: vmtouch. Dec 28 14:57:35 VM-Buster systemd[1]: Started LSB: Start vmtouch daemon. root@VM-Buster:~# pgrep vmtouch 19911 __ Since one can choose the run user via /etc/default/vmtouch, moving the binary to sbin seems to be the worse alternative solution. Best regards, MichaIng --- End Message --- --- Begin Message --- Source: vmtouch Source-Version: 1.3.1-2 Done: Lucas Nussbaum We believe that the bug you reported is fixed in the latest version of vmtouch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Nussbaum (supplier of updated vmtouch 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, 11 Jan 2021 23:32:44 +0100 Source: vmtouch Architecture: source Version: 1.3.1-2 Distribution: unstable Urgency: medium Maintainer: Lucas Nussbaum Changed-By: Lucas Nussbaum Closes: 947603 Changes: vmtouch (1.3.1-2) unstable; urgency=medium . * Fix path of binary in init script. Closes: #947603 * Upgrade to watch file format version 4 * Add upstream metadata * Bump debhelper compat level to 13 * Add Rules-Requires-Root: no * Add patch to add CPPFLAGS to cc invocation * Bump Standards-Version to 4.5.1 Checksums-Sha1: 9f51f2504bb251cb7fd80f5eea690365d074296f 1902 vmtouch_1.3.1-2.dsc e9b04d091a147e49a66af235ea98631749b12811 3916 vmtouch_1.3.1-2.debian.tar.xz 7da3bb2c42e1b306e0f453a7331ce57443f0f2a5 5581 vmtouch_1.3.1-2_source.buildinfo Checksums-Sha256: 0c3c1559c3d364d5c6aab10a543c04afca2dec5d584511779a8bf0ed8decfd41 1902 vmtouch_1.3.1-2.dsc 86b9d5d8fc4660f4783f11fdc5bace9dfca85ca8a87f2a61f09c8598100e6658 3916 vmtouch_1.3.1-2.debian.tar.xz a65f733480e70d641b96b075a6c957c8618b23328a028a1ad16f8a5c981b55b6 5581 vmtouch_1.3.1-2_source.buildinfo Files: 2476c7221aab8632e91855627d643709 1902 ad
Processed: ITP: usockets-dev -- miniscule async eventing, networking & crypto library
Processing commands for cont...@bugs.debian.org: > close 979852 Bug #979852 [wnpp] ITP: usockets-dev -- miniscule async eventing, networking & crypto library Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 979852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979261: marked as done (Stop using deprecated systemd-resolve tool)
Your message dated Mon, 11 Jan 2021 22:34:17 +
with message-id
and subject line Bug#979261: fixed in ltsp 21.01-1
has caused the Debian Bug report #979261,
regarding Stop using deprecated systemd-resolve tool
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.)
--
979261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ltsp
Version: 20.06-1
Severity: normal
Tags: patch
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: resolvectl
Hi,
systemd-resolve has been replaced by the resolvectl tool in systemd v239
(i.e. is available since buster). This is from the systemd release
notes:
* The systemd-resolve tool has been renamed to resolvectl (it also
remains available under the old name, for compatibility), and its
interface is now verb-based, similar in style to the other ctl
tools, such as systemctl or loginctl.
systemd-resolve is nowadays merely a symlink pointing at resolvectl and
we'd like to get rid of this compat symlink at some point.
Your package uses the old name like this:
$ grep -E "systemd-resolve\b" -R
ltsp/server/dnsmasq/55-dnsmasq.sh:# Jessie doesn't have systemd-resolve
ltsp/server/dnsmasq/55-dnsmasq.sh:if is_command systemd-resolve; then
ltsp/server/dnsmasq/55-dnsmasq.sh:dns_server=$(LANG=C.UTF-8 rw
systemd-resolve --status |
Attached is a patch which uses resolvectl instead.
Please review and consider applying it in your next upload.
It would be great if you can make this upload before the bullseye
release, so we can safely drop the symlink in bullseye+1.
Regards,
Michael
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ltsp depends on:
ii busybox 1:1.30.1-6
ii openssh-client [ssh-client] 1:8.4p1-3
ii procps 2:3.3.16-5
ii python3 3.9.1-1
ii systemd 247.2-4
Versions of packages ltsp recommends:
ii man-db 2.9.3-2
ii sshfs 3.7.1+repack-1
Versions of packages ltsp suggests:
pn dnsmasq
pn epoptes
ii ethtool 1:5.9-1
pn ltsp-binaries | ipxe
ii net-tools 1.60+git20181103.0eebece-1
pn nfs-kernel-server
ii openssh-server1:8.4p1-3
ii squashfs-tools1:4.4-2
diff --git a/ltsp/server/dnsmasq/55-dnsmasq.sh
b/ltsp/server/dnsmasq/55-dnsmasq.sh
index 09cc69d..9194262 100644
--- a/ltsp/server/dnsmasq/55-dnsmasq.sh
+++ b/ltsp/server/dnsmasq/55-dnsmasq.sh
@@ -56,9 +56,9 @@ dns_server() {
return 0
fi
dns_server=
-# Jessie doesn't have systemd-resolve
-if is_command systemd-resolve; then
-dns_server=$(LANG=C.UTF-8 rw systemd-resolve --status |
+# Stretch doesn't have resolvectl
+if is_command resolvectl; then
+dns_server=$(LANG=C.UTF-8 rw resolvectl status |
sed -n '/DNS Servers:/,/:/s/.* \([0-9.]\{7,15\}\).*/\1/p' |
grep -v '^127.0.' |
tr '\n' ',')
--- End Message ---
--- Begin Message ---
Source: ltsp
Source-Version: 21.01-1
Done: Vagrant Cascadian
We believe that the bug you reported is fixed in the latest version of
ltsp, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vagrant Cascadian (supplier of updated ltsp 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, 11 Jan 2021 14:22:12 -0800
Source: ltsp
Architecture: source
Version: 21.01-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LTSP Maintainers
Changed-By: Vagrant Cascadian
Closes: 979261
Changes:
ltsp (21.01-1) unstable; urgency=medium
.
[ A
Bug#972390: marked as done (manpage formatting problems)
Your message dated Mon, 11 Jan 2021 22:24:48 + with message-id and subject line Bug#972390: fixed in intelrdfpmath 2.0u2-4 has caused the Debian Bug report #972390, regarding manpage formatting problems 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.) -- 972390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libintelrdfpmath-dev Version: 2.0u2-3 Severity: minor Dear Maintainer, The formatting of the manpage is incorrect in the last section “Functions Added in Release 2.0”. The list of functions there is compacted on one single long line, while in the original README it occupies many lines. Also, it seems that the manpage is not generated at build time from the README. So it may easily become outdated in future upstream releases. All in all, I’m wondering whether it may not be easier to simply ship the README under /usr/share/doc/. It will never be outdated, and will be easier to discover for users. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org --- End Message --- --- Begin Message --- Source: intelrdfpmath Source-Version: 2.0u2-4 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of intelrdfpmath, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated intelrdfpmath 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, 11 Jan 2021 22:55:21 +0100 Source: intelrdfpmath Architecture: source Version: 2.0u2-4 Distribution: unstable Urgency: medium Maintainer: Christian Stalp Changed-By: Stephen Kitt Closes: 970790 972390 Changes: intelrdfpmath (2.0u2-4) unstable; urgency=medium . * Avoid conflicting declarations of wchar_t; thanks to Sébastien Villemot for the patch! Closes: #970790. * Ship the original README instead of the converted man page. Closes: #972390. * Standards-Version 4.5.1, no change required. Checksums-Sha1: e9af9f3c8d6154c0f0c5e6e762abf90320951537 1992 intelrdfpmath_2.0u2-4.dsc 8a6b34fe125a2af43328ff251318d7ca47221446 4504 intelrdfpmath_2.0u2-4.debian.tar.xz 7b16e16af6bf6ed64af80a254f63f0ae81df0f7b 5945 intelrdfpmath_2.0u2-4_source.buildinfo Checksums-Sha256: d3ca68d7aa6c4ebddbcd623fa4b8f77798e5ee560905501b68a757ffa4dadcf5 1992 intelrdfpmath_2.0u2-4.dsc c1e09321b2a28297225a0996568a5edbba5d0b66612327e3a4acd56ef80da15d 4504 intelrdfpmath_2.0u2-4.debian.tar.xz 867b5d53b53bd46d5869d2de820f4cfdae191be7e88c87e404e4930f572783a1 5945 intelrdfpmath_2.0u2-4_source.buildinfo Files: 148ac84436a1c5bf59c83cb7298e3d52 1992 libdevel optional intelrdfpmath_2.0u2-4.dsc 587f48ac20113ad3167bb8fde7c0708d 4504 libdevel optional intelrdfpmath_2.0u2-4.debian.tar.xz 5b938f1df82348efef173c4eef5e91eb 5945 libdevel optional intelrdfpmath_2.0u2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl/8yVQACgkQgNMC9Yht g5zD5g/9FkHe4biw3WxzUtHXJsmD90uv/4yHjb4GZhJCir9aGNic37kqVK24WqC7 bOeb3yUsVrdi1HsCWyqSy9TmoOeB0ypVdo6lSuJRFDdRGuJ2AQg8oUXH1H10PBR9 KPfOx5TFD+VKCe5e3T08p16cDYyA10+AkxIGa1z3FxHy7vp5eMo7jGYcrtgBtswu DmhmcJ4erU8m5g2yn3cP4857VMZAMDz9rcchxSzwDFGs59LNOaGHUY6zY+Z+J1jv cvjbE+AqycTokxpSGRn7Gwax+Xlik0kTsNZLjGzb/VrS2oFsLIqJ8O2IEoDQJ7Cd dZ/UkchAzcKj+LYgPvxQEtaht1lh8IDeWcL2LJgjY4NSn28apBSA/rM7ECmctCPS ZPry5su1BdBsRWjnFssxs8ZgNVB6r593OJP7LkW93Ig+HnZAPJIEQfgDOf+mMlgF 6Q92DRGo2308eV/QgkQgHTu9iVHuICArkcuGzGvWiAotB+ykhdfAg4ytSbOkNC4Y /FkWtX75iun43tjwagAw4GazA27O3Rnv5JUI5J9fDgfUVCq5BOPV7XqevNzz6OVS +yHK5TQqfVyzj62zno16uBds4G/ULIfGwuR55sZxUix+bhpXF47HrieDiQOLlhP5 yhnydqOUwZNx5bd249S0q762CSxeFGM4G8fwgJ5inI5x8n31UcU= =Yeh+ -END PGP SIGNATURE End Message ---
Bug#979346: marked as done (ITP: golang-github-go-co-op-gocron -- easy and fluent Go cron scheduling)
Your message dated Mon, 11 Jan 2021 22:00:11 + with message-id and subject line Bug#979346: fixed in golang-github-go-co-op-gocron 0.5.0-1 has caused the Debian Bug report #979346, regarding ITP: golang-github-go-co-op-gocron -- easy and fluent Go cron scheduling 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.) -- 979346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Cyril Brulebois * Package name: golang-github-go-co-op-gocron Version : 0.5.0-1 Upstream Author : Go Co Op * URL : https://github.com/go-co-op/gocron * License : BSD-2-clause Programming Lang: Go Description : easy and fluent Go cron scheduling goCron is a Golang job scheduling package which lets one run Go functions periodically at pre-determined interval using a simple, human-friendly syntax. . goCron is a Golang implementation of Ruby module clockwork and Python job scheduling package schedule. Part of the crowdsec packaging effort: https://lists.debian.org/debian-go/2020/12/msg00019.htm Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: golang-github-go-co-op-gocron Source-Version: 0.5.0-1 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-go-co-op-gocron, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-go-co-op-gocron 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, 05 Jan 2021 15:54:44 + Source: golang-github-go-co-op-gocron Binary: golang-github-go-co-op-gocron-dev Architecture: source all Version: 0.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Description: golang-github-go-co-op-gocron-dev - easy and fluent Go cron scheduling Closes: 979346 Changes: golang-github-go-co-op-gocron (0.5.0-1) unstable; urgency=medium . * Initial release (Closes: #979346). Checksums-Sha1: 66960f796fe689920d5b1d5a74ea74567a52014c 2307 golang-github-go-co-op-gocron_0.5.0-1.dsc df121a7de6ae36b09a1d26a9c54b38618319dc04 18440 golang-github-go-co-op-gocron_0.5.0.orig.tar.gz d8b98da5315db6d6ae33415ce75231147be04e4b 2684 golang-github-go-co-op-gocron_0.5.0-1.debian.tar.xz 3439542d03b6e886b47ac901443fd2e914bcb652 15172 golang-github-go-co-op-gocron-dev_0.5.0-1_all.deb 0eb582ff810c7ec383d62cedb1b547683645e7b3 6489 golang-github-go-co-op-gocron_0.5.0-1_amd64.buildinfo Checksums-Sha256: 75fa4d4c2dcd033d0601f3655db1056f9ffca12d4a221f32e201cdb373d6e750 2307 golang-github-go-co-op-gocron_0.5.0-1.dsc 88dc7fcdb1eaeba2d750407d1b03f2f6adb67e3c4ca6cd350aa770efc6ba562f 18440 golang-github-go-co-op-gocron_0.5.0.orig.tar.gz ea38173084a1a43e2a65ed5ce13959c321036942aaaf2f481f36715b9ae5c64e 2684 golang-github-go-co-op-gocron_0.5.0-1.debian.tar.xz d9ea267d59eb744a4adb5b4505d5c2ac5bb8adb7800214ee377000378949 15172 golang-github-go-co-op-gocron-dev_0.5.0-1_all.deb 53bf794dc03065b5b5f0b11065e3f58cae39aadf1f131e36051c26fc4b688e48 6489 golang-github-go-co-op-gocron_0.5.0-1_amd64.buildinfo Files: 1ac1278b066cf983af7e820875742ea3 2307 golang optional golang-github-go-co-op-gocron_0.5.0-1.dsc ac34742744fcdcf8d1237066d25c5fba 18440 golang optional golang-github-go-co-op-gocron_0.5.0.orig.tar.gz 834898ea73c78ffbc6ab5eef9bc9bf38 2684 golang optional golang-github-go-co-op-gocron_0.5.0-1.debian.tar.xz 7b8b6e9d115367234e99aa294a4df36a 15172 golang optional golang-github-go-co-op-gocron-dev_0.5.0-1_all.deb eba611ff514cd15939de61a720d6e1c5 6489 golang optional golang-github-go-co-op-gocron_0.5.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl/0jRgQHGtpYmlAZGVi aWFuLm9yZwAKCRD/kUrwwrNVIIACD/4uz01o7C5ez0P4019HFpORSPeyzEen0uOn hbuF2fzBGnM9rpNl39xutrteM+QC0jt38bwfvKATCjohz8TEfigd6XSZi
Bug#979271: marked as done (ITP: golang-github-alecaivazis-survey -- golang library for building interactive prompts)
Your message dated Mon, 11 Jan 2021 22:00:11 + with message-id and subject line Bug#979271: fixed in golang-github-alecaivazis-survey 2.2.7+ds1-1 has caused the Debian Bug report #979271, regarding ITP: golang-github-alecaivazis-survey -- golang library for building interactive prompts 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.) -- 979271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Cyril Brulebois * Package name: golang-github-alecaivazis-survey Version : 2.2.7-1 Upstream Author : Alec Aivazis * URL : https://github.com/AlecAivazis/survey * License : Expat Programming Lang: Go Description : golang library for building interactive prompts This library helps build interactive prompts. It features: - Various types of prompt (input, multiline, password, confirmation, select, multiselect, editor) - Filtering options - Keeping the filter alive - Validation - Help text - Updating icons - Custom types . Testing can be performed via the go-expect package. Part of the crowdsec packaging effort: https://lists.debian.org/debian-go/2020/12/msg00019.html Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: golang-github-alecaivazis-survey Source-Version: 2.2.7+ds1-1 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-alecaivazis-survey, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-alecaivazis-survey 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, 04 Jan 2021 19:27:34 + Source: golang-github-alecaivazis-survey Binary: golang-github-alecaivazis-survey-dev Architecture: source all Version: 2.2.7+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Description: golang-github-alecaivazis-survey-dev - golang library for building interactive prompts Closes: 979271 Changes: golang-github-alecaivazis-survey (2.2.7+ds1-1) unstable; urgency=medium . * Initial release (Closes: #979271). Checksums-Sha1: 59bdaa9a941e5dcc89aa12833d2de32ea54b3876 2589 golang-github-alecaivazis-survey_2.2.7+ds1-1.dsc e131d7b5151ccf67e9c18b0627b7ae547e1ddb2d 105412 golang-github-alecaivazis-survey_2.2.7+ds1.orig.tar.xz 66ee288477f5e1b99b7bf0b15313e8743a2c016c 2928 golang-github-alecaivazis-survey_2.2.7+ds1-1.debian.tar.xz 85edd462a8cf3a7c4f4888b00136faf63514e6f2 38264 golang-github-alecaivazis-survey-dev_2.2.7+ds1-1_all.deb 549f3b01a3eec92f066ba115a581c87fa2dd8630 7920 golang-github-alecaivazis-survey_2.2.7+ds1-1_amd64.buildinfo Checksums-Sha256: ddf6430f010d20aebeed4c0822e6576430e600c762aea6ced9363e048162df79 2589 golang-github-alecaivazis-survey_2.2.7+ds1-1.dsc cde1bfc9c10c9c69cb70f7133467a5ad112cb43e9b45a4dd966060cecfa62274 105412 golang-github-alecaivazis-survey_2.2.7+ds1.orig.tar.xz d689ff87e1d185817400792b0a0e9487d2c336a32040e2db5ecf4f90bcd60533 2928 golang-github-alecaivazis-survey_2.2.7+ds1-1.debian.tar.xz 483ba2ff6a3506f6180a934966842b42b9d3701b1df7a2bba0a7e319c5d75aac 38264 golang-github-alecaivazis-survey-dev_2.2.7+ds1-1_all.deb fe4408b6c266dc166b04487cabc1c069160083eda20fcbfe86a874ef93562bc2 7920 golang-github-alecaivazis-survey_2.2.7+ds1-1_amd64.buildinfo Files: d7bb43846334807770287850c7a06a51 2589 golang optional golang-github-alecaivazis-survey_2.2.7+ds1-1.dsc 7451234318905150a4d913911b492567 105412 golang optional golang-github-alecaivazis-survey_2.2.7+ds1.orig.tar.xz c01c736a778d390462b96bef2612f13c 2928 golang optional golang-github-alecaivazis-survey_2.2.7+ds1-1.debian.tar.xz 1a8de8fdc7ee09a92350dd2c3f3f1303 38264 golang optional golang-github-alecaivazis-survey-dev_2.2.7+ds1-1_all.deb d7e792b5c764922ca4776e5af4a50900 7920 golang optional golang-githu
Bug#979262: marked as done (ITP: golang-github-hinshun-vt10x -- vt10x terminal emulation backend)
Your message dated Mon, 11 Jan 2021 22:00:11 + with message-id and subject line Bug#979262: fixed in golang-github-hinshun-vt10x 0.0~git20180809.d55458d+ds1-1 has caused the Debian Bug report #979262, regarding ITP: golang-github-hinshun-vt10x -- vt10x terminal emulation backend 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.) -- 979262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Cyril Brulebois * Package name: golang-github-hinshun-vt10x Version : 0.0~git20180809.d55458d-1 Upstream Author : Edgar Lee * URL : https://github.com/hinshun/vt10x * License : Expat Programming Lang: Go Description : vt10x terminal emulation backend This package is a vt10x terminal emulation backend, influenced largely by st, rxvt, xterm, and iTerm as reference. It can be used for terminal muxing, as a terminal emulation frontend, or wherever terminal emulation is needed. Part of the crowdsec packaging effort: https://lists.debian.org/debian-go/2020/12/msg00019.html Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: golang-github-hinshun-vt10x Source-Version: 0.0~git20180809.d55458d+ds1-1 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-hinshun-vt10x, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-hinshun-vt10x 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, 04 Jan 2021 18:19:02 + Source: golang-github-hinshun-vt10x Binary: golang-github-hinshun-vt10x-dev Architecture: source all Version: 0.0~git20180809.d55458d+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Description: golang-github-hinshun-vt10x-dev - vt10x terminal emulation backend Closes: 979262 Changes: golang-github-hinshun-vt10x (0.0~git20180809.d55458d+ds1-1) unstable; urgency=medium . * Initial release (Closes: #979262). Checksums-Sha1: bfda66be33c68d4afd85d7a27208e90a45a71df6 2549 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.dsc f7685c4daef78ae1090df37ce1c3afeacbfa2002 13424 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1.orig.tar.xz 3c2cfb28d0a59c9fd63db7ff6674f35e066364c4 2816 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.debian.tar.xz 77c16aa080bf53f617b4c62d5bb08e93d8f334d7 13192 golang-github-hinshun-vt10x-dev_0.0~git20180809.d55458d+ds1-1_all.deb e77edbd73094c4e5ea1517846911a82762f4af5f 7704 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1_amd64.buildinfo Checksums-Sha256: 1bb1f04cd43fd0b9e4cf0aff612f07db4eeb32ea767464b89a434f56ed7c51ee 2549 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.dsc 784d91e1e376ba350fd756c7c4cc4f36bea462b4989a558770149fd749477b51 13424 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1.orig.tar.xz 47c3bc8ba34a3b3e83d1b87e03f41be510070bdbfbd3388f373debc8ff4f9120 2816 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.debian.tar.xz 6e0183d5687fcff16393e9012e3ef1b30a2f774863240bfa0dc9a9cd6ddc9ec9 13192 golang-github-hinshun-vt10x-dev_0.0~git20180809.d55458d+ds1-1_all.deb 2574fac6b7ee85c22e13859287e6246ff62484229f543dc19d6882325649c756 7704 golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1_amd64.buildinfo Files: 0038f3782ffabf9fed43930b465a5398 2549 golang optional golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.dsc 9680b408c2bfed90a26d9ead2d70a9b2 13424 golang optional golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1.orig.tar.xz 52fdd7fbdf632b32b82ab237e8a08cf0 2816 golang optional golang-github-hinshun-vt10x_0.0~git20180809.d55458d+ds1-1.debian.tar.xz c36ac6448a6c0e39727527ef8e221189 13192 golang optional golang-github-hinshun-vt10x-dev_0.0~git20180809.d55458d+ds1-1_all.deb 40a3f80
Bug#979251: marked as done (ITP: golang-github-netflix-go-expect -- expect-like golang library to automate terminal/console interactions)
Your message dated Mon, 11 Jan 2021 22:00:11 + with message-id and subject line Bug#979251: fixed in golang-github-netflix-go-expect 0.0~git20201125.85d881c-1 has caused the Debian Bug report #979251, regarding ITP: golang-github-netflix-go-expect -- expect-like golang library to automate terminal/console interactions 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.) -- 979251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Cyril Brulebois * Package name: golang-github-netflix-go-expect Version : 0.0~git20201125.85d881c-1 Upstream Author : Netflix, Inc. * URL : https://github.com/Netflix/go-expect * License : Apache-2.0 Programming Lang: Go Description : expect-like golang library to automate terminal/console interactions This package provides an expect-like interface to automate control of applications. It is unlike expect in that it does not spawn or manage process lifecycle. This package only focuses on expecting output and sending input through its pseudoterminal. Part of the crowdsec packaging effort: https://lists.debian.org/debian-go/2020/12/msg00019.html Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: golang-github-netflix-go-expect Source-Version: 0.0~git20201125.85d881c-1 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-netflix-go-expect, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-netflix-go-expect 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, 04 Jan 2021 17:26:30 + Source: golang-github-netflix-go-expect Binary: golang-github-netflix-go-expect-dev Architecture: source all Version: 0.0~git20201125.85d881c-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Description: golang-github-netflix-go-expect-dev - expect-like golang library to automate terminal/console interacti Closes: 979251 Changes: golang-github-netflix-go-expect (0.0~git20201125.85d881c-1) unstable; urgency=medium . * Initial release (Closes: #979251). Checksums-Sha1: 9be8f769fc1ce2170a4054b1c249e25646041688 2475 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1.dsc f62bfbc6bd8b3a7b5756184270e6c76be470ee52 14160 golang-github-netflix-go-expect_0.0~git20201125.85d881c.orig.tar.xz 33cc7faf799c29cc7f5b2bef79bab84b545be344 2508 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1.debian.tar.xz 1d08d24a6cbf410a6fc75be3e3805430975e53ca 11692 golang-github-netflix-go-expect-dev_0.0~git20201125.85d881c-1_all.deb 4570ead3c77b4c58447ac4565f17bde593c4d5f7 6670 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1_amd64.buildinfo Checksums-Sha256: 9dbd41bc206ac395fb70d3fffa85d13239477ea3ed758ebbebbad10262ce42f2 2475 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1.dsc c59008a8c5aa2898df8053709d3f7acce18effc35f05ef36d23814409254843e 14160 golang-github-netflix-go-expect_0.0~git20201125.85d881c.orig.tar.xz a4ed1c4b99d37eea4d9a0ab99cfaf7dc651bace599514a5588de4c50336bfadb 2508 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1.debian.tar.xz a07635ee969b3b17bf9d61db90c6a1f16ebce77b6544996427df608d03774e35 11692 golang-github-netflix-go-expect-dev_0.0~git20201125.85d881c-1_all.deb c17a82af85d08cfd610fa5ee61bcd8425f779aa0c14cfb9db4ef70499bfee24a 6670 golang-github-netflix-go-expect_0.0~git20201125.85d881c-1_amd64.buildinfo Files: ebdc445ba33b89f4805afde0b1e90d5c 2475 golang optional golang-github-netflix-go-expect_0.0~git20201125.85d881c-1.dsc 0a92bbeb56ac7738743c32e507238fcc 14160 golang optional golang-github-netflix-go-expect_0.0~git20201125.85d881c.orig.tar.xz 6812ae2caee245a2e37108cba80adb04 2508 golang optional golang-github-netflix-go-expect_0.0~gi
Bug#978101: marked as done (radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini)
Your message dated Mon, 11 Jan 2021 22:57:18 +0100 with message-id <161040223874.3767517.327093367459245...@auryn.jones.dk> and subject line Re: Bug#978101: radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini has caused the Debian Bug report #978101, regarding radicale: libapache2-mod-proxy-uwsgi needs to be dep: not sug:, no hint for filessystem_folder in radicale.ini 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.) -- 978101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: radicale Version: 2.1.11-6 Severity: important Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing radicale. On buster, I found out that this doesn't change in testing or unstable. * What exactly did you do (or not do) that was effective (or ineffective)? I did not installed libapache2-mod-proxy-uwsgi and I have changed filesystem_folder in /etc/radicale/config. * What was the outcome of this action? Radicale did not work. And it took me days to find out that libapache2-mod-proxy-uwsgi needed to be installed. And it didn't work because I have changed the filesystem_folder without changing /etc/uwsgi/apps-available/radicale.ini. * What outcome did you expect instead? I expected that (after necessary configuration) Radicale would work more or less out of the box. I have three suggestions: 1) the suggested way is to run Radicale with Apache and UWSGI. Therefore, libapache2-mod-proxy-uwsgi is necessary and not to be marked as suggested. 2) there must be a hint that changing filesystem_folder in /etc/radicale/config needs changes in /etc/uwsgi/apps-available/radicale.ini and maybe in the home directory of user radicale. 3) the description in radicale.README.Debian needs to be extened. I am willing to contribute an explaination that would have empowered myself to have the service up and running in a short time. This should be helpful for others, too. *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages radicale depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii lsb-base 10.2019051400 ii python3 3.7.3-1 ii python3-radicale 2.1.11-6 Versions of packages radicale recommends: ii ssl-cert 1.0.39 Versions of packages radicale suggests: ii apache2 2.4.38-3+deb10u4 ii apache2-utils 2.4.38-3+deb10u4 ii libapache2-mod-proxy-uwsgi 2.4.38-3+deb10u4 ii python3-bcrypt 3.1.6-1 ii python3-passlib 1.7.1-1 ii uwsgi 2.0.18-1 ii uwsgi-plugin-python32.0.18-1 -- Configuration Files: /etc/radicale/config changed [not included] /etc/radicale/logging changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Control: retitle -1 radicale: documentation is confusing Quoting Flo (2020-12-26 19:23:01) > In radicale.README.Debian at the point '## Apache via uWSGI with PAM > authentication' it says: 'Install needed packages:' with some packages > to install. But not libapache2-mod-proxy-uwsgi . This is missing. libapache2-mod-proxy-uwsgi 2.4.38-3+deb10u4 which you reported using is a transitional package - i.e. it does not contain anything. The needed module is nowadays included with apache2. > The brutal thing is, that the error messages in log files did not show > that this package is missing (at least not for me). If you followed README.Debian the uWSGI module really was missing then either this command would fail: a2enmod proxy_uwsgi ...or if the config snippet for the module existed without the module code, then this would fail: service apache2 restart So it seems that something else went wrong at your system than that package/module missing. > >> 2) there must be a hint that changing filesystem_folder in
Bug#979822: marked as done (postgresql-13: Claims to connect to port 5434 but does not)
Your message dated Mon, 11 Jan 2021 22:32:03 +0100 with message-id and subject line Re: Bug#979822: postgresql-13: Claims to connect to port 5434 but does not has caused the Debian Bug report #979822, regarding postgresql-13: Claims to connect to port 5434 but does not 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.) -- 979822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-13 Version: 13.1-1+b1 Severity: normal Short bug report: = from the postregsql log: 2021-01-11 18:20:07.039 CET [969840] LOG: PostgreSQL 13.1 (Debian 13.1-1+b1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.0-18) 10.2.0, 64-bit startet 2021-01-11 18:20:07.039 CET [969840] LOG: erwarte Verbindungen auf IPv4-Adresse »127.0.0.1«, Port 5434 (in english: expecting connection on IPv4 address "127.0.0.1", port 5434). 2021-01-11 18:20:07.078 CET [969840] LOG: Datenbanksystem ist bereit, um Verbindungen anzunehmen (in english: Database system is ready to accept connections) However: netstat -nlp | grep 5432 And clients complain that connection is not possible on that port. Long version: (aka: What lead up to this) = I'm running postgresql for ages. Until a few days ago I had version 11, 12 and 13 installed. The client was from 13, the server was running version 11. I intended to upgrade the server but made a mistake: I dropped the cluster on version 11, not 13 to prepare the upgrade. As I'm regularly backing up (including database dumps) I decided to simply (probably bad idea?) import the dump into version 13. However, I could not connect to the database afterwards. I removed postgresql 11 and 12, but no change. After (finally) reading the man page of pg_wrapper, I could connect. However, I needed to explicitly pass "--cluster 13/main" to psql. I did this, but found out that I could work around this explicit flag by adding helge * 13 main* to /etc/postgresql-common/user_clusters (This file was untouched before). However, this does not help if I try to acces via other methods, like in perl scripts (same user) or in PHP scripts (different user, added that in user_clusters as well). So I'm now trying to track this down, but to no avail so far. What really makes me think in circles is that the server happily tells me he is listening on port 5434 but actually does not, so I'm a bit lost how to proceed debugging this. If you have an idea, besides the bug reported above, how to revert to the 11 behaviour (simply connecting to the db server running on port 5434 without needing to edit user_clusters and other files) I would be more than happy :-)) [I have modified pg_hba.conf, but I tried both with the stock install and the version of "pg_hba.conf" I used with postgresql-11, no change detected both in behaviour and (non) error output] -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.3 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-13 depends on: ii debconf [debconf-2.0] 1.5.74 ii libc6 2.31-9 ii libgcc-s1 10.2.1-3 ii libgssapi-krb5-2 1.18.3-4 ii libicu67 67.1-5 ii libldap-2.4-2 2.4.56+dfsg-1 ii libllvm11 1:11.0.0-5+b1 ii libpam0g 1.3.1-5 ii libpq5 13.1-1+b1 ii libselinux13.1-2+b2 ii libssl1.1 1.1.1i-1 ii libstdc++6 10.2.1-3 ii libsystemd0247.2-4 ii libuuid1 2.36.1-4 ii libxml22.9.10+dfsg-6.3+b1 ii libxslt1.1 1.1.34-4 ii locales2.31-9 ii postgresql-client-13 13.1-1+b1 ii postgresql-common 223 ii ssl-cert 1.1.0 ii tzdata 2020f-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages postgresql-13 recommends: pn sysstat postgresql-13 suggests no packages. -- debconf information: postgresql-13/postrm_purge_data: true -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 956778 parcellite
Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator
Bug reassigned from package 'src:parcellite' to 'parcellite'.
No longer marked as found in versions parcellite/1.2.1-3.
Ignoring request to alter fixed versions of bug #956778 to the same values
previously set
> forcemerge 909651 956778
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Bug #956778 [parcellite] parcellite: Depends on deprecated libappindicator
Severity set to 'normal' from 'serious'
895037 was blocked by: 956765 956771 956777 974146 956778 956770 956761 956775
956767 956768 956782 956780 921339 956779 977156 956764 956766 956773 956772
956781 956769 956774 956776 906026 956762
895037 was blocking: 895038
Removed blocking bug(s) of 895037: 956778
Marked Bug as done
Marked as fixed in versions parcellite/1.2.1-4.
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Added tag(s) sid, bullseye, and pending.
Merged 909651 956778
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
895037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037
909651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909651
956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964791: marked as done (libclc-amdgcn: OpenCL fails to start)
Your message dated Tue, 12 Jan 2021 02:13:22 +0600 with message-id and subject line Re: Bug#964791: libclc-amdgcn: OpenCL fails to start has caused the Debian Bug report #964791, regarding libclc-amdgcn: OpenCL fails to start 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.) -- 964791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libclc-amdgcn Version: 0.2.0+git20190827-6 Severity: important Tags: upstream X-Debbugs-Cc: sajjadkabir...@gmail.com Dear Maintainer, OpenCL fails to initiate (and any program using it). For example, clinfo shows this: : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options I am using AMD Kaveri APU (R7 graphics) with AMDGPU. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libclc-amdgcn depends on: ii libclang-common-10-dev 1:10.0.1~+rc4-1 ii libclc-dev 0.2.0+git20190827-6 libclc-amdgcn recommends no packages. libclc-amdgcn suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Solved --- End Message ---
Processed: icu: autopkgtest failure (fixed in experimental)
Processing control commands: > close -1 68.2-1 Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental) Marked as fixed in versions icu/68.2-1. Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental) Marked Bug as done -- 979836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979753: marked as done (nmu: viking_1.8-4)
Your message dated Mon, 11 Jan 2021 20:29:29 +0100 with message-id and subject line Re: Bug#979753: nmu: viking_1.8-4 has caused the Debian Bug report #979753, regarding nmu: viking_1.8-4 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.) -- 979753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please rebuild viking (1.8-4) with the new mapnik in unstable: nmu viking_1.8-4 . ANY . unstable . -m "Rebuild against libmapnik3.1" dw viking_1.8-4 . ANY . unstable . -m "libmapnik-dev (>= 3.1.0)" Kind Regards, Bas --- End Message --- --- Begin Message --- On 2021-01-11 07:14:57 +0100, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Please rebuild viking (1.8-4) with the new mapnik in unstable: > > nmu viking_1.8-4 . ANY . unstable . -m "Rebuild against libmapnik3.1" > dw viking_1.8-4 . ANY . unstable . -m "libmapnik-dev (>= 3.1.0)" Scheduled Cheers > > Kind Regards, > > Bas > -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#979792: marked as done (nmu: user-mode-linux_5.10um1)
Your message dated Mon, 11 Jan 2021 20:29:14 +0100 with message-id and subject line Re: Bug#979792: nmu: user-mode-linux_5.10um1 has caused the Debian Bug report #979792, regarding nmu: user-mode-linux_5.10um1 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.) -- 979792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu user-mode-linux_5.10um1 . ANY . unstable . -m "Re-build package to pick latest Linux 5.10.5 changes" -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 2021-01-11 17:45:27 +0530, Ritesh Raj Sarraf wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu user-mode-linux_5.10um1 . ANY . unstable . -m "Re-build package to pick > latest Linux 5.10.5 changes" Scheduled Cheers > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (990, 'unstable'), (990, 'testing'), (500, 'stable-updates'), > (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) > Kernel taint flags: TAINT_USER > Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Processed: src:colord: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 1.4.5-2
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions colord/1.4.5-2.
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 978167
Bug #979831 {Done: Paul Gevers } [src:colord] src:colord:
fails to migrate to testing for too long: unresolved RC bug
979831 was not blocked by any bugs.
979831 was not blocking any bugs.
Added blocking bug(s) of 979831: 978167
--
979831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#974572: marked as done (libwww-perl: LWP::UserAgent Authen Digest POST message-digest broken/ineffective)
Your message dated Mon, 11 Jan 2021 18:18:46 +
with message-id
and subject line Bug#974572: fixed in libwww-perl 6.52-1
has caused the Debian Bug report #974572,
regarding libwww-perl: LWP::UserAgent Authen Digest POST message-digest
broken/ineffective
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.)
--
974572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwww-perl
Version: 6.36-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
while implementing Digest Auth for AnyEvent::HTTP i found an issue in
LWP::UserAgent Digest Authen. The whole code for creating the
"message-digest" is broken/ineffective as there seems to be a stray
md5->reset:
/usr/share/perl5/LWP/Authen/Digest.pm
50 if($request->method =~ /^(?:POST|PUT)$/) {
51 $md5->add($request->content);
52 my $content = $md5->hexdigest;
53 $md5->reset;
54 $md5->add(join(":", @digest[0..1], $content));
55 $md5->reset;
56 $resp{"message-digest"} = $md5->hexdigest;
57 push(@order, "message-digest");
58 }
As the md5 object is beeing reset before the md5->hexdigest is beeing
extracted it will always return the md5 null value hexdigest:
flo@p4:~$ perl -MDigest::MD5 -e '$m=new Digest::MD5; print "Init " .
$m->hexdigest() . "\n"; $m->add("Foo"); print "Foo " . $m->hexdigest() .
"\n"; $m->reset(); print "Reset " . $m->hexdigest . "\n";'
Init d41d8cd98f00b204e9800998ecf8427e
Foo 1356c67d7ad1638d816bfb822dd2c25d
Reset d41d8cd98f00b204e9800998ecf8427e
I also failed to find the corresponding RFC describing the message-digest auth
request field.
Flo
- -- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500,
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libwww-perl depends on:
ii ca-certificates 20200601~deb10u1
ii libencode-locale-perl 1.05-1
ii libfile-listing-perl6.04-1
ii libhtml-parser-perl 3.72-3+b3
ii libhtml-tagset-perl 3.20-3
ii libhtml-tree-perl 5.07-2
ii libhttp-cookies-perl6.04-1
ii libhttp-date-perl 6.02-1
ii libhttp-message-perl6.18-1
ii libhttp-negotiate-perl 6.01-1
ii liblwp-mediatypes-perl 6.02-1
ii liblwp-protocol-https-perl 6.07-2
ii libnet-http-perl6.18-1
ii libtry-tiny-perl0.30-1
ii liburi-perl 1.76-1
ii libwww-robotrules-perl 6.02-1
ii netbase 5.6
ii perl5.28.1-6+deb10u1
Versions of packages libwww-perl recommends:
ii libdata-dump-perl1.23-1
ii libhtml-form-perl6.03-1
ii libhtml-format-perl 2.12-1
ii libhttp-daemon-perl 6.01-3
ii libmailtools-perl2.18-1
Versions of packages libwww-perl suggests:
pn libauthen-ntlm-perl
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEdb9o7oebX2papQ/KkN1BIMsJ8i8FAl+tKT8ACgkQkN1BIMsJ
8i9ptg/5AasYlgD7zF44xi+8DeaiNR6xqpZTLDTkGaXq5Fb3DKFgdvRjrkwAPhz4
kW2qSFmL7p/aE0/hcD0cuz2VD+MiIQIWUdfyWYihg810qdJyAvkTzk/Rr2p5LQR3
JGny7Jk7idAv/rqLjd7M8wKrs9TWQZ4180GG6ibGsFtiMlngIV3oeIfXFCXemfSU
lJsJmN2Cfx3PM7V1UhPdw+XaJXCxZrHeBEtGG+t3YkLTYjR9v17u+8x+ALB5zK32
cubyC7vvaYpLFt1K+XEamfkoB3vU4/3QPrLp57Cy27NROrA3smASAclyeUnxlwsk
w3lSU8CqcdlpwFH2zjlXdL0BeUzz0C1bMfu8eVchxyByVvLaTzAiPQQqvUSNZue/
6CdQh+EAqd8cK3wtD4koPO8kxPhl9T3w4DLEB2G2WMDPA4x4W0pV2EsAGOTFHtNr
+KmA47l1LQ69Z05DrjIm7eyKUzzK5r6Trg57obWpPW9+aYpYIaum+gl0U50+2oiZ
JRsTt+NiHjnvvKFif4ZQUpH515OuKgIBH7pwi0G/jh8fDr83RoYFw3Llf1npA746
fzLlrRrKVkDVN3ga1yqVfSMFrxWYQOtkTiiBmrEtaJEx8vMUHza+qwCwovwNo/63
+5i25kInC3eoFyBKz45D1pYlhLaYlbGRbWp6K4AsPVfQCv2Lez8=
=Qju8
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libwww-perl
Source-Version: 6.52-1
Done: gregor herrmann
We believe that the bug you reported is fixed in the latest version of
libwww-perl, 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 974...@bugs.debian.org,
and
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 979590 979825
Bug #979590 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979825 [libx11] chromium: Chromium freezes on startup
Marked Bug as done
Outlook recorded from message bug 979825 message
Added indication that 979825 affects chromium
Marked as fixed in versions libx11/2:1.7.0-2.
There is no source info for the package 'libx11' at version '2:1.7.0-1' with
architecture ''
Unable to make a source version for version '2:1.7.0-1'
Marked as found in versions 2:1.7.0-1.
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Merged 979590 979618 979825
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590
979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618
979825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Processing commands for cont...@bugs.debian.org:
> reassign 979694 ispell 3.4.01-1
Bug #979694 [dictionaries-common] dictionaries-common: 'espa~nol' dict contains
illegal characters
Bug reassigned from package 'dictionaries-common' to 'ispell'.
No longer marked as found in versions dictionaries-common/1.28.3.
Ignoring request to alter fixed versions of bug #979694 to the same values
previously set
Bug #979694 [ispell] dictionaries-common: 'espa~nol' dict contains illegal
characters
Marked as found in versions ispell/3.4.01-1.
> reassign 979746 ispell 3.4.01-1
Bug #979746 [wspanish] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Bug reassigned from package 'wspanish' to 'ispell'.
No longer marked as found in versions wspanish/1.0.29.
Ignoring request to alter fixed versions of bug #979746 to the same values
previously set
Bug #979746 [ispell] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Marked as found in versions ispell/3.4.01-1.
> forcemerge 979575 979694 979746
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Added tag(s) l10n.
Added tag(s) l10n.
Added tag(s) l10n.
Bug #979746 [ispell] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 979746 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Marked as fixed in versions ispell/3.4.02-1.
Added tag(s) fixed-upstream and upstream.
Bug #979694 [ispell] dictionaries-common: 'espa~nol' dict contains illegal
characters
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 979694 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Marked as fixed in versions ispell/3.4.02-1.
Added tag(s) upstream, l10n, and fixed-upstream.
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Removed indication that 979565 affects ingerman, iesperanto, ifrench, iswiss,
and iogerman
Added indication that 979565 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Removed indication that 979549 affects iogerman, iswiss, ifrench, iesperanto,
and ingerman
Added indication that 979549 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Removed indication that 979575 affects iesperanto, ingerman, iogerman, iswiss,
and ifrench
Added indication that 979575 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Merged 979549 979565 979575 979694 979746
> affects 979575 ispanish
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Bug #979694 {Done: Robert Luberda } [ispell]
dictionaries-common: 'espa~nol' dict contains illegal characters
Bug #979746 {Done: Robert Luberda } [ispell] wspanish: Word
"xx" contains illegal characters, on dictionaries-common trigger
(ispell-autobuildhash)
Added indication that 979575 affects ispanish
Added indication that 979549 affects ispanish
Added indication that 979565 affects ispanish
Added indication that 979694 affects ispanish
Added indication that 979746 affects ispanish
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979549
979565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979565
979575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979575
979694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979694
979746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958690: marked as done (node-gyp: Remove dependency to node-request)
Your message dated Mon, 11 Jan 2021 17:55:52 + with message-id and subject line Bug#958690: fixed in node-gyp 7.1.2-3 has caused the Debian Bug report #958690, regarding node-gyp: Remove dependency to node-request 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.) -- 958690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-gyp Severity: important Control: block 956423 by -1 Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got --- End Message --- --- Begin Message --- Source: node-gyp Source-Version: 7.1.2-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-gyp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-gyp 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, 11 Jan 2021 18:36:19 +0100 Source: node-gyp Architecture: source Version: 7.1.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 958690 Changes: node-gyp (7.1.2-3) unstable; urgency=medium . * Team upload * Render node-request optional (Closes: #958690) Checksums-Sha1: a734ee397c87f15c9779e57da5f168fc288f1606 2075 node-gyp_7.1.2-3.dsc 1d8538a4c2c76f0bec9e07532fd4ebfeac9428f8 9760 node-gyp_7.1.2-3.debian.tar.xz Checksums-Sha256: bd2de97d65ef7732a1bafca02832f80097b1ca767f03b42831212435ea64a3b6 2075 node-gyp_7.1.2-3.dsc 348daf8bf1987fb156bdaf776613bc976e250bd9c1640cf884671a7f650c5a19 9760 node-gyp_7.1.2-3.debian.tar.xz Files: 26a668e5cfb7700803ffa0a83e32c48e 2075 javascript optional node-gyp_7.1.2-3.dsc 0cab8369ff5adca3629e376be8644f32 9760 javascript optional node-gyp_7.1.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8jNwACgkQ9tdMp8mZ 7umMBA/8DQ955o5YxXUQrf4DaFr3xLTVsPJc28boLx4ilWLMYarAKUSmuyF2aZO1 8qp3+eb40GI8BYS4GCFfcrWalFJPuA9RIt7D9jL0xaAC/OSTGgldRdN1EBzfNpxt 6cN37jaudR3G/AnLX83nL7zMC8V8T5t0+hPBhskcV5q0AO8gOkm6E/+31gdGN5rS WYV3juxG2pfjI1FtXWhCgQBFex7KvG4Gp8/zjl7UFe0rVzAJu0rRRNKd8KjZk6+I zlTL8KclFmC4yqnSyXGF8W9xorfRyPPyZi95iVXmzu6qaCobX3MXmQxNom5wAt7o s3WPdVYYhPuAFFZKEwLS6bRjfCJPnni+/pXqQHZPPwCRcaQFayUaGlcc3Ul0f5b4 Wjq2Lj9edfLBY0UbZQBr6MNv9aVVONiTOxkfEfhZoYm/bMxHymDjMn3TC8G2/A0H VkU45h8Nn0Ug47WnoQEOGRugwZHsdQmh9nZGh1Ay7vRef6/xmFzl8iTKY0NeIhGg AVKRStj7AB2bfQkbOVOx4tdDnAwJgkELSDP/jRyP/KfLXqPXDhrNNdF4PKNiJOTj kTdtrpMwKRhy8BuGgYAIUP1DJL5BO9De+Ys81uxGCSoydfcLqd4kqxbzj2WbvKyk 1O+rMgpAMqkqe83O1ZHJXoZvCmBOdZzPVC9tFQBlmq694+BalGw= =RBkQ -END PGP SIGNATURE End Message ---
Bug#979811: marked as done (node-base64url: Please remove deprecated node-typescript-types dependency)
Your message dated Mon, 11 Jan 2021 17:55:47 + with message-id and subject line Bug#979811: fixed in node-base64url 3.0.1-7 has caused the Debian Bug report #979811, regarding node-base64url: Please remove deprecated node-typescript-types dependency 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.) -- 979811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-base64url Severity: important node-base64url (build?) depends on transitional package node-typescript-types. It should instead depend explicitly on packages corresponding with each required Node.js module. Severity raised in the hope that we can drop node-typescript-types soon. --- End Message --- --- Begin Message --- Source: node-base64url Source-Version: 3.0.1-7 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-base64url, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-base64url 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, 11 Jan 2021 18:23:46 +0100 Source: node-base64url Architecture: source Version: 3.0.1-7 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 979811 Changes: node-base64url (3.0.1-7) unstable; urgency=medium . * Team upload . [ lintian-brush ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Xavier Guimard ] * Declare compliance with policy 4.5.1 * Update build dependencies: replace node-typescript-types by node-types-node (Closes: #979811) Checksums-Sha1: 610946a23177c42825cef51727be31a7f998cb34 2114 node-base64url_3.0.1-7.dsc 38fca700e32fbe9d8575a5848e5724e1aa888a1e 4688 node-base64url_3.0.1-7.debian.tar.xz Checksums-Sha256: c55be77a3a9ee1efd28f5f6f4517d24c0f4dda57eb711dbbb103d47f2581 2114 node-base64url_3.0.1-7.dsc 0b48fc7c2c395e314c569da930c07a7fb81d8f03234d8e43a30282068a29 4688 node-base64url_3.0.1-7.debian.tar.xz Files: 958638151180379e2548efbbf74c7c76 2114 javascript optional node-base64url_3.0.1-7.dsc b5a7f8aff99dcfe8995d3923e67350f3 4688 javascript optional node-base64url_3.0.1-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8ijcACgkQ9tdMp8mZ 7umaDQ//RCQB1byMxvO2YZ67RsVn6AQE2xkDz72q948hv5HbndE13WbQogyj21y2 XJ3N7nVsJWnC4vxQaex6Bg+TaT5mu03lpPb+gtB6cieN6Tu6++BEzM1PBnutCpok ZzfXfp1jP3RXQJ6Ez5XMe5gvmFT3lqj4zUWw+tedXmhfExrZk/mZ/J+pND1sVzwb Vh3+56N+wZq6hYy/t4G1iluN84v1EfXKU5i3VOgVR9q3YUG2SG1e0In7qHMcisEn AtUrhMKUPh8mBRfHOmlHrVx3KJEfuH00L0w4xwU3duufwOEQCH7jKu+wg556ttcj 0bCUqL4/K/UdzlpL3VsQucWLF6t0rDojm8c+NssIYmGwwWTixHiy/FRBbWO0iBdz ehmoD+3dGSjQsI7UJn3keNx3rGpJy2V6lJ3esfTyTdMRkx+YCpVFOGOUXXsu02Zz yZxfF9v2LKo6bzov5zoRKg6Y5iJ/caiINeaI8Jn8LnMIk5zj7kmohhK7LDXJFf81 oCap94ix9nu2w+/gNrPc8P+a0pvIOboML574UAA3BeSryeUEucZCBBQeahmQtuqM madSfGROaRGcRlEEd76/LTM9n9qUjUC6NNT/+AfIz2pFxiYslILHcE4BJO9V/ClP qrkewULIJsYHzkX13LO5oj0Z+7yiAkbd8Lstgew6yOXqj5oy1rU= =6BsB -END PGP SIGNATURE End Message ---
Bug#972300: marked as done (keditbookmarks: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:48:54 + with message-id and subject line Bug#972300: fixed in keditbookmarks 20.12.0-2 has caused the Debian Bug report #972300, regarding keditbookmarks: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keditbookmarks Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), keditbookmarks fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/keditbookmarks_20.04.0-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining keditbookmarks! live well, vagrant From 9b1cf46b595b17be5da9ec9fd5a7fa2b7c72d523 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:45:04 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 4f64a3a..b240019 100755 --- a/debian/rules +++ b/debian/rules @@ -1,7 +1,7 @@ #!/usr/bin/make -f # see FEATURE AREAS in dpkg-buildflags(1) -export DEB_BUILD_MAINT_OPTIONS = hardening=+all +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath # see ENVIRONMENT in dpkg-buildflags(1) # package maintainers to append CFLAGS -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: keditbookmarks Source-Version: 20.12.0-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of keditbookmarks, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated keditbookmarks 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, 11 Jan 2021 17:26:33 +0100 Source: keditbookmarks Architecture: source Version: 20.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972300 Changes: keditbookmarks (20.12.0-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972300) Checksums-Sha1: d84b8ae588f116a0473f8d1e0b9c4f7e4fd3e5d1 2756 keditbookmarks_20.12.0-2.dsc 1341e4f52aa07cac8db97064b4595c7ba18742a7 8096 keditbookmarks_20.12.0-2.debian.tar.xz 9668e0fc982ba4c47dcbe5ae58b7f3e632fccc1f 21286 keditbookmarks_20.12.0-2_amd64.buildinfo Checksums-Sha256: 75e9e77e3c1818ed7cfda18ae0903b58da8ffacb18432487818c9a583e7974c2 2756 keditbookmarks_20.12.0-2.dsc 681b8f3a74aba697e10663fec1b80a9f069d5d249d72a1355337393c3c4de0c2 8096 keditbookmarks_20.12.0-2.debian.tar.xz 15d37c8a4dd2f0c8a083a2a24b06ffc48f6b6881f0c09435c6ac0935e35d6b64 21286 keditbookmarks_20.12.0-2_amd6
Bug#978390: marked as done (node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error TS2345: Argument of type 'NormalizedOutputOptions' is not assignable to parameter of type 'OutputOptions'.)
Your message dated Mon, 11 Jan 2021 16:34:08 +
with message-id
and subject line Bug#978390: fixed in node-rollup-plugin-typescript
6.0.0+~1.0.1-3
has caused the Debian Bug report #978390,
regarding node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error
TS2345: Argument of type 'NormalizedOutputOptions' is not assignable to
parameter of type 'OutputOptions'.
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.)
--
978390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-typescript
Version: 6.0.0+~1.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
> cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
>
> src/index.js → dist/rollup-plugin-typescript.cjs.js,
> dist/rollup-plugin-typescript.es.js...
> (!) Entry module "src/index.js" is implicitly using "default" export mode,
> which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.js" to use named exports
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.js
> created dist/rollup-plugin-typescript.cjs.js,
> dist/rollup-plugin-typescript.es.js in 47ms
> # Step 1: build a temporary @rollup/plugin-typescript
> cd packages/typescript && \
> ln -s ../../../node_modules/@types/resolve node_modules/ && \
> mkdir dist && \
> NODE_PATH=node_modules tsc --module CommonJS --esModuleInterop
> src/index.ts
> src/index.ts(69,54): error TS2345: Argument of type 'NormalizedOutputOptions'
> is not assignable to parameter of type 'OutputOptions'.
> Types of property 'amd' are incompatible.
> Type 'NormalizedAmdOptions' is not assignable to type 'AmdOptions'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type 'AmdOptions'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type '{ autoId?: false; id: string; } & { define?: string; }'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type '{ autoId?: false; id: string; }'.
> Property 'id' is optional in type '{ autoId: false; id?: string;
> } & { define: string; }' but required in type '{ autoId?: false; id: string;
> }'.
> src/index.ts(70,54): error TS2345: Argument of type 'NormalizedOutputOptions'
> is not assignable to parameter of type 'OutputOptions'.
> make[1]: *** [debian/rules:25: override_dh_auto_build] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/node-rollup-plugin-typescript_6.0.0+~1.0.1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-typescript
Source-Version: 6.0.0+~1.0.1-3
Done: Xavier Guimard
We believe that the bug you reported is fixed in the latest version of
node-rollup-plugin-typescript, 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 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated
node-rollup-plugin-typescript package)
(This message was generated automatically
Bug#979784: marked as done (node-rollup-plugin-typescript: Please remove deprecated node-typescript-types dependency)
Your message dated Mon, 11 Jan 2021 16:34:08 + with message-id and subject line Bug#979784: fixed in node-rollup-plugin-typescript 6.0.0+~1.0.1-3 has caused the Debian Bug report #979784, regarding node-rollup-plugin-typescript: Please remove deprecated node-typescript-types dependency 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.) -- 979784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-rollup-plugin-typescript Severity: important node-rollup-plugin-typescript (build?) depends on transitional package node-typescript-types. It should instead depend explicitly on packages corresponding with each required Node.js module. Severity raised in the hope that we can drop node-typescript-types soon. --- End Message --- --- Begin Message --- Source: node-rollup-plugin-typescript Source-Version: 6.0.0+~1.0.1-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-rollup-plugin-typescript, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-rollup-plugin-typescript 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, 11 Jan 2021 17:07:15 +0100 Source: node-rollup-plugin-typescript Architecture: source Version: 6.0.0+~1.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 978390 979784 Changes: node-rollup-plugin-typescript (6.0.0+~1.0.1-3) unstable; urgency=medium . * Team upload . [ Pirate Praveen ] * Use backports-friendly versions * Tighten build dependencies . [ Xavier Guimard ] * Declare compliance with policy 4.5.1 * Add ctype=nodejs to component(s) * Fix regression due to typescript ≥ 4.1 (Closes: #978390) * Drop legacy test: rollup-plugin-commonjs is no more available * Replace node-typescript-types build dependency by node-types-estree (Closes: #979784) Checksums-Sha1: 17e98efe4a201d259095aa09785ee9924e8a1512 3055 node-rollup-plugin-typescript_6.0.0+~1.0.1-3.dsc a2d9117eefac444d9697ba98d4354e4a29c7af1a 10808 node-rollup-plugin-typescript_6.0.0+~1.0.1-3.debian.tar.xz Checksums-Sha256: 5e9c50eccb439fe1cd6200ce63bc2177efe601b4699bce2d9bbe734ccae5a410 3055 node-rollup-plugin-typescript_6.0.0+~1.0.1-3.dsc 7c22116fa352bd20c7e49c30886cdb790bc5eb31b2e92cea7a1920d88435a9f3 10808 node-rollup-plugin-typescript_6.0.0+~1.0.1-3.debian.tar.xz Files: 5b427292d724a37f4348ff26f0395429 3055 javascript optional node-rollup-plugin-typescript_6.0.0+~1.0.1-3.dsc 30439ab85f3159d6e898b0e4303314a5 10808 javascript optional node-rollup-plugin-typescript_6.0.0+~1.0.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8eLoACgkQ9tdMp8mZ 7ulUcg/8D3X7mxNT0n8pVmIyjJ8a/ivJwf9mfPm/XnYlzaXxKejpJ3vf8XsQZRJZ SDkX+D30QkODL1TfsXY78aXzSwnTE563k/iHLX3A5RaDvlOz9aLcnqTEcLNxp9O9 xxtYr5kOrUVOhpF50xRKQDfYYR8Brz4ouuNnbT64EfTwBT/kw5CK/dMrPnqXESa2 oSwcdfLBbmLyc/KLXUsWr/Zh3PAsrxj68jDNoDuiceioN6aAqKo9m9ojIzr2fjb2 aPWYL3lT2IKAFJTkf1+Q/TuWRtS+gQfq8hbfEMLtPHKDftlToSKmtu6dKs3RLHN9 6gUEu5eddXAFEmYpfykA4kDfrqMfH1cxOa8Q5eN200V2usbPMzFCxMXpwdmZAtdA Og+tZqB7KSqAkdthhwdxuF7GqdGpMUi4+xWp/oDmORb6W2YVbA7r55EjHxZo37rs oDfZwPf4bZmtyWiZEMXzkOSY/PW9JpXvhOwAGwqhYGV80Z9/B8yODWHLP0Fy6lZz XhjMHxGLCLJC619iYks7HbVfUxUeMNBUbD/8GgLc0AxO3zaUH1pGPAZsI2HhFKN3 wN4127VZAuVUe66/DeysfqhQAHheHV/9Hp85S9ainfANHpwnoQ4vtaUg/qeIR7kX 6b+rBBWRiE9wtx2At/nxeEM6xsB3ApR3d9/QHIwCP4vPGYxyZHg= =fA3j -END PGP SIGNATURE End Message ---
Bug#972302: marked as done (grantlee5: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:33:51 + with message-id and subject line Bug#972302: fixed in grantlee5 5.2.0-3 has caused the Debian Bug report #972302, regarding grantlee5: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grantlee5 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), grantlee5 fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/grantlee5_5.2.0-2_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining grantlee5! live well, vagrant From e9685403f92d54948eaa427ba36ac1ad3fa2bb5d Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:56:07 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/rules b/debian/rules index 1325d43..ee58c88 100755 --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,8 @@ DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +# Disable fixfilepath, as it triggers build failures. +export DEB_BUILD_MAINT_OPTIONS = reproducible=-fixfilepath testsuite_failing_archs := hppa ia64 sparc64 ifneq (,$(filter $(DEB_HOST_ARCH),$(testsuite_failing_archs))) -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: grantlee5 Source-Version: 5.2.0-3 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of grantlee5, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated grantlee5 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, 11 Jan 2021 17:19:37 +0100 Source: grantlee5 Architecture: source Version: 5.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Krap Maintainers Changed-By: Aurélien COUDERC Closes: 972302 Changes: grantlee5 (5.2.0-3) unstable; urgency=medium . * Team upload. . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972302) Checksums-Sha1: 33a5b2093557de811ad381f18a2b8e54ef1d59fb 2751 grantlee5_5.2.0-3.dsc 34dc7f3b1e1e733a1861b3052cd9464053ccf8f9 13220 grantlee5_5.2.0-3.debian.tar.xz d2aefacb27dc56060cd482499acf7724a6ec0873 13900 grantlee5_5.2.0-3_amd64.buildinfo Checksums-Sha256: 157ab3a804ed53bf2fd64f107d114b8fb2f12759773b65621879e8fc56b22887 2751 grantlee5_5.2.0-3.dsc 9faa2256acfe46e2f82a7d36b032cd1f7ac9d89de2f3b1861e86b8e95d6bf197 13220 grantlee5_5.2.0-3.debian.tar.xz 46083eea36edca8517408d621df94b912c8578be9c4585cc057cb29e0f4c68f6 13900 grantlee5_5.2.0-3_amd64.buildinfo Files: 16
Bug#970963: marked as done (pygnuplot: autopkgtest must be marked superficial)
Your message dated Mon, 11 Jan 2021 10:13:37 -0600 with message-id and subject line Bug #970963: Fixed in pygnuplot 0.11.16-4 has caused the Debian Bug report #970963, regarding pygnuplot: autopkgtest must be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pygnuplot Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in pygnuplot is running a trivial command that does not provide significant test coverage: -Test-Command: python3 -c 'import PyGnuplot' Executing that command is considered to be a trivial test, which does not provide significant coverage for a package as a whole. But these tests are a useful way to detect regressions in dependencies and prevent them from breaking your package. However, it is important that we are realistic about the level of test coverage provided by these commands: most regressions cannot be detected in this way. So it is not appropriate for packages with only superficial tests to have the reduced migration time to migrate from unstable to testing as that means less opportunity for testing by users compared to the package with no tests. To support this, the keyword "Restrictions: superficial" has been defined [1]. Packages where all tests are marked with this keyword are not considered for the reduced migration age from unstable to testing, and will not be allowed to migrate automatically in later stages of the freeze [2]. Its always better to have more extensive testing than having superficial testing, which again is better than having no test. Please consider i) Adding a non-trivial test, and/or ii) Mark the trivial test with "Restrictions: superficial", similar to [3] or [4]. The Release Team has listed this issue in the list of Release Critical Issues for bullseye [5] and has mentioned that the test must be marked superficial if it is not testing one of its own installed binary packages in some way. As a result, the severity of this bug report might be increased to serious in future. [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions [2] https://release.debian.org/bullseye/freeze_policy.html [3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468 [4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3 [5] https://release.debian.org/bullseye/rc_policy.txt -- Regards Sudip --- End Message --- --- Begin Message --- Source: pygnuplot Source-Version: 0.11.16-4 Done: Josue Ortega The bug you reported is fixed in the latest version of pygnuplot, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Jan 2021 12:30:27 -0600 Source: pygnuplot Architecture: source Version: 0.11.16-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Josue Ortega Changes: pygnuplot (0.11.16-4) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Josue Ortega ] * Mark autopkgtest as superficial (#970963) * Bump debhelper-compat (= 13) * Bump Standards-Versions to 4.5.1. No changes required * debian/control: Document field Rules-Requires-Root as 'no' Checksums-Sha1: f17591b18b4200ebb21a0165c3f1a377674545ac 2074 pygnuplot_0.11.16-4.dsc 9b804a135a3c234934c3ae6645c4aecc26081cc9 2280 pygnuplot_0.11.16-4.debian.tar.xz 9b5515a738267ecf0a249dcbc33bb2d0716650ca 6293 pygnuplot_0.11.16-4_amd64.buildinfo Checksums-Sha256: 77feda24783b270f4ffd633cfd5db386c0c6f1c9986135e5ef91fb249a71904a 2074 pygnuplot_0.11.16-4.dsc 5ab46919804eb65d61cda9b104e5752ebe129caa837f6bef54436d703fd900b5 2280 pygnuplot_0.11.16-4.debian.tar.xz adaf6e6eb03457dff14db3e9848c9692a0d409f24dd2abe61af1115586f0edbf 6293 pygnuplot_0.11.16-4_amd64.buildinfo Files: 8fff623730ec26c89e22aca067d0eed4 2074 python optional pygnuplot_0.11.16-4.dsc 3b4ab799de3033a6e8
Bug#972306: marked as done (analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:03:21 + with message-id and subject line Bug#972306: fixed in analitza 4:20.12.0-2 has caused the Debian Bug report #972306, regarding analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: analitza Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), analitza fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/analitza_20.08.0-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining analitza! live well, vagrant From 42f35de749a9eaf462a85eff7d26aa2150054a49 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 16 Oct 2020 00:08:52 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 38d755d..377deae 100755 --- a/debian/rules +++ b/debian/rules @@ -3,7 +3,8 @@ #export DH_VERBOSE = 1 # see FEATURE AREAS in dpkg-buildflags(1) -export DEB_BUILD_MAINT_OPTIONS = hardening=+all +# Disable fixfilepath as it triggers build failures. +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath # see ENVIRONMENT in dpkg-buildflags(1) # package maintainers to append CFLAGS -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: analitza Source-Version: 4:20.12.0-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of analitza, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated analitza 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, 11 Jan 2021 16:43:53 +0100 Source: analitza Architecture: source Version: 4:20.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972306 Changes: analitza (4:20.12.0-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972306) Checksums-Sha1: 64873eb84cb9336377eec7ff43746a8d3adb3559 2968 analitza_20.12.0-2.dsc 9ba7a7d1b993ebfa521da34b17b02296776f3ec6 8968 analitza_20.12.0-2.debian.tar.xz 951477a6ace835cd25caf7cbacaaafec68acb582 16264 analitza_20.12.0-2_amd64.buildinfo Checksums-Sha256: 08a83ee8bc191c6178c93d4b5f30bba724446a7340d747079e8b000f2463c837 2968 analitza_20.12.0-2.dsc 8688c0bfd984c867b44a8e61bec8754d5b724b7f3bcb5742fb46e81b72874803 8968 analitza_20.12.0-2.debian.tar.xz d404c01f2c474313b65085f07ec17e2354e8cdb71631bd27acab44e3e39ae32a 16264 analitza_20.12.0-2_amd64.buildinfo Files: 26fb84f08d01ca5ce
Bug#979734: marked as done (calibre: remove python3-crypto from (Build-)Depends)
Your message dated Mon, 11 Jan 2021 15:48:30 + with message-id and subject line Bug#979734: fixed in calibre 5.9.0+dfsg-2 has caused the Debian Bug report #979734, regarding calibre: remove python3-crypto from (Build-)Depends 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.) -- 979734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calibre Version: 5.8.1+dfsg+fontFix-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 972184 by -1 Control: block 979318 by -1 We will remove python3-crypto from bullseye. It is unmaintained and a replacement is available via python3-pycryptodome. calibre only uses any module from python3-crypto in src/calibre/test_build.py to check if is installed. No other code in calibre uses python3-crypto. So I recommend to simply remove this check and drop the dependencies. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: calibre Source-Version: 5.9.0+dfsg-2 Done: YOKOTA Hiroshi We believe that the bug you reported is fixed in the latest version of calibre, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YOKOTA Hiroshi (supplier of updated calibre 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, 12 Jan 2021 00:04:05 +0900 Source: calibre Architecture: source Version: 5.9.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Calibre maintainer team Changed-By: YOKOTA Hiroshi Closes: 979734 Changes: calibre (5.9.0+dfsg-2) unstable; urgency=medium . [ Norbert Preining ] * Remove dependency on python3-crypto (Closes: #979734) remove the one trivial crypto loading test from src/calibre/test_build.py . [ YOKOTA Hiroshi ] * Update patch queue Checksums-Sha1: 4faf39e9c794573a3ab5095a7b08509177bd94e9 3325 calibre_5.9.0+dfsg-2.dsc aeb9dfdb8c3876554c3b6a1c2eaa405a872e30c0 4411416 calibre_5.9.0+dfsg-2.debian.tar.xz 755da680b6a61672c4f73653564eefdcf1747733 19749 calibre_5.9.0+dfsg-2_source.buildinfo Checksums-Sha256: 0b347a72424472d722e2c714533e1bf6035450d7d53917a72cf927c331477617 3325 calibre_5.9.0+dfsg-2.dsc dbc1dae3ff3567656dd8a1ac50bb8b1536fbc8fd33bd7c6c1ac6dcac4e32ba82 4411416 calibre_5.9.0+dfsg-2.debian.tar.xz 0c556defeed7061518088ebeed1f1154d85b10e1fc3920ff37a31f20739713b3 19749 calibre_5.9.0+dfsg-2_source.buildinfo Files: 6ea681f8b594781bb5b28c1caa731165 3325 text optional calibre_5.9.0+dfsg-2.dsc 700f193f435f96bad07ca50e9e1a4921 4411416 text optional calibre_5.9.0+dfsg-2.debian.tar.xz a4fd1b29ae47e5bc8532efed5439bd7a 19749 text optional calibre_5.9.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEErjlfKHqxT11VFyPEqem2T5LebcoFAl/8cJ4WHHlva290YS5o Z21sQGdtYWlsLmNvbQAKCRCp6bZPkt5tyoPbEACvn0003KwlVZE/9uVXDN5T2IPi GgaIIES0nEUj1jvyrxaC6LJ8VuQkTTzJu9WmVFJNFLOX3EeVQ3MBT+RolLrzFX0S sT3VfS/ROmoYwdgA0iltOY+d1SbFgfXwfuZ9KigtCUAxhKgEKAaJQJLvmC8YbduD VMCnmiUy1UabSrYhtHtdTDn+VPN01sD69nIHEDvufjnODKgAo/0ZIlZ2FV37iguh ikrj7+v4hayEKf3RE41cQfVm0zYYtVUup3O/SaM4UT1PUYmseFFuptkNl+nB/32k /KKiLWrOjN55G17LmSAii5JZoSNMyams+XPHc2UdbZT/n+vjg8bfKw/OQ2JIAOCv bcSaOkqW4r8rsS90w86F+mr4e5G+P8eWhK6+bvM2KvuzKpmxUaMnG8E+pm9QfCPm sTNDo+5VKppYTa5wj14qcV/W8EGFWBIXulyNMqmSkbw7JoJPosPouFO/MBNXHTbf I7/R+eM7RbZfXPzcSgnSzpMCDj9u1LSsL+xIVj8LXuGZNFw9M10CYx2fGol2t2t+ Z5BJaM3JNVFTSkChfcM0Uqi4AFXejcMG2J/ygW7qGhNX05l3Q08gOEqntA765jLT /ULsttEKWo8uG7biUfT2wrNSSxViN6FtqJwDmyr+pG83R3nNAqHBZNUv7N9W4Spx 2Fcr2CJqx1wSgdUbnA== =70cm -END PGP SIGNATURE End Message ---
Bug#975789: marked as done (golang-github-xenolf-lego: FTBFS: src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment mismatch: 1 variable but d.client.Account.Login returns 2 values)
Your message dated Mon, 11 Jan 2021 14:36:35 +
with message-id
and subject line Bug#975789: fixed in golang-github-xenolf-lego 3.2.0-3
has caused the Debian Bug report #975789,
regarding golang-github-xenolf-lego: FTBFS:
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment
mismatch: 1 variable but d.client.Account.Login returns 2 values
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.)
--
975789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-xenolf-lego
Version: 3.2.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure
> set -e -x ;\
> cd _build/src/github.com/go-acme/lego && \
> for P in acmedns alidns auroradns azure bindman cloudflare designate
> dnsimple dnspod exoscale fastdns iij linode linodev4 liquidweb namedotcom
> namesilo ns1 oraclecloud sakuracloud transip vegadns ; do \
> perl -ni -E "print unless m{\b$P\b}"
> providers/dns/dns_providers.go ;\
> rm -rf providers/dns/$P ;\
> done
> + cd _build/src/github.com/go-acme/lego
> + perl -ni -E print unless m{\bacmedns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/acmedns
> + perl -ni -E print unless m{\balidns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/alidns
> + perl -ni -E print unless m{\bauroradns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/auroradns
> + perl -ni -E print unless m{\bazure\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/azure
> + perl -ni -E print unless m{\bbindman\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/bindman
> + perl -ni -E print unless m{\bcloudflare\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/cloudflare
> + perl -ni -E print unless m{\bdesignate\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/designate
> + perl -ni -E print unless m{\bdnsimple\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/dnsimple
> + perl -ni -E print unless m{\bdnspod\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/dnspod
> + perl -ni -E print unless m{\bexoscale\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/exoscale
> + perl -ni -E print unless m{\bfastdns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/fastdns
> + perl -ni -E print unless m{\biij\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/iij
> + perl -ni -E print unless m{\blinode\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/linode
> + perl -ni -E print unless m{\blinodev4\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/linodev4
> + perl -ni -E print unless m{\bliquidweb\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/liquidweb
> + perl -ni -E print unless m{\bnamedotcom\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/namedotcom
> + perl -ni -E print unless m{\bnamesilo\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/namesilo
> + perl -ni -E print unless m{\bns1\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/ns1
> + perl -ni -E print unless m{\boraclecloud\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/oraclecloud
> + perl -ni -E print unless m{\bsakuracloud\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/sakuracloud
> + perl -ni -E print unless m{\btransip\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/transip
> + perl -ni -E print unless m{\bvegadns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/vegadns
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
> cd _build && go generate -v github.com/go-acme/lego/acme
> github.com/go-acme/lego/acme/api
> github.com/go-acme/lego/acme/api/internal/nonces
> github.com/go-acme/lego/acme/api/internal/secure
> github.com/go-acme/lego/acme/api/internal/sender
> github.com/go-acme/lego/certcrypto github.com/go-acme/lego/certificate
> github.com/go-acme/lego/challenge github.com/go-acme/lego/challenge/dns01
> github.com/go-acme/lego/challenge/http01
> github.com/go-acme/lego/challenge/resolver
> github.com/go-acme/lego/challenge/tlsalpn01 github.com/go-acme/lego/cmd
> github.com/go-acme/lego/cmd/lego github.com/go-acme/lego/internal
> github.com/go-acme/lego/lego github.com/go-acme/lego/log
> github.com/go-acme/lego/platfor
Bug#979759: marked as done (bump user-mode-linux using linux-source version 5.10.5-1 (or greater))
Your message dated Mon, 11 Jan 2021 19:28:41 +0530 with message-id <8b120ff4b5f52ea08654f7565b8c547c076b32fe.ca...@debian.org> and subject line Re: Bug#979759: bump user-mode-linux using linux-source version 5.10.5-1 (or greater) has caused the Debian Bug report #979759, regarding bump user-mode-linux using linux-source version 5.10.5-1 (or greater) 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.) -- 979759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: user-mode-linux Version: 5.10-um1 Dear maintainers, Could you bump user-mode-linux package using linux-source package version 5.10.5-1 or greater? Linux 5.10.5 contains some extra backported patches for Debos, Debian Image Generator, and it's user-mode-linux backend. Debos currently allows to build images using a virtual machine with KVM, which usually isn't available for use on unprivileged cloud machines. On machines where these unprivileged cloud machines are used, Debos can either run directly on the host or inside a user-mode-linux "container". You can read some more about Debos and the UML backend here: https://github.com/go-debos/debos thanks! Christopher Obbard --- End Message --- --- Begin Message --- Dear Chris, I spent some time today to find a workable solution in the longer term. The below link has all the necessary details. https://release.debian.org/wanna-build.html So, henceforth, anyone can request a rebuild (binNMU) of a package, where there is a need. Like in this case, for user-mode-linux, a rebuild is needed so that it could pick the latest 5.10.5 changes. This is the bug I have filed. The process for filing the bug is automated. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979792 The only thing I wish is that attending to this bug's request were also automated. I'll wait to see the response on this bug report, to see who attends to it. I am closing this bug report because the actual action will happen in 979792 only. Thanks, Ritesh On Mon, 2021-01-11 at 09:55 +, Christopher Obbard wrote: > Package: user-mode-linux > Version: 5.10-um1 > > Dear maintainers, > > Could you bump user-mode-linux package using linux-source package > version 5.10.5-1 or greater? > > Linux 5.10.5 contains some extra backported patches for Debos, Debian > Image Generator, and it's user-mode-linux backend. Debos currently > allows to build images using a virtual machine with KVM, which > usually > isn't available for use on unprivileged cloud machines. On machines > where these unprivileged cloud machines are used, Debos can either > run > directly on the host or inside a user-mode-linux "container". -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#466116: marked as done (libfcgi0ldbl: libfcgi-dev)
Your message dated Mon, 11 Jan 2021 16:46:42 +0300
with message-id <2316181610371...@mail.yandex.ru>
and subject line Re: Bug#466116: libfcgi0ldbl: libfcgi-dev
has caused the Debian Bug report #466116,
regarding libfcgi0ldbl: libfcgi-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
466116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfcgi0ldbl
Version: 2.4.0-7
Severity: normal
I trying to setup a fastcgi-interface using lighttpd. I used the tiny
example given in the libfcgi documentation. However, this example seems
to be faulty: The programm SIGSEVS whenever it tries to
getenv("SERVER_NAME").
Commenting out getenv makes the programm working -- but without access
to the enviroment.
As I am starting with the topic, this is quite annoying, if the examples
are buggy...
Update: When replacing SERVER_NAME with QUERY_STRING, the programm stops
segfaulting.
If this is a problem of lightttpd, please reassign. I cannot tell.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libfcgi0ldbl depends on:
ii libc6 2.7-6GNU C Library: Shared libraries
ii libgcc1 1:4.3-20080202-1 GCC support library
ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3
libfcgi0ldbl recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
I have checked that sample program from libfcgi-dev with small addition [1] on
my test website and it shows corrent data [2] without dependency from web server
in use (normally nginx is used there, but I specially tested with lighttpd).
I have no idea why program crashes in your case. In real program I would
recommend to check that the getenv("SERVER_NAME") does not return null
pointer and that the length of data is not zero.
[1] Program shows few available environment variables at once.
[2] SERVER_NAME=sibuserv-ci.org
Best regards,
Boris--- End Message ---
Bug#979698: marked as done (src:nodejs: should provide virtual package node-types-node)
Your message dated Mon, 11 Jan 2021 13:49:32 + with message-id and subject line Bug#979698: fixed in nodejs 12.20.1~dfsg-3 has caused the Debian Bug report #979698, regarding src:nodejs: should provide virtual package node-types-node 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.) -- 979698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nodejs Version: 12.20.1~dfsg-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bug#979693 indicates that nodejs now embeds Node.js module @node/types. Please provide virtual packages for any and all modules installed, so that consuming packages can declare explicit package relations, which helps in e.g. assess when to deprecate embedded modules or maybe move them out to independent packages. Even if the module is inherently tied to the src:nodejs codebase, it is still helpful to consistently declare virtual packages for all modules: I hope that we can at some point make it into Debian Policy that Node.js modules *must* be declared as (virtual or real) package name, which can then simplify tooling. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/60G4ACgkQLHwxRsGg ASFL5BAAhc2+rVdE2JNYjw3X42mDoKOQz34+hiX++oGEmITW0XJB8uTCsdJ5s0oj kH6zkzqdw6m4flK/pHcPFN/vqQksSprI7ZR8MRfWogjBSTCTmiH2J5/jlmEgBKta 1CLvB7HdSnbRBU2r427oxrqvPMjL7BV6Rb1TLKN98mP9BHaBdBiU63AVnLoKi5Qn EdFX86/9/vvng6X4z7T2Gr1XN2p2UXFom094fbtJ+YyiZhSbFwcQdFXQez0glrkS 90E7FmW/fdvikBF614IBy3q21PtB6w9Fp05UmZu9BtoqePGzkqkXG3BU42t3axIK hoZFDAKPAyY02vacPJ+N/QLJTpJ7xQiJmYmExUbMVAfyPzVQmSBBDtmSgSbAfsYf N9qEJgT4oTtzJWDzY4Ytp9Ed+eiqjDiUOuekwViYpFzP2vgsYfCh5aoi7mfcr+IK wIrcvGXGkmOBkfWbjtCv2jHivj67sQwIl/77UrUVmvjdhcqAoHJEpxE74mWETu1Q QiGIG/LL/j5zbqA5Vgf+eb4fsHZ5npswkbHZbIPHCpQE2i799ewP/7ZAKuxuGQWZ QAgx9ESMj9BVOgrUtRJ8ML7lxxQ+uDOgiHQMweh6cGrUqRtpsnxkoGijTxmJNJJa g/rjkrv2+cr/QAVLzIXxygdFiVE4+4z86HOUR3XZY7lS1koQVOA= =49m6 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 12.20.1~dfsg-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of nodejs, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated nodejs 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, 11 Jan 2021 13:05:02 +0100 Source: nodejs Architecture: source Version: 12.20.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 979698 Changes: nodejs (12.20.1~dfsg-3) unstable; urgency=medium . * Team upload * Provide node-types-node (Closes: #979698) Checksums-Sha1: 1db4fc175afb1e3692aac1ecddc63cf000a6feea 3429 nodejs_12.20.1~dfsg-3.dsc 7ce485c3d6dc83b36253406a277ba56c67ebd395 134316 nodejs_12.20.1~dfsg-3.debian.tar.xz Checksums-Sha256: 94a160231cbf9c0a69a8795a5a0bdbad465f6ea29e9af31622497e767a6aace4 3429 nodejs_12.20.1~dfsg-3.dsc c9e0e0b5af8e92ee7c5f3c66f0f41bd8027cfe5bfe343a832f5c006ceed69f80 134316 nodejs_12.20.1~dfsg-3.debian.tar.xz Files: a2690d6ec6d7926aa7f6c2dbd12e128d 3429 javascript optional nodejs_12.20.1~dfsg-3.dsc c4048b6070ab80f44abb91512ebd445e 134316 javascript optional nodejs_12.20.1~dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8Uj4ACgkQ9tdMp8mZ 7um/Gg/9ELVzGPKafltxb2fGFX78OmBsekci7dWLkZFZesSo5F1RE4iHgAdSoTfb k3ZnPgrhgzCijf/GJG9EU8S9s8EU/6ozEZ7KZd/Xr4XIBOTr4kxgEhoGu7AS0g+l 5N8u5mOj8OrhAMRlQ6Eq60ubeARHhf3AmxvU+UuDtBRFGUf0Bt1qT3Pke0jL57L8 LI37Rw2oPMRb8cOHsrgqYpbnz+s8pompVtTCC7hlRZuxcrV6bDOXw5i8o+ePaJ+s /gW6bgFjDLI2EH9AOXRt24C8MMc6FjgStpItSpqdSJQodui/j9s203DiG+amNdn3 MfvOlGJtlogLBvxBhcR+upHRgfKStZ4lVr8Jgny//3LngQU5S9LDuOxq0Oxd9u7H xcU0K+pdSf4oAB7vU5jObMB2k8X0gvu9CBHGFiYKsULLrcrRKILL71+Z2RKgyOKX /f4SVQIY/4Z0pWAq04RcG4dN6ba1/wG6H9JBdKuPwLt5FDfLmyOu0C+I1U6tIaoG vR/NiycKNsf+4OuyQr38GbttIGHb9ebGzQuPACflbb6Pd71jWLKUX9gk+Hw0UTW/ AtbL/nASz+pATzOF6l3dTw4dNFJ6Wx7MhASnfoNWABXRMxXC/r3ZUQ8THF56pKDk d3kySdjpFp
Bug#957601: marked as done (netsniff-ng: ftbfs with GCC-10)
Your message dated Mon, 11 Jan 2021 13:49:22 + with message-id and subject line Bug#957601: fixed in netsniff-ng 0.6.8-1 has caused the Debian Bug report #957601, regarding netsniff-ng: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:netsniff-ng Version: 0.6.5-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/netsniff-ng_0.6.5-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c0): multiple definition of `simulate'; mausezahn/automops.o:(.bss+0x6e6c0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c4): multiple definition of `verbose'; mausezahn/automops.o:(.bss+0x6e6c4): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c8): multiple definition of `quiet'; mausezahn/automops.o:(.bss+0x6e6c8): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6cc): multiple definition of `ipv6_mode'; mausezahn/automops.o:(.bss+0x6e6cc): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6d0): multiple definition of `mode'; mausezahn/automops.o:(.bss+0x6e6d0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6d4): multiple definition of `device_list_entries'; mausezahn/automops.o:(.bss+0x6e6d4): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6e0): multiple definition of `device_list'; mausezahn/automops.o:(.bss+0x6e6e0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6ef20): multiple definition of `MZ_SIZE_LONG_INT'; mausezahn/automops.o:(.bss+0x6ef20): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e790): multiple definition of `mode'; mausezahn/automops.o:(.bss+0x6e6d0): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x60e0): multiple definition of `tx'; mausezahn/automops.o:(.bss+0x6020): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e788): multiple definition of `quiet'; mausezahn/automops.o:(.bss+0x6e6c8): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e538): multiple definition of `mz_stop'; mausezahn/automops.o:(.bss+0x6e478): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e540): multiple definition of `mz_start'; mausezahn/automops.o:(.bss+0x6e480): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e550): multiple definition of `total_d'; mausezahn/automops.o:(.bss+0x6e490): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x0): multiple definition of `cli_debug'; mausezahn/cdp.o:(.bss+0x0): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x4): multiple definition of `clidev'; mausezahn/cdp.o:(.bss+0x4): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x8): multiple definition of `clipkt'; mausezahn/cdp.o:(.bss+0x8): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x10): multiple definition of `mz_port'; mausezahn/cdp.o:(.bss+0x10): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x20): multiple definition of `mz_listen_addr'; mausezahn/cdp.o:(.bss+0x20): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x40): multiple definition of `mz_enable'; mausezahn/cdp.o:(.bss+0x40): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x60): multiple definition of `mz_password'; mausezahn/cdp.o:(.bss+0x60): first defined here /usr/bin/ld: m
Bug#914642: marked as done (netsniff-ng FTCBFS: builds for the wrong architecture)
Your message dated Mon, 11 Jan 2021 13:49:22 + with message-id and subject line Bug#914642: fixed in netsniff-ng 0.6.8-1 has caused the Debian Bug report #914642, regarding netsniff-ng FTCBFS: builds for the wrong architecture 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.) -- 914642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netsniff-ng Version: 0.6.5-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap netsniff-ng fails to cross build from source, because nothing tells its ./configure which architecture we are building for and thus it just builds for the build architecture. We cannot use dh_auto_configure, because netsniff-ng's ./configure is very much unlike autotools. Rather one is supposed to stuff the host architecture into a variable called CROSS_COMPILE. The attached patch implements that and makes netsniff-ng cross buildable. Please consider applying it. Helmut diff --minimal -Nru netsniff-ng-0.6.5/debian/changelog netsniff-ng-0.6.5/debian/changelog --- netsniff-ng-0.6.5/debian/changelog 2018-09-20 15:06:14.0 +0200 +++ netsniff-ng-0.6.5/debian/changelog 2018-11-25 21:47:27.0 +0100 @@ -1,3 +1,10 @@ +netsniff-ng (0.6.5-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Tell ./configure about the host architecture. (Closes: #-1) + + -- Helmut Grohne Sun, 25 Nov 2018 21:47:27 +0100 + netsniff-ng (0.6.5-1) unstable; urgency=low * New upstream release. diff --minimal -Nru netsniff-ng-0.6.5/debian/rules netsniff-ng-0.6.5/debian/rules --- netsniff-ng-0.6.5/debian/rules 2018-09-20 15:01:55.0 +0200 +++ netsniff-ng-0.6.5/debian/rules 2018-11-25 21:47:27.0 +0100 @@ -5,7 +5,9 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/architecture.mk include /usr/share/dpkg/buildflags.mk +export CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)- CFLAGS+=$(CPPFLAGS) CXXFLAGS+=$(CPPFLAGS) --- End Message --- --- Begin Message --- Source: netsniff-ng Source-Version: 0.6.8-1 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of netsniff-ng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated netsniff-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Jan 2021 18:36:02 +0530 Source: netsniff-ng Architecture: source Version: 0.6.8-1 Distribution: unstable Urgency: medium Maintainer: Daniel Borkmann Changed-By: Kartik Mistry Closes: 914642 957601 Changes: netsniff-ng (0.6.8-1) unstable; urgency=medium . * Upload to unstable. * New upstream release: + Fix mausezahn build with GCC 10 (Closes: #957601) * debian/control: + Updated to Standards-Version 4.5.1 + Switched to debhelper-compat. + Added 'Rules-Requires-Root' field. * Added debian/upstream/metadata file. * debian/rules: + Do not call dh_dwz, which generates unneeded debug files. . [ Helmut Grohne ] * debian/rules: + Fix FTCBFS: Tell ./configure about the host architecture. (Closes: #914642) Checksums-Sha1: 8cbe83184ddcf6b941a03aa9e3315a3a495d7354 2419 netsniff-ng_0.6.8-1.dsc 01bde7d90ae7b3b24852750d9df6e0ebcc071d6c 617820 netsniff-ng_0.6.8.orig.tar.xz 44b554057f199a8eb2ed99bc2ae3c167dcc24efa 195 netsniff-ng_0.6.8.orig.tar.xz.asc e5caf9e8b2f0fd1723c9b894aa04e409ad7a2d64 7136 netsniff-ng_0.6.8-1.debian.tar.xz Checksums-Sha256: 953d0ba27e7f55cfb560783a01d4f820c41762ce1526b87780c386c072f22e26 2419 netsniff-ng_0.6.8-1.dsc 77d17d4158faf1d93c7d922a1bd7f093a8b437bd658292c830708540e10894ba 617820 netsniff-ng_0.6.8.orig.tar.xz 4e05f790d80ba6d2a64fc96104c09fce529fca2410fbe579ca738e8544ab19ca 195 netsniff-ng_0.6.8.orig.tar.xz.asc f2b7e6045b649ad2b9ef1520436e4188914b9b40de2bc000265e0b7e879c74da 7136 netsniff-ng_0.6.8-1.debian.tar.xz Files: f6d403e84b7ec87a22366b9146fb3232 2419 net optional netsniff-ng_0.6.8-1.dsc 477580690816dc7eacaaca444a6bdb55 617820 net
Bug#909651: marked as done (Please enable AppIndicator support and switch over to Ayatana AppIndicator)
Your message dated Mon, 11 Jan 2021 13:35:33 + with message-id and subject line Bug#909651: fixed in parcellite 1.2.1-4 has caused the Debian Bug report #909651, regarding Please enable AppIndicator support and switch over to Ayatana AppIndicator 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.) -- 909651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parcellite Version: 1.1.9-1 Severity: wishlist Tags: patch User: pkg-ayatana-de...@lists.alioth.debian.org Usertags: ayatana-appindicator Dear maintainer of parcellite, find attached a .debdiff that switches on AppIndicator support for the system tray icon and that switches over from Ubuntu's AppIndicator to Ayatana AppIndicator. This contribution is part of the Ayatana Indicators shift in Debian. For more info, see https://lists.debian.org/debian-devel/2018/03/msg00506.html Thanks, Alessio q80yx9fi Description: Binary data --- End Message --- --- Begin Message --- Source: parcellite Source-Version: 1.2.1-4 Done: Thomas Koch We believe that the bug you reported is fixed in the latest version of parcellite, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Koch (supplier of updated parcellite 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, 11 Jan 2021 14:20:14 +0100 Source: parcellite Architecture: source Version: 1.2.1-4 Distribution: unstable Urgency: medium Maintainer: Hugo Lefeuvre Changed-By: Thomas Koch Closes: 909651 Changes: parcellite (1.2.1-4) unstable; urgency=medium . [ Hugo Lefeuvre ] * Enable AppIndicator support and switch over to Ayatana AppIndicator (thanks to Alessio Garzi for the patch !) (Closes: #909651). * debian/control: - Bump Standards-Version to 4.2.1. - Switch B-D from libappindicator-dev to libayatana-appindicator-dev. * debian/patches: - ayatana-appindicator.patch: switch to ayatana-appindicator. - fix-configure-ac.patch: fix build on sid. Checksums-Sha1: 0c5e279081124caf0f1af293adf21635cdc3d2b3 1964 parcellite_1.2.1-4.dsc a39063bf033de301c20d1f1f52f5c48be5a6caac 6492 parcellite_1.2.1-4.debian.tar.xz 2e1895ca9a9c6a3418e94a51f0f6a87bb1fff2a6 10886 parcellite_1.2.1-4_source.buildinfo Checksums-Sha256: 9c307e739067e089ad36cd6c7384cdbd6457b48d98b8883e26b717b23d58d9ef 1964 parcellite_1.2.1-4.dsc c8fa9b610d81a3133bd06c45a327b47b2988dd420ac222e754fb0eb95dd2856f 6492 parcellite_1.2.1-4.debian.tar.xz 9da0bf1d615d7d3051ee4094029cbc578d96627195b2b253cc8a3f393968259f 10886 parcellite_1.2.1-4_source.buildinfo Files: c34b73832851ac79dfd22b49552b7733 1964 misc optional parcellite_1.2.1-4.dsc 67a34be935429ad10cf29f67d5439be7 6492 misc optional parcellite_1.2.1-4.debian.tar.xz 327cdad1a4d32862ce53038bc17679dc 10886 misc optional parcellite_1.2.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdgQCBVl/ppbxMTvKB/xIkQQrploFAl/8UWYACgkQB/xIkQQr ploKAQ/+LB8pZY6G5/vO0QuXYw9agtIZD1ySHL0Ohvv69RenfFjtwwKO59DFzbyP Z0GGxOOROJSOuvTfdK0ID+ckt1cwmrVS0zhzdtyePCJBIz9YQt4TesLMZctUBJco QNMGXJiWdIJu+czYcleJwIbBinT4rNy5LW5OqK+N7HxA51VaxPWvJQBkaDwN5JWq e0bvSacSAfI4/8ksyfx90DdJW9jGnd0FPz5h92Aj3kERTvDYMKBgJNaQEjeYEZbT X88L+I17JNh7Ii+c8kRcfxvxGHuH2Uu8SM1v3n9xyZQ5kdGAzHOY1wa1ko4stOfT kzHCd9fiyMttWBCRgsswuRfKTY/oamxcvxqQZlfKSUPzl1xjNV3AJERYN2gFBG86 qdR7Wf8ET0oOq12fT0/xmaPjiliOwZo4VyvHr0JEAaQcDPPn7bJ4j0L1o7BiY09w KDF8ixDwELz0UlXqy0m/3+dIM285kHceqIoC7jwCy+NGOXj4tjK0EQlGBln/55Yg prdUclqXtIApTCouwsZQ6zfGND/HYdm6aALY2foi+AMBKWQjTrNU4ungbFZ6yfT2 gr5CEqdy1+jnK5F3BtIK+ZdZ4+/Qs/KXLFOsVP4Ofo5KRoAxDwep4FBUxS06yTkw OgCqZAfisxDP/aSznO0Y0Rbn4I4WHBVt1pfR0nuKo4g8JQPMJGQ= =VMo8 -END PGP SIGNATURE End Message ---
Bug#979761: marked as done (node-jest-worker: depends on transitional package node-typescript-types)
Your message dated Mon, 11 Jan 2021 13:35:27 + with message-id and subject line Bug#979761: fixed in node-jest 26.6.3+repack+~cs61.38.31-6 has caused the Debian Bug report #979761, regarding node-jest-worker: depends on transitional package node-typescript-types 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.) -- 979761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-jest-worker Version: 26.6.3+repack+~cs61.38.31-5 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 node-jest-worker depends on transitional package node-typescript-types. It should instead depend explicitly on packages corresponding with each required Node.js module. Severity raised in the hope that we can drop node-typescript-types soon. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/8Nj0ACgkQLHwxRsGg ASFylRAAo8FQLfHklWVD5wXj+1w8G3wvjQZOj/hDYMqHgyDOAQr0lYCGCvZi836U KklpLIsOc/c7OqAxibjDrIp6Vy1+903mQqMBdmacxjdBy6BlMpEfhbiz9ciRnywY mdXoWkZyU6FUzzrDZhpwAbvvi2AZXvUqiTnpTBKIShqf+9gsL8RHCQXJldu60JiJ 5HUXrkFBg2liXvEkoC5IPlbypvQ5vTpXWKWT+qhqNc8MavUwSP9m5AYxXUa0Csql Oo0TkTRyqfRlb46Fff4sw2BRFjVC9FUiLjDEIzSz2pTlEdSb87eK6GLXnk8NxDzV xE8XPbX1+8qDzX6P5H7KAIgtlEkJRJOtP9nt2oOG5BcrJemu4iaBXORSrTu/vJ0y zIbIYldeEP+CHHFLsupfCgaRtd5H9Uf6Wacpf7kgYxXsgsilwaDLsXFVwcoIm0eG jB51O/LlXO2OUzXFr1ea+465dB0pTyh6Vutl8tvsHMQazcwhlGYytXPXi8+RgbXB wLgzBBkVWhgnbqDHsJQd9j2VRnXQHg/q+wfMmQWf40ZC4aBxXWDTrYnazHoMrrU5 yaZXzGZCGDtsme/CyuzKJ4EVDpM2dK35WaBgnZ5k8aY3Uii7vYRUjvtvEHLZ8YPZ LsWjs0yJOPekQrekB6hRr9lv8rnB5aARcItRGLF7bIk7cCv30r8= =9E1D -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: node-jest Source-Version: 26.6.3+repack+~cs61.38.31-6 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-jest, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-jest 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, 11 Jan 2021 13:46:25 +0100 Source: node-jest Architecture: source Version: 26.6.3+repack+~cs61.38.31-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 979761 Changes: node-jest (26.6.3+repack+~cs61.38.31-6) unstable; urgency=medium . * Refresh typescript patch * Remove dependency to node-typescript-types (Closes: #979761) Checksums-Sha1: 8111b4d3710f82f2cf46407946843798240bad6b 11260 node-jest_26.6.3+repack+~cs61.38.31-6.dsc f513da0004da919e1048edca4941302cc30d22fd 142300 node-jest_26.6.3+repack+~cs61.38.31-6.debian.tar.xz Checksums-Sha256: 9166b24be65e6f110f0a411d2a2d7010a628ba9c9b37f02147003965e62409e5 11260 node-jest_26.6.3+repack+~cs61.38.31-6.dsc a44d767096a243e2f7b80df716d9c31dfedba9987a8e2c5cfc13c467851feb93 142300 node-jest_26.6.3+repack+~cs61.38.31-6.debian.tar.xz Files: ef8f52ea9136cc521f4c3a8e345df30a 11260 javascript optional node-jest_26.6.3+repack+~cs61.38.31-6.dsc 96474688eb0c0e9f6cb22142d40925bf 142300 javascript optional node-jest_26.6.3+repack+~cs61.38.31-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8UPIACgkQ9tdMp8mZ 7ul3yQ/+LW/Jq5y0WgfFaOu+NVCYDJdofbuvNhLWIsVqdh2dsayGuvUMS75DXbIR 15MrExkweEazlK0V0CwwgKlKXwo4kCqc+SSl9C8EtfH8VbwTXTtBTnl0dO3H1vMn iGqHtzns4zhj48UqUf/PteXpoLf0SE+GoKXwQwFwpL1+Z3bEcBGffQptFXk0Y0oW XTGvqG6uYk1ji25WnHvRPjODs7gmoqwNF8uT298H2L9SWd3pojFE1Fdra+eMojzC FkV2nAeLIVVk1C36tZ1SI8rAmoFssTLmPAyWIEsmPiHkTxqRvkR5Qf8AE89/Lo8J M8Or2Ey0IZkfqyhnosx0cLJaFoUxaj8mB8iKvK4LUuNQgZbL+lxa4A7eaJt77Qcs oXb7XoE2zQukdyO0Tp7Gvm+8gCjr/wdEz+sJHCAAtQeeABeXQMYYlNh+PTnqCuoW MWLOg0cqaMYy+ZwzsD6kRDcGJtbJwZxsfkyQlJgSDQfBN/1rC18EDyyxlZlzsOTx SxLV+yD3deJqhVDdj57le/Bw/iNFJbh+R2zC5I71HCQL6ut5dHOhK0opI396aty1 8wYoFQGxiifPXty9RgzlsbodwcDTOmIjXfdNnyIOIM/Wjn4GcgI1vlaNQb9I1PK1 SvYzeMllRBwhGQ5nfYEDgukS2uWEKJeYLOYp4FJksTpa0HlGL3E= =B1XB -END PGP SIGNATURE End Message ---
Bug#979758: marked as done (xxhash: broken pkgconfig file)
Your message dated Mon, 11 Jan 2021 13:26:31 +
with message-id
and subject line Bug#979758: fixed in xxhash 0.8.0-2
has caused the Debian Bug report #979758,
regarding xxhash: broken pkgconfig file
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.)
--
979758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xxhash
Version: 0.8.0-1
Severity: serious
tags: patch
Hello, after trying hard to see why python3-pkgconfig was not detecting xxhash
I discovered that the Version field was empty
https://github.com/Cyan4973/xxHash/commit/b4dbf5fefc37b8a5f80b3bbc6b8ff639cf5f0ec2
This trivial commit fixes it.
To reproduce:
python3
>>> import pkgconfig
>>> pkgconfig.installed('libxxhash', '>= 0.7.3')
True
This is what is expected
G.
--- End Message ---
--- Begin Message ---
Source: xxhash
Source-Version: 0.8.0-2
Done: Norbert Preining
We believe that the bug you reported is fixed in the latest version of
xxhash, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated xxhash 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, 11 Jan 2021 21:57:57 +0900
Source: xxhash
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining
Changed-By: Norbert Preining
Closes: 977345 979758
Changes:
xxhash (0.8.0-2) unstable; urgency=medium
.
* Use hardware-accelerated XXH3 computation on x86 architecture, and
install the hardware-accelerating header file.
Thanks to Julian Andres Klode. (Closes: #977345)
* Cherry-pick upstream: Fix empty version in .pc file (Closes: #979758)
Checksums-Sha1:
4f344cf5cdbee4879cdf575f15e03e09d4124503 1601 xxhash_0.8.0-2.dsc
ad48ecf4f560d2913e98dd7f799a820843d6882a 4160 xxhash_0.8.0-2.debian.tar.xz
f9a7fd3fcc10cedbad7703161107e95641ccd38e 6152 xxhash_0.8.0-2_source.buildinfo
Checksums-Sha256:
91c696b5371558ebb12c323b0bd4e15eece0a439ef49c6aa5a6d0c1cf6c7762a 1601
xxhash_0.8.0-2.dsc
5c427c2c08019a945412afac02326a24c72b65a83bff59447009db303233aecd 4160
xxhash_0.8.0-2.debian.tar.xz
575014ec3f2637463ecc71370bbd9261c7989bfa23ed20f0fbeef5089397a459 6152
xxhash_0.8.0-2_source.buildinfo
Files:
6f399f537b336850d0593ecbc8d040a3 1601 utils optional xxhash_0.8.0-2.dsc
1558d7b4f99c39a3e94e6a760dc4368a 4160 utils optional
xxhash_0.8.0-2.debian.tar.xz
4a618b27e449c58e301d4469d79f3d54 6152 utils optional
xxhash_0.8.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/8TCsACgkQ2A4JsIcU
AGbYNQf/Z/0F5l+vS6WoIPN92eBLECBcSf+U4N2qBqdpiRWkgaAbWMEgj3DfsJS0
/M1nBOUhl/OdvXjwFQ7bZkY9TL1MVzqzlZ0Dx201IpdkEWLpg6N++TgHx8UrgM+s
jgPlu//pUvQlBkgfeK1IAx2uYJn09yKX+FYeYseex5X1wcLbNJDvs6l1TKGBBXQq
5JomyX92B3CnkfKG8s8mt4kMuO0s3zQ2kHvXwSjX02f0+yylg35ZaBVCRa4KqchQ
XLSTXh6kRxTaIiHUpyrnLv6FcHxczacqZGDXfYkuGCCmWVgQRMSmRSHrWDdpF0TW
uQVrj8NjC99V8EMRuesAiYxk+fzOaQ==
=2FLG
-END PGP SIGNATURE End Message ---
Bug#977345: marked as done (libxxhash built without hw-accelerated XXH3, 50% performance loss)
Your message dated Mon, 11 Jan 2021 13:26:31 +
with message-id
and subject line Bug#977345: fixed in xxhash 0.8.0-2
has caused the Debian Bug report #977345,
regarding libxxhash built without hw-accelerated XXH3, 50% performance loss
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.)
--
977345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xxhash
Version: 0.8.0-1
Severity: normal
XXH3 supports various hardware-accelerated variants in
xxh_x86dispatch.{c,h}, which are currently not built into the library.
This means that it only operates at roughly half the speed on my Core
i5-8250U compared to the AVX2-accelerated variant.
The implementation is odd: Client code explcitly has to use the
xxh_x86dispatch.h header instead of the xxhash.h one. It would be more
convenient if any code that includes xxhash.h on x86 automatically
benefits from dispatched optimized code.
At the bare minimum, on x86, export DIGEST=1 when building and install
xxh_x86dispatch.h header. I'd love to see the xxh_x86dispatch.h also
replace the xxhash.h header on x86 (still keeping xxh_x86dispatch.h in
case people look for it) such that clients can directly benefit from it
even if they do not handle looking up that header and using it.
-- System Information:
Debian Release: bullseye/sid
APT prefers hirsute
APT policy: (991, 'hirsute'), (500, 'hirsute'), (500, 'groovy-updates'),
(500, 'groovy-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-32-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
--- End Message ---
--- Begin Message ---
Source: xxhash
Source-Version: 0.8.0-2
Done: Norbert Preining
We believe that the bug you reported is fixed in the latest version of
xxhash, 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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated xxhash 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, 11 Jan 2021 21:57:57 +0900
Source: xxhash
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining
Changed-By: Norbert Preining
Closes: 977345 979758
Changes:
xxhash (0.8.0-2) unstable; urgency=medium
.
* Use hardware-accelerated XXH3 computation on x86 architecture, and
install the hardware-accelerating header file.
Thanks to Julian Andres Klode. (Closes: #977345)
* Cherry-pick upstream: Fix empty version in .pc file (Closes: #979758)
Checksums-Sha1:
4f344cf5cdbee4879cdf575f15e03e09d4124503 1601 xxhash_0.8.0-2.dsc
ad48ecf4f560d2913e98dd7f799a820843d6882a 4160 xxhash_0.8.0-2.debian.tar.xz
f9a7fd3fcc10cedbad7703161107e95641ccd38e 6152 xxhash_0.8.0-2_source.buildinfo
Checksums-Sha256:
91c696b5371558ebb12c323b0bd4e15eece0a439ef49c6aa5a6d0c1cf6c7762a 1601
xxhash_0.8.0-2.dsc
5c427c2c08019a945412afac02326a24c72b65a83bff59447009db303233aecd 4160
xxhash_0.8.0-2.debian.tar.xz
575014ec3f2637463ecc71370bbd9261c7989bfa23ed20f0fbeef5089397a459 6152
xxhash_0.8.0-2_source.buildinfo
Files:
6f399f537b336850d0593ecbc8d040a3 1601 utils optional xxhash_0.8.0-2.dsc
1558d7b4f99c39a3e94e6a760dc4368a 4160 utils optional
xxhash_0.8.0-2.debian.tar.xz
4a618b27e449c58e301d4469d79f3d54 6152 utils optional
xxhash_0.8.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/8TCsACgkQ2A4JsIcU
AGbYNQf/Z/0F5l+vS6WoIPN92eBLECBcSf+U4N2qBqdpiRWkgaAbWMEgj3DfsJS0
/M1nBOUhl/OdvXjwFQ7bZkY9TL1MVzqzlZ0Dx201IpdkEWLpg6N++TgHx8UrgM+s
jgPlu//pUvQlBkgfeK1IAx2uYJn09yKX+FYeYseex5X1wcLbNJDvs6l1TKGBBXQq
5JomyX92B3CnkfKG8s8mt4kMuO0s3zQ2kHvXwSjX02f0+yylg35ZaBVCRa4KqchQ
XLSTXh6kR
Bug#979805: marked as done (node-https-proxy-agent: Please remove deprecated node-typescript-types dependency)
Your message dated Mon, 11 Jan 2021 13:03:57 + with message-id and subject line Bug#979805: fixed in node-https-proxy-agent 5.0.0-3 has caused the Debian Bug report #979805, regarding node-https-proxy-agent: Please remove deprecated node-typescript-types dependency 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.) -- 979805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-https-proxy-agent Severity: important node-https-proxy-agent (build?) depends on transitional package node-typescript-types. It should instead depend explicitly on packages corresponding with each required Node.js module. Severity raised in the hope that we can drop node-typescript-types soon. --- End Message --- --- Begin Message --- Source: node-https-proxy-agent Source-Version: 5.0.0-3 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of node-https-proxy-agent, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated node-https-proxy-agent 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, 11 Jan 2021 07:34:04 -0500 Source: node-https-proxy-agent Architecture: source Version: 5.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Andrius Merkys Closes: 979805 Changes: node-https-proxy-agent (5.0.0-3) unstable; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Bug-Submit. * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright). . [ Andrius Merkys ] * Dropping dependency on node-typescript-types (Closes: #979805). Checksums-Sha1: 59dfeefe620605c721589e3d5e905c165c77d896 2312 node-https-proxy-agent_5.0.0-3.dsc 232b574eecf0052d57afef3128e5daefbb7bbd2d 2640 node-https-proxy-agent_5.0.0-3.debian.tar.xz b4705981787be3b34c25c9f78844d5ee5d537d62 11335 node-https-proxy-agent_5.0.0-3_source.buildinfo Checksums-Sha256: fed3c075fd45b1fcbefeb9ee15b1e2f9a05f7f1b77c7ebce8cec81583b65b8dc 2312 node-https-proxy-agent_5.0.0-3.dsc 67d91452b2efbbdd3c600a5e1178eac5c655d603cc33de45da876037cd80e28d 2640 node-https-proxy-agent_5.0.0-3.debian.tar.xz 83a00d5f9153f145e3cf7de5d45a1c54f08e77a9bf56f24b21812642576130fa 11335 node-https-proxy-agent_5.0.0-3_source.buildinfo Files: 3bf568b656178895f9cc77209eef9529 2312 javascript optional node-https-proxy-agent_5.0.0-3.dsc 3812dd53ee0442ce565a4d8a3eca25c8 2640 javascript optional node-https-proxy-agent_5.0.0-3.debian.tar.xz dbb0ad742b3129d2226984a574839074 11335 javascript optional node-https-proxy-agent_5.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl/8RyQSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHPmYP/3TJQ8A3ZtfKMFCBRm5w07qGOU5bJ6Jn H07zum9rkiH9dYIeyVDxg4n6IOkygEzo0aCK/eFgLR2mR6dCwig/QwPAWPaBUYL1 XlcW+jDrDAvHmqeSXnSkjUIOY0vLGCWecxIY/nAsqjdibgOXgaBNbeshis5TGzu+ H+nxlMF1FXVb4/aou5fMZad9SGkKk6iuu2+YjWTXs8ih1Ch63Yia6X9CoCKMUYPx h4G8PmbGz02jSeXZWirO99hLNsUNy06Lj0b9+yP2ub8bZaDpyYkZ4fNCG3j+GXuR a0W8WJCS+TCNsBVBbYad0OqsdR6F6BxT9x0jmVFcPdU5xELx/lg1V6H8/Yl6hRNt KYrhjF/GS2+EgW6B3sPB7HkAkr5UBAzu04EJra3imt9J6m0G6xD4nkxdcXOPSnMr ewexPmKkxopNeLLaHGabDt/9O1vPyiksVbjfJqzSjH59Pn/TX+jZY01SZXtq3E4N QkLQWFRNi55VxmWjXBxJAZTgwD67l6soZuqSDR3pkOLcBCUa5l3h++15tA543swy IGmUVun6PTWn4tJgx4CSrTQQPXu//tOa/t0wmx7gJ7O+VCwAylGociWiOXJTNvDY s+Rkrm3Wodj7bLARPwz5w2Acr/GiHPE+EDHltVwlB3D1xgdwwy+XTuH0QYGr2JYX OvEND5S2ZgFw =9Fje -END PGP SIGNATURE End Message ---
Bug#979338: marked as done (python3-scapy: hardcodes tcpdump location to /usr/sbin/tcpdump)
Your message dated Mon, 11 Jan 2021 13:13:43 +0100 with message-id and subject line Fixed in 2.4.4-4 has caused the Debian Bug report #979338, regarding python3-scapy: hardcodes tcpdump location to /usr/sbin/tcpdump 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.) -- 979338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-scapy Version: 2.4.4-3 Severity: normal In tcpdump 4.99.0-1, the location of the tcpdump binary was changed from /usr/sbin/tcpdump to /usr/bin/tcpdump. This causes autopkgtest to fail for scapy, as the path is hardcoded to the old location via this patch: https://salsa.debian.org/pkg-security-team/scapy/-/raw/debian/master/debian/patches/use-absolute-paths.patch Simply removing the patch will allow the test suite to pass again, however you may consider versioning the dependency on tcpdump in the autopkgtest control file to ensure that the location will match the tcpdump version. Note that the location change may also impact operation of Scapy itself, in which case the severity of this bug would likely be higher than 'normal'. I have not tested this. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-scapy depends on: ii libjs-sphinxdoc 3.4.1-1 ii python3 3.9.1-1 ii sphinx-rtd-theme-common 0.5.0+dfsg-1 Versions of packages python3-scapy recommends: ii ipython3 7.19.0-3 pn python3-cryptography ii tcpdump 4.99.0-1 Versions of packages python3-scapy suggests: pn graphviz pn python3-matplotlib pn python3-pyx pn sox pn tcpreplay pn wireshark -- no debconf information --- End Message --- --- Begin Message --- Version: 2.4.4-4 This has been fixed in the last upload. Date: Mon, 11 Jan 2021 11:40:10 +0100 Source: scapy Architecture: source Version: 2.4.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Raphaël Hertzog Changes: scapy (2.4.4-4) unstable; urgency=medium . * Team upload. . [ Romain Francoise ] * Drop debian/patches/use-absolute-paths.patch (#979338) * debian/tests/control: version dependency on tcpdump * Cherry-pick upstream commit 42d58d8729 to fix pipetool test (and thus fix autopkgtest too) -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS--- End Message ---
Bug#979618: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 87.0.4280.88-0.4 Severity: grave X-Debbugs-Cc: deb...@rocketjump.eu Hi, starting chromium on bullseye will render a window (with various elements shifted down by half a screen), which is impossible to interact with, and causes gnome to offer a "force quit" prompt after a few seconds. Output from the CLI: ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- $ chromium libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [9413:9413:0109/060426.733876:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error [9413:9413:0109/060426.735693:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [9413:9413:0109/060426.855283:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.858413:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.860282:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.867099:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.869489:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9415:9428:0109/060426.876651:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 [9413:9413:0109/060426.993836:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060430.833703:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! [9413:9413:0109/060430.839756:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 2 times! Killed ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- Various things I've tried: - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - starting chromium with a fresh profile -> same problem Installing debug symbols and starting `chromium -g` will result in the same errors, except for chromium complaining about being started in single-process mode. One user on #debian-next IRC reported no such errors on sid and KDE, so it might not effect all users. I *think* about a week ago chromium still ran fine (I only use it for debugging purposes). Checking /var/log/apt/history.log, I don't see any libva* packages being updated in that timeframe. Regards, Lee -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.88-0.4 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-3 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-6 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-4 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii
Bug#979590: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-xcb1 Version: 2:1.7.0-1 Severity: normal X-Debbugs-Cc: mic...@lebihan.pl Dear Maintainer, After updating libx11-xcb1 chromium and google chrome UI is not responding to any input and clicking anywhere on the app window causes the GNOME app is not responding dialog to appear. The app actually is not frozen because if you pass a URL with dynamic web content as a parameter, it will be constantly updated. I didn't notice any other affected app, but I didn't test much. Michel Le Bihan -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: libx11 Source-Version: 2:1.7.0-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of libx11, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated libx11 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, 11 Jan 2021 12:15:25 +0100 Source: libx11 Architecture: source Version: 2:1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 979590 Changes: libx11 (2:1.7.0-2) unstable; urgency=medium . * Set a strict dependency of libx11-xcb1 on libx11-6, as internal ABI may change across releases - and indeed did change between 1.6.12 and 1.7.0 (closes: #979590) * Update upstream git URL in package descriptions. Checksums-Sha1: 9d7689b4f621e72e48cc225a5986b123b5102b98 2564 libx11_1.7.0-2.dsc f0294ed61e0ce05da05d1f7ea3682536e0f5ae96 73844 libx11_1.7.0-2.diff.gz Checksums-Sha256: 1540dcbbbdf7e08405d133127ca6f63fe191a3946ae9c5afc95293bc12f784a1 2564 libx11_1.7.0-2.dsc 910d4a1527458ff020f0bab9df55bab44d63db8247543d2b2256c7b258ce439c 73844 libx11_1.7.0-2.diff.gz Files: e8781a3e2d7accd1f2057d91a5940570 2564 x11 optional libx11_1.7.0-2.dsc f8911845bfd953f82a3ef1ac0697e022 73844 x11 optional libx11_1.7.0-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl/8NhYUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z61cYg/5AeB5A0SF/qCS2fCCaADJOla4RJlH HZPna/MmPxIonahyZ3caCuhJ+7etZdq9vAyGLqoy4wLyYWp3Xbq4Htx0TFDxGBHD qA0OTW7QmhrlrIs3b+140UmXaehasc7PD8paAlLzaWkqC6A5de30VCoE/XDzufNo V5qeVh/ouXFGzBtbY0UaOA9nLM1IewzL2bqt48U++QbgYDcLu49rc5JEIdEAzcf2 twe+4BIk0tRTItfxswbu+wdUXam3uzYoUwcH92Q306IBoTT2Ls4cErPaiHmovfsP eWjKU7f8sKKBF7AdkVqd8roBtTEHsa23Je09vdB0JFF7+Dljuj/cmUoDg5JbracU aZIrHrVobVJqwGExof2lIXQe1uuBPcLGGuKXNQuUSXuN6Q/jX3mfxn9flCpiij+K +u1Iu5CFjuwo8dHluHk14ev5yZ/jSTx0WT6bvNQHnr6RYpAt4cat7ST6NJluS8U7 5OlL4AaoVw4nuxW8WzimWk/XtaDwI2/XIK4cdnb41l4MlT4Qt/iwtPyifZX9rvnZ WL3Y6T0ZqRi8o2qSPUVIpIrOcW+JBLL7maKCw1I/oonbs4leFRSV5KxZzWoV9ATy iUM0H0/OHAx/EanyrgGhLhu8bn+W9dXj6vmMXPOpujwxcfv1vQO7BOfLw4Mk78oe 8GNy4TAE57g/XCE= =jAIK -END PGP SIGNATURE End Message ---
Bug#971299: marked as done (onionshare: Switch to python3-pycryptodome)
Your message dated Mon, 11 Jan 2021 11:54:39 + with message-id and subject line Bug#971299: fixed in onionshare 2.2-3 has caused the Debian Bug report #971299, regarding onionshare: Switch to python3-pycryptodome 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.) -- 971299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onionshare Version: 2.2-2 Severity: important Tags: sid bullseye Usertags: pycrypto Dear maintainer, onionshare currently Build-Depends or Depends on python3-crypto from PyCrypto. This project is no longer maintained and PyCryptodome (https://www.pycryptodome.org/en/latest/) provides a drop in replacement. Please switch to python3-pycryptodome. I'd like to remove python-crypto before the release of bullseye. Cheers --- End Message --- --- Begin Message --- Source: onionshare Source-Version: 2.2-3 Done: Clément Hermann We believe that the bug you reported is fixed in the latest version of onionshare, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clément Hermann (supplier of updated onionshare 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, 11 Jan 2021 12:30:19 CET Source: onionshare Binary: Architecture: source Version: 2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Clément Hermann Description: Closes: 965055 965152 971299 Changes: onionshare (2.2-3) unstable; urgency=medium . [ Ulrike Uhlig ] * Correct and update manpages. (Closes: #965055) * Document --website option in manpages. (Closes: #965152) * Replace python3-crypto by python3-pycryptodome (Closes: #971299) * Add debian/patches/cryptodome.diff to use the cryptodome namespace. Note that this does not fix the root cause in #886291. . [ Clément Hermann ] * manpage: fix groff warning (missing escape) * d/Copyright: Add missing license info for appstream metadata * d/missing-sources: refresh jquery to 3.4.0 * d/patches/cryptodome.diff: Add DEP-3 headers * d/control: - declare compliance with Debian Policy 4.5.1 (no change) - add myself to uploaders Checksums-Sha256: 5e49b4e44a07ecdbacf79301f503d6d1716bd3e8258bea38e6717bab7da564f6 2254 onionshare_2.2-3.dsc 3cfe3ae2fb64eaa58aee497ad1f32f4123b83da64b676d6ff8597d4ffa1aabf7 78340 onionshare_2.2-3.debian.tar.xz ec4fcd8ee00eb4c1d8855c3482b4afba5b9e3bde73f9b3e2fb86e80714848239 14130 onionshare_2.2-3_sourceonly.buildinfo Checksums-Sha1: b137668733981cbc6776234581c0322dfd133309 2254 onionshare_2.2-3.dsc a97f75dcdad575e50d62d9a0e96f7823d35a2821 78340 onionshare_2.2-3.debian.tar.xz 7860613bbde0c2918731d5f503c683acd26a6ae7 14130 onionshare_2.2-3_sourceonly.buildinfo Files: 58a4147235de4eb7f77a8f9a54f860a9 2254 net optional onionshare_2.2-3.dsc aa9794e0a48a24e6e4dfc85f4c98dc63 78340 net optional onionshare_2.2-3.debian.tar.xz 7b92df43b8e9eca22566c6c5ad89edac 14130 - - onionshare_2.2-3_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAl/8NtkACgkQ2KOaUw8N zMsEHw//cSnbxu2DlLBOxG+SEKMphJt7nntpRi16DtkkIoX9h4z7lo1+ngKQi01+ AHkUaB7Nu6cLiU1oTE0OLU342RTGkAkx7NQNnTJskQXYjQDRWSUrn0kegE5ZF6w5 tBhpTo+5DqbDuKfqbbCtR1dTf2NblQN6iWBfH1qCdHcMl4NYls1IFcPbTXHepT/P gQ9SJ2y1oyqGyijS3GLPV1sRw/b0zXij8W7ChMWKpMOX2TvGAmL/0mAJfJwa9xpr 31J6rvKQMMlDk1DXw6a3N08kdyjUPnhG6Gd+dxpet/9+qF65LTnVj9AydqOZRRuO Nx+fmGBOA/58ODsexKMfI0Qfz1KkOwF+CF1E/o8kfXziWRniEIOTvbmDrtLFvBjD IYU6WPznGv7RLzOQ9r6Ci02JYwGZoTjFkeyf0Yw/VgG/0vskMnPMJjEucafr187y fSQh8kIKKfJBocV7eknbChfQfz9YZerh9yLx/yio6gX8pbysRtdKut83L3SVlHuG zg+5jBPyCNbynRAtuioIGju8YQH4k0EBRpqVL62P+py5C+IpQz1RLY08wZsHkqUB MW0cM7bce8xObKjmxjCeR0VnADqGgPqgYAAnDif0U4/+AvAi8hIRGdhq3ltbKahZ MtpCUNV/Tbm0SnPV2608znx83ZSUkeh14d4mvnHJAm/EVTC9TMg= =iZxs -END PGP SIGNATURE End Message ---
Bug#965152: marked as done (onionshare man page: undocumented --website)
Your message dated Mon, 11 Jan 2021 11:54:39 + with message-id and subject line Bug#965152: fixed in onionshare 2.2-3 has caused the Debian Bug report #965152, regarding onionshare man page: undocumented --website 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.) -- 965152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: onionshare Version: 2.2-2 Severity: minor The --website option is not documented in the manual page. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: onionshare Source-Version: 2.2-3 Done: Clément Hermann We believe that the bug you reported is fixed in the latest version of onionshare, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clément Hermann (supplier of updated onionshare 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, 11 Jan 2021 12:30:19 CET Source: onionshare Binary: Architecture: source Version: 2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Clément Hermann Description: Closes: 965055 965152 971299 Changes: onionshare (2.2-3) unstable; urgency=medium . [ Ulrike Uhlig ] * Correct and update manpages. (Closes: #965055) * Document --website option in manpages. (Closes: #965152) * Replace python3-crypto by python3-pycryptodome (Closes: #971299) * Add debian/patches/cryptodome.diff to use the cryptodome namespace. Note that this does not fix the root cause in #886291. . [ Clément Hermann ] * manpage: fix groff warning (missing escape) * d/Copyright: Add missing license info for appstream metadata * d/missing-sources: refresh jquery to 3.4.0 * d/patches/cryptodome.diff: Add DEP-3 headers * d/control: - declare compliance with Debian Policy 4.5.1 (no change) - add myself to uploaders Checksums-Sha256: 5e49b4e44a07ecdbacf79301f503d6d1716bd3e8258bea38e6717bab7da564f6 2254 onionshare_2.2-3.dsc 3cfe3ae2fb64eaa58aee497ad1f32f4123b83da64b676d6ff8597d4ffa1aabf7 78340 onionshare_2.2-3.debian.tar.xz ec4fcd8ee00eb4c1d8855c3482b4afba5b9e3bde73f9b3e2fb86e80714848239 14130 onionshare_2.2-3_sourceonly.buildinfo Checksums-Sha1: b137668733981cbc6776234581c0322dfd133309 2254 onionshare_2.2-3.dsc a97f75dcdad575e50d62d9a0e96f7823d35a2821 78340 onionshare_2.2-3.debian.tar.xz 7860613bbde0c2918731d5f503c683acd26a6ae7 14130 onionshare_2.2-3_sourceonly.buildinfo Files: 58a4147235de4eb7f77a8f9a54f860a9 2254 net optional onionshare_2.2-3.dsc aa9794e0a48a24e6e4dfc85f4c98dc63 78340 net optional onionshare_2.2-3.debian.tar.xz 7b92df43b8e9eca22566c6c5ad89edac 14130 - - onionshare_2.2-3_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAl/8NtkACgkQ2KOaUw8N zMsEHw//cSnbxu2DlLBOxG+SEKMphJt7nntpRi16DtkkIoX9h4z7lo1+ngKQi01+ AHkUaB7Nu6cLiU1oTE0OLU342RTGkAkx7NQNnTJskQXYjQDRWSUrn0kegE5ZF6w5 tBhpTo+5DqbDuKfqbbCtR1dTf2NblQN6iWBfH1qCdHcMl4NYls1IFcPbTXHepT/P gQ9SJ2y1oyqGyijS3GLPV1sRw/b0zXij8W7ChMWKpMOX2TvGAmL/0mAJfJwa9xpr 31J6rvKQMMlDk1DXw6a3N08kdyjUPnhG6Gd+dxpet/9+qF65LTnVj9AydqOZRRuO Nx+fmGBOA/58ODsexKMfI0Qfz1KkOwF+CF1E/o8kfXziWRniEIOTvbmDrtLFvBjD IYU6WPznGv7RLzOQ9r6Ci02JYwGZoTjFkeyf0Yw/VgG/0vskMnPMJjEucafr187y fSQh8kIKKfJBocV7eknbChfQfz9YZerh9yLx/yio6gX8pbysRtdKut83L3SVlHuG zg+5jBPyCNbynRAtuioIGju8YQH4k0EBRpqVL62P+py5C+IpQz1RLY08wZsHkqUB MW0cM7bce8xObKjmxjCeR0VnADqGgPqgYAAnDif0U4/+AvAi8hIRGdhq3ltbKahZ MtpCUNV/Tbm0SnPV2608znx83ZSUkeh14d4mvnHJAm/EVTC9TMg= =iZxs -END PGP SIGNATURE End Message ---
Bug#965055: marked as done (onionshare man page: "crypto key lives in /tmp/onionshare/tmpXXX/private_key")
Your message dated Mon, 11 Jan 2021 11:54:39 + with message-id and subject line Bug#965055: fixed in onionshare 2.2-3 has caused the Debian Bug report #965055, regarding onionshare man page: "crypto key lives in /tmp/onionshare/tmpXXX/private_key" 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.) -- 965055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: onionshare Version: 2.2-2 Severity: minor The onionshare(1) man page says: "the crypto key lives in /tmp/onionshare/tmpXXX/private_key". I don't belive this is correct. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: onionshare Source-Version: 2.2-3 Done: Clément Hermann We believe that the bug you reported is fixed in the latest version of onionshare, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clément Hermann (supplier of updated onionshare 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, 11 Jan 2021 12:30:19 CET Source: onionshare Binary: Architecture: source Version: 2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Clément Hermann Description: Closes: 965055 965152 971299 Changes: onionshare (2.2-3) unstable; urgency=medium . [ Ulrike Uhlig ] * Correct and update manpages. (Closes: #965055) * Document --website option in manpages. (Closes: #965152) * Replace python3-crypto by python3-pycryptodome (Closes: #971299) * Add debian/patches/cryptodome.diff to use the cryptodome namespace. Note that this does not fix the root cause in #886291. . [ Clément Hermann ] * manpage: fix groff warning (missing escape) * d/Copyright: Add missing license info for appstream metadata * d/missing-sources: refresh jquery to 3.4.0 * d/patches/cryptodome.diff: Add DEP-3 headers * d/control: - declare compliance with Debian Policy 4.5.1 (no change) - add myself to uploaders Checksums-Sha256: 5e49b4e44a07ecdbacf79301f503d6d1716bd3e8258bea38e6717bab7da564f6 2254 onionshare_2.2-3.dsc 3cfe3ae2fb64eaa58aee497ad1f32f4123b83da64b676d6ff8597d4ffa1aabf7 78340 onionshare_2.2-3.debian.tar.xz ec4fcd8ee00eb4c1d8855c3482b4afba5b9e3bde73f9b3e2fb86e80714848239 14130 onionshare_2.2-3_sourceonly.buildinfo Checksums-Sha1: b137668733981cbc6776234581c0322dfd133309 2254 onionshare_2.2-3.dsc a97f75dcdad575e50d62d9a0e96f7823d35a2821 78340 onionshare_2.2-3.debian.tar.xz 7860613bbde0c2918731d5f503c683acd26a6ae7 14130 onionshare_2.2-3_sourceonly.buildinfo Files: 58a4147235de4eb7f77a8f9a54f860a9 2254 net optional onionshare_2.2-3.dsc aa9794e0a48a24e6e4dfc85f4c98dc63 78340 net optional onionshare_2.2-3.debian.tar.xz 7b92df43b8e9eca22566c6c5ad89edac 14130 - - onionshare_2.2-3_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAl/8NtkACgkQ2KOaUw8N zMsEHw//cSnbxu2DlLBOxG+SEKMphJt7nntpRi16DtkkIoX9h4z7lo1+ngKQi01+ AHkUaB7Nu6cLiU1oTE0OLU342RTGkAkx7NQNnTJskQXYjQDRWSUrn0kegE5ZF6w5 tBhpTo+5DqbDuKfqbbCtR1dTf2NblQN6iWBfH1qCdHcMl4NYls1IFcPbTXHepT/P gQ9SJ2y1oyqGyijS3GLPV1sRw/b0zXij8W7ChMWKpMOX2TvGAmL/0mAJfJwa9xpr 31J6rvKQMMlDk1DXw6a3N08kdyjUPnhG6Gd+dxpet/9+qF65LTnVj9AydqOZRRuO Nx+fmGBOA/58ODsexKMfI0Qfz1KkOwF+CF1E/o8kfXziWRniEIOTvbmDrtLFvBjD IYU6WPznGv7RLzOQ9r6Ci02JYwGZoTjFkeyf0Yw/VgG/0vskMnPMJjEucafr187y fSQh8kIKKfJBocV7eknbChfQfz9YZerh9yLx/yio6gX8pbysRtdKut83L3SVlHuG zg+5jBPyCNbynRAtuioIGju8YQH4k0EBRpqVL62P+py5C+IpQz1RLY08wZsHkqUB MW0cM7bce8xObKjmxjCeR0VnADqGgPqgYAAnDif0U4/+AvAi8hIRGdhq3ltbKahZ MtpCUNV/Tbm0SnPV2608znx83ZSUkeh14d4mvnHJAm/EVTC9TMg= =iZxs -END PGP SIGNATURE End Message ---
Bug#432823: marked as done (libfcgi-dev: unable to properly handle Expect:100-Continue ?)
Your message dated Mon, 11 Jan 2021 14:27:04 +0300 with message-id <1509311610364...@mail.yandex.ru> and subject line Re: Bug#432823: libfcgi-dev: unable to properly handle Expect:100-Continue ? has caused the Debian Bug report #432823, regarding libfcgi-dev: unable to properly handle Expect:100-Continue ? 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.) -- 432823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfcgi-dev Version: 2.4.0-5 Severity: normal I am using the fastcgi_stdio package under apache2 and encountered a situation which I am not sure is the problem of apache2 or the cgi protocol or fastcgi itself. If the client put a "Expect: 100-Continue" in the header, either apache2 or fastcgi recognize it and that I can no longer retrieve any of those CGI parameters or HTTP_* headers, until I write out "Status: xxx" message through the interface. This however is wrong logical wise as I need the CGI parameters for processing before I can put out the right Status line. So instead of responding 403 for access denied(say for an upload), the client receive a 200 OK then a body text of 403. This is all wrong. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.18.1-grsec+e+f6b+gr219+opt+c4a+gr2b-grsec Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libfcgi-dev depends on: ii libfcgi0 2.4.0-5Shared library of FastCGI -- no debconf information --- End Message --- --- Begin Message --- Hi, As far as I see at [1] the bug was in Apache and it should be fixed since Apache version 2.2.8. [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=38014 Best regards, Boris--- End Message ---
Bug#979664: marked as done (apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21)
Your message dated Mon, 11 Jan 2021 11:18:32 + with message-id and subject line Bug#979664: fixed in apache2 2.4.46-4 has caused the Debian Bug report #979664, regarding apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21 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.) -- 979664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache2 Version: 2.4.46-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/a/apache2/9549366/log.gz # Failed test 2 in t/modules/data.t at line 21 t/modules/data.t Failed 1/2 subtests [...] Test Summary Report --- t/modules/data.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 Files=134, Tests=10102, 318 wallclock secs ( 3.23 usr 0.30 sys + 201.11 cusr 50.96 csys = 255.60 CPU) Result: FAIL Failed 1/134 test programs. 1/10102 subtests failed. [warning] server localhost:8529 shutdown [ error] error running tests (please examine t/logs/error_log) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.46-4 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of apache2, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated apache2 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, 11 Jan 2021 11:58:23 +0100 Source: apache2 Architecture: source Version: 2.4.46-4 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Xavier Guimard Closes: 979664 Changes: apache2 (2.4.46-4) unstable; urgency=medium . * Ignore other random another test failures (Closes: #979664) Checksums-Sha1: bda62f5b58a48e56bbfceb5f41b7bd968c7fc263 3501 apache2_2.4.46-4.dsc a7c3eb412e1624e3e967754e6e701a129c736eef 882336 apache2_2.4.46-4.debian.tar.xz Checksums-Sha256: 1ebe1ce5b99df7660c98eacad3acc104063afa955bdc37fc18c5bd4ef536538e 3501 apache2_2.4.46-4.dsc c3fb8c74db25010cf663582332eb38f1679a678d7ad40a4ffbd40fe74ce68759 882336 apache2_2.4.46-4.debian.tar.xz Files: 94f9e3e434a762e385b6270609427511 3501 httpd optional apache2_2.4.46-4.dsc b8a574a930140e42d502b9d7da58b04c 882336 httpd optional apache2_2.4.46-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8MKQACgkQ9tdMp8mZ 7umDfQ//b/jeUeSd7Q0P5qTyj/xAay8akQ6a0n7LAqAvqMaezikLymDPq8MECtza 8zZSo4WtpjIwlWUVxXYWkWNnosw4saloD/R1HFRLYFsRREwyGfBJPdThB4nAIeCp uqEL6Unh0eWGajTT+Gg9r/uEkB9dtNnA1e5zTLSmH9mtd3E29zfm1k/S+9qClKW4 I8fHvfepylrXcrHFwv6/WQ/bFEitP9d6QYKi6hxEZN2laC8OuVDOqt6JRVP1OSRW 7/3NMSz0PF208eSaM4re1d+hSWuAIWPOmWIHxsJnwoqWXwlO5DwAc4nZkAPAioCF +TgLIRZC2+Ut9ukrlDIJKBxHiVTSoKIH/MdmPn/egqMnhoW4ndbqDbreVGhXtWBE I3dulNZxVJH05BQf97qtIquhYrj8vGj43W8Lu2ctRcDbVrLjfbDyS/EWdSOJD2YE wjsGUEbbAjFZlVzUNc83EKocZyPKtK4f+JBEIJEFoCJ7Ovt+VhikZPND1GGbmgIZ plyPP98U2Ka17TEI9w5CM0uLTcj1K96KiEfKUcz+xzLMzx3pGTD6/WL67XnKeIE8 78qhQ7ybCdYgezALYfh2R2sf31B5s7I8nBXGOqGFkGxnkc4uVjNx0s+nXuhhh15j RKvZ6DyvsvW8i5UXgikEly+jNtoA1dflIaKD4SYhtTLceM2iBgU= =D/xG -END PGP SIGNATURE End Message ---
Bug#979000: marked as done (libasound2: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all)
Your message dated Mon, 11 Jan 2021 11:58:19 +0100 with message-id <2021005819.oykhvgk6qpago...@toy.home.lxtec.de> and subject line Re: Bug#979000: libasound2: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all has caused the Debian Bug report #979000, regarding libasound2: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all 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.) -- 979000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libasound2 Version: 1.2.4-1 Severity: important Tags: newcomer X-Debbugs-Cc: maya587...@re-gister.com With Debian testing freshly installed on my new Lenovo IdeaPad 5 14ARE05 (dual boot with Win 10), the sound output isn't working. I can only select 'HDMI1 Output' or 'HDMI2 Output' as an output device. This issue seems to be the one described here for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157 According to the thread this has been fixed for Ubuntu, but I couldn't find it in the changelogs of Debian alsa-lib. Here's my output of $ lspci -nnk | grep -A2 Audio 04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: snd_hda_intel -- 04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:3822] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:3823] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libasound2 depends on: ii libasound2-data 1.2.4-1 ii libc62.31-6 libasound2 recommends no packages. Versions of packages libasound2 suggests: ii libasound2-plugins 1.2.2-2 -- no debconf information --- End Message --- --- Begin Message --- * Maya [2021-01-10 22:39 +0100]: > Awesome, that did it! :-) > Thanks a lot! Closed hereby. Thanks for cooperation Elimar -- Numeric stability is probably not all that important when you're guessing;-)--- End Message ---
Bug#882467: marked as done (node-typescript-types: should provide virtual packages for each /type package, versioned)
Your message dated Mon, 11 Jan 2021 11:47:45 +0100 with message-id <3ae6d959-d987-34f9-1ff7-5e6c25168...@debian.org> and subject line node-typescript-types is now a transitional package has caused the Debian Bug report #882467, regarding node-typescript-types: should provide virtual packages for each /type package, versioned 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.) -- 882467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-typescript-types Version: 20170519-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Currently there is no way to ensure dependency on a specific version of a specific Typescript type library. Please add "Provides:" hints for each included type library, with version (which should be supported with recent APT tools). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloWmLYACgkQLHwxRsGg ASGeJA/9HKQylf8tPxDVcOeExxp398FRg8rXiJZAdpJ0pEqE+ArvZmYKwxfx2Uxn lEe4+aeStmvqe76lazoESQf/16ft8KD+lBgoWY42TiuZ+XDu/yRfikFFCOh0DRBU nonGW8KMWD7TFwrz2Qnzu6J1TxW6pNrKLmZ9z8nTgZJn37sVxaLAw7pA6KAGZG2Z b/Je1Mjba1GAcZDR23NWr+doSE0imCQWf/d2q1cdknPBMVoDilWFHy3ENIOR+sFF McuSAOxC738CZarPzYl+B1CKWl/jcNGmr8W4dZGvjOFKyx6d6DOWlrf63+IGStsW as3ZKroKxe1BqQppKiLaO7GjadQitqKofDJV9rchLXl35BRy7c+c4GFMHqu/9Sqr vnovY3FtrHiJRRQOfCrrNSTTZ1AsKJ6v/s4ysQVxdAnUwJu/4LWDdFLJIIKB0xOI QbFQyZUfhfTH34fKLXx21dRUE8AppjDcTwvG89RrSv2TJWjkXH1UCMZaw9gvm/O8 GrUzA5DRGodnNFNFH/nR7ZOL8BJCfnzNuIQjEunCnSkZzt5o0Kh59PUI9UwlcKrV 2yU0Wqx0OXQ/eXQ1A1QQHr1P+f+t0CWDRj7zPJwWXR0QJJDNCDJqIcPXG5/QxwYX Gyh5w2kCrWg+tBxSEoLh/oRtxGKCWHbd8sxnzL8XeTvvqvF71VQ= =MnOj -END PGP SIGNATURE- --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 0--- End Message ---
Bug#930253: marked as done (convert get-orig-source.sh to debian/watch + uscan and multiple tarballs)
Your message dated Mon, 11 Jan 2021 11:47:45 +0100 with message-id <3ae6d959-d987-34f9-1ff7-5e6c25168...@debian.org> and subject line node-typescript-types is now a transitional package has caused the Debian Bug report #930253, regarding convert get-orig-source.sh to debian/watch + uscan and multiple tarballs 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.) -- 930253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:typescript-types version: 20190209-1 severity: wishlist If there is an agreement in principle, I can help with implementing it. See node-gulp for an example of using multiple tarballs. --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 1--- End Message ---
Bug#979666: marked as done (cross-toolchain-base_50_all-buildd.changes REJECTED)
Your message dated Mon, 11 Jan 2021 11:49:38 +0100 with message-id <84fdb3f3-acf8-5dca-c469-137407258...@debian.org> and subject line 51 successfully built has caused the Debian Bug report #979666, regarding cross-toolchain-base_50_all-buildd.changes REJECTED 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.) -- 979666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base Version: 50 Severity: serious - Forwarded message from Debian FTP Masters - From: Debian FTP Masters To: all / amd64 / i386 Build Daemon Date: Sat, 09 Jan 2021 21:18:45 + Subject: cross-toolchain-base_50_all-buildd.changes REJECTED Message-Id: Version check failed: Your upload included the binary package libc6-amd64-cross, version 2.31-9cross1, for all, however unstable already has version 2.31-9cross1. Uploads to unstable must have a higher version than present in unstable. Mapping sid to unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. - End forwarded message - --- End Message --- --- Begin Message --- 51 successfully built.--- End Message ---
Bug#887214: marked as done (nomad should depend on e2fsprogs explicitly)
Your message dated Mon, 11 Jan 2021 12:01:15 +0200 with message-id <2021000115.ga52...@tty.gr> and subject line Re: Bug#887214: nomad should depend on e2fsprogs explicitly has caused the Debian Bug report #887214, regarding nomad should depend on e2fsprogs explicitly 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.) -- 887214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nomad Version: 0.4.0+dfsg-1 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. nomad was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/bin/nomad contains debugfs. According to file it is a ELF 64-bit LSB executable, x86-64, version 1 (SYSV) Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- On Mon, Jan 11, 2021 at 01:04:47PM +1100, Dmitry Smirnov wrote: > On Monday, 11 January 2021 8:42:44 AM AEDT Faidon Liambotis wrote: > > It doesn't look like this code uses any binary from e2fsprogs, and > > therefore I don't think a dependency is needed, i.e. I think this is a > > false positive. > > > > Leaving this open for now in case the maintainer disagrees. Happy to > > look into things further if that's the case. > > I also think it is a false positive. When I looked at it, I could not > find explicit use of (anything from) e2fsprogs. Thanks for confirming. Great! Resolving then, thanks for confirming! Best, Faidon--- End Message ---
Bug#977888: marked as done (kdenlive: Missing icons etc. when installed on non-KDE environment)
Your message dated Mon, 11 Jan 2021 09:56:55 + with message-id and subject line Bug#977888: fixed in kdenlive 20.12.1-1 has caused the Debian Bug report #977888, regarding kdenlive: Missing icons etc. when installed on non-KDE environment 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.) -- 977888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kdenlive Version: 20.12.0-2 Severity: normal X-Debbugs-Cc: f...@debian.org Hello, After installing Kdenlive on a freshly installed Debian bullseye/sid running a non-KDE desktop environment, e.g. GNOME 3, Kdenlive appears to be missing icons etc., with the GUI looking somewhat broken and incomplete. There is no way to change the Colour Theme to Breeze Dark either, as it is not present in the menu. I personally managed to fix the issue by running sudo apt install kde-style-breeze though some others have recommended sudo apt install breeze see https://askubuntu.com/questions/1262776/kdenlive-dark-theme-on-ubuntu-20-04-how-to-enable I see that the kdenlive package already Recommends: breeze-icon-theme, though that appears to be insufficient. Perhaps it is more failsafe to replace "Recommends: breeze-icon-theme" with "Recommends: breeze" instead? This will ensure the end users get the complete, beautiful, and upstream default GUI regardless of desktop environment. Thanks in advance! Cheers, Anthony -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdenlive depends on: ii ffmpeg 7:4.3.1-5 ii gstreamer1.0-plugins-bad 1.18.2-1 ii kded5 5.74.0-2 ii kdenlive-data 20.12.0-2 ii kinit 5.74.0-2 ii kio5.74.0-2 ii libc6 2.31-5 ii libkf5archive5 5.74.0-2 ii libkf5bookmarks5 5.74.0-2 ii libkf5completion5 5.74.0-2 ii libkf5configcore5 5.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5configwidgets5 5.74.0-2 ii libkf5coreaddons5 5.74.0-2 ii libkf5crash5 5.74.0-2 ii libkf5dbusaddons5 5.74.0-2 ii libkf5declarative5 5.74.0-2 ii libkf5filemetadata35.74.0-2 ii libkf5guiaddons5 5.74.0-3 ii libkf5i18n55.74.0-3 ii libkf5iconthemes5 5.74.0-2 ii libkf5itemviews5 5.74.0-2 ii libkf5jobwidgets5 5.74.0-2 ii libkf5kiocore5 5.74.0-2 ii libkf5kiofilewidgets5 5.74.0-2 ii libkf5kiogui5 5.74.0-2 ii libkf5kiowidgets5 5.74.0-2 ii libkf5newstuff55.74.0-2 ii libkf5notifications5 5.74.0-2 ii libkf5notifyconfig55.74.0-2 ii libkf5purpose-bin 5.74.0-2 ii libkf5purpose5 5.74.0-2 ii libkf5service-bin 5.74.0-2 ii libkf5service5 5.74.0-2 ii libkf5solid5 5.74.0-2 ii libkf5widgetsaddons5 5.74.0-3 ii libkf5xmlgui5 5.74.0-2+b2 ii libmlt++3 6.24.0-1 ii libmlt66.24.0-1 ii libqt5concurrent5 5.15.2+dfsg-2 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus55.15.2+dfsg-2 ii libqt5gui5 5.15.2+dfsg-2 ii libqt5multimedia5 5.15.2-2 ii libqt5network5 5.15.2+dfsg-2 ii libqt5qml5 5.15.2+dfsg-2 ii libqt5quick5 5.15.2+dfsg-2 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5quickwidgets55.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-2 ii libqt5xml5 5.15.2+dfsg-2 ii librttr-core0.9.6 0.9.6+dfsg1-4 ii libstdc++6 10.2.1-1 ii melt 6.24.0-1 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtqml-models2 5.15.2+dfsg-2 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-cont
Bug#975351: marked as done (pascal 3.2.0 - installation errors for Lazarus 2.1.0)
Your message dated Mon, 11 Jan 2021 09:51:13 +
with message-id
and subject line Bug#975351: fixed in fpc 3.2.0+dfsg-9
has caused the Debian Bug report #975351,
regarding pascal 3.2.0 - installation errors for Lazarus 2.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fpc-3.2.0
Version: 3.2.0+dfsg-8
Severity: normal
X-Debbugs-Cc: serfyo...@yandex.ru
Dear Maintainer,
After installing "pascal 3.2.0" for
" /usr/bin/x86_64-linux-gnu-fpcmkcfg-3.2.0"
the fpcmkcfg symlink is not created,
and this name is used in
" /usr/lib/x86_64-linux-gnu/fpc/3.2.0/samplecfg "
when creating"FPCMKCFGBIN".
Adding into the "fp-compiler-3.2.0_3.2.0+dfsg-9_amd64.deb" package lines
to "postinst" file
--slave /usr/bin/fpcmkcfg fpcmkcfg /usr/bin/x86_64-linux-gnu-fpcmkcfg-3.2.0
into
# add alternatives
update-alternatives \
--install /usr/bin/fpc fpc /usr/bin/x86_64-linux-gnu-fpc-3.2.0 302 \
--slave /usr/bin/ppcx64 ppcx64 ${LIB_DIR}/3.2.0/ppcx64 \
--slave /usr/bin/fpc-depends fpc-depends /usr/bin/fpc-depends-3.2.0 \
--slave /usr/bin/fpcres fpcres /usr/bin/x86_64-linux-gnu-fpcres-3.2.0 \
--slave ${MAN_DIR}/ppcx64.1.gz ppcx64.1.gz ${MAN_DIR}/ppcx64-3.2.0.1.gz \
--slave ${MAN_DIR}/fpc.1.gz fpc.1.gz ${MAN_DIR}/fpc-3.2.0.1.gz \
--slave ${MAN_DIR}/fpc-depends.1.gz fpc-depends.1.gz
${MAN_DIR}/fpc-depends-3.2.0.1.gz \
--slave ${MAN_DIR}/fpcres.1.gz fpcres.1.gz ${MAN_DIR}/fpcres-3.2.0.1.gz
and
${LIB_DIR}/3.2.0/samplecfg ${LIB_DIR}/3.2.0
at the end of the "postinst" file solves this problem.
Also need to replace some links in "samplecfg" :
#FPCBIN=`dirname "$1"`/../../bin/fpc
FPCBIN='/usr/bin/fpc'
#FPBIN=`dirname "$1"`/../../bin/fp
FPBIN='/usr/bin/fp'
#FPPKGBIN=`dirname "$1"`/../../bin/fppkg
FPPKGBIN='/usr/bin/fppkg'
#FPCMKCFGBIN=`dirname "$1"`/../../bin/fpcmkcfg
FPCMKCFGBIN='/usr/bin/fpcmkcfg'
#SHAREPATH=`dirname "$1"`/../../share/fpc/\$fpcversion
SHAREPATH="/usr/share/fpcsrc/\$fpcversion"
# set right path to FPC with $fpcversion
#FPCPATH=`dirname "$1"`/\$fpcversion
FPCPATH=/usr/lib/x86_64-linux-gnu/fpc/\$fpcversion
# set right prefix to FPC
#FPCGLOBALPATH=`dirname "$1"`
FPCGLOBALPATH=/usr/lib/x86_64-linux-gnu/fpc
#FPCGLOBALPREFIX="$FPCGLOBALPATH"/../../
FPCGLOBALPREFIX=/usr/
otherwise, after installing "Lazarus 2.1.0", an error occurs when starting it
with an unintelligible description for "fppkg" (for "Lazarus" 2.0.10+dfsg-4
"fppkg" is not used).
And files should be created in $HOME with this content:
.config
fppkg.cfg
[Defaults]
ConfigVersion=5
InstallRepository=user
LocalRepository={UserDir}.fppkg/
BuildDir={LocalRepository}build/
ArchivesDir={LocalRepository}archives/
Downloader=FPC
CompilerConfig=default
FPMakeCompilerConfig=default
CompilerConfigDir=/etc/fppkg
RemoteMirrors=https://www.freepascal.org/repository/mirrors.xml
RemoteRepository=auto
[Repository]
Name=fpc
Description=Packages which are installed along with the Free Pascal Compiler
Path=/usr/lib/x86_64-linux-gnu/fpc/{CompilerVersion}/
Prefix=/usr/
#[IncludeFiles]
#FileMask=/etc/fppkgconf.d/*.conf
[Repository]
Name=user
Description=User-installed packages
Path={LocalRepository}lib/fpc/{CompilerVersion}
Prefix={LocalRepository}
.fppkg
config
default
[Defaults]
ConfigVersion=5
GlobalPrefix=/usr/
LocalPrefix={LocalRepository}
GlobalInstallDir={GlobalPrefix}lib/x86_64-linux-gnu/fpc/{CompilerVersion}/
LocalInstallDir={LocalPrefix}lib/fpc/{CompilerVersion}/
Compiler=/usr/bin/fpc
OS=linux
CPU=x86_64
Version=3.2.0
or not created at all.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fpc-3.2.0 depends on:
ii fp-compiler-3.2.0 3.2.0+dfsg-8
ii fp-ide-3.2.0 3.2.0+dfsg-8
ii fp-units-base-3.2.03.2.0+dfsg-8
ii fp-units-db-3.2.0 3.2.0+dfsg-8
ii fp-units-fcl-3.2.0 3
Bug#804218: marked as done (libqglviewer FTBFS on armel and armhf)
Your message dated Mon, 11 Jan 2021 10:33:06 +0100
with message-id
and subject line Re: Bug#804218: libqglviewer FTBFS on armel and armhf
has caused the Debian Bug report #804218,
regarding libqglviewer FTBFS on armel and armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
804218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libqglviewer
version: 2.6.3+dfsg1-1
x-debbugs-cc: woo...@debian.org
libqglviewer FTBFS on armel and armhf, the qt4 and qt5 builds both fail
for different reasons. wookey asked me to take a look at it.
The qt4 build is suffering from qreal vs double issues. These were
fairly easy to patch.
The qt5 build is suffering from the fact that Debian builds qt5 on
armel/armhf against opengl es. libqglviewer includes regular opengl
headers leading to conflicting declarations. I tried patching it to
include opengl es headers instead but I then ran into a load of stuff
that only exists in desktop opengl. This needs the attention of an
opengl expert if it's fixable at all.
It would probably be possible to modify the source package to only build
the qt4 version on armel/armhf but given that qt4 is on it's way out
that doesn't seem like the best idea to me.
debdiff of what i've done is attatched.
diff -Nru libqglviewer-2.6.3+dfsg1/debian/changelog
libqglviewer-2.6.3+dfsg1/debian/changelog
--- libqglviewer-2.6.3+dfsg1/debian/changelog 2015-06-26 17:01:38.0
+
+++ libqglviewer-2.6.3+dfsg1/debian/changelog 2015-11-05 16:09:03.0
+
@@ -1,3 +1,10 @@
+libqglviewer (2.6.3+dfsg1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Attempt to fix build on arm*
+
+ -- root Thu, 05 Nov 2015 16:08:55 +
+
libqglviewer (2.6.3+dfsg1-1) unstable; urgency=medium
* [7ad92fc] Add -qt4 packages.
diff -Nru libqglviewer-2.6.3+dfsg1/debian/patches/arm-fixes
libqglviewer-2.6.3+dfsg1/debian/patches/arm-fixes
--- libqglviewer-2.6.3+dfsg1/debian/patches/arm-fixes 1970-01-01
00:00:00.0 +
+++ libqglviewer-2.6.3+dfsg1/debian/patches/arm-fixes 2015-11-06
09:43:11.0 +
@@ -0,0 +1,122 @@
+Description:
+ TODO: Put a short summary on the line above and replace this paragraph
+ with a longer explanation of this change. Complete the meta-information
+ with other relevant fields (see below for details). To make it easier, the
+ information below has been extracted from the changelog. Adjust it or drop
+ it.
+ .
+ libqglviewer (2.6.3+dfsg1-1.1) UNRELEASED; urgency=medium
+ .
+ * Non-maintainer upload.
+ * Attempt to fix build on arm*
+Author: root
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: ,
+Bug:
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded:
+Reviewed-By:
+Last-Update:
+
+Index: libqglviewer-2.6.3+dfsg1/QGLViewer/vec.h
+===
+--- libqglviewer-2.6.3+dfsg1.orig/QGLViewer/vec.h
libqglviewer-2.6.3+dfsg1/QGLViewer/vec.h
+@@ -157,7 +157,7 @@ public:
+
+ #ifndef DOXYGEN
+ /*! This method is deprecated since version 2.0. Use operator const
double* instead. */
+- const double* address() const { qWarning("Vec::address() is deprecated,
use operator const double* instead."); return operator const double*(); }
++ const qreal* address() const { qWarning("Vec::address() is deprecated,
use operator const double* instead."); return operator const qreal*(); }
+ #endif
+
+ /*! Conversion operator returning the memory address of the vector.
+@@ -168,7 +168,7 @@ public:
+ glNormal3dv(normal);
+ glVertex3dv(pos);
+ \endcode */
+- operator const double*() const {
++ operator const qreal*() const {
+ #ifdef QGLVIEWER_UNION_NOT_SUPPORTED
+ return &x;
+ #else
+@@ -179,7 +179,7 @@ public:
+ /*! Non const conversion operator returning the memory address of the
vector.
+
+ Useful to pass a Vec to a method that requires and fills a \c double*, as
provided by certain libraries. */
+- operator double*() {
++ operator qreal*() {
+ #ifdef QGLVIEWER_UNION_NOT_SUPPORTED
+ return &x;
+ #else
+Index: libqglviewer-2.6.3+dfsg1/QGLViewer/quaternion.cpp
+===
+--- libqglviewer-2.6.3+dfsg1.orig/QGLViewer/quaternion.cpp
l
Bug#977622: marked as done (golang-github-tidwall-gjson: CVE-2020-35380)
Your message dated Mon, 11 Jan 2021 09:28:18 + with message-id and subject line Bug#977622: fixed in golang-github-tidwall-gjson 1.6.7-1 has caused the Debian Bug report #977622, regarding golang-github-tidwall-gjson: CVE-2020-35380 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.) -- 977622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-tidwall-gjson Version: 1.1.5-2 Severity: important Tags: security upstream Forwarded: https://github.com/tidwall/gjson/issues/192 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-tidwall-gjson. CVE-2020-35380[0]: | GJSON before 1.6.4 allows attackers to cause a denial of service via | crafted JSON. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-35380 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35380 [1] https://github.com/tidwall/gjson/issues/192 Regards, Salvatore --- End Message --- --- Begin Message --- Source: golang-github-tidwall-gjson Source-Version: 1.6.7-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of golang-github-tidwall-gjson, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated golang-github-tidwall-gjson 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, 10 Jan 2021 16:01:30 + Source: golang-github-tidwall-gjson Architecture: source Version: 1.6.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Thorsten Alteholz Closes: 977622 Changes: golang-github-tidwall-gjson (1.6.7-1) unstable; urgency=medium . * New upstream release 1.6.7 * Fix for: - CVE-2020-36067 - CVE-2020-36066 at least v1.0.3 of golang-github-tidwall-match is required - CVE-2020-35380 (Closes: #977622) * Add myself as uploader * debian/control: add missing Depends: golang-github-tidwall-pretty-dev * debian/control: use dh13 * debian/control: bump standard to 4.5.1 (no changes) * reverse dependencies successfully built with ratt: - golang-github-tidwall-buntdb - golang-github-tidwall-grect - wuzz - garagemq - g10k Checksums-Sha1: f2b24fe9b76fd5cf8382e1a239ffb4b5eb1f68cc 2532 golang-github-tidwall-gjson_1.6.7-1.dsc 6cdfd07b1b3956137e69b795d470f9ab2b12f5e9 52035 golang-github-tidwall-gjson_1.6.7.orig.tar.gz 76b2c38f57c38def7c09435e9d0b2e7bcc324b9b 2520 golang-github-tidwall-gjson_1.6.7-1.debian.tar.xz e76cb62f9eb00b4d1ee723a4f5d53143b6531ddb 6786 golang-github-tidwall-gjson_1.6.7-1_amd64.buildinfo Checksums-Sha256: ce5649ad1aded9f7f373e8ae0f399f3629afc4e994540493fb55e96e796a8b51 2532 golang-github-tidwall-gjson_1.6.7-1.dsc 26dbae82e871df9a578a73412227d7602d9c875dcfb3ece0156eebabda468877 52035 golang-github-tidwall-gjson_1.6.7.orig.tar.gz 55b0c2b620a15a949efd7712cee921feacc8a9708bd1f799a7c0bddf8678c1d7 2520 golang-github-tidwall-gjson_1.6.7-1.debian.tar.xz 0ac4a8b387cd9398a71c68b8d3de151567d86c3d1494f9828810309e54b67ed8 6786 golang-github-tidwall-gjson_1.6.7-1_amd64.buildinfo Files: 3ee348a45f8b7a57cdf6f02661aa9672 2532 devel optional golang-github-tidwall-gjson_1.6.7-1.dsc c4927c6b21ed1db8a288d1125dce645e 52035 devel optional golang-github-tidwall-gjson_1.6.7.orig.tar.gz 3f3aba646fd8eb0700cdb4cf84005413 2520 devel optional golang-github-tidwall-gjson_1.6.7-1.debian.tar.xz d151deb4b8449566b3b80c1ddd1134b3 6786 devel optional golang-github-tidwall-gjson_1.6.7-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl/7LRdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYRwAuD/9tZ0JEUEeJlnSzqDVvDPoz94ePzIz5 c
Bug#974891: marked as done (win32-loader: [INTL:ru] Russian debconf templates translation update)
Your message dated Mon, 11 Jan 2021 08:34:31 + with message-id and subject line Bug#974891: fixed in win32-loader 0.10.4 has caused the Debian Bug report #974891, regarding win32-loader: [INTL:ru] Russian debconf templates translation update 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.) -- 974891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: win32-loader Version: 0.10.1 Severity: wishlist Tags: l10n patch Russian debconf templates translation update is attached. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ru.po.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: win32-loader Source-Version: 0.10.4 Done: Thomas Gaugler We believe that the bug you reported is fixed in the latest version of win32-loader, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Gaugler (supplier of updated win32-loader 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, 11 Jan 2021 08:24:07 +0100 Source: win32-loader Architecture: source Version: 0.10.4 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Thomas Gaugler Closes: 974891 Changes: win32-loader (0.10.4) unstable; urgency=medium . [ Thomas Gaugler ] * Run win64 tests only on 64-bit wine * Makefile: Add build directory as prerequisite for icon generation * s_install.nsi: Fix indentation * Use signed grub efi file of testing instead of buster The signed grub efi file of buster lacks the leading / in the prefix. * l10n: Generate translations only via shell script, update po and pot files * Write entries to preseed.cfg one by one By default NSIS limits strings to 1024 characters. Writing each entry destined for preseed.cfg on its own prevents a possible data loss. * Use "create error" message in case adding preseed.cfg to installer's initrd.gz fails * Restore variables before returning from Get_SHA256_ref * Download signed grub efi file of testing (bullseye) if the one of stable (buster) is faulty determined by its sha256 fingerprint . [ Updated translations ] * Russian (ru.po) by Yuri Kozlov. Closes: #974891 . [ Didier Raboud ] * Bump S-V to 4.5.1 without changes needed Checksums-Sha1: e48c42d80c1c5c7d4b7bd423db49bcd16969d2c2 2008 win32-loader_0.10.4.dsc 66829a42e7f2526275e49bb0ff89effd65875898 289252 win32-loader_0.10.4.tar.xz Checksums-Sha256: 19402d67b9a5c4813f0ba1bf2c72f45599a1cc7393b20a5cee38a21a7d1d2b60 2008 win32-loader_0.10.4.dsc 6080985c954e425ba65a8923e9d5af926cf799e05948763070fbf4d1ff250e5b 289252 win32-loader_0.10.4.tar.xz Files: 8d63a9196ce2b314a63020ff0606bf8c 2008 utils optional win32-loader_0.10.4.dsc cd9d26cde57d8f5790d45b7c6ae50feb 289252 utils optional win32-loader_0.10.4.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJ3k7rA0YCplkx4gZqcb6xg1jAWkFAl/7/80ACgkQqcb6xg1j AWnzxg//TE32V9o098ur9xZ0ntsBC9TWAxoFZ3JAVD6kkUA/XbPnTNhTOz1n2kTl gIBaxHtjrFrtBdOWgvURU+Gaira99jC1ENlejSuJZrl5lKxpq8qrnVgAIw7wMbwq DD1H3e6hHqLCsyIwXPWwctZSHbydTiVfCKjNubSvSoJwEK2jLEpeEEqHsQpwltJi Phd+mAlVo+cArmXSe632Js7wlU/Y9WeN2ez6PR2XOWRwKk24t5ojgxZGTysXkkLK WsZ6bAH/D5CqXW9ZWUySDFGdlkOF2KsfPweI6YeXX6obnIgj3UG0J8wt1tm00Ucs UrYQWyAIRVmtwfNT0EA7EOTvBCSlFTzqzYWSeSHAOUBQ+ScokU57OhGMUZ+/C591 3AWBPaYWbBINxnw5zZUMQk3oB0uPddWrrrZ9vlGicyFkF2zMn65rSz7YbxN0n+Kk DDK5hYcj3YVtRZlzgSpGUeWx4cGJq/0ZYjVR8lLNTadH9Rd0JkbvI50Z+b3pSl+9 /UJgqIyZEi6oDLqLAguy+3OsSxDUKrFBghEGhCJg6PdvJUnPewUISzKpNxdD+B+W U8S/9tqYG/cRgfLdVb1vHSXldDiCUxj/8IxwibdOoJfcsgOSTF22ZmTEGeP1RPBe mGxoKEQ/RyF9v75ll01/yYZpCZN8SKwK8j1Cg
Bug#923850: marked as done (debootstick: support for disk layout (partitions))
Your message dated Mon, 11 Jan 2021 09:01:42 +0100 with message-id <7159d5fd-b742-55ce-09be-39c397bbd...@gmail.com> and subject line Re: Bug#923850: debootstick: support for disk layout (partitions) has caused the Debian Bug report #923850, regarding debootstick: support for disk layout (partitions) 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.) -- 923850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debootstick Version: 2.1 Severity: wishlist Dear Maintainer, I would like to create bootable images with more than just rootfs, i.e. to include several partitions. How would you find such a feature? Best regards, Dejan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstick depends on: ii dosfstools 4.1-2 ii e2fsprogs 1.44.5-1 ii gdisk 1.0.3-1.1 ii grub-efi-amd64-bin 2.02+dfsg1-11 ii grub-efi-ia32-bin 2.02+dfsg1-11 ii kpartx 0.7.9-2 ii lvm22.03.02-2 ii qemu-user-static1:3.1+dfsg-4 ii uuid-runtime2.33.1-0.1 debootstick recommends no packages. Versions of packages debootstick suggests: ii debootstrap 1.0.114 pn kvm -- no debconf information -- debsums errors found: debsums: changed file /usr/sbin/debootstick (from debootstick package) --- End Message --- --- Begin Message --- Package: debootstick Version: 2.5 Closing this bug since this feature was added to version 2.5 now in unstable. Le 06/03/2019 à 08:34, Dejan Muhamedagic a écrit : Package: debootstick Version: 2.1 Severity: wishlist Dear Maintainer, I would like to create bootable images with more than just rootfs, i.e. to include several partitions. How would you find such a feature? Best regards, Dejan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstick depends on: ii dosfstools 4.1-2 ii e2fsprogs 1.44.5-1 ii gdisk 1.0.3-1.1 ii grub-efi-amd64-bin 2.02+dfsg1-11 ii grub-efi-ia32-bin 2.02+dfsg1-11 ii kpartx 0.7.9-2 ii lvm22.03.02-2 ii qemu-user-static1:3.1+dfsg-4 ii uuid-runtime2.33.1-0.1 debootstick recommends no packages. Versions of packages debootstick suggests: ii debootstrap 1.0.114 pn kvm -- no debconf information -- debsums errors found: debsums: changed file /usr/sbin/debootstick (from debootstick package) -- Etienne Dublé CNRS/LIG Research Engineer--- End Message ---
