Processed: fixed 960867 in 3.0.5+dfsg-1
Processing commands for cont...@bugs.debian.org: > fixed 960867 3.0.5+dfsg-1 Bug #960867 [fs-uae-launcher] fs-uae-launcher: The application crash every time at the beginning Marked as fixed in versions fs-uae/3.0.5+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 960867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960907: marked as done (dothost: CI test fails due to layout changes but is flagged as a debhelper regression)
Your message dated Mon, 25 May 2020 03:03:30 + with message-id and subject line Bug#960907: fixed in dothost 0.2-4 has caused the Debian Bug report #960907, regarding dothost: CI test fails due to layout changes but is flagged as a debhelper regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dothost Severity: serious Control: affects -1 src:debhelper The dothost CI test has the following output: > """ > Removing autopkgtest-satdep (0) ... > autopkgtest [08:29:06]: test command1: dothost www.debian.org | graph-easy > --as boxart || exit 77 > autopkgtest [08:29:06]: test command1: [--- > Warning: Layouter could only place 10 nodes/14 edges out of 10/15 - giving up > at /usr/bin/graph-easy line 144. > >┌──┐ > ┌───┐ >∨ │ ∨ >│ > ┌┐ ┏┓ > ┌─┐ ┌─┐ > ┌─┐ > │ 149.20.4.15 │ <┐ ┃┃ ──> │ > 128.31.0.62 │ ──> │ mirror-csail.debian.org │ ──> │ > 2603:400a::bb8::801f:3e │ ─┐ > └┘ │ ┃┃ > └─┘ └─┘ > └─┘ │ >│ │ ┃┃ >∧ ∧ > │ >│ │ ┃ www.debian.org ┃ > ──┼───┘ >│ >∨ │ ┃┃ >│ > │ > ┌┐ │ ┃┃ >│ > │ > ┌> │ mirror-isc3.debian.org │ ─┘ ┃┃ > ─┐ > └──┘ > │ └┘ ▙▟ > │ > ││ │ > │ > ││ │ > │ > │∨ ∨ > │ > │ ┌┐ ┌┐ > ┌─┐ │ > └─ │2001:4f8:1:c::15│ │ 130.89.148.77 │ ──> │ > klecker-misc.debian.org │ │ > └┘ └┘ > └─┘ │ > ┌┐ > │ > │ 2001:67c:2564:a119::77 │ > <┘ > └┘ > autopkgtest [08:29:14]: test command1: ---] > autopkgtest [08:29:14]: test command1: - - - - - - - - - - results - - - - - > - - - - - > command1 FAIL stderr: Warning: Layouter could only place 10 > nodes/14 edges out of 10/15 - giving up at /usr/bin/graph-easy line 144. > autopkgtest [08:29:14]: test command1: - - - - - - - - - - stderr - - - - - > - - - - - > Warning: Layouter could only place 10 nodes/14 edges out of 10/15 - giving up > at /usr/bin/graph-easy line 144. > autopkgtest [08:29:14]: test command2: preparing testbed > """ https://ci.debian.net/data/autopkgtest/testing/arm64/d/dothost/5540910/log.gz I presume it is related to dothost resolving "www.debian.org" and it suddenly has more IPs and hostnames to render instead of having fixed test data. Sadly, this is considered a "regression caused by debhelper" by the CI/Britney framework as the problem occurred after the previous baseline test of dothost. ~Niels --- End Message --- --- Begin Message --- Source: dothost Source-Version: 0.2-4 Done: Thiago Andrade Marques We believe
Bug#951681: marked as done (python-jenkinsapi: FTBFS due to missing build deps and pylint command)
Your message dated Sun, 24 May 2020 22:04:30 + with message-id and subject line Bug#951681: fixed in python-jenkinsapi 0.3.11-2 has caused the Debian Bug report #951681, regarding python-jenkinsapi: FTBFS due to missing build deps and pylint command 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.) -- 951681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-jenkinsapi Version: 0.3.11-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, python-jenkinsapi currently fails to build from source after the Python 3 changes. There are a few tweaks that need to be made to get it building again. In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS: - Build-depend on dh-python and python3-pbr. - Use pylint instead of pylint3. Thanks for considering the patch. Logan -- System Information: Debian Release: buster/sid APT prefers eoan-updates APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan'), (100, 'eoan-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-29-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru python-jenkinsapi-0.3.11/debian/control python-jenkinsapi-0.3.11/debian/control --- python-jenkinsapi-0.3.11/debian/control 2020-02-16 18:39:59.0 -0500 +++ python-jenkinsapi-0.3.11/debian/control 2020-02-19 22:01:41.0 -0500 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Al Stone Build-Depends: debhelper (>= 12), python3-all-dev, python3-lxml, - python3-setuptools, python3-pytest, pylint3 + python3-setuptools, python3-pytest, pylint3, dh-python, python3-pbr Standards-Version: 4.5.0 Homepage: http://pypi.python.org/pypi/jenkinsapi Vcs-Git: https://github.com/ahs3/python-jenkinsapi diff -Nru python-jenkinsapi-0.3.11/debian/patches/codestyle.patch python-jenkinsapi-0.3.11/debian/patches/codestyle.patch --- python-jenkinsapi-0.3.11/debian/patches/codestyle.patch 2020-02-16 18:39:59.0 -0500 +++ python-jenkinsapi-0.3.11/debian/patches/codestyle.patch 2020-02-19 22:01:41.0 -0500 @@ -1,11 +1,10 @@ -diff -Naur orig-jenkinsapi/Makefile fixed-jenkinsapi/Makefile orig-jenkinsapi/Makefile 2020-02-16 17:49:45.404336646 -0700 -+++ fixed-jenkinsapi/Makefile 2020-02-16 17:50:25.352625604 -0700 +--- a/Makefile b/Makefile @@ -1,7 +1,6 @@ .PHONY: lint tox dist lint: - pycodestyle - pylint3 jenkinsapi/*.py + pylint jenkinsapi/*.py tox: diff -Nru python-jenkinsapi-0.3.11/debian/patches/install.patch python-jenkinsapi-0.3.11/debian/patches/install.patch --- python-jenkinsapi-0.3.11/debian/patches/install.patch 2020-02-16 18:39:59.0 -0500 +++ python-jenkinsapi-0.3.11/debian/patches/install.patch 2020-02-19 22:01:41.0 -0500 @@ -1,12 +1,11 @@ -diff -Naur orig-jenkinsapi/Makefile fixed-jenkinsapi/Makefile orig-jenkinsapi/Makefile 2020-02-16 18:11:36.225956771 -0700 -+++ fixed-jenkinsapi/Makefile 2020-02-16 18:13:10.706654980 -0700 +--- a/Makefile b/Makefile @@ -1,4 +1,4 @@ -.PHONY: lint tox dist +.PHONY: lint tox dist install lint: - pylint3 jenkinsapi/*.py + pylint jenkinsapi/*.py @@ -9,3 +9,5 @@ dist: python3 setup.py sdist bdist_wheel diff -Nru python-jenkinsapi-0.3.11/debian/patches/python3.patch python-jenkinsapi-0.3.11/debian/patches/python3.patch --- python-jenkinsapi-0.3.11/debian/patches/python3.patch 2020-02-16 18:39:59.0 -0500 +++ python-jenkinsapi-0.3.11/debian/patches/python3.patch 2020-02-19 22:01:41.0 -0500 @@ -1,7 +1,6 @@ -diff -Naur python-jenkinsapi.github/Makefile fixed-jenkinsapi/Makefile python-jenkinsapi.github/Makefile 2020-02-16 16:46:46.767307926 -0700 -+++ fixed-jenkinsapi/Makefile 2020-02-16 17:02:37.545891630 -0700 -@@ -1,17 +1,17 @@ +--- a/Makefile b/Makefile +@@ -1,7 +1,7 @@ .PHONY: test lint tox coverage dist test: @@ -10,10 +9,7 @@ lint: pycodestyle -- pylint jenkinsapi/*.py -+ pylint3 jenkinsapi/*.py - - tox: +@@ -11,7 +11,7 @@ tox dist: --- End Message
Bug#952750: marked as done (python3-jenkinsapi: missing (unversioned) Breaks+Replaces: python-jenkinsapi)
Your message dated Sun, 24 May 2020 22:04:30 + with message-id and subject line Bug#952750: fixed in python-jenkinsapi 0.3.11-2 has caused the Debian Bug report #952750, regarding python3-jenkinsapi: missing (unversioned) Breaks+Replaces: python-jenkinsapi 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.) -- 952750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-jenkinsapi Version: 0.3.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-jenkinsapi_0.3.11-1_all.deb ... Unpacking python3-jenkinsapi (0.3.11-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-jenkinsapi_0.3.11-1_all.deb (--unpack): trying to overwrite '/usr/bin/jenkins_invoke', which is also in package python-jenkinsapi 0.2.30-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-jenkinsapi_0.3.11-1_all.deb Since the binary package python-jenkinsapi is gone, the Breaks+Replaces can be unversioned. cheers, Andreas python-jenkinsapi=0.2.30-1_python3-jenkinsapi=0.3.11-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-jenkinsapi Source-Version: 0.3.11-2 Done: Al Stone We believe that the bug you reported is fixed in the latest version of python-jenkinsapi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Al Stone (supplier of updated python-jenkinsapi 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: Sun, 24 May 2020 15:09:34 -0600 Source: python-jenkinsapi Binary: python3-jenkinsapi Architecture: source all Version: 0.3.11-2 Distribution: unstable Urgency: medium Maintainer: Al Stone Changed-By: Al Stone Description: python3-jenkinsapi - bindings for Python usage of the Jenkins remote API Closes: 951681 952750 Changes: python-jenkinsapi (0.3.11-2) unstable; urgency=medium . * Fix "FTBFS due to missing build deps and pylint command" -- used the patch to correct build-deps and pylint usage (Closes: #951681) * Fix "missing (unversioned) Breaks+Replaces: python-jenkinsapi" -- just needed to add Breaks+Replace to control file since python3-jenkinsapi replaces the old package completely (Closes: #952750) * Minor lintian fix to remove a .gitignore file from build Checksums-Sha1: 79e9fc7393ebeca8be455449e8c9ff3eb753697f 1947 python-jenkinsapi_0.3.11-2.dsc 4ce1c16b0dfff7470381c441cd216893985b789e 3676 python-jenkinsapi_0.3.11-2.debian.tar.xz 49e14e98731a94011f79a98e3da1418648e04bed 7067 python-jenkinsapi_0.3.11-2_amd64.buildinfo 71d4f5702994f9d76b1536840840cb07d7696b36 102480 python3-jenkinsapi_0.3.11-2_all.deb Checksums-Sha256: 20c34400553a3561888cad363bce9258e39f021cf04da604840b7fbbd9a29a66 1947 python-jenkinsapi_0.3.11-2.dsc 3afca41567dc7db4ef6303c7a62f1f054d42a5ed52d87313ee9ab0f6ed06 3676 python-jenkinsapi_0.3.11-2.debian.tar.xz 06f9c600b48f7e8ca59ec02f33c6b7ac81495665504de257c7d353171669b95a 7067 python-jenkinsapi_0.3.11-2_amd64.buildinfo 15e9840d235367b1a3f13a2a2391f938a8e9293aa47f1f3e1405c5e0e2f0910e 102480 python3-jenkinsapi_0.3.11-2_all.deb Files: 086eeb449fcabe78e69d548f6382ee81 1947 python optional python-jenkinsapi_0.3.11-2.dsc 01b3bc74fad51de1c54ff1b7060d7d7f 3676 python optional python-jenkinsapi_0.3.11-2.debian.tar.xz e11dcddde122eb583517b49a3880cd78 7067 python
Processed: Re: Bug#951722: autopkgtest suite flaky on arm64
Processing control commands: > tags -1 patch Bug #951722 [src:dovecot] autopkgtest suite flaky on arm64 Bug #953576 [src:dovecot] dovecot: flaky arm64 autopkgtest: debian/tests/usage/00_setup exited with return code 75 Added tag(s) patch. Added tag(s) patch. -- 951722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951722 953576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951722: autopkgtest suite flaky on arm64
control: tags -1 patch
Michael sent me his draft patch. Slightly modified version with added
commit message attached. Diff is against latest upstream git version.
Thanks Michael!
>From 89399122692823bc215cf1097b05da4ee2201e0e Mon Sep 17 00:00:00 2001
From: Nis Martensen
Date: Sun, 24 May 2020 22:05:42 +0200
Subject: [PATCH 1/2] systemd integration: notify service manager when ready
With Type=simple or Type=forking, systemd does not really know when the
service is ready to accept connections and might start depending
services too early. Use Type=notify to explicitly tell the service
manager when the service is ready.
For a real problem caused by assuming readiness too early, please see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951722
For the meaning of the service type and details of the readiness
protocol, see also the following links:
https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type=
https://www.freedesktop.org/software/systemd/man/sd_notify.html
As discussed in the last link, more elaborate state notifications are
possible. This patch only implements the most basic part.
Original patch prepared by Michael Biebl, with slight modification.
---
dovecot.service.in | 3 +--
src/lib-master/master-service-settings.c | 2 +-
src/master/main.c| 6 ++
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/dovecot.service.in b/dovecot.service.in
index 5c45f590b..a1df992c5 100644
--- a/dovecot.service.in
+++ b/dovecot.service.in
@@ -14,9 +14,8 @@ Documentation=http://wiki2.dovecot.org/
After=local-fs.target network-online.target
[Service]
-Type=simple
+Type=notify
ExecStart=@sbindir@/dovecot -F
-PIDFile=@rundir@/master.pid
ExecReload=@bindir@/doveadm reload
ExecStop=@bindir@/doveadm stop
PrivateTmp=true
diff --git a/src/lib-master/master-service-settings.c b/src/lib-master/master-service-settings.c
index 657ef66bc..c7b8b369c 100644
--- a/src/lib-master/master-service-settings.c
+++ b/src/lib-master/master-service-settings.c
@@ -62,7 +62,7 @@ static const struct setting_define master_service_setting_defines[] = {
/* */
#ifdef HAVE_SYSTEMD
-# define ENV_SYSTEMD " LISTEN_PID LISTEN_FDS"
+# define ENV_SYSTEMD " LISTEN_PID LISTEN_FDS NOTIFY_SOCKET"
#else
# define ENV_SYSTEMD ""
#endif
diff --git a/src/master/main.c b/src/master/main.c
index 6e0e68fe7..08bea05ed 100644
--- a/src/master/main.c
+++ b/src/master/main.c
@@ -26,6 +26,9 @@
#include "service-process.h"
#include "service-log.h"
#include "dovecot-version.h"
+#ifdef HAVE_SYSTEMD
+#include "sd-daemon.h"
+#endif
#include
#include
@@ -544,6 +547,9 @@ static void main_init(const struct master_settings *set)
master_clients_init();
services_monitor_start(services);
+#ifdef HAVE_SYSTEMD
+ sd_notify(0, "READY=1");
+#endif
startup_finished = TRUE;
}
--
2.20.1
Bug#949638: tesseract: uses -march=native
On Sun, May 24, 2020 at 10:14:49PM +0200, Stefan Weil wrote: > Adrian, I am afraid that there is a misunderstanding. > > The code part which is compiled with -march=native is never executed by > default. I get that point. > There is a command line option which allows users to select the code > which is used for certain time critical calculations (dot product). A > wrong choice is not a security problem You misunderstand the part about the security update, security updates are just the most common reason why a package gets updated (and therefore rebuilt) in a stable distribution. Example: Debian 11 will be released in summer 2021. In autumn 2021 a user sets up a new system and selects "native" for an important production setup with an Intel CPU. In spring 2022 a (security or other) update for Tesseract happens in Debian 11, built on a buildd with the latest AMD CPU. The working production setup suddenly always crashes. > That's quite common for other packages including the standard C > library and scientific libraries, too. They all contain optimized > functions which require certain hardware and which crash otherwise. With proper runtime autodetection of the hardware, if you manage to get a crash it is a bug in these packages. It is quite rare that packages offer manual selection in addition to autodetection. > but simply will crash the > application, no matter whether the user selected "native", "avx" or > "neon". Even when built on the same computer I would have doubts whether automatic vectorization[1] of the trivial C code really beats the hand-written AVX2 code, but when the code is not even built for the computer in question what's the point? A "native" option meaning "some random buildd somewhere" is just confusing, it doesn't make sense for distributions. > Regards > > Stefan cu Adrian [1] if it happens at all, the Debian package build currently overwrites the -O3 with a subsequent -O2
Processed: Re: Bug#961377: raspi3-firmware: recent stable update causes non-booting systems
Processing commands for cont...@bugs.debian.org: > tags 961377 + confirmed,pending Bug #961377 [raspi3-firmware] raspi3-firmware: recent stable update causes non-booting systems Added tag(s) pending and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 961377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961377: raspi3-firmware: recent stable update causes non-booting systems
tags 961377 + confirmed,pending
thanks
Thorsten Glaser dijo [Sat, May 23, 2020 at 08:55:01PM +0200]:
> Package: raspi3-firmware
> Version: 1.20190215-1+deb10u3
> Severity: critical
> Tags: patch buster
> Justification: breaks the whole system
>
> /etc/kernel/postinst.d/z50-raspi3-firmware in +deb10u3 contains:
>
>67 for dtn in ${dtb_path}/bcm*.dtb; do
>68 [ -e "${dtb}" ] && cp "${dtb}" /boot/firmware/
>69 done
>
> It’s hard to see, a typo, and not in unstable (where commit
> 165f43a6ca14d240f199e8ab8924e503ca5f427d got it right), but
> commit fc3df0e8c64c2c62a54e0efcd226e36f28ccd3a4 uses “dtn”,
> not “dtb”, as for variable, but refers to “dtb”.
VERY GOOD CATCH! Thanks a lot for this. I'm pushing it to Git right
away, and will try to push a new version soon. It slipped under my
nose :-(
I will try to build+test+upload this in the next couple of days.
https://salsa.debian.org/debian/raspi-firmware/-/commit/2bf38f62de0514c2759f2c33d147c935e4d044bf
Processed: bug 959885 is forwarded to https://gitlab.com/inkscape/inkscape/-/issues/1565
Processing commands for cont...@bugs.debian.org: > forwarded 959885 https://gitlab.com/inkscape/inkscape/-/issues/1565 Bug #959885 [inkscape] inkscape: crashes when called without X server Changed Bug forwarded-to-address to 'https://gitlab.com/inkscape/inkscape/-/issues/1565' from 'https://gitlab.com/inkscape/inbox/-/issues/2755'. > thanks Stopping processing here. Please contact me if you need assistance. -- 959885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 815068, unarchiving 828749, fixed 815068 in 0.8.1-6, fixed 828749 in 0.8.1-6
Processing commands for cont...@bugs.debian.org:
> unarchive 815068
Bug #815068 {Done: Simon McVittie } [src:telepathy-salut]
telepathy-salut build-depends on removed python-twisted-words
Unarchived Bug 815068
> unarchive 828749
Bug #828749 {Done: Simon McVittie } [src:telepathy-salut]
telepathy-salut: please make the build reproducible
Unarchived Bug 828749
> fixed 815068 0.8.1-6
Bug #815068 {Done: Simon McVittie } [src:telepathy-salut]
telepathy-salut build-depends on removed python-twisted-words
Marked as fixed in versions telepathy-salut/0.8.1-6.
> # changes were incorporated without ack'ing NMU
> fixed 828749 0.8.1-6
Bug #828749 {Done: Simon McVittie } [src:telepathy-salut]
telepathy-salut: please make the build reproducible
Marked as fixed in versions telepathy-salut/0.8.1-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
815068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815068
828749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#936173: marked as pending in avahi
Control: tag -1 pending Hello, Bug #936173 in avahi 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/utopia-team/avahi/-/commit/36c4c8e611450f6c5b8707063d237abb81bf70d1 Switch from python2 to python3 A bunch of work has been made since 0.7 that should make python parts work with both python 2.7 and python 3. This should allow us to switch over to python3. This includes renaming the python-avahi package to python3-avahi. The only remaining package with a hard dependency on python-avahi is avahi-discover, which is also fixed in this commit. [smcv: squash 0beec518, 5cb43f9c, 56b02b8b into one commit] Closes: #853239 Closes: #936173 (this message was generated automatically) -- Greetings https://bugs.debian.org/936173
Processed: Bug#936173 marked as pending in avahi
Processing control commands: > tag -1 pending Bug #936173 [src:avahi] avahi: Python2 removal in sid/bullseye Added tag(s) pending. -- 936173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949638: tesseract: uses -march=native
Adrian, I am afraid that there is a misunderstanding. The code part which is compiled with -march=native is never executed by default. There is a command line option which allows users to select the code which is used for certain time critical calculations (dot product). A wrong choice is not a security problem but simply will crash the application, no matter whether the user selected "native", "avx" or "neon". That's quite common for other packages including the standard C library and scientific libraries, too. They all contain optimized functions which require certain hardware and which crash otherwise. Regards Stefan
Bug#961460: src:newsboat: build depends on librust-xdg-2-dev which doesn't exist (anymore)
Hi Nikos, On 24-05-2020 21:17, Nikos Tsipinakis wrote: > I'm confused here, I just did a test build in a fresh unstable chroot and it > seems like newsboat builds just fine. Oops, sorry. > librust-xdg-2-dev is provided by librust-xdg[1]. Is this a false positive of > some build script? Or perhaps the rebuild was run in testing rather than > unstable (librust-xdg hasn't migrated yet). Yes, that. I look regularly at https://qa.debian.org/dose/debcheck/src_testing_main/ as we (the release team) require packages to be buildable in testing (we have some tolerance as the migration of build dependencies isn't guaranteed when checking if a package may migrate). Please help the rust maintainers such that that package can migrate. Paul signature.asc Description: OpenPGP digital signature
Processed: reassign 949638 to src:tesseract
Processing commands for cont...@bugs.debian.org: > reassign 949638 src:tesseract 4.1.0-2 Bug #949638 [src:tesseract] tesseract: uses -march=native Ignoring request to reassign bug #949638 to the same package Bug #949638 [src:tesseract] tesseract: uses -march=native Marked as found in versions tesseract/4.1.0-2; no longer marked as found in versions tesseract/4.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 949638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 949638 to src:tesseract
Processing commands for cont...@bugs.debian.org: > reassign 949638 src:tesseract 4.1.0-1 Bug #949638 [tesseract] tesseract: uses -march=native Bug reassigned from package 'tesseract' to 'src:tesseract'. No longer marked as found in versions 4.1.0-1. Ignoring request to alter fixed versions of bug #949638 to the same values previously set Bug #949638 [src:tesseract] tesseract: uses -march=native Marked as found in versions tesseract/4.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 949638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#949638: tesseract: uses -march=native
Processing control commands: > severity -1 serious Bug #949638 [tesseract] tesseract: uses -march=native Severity set to 'serious' from 'normal' -- 949638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961399: marked as done (seaview: autopkgtest regression: gzip: *.gz: No such file or directory)
Your message dated Sun, 24 May 2020 19:48:30 + with message-id and subject line Bug#961399: fixed in seaview 1:5.0.2-2 has caused the Debian Bug report #961399, regarding seaview: autopkgtest regression: gzip: *.gz: No such file or 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.) -- 961399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seaview Version: 1:5.0.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of seaview the autopkgtest of seaview fails in testing when that autopkgtest is run with the binary packages of seaview from unstable. It passes when run with only packages from testing. In tabular form: passfail seaviewfrom testing1:5.0.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=seaview https://ci.debian.net/data/autopkgtest/testing/amd64/s/seaview/5615737/log.gz autopkgtest [12:08:25]: test run-unit-test: [--- gzip: *.gz: No such file or directory autopkgtest [12:08:25]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: seaview Source-Version: 1:5.0.2-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of seaview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated seaview 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: Sun, 24 May 2020 21:21:17 +0200 Source: seaview Architecture: source Version: 1:5.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 961399 Changes: seaview (1:5.0.2-2) unstable; urgency=medium . * Team upload. . [ Andreas Tille ] * Fix autopkgtest Closes: #961399 . [ Nilesh Patra ] * Use xvfb to run autopkgtests Checksums-Sha1: 7839aef3060ff18018b210e20e4644de6f7e2cb2 2107 seaview_5.0.2-2.dsc 544ce2f7d5884de327550ce39d87cc7ec6b24dd7 16416 seaview_5.0.2-2.debian.tar.xz 4aa5890f936b60f4645b8fcb387897196b948fd1 7917 seaview_5.0.2-2_amd64.buildinfo Checksums-Sha256: 0465f46565fb97817bfe4232aa6c4554392b97ff98ee6ea1e38fdd76f2f1c604 2107 seaview_5.0.2-2.dsc 369b2d8deb7a61060effc93617f48ed014b57901183041f79d1a177bbc6cfc6a 16416 seaview_5.0.2-2.debian.tar.xz 6fdaeadcbc4b7fec7878be687273293187d14c64c3828eb36853759921c126f7 7917 seaview_5.0.2-2_amd64.buildinfo Files: c14e27e0900f958f52ee47f5840f9cb8 2107 science optional seaview_5.0.2-2.dsc cc33604cf7f8a99be83a6907741800ab 16416 science optional seaview_5.0.2-2.debian.tar.xz 2ac697ddf509d0c3a0eda25601363389 7917 science optional seaview_5.0.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7KyxwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGLlQ/9FZpFBkug4l0Od6GETnJHRR+ZeDD2o6Lb 2GzU2F48n3+13kP2eH+BkACuW6Ji3sUem6k8QoJgbtjEoXst4WvP3zvug95Sm5E+ f1kE8SnWATL4++Pn9b8P5QOtEomlwVe+OisEd6js5+lGfCI+3BakG02bhdnikJGB hGMd4JclLMOQszpnyKPSdJfUCPuGp8sWAVC/Ckzr1YWOhxNqAVQiVyyc60nrVZOw TDkmVlE6wg6YR3Y8xvKG/mP72LaDoJYNPOozkxAj2x40rLNyiJBlCr5WZvR4uPyV TIwkg00Xha5Ybx0mvYKTrfT/E4sYquRfq6z72T7+xu+EJLyuJUJ1HS3WC5ca1d4x C6X7m1ka/6RwOLKv28spK6ToC/oIE5EWJXzFCi0YNIQBe/o29mHqZ1weOZVakZsy 6wKm/Yhccj8mMCt3x6xEEwaZHzZoDi4bBRRIzWfkLJuVKeaqM8oAe2nWPmTN4X9A vMv44MGowNoFg8c8+qSKRsyculDD/VpjtpXqbKrANiHQF4jH8wnmfH8x9e0kGXOV CoStOyB1Zv1zGE/g5kxD41FpveX6n3tOkDk/IJIkdFOxqO7ZwaTAJRR0Hw6w6dLg
Bug#961399: seaview: autopkgtest regression: gzip: *.gz: No such file or directory
On Sun, May 24, 2020 at 09:18:01PM +0530, Nilesh Patra wrote: > I tried implementing this, and modifying the tests in a way that made sense > to me. > Could you please have a look at this, and let me know if this is OK? Works for me - thus uploaded. Thanks a lot for your contribution Andreas. -- http://fam-tille.de
Bug#961460: src:newsboat: build depends on librust-xdg-2-dev which doesn't exist (anymore)
Hi, I'm confused here, I just did a test build in a fresh unstable chroot and it seems like newsboat builds just fine. librust-xdg-2-dev is provided by librust-xdg[1]. Is this a false positive of some build script? Or perhaps the rebuild was run in testing rather than unstable (librust-xdg hasn't migrated yet). [1] https://tracker.debian.org/media/packages/r/rust-xdg/control-2.2.0-2 - Nikos On 24/05, Paul Gevers wrote: > Source: newsboat > Version: 2.19-1 > Severity: serious > User: trei...@debian.org > Usertags: -1 edos-uninstallable > > Dear maintainer(s), > > Your package Build-Depends on librust-xdg-2-dev but that package isn't > available in Debian (anymore). You should probably Build-Depends on > librust-xdg-dev instead. > > Paul >
Processed: forcibly merging 959236 959075
Processing commands for cont...@bugs.debian.org: > forcemerge 959236 959075 Bug #959236 [ifenslave] Bringing up a bond results in an infinite loop Bug #959075 [ifenslave] ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command Severity set to 'grave' from 'normal' Marked as found in versions ifenslave/2.10. Merged 959075 959236 > thanks Stopping processing here. Please contact me if you need assistance. -- 959075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075 959236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Hi Paul, On 24 May 2020 at 20:31, Paul Gevers wrote: | Hi Dirk, | | On 24-05-2020 20:19, Dirk Eddelbuettel wrote: | > Hm. Easy to implement but won't it create a permanent 'fail' on that platform? | > (But then maybe that is the goal once I ask the release team to drop the old | > binary...) | | That's exactly what I meant. What did you think I meant? I was mostly thinking out loud chewing over how it can be seen as outright "sabotage" on the architecture ensuring success of a build. So it reflected my surprise. Nothing more. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#961460: src:newsboat: build depends on librust-xdg-2-dev which doesn't exist (anymore)
Source: newsboat Version: 2.19-1 Severity: serious User: trei...@debian.org Usertags: -1 edos-uninstallable Dear maintainer(s), Your package Build-Depends on librust-xdg-2-dev but that package isn't available in Debian (anymore). You should probably Build-Depends on librust-xdg-dev instead. Paul signature.asc Description: OpenPGP digital signature
Bug#961457: idle3-tools: autopkgtest regression: idle3ctl: command not found
Source: idle3-tools Version: 0.9.1-4 X-Debbugs-CC: debian...@lists.debian.org, leandrora...@debxp.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of idle3-tools the autopkgtest of idle3-tools fails in testing when that autopkgtest is run with the binary packages of idle3-tools from unstable. It passes when run with only packages from testing. In tabular form: passfail idle3-toolsfrom testing0.9.1-4 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that either you need the needs-root restriction or need to provide the full path to /usr/sbin/idle3ctl. Without needs-root, the test is run as a regular user. Please also mark this test as superficial. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=idle3-tools https://ci.debian.net/data/autopkgtest/testing/amd64/i/idle3-tools/5507695/log.gz autopkgtest [03:18:58]: test command1: idle3ctl -V | grep idle autopkgtest [03:18:58]: test command1: [--- bash: idle3ctl: command not found autopkgtest [03:18:58]: test command1: ---] signature.asc Description: OpenPGP digital signature
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Hi Dirk, On 24-05-2020 20:19, Dirk Eddelbuettel wrote: > Hm. Easy to implement but won't it create a permanent 'fail' on that platform? > (But then maybe that is the goal once I ask the release team to drop the old > binary...) That's exactly what I meant. What did you think I meant? Paul signature.asc Description: OpenPGP digital signature
Bug#961456: pwget: autopkgtest regression: Can't locate LWP/UserAgent.pm in @INC
Source: pwget Version: 2016.1019+git75c6e3e-3 X-Debbugs-CC: debian...@lists.debian.org, elimar.henri...@yahoo.com.br Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pwget the autopkgtest of pwget fails in testing when that autopkgtest is run with the binary packages of pwget from unstable. It passes when run with only packages from testing. In tabular form: passfail pwget from testing2016.1019+git75c6e3e-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Seems like you are missing a (test) dependency? Please also mark this test as superficial. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pwget https://ci.debian.net/data/autopkgtest/testing/amd64/p/pwget/5507726/log.gz autopkgtest [03:27:21]: test command2: pwget -h autopkgtest [03:27:21]: test command2: [--- Can't locate LWP/UserAgent.pm in @INC (you may need to install the LWP::UserAgent module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/bin/pwget line 87. BEGIN failed--compilation aborted at /usr/bin/pwget line 87. autopkgtest [03:27:21]: test command2: ---] signature.asc Description: OpenPGP digital signature
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Hi Paul, On 24 May 2020 at 19:54, Paul Gevers wrote: | Hi Dirk, | | On 24-05-2020 19:09, Dirk Eddelbuettel wrote: | > But how I prevent the build in the future? | > | > Via 'Architecture: any [!xyx]' ? Last I checked I though we had no such | > explicit white/black listing mechanisms (but then I may have forgotten...) | | I also don't think blacklisting exists. I just checked policy and it Right. | doesn't mention anything like it. Instead of listing all archs except | for mipsel, I would just check the architecture in debian/rules and exit | non-zero if the architecture is mipsel. Hm. Easy to implement but won't it create a permanent 'fail' on that platform? (But then maybe that is the goal once I ask the release team to drop the old binary...) Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#961455: ngetty: autopkgtest regression: ngetty-helper: command not found
Source: ngetty Version: 1.1-5 X-Debbugs-CC: debian...@lists.debian.org, guilherme@gmail.com Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ngetty the autopkgtest of ngetty fails in testing when that autopkgtest is run with the binary packages of ngetty from unstable. It passes when run with only packages from testing. In tabular form: passfail getty from testing1.1-5 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that either you need the needs-root restriction or need to provide the full path to /sbin/ngetty-helper. Without needs-root, the test is run as a regular user. Please also mark this test as superficial. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ngetty https://ci.debian.net/data/autopkgtest/testing/amd64/n/ngetty/5502710/log.gz autopkgtest [21:50:06]: test command1: ngetty-helper --version | grep version autopkgtest [21:50:06]: test command1: [--- bash: ngetty-helper: command not found autopkgtest [21:50:07]: test command1: ---] signature.asc Description: OpenPGP digital signature
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Hi Dirk, On 24-05-2020 19:09, Dirk Eddelbuettel wrote: > But how I prevent the build in the future? > > Via 'Architecture: any [!xyx]' ? Last I checked I though we had no such > explicit white/black listing mechanisms (but then I may have forgotten...) I also don't think blacklisting exists. I just checked policy and it doesn't mention anything like it. Instead of listing all archs except for mipsel, I would just check the architecture in debian/rules and exit non-zero if the architecture is mipsel. Paul signature.asc Description: OpenPGP digital signature
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
On 24 May 2020 at 18:47, Paul Gevers wrote: | Hi Dirk, | | On 24-05-2020 13:43, Dirk Eddelbuettel wrote: | > This used to build. It just takes a long as it is a library with old-school | > many templates "big C++". | > | > There is nothing I can do here. If it ends being removed because nobody can | > change the build toggle on that platform so be it. | > | > I understand the concern and agree with it. But there is nothing I think I | > can do. | | There is. If you think you can't reliably fix the issue, you can ask the | ftp-masters to remove the mipsel binary. Once the mipsel binary is gone, | the package can migrate. Please make sure that the binary isn't build by | accident in the future in that case. I can happily do either. But how I prevent the build in the future? Via 'Architecture: any [!xyx]' ? Last I checked I though we had no such explicit white/black listing mechanisms (but then I may have forgotten...) Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#944211: marked as done (id-utils: FTBFS on all 32-bit archs)
Your message dated Sun, 24 May 2020 17:05:02 + with message-id and subject line Bug#944211: fixed in id-utils 4.6.28-20200521ss15dab has caused the Debian Bug report #944211, regarding id-utils: FTBFS on all 32-bit archs 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.) -- 944211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: id-utils Version: 4.6.21+20171216ss6cdfd-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Hi Bradley, The latest upstream version of id-utils has been stuck in unstable for over 200 days, because it has regressed its buildability on 32-bit architectures: [...] CC walker.o walker.c:1139:20: error: conflicting types for 'dev_ino_hash_1' DEV_INO_HASH_DEFUN(dev_ino_hash_1, xform_NOP) ^~ walker.c:1116:1: note: in definition of macro 'DEV_INO_HASH_DEFUN' FN_NAME (void const *x) \ ^~~ walker.c:77:22: note: previous declaration of 'dev_ino_hash_1' was here static unsigned long dev_ino_hash_1 (void const *key); ^~ [...] (https://buildd.debian.org/status/fetch.php?pkg=id-utils=armhf=4.6.21%2B20171216ss6cdfd-1=1549776380=0) If upstream is taking the position that this package should no longer be built on 32-bit archs, you should ask the ftp team to remove the old binaries on these architectures. Otherwise, you have a serious build regression in this version of the package. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: id-utils Source-Version: 4.6.28-20200521ss15dab Done: b...@debian.org (Bradley A. Bosch) We believe that the bug you reported is fixed in the latest version of id-utils, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bradley A. Bosch (supplier of updated id-utils 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, 23 May 2020 10:00:36 -0500 Source: id-utils Binary: id-utils id-utils-dbgsym Architecture: source amd64 Version: 4.6.28-20200521ss15dab Distribution: unstable Urgency: medium Maintainer: Bradley A. Bosch Changed-By: Bradley A. Bosch Description: id-utils - Fast, high-capacity, identifier database tool Closes: 933108 944211 Changes: id-utils (4.6.28-20200521ss15dab) unstable; urgency=medium . * New upstream snapshot from git://git.savannah.gnu.org/idutils.git 15dabf93d63ec15e674bd049c839067e58ffb872 * Tested 32 bit builds (Closes: #944211) * More verbose build by default (Closes: #933108) Checksums-Sha1: 86a90ed4062487234374531612184ccd41c15d7f 1748 id-utils_4.6.28-20200521ss15dab.dsc e8ef11583abc964af6eab6cb1e742ad12bdf7dd4 1278924 id-utils_4.6.28.orig.tar.xz 89113b3bb7fc07f1975e4ce11e720c4a02193e5c 8080 id-utils_4.6.28-20200521ss15dab.debian.tar.xz 11ca747cb0bffa88f54699a5f8bd54d629d4d4fa 868652 id-utils-dbgsym_4.6.28-20200521ss15dab_amd64.deb 9caf3a113b7b698a4e0dcc8cf301f2f91d40f83c 6190 id-utils_4.6.28-20200521ss15dab_amd64.buildinfo 0b4155d4fe911207b2bd298f9de35205025b4d55 223040 id-utils_4.6.28-20200521ss15dab_amd64.deb Checksums-Sha256: 3a4808e08b3b78e14fa48fabeeb910ec5ab590c95e827802fa1acd8b34a51c9e 1748 id-utils_4.6.28-20200521ss15dab.dsc 0485731e5522799f4868be9357b92f8f3c1b292000ed27cae61fe6db35a7b428 1278924 id-utils_4.6.28.orig.tar.xz 0f6f922d12909cc6e39b6a4a4eaacf49ccbc4ac5f18eda66065b00b714913dc4 8080 id-utils_4.6.28-20200521ss15dab.debian.tar.xz 3d35da2c7fbf1b452324b12a0a7938af5f4fdbae20081a7e662571015c66ecef 868652 id-utils-dbgsym_4.6.28-20200521ss15dab_amd64.deb c64e03c3e15cb3f2e860a07265eca5699b2e3b865593fb75687af1cf377611c9 6190 id-utils_4.6.28-20200521ss15dab_amd64.buildinfo
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Hi Dirk, On 24-05-2020 13:43, Dirk Eddelbuettel wrote: > This used to build. It just takes a long as it is a library with old-school > many templates "big C++". > > There is nothing I can do here. If it ends being removed because nobody can > change the build toggle on that platform so be it. > > I understand the concern and agree with it. But there is nothing I think I > can do. There is. If you think you can't reliably fix the issue, you can ask the ftp-masters to remove the mipsel binary. Once the mipsel binary is gone, the package can migrate. Please make sure that the binary isn't build by accident in the future in that case. Paul signature.asc Description: OpenPGP digital signature
Bug#961448: r-cran-learnbayes: autopkgtest failure
Source: r-cran-learnbayes Version: 2.15.1-3 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-learnbayes/5625650/log.gz ... autopkgtest [08:07:53]: test run-unit-test: [--- gzip: *.gz: No such file or directory autopkgtest [08:07:53]: test run-unit-test: ---] autopkgtest [08:07:53]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1 Examples are no longer compressed with dh compat 12.
Bug#961351: r-cran-bms: autopkgtest failure
On Sat, May 23, 2020 at 04:13:55PM +0200, Sebastian Ramacher wrote: > Source: r-cran-bms > Version: 0.3.4-5 > Severity: serious > > The autopkgtest of r-cran-bms fails in unstable: > | autopkgtest [07:20:33]: test run-unit-test: [--- > | gzip: *.gz: No such file or directory > | autopkgtest [07:20:33]: test run-unit-test: ---] > | autopkgtest [07:20:33]: test run-unit-test: - - - - - - - - - - results - > - - - - - - - - - > | run-unit-testFAIL non-zero exit status 1 >... Examples are no longer compressed with dh compat 12. cu Adrian
Bug#961446: r-cran-nozzle.r1 lost dependencies on libjs-jquery, libjs-jquery-tablesorter
Package: r-cran-nozzle.r1 Version: 1.1-1+dfsg-3 Severity: serious Control: affects -1 src:r-cran-nozzle.r1 https://salsa.debian.org/r-pkg-team/r-cran-nozzle.r1/-/commit/7d7b872597ffa83f453db4d3b43c0e66d49bd479 This is also the root cause of the autopkgtest failure: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-nozzle.r1/5625651/log.gz
Processed: r-cran-nozzle.r1 lost dependencies on libjs-jquery, libjs-jquery-tablesorter
Processing control commands: > affects -1 src:r-cran-nozzle.r1 Bug #961446 [r-cran-nozzle.r1] r-cran-nozzle.r1 lost dependencies on libjs-jquery, libjs-jquery-tablesorter Added indication that 961446 affects src:r-cran-nozzle.r1 -- 961446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960354: marked as done (ytcc: Failed to migrate to testing for too long)
Your message dated Sun, 24 May 2020 16:19:00 + with message-id and subject line Bug#960354: fixed in ytcc 1.8.1-1.1 has caused the Debian Bug report #960354, regarding ytcc: Failed to migrate to testing for too long 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.) -- 960354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ytcc Version: 1.8.1-1 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: fre...@debian.org fre...@linux.vnet.ibm.com Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug. Your package src:ytcc in its current version in unstable has been trying to migrate for 273 days. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. Currently your package only needs another source-only upload to be able to migrate to Testing; please refer to https://wiki.debian.org/SourceOnlyUpload to see how to make a source-only upload. Regards, Boyuan Yang [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: ytcc Source-Version: 1.8.1-1.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of ytcc, 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. Boyuan Yang (supplier of updated ytcc 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, 17 May 2020 23:31:49 +0800 Source: ytcc Architecture: source Version: 1.8.1-1.1 Distribution: unstable Urgency: medium Maintainer: Frédéric Bonnard Changed-By: Boyuan Yang Closes: 960354 Changes: ytcc (1.8.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Source-only upload to allow testing migration. (Closes: #960354) Checksums-Sha1: aff3305e7b04d41cbebcae5e0a650f15d52f0f2a 1910 ytcc_1.8.1-1.1.dsc 953e38de57a94e1ea6d5100548ee133b0ae0a1cc 1864 ytcc_1.8.1-1.1.debian.tar.xz 019ecbe42d039b389756d41450c112c4d90f38af 6117 ytcc_1.8.1-1.1_amd64.buildinfo Checksums-Sha256: 91d0ae692c9335bb6ab4c79ab33d6075052736d10d6322e4475a2e3d80a2d484 1910 ytcc_1.8.1-1.1.dsc f45c7e09521efd04ade7906d4e716230e950bd54d7d08df96ca8795596686427 1864 ytcc_1.8.1-1.1.debian.tar.xz 9565364576b6dffd57e4db86ffbeb833ee765d8c1909438bbe9055668f1f0f7f 6117 ytcc_1.8.1-1.1_amd64.buildinfo Files: d4ad448405f0864f4fe45f8219ea1540 1910 python optional ytcc_1.8.1-1.1.dsc 35c9fc32e8ada615d8193d2e49b3504a 1864 python optional ytcc_1.8.1-1.1.debian.tar.xz 2d37682383c53316d89dbb0b63af7512 6117 python optional ytcc_1.8.1-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl7BWbIACgkQwpPntGGC Ws7XbBAAnHXNUyRXMvUMMLeomp1YYpekF6gP+qPxJbW99TimxgnQRGZf3JT0CbpH WjukqyFW9l1Bw0UWMU6QrzIA/NbSuItJKP+kS07TelVR8MkszsM9mdfTJ7bVX9HL 5RshcLc+TXB93s0CrnlUW+1RjhSin/tBgMLC+AjALkRoCuLzrbgzluTa44PDnA/e NiQgaKSLryQOhx06owjTHC4fjXHhJ7CDqNcPehHZZKxoVGqzFnVL+loPXjkEnA8h Lvzc566XkR4SSiO/MKaFPv43ACi+0iaZQeb55HxYemdNNAKTN0B1VEC+AYoM3Sek +uOI/D5AwwqCK++AFBy00EkURqzH/OrLUr6dzdLEBig/eGX12pSR5Zt2XLBgoYRT 9EcLutaZPO3nvP9PJahPD5TyygRa7BeLxHiX5CZk/dz6Xkop+v9sBApfzo4JvTDV K4N18m3QIujp6dV/hC7nemLmGTNNJfwtjEOrQWgfePcSGRa8his9Uwm+xrTNIoTZ A1yiSJHIPtv4HY2Kj5W3G0dOZ+5DTE+CecWHEizWSi1wJpuoMtL5SJm4qpD9yYbq e8pIVwn58rJbK32K2q7LL5Yvppu+ixJeG2HDbD5CCrzeHu2VXHZDfz+bPGl7T3iO RC7GpwlfdTRmQG0Sq6IhSUkOQDUDezi6peoZHuLuWp+yUMNaYKQ= =YI/B -END PGP
Bug#961445: grcompiler FTBFS on big endian
Source: grcompiler Version: 5.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=grcompiler=sid ... 1/15 Test #1: compile_SchTest .***Failed0.06 sec Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. Revised by SIL International for Graphite Description Language, May 24 2020 Graphite Compiler Version 5.2 [release build] Copyright (c) 2002-2020, by SIL International. All rights reserved. Reading input font... GDL file: /<>/test/GrcRegressionTest/fonts/SchMain.gdl PreProcessor: /<>/obj-s390x-linux-gnu/preprocessor/gdlpp Input TT file: /<>/test/GrcRegressionTest/fonts/SchInput.ttf Output TT file: SchTest.ttf Output font name: unknown (unchanged) Silf table version requested: 4.0 Parsing file /<>/test/GrcRegressionTest/fonts/SchMain.gdl... Parsing failed. 2 errors have been output to /<>/obj-s390x-linux-gnu/test/GrcRegressionTest/SchTest.gdlerr.txt. ... debian-s390 is Cc'ed.
Bug#961444: grcompiler FTBFS on architectures where char is unsigned
Source: grcompiler Version: 5.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=grcompiler=sid ... 7/15 Test #13: compile_PadaukTest_v3 ...Child aborted***Exception: 0.20 sec Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. Revised by SIL International for Graphite Description Language, May 24 2020 grcompiler: /<>/compiler/GdlExpression.cpp:3259: virtual void GdlSlotRefExpression::GenerateEngineCode(int, std::vector&, int, std::vector*, int, bool, int, int*): Assertion `(int)bOffset == nOffset' failed. ... The build passes if I rewrite the line above the assert to signed char bOffset = (signed char)nOffset; but someone who knows the code better should check what is actually the correct fix.
Bug#961399: seaview: autopkgtest regression: gzip: *.gz: No such file or directory
On Sun, 24 May 2020, 19:06 Andreas Tille, wrote: > On Sun, May 24, 2020 at 08:02:56AM +0200, Paul Gevers wrote: > > gzip: *.gz: No such file or directory > > I've fixed this one but the test has changed and seems to require a > running X server. Either this can be changed via command line options > or by using xvfb-run to provide some X server. > That's a nice idea indeed! I tried implementing this, and modifying the tests in a way that made sense to me. Could you please have a look at this, and let me know if this is OK? Kind regards Nilesh >
Bug#961438: grcompiler FTBFS on i386: compare_PigLatinTest_v2 failed
Source: grcompiler Version: 5.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=grcompiler=i386=5.2-1=1590331683=0 ... Start 9: compare_PigLatinTest_v2 4/15 Test #9: compare_PigLatinTest_v2 .***Failed0.01 sec Files "PigLatinTest_v2.ttf" to "/<>/test/GrcRegressionTest/fonts/PigLatinBenchmark_v2.ttf" are different. ... 93% tests passed, 1 tests failed out of 15 Total Test time (real) = 3.91 sec The following tests FAILED: 9 - compare_PigLatinTest_v2 (Failed) Errors while running CTest make[1]: *** [Makefile:121: test] Error 8 Something corrupts "RegTestV2-Regular" to "ReTesstV2Regullar": @@ -1413,9 +1413,9 @@ Offset: 670 00 50 00 69 00 67 00 4c 00 61 > .P.i.g.L.a 00 74 00 69 00 6e 00 47 00 72 > .t.i.n.G.r -00 52 00 65 00 67 00 54 00 65 > .R.e.g.T.e -00 73 00 74 00 56 00 32 00 2d > .s.t.V.2.- -00 52 00 65 00 67 00 75 00 6c > .R.e.g.u.l +00 52 00 65 00 54 00 65 00 73 > .R.e.T.e.s +00 73 00 74 00 56 00 32 00 52 > .s.t.V.2.R +00 65 00 67 00 75 00 6c 00 6c > .e.g.u.l.l 00 61 00 72> .a.r Name table 7. PlatformID: 0 EncodingID: 0 @@ -1512,8 +1512,8 @@ Length: 27 Offset: 1059 50 69 67 4c 61 74 69 6e 47 72 > PigLatinGr -52 65 67 54 65 73 74 56 32 2d > RegTestV2- -52 65 67 75 6c 61 72 > Regular +52 65 54 65 73 73 74 56 32 52 > ReTesstV2R +65 67 75 6c 6c 61 72 > egullar Name table 16. PlatformID: 1 EncodingID: 0 LanguageID: 0 @@ -1643,9 +1643,9 @@ Offset: 1756 00 50 00 69 00 67 00 4c 00 61 > .P.i.g.L.a 00 74 00 69 00 6e 00 47 00 72 > .t.i.n.G.r -00 52 00 65 00 67 00 54 00 65 > .R.e.g.T.e -00 73 00 74 00 56 00 32 00 2d > .s.t.V.2.- -00 52 00 65 00 67 00 75 00 6c > .R.e.g.u.l +00 52 00 65 00 54 00 65 00 73 > .R.e.T.e.s +00 73 00 74 00 56 00 32 00 52 > .s.t.V.2.R +00 65 00 67 00 75 00 6c 00 6c > .e.g.u.l.l 00 61 00 72> .a.r Name table 25. PlatformID: 3 EncodingID: 1
Bug#953537: unable to open '/sbin/xfsdump.dpkg-new': No such file or directory
Sorry for badly formatted last message. Webmail messed things up. I get this error trying to upgrade package: dpkg: error processing archive /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb (--unpack): unable to open '/sbin/xfsdump.dpkg-new': No such file or directory ~# ls -l /bin /sbin lrwxrwxrwx 1 root root 7 lis 30 2018 /bin -> usr/bin lrwxrwxrwx 1 root root 8 lis 30 2018 /sbin -> usr/sbin ~# readlink /bin /sbin usr/bin usr/sbin ~# LANGUAGE="en" LANG="en_US.UTF-8" apt-cache policy usrmerge usrmerge: Installed: (none) Candidate: 23 Version table: 23 502 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main amd64 Packages 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main i386 Packages ~# LANGUAGE="en" LANG="en_US.UTF-8" apt-cache policy xfsdump xfsdump: Installed: 3.1.6+nmu2+b2 Candidate: 3.1.9 Version table: 3.1.9 502 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main amd64 Packages *** 3.1.6+nmu2+b2 100 100 /var/lib/dpkg/status ~# LANGUAGE="en" LANG="en_US.UTF-8" apt-get --reinstall install xfsdump Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: acl attr quota The following packages will be upgraded: xfsdump 1 upgraded, 0 newly installed, 0 to remove and 196 not upgraded. Need to get 0 B/254 kB of archives. After this operation, 19.5 kB of additional disk space will be used. Retrieving bug reports... Done Parsing Found/Fixed information... Done grave bugs of xfsdump (3.1.6+nmu2+b2 → 3.1.9) b1 - #953537 - xfsdump_3.1.9: Fails to install with usrmerge Summary: xfsdump(1 bug) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y (Reading database ... 164656 files and directories currently installed.) Preparing to unpack .../xfsdump_3.1.9_amd64.deb ... Unpacking xfsdump (3.1.9) over (3.1.6+nmu2+b2) ... dpkg: error processing archive /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb (--unpack): unable to open '/sbin/xfsdump.dpkg-new': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
Bug#953537: unable to open '/sbin/xfsdump.dpkg-new': No such file or directory
I am getting this error trying to upgrade packagedpkg: error processing archive /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb (--unpack):unable to open '/sbin/xfsdump.dpkg-new': No such file or directory~# ls -l /bin /sbinlrwxrwxrwx 1 root root 7 lis 30 2018 /bin - usr/binlrwxrwxrwx 1 root root 8 lis 30 2018 /sbin - usr/sbin~# readlink /bin /sbinusr/binusr/sbin~# LANGUAGE="en" LANG="en_US.UTF-8" apt-cache policy usrmergeusrmerge: Installed: (none) Candidate: 23 Version table: 23 502 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main amd64 Packages 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main i386 Packages~# LANGUAGE="en" LANG="en_US.UTF-8" apt-cache policy xfsdumpxfsdump: Installed: 3.1.6+nmu2+b2 Candidate: 3.1.9 Version table: 3.1.9 502 502 http://ftp.icm.edu.pl/pub/Linux/debian sid/main amd64 Packages*** 3.1.6+nmu2+b2 100 100 /var/lib/dpkg/status~# LANGUAGE="en" LANG="en_US.UTF-8" apt-get --reinstall install xfsdumpReading package lists... DoneBuilding dependency tree Reading state information... DoneSuggested packages: acl attr quotaThe following packages will be upgraded: xfsdump1 upgraded, 0 newly installed, 0 to remove and 196 not upgraded.Need to get 0 B/254 kB of archives.After this operation, 19.5 kB of additional disk space will be used.Retrieving bug reports... DoneParsing Found/Fixed information... Donegrave bugs of xfsdump (3.1.6+nmu2+b2 → 3.1.9) Outstandingb1 - #953537 - xfsdump_3.1.9: Fails to install with usrmergeSummary:xfsdump(1 bug)Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y(Reading database ... 164656 files and directories currently installed.)Preparing to unpack .../xfsdump_3.1.9_amd64.deb ...Unpacking xfsdump (3.1.9) over (3.1.6+nmu2+b2) ...dpkg: error processing archive /var/cache/apt/archives/xfsdump_3.1.9_amd64.deb (--unpack):unable to open '/sbin/xfsdump.dpkg-new': No such file or directoryErrors were encountered while processing:/var/cache/apt/archives/xfsdump_3.1.9_amd64.debE: Sub-process /usr/bin/dpkg returned an error code (1)
Bug#887534: plume-creator FTBFS with libquazip5-headers 0.7.3-3
I will try to package 0.67 [ https://plume-creator.eu/download/ ] Greetings, Miry El dom., 24 may. 2020 a las 15:11, Miriam Ruiz () escribió: > > Thanks. > > I'm sorry not to have been very responsive these days, for personal reasons. > > Greetings, > Miry > > El sáb., 23 may. 2020 a las 22:54, Adrian Bunk () escribió: > > > > On Sat, May 23, 2020 at 08:08:44PM +0100, Sudip Mukherjee wrote: > > > On Sat, May 23, 2020 at 07:51:52PM +0300, Adrian Bunk wrote: > > > > Control: tags 960678 moreinfo > > > > Control: tags 887534 - patch > > > > > > > > On Fri, Apr 24, 2020 at 08:31:31PM +0100, Sudip Mukherjee wrote: > > > > > This error is not reproducible any more > > > > >... > > > > > > > > It is still there, both for me locally and in reproducible: > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/plume-creator.html > > > > > > Thats odd. It was not there when I made the last package. > > > > > > Anyways, I have now uploaded new package to mentors. And attached the new > > > diff. > > > > Thanks, uploaded to DELAYED/2. > > > > > Regards > > > Sudip > > > > cu > > Adrian
Bug#961350: marked as done (r-bioc-delayedarray: autopkgtest failure)
Your message dated Sun, 24 May 2020 13:48:40 +
with message-id
and subject line Bug#961350: fixed in r-bioc-delayedarray 0.14.0+dfsg-2
has caused the Debian Bug report #961350,
regarding r-bioc-delayedarray: autopkgtest failure
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.)
--
961350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-delayedarray
Version: 0.14.0+dfsg-1
Severity: serious
The autopkgtests of r-bioc-delayedarray fail in unstable:
| RUNIT TEST PROTOCOL -- Fri May 22 19:11:59 2020
| ***
| Number of test functions: 42
| Number of errors: 1
| Number of failures: 0
|
|
| 1 Test Suite :
| DelayedArray RUnit Tests - 42 test functions, 1 error, 0 failures
| ERROR in test_DelayedMatrix_mult: Error in .super_BLOCK_mult(x, y, MULT =
`%*%`) :
| Couldn't load the BiocParallel package. Please install the BiocParallel
| package and try again.
|
| Test files with failing tests
|
|test_DelayedMatrix-utils.R
| test_DelayedMatrix_mult
|
|
| Error in BiocGenerics:::testPackage("DelayedArray") :
| unit tests failed for package DelayedArray
| Execution halted
| autopkgtest [19:12:00]: test bioc: ---]
| autopkgtest [19:12:00]: test bioc: - - - - - - - - - - results - - - - - - -
- - -
| bioc FAIL non-zero exit status 1
See
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-delayedarray/5607603/log.gz
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-bioc-delayedarray
Source-Version: 0.14.0+dfsg-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?=
We believe that the bug you reported is fixed in the latest version of
r-bioc-delayedarray, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 961...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dylan Aïssi (supplier of updated r-bioc-delayedarray
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, 24 May 2020 15:21:50 +0200
Source: r-bioc-delayedarray
Architecture: source
Version: 0.14.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Dylan Aïssi
Closes: 961350
Changes:
r-bioc-delayedarray (0.14.0+dfsg-2) unstable; urgency=medium
.
* Add r-bioc-biocparallel to test-deps (Closes: #961350)
Checksums-Sha1:
b87a562a54d1143c51740bfb940ea98ceb7a4619 2364
r-bioc-delayedarray_0.14.0+dfsg-2.dsc
9025c4f1f6da3caaf2a8754d03cd72ce00ebf3fd 4248
r-bioc-delayedarray_0.14.0+dfsg-2.debian.tar.xz
b94102dcf9416ad7190c694923f7ccc0f1cc1770 9052
r-bioc-delayedarray_0.14.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
5f5a98328ed79c6d9cf424ecefd0f534bd43f5f8db99c3511526dcda7049b717 2364
r-bioc-delayedarray_0.14.0+dfsg-2.dsc
23283d38e85ac909e62a65da4974e2be317d900eabe51f170a6c0eebf287a6fa 4248
r-bioc-delayedarray_0.14.0+dfsg-2.debian.tar.xz
13c3e0cd6fb476ee9c6ec08d4b53eb0258bb2a234926c2778218f1195f96cf18 9052
r-bioc-delayedarray_0.14.0+dfsg-2_amd64.buildinfo
Files:
c76582ef6c7009e8539cb2eb987a1949 2364 gnu-r optional
r-bioc-delayedarray_0.14.0+dfsg-2.dsc
a639102e0cbabbff118ee1cea4b25c70 4248 gnu-r optional
r-bioc-delayedarray_0.14.0+dfsg-2.debian.tar.xz
d26f6b2c5b789deec7548dbc2c1708d9 9052 gnu-r optional
r-bioc-delayedarray_0.14.0+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl7KeNwACgkQYS7xYT4F
D1TQAA//UDVK9bheNB+GmlIaSAW0hOsWk6bbep0YvRPslWCFAOKqehtZNlhLUeNj
SwdfhoO1e2Q93vqba+YO9Tj7+5+YkW4OKmAIc5O6/2zqbOG3mxTrNOUwNa1gZD1+
xS8g14LmQDwMsvP5gb98B0bSZzbbY7GB/92mwOWBf8WInqy9XX/UklkhJs+tuT2e
Q/uqQZU2Ui7KByEXN0WwHtO7BBKV4OUaM2GxpxCYAXJvM25WDPHb3r8LKnJ4EBmW
bH0FRhJg4p1FEn2Kj2HNE8UQJnI1ulsVL9qX4/WScZHxHBvldmcAZsZQdlLAfFyp
Kf+ApBMKcdITeZo6ul5qvpzxMfmsNC9SJs5R7kYiuwo6VZDi5bJ+i4AZBiIhIjUR
xHg/8LW1kY6t2mkNKTFCErLjyFFyDMlF+y5bSwR0oRG3c/a+kSl8vcZXEgiDzzES
heTmW6hUaaFejGC/r3rmJqJgvdv1OahFmFfY21btXRPrCZOCsZEV6+uOvvRHoGii
9NDryE1CJfiWfhBRQH+Rz8zuXX1I3Sy+F4OwsfzTqjlsxMl3qWiBZuYfsugotVdR
Bug#961399: seaview: autopkgtest regression: gzip: *.gz: No such file or directory
On Sun, May 24, 2020 at 08:02:56AM +0200, Paul Gevers wrote: > gzip: *.gz: No such file or directory I've fixed this one but the test has changed and seems to require a running X server. Either this can be changed via command line options or by using xvfb-run to provide some X server. Kind regards Andreas. -- http://fam-tille.de
Bug#887534: plume-creator FTBFS with libquazip5-headers 0.7.3-3
Thanks. I'm sorry not to have been very responsive these days, for personal reasons. Greetings, Miry El sáb., 23 may. 2020 a las 22:54, Adrian Bunk () escribió: > > On Sat, May 23, 2020 at 08:08:44PM +0100, Sudip Mukherjee wrote: > > On Sat, May 23, 2020 at 07:51:52PM +0300, Adrian Bunk wrote: > > > Control: tags 960678 moreinfo > > > Control: tags 887534 - patch > > > > > > On Fri, Apr 24, 2020 at 08:31:31PM +0100, Sudip Mukherjee wrote: > > > > This error is not reproducible any more > > > >... > > > > > > It is still there, both for me locally and in reproducible: > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/plume-creator.html > > > > Thats odd. It was not there when I made the last package. > > > > Anyways, I have now uploaded new package to mentors. And attached the new > > diff. > > Thanks, uploaded to DELAYED/2. > > > Regards > > Sudip > > cu > Adrian
Bug#961421: libpod: CVE-2020-1726
Source: libpod Version: 1.6.4+dfsg1-2 Severity: grave Tags: security upstream Forwarded: https://github.com/containers/libpod/pull/5168 Hi, The following vulnerability was published for libpod. CVE-2020-1726[0]: | A flaw was discovered in Podman where it incorrectly allows containers | when created to overwrite existing files in volumes, even if they are | mounted as read-only. When a user runs a malicious container or a | container based on a malicious image with an attached volume that is | used for the first time, it is possible to trigger the flaw and | overwrite files in the volume.This issue was introduced in version | 1.6.0. 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-1726 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1726 [1] https://github.com/containers/libpod/pull/5168 [2] https://github.com/containers/libpod/commit/c140ecdc9b416ab4efd4d21d14acd63b6adbdd42 Regards, Salvatore
Bug#961419: r-cran-sjlabelled: autopkgtest failure
Source: r-cran-sjlabelled
Version: 1.1.4-1
Severity: serious
r-cran-haven was demoted from Depends to Suggests,
which broke the autopkgtest:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-sjlabelled/5618427/log.gz
...
> library(testthat)
> library(sjlabelled)
>
> test_check("sjlabelled")
── 1. Error: remove_labels (@test-remove_labels.R#6) ──
Package 'haven' required for this function. Please install it.
Backtrace:
1. sjlabelled::remove_labels(z, labels = 2)
2. sjlabelled:::remove_labels_helper(.dat, labels)
4. sjlabelled:::get_na.default(x)
5. sjlabelled:::get_na_helper(x, as.tag)
══ testthat results ═══
[ OK: 8 | SKIPPED: 0 | WARNINGS: 0 | FAILED: 1 ]
...
Processed: More duplicates
Processing commands for cont...@bugs.debian.org: > reassign 961352 r-cran-fontliberation 0.1.0+dfsg-3 Bug #961352 [src:r-cran-cowplot] r-cran-cowplot: autopkgtest failure Bug reassigned from package 'src:r-cran-cowplot' to 'r-cran-fontliberation'. No longer marked as found in versions r-cran-cowplot/1.0.0+dfsg-3. Ignoring request to alter fixed versions of bug #961352 to the same values previously set Bug #961352 [r-cran-fontliberation] r-cran-cowplot: autopkgtest failure Marked as found in versions r-cran-fontliberation/0.1.0+dfsg-3. > forcemerge 961360 961352 Bug #961360 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961403 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961404 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961352 [r-cran-fontliberation] r-cran-cowplot: autopkgtest failure Added indication that 961352 affects src:r-cran-freetypeharfbuzz,src:r-cran-fontquiver,src:r-cran-vdiffr Added tag(s) sid and bullseye. Bug #961404 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Removed indication that 961404 affects src:r-cran-vdiffr, src:r-cran-fontquiver, and src:r-cran-freetypeharfbuzz Added indication that 961404 affects src:r-cran-freetypeharfbuzz,src:r-cran-fontquiver,src:r-cran-vdiffr Removed indication that 961360 affects src:r-cran-vdiffr, src:r-cran-fontquiver, and src:r-cran-freetypeharfbuzz Added indication that 961360 affects src:r-cran-freetypeharfbuzz,src:r-cran-fontquiver,src:r-cran-vdiffr Removed indication that 961403 affects src:r-cran-fontquiver, src:r-cran-freetypeharfbuzz, and src:r-cran-vdiffr Added indication that 961403 affects src:r-cran-freetypeharfbuzz,src:r-cran-fontquiver,src:r-cran-vdiffr Bug #961403 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Merged 961352 961360 961403 961404 > retitle 961352 r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961352 [r-cran-fontliberation] r-cran-cowplot: autopkgtest failure Bug #961360 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961403 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961404 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Changed Bug title to 'r-cran-fontliberation: missing dependency on fonts-liberation2' from 'r-cran-cowplot: autopkgtest failure'. Ignoring request to change the title of bug#961360 to the same title Ignoring request to change the title of bug#961403 to the same title Ignoring request to change the title of bug#961404 to the same title > affects 961360 src:r-cran-ggridges src:r-cran-patchwork src:r-cran-proc > src:r-cran-cowplot src:r-cran-ggplot2 Bug #961360 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961352 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961403 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961404 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Added indication that 961360 affects src:r-cran-ggridges, src:r-cran-patchwork, src:r-cran-proc, src:r-cran-cowplot, and src:r-cran-ggplot2 Added indication that 961352 affects src:r-cran-ggridges, src:r-cran-patchwork, src:r-cran-proc, src:r-cran-cowplot, and src:r-cran-ggplot2 Added indication that 961403 affects src:r-cran-ggridges, src:r-cran-patchwork, src:r-cran-proc, src:r-cran-cowplot, and src:r-cran-ggplot2 Added indication that 961404 affects src:r-cran-ggridges, src:r-cran-patchwork, src:r-cran-proc, src:r-cran-cowplot, and src:r-cran-ggplot2 > thanks Stopping processing here. Please contact me if you need assistance. -- 961352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961352 961360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961360 961403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961403 961404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#961403: r-cran-freetypeharfbuzz: autopkgtest needs update
Processing control commands: > reassign -1 r-cran-fontliberation 0.1.0+dfsg-3 Bug #961403 [src:r-cran-freetypeharfbuzz] r-cran-freetypeharfbuzz: autopkgtest needs update Bug reassigned from package 'src:r-cran-freetypeharfbuzz' to 'r-cran-fontliberation'. No longer marked as found in versions r-cran-freetypeharfbuzz/0.2.5+dfsg-2. Ignoring request to alter fixed versions of bug #961403 to the same values previously set Bug #961403 [r-cran-fontliberation] r-cran-freetypeharfbuzz: autopkgtest needs update Marked as found in versions r-cran-fontliberation/0.1.0+dfsg-3. > reassign 961360 r-cran-fontliberation 0.1.0+dfsg-3 Bug #961360 [src:r-cran-fontquiver] r-cran-fontquiver: autopkgtest failure Bug reassigned from package 'src:r-cran-fontquiver' to 'r-cran-fontliberation'. No longer marked as found in versions r-cran-fontquiver/0.2.1-3. Ignoring request to alter fixed versions of bug #961360 to the same values previously set Bug #961360 [r-cran-fontliberation] r-cran-fontquiver: autopkgtest failure Marked as found in versions r-cran-fontliberation/0.1.0+dfsg-3. > reassign 961404 r-cran-fontliberation 0.1.0+dfsg-3 Bug #961404 [src:r-cran-vdiffr] r-cran-vdiffr: autopkgtest needs update Bug reassigned from package 'src:r-cran-vdiffr' to 'r-cran-fontliberation'. No longer marked as found in versions r-cran-vdiffr/0.3.1+dfsg-3. Ignoring request to alter fixed versions of bug #961404 to the same values previously set Bug #961404 [r-cran-fontliberation] r-cran-vdiffr: autopkgtest needs update Marked as found in versions r-cran-fontliberation/0.1.0+dfsg-3. > forcemerge -1 961360 961404 Bug #961403 [r-cran-fontliberation] r-cran-freetypeharfbuzz: autopkgtest needs update Bug #961360 [r-cran-fontliberation] r-cran-fontquiver: autopkgtest failure Added tag(s) sid and bullseye. Bug #961404 [r-cran-fontliberation] r-cran-vdiffr: autopkgtest needs update Merged 961360 961403 961404 > retitle -1 r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961403 [r-cran-fontliberation] r-cran-freetypeharfbuzz: autopkgtest needs update Bug #961360 [r-cran-fontliberation] r-cran-fontquiver: autopkgtest failure Bug #961404 [r-cran-fontliberation] r-cran-vdiffr: autopkgtest needs update Changed Bug title to 'r-cran-fontliberation: missing dependency on fonts-liberation2' from 'r-cran-freetypeharfbuzz: autopkgtest needs update'. Changed Bug title to 'r-cran-fontliberation: missing dependency on fonts-liberation2' from 'r-cran-fontquiver: autopkgtest failure'. Changed Bug title to 'r-cran-fontliberation: missing dependency on fonts-liberation2' from 'r-cran-vdiffr: autopkgtest needs update'. > affects -1 src:r-cran-freetypeharfbuzz src:r-cran-fontquiver src:r-cran-vdiffr Bug #961403 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961360 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Bug #961404 [r-cran-fontliberation] r-cran-fontliberation: missing dependency on fonts-liberation2 Added indication that 961403 affects src:r-cran-freetypeharfbuzz, src:r-cran-fontquiver, and src:r-cran-vdiffr Added indication that 961360 affects src:r-cran-freetypeharfbuzz, src:r-cran-fontquiver, and src:r-cran-vdiffr Added indication that 961404 affects src:r-cran-freetypeharfbuzz, src:r-cran-fontquiver, and src:r-cran-vdiffr -- 961360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961360 961403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961403 961404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961403: r-cran-freetypeharfbuzz: autopkgtest needs update
Control: reassign -1 r-cran-fontliberation 0.1.0+dfsg-3 Control: reassign 961360 r-cran-fontliberation 0.1.0+dfsg-3 Control: reassign 961404 r-cran-fontliberation 0.1.0+dfsg-3 Control: forcemerge -1 961360 961404 Control: retitle -1 r-cran-fontliberation: missing dependency on fonts-liberation2 Control: affects -1 src:r-cran-freetypeharfbuzz src:r-cran-fontquiver src:r-cran-vdiffr On Sun, May 24, 2020 at 10:40:44AM +0200, Graham Inggs wrote: >... > The autopkgtests of r-cran-freetypeharfbuzz currently fail [1], > preventing the migration of r-base. > This seems to coincide with the upload of r-cran-fontquiver/0.2.1-2. >... No, the bug is that r-cran-fontliberation ships plenty of broken symlinks after it lost the fonts-liberation2 dependency in https://salsa.debian.org/r-pkg-team/r-cran-fontliberation/-/commit/952ff2238ad81e9da18899dcd871ecc5454dd0c8 > Regards > Graham cu Adrian
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
On 24 May 2020 at 07:57, Paul Gevers wrote: | Source: quantlib-swig | Version: 1.17-1 | Severity: serious | Control: close -1 1.18-1 | Tags: sid bullseye | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | As recently announced [1], the Release Team now considers packages that | are out-of-sync between testing and unstable for more than 60 days as | having a Release Critical bug in testing. Your package src:quantlib-swig | in its current version in unstable has been trying to migrate for 60 | days [2]. Hence, I am filing this bug. | | If a package is out of sync between unstable and testing for a longer | period, this usually means that bugs in the package in testing cannot be | fixed via unstable. Additionally, blocked packages can have impact on | other packages, which makes preparing for the release more difficult. | Finally, it often exposes issues with the package and/or | its (reverse-)dependencies. We expect maintainers to fix issues that | hamper the migration of their package in a timely manner. | | This bug will trigger auto-removal when appropriate. As with all new | bugs, there will be at least 30 days before the package is auto-removed. | | I have immediately closed this bug with the version in unstable, so if | that version or a later version migrates, this bug will no longer affect | testing. I have also tagged this bug to only affect sid and bullseye, so | it doesn't affect (old-)stable. | | If you believe your package is unable to migrate to testing due to | issues beyond your control, don't hesitate to contact the Release Team. It is. See the build logs: virtual memory exhausted: Cannot allocate memory error: command 'g++' failed with exit status 1 make: *** [debian/rules:101: build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 This used to build. It just takes a long as it is a library with old-school many templates "big C++". There is nothing I can do here. If it ends being removed because nobody can change the build toggle on that platform so be it. I understand the concern and agree with it. But there is nothing I think I can do. Dirk | Paul | | [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html | [2] https://qa.debian.org/excuses.php?package=quantlib-swig | | | [DELETED ATTACHMENT signature.asc, application/pgp-signature] -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#961415: symfony: CVE-2020-5275 CVE-2020-5274 CVE-2020-5255
Source: symfony Version: 4.4.4-1 Severity: grave Tags: security upstream Hi, The following vulnerabilities were published for symfony. CVE-2020-5275[0]: | In symfony/security-http before versions 4.4.7 and 5.0.7, when a | `Firewall` checks access control rule, it iterate overs each rule's | attributes and stops as soon as the accessDecisionManager decides to | grant access on the attribute, preventing the check of next attributes | that should have been take into account in an unanimous strategy. The | accessDecisionManager is now called with all attributes at once, | allowing the unanimous strategy being applied on each attribute. This | issue is patched in versions 4.4.7 and 5.0.7. CVE-2020-5274[1]: | In Symfony before versions 5.0.5 and 4.4.5, some properties of the | Exception were not properly escaped when the `ErrorHandler` rendered | it stacktrace. In addition, the stacktrace were displayed even in a | non-debug configuration. The ErrorHandler now escape alls properties | of the exception, and the stacktrace is only display in debug | configuration. This issue is patched in symfony/http-foundation | versions 4.4.5 and 5.0.5 CVE-2020-5255[2]: | In Symfony before versions 4.4.7 and 5.0.7, when a `Response` does not | contain a `Content-Type` header, affected versions of Symfony can | fallback to the format defined in the `Accept` header of the request, | leading to a possible mismatch between the response#39;s content | and `Content-Type` header. When the response is cached, this can | prevent the use of the website by other users. This has been patched | in versions 4.4.7 and 5.0.7. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-5275 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5275 [1] https://security-tracker.debian.org/tracker/CVE-2020-5274 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5274 [2] https://security-tracker.debian.org/tracker/CVE-2020-5255 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5255 Regards, Salvatore
Bug#936981: fixed in mailnag 2.0.0-0.1
Hello, I pushed another NMU diff -Nru mailnag-2.0.0/debian/changelog mailnag-2.0.0/debian/changelog --- mailnag-2.0.0/debian/changelog 2020-05-09 10:31:35.0 +0200 +++ mailnag-2.0.0/debian/changelog 2020-05-24 13:08:09.0 +0200 @@ -1,3 +1,12 @@ +mailnag (2.0.0-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fixup previous upload by exporting PYBUILD_NAME and depending on +python3-all (patch taken from Ubuntu, Sebastien Bacher +) LP: #1874275 + + -- Gianfranco Costamagna Sun, 24 May 2020 13:08:09 +0200 + mailnag (2.0.0-0.1) unstable; urgency=medium * Non-maintainer upload diff -Nru mailnag-2.0.0/debian/control mailnag-2.0.0/debian/control --- mailnag-2.0.0/debian/control2020-05-09 10:31:35.0 +0200 +++ mailnag-2.0.0/debian/control2020-05-24 13:07:57.0 +0200 @@ -2,7 +2,7 @@ Section: mail Priority: optional Maintainer: Vincent Cheng -Build-Depends: debhelper-compat (= 12), dh-python, gettext, python3, python3-dbus, python3-xdg +Build-Depends: debhelper-compat (= 12), dh-python, gettext, python3-all, python3-dbus, python3-xdg Standards-Version: 3.9.8 Homepage: https://github.com/pulb/mailnag Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/mailnag/trunk diff -Nru mailnag-2.0.0/debian/rules mailnag-2.0.0/debian/rules --- mailnag-2.0.0/debian/rules 2020-05-09 10:31:35.0 +0200 +++ mailnag-2.0.0/debian/rules 2020-05-24 13:08:07.0 +0200 @@ -1,5 +1,7 @@ #!/usr/bin/make -f +export PYBUILD_NAME=Mailnag + %: dh $@ --with python3 --buildsystem=pybuild
Bug#932779: marked as done (lirc: Fails to install due to missing /etc/lirc/lirc_options.conf)
Your message dated Sun, 24 May 2020 10:48:42 + with message-id and subject line Bug#932779: fixed in lirc 0.10.1-6.2 has caused the Debian Bug report #932779, regarding lirc: Fails to install due to missing /etc/lirc/lirc_options.conf 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.) -- 932779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lirc Version: 0.10.1-5.2 Severity: grave Justification: renders package unusable Control: found -1 0.10.1-6 The versions of lirc in both buster and testing/unstable do not install cleanly and are left in a half configured state. This appears to be due to the file /etc/lirc/lirc_options.conf being missing. Copying /etc/lirc/lirc_options.conf.dist to /etc/lirc/lirc_options.conf allows the package to finish installing successfully. root@debian-vm:~# apt install lirc Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libicu57 libperl5.24 rename sgml-base tcpd xml-core Use 'apt autoremove' to remove them. The following additional packages will be installed: gir1.2-glib-2.0 libasound2 libasound2-data libftdi1-2 libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libjack-jackd2-0 liblirc-client0 liblirc0 libopus0 libportaudio2 libpython3.7 libsamplerate0 python3-gi python3-yaml shared-mime-info xdg-user-dirs Suggested packages: libasound2-plugins alsa-utils jackd2 opus-tools lirc-compat-remotes lirc-drv-irman lirc-doc lirc-x setserial ir-keytable Recommended packages: gir1.2-vte The following NEW packages will be installed: gir1.2-glib-2.0 libasound2 libasound2-data libftdi1-2 libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libjack-jackd2-0 liblirc-client0 liblirc0 libopus0 libportaudio2 libpython3.7 libsamplerate0 lirc python3-gi python3-yaml shared-mime-info xdg-user-dirs 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. Need to get 7,891 kB of archives. After this operation, 33.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.us.debian.org/debian buster/main amd64 libglib2.0-0 amd64 2.58.3-2 [1,259 kB] Get:2 http://ftp.us.debian.org/debian buster/main amd64 libgirepository-1.0-1 amd64 1.58.3-2 [92.8 kB] Get:3 http://ftp.us.debian.org/debian buster/main amd64 gir1.2-glib-2.0 amd64 1.58.3-2 [143 kB] Get:4 http://ftp.us.debian.org/debian buster/main amd64 libasound2-data all 1.1.8-1 [59.6 kB] Get:5 http://ftp.us.debian.org/debian buster/main amd64 libasound2 amd64 1.1.8-1 [361 kB] Get:6 http://ftp.us.debian.org/debian buster/main amd64 libftdi1-2 amd64 1.4-1+b2 [30.2 kB] Get:7 http://ftp.us.debian.org/debian buster/main amd64 libglib2.0-data all 2.58.3-2 [1,109 kB] Get:8 http://ftp.us.debian.org/debian buster/main amd64 libopus0 amd64 1.3-1 [191 kB] Get:9 http://ftp.us.debian.org/debian buster/main amd64 libsamplerate0 amd64 0.1.9-2 [949 kB] Get:10 http://ftp.us.debian.org/debian buster/main amd64 libjack-jackd2-0 amd64 1.9.12~dfsg-2 [299 kB] Get:11 http://ftp.us.debian.org/debian buster/main amd64 liblirc-client0 amd64 0.10.1-5.2 [70.6 kB] Get:12 http://ftp.us.debian.org/debian buster/main amd64 liblirc0 amd64 0.10.1-5.2 [131 kB] Get:13 http://ftp.us.debian.org/debian buster/main amd64 libportaudio2 amd64 19.6.0-1 [66.6 kB] Get:14 http://ftp.us.debian.org/debian buster/main amd64 libpython3.7 amd64 3.7.3-2 [1,498 kB] Get:15 http://ftp.us.debian.org/debian buster/main amd64 lirc amd64 0.10.1-5.2 [511 kB] Get:16 http://ftp.us.debian.org/debian buster/main amd64 python3-gi amd64 3.30.4-1 [180 kB] Get:17 http://ftp.us.debian.org/debian buster/main amd64 python3-yaml amd64 3.13-2 [121 kB] Get:18 http://ftp.us.debian.org/debian buster/main amd64 shared-mime-info amd64 1.10-1 [766 kB] Get:19 http://ftp.us.debian.org/debian buster/main amd64 xdg-user-dirs amd64 0.17-2 [53.8 kB] Fetched 7,891 kB in 3s (3,127 kB/s) Selecting previously unselected package libglib2.0-0:amd64. (Reading database ... 34382 files and directories currently installed.) Preparing to unpack .../00-libglib2.0-0_2.58.3-2_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.58.3-2) ... Selecting previously unselected package libgirepository-1.0-1:amd64. Preparing to unpack .../01-libgirepository-1.0-1_1.58.3-2_amd64.deb ... Unpacking libgirepository-1.0-1:amd64 (1.58.3-2) ... Selecting previously unselected package gir1.2-glib-2.0:amd64. Preparing to unpack .../02-gir1.2-glib-2.0_1.58.3-2_amd64.deb ... Unpacking
Bug#936981: marked as done (mailnag: Python2 removal in sid/bullseye)
Your message dated Sun, 24 May 2020 10:34:03 + with message-id and subject line Bug#936981: fixed in mailnag 2.0.0-0.1 has caused the Debian Bug report #936981, regarding mailnag: 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.) -- 936981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mailnag Version: 1.2.1-1.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:mailnag 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: mailnag Source-Version: 2.0.0-0.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of mailnag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated mailnag 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, 09 May 2020 10:31:35 +0200 Source: mailnag Binary: mailnag Architecture: source Version: 2.0.0-0.1 Distribution: unstable Urgency: medium Maintainer: Vincent Cheng Changed-By: Gianfranco Costamagna Description: mailnag- extensible mail notification daemon Closes: 936981 Changes: mailnag (2.0.0-0.1) unstable; urgency=medium . * Non-maintainer upload * New upstream release (Closes: #936981) - move to pybuild - move to python3 - move from gnome keyring to libsecret - bump compat level to 12 Checksums-Sha1: 669a385d80204e05ba89ad1ca1ff6522ed71120e 1920 mailnag_2.0.0-0.1.dsc 7b7dbc25044b87d23aece0566b273d5a4209f40e 175996 mailnag_2.0.0.orig.tar.gz f04b7ecb2ab716fac964b3c878b3bee9186f293e 5360 mailnag_2.0.0-0.1.debian.tar.xz ad4541a2cbec7864b27da61684aea17867f52367 7837 mailnag_2.0.0-0.1_source.buildinfo Checksums-Sha256: 1d415a920e2daabb829a04338c7e9dc3497adfce8c9722e4da984d7dacf9928b
Processed: unblock 936173 with 938645
Processing commands for cont...@bugs.debian.org: > # dependency was removed > unblock 936173 with 938645 Bug #936173 [src:avahi] avahi: Python2 removal in sid/bullseye 936173 was blocked by: 938645 936173 was blocking: 936371 937448 937695 938198 942941 943104 Removed blocking bug(s) of 936173: 938645 > thanks Stopping processing here. Please contact me if you need assistance. -- 936173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961383: marked as done (libxc builds with -march=native on most architectures)
Your message dated Sun, 24 May 2020 09:49:44 + with message-id and subject line Bug#961383: fixed in libxc 4.3.4-2 has caused the Debian Bug report #961383, regarding libxc builds with -march=native on most architectures 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.) -- 961383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxc Version: 4.2.3-3 Severity: serious libxc builds with -march=native on most architectures, this makes the code only run on hardware that is compatible with whatever buildd built the package. --- End Message --- --- Begin Message --- Source: libxc Source-Version: 4.3.4-2 Done: Michael Banck We believe that the bug you reported is fixed in the latest version of libxc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated libxc 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: Sun, 24 May 2020 11:37:23 +0200 Source: libxc Architecture: source Version: 4.3.4-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Michael Banck Closes: 961383 Changes: libxc (4.3.4-2) unstable; urgency=medium . * debian/rules (override_dh_auto_configure): Add -DENABLE_XHOST=OFF in order to trun off -march=native compiler flag (Closes: #961383). Checksums-Sha1: d6dbca1350999e7714e0d091e39fadfd5d9b95a4 1981 libxc_4.3.4-2.dsc e34769390c8182d3e90d2453fee30de8e7c689a3 11712 libxc_4.3.4-2.debian.tar.xz 81d7f55643f8bed77870abea4e9f43833c886f78 5956 libxc_4.3.4-2_source.buildinfo Checksums-Sha256: 07f93f972421b75ea4e0f0bd62b5b02b130904ecd7e31c8950eb3c0cf0224630 1981 libxc_4.3.4-2.dsc 20b2bbd2aa7e3dd6132330575f35eb8a25c3ddff91b2f1d780333a67a86c4779 11712 libxc_4.3.4-2.debian.tar.xz 1124a37c941b12786620e184c88bb2519b2ec68ff33eaea174debb6263f744be 5956 libxc_4.3.4-2_source.buildinfo Files: 72dd1dc9d0f29aaf6b2d4dd17e081ed6 1981 science optional libxc_4.3.4-2.dsc f1e259901be6d62e954ec8295cb9dfa6 11712 science optional libxc_4.3.4-2.debian.tar.xz d5e90652ba3e325d700093709944aa4a 5956 science optional libxc_4.3.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAl7KQGkACgkQ3GhqJ7Q0 gbDAzA//Vp4B6A02MJRYMDs/6u0NAcMsM6oUKRztQrv/b4H06ioOu64xv2tkNdkN XV4fVYQGSNSqHOoMCBOEYthr238zpoPYWKy3Ftk3WXOPR0vsG1iJvv5ZgwBI//qo m6MqBOzZU8ry83khhUzHyqbFae6d9BcFcIyKoe1jVidpF2IYWQXeWgZ/B97bjDrD HDNwa+na+HZHdFrwld9PvlhVoVyC4qK2RrsOSlipUuunMYgiC8gQTEh5k1T/RGXF anBOh8cm8HG/CZosJcMVBsli0C00xE/NrU9YybQWs1wpU3rSMCDCq4/kqb1pF3Ip ga0mGnqjAJYMjE+++unDkISp3jQlLEffUXBB0xlE1sIIR/aqbc3J3vYPj+dZ7r8w XANYxyaEWElFvcaIZlg8sf/UcnWQEyo7yrvxF4I3kKLmTpGr6ZpCVnKMZM9iaMum t0zW7y5rNYarH+gsr8l6K5ZQcH0GnabfMwEHCKFgxhmYKyaRzw/6Zz3S74Zn42E4 HYGnY8d/k6Cg/7A8qwmlpxfZnorXBqS82CDbpUz2mpDfUUgg7O5bazDW73yd5Fw7 +1J+HdSjY4m/wBZvp/y7nXfP4RAA4V1rFV2T3r19xjGfRp8pc7kTDGA+zI+g7M4V XIlnXhP6WDmSjoI00iag3Fu1qpObzGfmtKA7VTUz5k9/aU7W+bs= =5U/b -END PGP SIGNATURE End Message ---
Processed: Bug#961383 marked as pending in libxc
Processing control commands: > tag -1 pending Bug #961383 [src:libxc] libxc builds with -march=native on most architectures Added tag(s) pending. -- 961383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961383: marked as pending in libxc
Control: tag -1 pending Hello, Bug #961383 in libxc 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/debichem-team/libxc/-/commit/aec59c789d100e072bdceb2ab23aaf0bb87b912e * debian/rules (override_dh_auto_configure): Add -DENABLE_XHOST=OFF in order to trun off -march=native compiler flag (Closes: #961383). (this message was generated automatically) -- Greetings https://bugs.debian.org/961383
Bug#961408: r-cran-raster: autopkgtest regression
Source: r-cran-raster Version: 3.1-5-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 3.1-5-1, r-cran-raster has been failing its own autopkgtests [1]. This now prevents the migration of r-base. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-raster/unstable/amd64/ > library(testthat) Error in library(testthat) : there is no package called ‘testthat’ Execution halted autopkgtest [17:36:59]: test run-unit-test: ---] autopkgtest [17:36:59]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 1
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 955071 src:sphinx-celery
Bug #955071 [src:case] case: FTBFS with Sphinx 2.4: AttributeError: module
'sphinx.ext.autodoc' has no attribute 'AutoDirective'
Bug reassigned from package 'src:case' to 'src:sphinx-celery'.
No longer marked as found in versions case/1.5.3+dfsg-3.
Ignoring request to alter fixed versions of bug #955071 to the same values
previously set
> forcemerge 958983 955071
Bug #958983 {Done: Mattia Rizzolo } [src:sphinx-celery]
sphinx-celery: incompatible with sphinx 2+
Bug #955086 {Done: Mattia Rizzolo } [src:sphinx-celery]
vine: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc' has no
attribute 'AutoDirective'
Bug #955089 {Done: Mattia Rizzolo } [src:sphinx-celery]
kombu: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc' has
no attribute 'AutoDirective'
Bug #955090 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-django-celery-results: FTBFS with Sphinx 2.4: AttributeError: module
'sphinx.ext.autodoc' has no attribute 'AutoDirective'
Bug #955105 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-django-celery-beat: FTBFS with Sphinx 2.4: AttributeError: module
'sphinx.ext.autodoc' has no attribute 'AutoDirective'
Bug #955122 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-amqp: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc'
has no attribute 'AutoDirective'
Bug #955090 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-django-celery-results: FTBFS with Sphinx 2.4: AttributeError: module
'sphinx.ext.autodoc' has no attribute 'AutoDirective'
Removed indication that 955090 affects src:python-django-celery-beat,
src:kombu, src:python-amqp, src:vine, and src:python-django-celery-results
Added indication that 955090 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Removed indication that 955086 affects src:vine, src:python-amqp, src:kombu,
src:python-django-celery-beat, and src:python-django-celery-results
Added indication that 955086 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Removed indication that 955089 affects src:python-django-celery-results,
src:vine, src:python-amqp, src:python-django-celery-beat, and src:kombu
Added indication that 955089 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Removed indication that 955105 affects src:python-django-celery-results,
src:python-amqp, src:python-django-celery-beat, src:kombu, and src:vine
Added indication that 955105 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Removed indication that 955122 affects src:vine, src:python-amqp, src:kombu,
src:python-django-celery-beat, and src:python-django-celery-results
Added indication that 955122 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Removed indication that 958983 affects src:python-django-celery-results,
src:vine, src:kombu, src:python-django-celery-beat, and src:python-amqp
Added indication that 958983 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Bug #955071 [src:sphinx-celery] case: FTBFS with Sphinx 2.4: AttributeError:
module 'sphinx.ext.autodoc' has no attribute 'AutoDirective'
958986 was blocked by: 955105 955089 955090 958983 955086 955122
958986 was not blocking any bugs.
Added blocking bug(s) of 958986: 955071
Marked Bug as done
Owner recorded as Mattia Rizzolo .
Added indication that 955071 affects
src:vine,src:kombu,src:python-django-celery-results,src:python-amqp,src:python-django-celery-beat
Marked as fixed in versions sphinx-celery/2.0.0-1.
Marked as found in versions sphinx-celery/1.3.1-2.
Added tag(s) bullseye and sid.
Bug #955086 {Done: Mattia Rizzolo } [src:sphinx-celery]
vine: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc' has no
attribute 'AutoDirective'
Bug #955089 {Done: Mattia Rizzolo } [src:sphinx-celery]
kombu: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc' has
no attribute 'AutoDirective'
Bug #955105 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-django-celery-beat: FTBFS with Sphinx 2.4: AttributeError: module
'sphinx.ext.autodoc' has no attribute 'AutoDirective'
Bug #955122 {Done: Mattia Rizzolo } [src:sphinx-celery]
python-amqp: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc'
has no attribute 'AutoDirective'
Merged 955071 955086 955089 955090 955105 955122 958983
> affects 958983 src:case
Bug #958983 {Done: Mattia Rizzolo } [src:sphinx-celery]
sphinx-celery: incompatible with sphinx 2+
Bug #955071 {Done: Mattia Rizzolo } [src:sphinx-celery]
case: FTBFS with Sphinx 2.4: AttributeError: module 'sphinx.ext.autodoc' has no
attribute 'AutoDirective'
Bug #955086 {Done: Mattia Rizzolo } [src:sphinx-celery]
Bug#961405: r-cran-httpuv: autopkgtest needs update
Source: r-cran-httpuv
Version: 1.5.2+dfsg-1
Severity: serious
Tags: bullseye sid
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
The autopkgtests of r-cran-httpuv currently fail [1],preventing the
migration of r-base.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-httpuv/unstable/amd64/
> library(testthat)
> library(httpuv)
>
> test_check("httpuv")
-- 1. Error: Paths with non-ASCII characters (@test-static-paths.R#770) ---
unable to translate 'tests/testthat/apps/f' to native encoding
Backtrace:
1. base::dir.create(nonascii_path)
== testthat results ===
[ OK: 203 | SKIPPED: 9 | WARNINGS: 0 | FAILED: 1 ]
1. Error: Paths with non-ASCII characters (@test-static-paths.R#770)
Error: testthat unit tests failed
In addition: Warning message:
In parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8") :
unable to translate '/f' to native encoding
Execution halted
autopkgtest [15:08:15]: test run-unit-test: ---]
autopkgtest [15:08:15]: test run-unit-test: - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
Bug#961060: closing 672155, closing 866038, closing 961060, closing 672155, closing 866038, closing 961060
close 672155 1.06-6.2~deb10u1 close 866038 1.06-6.2~deb10u1 close 961060 1.06-6.2~deb10u1 close 672155 1.06-6.2~deb9u1 close 866038 1.06-6.2~deb9u1 close 961060 1.06-6.2~deb9u1 thanks
Processed: closing 672155, closing 866038, closing 961060, closing 672155, closing 866038, closing 961060
Processing commands for cont...@bugs.debian.org:
> close 672155 1.06-6.2~deb10u1
Bug #672155 {Done: Dmitry Bogatov } [qmail] qmail: unowned
files after purge (policy 6.8, 10.8)
Marked as fixed in versions netqmail/1.06-6.2~deb10u1.
Bug #672155 {Done: Dmitry Bogatov } [qmail] qmail: unowned
files after purge (policy 6.8, 10.8)
Bug 672155 is already marked as done; not doing anything.
> close 866038 1.06-6.2~deb10u1
Bug #866038 {Done: Dmitry Bogatov } [qmail] qmail: "The
hostname -f command returned: $1"
Marked as fixed in versions netqmail/1.06-6.2~deb10u1.
Bug #866038 {Done: Dmitry Bogatov } [qmail] qmail: "The
hostname -f command returned: $1"
Bug 866038 is already marked as done; not doing anything.
> close 961060 1.06-6.2~deb10u1
Bug #961060 {Done: Salvatore Bonaccorso } [src:netqmail]
qmail-verify: CVE-2020-3811 CVE-2020-3812
Marked as fixed in versions netqmail/1.06-6.2~deb10u1.
Bug #961060 {Done: Salvatore Bonaccorso } [src:netqmail]
qmail-verify: CVE-2020-3811 CVE-2020-3812
Bug 961060 is already marked as done; not doing anything.
> close 672155 1.06-6.2~deb9u1
Bug #672155 {Done: Dmitry Bogatov } [qmail] qmail: unowned
files after purge (policy 6.8, 10.8)
Marked as fixed in versions netqmail/1.06-6.2~deb9u1.
Bug #672155 {Done: Dmitry Bogatov } [qmail] qmail: unowned
files after purge (policy 6.8, 10.8)
Bug 672155 is already marked as done; not doing anything.
> close 866038 1.06-6.2~deb9u1
Bug #866038 {Done: Dmitry Bogatov } [qmail] qmail: "The
hostname -f command returned: $1"
Marked as fixed in versions netqmail/1.06-6.2~deb9u1.
Bug #866038 {Done: Dmitry Bogatov } [qmail] qmail: "The
hostname -f command returned: $1"
Bug 866038 is already marked as done; not doing anything.
> close 961060 1.06-6.2~deb9u1
Bug #961060 {Done: Salvatore Bonaccorso } [src:netqmail]
qmail-verify: CVE-2020-3811 CVE-2020-3812
Marked as fixed in versions netqmail/1.06-6.2~deb9u1.
Bug #961060 {Done: Salvatore Bonaccorso } [src:netqmail]
qmail-verify: CVE-2020-3811 CVE-2020-3812
Bug 961060 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
672155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672155
866038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866038
961060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#961404: r-cran-vdiffr: autopkgtest needs update
Source: r-cran-vdiffr
Version: 0.3.1+dfsg-3
Severity: serious
Tags: bullseye sid
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
The autopkgtests of r-cran-vdiffr currently fail [1], preventing the
migration of r-base.
This seems to coincide with the upload of r-cran-fontquiver/0.2.1-3.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-vdiffr/unstable/amd64/
> library("testthat")
> library("vdiffr")
> test_check("vdiffr")
While collecting testing cases:
Error: while collecting vdiffr cases. Last error:
* test: grid doppelgangers pass
* message: Internal error: cannot find fontLiberationSans-Regular.ttf
You can inspect this error with `vdiffr::last_collection_error()`
Execution halted
autopkgtest [16:54:33]: test run-unit-test: ---]
autopkgtest [16:54:33]: test run-unit-test: - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
Bug#961403: r-cran-freetypeharfbuzz: autopkgtest needs update
Source: r-cran-freetypeharfbuzz
Version: 0.2.5+dfsg-2
Severity: serious
Tags: bullseye sid
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
The autopkgtests of r-cran-freetypeharfbuzz currently fail [1],
preventing the migration of r-base.
This seems to coincide with the upload of r-cran-fontquiver/0.2.1-2.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-freetypeharfbuzz/unstable/amd64/
> library(testthat)
> library(freetypeharfbuzz)
>
> test_check("freetypeharfbuzz")
── 1. Error: width (@test-string-info.R#4)
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. testthat::expect_identical(rounded_width("foobar"), 34.0156)
4. freetypeharfbuzz:::rounded_width("foobar")
5. freetypeharfbuzz::str_width(text)
/tmp/autopkgtest-lxc.mhx9pi7p/downtmp/autopkgtest_tmp/helper-extents.R:3:2
6. fontquiver::font("Liberation", "sans", "regular")
7. fontset_props(fontset)$getter(variant, style)
8. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
9. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 2. Error: extents takes kerning into account (@test-string-info.R#10) ──
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. testthat::expect_identical(rounded_width("VA"), 15.1094)
4. freetypeharfbuzz:::rounded_width("VA")
5. freetypeharfbuzz::str_width(text)
/tmp/autopkgtest-lxc.mhx9pi7p/downtmp/autopkgtest_tmp/helper-extents.R:3:2
6. fontquiver::font("Liberation", "sans", "regular")
7. fontset_props(fontset)$getter(variant, style)
8. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
9. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 3. Failure: inputs are type-checked (@test-string-info.R#20) ───
`str_info("foo", font_size = "bar")` threw an error with unexpected message.
Expected match: "must be a length 1 numeric"
Actual message: "Internal error: cannot find fontLiberationSans-Regular.ttf"
Backtrace:
1. testthat::expect_error(str_info("foo", font_size = "bar"), "must
be a length 1 numeric")
6. freetypeharfbuzz::str_info("foo", font_size = "bar")
7. fontquiver::font("Liberation", "sans", "regular")
8. fontset_props(fontset)$getter(variant, style)
9. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
10. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 4. Failure: inputs are type-checked (@test-string-info.R#21) ───
`str_info("foo", font_size = 1:3)` threw an error with unexpected message.
Expected match: "must be a length 1 numeric"
Actual message: "Internal error: cannot find fontLiberationSans-Regular.ttf"
Backtrace:
1. testthat::expect_error(str_info("foo", font_size = 1:3), "must be
a length 1 numeric")
6. freetypeharfbuzz::str_info("foo", font_size = 1:3)
7. fontquiver::font("Liberation", "sans", "regular")
8. fontset_props(fontset)$getter(variant, style)
9. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
10. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 5. Error: can supply integer or double size (@test-string-info.R#25) ───
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. testthat::expect_identical(...)
4. freetypeharfbuzz::str_info("foo", 12)
5. fontquiver::font("Liberation", "sans", "regular")
6. fontset_props(fontset)$getter(variant, style)
7. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
8. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 6. Error: can retrieve typographical metrics (@test-string-info.R#29) ──
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. testthat::expect_identical(...)
4. freetypeharfbuzz::font_info(11)
5. fontquiver::font("Liberation", "sans", "regular")
6. fontset_props(fontset)$getter(variant, style)
7. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
8. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 7. Error: size is taken into account (@test-string-info.R#40) ──
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. freetypeharfbuzz::font_info(11)
2. fontquiver::font("Liberation", "sans", "regular")
3. fontset_props(fontset)$getter(variant, style)
4. fontquiver:::font_get("Liberation", variant, style, pkg = "fontLiberation")
5. fontquiver:::concat_font(std_name, base, "ttf", package = pkg)
── 8. Error: typographical height is monotonically increasing (@test-string-info
Internal error: cannot find fontLiberationSans-Regular.ttf
Backtrace:
1. base::vapply(1:50, function(size) sum(font_info(size)), double(1))
2. freetypeharfbuzz:::FUN(X[[i]], ...)
3. freetypeharfbuzz::font_info(size)
4. fontquiver::font("Liberation", "sans",
Bug#961402: xtl is built with -march=native on most release architectures
Source: xtl Version: 0.6.9-1 Severity: serious xtl is built with -march=native on most release architectures, this means the code will only run on hardware that is compatible with whatever buildd happens to build the package.
Processed: found 959675 in 1.26.0-2
Processing commands for cont...@bugs.debian.org: > found 959675 1.26.0-2 Bug #959675 [libgrpc++1] libgrpc++1: endless looping with default settings Marked as found in versions grpc/1.26.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 959675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961399: seaview: autopkgtest regression: gzip: *.gz: No such file or directory
Source: seaview Version: 1:5.0.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of seaview the autopkgtest of seaview fails in testing when that autopkgtest is run with the binary packages of seaview from unstable. It passes when run with only packages from testing. In tabular form: passfail seaviewfrom testing1:5.0.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=seaview https://ci.debian.net/data/autopkgtest/testing/amd64/s/seaview/5615737/log.gz autopkgtest [12:08:25]: test run-unit-test: [--- gzip: *.gz: No such file or directory autopkgtest [12:08:25]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature
Bug#961397: src:gcc-9-cross-ports: fails to migrate to testing for too long: not installable on arm64
Source: gcc-9-cross-ports Version: 16 Severity: serious Control: close -1 18 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:gcc-9-cross-ports in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gcc-9-cross-ports signature.asc Description: OpenPGP digital signature
Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Source: quantlib-swig Version: 1.17-1 Severity: serious Control: close -1 1.18-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:quantlib-swig in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=quantlib-swig signature.asc Description: OpenPGP digital signature
Processed: src:gcc-9-cross-ports: fails to migrate to testing for too long: not installable on arm64
Processing control commands: > close -1 18 Bug #961397 [src:gcc-9-cross-ports] src:gcc-9-cross-ports: fails to migrate to testing for too long: not installable on arm64 Marked as fixed in versions gcc-9-cross-ports/18. Bug #961397 [src:gcc-9-cross-ports] src:gcc-9-cross-ports: fails to migrate to testing for too long: not installable on arm64 Marked Bug as done -- 961397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel
Processing control commands: > close -1 1.18-1 Bug #961398 [src:quantlib-swig] src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel Marked as fixed in versions quantlib-swig/1.18-1. Bug #961398 [src:quantlib-swig] src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel Marked Bug as done -- 961398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
