Bug#935552: marked as pending in nomad
Control: tag -1 pending Hello, Bug #935552 in nomad reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/nomad/commit/977675c3e209c75e1008bc4bc75382353c26e304 Fixed FTBFS (Closes: #935552). (this message was generated automatically) -- Greetings https://bugs.debian.org/935552
Processed: Bug#935552 marked as pending in nomad
Processing control commands: > tag -1 pending Bug #935552 [src:nomad] nomad: FTBFS Added tag(s) pending. -- 935552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942237: fiat: autopkgtest needs update for new version of pytest
Package: python3-fiat Version: 2019.1.0-2 Followup-For: Bug #942237 Upstream does have a patch, but it requires a new package pytest_cases. There was some debate upstream about whether it would be better to prepare the tests without needing to depend on the new package. I'm waiting for that debate to resolve. Drew
Bug#942674: Acknowledgement (git: FTBFS on big-endian targets - testsuite failure)
Control: tags -1 +patch
The attached patch fixes the problem for me. It comes from [1].
Thanks,
Adrian
> [1] https://www.spinics.net/lists/git/msg368292.html
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
From: SZEDER =?utf-8?B?R8OhYm9y?=
To: John Paul Adrian Glaubitz ,
Junio C Hamano
Cc: Todd Zullinger , g...@vger.kernel.org
Subject: [PATCH] test-progress: fix test failures on big-endian systems
On Sat, Oct 19, 2019 at 11:38:40PM +0200, John Paul Adrian Glaubitz wrote:
> The testsuite is failing again on s390x and all other big-endian targets in
> Debian. For a full build log on s390x see [1].
Gah, my progress display fixes strike again...
I think the patch below should fix it, but I could only test it on
little-endian systems. Could you please confirm that it indeed works
on big-endian as well?
--- >8 ---
Subject: [PATCH] test-progress: fix test failures on big-endian systems
In 't0500-progress-display.sh' all tests running 'test-tool progress
--total=' fail on big-endian systems, e.g. like this:
+ test-tool progress --total=3 Working hard
[...]
+ test_i18ncmp expect out
--- expect 2019-10-18 23:07:54.765523916 +
+++ out 2019-10-18 23:07:54.773523916 +
@@ -1,4 +1,2 @@
-Working hard: 33% (1/3)
-Working hard: 66% (2/3)
-Working hard: 100% (3/3)
-Working hard: 100% (3/3), done.
+Working hard: 0% (1/12884901888)
+Working hard: 0% (3/12884901888), done.
The reason for that bogus value is that '--total's parameter is parsed
via parse-options's OPT_INTEGER into a uint64_t variable [1], so the
two bits of 3 end up in the "wrong" bytes on big-endian systems
(12884901888 = 0x3).
Change the type of that variable from uint64_t to int, to match what
parse-options expects; in the tests of the progress output we won't
use values that don't fit into an int anyway.
[1] start_progress() expects the total number as an uint64_t, that's
why I chose the same type when declaring the variable holding the
value given on the command line.
Signed-off-by: SZEDER Gábor
---
t/helper/test-progress.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/helper/test-progress.c b/t/helper/test-progress.c
index 4e9f7fafdf..42b96cb103 100644
--- a/t/helper/test-progress.c
+++ b/t/helper/test-progress.c
@@ -29,7 +29,7 @@ void progress_test_force_update(void);
int cmd__progress(int argc, const char **argv)
{
- uint64_t total = 0;
+ int total = 0;
const char *title;
struct strbuf line = STRBUF_INIT;
struct progress *progress;
--
2.24.0.rc0.472.ga6f06c86b4
Processed: Re: Bug#942674: Acknowledgement (git: FTBFS on big-endian targets - testsuite failure)
Processing control commands: > tags -1 +patch Bug #942674 [src:git] git: FTBFS on big-endian targets - testsuite failure Added tag(s) patch. -- 942674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942119: marked as done (libproxy: depends on mono for build-arch; mono not universally present)
Your message dated Sat, 19 Oct 2019 23:49:28 + with message-id and subject line Bug#942119: fixed in libproxy 0.4.15-8 has caused the Debian Bug report #942119, regarding libproxy: depends on mono for build-arch; mono not universally present 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.) -- 942119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libproxy Version: 0.4.15-7 Severity: serious Justification: FTBFS on release architecture src:libproxy recently gained a B-D-Arch on dh-sequence-cli which depends on mono-utils, which isn’t available for the architectures mips64el (release), alpha, hppa, hurd-i386, ia64, kfreebsd-amd64, kfreebsd-i386, m68k, riscv64, sh4, sparc64, x32, and any new ones. Please use mono only in B-D-Indep. Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg ** Mit der tarent Academy bieten wir auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt. ** --- End Message --- --- Begin Message --- Source: libproxy Source-Version: 0.4.15-8 We believe that the bug you reported is fixed in the latest version of libproxy, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated libproxy 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: Sat, 19 Oct 2019 19:37:24 -0400 Source: libproxy Architecture: source Version: 0.4.15-8 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 942119 Changes: libproxy (0.4.15-8) unstable; urgency=medium . * Drop Build-Depends on dh-sequence-cli. Thanks to Simon McVittie (Closes: #942119) Checksums-Sha1: 92db0d3bc1f3fddee454622a199b86367b2965be 3454 libproxy_0.4.15-8.dsc 4b64bfa8a0ee043bc3eb37e81e16be5f639dde59 11652 libproxy_0.4.15-8.debian.tar.xz 2f423597a5d12155c6a0347f5ee2128c8c9f8091 19932 libproxy_0.4.15-8_source.buildinfo Checksums-Sha256: d2f715439f7a45b8678d945c6497de57fba6854273177ffa49fe1e9696ee64c8 3454 libproxy_0.4.15-8.dsc 19a161ec6e0ccfdd697bf8413418c4dc26208715e22bc85f0918a76094ec 11652 libproxy_0.4.15-8.debian.tar.xz d21915fa13f91da885bbaa32519f1387f2e8deb1df8c145ce8bba7087adf107b 19932 libproxy_0.4.15-8_source.buildinfo Files: 4cd35761239ab8b4c72c9b739d08c006 3454 libs optional libproxy_0.4.15-8.dsc 1010006b88ee7c01c855561feb755679 11652 libs optional libproxy_0.4.15-8.debian.tar.xz a9fd13ab279eacd4176458c5d4ec7a57 19932 libs optional libproxy_0.4.15-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAl2rnlcACgkQ5mx3Wuv+ bH2nqRAAgQCxW7UMezFDVG5g9Rr72HGplFPD4LQBfK2mCd8ol5cXr9wYntsErCaR UGTz+pYflX3ZqF48KelvgoKxCKXwpykxKh6+Y5TPZf6/njthiu+CsCpK7o3fE9oL NUzU5AI01hB5uJKCezmGCCX2ccU3DuOpaYZ0CWGe5UPVbVJyvS7DrZA30tb3VqYg b3gFyIU+mtrxfT07gEalOTuwfkzTK6TlywZV5VBr9c7tWxS14jyFaJatVPaaTxG0 16MU1NtrPT1apY2BfJWhx3msmOlDNMv3F3bdUcOKIe8c/M51oaheF47q10hsX6P3 3K0xNTD83QBNPRUvMNVL7UpPD9jGicFUxmEXk3QSBPGPGZAlQ2CW7iyhvFvStzfS jVoZrC2Ogc+P7lW0M91HqCnbO2LiiNlbY+Yzg8mAdadWSUQN9wx3ahMT4XRALWTR Pf0KwHqf5GU/1I6r6XtjAYoqyLJBfIh8YYAfIG6okm0qCx819hDnCBKfv3w/yiqe DQMi5RxV1ANyMHqbKjw2yoL8/BhBBq5vgJybKGeKZgpKb5kLaZaqfACjdz1qecrj zYXGwsqi8ln7Y0U6fRlM9c1aLx3Vhip7XCE3HmuCB1J8HbjSmde1wi6w4PGtnLlJ jUVc+hlCFiamibprsMTIwKuZFhriHYOmE1oMYVHToTewYyA2Ays= =SHal -END PGP SIGNATURE End Message ---
Processed: Bug#942119 marked as pending in libproxy
Processing control commands: > tag -1 pending Bug #942119 [src:libproxy] libproxy: depends on mono for build-arch; mono not universally present Added tag(s) pending. -- 942119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942688: elixir-lang: tests fail randomly during build
Source: elixir-lang Version: 1.9.1.dfsg-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, The latest upload failed to build on a few architectures: https://buildd.debian.org/status/package.php?p=elixir-lang&suite=sid I tried building it locally and it worked. I then tried 10 builds in a row, and 1 of them failed. So I suspect that builds will fail ~ 10% of the time. Maybe if I tried more times I could have a better estimate, but this seems relevant enough since it already failed on the buildd. I have failures like this in past be caused by: - implicit dependency on the order in which tests are run (does the elixir test suite randomizes the execution order?) - timing issues and race conditions The full build log for the failed build is attached. Note that the failure I found does not match the ones that happened on the amd64 and arm64 buildds. So not only the tests fail randomly, but the failure is on different tests each time. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled elixir-lang_amd64-2019-10-19T23:09:13Z.build.gz Description: application/gzip signature.asc Description: PGP signature
Bug#942119: marked as pending in libproxy
Control: tag -1 pending Hello, Bug #942119 in libproxy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/libproxy/commit/54783bbd78a96c7c2fdb850be804a5f6c59c46dd Drop Build-Depends on dh-sequence-cli Closes: #942119 Thanks: Simon McVittie (this message was generated automatically) -- Greetings https://bugs.debian.org/942119
Bug#941414: certificates about to expire
Hi, > In fact, the proposed "fix" I'm working on is to actually get the > version that is currently in backports directly in the oldstable > distribution, but I need to tweak it a bit as to do that I need to > reintroduce the 'letsencrypt.sh' compatibility packages/scripts. unfortunately, that version (0.6.2-2+deb10u1~bpo9+1) is not backwards compatible with the current stretch version (0.3.1-3+deb9u2), in that it deploys all challenges for a certificate at once, and only then submits the verification requests for the individual host names. If you happen to deploy challenges for multiple host names to the same location, that fails because the last deployed challenge overwrites all other challenges in that location, and the verification request for the first host name then causes dehydrated to abort (also, without any useful error message). For anyone facing the same problem: A (temporary) workaround I found was to set HOOK_CHAIN=yes, which causes all challenges for a given domain to be deployed in a single call to the hook script. If your hook script simply ignores the additional parameters, that then causes only the first challenge to actually be deployed, and thus the verification for the first host name to succeed. Then you just have to re-run dehydrated until all the host names have been verified. Regards, Florian
Bug#938530: sphinxcontrib-actdiag: diff for NMU version 0.8.5-1.1
Control: tags 938530 + patch
Dear maintainer,
I've prepared an NMU for sphinxcontrib-actdiag (versioned as 0.8.5-1.1). The
diff
is attached to this message.
i've uploaded directly to unstable becaues it fixes a RC bug
Regards.
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/changelog sphinxcontrib-actdiag-0.8.5/debian/changelog
--- sphinxcontrib-actdiag-0.8.5/debian/changelog 2016-10-31 19:58:04.0 -0400
+++ sphinxcontrib-actdiag-0.8.5/debian/changelog 2019-10-19 18:07:40.0 -0400
@@ -1,3 +1,10 @@
+sphinxcontrib-actdiag (0.8.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #938530
+
+ -- Sandro Tosi Sat, 19 Oct 2019 18:07:40 -0400
+
sphinxcontrib-actdiag (0.8.5-1) unstable; urgency=medium
* New upstream release
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/control sphinxcontrib-actdiag-0.8.5/debian/control
--- sphinxcontrib-actdiag-0.8.5/debian/control 2016-10-31 19:58:02.0 -0400
+++ sphinxcontrib-actdiag-0.8.5/debian/control 2019-10-19 18:07:22.0 -0400
@@ -4,12 +4,6 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 9.0.0),
dh-python,
- python-all,
- python-setuptools,
- python-sphinx (>= 0.6),
- python-blockdiag (>= 1.5.0),
- python-actdiag (>= 0.5.3),
- python-mock,
python3-all,
python3-setuptools,
python3-sphinx (>= 0.6),
@@ -17,21 +11,8 @@
python3-actdiag (>= 0.5.3),
python3-mock
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://github.com/blockdiag/sphinxcontrib-actdiag
-Package: python-sphinxcontrib.actdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-actdiag (>= 0.5.3),
- python-sphinx (>= 0.6)
-Description: Sphinx "actdiag" extension
- This package contains the actdiag Sphinx extension. This extension enable you
- to insert activity diagrams in your Sphinx document. This is a sphinx
- extension which render block diagrams by using python-actdiag.
-
Package: python3-sphinxcontrib.actdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/rules sphinxcontrib-actdiag-0.8.5/debian/rules
--- sphinxcontrib-actdiag-0.8.5/debian/rules 2014-11-22 12:00:08.0 -0500
+++ sphinxcontrib-actdiag-0.8.5/debian/rules 2019-10-19 18:07:36.0 -0400
@@ -8,12 +8,8 @@
export PYBUILD_DISABLE=test
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
find $(CURDIR)/debian/python3-sphinxcontrib.actdiag -name tests -a -type d | xargs rm -rf
-
-override_dh_python2:
- dh_python2
- find $(CURDIR)/debian/python-sphinxcontrib.actdiag -name tests -a -type d | xargs rm -rf
Processed: sphinxcontrib-actdiag: diff for NMU version 0.8.5-1.1
Processing control commands: > tags 938530 + patch Bug #938530 [src:sphinxcontrib-actdiag] sphinxcontrib-actdiag: Python2 removal in sid/bullseye Added tag(s) patch. -- 938530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942674: git: FTBFS on big-endian targets - testsuite failure
Source: git Version: 1:2.24.0~rc0-1 Severity: serious Tags: ftbfs Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x Hi! git currently fails to build from source on all big-endian targets due to test suite failures. This includes powerpc, ppc64, sparc64 and s390x which is why this bug has severity serious [1]. There have been testsuite failures on big-endian in the past before, see [2]. I will also notify upstream. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=git&arch=s390x&ver=1%3A2.24.0%7Erc0-1&stamp=1571440098&raw=0 > [2] https://www.spinics.net/lists/git/msg363527.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#941414: certificates about to expire
On Sat, Oct 19, 2019 at 08:14:33PM +0200, Florian Zumbiehl wrote: > Is there any plan to fix this bug before then, or will users have to work > around this individually to avoid running into expired certificates? And if > the latter, what is the recommended workaround? Is the current backports > version usable? The current version in stretch-backports is perfectly usable. It also moves to the v2 version of the ACME API, which is the only one that Let's Encrypt now supports. In fact, the proposed "fix" I'm working on is to actually get the version that is currently in backports directly in the oldstable distribution, but I need to tweak it a bit as to do that I need to reintroduce the 'letsencrypt.sh' compatibility packages/scripts. So, yes, if you are affected by this bug I recommended to just use the version in stretch-backports. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#942667: cracklib2 ignores build failures
Package: src:cracklib Version: 2.9.6-2 Severity: serious Tags: sid bullseye cracklib2 ignores build failures, not setting -e for all the loops iterating over python versions. Seen with 3.8 as a supported python version.
Bug#942403: golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest
Le mardi 15 octobre 2019 à 21:08:17+0200, Paul Gevers a écrit : > Hi, > > On 15-10-2019 21:00, Paul Gevers wrote: > > github.com/CanonicalLtd/raft-membership > >dh_auto_test -O--buildsystem=golang > > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 > > github.com/CanonicalLtd/raft-membership > > # github.com/CanonicalLtd/raft-test/internal/network > > src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2: > > cannot use transport (type *eventTransport) as type raft.Transport in > > return argument: > > *eventTransport does not implement raft.Transport (missing TimeoutNow > > method) > > FAILgithub.com/CanonicalLtd/raft-membership [build failed] > > dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 > > github.com/CanonicalLtd/raft-membership returned exit code 2 > > make: *** [debian/rules:4: build] Error 255 > > By the way, this also looks very much like the error message in > golang-github-canonicalltd-raft-test > > Paul > > https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-canonicalltd-raft-test/3142465/log.gz > > github.com/CanonicalLtd/raft-test/internal/network > # github.com/CanonicalLtd/raft-test/internal/network > src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2: > cannot use transport (type *eventTransport) as type raft.Transport in > return argument: > *eventTransport does not implement raft.Transport (missing TimeoutNow > method) > dh_auto_build: cd obj-x86_64-linux-gnu && go install > -gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" > -asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" > -v -p 2 github.com/CanonicalLtd/raft-test > github.com/CanonicalLtd/raft-test/internal/election > github.com/CanonicalLtd/raft-test/internal/event > github.com/CanonicalLtd/raft-test/internal/fsms > github.com/CanonicalLtd/raft-test/internal/logging > github.com/CanonicalLtd/raft-test/internal/network returned exit code 2 Dear Paul, Thanks for the bug report. It seems to me that this bug is caused by the current version of golang-github-canonicalltd-raft-test in the archive. I'll upload the latest version ASAP. I'm not sure if I should reassign the bug to golang-github-canonicalltd-raft-test , feel free to do so. Cheers! -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Processed: tagging 922566, tagging 922573, tagging 922578, tagging 922582, tagging 922579, tagging 922583 ...
Processing commands for cont...@bugs.debian.org:
> tags 922566 + sid bullseye
Bug #922566 [src:actiona] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922573 + sid bullseye
Bug #922573 [src:darknet] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922578 + sid bullseye
Bug #922578 [src:eviacam] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922582 + sid bullseye
Bug #922582 [src:gmic] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922579 + sid bullseye
Bug #922579 [src:freeture] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922583 + sid bullseye
Bug #922583 [src:gst-plugins-bad1.0] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922584 + sid bullseye
Bug #922584 [src:limereg] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922585 + sid bullseye
Bug #922585 [src:mldemos] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922587 + sid bullseye
Bug #922587 [src:node-opencv] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922588 + sid bullseye
Bug #922588 [src:openalpr] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922590 + sid bullseye
Bug #922590 [src:php-facedetect] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922589 + sid bullseye
Bug #922589 [src:opencfu] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922591 + sid bullseye
Bug #922591 [src:ros-opencv-apps] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922592 + sid bullseye
Bug #922592 [src:ros-vision-opencv] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922593 + sid bullseye
Bug #922593 {Done: Bas Couwenberg } [src:saga] FTBFS
against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922595 + sid bullseye
Bug #922595 [src:sdaps] FTBFS due to PDF compilation failure (against Opencv
4.0.1)
Added tag(s) sid and bullseye.
> tags 922596 + sid bullseye
Bug #922596 [src:siril] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 922600 + sid bullseye
Bug #922600 [src:visp] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 915708 + sid bullseye
Bug #915708 [src:eviacam] eviacam FTBFS against opencv 3.4.4 in experimental
Added tag(s) sid and bullseye.
> tags 915712 + sid bullseye
Bug #915712 [src:php-facedetect] php-facedetect FTBFS against opencv 3.4.4 in
experimental
Added tag(s) sid and bullseye.
> tags 915711 + sid bullseye
Bug #915711 [src:mldemos] mldemos FTBFS against opencv 3.4.4 in experimental
Added tag(s) bullseye and sid.
> tags 922569 + sid bullseye
Bug #922569 {Done: Mo Zhou } [src:caffe] FTBFS against
opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 934868 + sid bullseye
Bug #934868 {Done: Yaroslav Halchenko } [pynwb] pynwb:
Please drop python2 support
Added tag(s) sid and bullseye.
> tags 922570 + sid bullseye
Bug #922570 {Done: Debian FTP Masters }
[src:caffe-contrib] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922574 + sid bullseye
Bug #922574 [src:digikam] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922586 + sid bullseye
Bug #922586 [src:mrpt] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922597 + sid bullseye
Bug #922597 {Done: Debian FTP Masters }
[src:sitplus] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915708
915711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915711
915712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915712
922566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922566
922569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922569
922570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922570
922573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922573
922574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922574
922578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922578
922579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922579
922582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922582
922583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922583
922584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922584
922585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922585
922586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922586
922587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922587
922588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922588
922589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922589
922590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922590
922591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922591
922592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922592
922593: https://bugs.debian.org/cgi-
Bug#941414: certificates about to expire
Hi, as the recommended strategy by LetsEncrypt is to renew certificates 30 days before their expiry, and we are approaching 30 days since the change that exposed this bug that thus is preventing certificate renewal since then, certificates generated using dehydrated are going to start expiring in about a week. Is there any plan to fix this bug before then, or will users have to work around this individually to avoid running into expired certificates? And if the latter, what is the recommended workaround? Is the current backports version usable? Regards, Florian
Processed: seqdiag: diff for NMU version 0.9.5+dfsg-1.2
Processing control commands: > tags 938466 + patch Bug #938466 [src:seqdiag] seqdiag: Python2 removal in sid/bullseye Added tag(s) patch. -- 938466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938466: seqdiag: diff for NMU version 0.9.5+dfsg-1.2
Control: tags 938466 + patch
Dear maintainer,
I've prepared an NMU for seqdiag (versioned as 0.9.5+dfsg-1.2). The diff
is attached to this message.
I've uploaded directly to unstable as it fixes an RC bug, and it's an NMU of
an NMU
Regards.
diff -Nru seqdiag-0.9.5+dfsg/debian/changelog seqdiag-0.9.5+dfsg/debian/changelog
--- seqdiag-0.9.5+dfsg/debian/changelog 2018-07-16 04:57:18.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/changelog 2019-10-19 14:10:26.0 -0400
@@ -1,3 +1,10 @@
+seqdiag (0.9.5+dfsg-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #938466
+
+ -- Sandro Tosi Sat, 19 Oct 2019 14:10:26 -0400
+
seqdiag (0.9.5+dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru seqdiag-0.9.5+dfsg/debian/control seqdiag-0.9.5+dfsg/debian/control
--- seqdiag-0.9.5+dfsg/debian/control 2016-10-11 00:33:57.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/control 2019-10-19 14:09:52.0 -0400
@@ -4,13 +4,7 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 8.0.0),
dh-python,
- python-all,
- python-setuptools,
pep8 (>= 1.3),
- python-nose,
- python-unittest2,
- python-reportlab,
- python-blockdiag (>= 1.5.0),
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -19,19 +13,8 @@
python3-blockdiag (>= 1.5.0),
fonts-vlgothic | fonts-japanese-gothic
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://blockdiag.com/
-Package: python-seqdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0)
-Description: seqdiag generate sequence-diagram image file from spec-text file
- Generate sequence-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. And get some examples and generated
- images.
-
Package: python3-seqdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages
--- seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages 2011-11-03 13:02:27.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/python-seqdiag.manpages 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-seqdiag.1
diff -Nru seqdiag-0.9.5+dfsg/debian/rules seqdiag-0.9.5+dfsg/debian/rules
--- seqdiag-0.9.5+dfsg/debian/rules 2014-08-31 22:31:04.0 -0400
+++ seqdiag-0.9.5+dfsg/debian/rules 2019-10-19 14:10:11.0 -0400
@@ -7,7 +7,7 @@
export PYBUILD_NAME=seqdiag
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable
On Thu, Oct 17, 2019 at 10:02 AM Moritz Muehlenhoff wrote: > IMHO for stretch-security/buster-security we should rather rebase the old > 4.9.2ish packages to 4.9.3, given that it creates new system users etc. > it seems not really suitable for a security update. Ok, that is what I did. Review welcome: https://people.debian.org/~rfrancoise/tcpdump/tcpdump_4.9.3-1~deb10u1_source.changes https://people.debian.org/~rfrancoise/tcpdump/tcpdump_4.9.3-1~deb9u1_source.changes Thanks.
Bug#942647: celery-batches: Incomplete debian/copyright, etc.
Source: celery-batches Version: 0.2-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: ftpmas...@debian.org, deba...@debian.org, rodrilopez@gmail.com Hi, I just ACCEPTed celery-batches from NEW but the FTP team noticed docs/ has a different license not mentioned in debian/copyright. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: tagging 933642
Processing commands for cont...@bugs.debian.org: > tags 933642 + pending Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py processes running after build Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 933642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 933642 in 2.19.4
Processing commands for cont...@bugs.debian.org: > found 933642 2.19.4 Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py processes running after build Marked as found in versions devscripts/2.19.4. > thanks Stopping processing here. Please contact me if you need assistance. -- 933642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942629: marked as done (golang-1.12: CVE-2019-17596: invalid public key causes panic in dsa.Verify)
Your message dated Sat, 19 Oct 2019 12:20:23 + with message-id and subject line Bug#942629: fixed in golang-1.12 1.12.12-1 has caused the Debian Bug report #942629, regarding golang-1.12: CVE-2019-17596: invalid public key causes panic in dsa.Verify 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.) -- 942629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-1.13 Version: 1.13.1-1 Severity: grave Tags: security upstream Control: clone -1 -2 Control: reassign -2 src:golang-1.12 1.12.10-1 Control: retitle -2 golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify Control: forwarded -1 https://github.com/golang/go/issues/34962 Control: forwarded -2 https://github.com/golang/go/issues/34961 Hi, The following vulnerability was published for golang-1.13. CVE-2019-17596[0]: crypto/dsa: invalid public key causes panic in dsa.Verify 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-2019-17596 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17596 [1] https://github.com/golang/go/issues/34962 [2] https://github.com/golang/go/issues/34961 [3] https://github.com/golang/go/issues/34960 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: golang-1.12 Source-Version: 1.12.12-1 We believe that the bug you reported is fixed in the latest version of golang-1.12, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated golang-1.12 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: Sat, 19 Oct 2019 13:51:14 +0200 Source: golang-1.12 Architecture: source Version: 1.12.12-1 Distribution: unstable Urgency: medium Maintainer: Go Compiler Team Changed-By: Dr. Tobias Quathamer Closes: 942629 Changes: golang-1.12 (1.12.12-1) unstable; urgency=medium . * New upstream version 1.12.12 - Remove patch 0003-arm64-arm64asm-recognise-ssbb-pssbb-mnemonics.patch, has been applied upstream. - crypto/dsa: invalid public key causes panic in dsa.Verify. Fixes CVE-2019-17596. Closes: #942629 * Update Standards-Version to 4.4.1, no changes needed Checksums-Sha1: 5c4db0783e2f3ddf9f3bbb1a15b4a50282b45c00 2858 golang-1.12_1.12.12-1.dsc 92172e71bbf60c1855b6ecbc747270ec0d89fd69 21980254 golang-1.12_1.12.12.orig.tar.gz 70cef2d325fc57c7adc84b2eab3965469727fe72 819 golang-1.12_1.12.12.orig.tar.gz.asc 6385dfce61a0982e8676835c465122871ba9e9ff 35816 golang-1.12_1.12.12-1.debian.tar.xz ce629a856d9d3b9fc20b38036f68faa06b1ea30f 6559 golang-1.12_1.12.12-1_amd64.buildinfo Checksums-Sha256: 3dcb95c42e9783a34d88aa85b859173d5b0d279a432922ce7db4906fdd477218 2858 golang-1.12_1.12.12-1.dsc fcb33b5290fa9bcc52be3211501540df7483d7276b031fc77528672a3c705b99 21980254 golang-1.12_1.12.12.orig.tar.gz 430ae60dfd6757054a7db1ea3e39d362499b96e7d9b2490beb07706a305dddea 819 golang-1.12_1.12.12.orig.tar.gz.asc d66b57069bea31fa60d75993bd2e166d155e70e373b3707b217db466b3939e60 35816 golang-1.12_1.12.12-1.debian.tar.xz 3a0f12464cf5c3f160068f1dffb323c8a6c29d3bc329578d4d0fb914453080b2 6559 golang-1.12_1.12.12-1_amd64.buildinfo Files: cc1a1ffe10b3afe291a8d7b694d83e66 2858 devel optional golang-1.12_1.12.12-1.dsc 7524b954f00d8eaf34c5c08772c7944b 21980254 devel optional golang-1.12_1.12.12.orig.tar.gz dde5ef690f1be2c523e1476fe8788937 819 devel optional golang-1.12_1.12.12.orig.tar.gz.asc 79bb772a5b22ecd2b25ad7b54712d761 35816 devel optional golang-1.12_1.12.12-1.debian.tar.xz 76156b839fa63429c8d8c8ba529ade2e 6559 devel optional golang-1.12_1.12.12-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl2q+t4ACgkQEwLx8Dbr 6xlY7w//WUpeB83qpLOFPIgm5jbycxxq+GoW3/VYSySIM+JED8E/txg4cjJQy3wQ kog3VJ0oIJQvSlswWSV5m6WP0k5Tr0k6YjW4CKR09ztVQeWU8RIk2rehA2vRwnVN
Bug#942628: marked as done (golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify)
Your message dated Sat, 19 Oct 2019 12:04:43 + with message-id and subject line Bug#942628: fixed in golang-1.13 1.13.3-1 has caused the Debian Bug report #942628, regarding golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify 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.) -- 942628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-1.13 Version: 1.13.1-1 Severity: grave Tags: security upstream Control: clone -1 -2 Control: reassign -2 src:golang-1.12 1.12.10-1 Control: retitle -2 golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify Control: forwarded -1 https://github.com/golang/go/issues/34962 Control: forwarded -2 https://github.com/golang/go/issues/34961 Hi, The following vulnerability was published for golang-1.13. CVE-2019-17596[0]: crypto/dsa: invalid public key causes panic in dsa.Verify 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-2019-17596 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17596 [1] https://github.com/golang/go/issues/34962 [2] https://github.com/golang/go/issues/34961 [3] https://github.com/golang/go/issues/34960 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: golang-1.13 Source-Version: 1.13.3-1 We believe that the bug you reported is fixed in the latest version of golang-1.13, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated golang-1.13 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: Sat, 19 Oct 2019 13:30:36 +0200 Source: golang-1.13 Architecture: source Version: 1.13.3-1 Distribution: unstable Urgency: medium Maintainer: Go Compiler Team Changed-By: Dr. Tobias Quathamer Closes: 942628 Changes: golang-1.13 (1.13.3-1) unstable; urgency=medium . * New upstream version 1.13.3 - Refresh patch - crypto/dsa: invalid public key causes panic in dsa.Verify. Fixes CVE-2019-17596. Closes: #942628 * Update Standards-Version to 4.4.1, no changes needed Checksums-Sha1: ffd4f399be0b601b6d19f367423bb334408d00de 2848 golang-1.13_1.13.3-1.dsc 1fdfd1586888d4d24f5dadee6016092f89e6049e 21618379 golang-1.13_1.13.3.orig.tar.gz 71354e37d6380fca61ee10a0922661fe8fe5c7b7 819 golang-1.13_1.13.3.orig.tar.gz.asc 9282a793d3a750967c8825978dcd3c01ea7ccc59 34168 golang-1.13_1.13.3-1.debian.tar.xz 27ddba6e9c0e2edd4c5e2f76061aabd589de9a18 6542 golang-1.13_1.13.3-1_amd64.buildinfo Checksums-Sha256: 1af77d2830097e986e50d8952a3d6c6bad60b1adec27d237d91c305d8b8e7d66 2848 golang-1.13_1.13.3-1.dsc 4f7123044375d5c404280737fbd2d0b17064b66182a65919ffe20ffe8620e3df 21618379 golang-1.13_1.13.3.orig.tar.gz 2a7c3786a48ec76790f780d35def629e8b773362ea1b85f4ebebd8538c55df91 819 golang-1.13_1.13.3.orig.tar.gz.asc 7c7cf2ffce8028eb1669748d60e5918b039940b0b093b29f9a297f854780a38c 34168 golang-1.13_1.13.3-1.debian.tar.xz f2370a67c474fb3e5445ba84194bbfd98096c9d8bc9a157e2094169256354bd2 6542 golang-1.13_1.13.3-1_amd64.buildinfo Files: c322cf6fbc7352036701e050aef23bf8 2848 devel optional golang-1.13_1.13.3-1.dsc 94ae8bf6a4fe623e34cb8b0db2a71ec0 21618379 devel optional golang-1.13_1.13.3.orig.tar.gz 35a89bc604faed9bc3a2caba6d897b53 819 devel optional golang-1.13_1.13.3.orig.tar.gz.asc 655497421e2ee72c9279614ea78b3b60 34168 devel optional golang-1.13_1.13.3-1.debian.tar.xz 80911b1ba1224f109e26695d17fa14d2 6542 devel optional golang-1.13_1.13.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl2q9uoACgkQEwLx8Dbr 6xmU6A/+O6L7UcbJqKjCDQ8EQRjGvKZIQlTDuqf0WWgp6JrYfKIgZB50MzNloVfH 2g08XH9N6uzJWdZs2DoR0P4XN9pG5jMJm8fgC5LMFrwQ7SmNV85OU4gu44Lh9yJm +neon+D9GtD4MNy1VtKD+yVKZ+fmfeN5aF4wSTHaBxwGO78v05so+7EV7lJSorpi QW2oNSCj6kTmZogOWuQgoCnDQCunTHVVKE8DE7Pxfvo4YKX
Bug#937745: marked as done (python-fabio: Python2 removal in sid/bullseye)
Your message dated Sat, 19 Oct 2019 11:49:24 + with message-id and subject line Bug#937745: fixed in python-fabio 0.9.0+dfsg-2 has caused the Debian Bug report #937745, regarding python-fabio: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-fabio Version: 0.9.0+dfsg-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-fabio If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-fabio Source-Version: 0.9.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of python-fabio, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated python-fabio 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: Sat, 19 Oct 2019 13:25:00 +0200 Source: python-fabio Architecture: source Version: 0.9.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Picca Frédéric-Emmanuel Closes: 937745 Changes: python-fabio (0.9.0+dfsg-2) unstable; urgency=medium . * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP. * Use debhelper-compat instead of debian/compat. * Removed Python2 module (Closes: #937745). * d/control: switched to compat level 12. - d/rules: Use --doc-main-package python3-fabio * Bump Standards-Version 4.4.1. Checksums-Sha1: 3c93f7741b84aa2dab889953512d7ea2c1a2afd1 2922 python-fabio_0.9.0+dfsg-2.dsc 28275067969cec71621034de31f38fbb56f4b79b 8192 python-fabio_0.9.0+dfsg-2.debian.tar.xz Checksums-Sha256: c8db755d288f289517cf9d0af828e2039fc40d221c777bdbed03a62d4a736f06 2922 python-fabio_0.9.0+dfsg-2.dsc f2032a2ba7beb67e8820d144a6ff0f04cf3d2b44a2e
Processed: Bug housekeeping
Processing commands for cont...@bugs.debian.org: > retitle 942629 golang-1.12: CVE-2019-17596: invalid public key causes panic > in dsa.Verify Bug #942629 [src:golang-1.12] golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify Changed Bug title to 'golang-1.12: CVE-2019-17596: invalid public key causes panic in dsa.Verify' from 'golang-1.13: CVE-2019-17596: invalid public key causes panic in dsa.Verify'. > thanks Stopping processing here. Please contact me if you need assistance. -- 942629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938481: marked as done (silx: Python2 removal in sid/bullseye)
Your message dated Sat, 19 Oct 2019 11:35:23 + with message-id and subject line Bug#938481: fixed in silx 0.11.0+dfsg-2 has caused the Debian Bug report #938481, regarding silx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:silx Version: 0.11.0+dfsg-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:silx If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: silx Source-Version: 0.11.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of silx, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated silx 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: Sat, 19 Oct 2019 13:19:44 +0200 Source: silx Architecture: source Version: 0.11.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Picca Frédéric-Emmanuel Closes: 938481 Changes: silx (0.11.0+dfsg-2) unstable; urgency=medium . * Use debhelper-compat instead of debian/compat. * remove Python2 modules (Closes: #938481). * Switched to compat level 12 - d/rules: Used --doc-main-package python3-silx. Checksums-Sha1: dbd26daf522d3217bbdece371a9c9ea98b35ed89 3108 silx_0.11.0+dfsg-2.dsc c9ca59dede63b6bcbc6287a5636db878d8346019 20448 silx_0.11.0+dfsg-2.debian.tar.xz Checksums-Sha256: b35ff4816c551882b6bc2138ec3bc89f419609f261acec5421d5e1d9cf987420 3108 silx_0.11.0+dfsg-2.dsc 010dbd09f6bfa22912625a24fba3ad574fcb57d3ceee3a6aac19cc1cef6ea8b4 20448 silx_0.11.0+dfsg-2.debian.tar.xz Files: 38d988d218b98e47b599b04360b6f173 3108 science optional silx_0.11.0+dfsg-2.dsc 00ef8ce0e2191116f108dcc9eb093683 20448
Bug#942634: apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX)
Package: apt-cacher-ng Version: 3.2-2 Severity: grave Justification: renders package unusable Dear maintainer, apt-cacher-ng stopped working recently when used to cache the debian/sid suite. It reports the following error: | An error occurred while reading this file, some contents may have been ignored. Tag | Parsing metadata in deb/dists/sid/main/binary-arm64/Packages.xz I have tracked down this issue to a too small value of BUFSIZEMAX. The Packages file in sid now contains lines that are way longer than before and thus this variable needs to get adjusted: | $ wget -q -O - http://ftp.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | xzcat | wc -L | 59936 | $ wget -q -O - http://ftp.debian.org/debian/dists/sid/main/binary-amd64/Packages.xz | xzcat | wc -L | 149619 I have found that doubling the value to 32*4096 is enough, but it might be safer to double it to 64*4096 to be able to cope with further increase. Regards, Aurelien -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#939974: bug has been resolved
I can conform that the recent introduction of uhd 3.14.1.1-1 has fixed the FTBFS and the package is building fine again. -- - Harald Welte http://laforge.gnumonks.org/ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Processed: tagging 941999, tagging 939751, tagging 941610
Processing commands for cont...@bugs.debian.org: > tags 941999 + pending Bug #941999 [src:kopanocore] kopanocore: autopkgtest tries to install packages itself but doesn't exit appropriately if that fails Added tag(s) pending. > tags 939751 + pending Bug #939751 [kopano-server] Kopano-Server in Stable not compatible with MariaDB 10.3 Added tag(s) pending. > tags 941610 + pending Bug #941610 [kopano-server] kopano-server crashes Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 939751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939751 941610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941610 941999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
