Bug#962013: marked as done (libjson-c-doc: not follow changes about installation directory)
Your message dated Mon, 27 Jul 2020 10:00:11 + with message-id and subject line Bug#962013: fixed in json-c 0.14+dfsg-1 has caused the Debian Bug report #962013, regarding libjson-c-doc: not follow changes about installation directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjson-c-doc Version: 0.13.1+dfsg-7 Severity: normal Dear Maintainer, With latest debhelper, documentation files are installed in /usr/share/doc/libjson-c-dev instead of /usr/share/doc/libjson-c-doc. So there are some odd destination: /usr/share/doc/libjson-c-doc/html/jquery.js There is no libjson-c-doc's file in /usr/share/doc-base. These have been fixed correctly in the buster version: libjson-c-doc (0.12.1+ds-2). Changes: debian/libjson-c-doc.links, debian/libjson-c-doc.doc-base Thank you, Hiroyuki YAMAMORI -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libjson-c-doc depends on: ii libjs-jquery 3.5.1+dfsg-4 libjson-c-doc recommends no packages. libjson-c-doc suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: json-c Source-Version: 0.14+dfsg-1 Done: Nicolas Mora We believe that the bug you reported is fixed in the latest version of json-c, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Mora (supplier of updated json-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Jul 2020 18:16:11 -0400 Source: json-c Binary: libjson-c-dev libjson-c-doc libjson-c5 libjson-c5-dbgsym libjson-c5-udeb Architecture: source amd64 all Version: 0.14+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nicolas Mora Changed-By: Nicolas Mora Description: libjson-c-dev - JSON manipulation library - development files libjson-c-doc - JSON manipulation library - documentation files libjson-c5 - JSON manipulation library - shared library libjson-c5-udeb - JSON manipulation library - shared library (udeb) (udeb) Closes: 844452 960326 962013 Changes: json-c (0.14+dfsg-1) unstable; urgency=medium . [Gianfranco Costamagna] * Fix documentation generation (Closes: #962013) * debian/patches/608.patch: - Add patch to fix CVE-2020-12762 (Closes: #960326) . [Nicolas Mora] * New upstream release 0.14. * Upload to unstable * New maintainer (Closes: #844452) * d/control: Rules-Requires-Root: no * Add d/gbp.conf * debian/patches/0002-doxygen.patch - Remove remote images in doxygen generated files * Update symbols file * Add autpkgtests * Clean lintian-overrides * debian/patches/0003-config-h.patch - Remove macro PACKAGE_NAME Checksums-Sha1: d3bc7850e5fb092cee966a47da575199b57f93b3 2152 json-c_0.14+dfsg-1.dsc 9111e4236c9b0556af723475bfdf36f9a54778bd 158427 json-c_0.14+dfsg.orig.tar.gz 7e7f723d4858774bcae8931bf0cbe48fd1d85451 10736 json-c_0.14+dfsg-1.debian.tar.xz 4dcb1cac7ea668f2239d527f6dafcc625553ab4c 8053 json-c_0.14+dfsg-1_amd64.buildinfo df371e45717fd0caf4dd54386a4204591e90f9a4 37960 libjson-c-dev_0.14+dfsg-1_amd64.deb 2879cec92fa7bc28b58b3cfcef892b1a61f647fd 102772 libjson-c-doc_0.14+dfsg-1_all.deb 7601926bd5fc61174c5dd88bbf73180a2a6f693a 68088 libjson-c5-dbgsym_0.14+dfsg-1_amd64.deb b39c2cf76cd902d2675792ef163a4a6b9bbbd84b 25260 libjson-c5-udeb_0.14+dfsg-1_amd64.udeb 6de4a930a97264929e7bc9c31c122bc9c98b4d7f 40776 libjson-c5_0.14+dfsg-1_amd64.deb Checksums-Sha256: 9151aa56dae6c160bc2ab07b209eec516cf440c3005365d9220efdf91edb3219 2152 json-c_0.14+dfsg-1.dsc 95899fdefc4b69676d751f9342d8a7b5d46509ee5a4129fd420c1b4704888d6e 158427 json-c_0.14+dfsg.orig.tar.gz 041cc26bf7576fb3a2
Bug#966366: json-c: Please package new release (0.15)
Source: json-c Version: 0.14+dfsg-1 Tags: sid Severity: normal X-Debbugs-CC: babelou...@debian.org Dear new Debian json-c maintainer, It seems that the json-c upstream has just released v0.15: https://github.com/json-c/json-c/releases Please consider packaging this new release. I know that it sounds subtle to request upgrading to a new version just when the v0.14 enters unstable, but I am really looking forward to keep up with the pace of upstream. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#516394: removal of djbdns ?
On Mon, Jun 08, 2020 at 07:44:22PM +0200, Matija Nalis wrote: > Hi, > > I see djbdns is removed from testing, due to unarchiving of > critical bug #516394 > > However, as source package djbdns 1:1.05-11 builds several binary > packages (axfrdns, djbdns-conf, djbdns-utils, rbldns, tinydns, > walldns) and the bug is only in (if not patched) dnscache, > would other packages reenter testing and later new stable Debian? Hi, I just adopted the djbdns package; the 1:1.05-12 upload with a couple of packaging fixes should hit unstable in the mirror sync (it has already been built on most architectures; I'll drop the lsof build dependency in the next upload so that it builds on even more). Apropos, let me express my thanks to Dmitry Bogatov for the large overhaul in 1:1.05-10: bringing the Debian packaging up to date and incorporating some bugfixes from other packaging systems. Now... related to that. I am not sure whether Moritz Muehlenhoff, when reopening this bug, was aware of the fact that Dmitry Bogatov included two patches from Jeff King that address the cache poisoning attack - and actually, the patches were mentioned in this bug log by Matija Nalis back in 2010. Moritz, is it possible that you had missed the inclusion of these two patches, or do you believe that they, by themselves, are still not enough to address this problem? If so, that would indeed be kind of unfortunate, since it is my impression that these particular patches are considered the best way to handle this among users of Prof. Bernstein's software. Of course, I do not intend to argue with the Security Team - I only have the utmost respect and gratitude for everything you people do for Debian! So if it is still your collective stated position that Jeff King's patches, applied to the djbdns package in Debian as debian/patches/0007-dnscache-merge-similar-outgoing-udp-packets.patch and debian/patches/0008-Cache-SOA-records.patch, are not enough, then I guess I may have to look for some other way to manage the situation, possibly breaking dnscache off into its own source package to allow the rest to eventually migrate to testing. I am late in coming to this discussion, so let me express my thanks to everyone who has spoken their mind in good faith in the bug log. Here's hoping we find some way to move forward :) G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#957579: marked as done (naspro-bridges: ftbfs with GCC-10)
Your message dated Mon, 27 Jul 2020 21:33:36 + with message-id and subject line Bug#957579: fixed in naspro-bridges 0.5.1-3 has caused the Debian Bug report #957579, regarding naspro-bridges: 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.) -- 957579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:naspro-bridges Version: 0.5.1-2 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/naspro-bridges_0.5.1-2_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 [...] checking pkg-config is at least version 0.9.0... yes checking for NABRIT... yes checking ladspa.h usability... yes checking ladspa.h presence... yes checking for ladspa.h... yes checking whether LRDF-equivalent LV2 bundles should be installed... yes checking for DSSI... yes checking for ALSA... yes checking whether to enable bridging of DSSI programs as LV2 presets... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating ladspa/manifest.ttl config.status: creating ladspa/Makefile config.status: creating ladspa/data/Makefile config.status: creating dssi/manifest.ttl config.status: creating dssi/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode configure: LADSPA bridge: yes configure: LRDF-equivalent bundles: yes configure: DSSI bridge:yes configure: DSSI programs as LV2 presets: yes dh_auto_build -O--parallel dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in ladspa make[3]: Entering directory '/<>/ladspa' Making all in data make[4]: Entering directory '/<>/ladspa/data' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/ladspa/data' make[4]: Entering directory '/<>/ladspa' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c -o manifest.lo manifest.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c -o bridge.lo bridge.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c -o pluglib.lo pluglib.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c -o plugin.lo plugin.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c manifest.c -fPIC -DPIC -o .libs/manifest.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wall -Werror -Wno-strict-aliasing -pthread -I/usr/include/NASPRO/brit-3 -I/usr/include/NASPRO/core-5 -g -O2 -c pluglib.c -fPIC -DPIC -o .
Processing of naspro-bridges_0.5.1-3_source.changes
naspro-bridges_0.5.1-3_source.changes uploaded successfully to localhost along with the files: naspro-bridges_0.5.1-3.dsc naspro-bridges_0.5.1-3.debian.tar.xz naspro-bridges_0.5.1-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
naspro-bridges_0.5.1-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Jul 2020 21:54:12 +0100 Source: naspro-bridges Architecture: source Version: 0.5.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 957579 Changes: naspro-bridges (0.5.1-3) unstable; urgency=medium . * QA upload. * Fix ftbfs with GCC-10. (Closes: #957579) * Update Standards-Version to 4.5.0 * Use debhelper-compat. - Update compat level to 13. - Remove parallel and autoreconf from d/rules. - Remove dependency on dh-autoreconf. * Use https with copyright-format-uri. Checksums-Sha1: 7d801716633ff9d497d8b1e6229a9ab8e71572c3 1897 naspro-bridges_0.5.1-3.dsc b2e918b445ed4c587ad74b4f06befec30357dd50 2932 naspro-bridges_0.5.1-3.debian.tar.xz 7ee7aa6632b69d79a9606d79c6784f62362ee399 7253 naspro-bridges_0.5.1-3_amd64.buildinfo Checksums-Sha256: 214a0af2000dfa9c8043dd558a7abbe2696eb505c0e9e8bf26c2a7806663efee 1897 naspro-bridges_0.5.1-3.dsc cb0a0a5680970ec817feee6bf93a3b790d61c398832fa578b56edb9ba841ebad 2932 naspro-bridges_0.5.1-3.debian.tar.xz 5a07be24d1263134b676c91728258e105e9287530036177d8eb762037bf621f0 7253 naspro-bridges_0.5.1-3_amd64.buildinfo Files: d0a32514de4cca5b9e6b781ad509730b 1897 libs optional naspro-bridges_0.5.1-3.dsc 068dffc9c5cf64e86880c8f2f55279b8 2932 libs optional naspro-bridges_0.5.1-3.debian.tar.xz 737bb5c71df944fad088b1dfc15b610b 7253 libs optional naspro-bridges_0.5.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl8fQHkACgkQR5mjUUbR KzUW8hAAh/SojIsQdZFOnaLrQ5zxlwwF8x3uC1KQzNiV0i56+q8ny6nk9F6CM2Kw ucM3pgkDnaz5thl5qDe0KIxyjJKDJJmK1DOlRkLMSbtogDOyWQCX/klL7QwhzTLF aAdXjQlAN/CA9CG850hmWZg/gAOUgOxaBhvLFXeA2vKNkapWSiXrMt1Y7iKu+K8k B7ZMgPwUM31sQ2XlQGb8DALKpAEpflttRuBQp0QE4bSbWMQCzCMqWSDTf2BGPgul 11ad1fjkoOyw5h62KWlmql81qH8vpMTS7NMq2Avg9IycOTJsbd/PmjJbxAcSL5+A GlzMQSlD4LCpcvKintCq0O6thDBrN5oKaj/qZAYkqCinry5ssUBu94k0GV4PPH9b 5Ad0Cw+05kfi6aer/3HLu/cdlBOVynAUFBBS00gjou3qsoWYB9I5eK+mC7gebvWs nR7p4H6gB94ZXEr/PeHNFPy0iUG/azqyhtTHGiN5hUyVblGM8WY1KSXgFYRZ5c8A 70h+8AIaNLu32dQZlZ7LKf+yzqtJdOIXQqZgMQwoFv7AVxk7mvYrjYSbw81pSdxu HdDKfI2/hejt/nMFyV2hTS+Z04sO+K+v9co1MmuwBgfeW1ywL0TAKUQyHltqmgts Cp8NSN4ncUqKTZW7gpQku3JUaD9yGdVq1j02no28N2/HLZp+nm8= =RF6N -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#957927: marked as done (webdruid: ftbfs with GCC-10)
Your message dated Mon, 27 Jul 2020 22:20:03 +
with message-id
and subject line Bug#957927: fixed in webdruid 0.5.4-16
has caused the Debian Bug report #957927,
regarding webdruid: 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.)
--
957927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:webdruid
Version: 0.5.4-15
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/webdruid_0.5.4-15_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
[...]
| |
| struct gzFile_s **
In file included from /usr/include/zlib.h:34,
from logs_mgmt.c:28:
/usr/include/zlib.h:1566:33: note: expected ‘gzFile’ {aka ‘struct gzFile_s *’}
but argument is of type ‘struct gzFile_s **’
1566 | ZEXTERN int ZEXPORTgzrewind OF((gzFile file));
| ^~
logs_mgmt.c: In function ‘our_gzgets’:
logs_mgmt.c:437:38: warning: passing argument 1 of ‘gzread’ from incompatible
pointer type [-Wincompatible-pointer-types]
437 | plog->gz_f_end = gzread(plog->gz_file, plog->gz_f_buf,
GZ_BUFSIZE);
| ^
| |
| struct gzFile_s **
In file included from /usr/include/zlib.h:34,
from logs_mgmt.c:28:
/usr/include/zlib.h:1390:28: note: expected ‘gzFile’ {aka ‘struct gzFile_s *’}
but argument is of type ‘struct gzFile_s **’
1390 | ZEXTERN int ZEXPORT gzread OF((gzFile file, voidp buf, unsigned len));
|^~
logs_mgmt.c: In function ‘free_log_struct’:
logs_mgmt.c:566:19: warning: passing argument 1 of ‘gzclose’ from incompatible
pointer type [-Wincompatible-pointer-types]
566 | gzclose(plog->gz_file);
| ^
| |
| struct gzFile_s **
In file included from /usr/include/zlib.h:34,
from logs_mgmt.c:28:
/usr/include/zlib.h:1630:32: note: expected ‘gzFile’ {aka ‘struct gzFile_s *’}
but argument is of type ‘struct gzFile_s **’
1630 | ZEXTERN int ZEXPORTgzclose OF((gzFile file));
|^~
msgfmt po/ca.po -o po/ca.mo
msgfmt po/cs.po -o po/cs.mo
msgfmt po/da.po -o po/da.mo
msgfmt po/de.po -o po/de.mo
msgfmt po/el.po -o po/el.mo
msgfmt po/es.po -o po/es.mo
msgfmt po/et.po -o po/et.mo
msgfmt po/fi.po -o po/fi.mo
msgfmt po/fr.po -o po/fr.mo
msgfmt po/gl.po -o po/gl.mo
msgfmt po/hr.po -o po/hr.mo
msgfmt po/hu.po -o po/hu.mo
msgfmt po/id.po -o po/id.mo
msgfmt po/is.po -o po/is.mo
msgfmt po/it.po -o po/it.mo
msgfmt po/ja.po -o po/ja.mo
msgfmt po/ko.po -o po/ko.mo
msgfmt po/lv.po -o po/lv.mo
msgfmt po/ml.po -o po/ml.mo
msgfmt po/nl.po -o po/nl.mo
msgfmt po/no.po -o po/no.mo
msgfmt po/pl.po -o po/pl.mo
msgfmt po/pt.po -o po/pt.mo
msgfmt po/ro.po -o po/ro.mo
msgfmt po/ru.po -o po/ru.mo
msgfmt po/sl.po -o po/sl.mo
msgfmt po/sr.po -o po/sr.mo
msgfmt po/sv.po -o po/sv.mo
msgfmt po/tr.po -o po/tr.mo
msgfmt po/uk.po -o po/uk.mo
msgfmt po/zh.po -o po/zh.mo
gcc -Wl,-z,relro -o webdruid webdruid.o hashtab.o linklist.o preserve.o
parser.o output.o xml_output.o dot_output.o utils.o dns_resolv.o graphs.o
sengine.o logs_mgmt.o -lgd -lfreetype -lpng -lpthread -lz -lm -ldb
/usr/bin/ld: dns_resolv.o:(.bss+0x21c0): multiple definition
Processing of webdruid_0.5.4-16_source.changes
webdruid_0.5.4-16_source.changes uploaded successfully to localhost along with the files: webdruid_0.5.4-16.dsc webdruid_0.5.4-16.debian.tar.xz webdruid_0.5.4-16_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
webdruid_0.5.4-16_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Jul 2020 23:04:13 +0100 Source: webdruid Architecture: source Version: 0.5.4-16 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 957927 Changes: webdruid (0.5.4-16) unstable; urgency=medium . * QA upload. * Fix ftbfs with GCC-10. (Closes: #957927) * Update Standards-Version to 4.5.0 Checksums-Sha1: 523bcc25f4840504011e12d8194bcec001a01b23 1866 webdruid_0.5.4-16.dsc 1876fe3ba3f7c3722cb6a7e82b417ccd6c8d90a9 7288 webdruid_0.5.4-16.debian.tar.xz 8b643e7f7f3d00d377cd55f948a74977bdcc0b43 7314 webdruid_0.5.4-16_amd64.buildinfo Checksums-Sha256: 148a5c89dc77d5720dd735c5388ca72603b41626c3fd8679124197105705b175 1866 webdruid_0.5.4-16.dsc 685bc82bc75b45c09217912820afc5902e210c8188cf724c2c0e74fbc8b6e716 7288 webdruid_0.5.4-16.debian.tar.xz b080aff3ce5056ebc5267238ab0ce9d9d6354d4200f423e1b9e4092ccbc31d55 7314 webdruid_0.5.4-16_amd64.buildinfo Files: 0af400cad04a18b488335a294539ec7b 1866 web optional webdruid_0.5.4-16.dsc 9af2d9049e472b2e95e54f47079c7c5f 7288 web optional webdruid_0.5.4-16.debian.tar.xz aeabb1242b757a0a0e578fe993d3e899 7314 web optional webdruid_0.5.4-16_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl8fUFkACgkQR5mjUUbR KzWh5Q//TJ51cYwVt4Rrsm0HqA/OHGAUKOppuaB/TmBYyS0pW+GbetH6rXxgmkWj TkSeD/KCHOx6NjNEjqI9pD8a9Wt/Kgnx/BOfPYkxh936dfIbMS4p+I8Ff9cw0eqB ZZmHh0tCViz86c0nOa/sZY63d6Qu5Z/NR3kf7PD4amc1nXH5Gcxl6blAa8+aUoN4 gQh1/Dg6cKPRcRFb0ahJDk02+0o4zfCPbSlalP1ffM3mrY0UnFnUlvDNop0apeyb L2jmkZN4aUY3QVlxiZ33+zoASc6sa8HFBfmpM0PEpiZA9YdYddF/TtM4qVJ3Qi5u bjBVEQPSpOQ+M8GLan8H8OHCBA/OWfS7pxppLPFI/+H+GAtSlL5Efhmj6OdUYf4l /oiwMppPbTdSf/tcAE3en6OhUTl+7zRLjgZb7Qan3LxR/ySRmQzJ2ey7oOwIg+ah hWcTawkcd7BorGzLeLBIPDDFmZpWo7+Ql3BCAd0P52lN5vijH10VJ3qgEZGEnl8e xV9x5wgFjd8taW36ienCe3TAV7oQag36U/RiA/eVsPEFHZreA6CIazGb11JJb3fL 47iVku/3Ya2/Yn0f0DtRtil5MDBBntYrZo7pNiZVr/sTWsUwarZwN2KseD1bCjof o/rqwprMdDU4Pf/PCTb1aoWnvHQU2VfKe1sMUMCjQSvUQZNzU0M= =AsUa -END PGP SIGNATURE- Thank you for your contribution to Debian.
bcolz is marked for autoremoval from testing
bcolz 1.2.1+ds2-5 is marked for autoremoval from testing on 2020-08-18 It is affected by these RC bugs: 965354: bcolz: FTBFS with newer python3-numpydoc
mmorph is marked for autoremoval from testing
mmorph 2.3.4.2-17 is marked for autoremoval from testing on 2020-08-10 It is affected by these RC bugs: 957550: mmorph: ftbfs with GCC-10
