Bug#951936: marked as done (egl-wayland: FTBFS: ../src/wayland-eglsurface.c:1521:10: error: ‘EGL_WAYLAND_Y_INVERTED_WL’ undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Tue, 07 Apr 2020 04:03:32 +
with message-id 
and subject line Bug#951936: fixed in egl-wayland 1:1.1.4-1
has caused the Debian Bug report #951936,
regarding egl-wayland: FTBFS: ../src/wayland-eglsurface.c:1521:10: error: 
‘EGL_WAYLAND_Y_INVERTED_WL’ undeclared (first use in this function)
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.)


-- 
951936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: egl-wayland
Version: 1:1.1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -Isrc/25a6634@@nvidia-egl-wayland@sha -Isrc -I../src -I../include 
> -I../wayland-egl -Iwayland-eglstream -I/usr/include/EGL 
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wall 
> -Werror -fvisibility=hidden -DWL_HIDE_DEPRECATED -Wno-pedantic -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglsurface.c.o' -MF 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglsurface.c.o.d' -o 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglsurface.c.o' -c 
> ../src/wayland-eglsurface.c
> ../src/wayland-eglsurface.c: In function ‘wlEglQueryNativeResourceHook’:
> ../src/wayland-eglsurface.c:1521:10: error: ‘EGL_WAYLAND_Y_INVERTED_WL’ 
> undeclared (first use in this function)
>  1521 | case EGL_WAYLAND_Y_INVERTED_WL:
>   |  ^
> ../src/wayland-eglsurface.c:1521:10: note: each undeclared identifier is 
> reported only once for each function it appears in
> [12/17] cc -Isrc/25a6634@@nvidia-egl-wayland@sha -Isrc -I../src -I../include 
> -I../wayland-egl -Iwayland-eglstream -I/usr/include/EGL 
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wall 
> -Werror -fvisibility=hidden -DWL_HIDE_DEPRECATED -Wno-pedantic -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglswap.c.o' -MF 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglswap.c.o.d' -o 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglswap.c.o' -c 
> ../src/wayland-eglswap.c
> [13/17] cc -Isrc/25a6634@@nvidia-egl-wayland@sha -Isrc -I../src -I../include 
> -I../wayland-egl -Iwayland-eglstream -I/usr/include/EGL 
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wall 
> -Werror -fvisibility=hidden -DWL_HIDE_DEPRECATED -Wno-pedantic -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@nvidia-egl-wayland@sha/wayland-egldisplay.c.o' -MF 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-egldisplay.c.o.d' -o 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-egldisplay.c.o' -c 
> ../src/wayland-egldisplay.c
> [14/17] cc -Isrc/25a6634@@nvidia-egl-wayland@sha -Isrc -I../src -I../include 
> -I../wayland-egl -Iwayland-eglstream -I/usr/include/EGL 
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wall 
> -Werror -fvisibility=hidden -DWL_HIDE_DEPRECATED -Wno-pedantic -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> -MQ 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglutils.c.o' -MF 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglutils.c.o.d' -o 
> 'src/25a6634@@nvidia-egl-wayland@sha/wayland-eglutils.c.o' -c 
> ../src/wayland-eglutils.c
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd build && LC_ALL=C.UTF-8 ninja -j4 -v returned exit 
> code 1
> make: *** [debian/rules:16: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/egl-wayland_1.1.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: egl-wayland
Source-Version: 1:1.1.4-1
Done: Timo Aaltonen 

We believe that the bug you reported 

Bug#956084: inetutils-telnetd: CVE-2020-10188

[Paul Szabo]

Package: inetutils-telnetd
Severity: critical
Tags: security
Justification: root security hole

Looking in https://security-tracker.debian.org/tracker/CVE-2020-10188 :

  utility.c in telnetd in netkit telnet through 0.17 allows remote
  attackers to execute arbitrary code via short writes or urgent data,
  because of a buffer overflow involving the netclear and nextitem
  functions.

Seems to me that inetutils contains the same (vulnerable) utility.c
functions. Please check.

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   www.maths.usyd.edu.au/u/psz
School of Mathematics and Statistics   University of SydneyAustralia

Bug#956083: autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups

[Martina Ferrari]

Package: autopostgresqlbackup
Version: 1.1-1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Due to a human error, today I had to resort to backups to recover data from a
PostgreSQL database. In the worst possible moment, I realised that ALL of the
backups we had of this database are useless.

Turns out that when dumping the database to a huge text file, the system was
running out of disk space, and so the file is truncated.

Instead of detecting the problem, aborting the backup, and sending an email to
the administrator, autopostgresqlbackup assumes the dump finished well,
proceeded to compress the truncated dump, and continued as if nothing had
happened. This had been going on for months without me realising, and so I have
no useful backup.

I am setting the severity as critical, because this bug has made me lose real
world data today.

The sad part is that the bug is pretty trivial to fix: all commands should be
checked for non-zero return codes, probably by setting the '-e' flag at the
beginning of the script.

I can't believe this has gone this long without anybody noticing, and how many
people might be trusting this tool for their backups. I'd say this deserves to
be fixed in stable too.

-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autopostgresqlbackup depends on:
ii  bsd-mailx [mailx] 8.1.2-0.20180807cvs-1
ii  postgresql-client-common  200+deb10u3

Versions of packages autopostgresqlbackup recommends:
pn  heirloom-mailx | biabam | mutt  
ii  openssl 1.1.1d-0+deb10u2

Versions of packages autopostgresqlbackup suggests:
ii  bzip2 1.0.6-9.2~deb10u1
ii  xz-utils  5.2.4-1

-- no debconf information

Bug#951936: egl-wayland: FTBFS: ../src/wayland-eglsurface.c:1521:10: error: ‘EGL_WAYLAND_Y_INVERTED_WL’ undeclared (first use in this function)

[Logan Rosen]

Package: egl-wayland
Version: 1:1.1.3-1
Followup-For: Bug #951936
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/missing-definitions.patch: Cherrypick upstream Git commit to add
missing definitions that used to be provided by mesa, fixing FTBFS.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru egl-wayland-1.1.3/debian/patches/add-missing-definitions.patch 
egl-wayland-1.1.3/debian/patches/add-missing-definitions.patch
--- egl-wayland-1.1.3/debian/patches/add-missing-definitions.patch  
1969-12-31 19:00:00.0 -0500
+++ egl-wayland-1.1.3/debian/patches/add-missing-definitions.patch  
2020-04-06 22:52:57.0 -0400
@@ -0,0 +1,56 @@
+From 4a343a4b563e84c6258efbddf1d910f9dd6e0300 Mon Sep 17 00:00:00 2001
+From: Erik Kurzinger 
+Date: Wed, 25 Mar 2020 08:38:09 -0700
+Subject: [PATCH] add EGL_WL_bind_wayland_display definitions to
+ wayland-egl-ext.h
+
+The definitions for the EGL_WL_bind_wayland_display extension were previously
+provided by eglmesaext.h, included through eglext.h. However, recent versions
+of the eglext.h header shipped with mesa (which most distributions use) no
+longer include platform headers. This causes the build to fail due to undefined
+symbols.
+
+This change adds the required definitions to wayland-egl-ext.h ensuring they're
+always available. This also avoids having a dependency on the aforementioned
+mesa header.
+
+Signed-off-by: Erik Kurzinger 
+---
+ wayland-egl/wayland-egl-ext.h | 24 
+ 1 file changed, 24 insertions(+)
+
+diff --git a/wayland-egl/wayland-egl-ext.h b/wayland-egl/wayland-egl-ext.h
+index 6688e45..a258bf4 100644
+--- a/wayland-egl/wayland-egl-ext.h
 b/wayland-egl/wayland-egl-ext.h
+@@ -23,6 +23,30 @@
+ #ifndef WAYLAND_EGL_EXT_H
+ #define WAYLAND_EGL_EXT_H
+ 
++#ifndef EGL_WL_bind_wayland_display
++#define EGL_WL_bind_wayland_display 1
++#define PFNEGLBINDWAYLANDDISPLAYWL PFNEGLBINDWAYLANDDISPLAYWLPROC
++#define PFNEGLUNBINDWAYLANDDISPLAYWL PFNEGLUNBINDWAYLANDDISPLAYWLPROC
++#define PFNEGLQUERYWAYLANDBUFFERWL PFNEGLQUERYWAYLANDBUFFERWLPROC
++struct wl_display;
++struct wl_resource;
++#define EGL_WAYLAND_BUFFER_WL 0x31D5
++#define EGL_WAYLAND_PLANE_WL  0x31D6
++#define EGL_TEXTURE_Y_U_V_WL  0x31D7
++#define EGL_TEXTURE_Y_UV_WL   0x31D8
++#define EGL_TEXTURE_Y_XUXV_WL 0x31D9
++#define EGL_TEXTURE_EXTERNAL_WL   0x31DA
++#define EGL_WAYLAND_Y_INVERTED_WL 0x31DB
++typedef EGLBoolean (EGLAPIENTRYP PFNEGLBINDWAYLANDDISPLAYWLPROC) (EGLDisplay 
dpy, struct wl_display *display);
++typedef EGLBoolean (EGLAPIENTRYP PFNEGLUNBINDWAYLANDDISPLAYWLPROC) 
(EGLDisplay dpy, struct wl_display *display);
++typedef EGLBoolean (EGLAPIENTRYP PFNEGLQUERYWAYLANDBUFFERWLPROC) (EGLDisplay 
dpy, struct wl_resource *buffer, EGLint attribute, EGLint *value);
++#ifdef EGL_EGLEXT_PROTOTYPES
++EGLAPI EGLBoolean EGLAPIENTRY eglBindWaylandDisplayWL (EGLDisplay dpy, struct 
wl_display *display);
++EGLAPI EGLBoolean EGLAPIENTRY eglUnbindWaylandDisplayWL (EGLDisplay dpy, 
struct wl_display *display);
++EGLAPI EGLBoolean EGLAPIENTRY eglQueryWaylandBufferWL (EGLDisplay dpy, struct 
wl_resource *buffer, EGLint attribute, EGLint *value);
++#endif
++#endif /* EGL_WL_bind_wayland_display */
++
+ #ifndef EGL_WL_wayland_eglstream
+ #define EGL_WL_wayland_eglstream 1
+ #define EGL_WAYLAND_EGLSTREAM_WL  0x334B
diff -Nru egl-wayland-1.1.3/debian/patches/series 
egl-wayland-1.1.3/debian/patches/series
--- egl-wayland-1.1.3/debian/patches/series 2019-07-08 07:46:16.0 
-0400
+++ egl-wayland-1.1.3/debian/patches/series 2020-04-06 22:53:09.0 
-0400
@@ -1 +1,2 @@
 fix-pkgconfig-target.diff
+add-missing-definitions.patch

Processed: Bug#956077 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #956077 [lintian] lintian: file-in-etc-not-marked-as-conffile shouldn't be 
reported for udebs?
Added tag(s) pending.

-- 
956077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956077: marked as pending in lintian

[Felix Lechner]

Control: tag -1 pending

Hello,

Bug #956077 in lintian 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/lintian/lintian/-/commit/c25bdfa12f5474d5dc0f3bbd37a9c6ba92899f52


Do not look for conffiles in udebs. (Closes: #956077)

Fixes a false positive for file-in-etc-not-marked-as-conffile in
udebs, which do not declare conffiles.

The bug was introduced in commit 9d30607e, when the scope of some
checks was expanded to eliminate check descriptions.

Sorry about the inconvenience.

The problem is already present in rootskel_1.132_amd64.udeb from the
archive (no *.changes file needed). With this commit, the offending
tag is gone:

$ frontend/lintian ../bugs/udeb/rootskel_1.132_amd64.udeb
I: rootskel udeb: hardening-no-fortify-functions sbin/get-real-console-linux
I: rootskel udeb: package-contains-empty-directory dev/
I: rootskel udeb: package-contains-empty-directory initrd/
I: rootskel udeb: package-contains-empty-directory media/
I: rootskel udeb: package-contains-empty-directory ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
P: rootskel udeb: executable-in-usr-lib usr/lib/finish-install.d/07rootskel

Thanks to Samuel Thibault for bringing this issue to our attention!


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/956077

Bug#903413: debbugs: FTBFS in buster/sid (dh_installdocs: Cannot find "UPGRADE")

[Logan Rosen]

Package: debbugs
Version: 2.6.0
Followup-For: Bug #903413
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/docs: Replace UPGRADE with UPGRADE.md to fix FTBFS.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru debbugs-2.6.0/debian/docs debbugs-2.6.0ubuntu1/debian/docs
--- debbugs-2.6.0/debian/docs   2018-01-04 14:01:02.0 -0500
+++ debbugs-2.6.0ubuntu1/debian/docs2020-04-06 22:36:07.0 -0400
@@ -1 +1 @@
-UPGRADE debian/README.mail
+UPGRADE.md debian/README.mail

Bug#954506: ttyrec: diff for NMU version 1.0.8-5.1

[NIIBE Yutaka]

Sudip Mukherjee  wrote:
> I've prepared an NMU for ttyrec (versioned as 1.0.8-5.1) and
> uploaded it to mentors for sponsoring. Please feel free to tell me if I
> should remove it.

Thank you for your work.

It is OK for Debian.

Ideally, it should not be Debian-only patch, so that upstream will
eventually be able to merge the fix.

When I will have time, I'll try that approach.
-- 

Bug#916049: cloop FTBFS with glibc 2.28

[Logan Rosen]

Package: cloop
Version: 3.14.1.2
Followup-For: Bug #916049
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * extract_compressed_fs.c: Define _DEFAULT_SOURCE to fix FTBFS with glibc
2.28+ due to loff_t only being defined when that macro is defined.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru cloop-3.14.1.2ubuntu2/extract_compressed_fs.c 
cloop-3.14.1.2ubuntu3/extract_compressed_fs.c
--- cloop-3.14.1.2ubuntu2/extract_compressed_fs.c   2015-05-03 
07:22:21.0 -0400
+++ cloop-3.14.1.2ubuntu3/extract_compressed_fs.c   2020-04-06 
22:15:51.0 -0400
@@ -4,6 +4,7 @@
 
 #define _LARGEFILE64_SOURCE
 #define _XOPEN_SOURCE 600
+#define _DEFAULT_SOURCE
 
 #include 
 #include 

Bug#952354: brebis: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module)

[Logan Rosen]

Package: brebis
Version: 0.10-1
Followup-For: Bug #952354
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on dh-python to fix FTBFS due to missing python3.pm.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru brebis-0.10/debian/control brebis-0.10/debian/control
--- brebis-0.10/debian/control  2015-07-21 23:31:22.0 -0400
+++ brebis-0.10/debian/control  2020-04-06 21:48:31.0 -0400
@@ -1,9 +1,9 @@
 Source: brebis
 Priority: optional
 Section: python
 Maintainer: Carl Chenet 
 Uploaders: Python Applications Packaging Team 

-Build-Depends: debhelper (>= 9), python3-all
+Build-Depends: debhelper (>= 9), python3-all, dh-python
 X-Python3-Version: >= 3.4
 Standards-Version: 3.9.6.1
 Homepage: http://www.brebisproject.org/

Bug#952348: backupchecker: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 m

[Logan Rosen]

Package: backupchecker
Version: 1.7-1
Followup-For: Bug #952348
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on dh-python to fix FTBFS due to missing python3.pm.

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru backupchecker-1.7/debian/control backupchecker-1.7/debian/control
--- backupchecker-1.7/debian/control2015-02-15 17:50:59.0 -0500
+++ backupchecker-1.7/debian/control2020-04-06 21:40:38.0 -0400
@@ -3,7 +3,7 @@
 Section: python
 Maintainer: Carl Chenet 
 Uploaders: Python Applications Packaging Team 

-Build-Depends: debhelper (>= 9), python3-all
+Build-Depends: debhelper (>= 9), python3-all, dh-python
 X-Python3-Version: >= 3.4
 Standards-Version: 3.9.6.1
 Homepage: https://github.com/backupchecker/backupchecker

Bug#956077: lintian: file-in-etc-not-marked-as-conffile shouldn't be reported for udebs?

[Samuel Thibault]

Package: lintian
Version: 2.63.0
Severity: serious
Justification: prevents upload of brltty package

Hello,

While running lintian on the output of the brltty source package, I am
getting this:

E: brltty-udeb udeb: file-in-etc-not-marked-as-conffile 
etc/brltty/Attributes/invleft_right.atb
E: brltty-udeb udeb: file-in-etc-not-marked-as-conffile 
etc/brltty/Attributes/left_right.atb
E: brltty-udeb udeb: file-in-etc-not-marked-as-conffile 
etc/brltty/Attributes/upper_lower.atb
E: brltty-udeb udeb: file-in-etc-not-marked-as-conffile ... use 
--no-tag-display-limit to see all (or pipe to a file/program)

But AIUI for a udeb it does not make sense to have conffiles, thus why
they are not getting set, that's expected.  I tried to override it with
this in brltty-udeb.lintian-overrides:

brltty-udeb udeb: file-in-etc-not-marked-as-conffile 
etc/brltty/Attributes/invleft_right.atb

but that didn't work. That's basically preventing me from uploading the
brltty package since ftpmaster also gets the error.

This can be reproduced efficiently with

  apt-get source rootskel 
  cd rootskel-*
  dpkg-buildpackage/pdebuild/whatever your liking
  lintian ../rootskel*.changes

I bisected the issue down to apparition in lintian version 2.58.0

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils 2.34-5
ii  bzip21.0.8-2
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-4
ii  gettext  0.19.8.1-10
ii  gpg  2.2.20-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b3
ii  libarchive-zip-perl  1.68-1
ii  libcapture-tiny-perl 0.48-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.43-2
ii  libcpanel-json-xs-perl   4.19-1
ii  libdevel-size-perl   0.83-1+b1
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libhtml-parser-perl  3.72-5
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libipc-run-perl  20180523.0-2
ii  libjson-maybexs-perl 1.004000-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmoo-perl  2.003006-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libsereal-decoder-perl   4.011+ds-1
ii  libsereal-encoder-perl   4.011+ds-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3200-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.008001-2
ii  libunicode-utf8-perl 0.62-1+b1
ii  liburi-perl  1.76-2
ii  libxml-libxml-perl   2.0134+dfsg-2
ii  libxml-writer-perl   0.625-1
ii  libyaml-libyaml-perl 0.81+repack-1
ii  man-db   2.9.1-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libtext-template-perl  1.58-1

-- no debconf information

-- 
Samuel
 xlnt comme sujet de stage je peux essayer de donner une description 
formelle de automake
 -+- #ens-mim -+-

Bug#938836: marked as done (xapian-bindings: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 22:04:45 +
with message-id 
and subject line Bug#938836: fixed in xapian-bindings 1.4.15-1
has caused the Debian Bug report #938836,
regarding xapian-bindings: 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.)


-- 
938836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xapian-bindings
Version: 1.4.12-2
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:xapian-bindings

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: xapian-bindings
Source-Version: 1.4.15-1
Done: Olly Betts 

We believe that the bug you reported is fixed in the latest version of
xapian-bindings, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 938...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated xapian-bindings package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Apr 2020 09:44:14 +1200
Source: xapian-bindings
Architecture: source
Version: 1.4.15-1
Distribution: unstable
Urgency: medium
Maintainer: Olly Betts 
Changed-By: Olly Betts 
Closes: 938836 953949 955072
Changes:
 xapian-bindings (1.4.15-1) unstable; urgency=medium
 .
   * New upstream release
 + debian/patches/ruby-2.7.patch: Drop patch included upstream.
   * Drop Python 2 bindings (python-xapian binary package).
 (Closes: #938836, #955072, #953949)
Checksums-Sha1:
 5a6a70853dcbbf9a47950603a7a38a2cf555cbcd 2721 xapian-bindings_1.4.15-1.dsc
 04626b5eda40ad1b3f4f2c60c344ce1fca5fff53 1132248 
xapian-bindings_1.4.15.orig.tar.xz
 09b91e648207b1a3b73a75be29e7ec8091381b47 833 
xapian-bindings_1.4.15.orig.tar.xz.asc
 b0397691f3500c3f6238ea09ec84911aeda6 21908 
xapian-bindings_1.4.15-1.debian.tar.xz
 ffbe142c1e32139dd4d4dbf251e2146f566fb757 15052 

Bug#956017: marked as done (gnome-maps: no results when searching for an address)

[Debian Bug Tracking System]

Your message dated Mon, 6 Apr 2020 22:47:46 +0100
with message-id <20200406214739.ga142...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#956017: gnome-maps: no results when searching for an 
address
has caused the Debian Bug report #956017,
regarding gnome-maps: no results when searching for an address
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.)


-- 
956017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-maps
Version: 3.30.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when entering an address into the search box of GNOME Maps on Debian
Stable, I get a loading animation for a few seconds and then "No results
found". The same applies for entering an address into the start or end
point of the routing panel.

This problem is fixed in newer versions of the package, but I believe it
should also get a bug fix for stable because in its current state, GNOME
Maps doesn't provide the basic functionality users would want from a map
application.

I'm not quite sure whether Debian provides bug fixes for stable in
situations like this, though, so sorry if I did something wrong with
this bug report.


-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-maps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  geoclue-2.0  2.5.2-1
ii  gir1.2-champlain-0.120.12.16-3
ii  gir1.2-clutter-1.0   1.26.2+dfsg-10
ii  gir1.2-cogl-1.0  1.22.2-6
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-geocodeglib-1.0   3.26.1-1
ii  gir1.2-gfbgraph-0.2  0.2.3-3
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-goa-1.0   3.30.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gtkchamplain-0.12 0.12.16-3
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-rest-0.7  0.8.1-1
ii  gir1.2-secret-1  0.18.7-1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-webkit2-4.0   2.26.4-1~deb10u2
ii  gjs  1.54.3-1
ii  libc62.28-10
ii  libchamplain-0.12-0  0.12.16-3
ii  libfolks25   0.11.4-1+b2
ii  libgee-0.8-2 0.20.1-2
ii  libgeocode-glib0 3.26.1-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libglib2.0-bin   2.58.3-2+deb10u2
ii  librest-0.7-00.8.1-1
ii  libxml2  2.9.4+dfsg1-7+b3

gnome-maps recommends no packages.

gnome-maps suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 06 Apr 2020 at 10:44:13 +0200, Keno Goertz wrote:
> when entering an address into the search box of GNOME Maps on Debian
> Stable, I get a loading animation for a few seconds and then "No results
> found".

On Mon, 06 Apr 2020 at 12:35:32 +0200, Keno Goertz wrote:
> Turns out geocode-glib uses https://nominatim.gnome.org, which is
> currently down (I don't know since when).

It sounds as though this is resolved for now.

For the future: this service is outside Debian's control, so when it
isn't working, there is little the Debian maintainers of gnome-maps can
do about that.

smcv--- End Message ---

Bug#951999: Autoconf issue in mpqc

[Jeremy Sowden]

On 2020-04-05, at 22:38:39 +0100, Jeremy Sowden wrote:
> On 2020-04-05, at 14:32:16 +0200, Andreas Tille wrote:
> > On Sun, Apr 05, 2020 at 12:34:55PM +0100, Jeremy Sowden wrote:
> > > > > I've attached the part or the build log that seems to be
> > > > > autoconf relevant.  I admit I'm a bit astonished since I can
> > > > > only see warnings but no error ...
> > > >
> > > > Here's a patch that fixes the autoheader warnings.
> > >
> > > Whoops.  That version doesn't seem to apply.  The patch I've
> > > attached to this message I have actually tested properly.
> > >
> > > > autoreconf is still failing.
> > >
> > > That's not quite right: "autoreconf" fails, but  "autoreconf -f
> > > -i" (which is what dh_autoreconf does) succeeds.  Now
> > > dh_auto_configure fails.
> >
> > I confirm it fails with
> >
> > ...
> > checking if semctl requires semun... no
> > checking if fortran compiler works... no
> > configure: error: in `/build/mpqc-2.3.1':
> > configure: error: fortran compiler does not work
> >
> >
> > I've updated Git with your patch - thanks a lot so far.
>
> In my case, the problem was:
>
>   ./configure: line 4287: mpicc: command not found
>
> IOW, missing build-deps.  Once I installed those, dh_auto_configure
> was happy, but there were compilation failures because autoheader
> clobbered src/lib/scconfig.h.in.  I've attached two patches which fix
> those.

Having re-read the autoconf and autoheader doc's this evening, I think
the attached fixes are an improvement over yesterday's.

J.
From cb556d820337b9e2b24cdc70049e9bca1967c7af Mon Sep 17 00:00:00 2001
From: Jeremy Sowden 
Date: Sun, 5 Apr 2020 20:22:51 +0100
Subject: [PATCH v2 1/2] shmtype fix.

---
 debian/patches/series|  1 +
 debian/patches/shmtype.patch | 21 +
 2 files changed, 22 insertions(+)
 create mode 100644 debian/patches/shmtype.patch

diff --git a/debian/patches/series b/debian/patches/series
index db79d4fb8ff5..c5ef93ff27ed 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,3 +12,4 @@ g++6-constexpr.patch
 Fix_mpi.patch
 autoconf.patch
 autoheader.patch
+shmtype.patch
diff --git a/debian/patches/shmtype.patch b/debian/patches/shmtype.patch
new file mode 100644
index ..273b16a9dec6
--- /dev/null
+++ b/debian/patches/shmtype.patch
@@ -0,0 +1,21 @@
+diff --git a/configure.in b/configure.in
+index 8ebd2fa89c95..96e7fb7039da 100644
+--- a/configure.in
 b/configure.in
+@@ -8,6 +8,7 @@ define([AC_CACHE_SAVE], )dnl for debugging configure.in
+ AC_INIT(src/lib/util/ref/ref.h)
+ AC_PREREQ(2.55)
+ AC_CONFIG_HEADER(src/lib/scconfig.h)
++AH_BOTTOM([#include "shm_type.h"])
+ AC_CONFIG_AUX_DIR(bin)
+ AC_CONFIG_MACRO_DIR([lib/autoconf])
+ 
+diff --git a/src/lib/shm_type.h b/src/lib/shm_type.h
+new file mode 100644
+index ..8c62fb392b34
+--- /dev/null
 b/src/lib/shm_type.h
+@@ -0,0 +1,3 @@
++#ifndef SHMTYPE
++#define SHMTYPE char*
++#endif
-- 
2.25.1

From 758970c9d0b5928b60b000acd3485cc666827591 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden 
Date: Sun, 5 Apr 2020 20:58:57 +0100
Subject: [PATCH v2 2/2] restrictxx fix.

---
 debian/patches/restrictxx.patch | 27 +++
 debian/patches/series   |  1 +
 2 files changed, 28 insertions(+)
 create mode 100644 debian/patches/restrictxx.patch

diff --git a/debian/patches/restrictxx.patch b/debian/patches/restrictxx.patch
new file mode 100644
index ..3730918e8701
--- /dev/null
+++ b/debian/patches/restrictxx.patch
@@ -0,0 +1,27 @@
+diff --git a/configure.in b/configure.in
+index 96e7fb7039da..040b475941c7 100644
+--- a/configure.in
 b/configure.in
+@@ -8,7 +8,10 @@ define([AC_CACHE_SAVE], )dnl for debugging configure.in
+ AC_INIT(src/lib/util/ref/ref.h)
+ AC_PREREQ(2.55)
+ AC_CONFIG_HEADER(src/lib/scconfig.h)
+-AH_BOTTOM([#include "shm_type.h"])
++AH_BOTTOM([
++#include "shm_type.h"
++#include "restrictxx.h"
++])
+ AC_CONFIG_AUX_DIR(bin)
+ AC_CONFIG_MACRO_DIR([lib/autoconf])
+ 
+diff --git a/src/lib/restrictxx.h b/src/lib/restrictxx.h
+new file mode 100644
+index ..cacfea3b7db5
+--- /dev/null
 b/src/lib/restrictxx.h
+@@ -0,0 +1,5 @@
++#ifdef CXX_RESTRICT
++#define restrictxx restrict
++#else
++#define restrictxx
++#endif
diff --git a/debian/patches/series b/debian/patches/series
index c5ef93ff27ed..9662a2c679b6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -13,3 +13,4 @@ Fix_mpi.patch
 autoconf.patch
 autoheader.patch
 shmtype.patch
+restrictxx.patch
-- 
2.25.1



signature.asc
Description: PGP signature

Processed: [bts-link] source package gnome-music

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gnome-music
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #954195 (http://bugs.debian.org/954195)
> # Bug title: gnome-music fails to start
> #  * https://gitlab.gnome.org/GNOME/gnome-music/issues/377
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 954195 + fixed-upstream
Bug #954195 [gnome-music] gnome-music fails to start
Added tag(s) fixed-upstream.
> usertags 954195 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954736: isc-dhcp rebuild enough?

[Bernhard Schmidt]

Hi,

since 9.16 the bind9 package is not building the bind9 shared libraries
anymore, which have previously been used by isc-dhcp instead of the
bundled bind9 source. Ondrej had filed Bug#942502 about this last October.

bind9 9.16 has now been uploaded to unstable, but (among two RC bugs)
the uninstallability of isc-dhcp prevents migration to testing. Ondrej
has also uploaded src:bind9-libs, which take over the -dev packages and
shared libraries with the most recent 9.11 code.

If I'm not mistaken a simple rebuild of src:isc-dhcp, possibly with
tightened build-dep on libbind-export-dev to ensure the use of the new
src:bind9-libs package should be enough.

Bug#942502: not using the embedded bind9 source, but the new dedicated
source package
Bug#954736: fixed by rebuilding isc-dhcp against the new libdns-export

This would unentangle bind9 and isc-dhcp and allow the latter to
propagate to testing.

Is there something I'm missing?

Bernhard

Processed: [bts-link] source package automat

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package automat
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #954079 (http://bugs.debian.org/954079)
> # Bug title: magic-wormhole: Fails to send with a type error
> #  * https://github.com/glyph/automat/issues/118
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 954079 + fixed-upstream
Bug #954079 [automat] magic-wormhole: Fails to send with a type error
Added tag(s) fixed-upstream.
> usertags 954079 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#937751: python-fftw: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Mon, Sep 02, 2019 at 02:07:36PM +0200, Jerome Kieffer wrote:
> Hi Matthias,
> 
> I believe the python-fftw packge has superseeded by python-pyfftw. Even
> if it has apparently less installation in popcon, it is at least
> actively maintained.
> 
> My feeling would be to drop it as "there should be one and only one
> obvious way to do it" and pyfftw is closer to this obvious way.
> 
> What do you think?

Agreed, I've just gone ahead and filed a removal bug.

Cheers,
Moritz

Bug#956017: gnome-maps: no results when searching for an address

[Keno Goertz]

The service is now back up, so this issue is resolved! Sorry for
opening this bug report, I wasn't sure I'd be able to figure it out by
myself.

Am Montag, den 06.04.2020, 12:35 +0200 schrieb Keno Goertz:
> Turns out geocode-glib uses https://nominatim.gnome.org, which is
> currently down (I don't know since when). The more recent version of
> GNOME maps doesn't use geocode-glib for geocoding, so it doesn't
> experience this problem.
> 
> I will write a mail to the person hosting GNOME's nominatim service.


signature.asc
Description: This is a digitally signed message part

Processed: ttyrec: diff for NMU version 1.0.8-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 954506 + patch
Bug #954506 [src:ttyrec] ttyrec: FTBFS: ttyrec.c:60:10: fatal error: stropts.h: 
No such file or directory
Added tag(s) patch.
> tags 954506 + pending
Bug #954506 [src:ttyrec] ttyrec: FTBFS: ttyrec.c:60:10: fatal error: stropts.h: 
No such file or directory
Added tag(s) pending.

-- 
954506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954506: ttyrec: diff for NMU version 1.0.8-5.1

[Sudip Mukherjee]

Control: tags 954506 + patch
Control: tags 954506 + pending

Dear maintainer,

I've prepared an NMU for ttyrec (versioned as 1.0.8-5.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru ttyrec-1.0.8/debian/changelog ttyrec-1.0.8/debian/changelog
--- ttyrec-1.0.8/debian/changelog   2010-04-28 06:09:09.0 +0100
+++ ttyrec-1.0.8/debian/changelog   2020-04-06 19:48:56.0 +0100
@@ -1,3 +1,10 @@
+ttyrec (1.0.8-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #954506)
+
+ -- Sudip Mukherjee   Mon, 06 Apr 2020 19:48:56 
+0100
+
 ttyrec (1.0.8-5) unstable; urgency=low
 
   * debian/patches/15_ttyrec_dont_record_query.diff: New file (Closes:
diff -Nru ttyrec-1.0.8/debian/patches/17_remove_stropts.patch 
ttyrec-1.0.8/debian/patches/17_remove_stropts.patch
--- ttyrec-1.0.8/debian/patches/17_remove_stropts.patch 1970-01-01 
01:00:00.0 +0100
+++ ttyrec-1.0.8/debian/patches/17_remove_stropts.patch 2020-04-06 
19:48:21.0 +0100
@@ -0,0 +1,48 @@
+Description: Fix FTBFS
+ glibc removed obsolete, never-implemented XSI STREAMS declarations via:
+ 
https://sourceware.org/git/?p=glibc.git;a=commit;h=a0a0dc83173ce11ff45105fd32e5d14356cdfb9c
+ And so stropts.h file is not available anymore.
+
+ Moreover isastream() was declared in stropts.h and was never actually
+ implemented. It always returned 0.
+ ref: https://sources.debian.org/src/glibc/2.30-4/posix/streams-compat.c/#L68
+ As a result, "if (isastrem())" will always be false, so remove that.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/954506
+
+---
+
+--- ttyrec-1.0.8.orig/ttyrec.c
 ttyrec-1.0.8/ttyrec.c
+@@ -57,7 +57,6 @@
+ 
+ #if defined(SVR4)
+ #include 
+-#include 
+ #endif /* SVR4 */
+ 
+ #include 
+@@ -483,22 +482,6 @@ getslave()
+   perror("open(fd, O_RDWR)");
+   fail();
+   }
+-  if (isastream(slave)) {
+-  if (ioctl(slave, I_PUSH, "ptem") < 0) {
+-  perror("ioctl(fd, I_PUSH, ptem)");
+-  fail();
+-  }
+-  if (ioctl(slave, I_PUSH, "ldterm") < 0) {
+-  perror("ioctl(fd, I_PUSH, ldterm)");
+-  fail();
+-  }
+-#ifndef _HPUX_SOURCE
+-  if (ioctl(slave, I_PUSH, "ttcompat") < 0) {
+-  perror("ioctl(fd, I_PUSH, ttcompat)");
+-  fail();
+-  }
+-#endif
+-  }
+   (void) tcsetattr(slave, TCSAFLUSH, );
+   (void) ioctl(slave, TIOCSWINSZ, (char *));
+   (void) ioctl(slave, TIOCSCTTY, 0);
diff -Nru ttyrec-1.0.8/debian/patches/series ttyrec-1.0.8/debian/patches/series
--- ttyrec-1.0.8/debian/patches/series  2010-04-28 05:49:40.0 +0100
+++ ttyrec-1.0.8/debian/patches/series  2020-04-06 19:41:17.0 +0100
@@ -14,3 +14,4 @@
 14_ttyplay_man.diff
 15_ttyrec_dont_record_query.diff
 16_ttyrec_XCASE.diff
+17_remove_stropts.patch

Bug#956057: trying to overwrite '/usr/lib/x86_64-linux-gnu/libmaeparser.so.1', which is also in package libschroedinger-maeparser1:amd64 1.2.2-1

[Daniel Leidert]

Package: libmaeparser1
Version: 1.2.3-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have libschroedinger-maeparser1 and when I try to upgrade the system
libmaeparser1 is pulled in and it seems to miss a Conflicts/Breaks.

Regards, Daniel

- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmaeparser1 depends on:
ii  libboost-iostreams1.67.0  1.67.0-17
ii  libc6 2.30-4
ii  libgcc-s1 [libgcc-s1] 10-20200402-1
ii  libstdc++610-20200402-1

libmaeparser1 recommends no packages.

libmaeparser1 suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl6LhR4ACgkQS80FZ8KW
0F3Hyg/+O86GKNIRipZgyQwn5Ezu0qDCejND9M6vIrN4xP/LzpY/bOqRJkV/DjyA
iLiV0ZIWz869QKBkvfvfoHwRRcz0bHhCjYTk9FdoRgmva11uJVULWVRSzDjCC75s
adyMuc9bSZhOuW6du/SWuyXXkKzAWkskOroHxP4qLo+tZ8ZZCZQmj/jTs0QYLXar
W3zsj+p5t6IrN2tQiRPwn0VrW9p3uMpb44LVYw561wS7BY8UXcCBQQLk250v6q2I
McvpPuLWskdwPqt9MrASYGRnFoYbmBgblzqQpIGymPCuAZq0ELGReu0wpXP5Pu8u
O040aHd2dsiANTskzzsWI4bQWAuk/8Bhczs9GrLyyxrg63dVr+H0yIDcnUHn50i9
8/i4/YM9QF/7XpVCcJ2bK4/W0bMmwxkzKd3TOaR14jT8vjwAK+G9YrS3hlGiD0vK
1uA2YeBCq4EEhg6Mk3mfL3yuBlEJ4pJv6rTMoyLKgdG5RGTXTD2E2YEv2g53PFMQ
ZEJRyJlRofpvj2qEttbvKkqmrlyQcPI++bjK6dT7noAEUMxguRxCHJBj4LboAPjB
2bkTx2QoxfLB0allk1UCtA5EATwD1fHgfbksBftpDttz42ha1iHsrbAe3KUzf+BI
2bgXl7YnTcwP55GTbiIvO6Wy+uVvLV1OSF1zXKs0rj1OnS6Zjqw=
=G/Lp
-END PGP SIGNATURE-

Bug#956013: Fails to install

[David Prévot]

Hi,

Le 06/04/2020 à 07:46, Mario Blättermann a écrit :
> David Prévot  schrieb am Mo., 6. Apr. 2020, 18:51:
>> Le 06/04/2020 à 02:39, Dr. Tobias Quathamer a écrit :
>>
>>> I think that this bug is now fixed in git. If you have the time, I'd
>>> value your input if I've thought of everything before I start another
>>> upload cycle.
>>
>> I very much doubt it is manpages-l10n task to take over
>> manpages-fr-extra (especially via a transnational dummy package).
> 
> It *is* the task of manpages-l10n because the source tarball contains
> translations which were previously maintained within manpages-fr-extra.

Ho, that’s nice to hear. I totally failed to notice the takeover of
glibc, openssl, bash, coreutils, most, etc. manpage translations that
manpages-fr-extra used to provide.

Anyway, you could simply upload a manpages-fr-extra update providing the
dummy package instead of adding it in manpages-l10n (and be bugged by
version handling and NEW processing) if you want this issue resolved
quickly.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#952176: marked as done (golang-github-facebookgo-ensure: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/facebookgo/ensure returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 6 Apr 2020 19:18:12 +0200 (CEST)
with message-id 
and subject line closing this bug
has caused the Debian Bug report #952176,
regarding golang-github-facebookgo-ensure: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/facebookgo/ensure 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-facebookgo-ensure
Version: 0.0~git20160127.0.b4ab57d-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/facebookgo/ensure
> runtime/internal/sys
> internal/race
> runtime/internal/atomic
> internal/cpu
> runtime/internal/math
> sync/atomic
> unicode
> unicode/utf8
> math/bits
> internal/testlog
> internal/bytealg
> math
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> bytes
> strings
> reflect
> regexp/syntax
> internal/syscall/unix
> time
> regexp
> internal/poll
> internal/fmtsort
> github.com/facebookgo/subset
> os
> path/filepath
> fmt
> encoding/hex
> github.com/facebookgo/stack
> github.com/davecgh/go-spew/spew
> github.com/facebookgo/ensure
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/facebookgo/ensure
> === RUN   TestIndirectStackTrace
> --- FAIL: TestIndirectStackTrace (0.00s)
> ensure.go:65: 
> github.com/facebookgo/ensure/common_test.go:36 (*capture).Contains
> github.com/facebookgo/ensure/ensure_no_race_test.go:18 
> TestIndirectStackTrace
> expected substring 
> "github.com/facebookgo/ensure/ensure_no_race_test.go:12" was not found in 
> "ensure_no_race_test.go:12: expected substring "bar" was not 
> found in "foo""
> === RUN   TestNilErr
> --- PASS: TestNilErr (0.00s)
> === RUN   TestMatchingError
> --- PASS: TestMatchingError (0.00s)
> === RUN   TestExtras
> --- PASS: TestExtras (0.00s)
> === RUN   TestDeepEqualStruct
> --- PASS: TestDeepEqualStruct (0.00s)
> === RUN   TestDeepEqualString
> --- PASS: TestDeepEqualString (0.00s)
> === RUN   TestNotDeepEqualStruct
> --- PASS: TestNotDeepEqualStruct (0.00s)
> === RUN   TestSubsetStruct
> --- PASS: TestSubsetStruct (0.00s)
> === RUN   TestUnexpectedNilErr
> --- PASS: TestUnexpectedNilErr (0.00s)
> === RUN   TestNilString
> --- PASS: TestNilString (0.00s)
> === RUN   TestNilInt
> --- PASS: TestNilInt (0.00s)
> === RUN   TestNilStruct
> --- PASS: TestNilStruct (0.00s)
> === RUN   TestNonNil
> --- FAIL: TestNonNil (0.00s)
> ensure.go:65: 
> github.com/facebookgo/ensure/common_test.go:29  (*capture).Equal
> github.com/facebookgo/ensure/ensure_test.go:137 TestNonNil
> expected these to be equal:
> ACTUAL:
> (string) (len=196) "
> github.com/facebookgo/ensure/ensure.go:204
> NotNil\n/usr/lib/go-1.13/src/testing/testing.go:909   
> tRunner\n/usr/lib/go-1.13/src/runtime/asm_amd64.s:1357 goexit\nexpected a 
> value but got nil"
> 
> EXPECTED:
> (string) (len=48) "ensure_test.go:136: expected a value but got nil"
> === RUN   TestStringContains
> --- PASS: TestStringContains (0.00s)
> === RUN   TestStringDoesNotContain
> --- PASS: TestStringDoesNotContain (0.00s)
> === RUN   TestExpectedNilErr
> --- PASS: TestExpectedNilErr (0.00s)
> === RUN   TestNilErrUsingNil
> --- PASS: TestNilErrUsingNil (0.00s)
> === RUN   TestTrue
> --- FAIL: TestTrue (0.00s)
> ensure.go:65: 
> github.com/facebookgo/ensure/common_test.go:29  (*capture).Equal
> github.com/facebookgo/ensure/ensure_test.go:171 TestTrue
> expected these to be equal:
> ACTUAL:
> (string) (len=193) "
> github.com/facebookgo/ensure/ensure.go:215
> True\n/usr/lib/go-1.13/src/testing/testing.go:909   
> tRunner\n/usr/lib/go-1.13/src/runtime/asm_amd64.s:1357 goexit\nexpected true 
> but got false"
> 
> EXPECTED:
> 

Bug#956013: Fails to install

[Dr. Tobias Quathamer]

Am 6. April 2020 18:51:31 MESZ schrieb "David Prévot" :
>Le 06/04/2020 à 02:39, Dr. Tobias Quathamer a écrit :
>
>> I think that this bug is now fixed in git. If you have the time, I'd
>> value your input if I've thought of everything before I start another
>> upload cycle.
>
>I very much doubt it is manpages-l10n task to take over
>manpages-fr-extra (especially via a transnational dummy package).
>
>Anyway, adding a manpages-fr-extra package with a version lower the one
>currently in unstable will not supersede it.
>
>Regards
>
>David

Hi David,

I'm not sure if I understand correctly what you want to say.

Do you mean that the separate package manpages-fr-extra should stay as a 
separate package? If so, please note that all existing translations from 
manpages-fr-extra have been imported into manpages-l10n, so I thought that we 
could supersede and remove manpages-fr-extra.

If this is not wanted, I can of course remove those translations, so that 
manpages-fr-extra can still exist as an own project.

Regarding the version number: I've added a special case for manpages-fr-extra 
in d/rules, so that the new version number of that package is greater than the 
current version in unstable (20200406 vs. 20151231).

Please tell me if the French translation team would like to keep 
manpages-fr-extra, I certainly don't want to step on anyone's toes.

Regards,
Tobias

Bug#956013: Fails to install

[Mario Blättermann]

Hi David,

David Prévot  schrieb am Mo., 6. Apr. 2020, 18:51:

> Le 06/04/2020 à 02:39, Dr. Tobias Quathamer a écrit :
>
> > I think that this bug is now fixed in git. If you have the time, I'd
> > value your input if I've thought of everything before I start another
> > upload cycle.
>
> I very much doubt it is manpages-l10n task to take over
> manpages-fr-extra (especially via a transnational dummy package).
>

It *is* the task of manpages-l10n because the source tarball contains
translations which were previously maintained within manpages-fr-extra.

Well, alternatively we could disable the man pages which come from there
and keep publishing the old manpages-fr-extra package again and again, with
all the outdated stuff it contains. Doesn't make sense at all. Instead,
let's go a step ahead and switch to up-to-date man pages.

Best Regards,
Mario


Anyway, adding a manpages-fr-extra package with a version lower the one
> currently in unstable will not supersede it.
>
> Regards
>
> David
>
>

Bug#956013: Fails to install

[David Prévot]

Le 06/04/2020 à 02:39, Dr. Tobias Quathamer a écrit :

> I think that this bug is now fixed in git. If you have the time, I'd
> value your input if I've thought of everything before I start another
> upload cycle.

I very much doubt it is manpages-l10n task to take over
manpages-fr-extra (especially via a transnational dummy package).

Anyway, adding a manpages-fr-extra package with a version lower the one
currently in unstable will not supersede it.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#954496: cwltool: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13

[tony mancill]

On Mon, Mar 30, 2020 at 05:49:42PM +0900, Kentaro Hayashi wrote:
> > /usr/lib/python3/dist-packages/coloredlogs/__init__.py:192: in 
> > from humanfriendly.terminal import ANSI_COLOR_CODES, ansi_wrap, 
> > terminal_supports_colors
> > E   ModuleNotFoundError: No module named 'humanfriendly.terminal'
> 
> Hi, It seems this bug was already fixed by #954640, and you should use latest 
> humanfriendly/8.1-2.
> 
>   python3-humanfriendly: humanfriendly.terminal module missing from package
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954640
> 
> http://qa-logs.debian.net/2020/03/21/cwltool_2.0.20200224214940+dfsg-1_unstable.log
> indicates that it uses humanfriendly/8.1-1 (old version).
> This package lacks humanfiriendly.terminal module.
> 
> FYI: Here is the d/changelog about 8.1-2
> 
>  Changes:
>  humanfriendly (8.1-2) unstable; urgency=medium
>  .
>* Team upload.
>  .
>[Christian Pommranz]
>  .
>* Install humanfriendly.terminal module (Closes: #954640)

I can confirm that building against humanfriendly (=8.1-2) [1] addresses
this FTBFS, and this version migrated into tested on 2020-04-02.
python3-humanfriendly is being pulled in transitively via
python3-coloredlogs.

Is there anything else to do for this?

Thanks,
tony

[1] 
https://tracker.debian.org/news/1112315/accepted-humanfriendly-81-2-source-into-unstable/
  


signature.asc
Description: PGP signature

Bug#954311: Not just rendering issues...

[Timo Aaltonen]

On 6.4.2020 1.55, Pascal Giard wrote:
> Thanks A LOT for the /etc/drirc trick, it fixed the problem
> detailed below for me.
> Took me over an hour to figure out what was wrong and to end up on this
> bug report.
> 
> I have a Thinkpad T480 (Intel UHD 620).
> 
> The new iris driver causes all my video players to crash (e.g., VLC or
> mpv) and prevents Zoom from converting my recorded sessions.
Do you use xserver-xorg-video-intel? If yes, get rid of it.


-- 
t

Bug#954244: marked as done (mpich FTBFS on armel, armhf, i386, mipsel: static assertion failed: "MPL_COMPILE_TIME_ASSERT failure")

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 15:05:33 +
with message-id 
and subject line Bug#954244: fixed in mpich 3.4~a2+really3.3.2-1
has caused the Debian Bug report #954244,
regarding mpich FTBFS on armel, armhf, i386, mipsel: static assertion failed: 
"MPL_COMPILE_TIME_ASSERT 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.)


-- 
954244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpich
Version: 3.4~a2-1
Severity: serious
Justification: ftbfs

Hi maintainer(s),

The latest versions of your package fails to build from source, which
prevents it from migrating to testing.

Paul

https://buildd.debian.org/status/package.php?p=mpich

Tail of log for mpich on armel:

In file included from /<>/src/mpl/include/mpl.h:10,
 from ./src/include/mpiimpl.h:153,
 from src/mpi/coll/allgather/allgather_allcomm_nb.c:7:
./src/mpid/ch4/netmod/include/../ofi/ofi_iovec_util.h: In function
‘MPIDI_OFI_merge_segment’:
/<>/src/mpl/include/mpl_base.h:90:39: error: static
assertion failed: "MPL_COMPILE_TIME_ASSERT failure"
   90 | #define MPL_static_assert(cond_,msg_) _Static_assert(cond_,msg_)
  |   ^~
/<>/src/mpl/include/mpl_base.h:101:40: note: in expansion
of macro ‘MPL_static_assert’
  101 | #define MPL_COMPILE_TIME_ASSERT(cond_) MPL_static_assert(cond_,
"MPL_COMPILE_TIME_ASSERT failure")
  |^
./src/mpid/ch4/netmod/include/../ofi/ofi_iovec_util.h:388:5: note: in
expansion of macro ‘MPL_COMPILE_TIME_ASSERT’
  388 | MPL_COMPILE_TIME_ASSERT(offsetof(struct iovec, iov_len) ==
offsetof(struct fi_rma_iov, len));
  | ^~~
make[3]: *** [Makefile:32896: src/mpi/attr/lib_libmpich_la-dup_fn.lo]
Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:32910:
src/mpi/coll/allgather/lib_libmpich_la-allgather_intra_recursive_doubling.lo]
Error 1
make[3]: *** [Makefile:32903:
src/mpi/coll/allgather/lib_libmpich_la-allgather_allcomm_nb.lo] Error 1
make[3]: *** [Makefile:32889: src/mpi/attr/lib_libmpich_la-attrutil.lo]
Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:45372: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:13561: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j4 returned exit code 2
make: *** [debian/rules:69: build-arch] Error 25



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 3.4~a2+really3.3.2-1
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
mpich, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mpich package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 06 Apr 2020 14:56:01 +0100
Source: mpich
Architecture: source
Version: 3.4~a2+really3.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 954244
Changes:
 mpich (3.4~a2+really3.3.2-1) unstable; urgency=medium
 .
   * Upload to remove broken 3.4~a2 pkg. Closes: #954244
Checksums-Sha1:
 683e030a80988d60379f9c1d1f41b176d14adbdf 2600 mpich_3.4~a2+really3.3.2-1.dsc
 14c0c53d8d2c5054d95fba52ed3ecff80c8f5ee2 13118648 
mpich_3.4~a2+really3.3.2.orig.tar.xz
 89574dd33beb93dcdc637d37192eb48fbc9b568f 339292 
mpich_3.4~a2+really3.3.2-1.debian.tar.xz
Checksums-Sha256:
 7718e909a190a664e0a7ff9dda5d05ae9f73d62d498729ced0a21f59ecba9b52 2600 
mpich_3.4~a2+really3.3.2-1.dsc
 c55080b5758a6ba0cb5bb7f5ec29e9ab71f66d8f2ac421a3d5dcbaf8cb7b8244 13118648 
mpich_3.4~a2+really3.3.2.orig.tar.xz
 c3ff3ff2ac2c40c2e66882b01bb9d38a85626e2396509c9d3290267281eea419 339292 
mpich_3.4~a2+really3.3.2-1.debian.tar.xz
Files:
 51edbf60b4b6ef1a9593da1a09fd87aa 2600 devel optional 
mpich_3.4~a2+really3.3.2-1.dsc
 f417bbea2bb39d354192d35a88593163 13118648 devel optional 

Processed (with 1 error): reopening 948295, forcibly merging 937687 948295

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 948295
Bug #948295 {Done: =?utf-8?q?Guido_G=C3=BCnther?= } 
[src:python-dateutil] python-dateutils's autopkg tests fail / Update to 2.8.1 
for Python 3.8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-dateutil/2.8.1-1.
> forcemerge 937687 948295
Bug #937687 [src:python-dateutil] python-dateutil: Python2 removal in 
sid/bullseye
Bug #948295 [src:python-dateutil] python-dateutils's autopkg tests fail / 
Update to 2.8.1 for Python 3.8
Severity set to 'normal' from 'serious'
Failed to forcibly merge 937687: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
937687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937687
948295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956034: nvidia-legacy-340xx-driver: Fails to build with kernel 5.5

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-3
Followup-For: Bug #956034

Got it!
Patching was as easy as

patch /usr/src/nvidia-legacy-340xx-340.108/uvm/Makefile < 03-unfuck-
for-5.5.x.patch

and forcing dkms to rebuild it was done with

dkms autoinstall

via the recovery mode. Now I have a working nvidia 340.xx on kernel 5.5.



-- Package-specific info:
uname -a:
Linux mitsos 5.5.0-1-amd64 #1 SMP Debian 5.5.13-2 (2020-03-30) x86_64 GNU/Linux

/proc/version:
Linux version 5.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-8)) #1 SMP Debian 5.5.13-2 (2020-03-30)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 9.3.0 (Debian 9.3.0-8) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.319348] Console: colour VGA+ 80x25
[0.751062] pci :01:00.0: vgaarb: setting as boot VGA device
[0.751062] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.751062] pci :01:00.0: vgaarb: bridge control possible
[0.751062] vgaarb: loaded
[0.933623] Linux agpgart interface v0.103
[3.228114] nvidia: loading out-of-tree module taints kernel.
[3.228125] nvidia: module license 'NVIDIA' taints kernel.
[3.278200] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.283530] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.283552] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.602961] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[4.836981] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17
[4.837062] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18
[4.837136] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input24
[4.837206] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input25
[8.483374] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Apr  6 16:52 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Apr  6 16:52 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Apr  6 16:52 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Apr  6 16:52 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jan  5 09:29 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jan  5 09:29 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jan  5 09:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jan  5 09:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   54 Jan  5 09:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Jan  5 09:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   25 Jan  5 09:29 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jan  5 09:29 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jan  5 09:29 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jan  5 09:29 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jan  5 09:29 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jan  5 09:29 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jan  5 09:29 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Jan  5 09:27 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root root   57 Jan  5 09:27 
/etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> 

Bug#955456: FTBFS: test file tmp_test_filters.h5 does not exist

[Drew Parsons]

On 2020-04-06 20:23, Gilles Filippini wrote:

Drew Parsons a écrit le 06/04/2020 à 05:08 :

Do we want to use this as a solution? Or would you prefer an 
environment
variable that h5py can check to allow mpi invocation on a serial 
process?


I let this decision up to you.



I think it's reasonable to give h5py an environment variable to work 
with, since the same problem might occur for other applications 
(including user apps). It's conceivable some users might want their hdf5 
(h5py) apps to build against mpi, even if also used in serial mode.



Whatever you choose it deserve a bit fat
note in README.Debian.


Certainly.


Note that this means bitshuffle as built now is expressly tied in with
hdf5-mpi and h5py-mpi (this seems intentional by debian/rules and
debian/control, though the Build-Depends must be updated to
python3-h5py-mpi).  It's a separate question whether it's desirable to
also support a hdf5-serial build of bitshuffle.  Likewise we need to
think about what we want to happen when bitshuffle is invoked in a
serial process.


I'll let that to the bitshuffle maintainer.


More puzzles for Thorsten to spend the weekends on :)


I'll propose a patch to fix
the current FTBFS, sticking on the mpi flavour to be conservative vs
bitshuffle's previous builds.


Thanks for your help.

Drew

Bug#953172: marked as done (kerneloops: service http://oops.kernel.org no longer available)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 13:20:37 +
with message-id 
and subject line Bug#956031: Removed package(s) from unstable
has caused the Debian Bug report #953172,
regarding kerneloops: service http://oops.kernel.org no longer available
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.)


-- 
953172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kerneloops
Version: 0.12+git20140509-6
Severity: normal

Dear Maintainer,

The server at http://oops.kernel.org is no longer accepting submissions.  As
far as I can see, this has been the case since 2017.  The developer mentions a
migration of code at that time in an open issue on github.  The corresponding
issue was never closed.

This package is therefore no longer relevant or useful. In my opinion, it
should be removed from the Debian repository.




-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), 
LANGUAGE=nl_NL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 0.12+git20181124-7+rm

Dear submitter,

as the package kerneloops has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/956031

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#955456: FTBFS: test file tmp_test_filters.h5 does not exist

[Gilles Filippini]

Control: tags -1 + patch

Gilles Filippini a écrit le 06/04/2020 à 14:23 :
> Drew Parsons a écrit le 06/04/2020 à 05:08 :
>> On 2020-04-06 09:56, Drew Parsons wrote:
>>> On 2020-04-06 01:48, Gilles Filippini wrote:
 Drew Parsons a écrit le 05/04/2020 à 18:57 :
>
> Another option is to create an environment variable to force h5py to
> load the mpi version even when run in a serial environment without
> mpirun. Easy enough to set up, though I'm interested to see if "mpirun
> -n 1 dh_auto_build" or a variation of that is viable.  Maybe
> %:
> mpirun -n 1 dh $@ --with python3 --buildsystem=pybuild

 This, way the test cases run against python3.7 is OK, but it fails
 against python3.8 with:

 I: pybuild base:217: cd
 /build/bitshuffle-z2ZvpN/bitshuffle-0.3.5/.pybuild/cpython3_3.8_bitshuffle/build;

 python3.8 -m unittest discover -v
 [pinibrem15:43725] OPAL ERROR: Unreachable in file ext3x_client.c at
 line 112
 *** An error occurred in MPI_Init_thread
 *** on a NULL communicator
 *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
 ***    and potentially your MPI job)
 [pinibrem15:43725] Local abort before MPI_INIT completed completed
 successfully, but am not able to aggregate error messages, and not able
 to guarantee that all other processes were killed!
 E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1:
 cd
 /build/bitshuffle-z2ZvpN/bitshuffle-0.3.5/.pybuild/cpython3_3.8_bitshuffle/build;

 python3.8 -m unittest discover -v
 dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8"
 returned exit code 13

 But the HDF5 error is no more present with python3.7. So it seems a good
 point.
>>>
>>>
>>> Strange again.  I would have expected the same behaviour in python3.8
>>> and python3.7, whether successful or unsuccessful.
>>
>>
>> Putting dh into mpirun seems to be interfering with process spawning. 
>> Once MPI is initialised (for the python3.7 test) it's not reinitialised
>> for the python3.8 and so it's in a bad state for the test. Something
>> like that.
>>
>> It's only in the tests where h5py is invoked that we get the problems.
>> This variant works, applying mpirun separately for each test run:
>>
>> override_dh_auto_test:
>>     set -e; \
>>     for py in `py3versions -s -v`; do \
>>   mpirun -n 1 pybuild --test -i python{version} -p $$py; \
>>     done
>>
>> (could use mpirun -n $(NPROC) for real mpi testing).
> 
> Yes, it works! \o/
> 
>> Do we want to use this as a solution? Or would you prefer an environment
>> variable that h5py can check to allow mpi invocation on a serial process?
> 
> I let this decision up to you. Whatever you choose it deserve a bit fat
> note in README.Debian.
> 
>> Note that this means bitshuffle as built now is expressly tied in with
>> hdf5-mpi and h5py-mpi (this seems intentional by debian/rules and
>> debian/control, though the Build-Depends must be updated to
>> python3-h5py-mpi).  It's a separate question whether it's desirable to
>> also support a hdf5-serial build of bitshuffle.  Likewise we need to
>> think about what we want to happen when bitshuffle is invoked in a
>> serial process.
> 
> I'll let that to the bitshuffle maintainer. I'll propose a patch to fix
> the current FTBFS, sticking on the mpi flavour to be conservative vs
> bitshuffle's previous builds.

Here it is.

_g.
diff -Nru bitshuffle-0.3.5/debian/changelog bitshuffle-0.3.5/debian/changelog
--- bitshuffle-0.3.5/debian/changelog   2019-12-01 19:03:38.0 +0100
+++ bitshuffle-0.3.5/debian/changelog   2020-04-06 14:47:10.0 +0200
@@ -1,3 +1,21 @@
+bitshuffle (0.3.5-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Drew Parsons , Gilles Filippini  ]
+  * Closes: #955456
+- fix-deprecated.patch: fix test_h5filter.py and test_h5plugin.py
+  to open files with flag 'w' when required
+- Build-Depends: python3-h5py-mpi to force using the mpi flavour
+  of h5py
+- override_dh_auto_test:
+  - Run the tests via mpirun so that h5py knows it has to invoke its
+mpi implementation
+  - Launch the tests for each python version separatly to permit MPI
+initialization at each run
+
+ -- Gilles Filippini   Mon, 06 Apr 2020 14:47:10 +0200
+
 bitshuffle (0.3.5-3) unstable; urgency=medium
 
   * don't use -march=native when building the package
diff -Nru bitshuffle-0.3.5/debian/control bitshuffle-0.3.5/debian/control
--- bitshuffle-0.3.5/debian/control 2019-12-01 19:03:38.0 +0100
+++ bitshuffle-0.3.5/debian/control 2020-04-06 14:46:51.0 +0200
@@ -11,7 +11,7 @@
 #  , libopenmpi-dev
, openmpi-bin
, python3-setuptools
-   , python3-h5py
+   , python3-h5py-mpi
 , quilt
 , cmake
, pkg-config
diff -Nru bitshuffle-0.3.5/debian/patches/fix-deprecated.patch 

Processed: Re: FTBFS: test file tmp_test_filters.h5 does not exist

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #955456 [bitshuffle] FTBFS: test file tmp_test_filters.h5 does not exist
Added tag(s) patch.

-- 
955456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign to ruby-vcr

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 951889 ruby-vcr
Bug #951889 [ruby-excon] ruby-excon 0.72 breaks ruby-vcr
Bug reassigned from package 'ruby-excon' to 'ruby-vcr'.
No longer marked as found in versions ruby-excon/0.72.0-1.
Ignoring request to alter fixed versions of bug #951889 to the same values 
previously set
> found 951889 4.0.0-2
Bug #951889 [ruby-vcr] ruby-excon 0.72 breaks ruby-vcr
Marked as found in versions ruby-vcr/4.0.0-2.
> fixed 951889 5.1.0-2
Bug #951889 [ruby-vcr] ruby-excon 0.72 breaks ruby-vcr
Marked as fixed in versions ruby-vcr/5.1.0-2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
951889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951889: marked as done (ruby-excon 0.72 breaks ruby-vcr)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 18:33:50 +0530
with message-id 
and subject line fixed in ruby-vcr 5.1.0-2
has caused the Debian Bug report #951889,
regarding ruby-excon 0.72 breaks ruby-vcr
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.)


-- 
951889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ruby-excon
Version: 0.72.0-1
Severity: grave
Control: forwarded -1 https://github.com/vcr/vcr/issues/801

reported test failure upstream to vcs.
--- End Message ---
--- Begin Message ---

closing.--- End Message ---

Bug#955527: kernelshark: Crash (SIGSEGV) when pressing the "+" button

[Sudip Mukherjee]

Control: tags 955527 upstream fixed-upstream

This has been fixed in https://bugzilla.kernel.org/show_bug.cgi?id=204195

I think I will wait for few more days for the fix to:
https://bugzilla.kernel.org/show_bug.cgi?id=207069 and then package
both together.

--
Regards
Sudip

Processed: Re: kernelshark: Crash (SIGSEGV) when pressing the "+" button

[Debian Bug Tracking System]

Processing control commands:

> tags 955527 upstream fixed-upstream
Bug #955527 [kernelshark] kernelshark: Crash (SIGSEGV) when pressing the "+" 
button
Added tag(s) fixed-upstream and upstream.

-- 
955527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956013: Fails to install

[Dr. Tobias Quathamer]

Am 06.04.20 um 08:38 schrieb David Prévot:
> Thanks for updating those translations. Unfortunately, there is an
> unhandled upgrade path (missing Breaks and Replace on manpages-fr-extra
> (<< 20151231something), and of course the manpages-fr-extra counterpart
> update).

Hi David,

I think that this bug is now fixed in git. If you have the time, I'd
value your input if I've thought of everything before I start another
upload cycle.

Regards,
Tobias

Git repository:
https://salsa.debian.org/debian/manpages-de

Hopefully fixing commit:
https://salsa.debian.org/debian/manpages-de/-/commit/33c242f69a18af92a2d51d696860d7e1a8f1fb2c



signature.asc
Description: OpenPGP digital signature

Processed: block 952066 with 953136

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 952066 with 953136
Bug #952066 [src:jag] jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: 
No such file or directory
952066 was not blocked by any bugs.
952066 was not blocking any bugs.
Added blocking bug(s) of 952066: 953136
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 952048

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 952048 + fixed-upstream
Bug #952048 [src:iem-plugin-suite] iem-plugin-suite: FTBFS: 
../../../resources/Standalone/MyStandaloneFilterWindow.h:132:47: error: cannot 
convert ‘juce::AudioIODeviceType*’ to ‘std::unique_ptr’
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955456: FTBFS: test file tmp_test_filters.h5 does not exist

[Gilles Filippini]

Drew Parsons a écrit le 06/04/2020 à 05:08 :
> On 2020-04-06 09:56, Drew Parsons wrote:
>> On 2020-04-06 01:48, Gilles Filippini wrote:
>>> Drew Parsons a écrit le 05/04/2020 à 18:57 :

 Another option is to create an environment variable to force h5py to
 load the mpi version even when run in a serial environment without
 mpirun. Easy enough to set up, though I'm interested to see if "mpirun
 -n 1 dh_auto_build" or a variation of that is viable.  Maybe
 %:
 mpirun -n 1 dh $@ --with python3 --buildsystem=pybuild
>>>
>>> This, way the test cases run against python3.7 is OK, but it fails
>>> against python3.8 with:
>>>
>>> I: pybuild base:217: cd
>>> /build/bitshuffle-z2ZvpN/bitshuffle-0.3.5/.pybuild/cpython3_3.8_bitshuffle/build;
>>>
>>> python3.8 -m unittest discover -v
>>> [pinibrem15:43725] OPAL ERROR: Unreachable in file ext3x_client.c at
>>> line 112
>>> *** An error occurred in MPI_Init_thread
>>> *** on a NULL communicator
>>> *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
>>> ***    and potentially your MPI job)
>>> [pinibrem15:43725] Local abort before MPI_INIT completed completed
>>> successfully, but am not able to aggregate error messages, and not able
>>> to guarantee that all other processes were killed!
>>> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1:
>>> cd
>>> /build/bitshuffle-z2ZvpN/bitshuffle-0.3.5/.pybuild/cpython3_3.8_bitshuffle/build;
>>>
>>> python3.8 -m unittest discover -v
>>> dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8"
>>> returned exit code 13
>>>
>>> But the HDF5 error is no more present with python3.7. So it seems a good
>>> point.
>>
>>
>> Strange again.  I would have expected the same behaviour in python3.8
>> and python3.7, whether successful or unsuccessful.
> 
> 
> Putting dh into mpirun seems to be interfering with process spawning. 
> Once MPI is initialised (for the python3.7 test) it's not reinitialised
> for the python3.8 and so it's in a bad state for the test. Something
> like that.
> 
> It's only in the tests where h5py is invoked that we get the problems.
> This variant works, applying mpirun separately for each test run:
> 
> override_dh_auto_test:
>     set -e; \
>     for py in `py3versions -s -v`; do \
>   mpirun -n 1 pybuild --test -i python{version} -p $$py; \
>     done
> 
> (could use mpirun -n $(NPROC) for real mpi testing).

Yes, it works! \o/

> Do we want to use this as a solution? Or would you prefer an environment
> variable that h5py can check to allow mpi invocation on a serial process?

I let this decision up to you. Whatever you choose it deserve a bit fat
note in README.Debian.

> Note that this means bitshuffle as built now is expressly tied in with
> hdf5-mpi and h5py-mpi (this seems intentional by debian/rules and
> debian/control, though the Build-Depends must be updated to
> python3-h5py-mpi).  It's a separate question whether it's desirable to
> also support a hdf5-serial build of bitshuffle.  Likewise we need to
> think about what we want to happen when bitshuffle is invoked in a
> serial process.

I'll let that to the bitshuffle maintainer. I'll propose a patch to fix
the current FTBFS, sticking on the mpi flavour to be conservative vs
bitshuffle's previous builds.

> I think part of the confusion here is that bitshuffle (at least in the
> tests) is double-handling the HDF5 library, with direct calls on the one
> hand, but indirectly through h5py as well, on the other hand.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed: block 952006 with 953751

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 952006 with 953751
Bug #952006 {Done: Michael Fladischer } [src:drf-extensions] 
drf-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.8 3.7" --system=custom 
"--test-args=PYTHONPATH='.:tests_app' {interpreter} /usr/bin/django-admin test 
--settings=settings tests_app" returned exit code 13
952006 was not blocked by any bugs.
952006 was not blocking any bugs.
Added blocking bug(s) of 952006: 953751
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956034: nvidia-legacy-340xx-driver: Fails to build with kernel 5.5

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-3
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

As with my previous bug reports for kernels 5.2 to 5.4, here is a new one for
5.5.
Building it fails like so
https://gist.github.com/pitsi/54af884134b251c237a6c810a7f4148b

Please excuse the use of github's gits, but the log was too big for any of the
pastebin services to handle (1.1MB). I will delete it once the bug is resolved.

And here is the relevant patch, from arch's aur repo
https://aur.archlinux.org/cgit/aur.git/plain/03-unfuck-
for-5.5.x.patch?h=nvidia-340xx

I do not know how to patch it myself and how to force dkms to rebuild it once I
patch it.



-- Package-specific info:
uname -a:
Linux mitsos 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux

/proc/version:
Linux version 5.4.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 
20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 9.2.1 20200123 (Debian 9.2.1-25) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.318029] Console: colour VGA+ 80x25
[0.743767] pci :01:00.0: vgaarb: setting as boot VGA device
[0.743767] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.743767] pci :01:00.0: vgaarb: bridge control possible
[0.743767] vgaarb: loaded
[0.928344] Linux agpgart interface v0.103
[3.349739] nvidia: loading out-of-tree module taints kernel.
[3.349751] nvidia: module license 'NVIDIA' taints kernel.
[3.378206] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.386836] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.390037] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.390050] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.861937] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[5.089395] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17
[5.089479] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18
[5.095512] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input23
[5.095611] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input25
[8.712492] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Apr  6 14:24 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Apr  6 14:25 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Apr  6 14:25 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Apr  6 14:24 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jan  5 09:29 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jan  5 09:29 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jan  5 09:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jan  5 09:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   54 Jan  5 09:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Jan  5 09:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   25 Jan  5 09:29 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jan  5 09:29 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jan  5 09:29 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jan  5 09:29 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jan  5 09:29 

Processed: tagging 951986

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 951986 + fixed-upstream
Bug #951986 [src:feedreader] feedreader: FTBFS: 
../src/Backend/FeedServer.vala:60.98-60.148: error: The name 
`COLLECTION_CREATE_NONE' does not exist in the context of 
`Secret.CollectionCreateFlags' (libsecret-1)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
951986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libwildmagic: diff for NMU version 5.13-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 815240 + patch
Bug #815240 [src:libwildmagic] libwildmagic: should be Architecture: linux-any
Ignoring request to alter tags of bug #815240 to the same tags previously set
> tags 815240 + pending
Bug #815240 [src:libwildmagic] libwildmagic: should be Architecture: linux-any
Ignoring request to alter tags of bug #815240 to the same tags previously set
> tags 951972 + patch
Bug #951972 [src:libwildmagic] libwildmagic: FTBFS: ld: cannot find -lXext
Ignoring request to alter tags of bug #951972 to the same tags previously set
> tags 951972 + pending
Bug #951972 [src:libwildmagic] libwildmagic: FTBFS: ld: cannot find -lXext
Ignoring request to alter tags of bug #951972 to the same tags previously set

-- 
815240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815240
951972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libwildmagic: diff for NMU version 5.13-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 815240 + patch
Bug #815240 [src:libwildmagic] libwildmagic: should be Architecture: linux-any
Added tag(s) patch.
> tags 815240 + pending
Bug #815240 [src:libwildmagic] libwildmagic: should be Architecture: linux-any
Added tag(s) pending.
> tags 951972 + patch
Bug #951972 [src:libwildmagic] libwildmagic: FTBFS: ld: cannot find -lXext
Added tag(s) patch.
> tags 951972 + pending
Bug #951972 [src:libwildmagic] libwildmagic: FTBFS: ld: cannot find -lXext
Added tag(s) pending.

-- 
815240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815240
951972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951972: libwildmagic: diff for NMU version 5.13-1.1

[Adrian Bunk]

Control: tags 815240 + patch
Control: tags 815240 + pending
Control: tags 951972 + patch
Control: tags 951972 + pending

Dear maintainer,

I've prepared an NMU for libwildmagic (versioned as 5.13-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libwildmagic-5.13/debian/changelog libwildmagic-5.13/debian/changelog
--- libwildmagic-5.13/debian/changelog	2014-08-13 13:04:25.0 +0300
+++ libwildmagic-5.13/debian/changelog	2020-04-06 14:53:56.0 +0300
@@ -1,3 +1,11 @@
+libwildmagic (5.13-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add the missing build dependency on libxext-dev. (Closes: #951972)
+  * Architecture: linux-any (Closes: #815240)
+
+ -- Adrian Bunk   Mon, 06 Apr 2020 14:53:56 +0300
+
 libwildmagic (5.13-1) unstable; urgency=low
   
   * New upstream version implementing all the stuff that I used to put in
diff -Nru libwildmagic-5.13/debian/control libwildmagic-5.13/debian/control
--- libwildmagic-5.13/debian/control	2014-08-13 13:04:25.0 +0300
+++ libwildmagic-5.13/debian/control	2020-04-06 14:53:56.0 +0300
@@ -5,6 +5,7 @@
 Build-Depends: debhelper (>= 9.2), 
dpkg-dev (>= 1.16.1~),
libglu1-mesa-dev (>= 9.0.0), 
+   libxext-dev,
quilt,
docbook-to-man
 Standards-Version: 3.9.5
@@ -15,7 +16,7 @@
 
 Package: libwildmagic-dev
 Section: libdevel
-Architecture: any
+Architecture: linux-any
 Depends: ${misc:Depends}, 
  libwildmagic5 (= ${binary:Version})
 Description: libraries for mathematics, physics, numerical methods - dev files
@@ -41,7 +42,7 @@
  This package ships the library development files.
 
 Package: libwildmagic5
-Architecture: any
+Architecture: linux-any
 Depends: libwildmagic-common (= ${source:Version}),
  ${shlibs:Depends}, 
  ${misc:Depends}
@@ -68,7 +69,7 @@
 Package: libwildmagic5-dbg
 Section: debug
 Priority: extra
-Architecture: any
+Architecture: linux-any
 Depends: libwildmagic-common (= ${source:Version}),
  libwildmagic5 (= ${binary:Version}),
  ${misc:Depends}
@@ -113,7 +114,7 @@
 
 
 Package: libwildmagic-examples
-Architecture: any
+Architecture: linux-any
 Depends: ${shlibs:Depends}, ${misc:Depends}, 
  libwildmagic5 (= ${binary:Version})
 Suggests: 

Bug#956013: Fails to install

[Dr. Tobias Quathamer]

Am 06.04.20 um 08:38 schrieb David Prévot:
> Hi,
> 
> Thanks for updating those translations. Unfortunately, there is an
> unhandled upgrade path (missing Breaks and Replace on manpages-fr-extra
> (<< 20151231something), and of course the manpages-fr-extra counterpart
> update).

Hi David,

thanks for reporting this bug. Yes, I've thought about this during the
preparation of this package. However, I forgot to actually add the
-extra package for French. Hrm.

I'll correct this with another upload, probably tomorrow. And I'll ask
ftpmaster if they would be willing to fast-track this package, as it
will end up in NEW again.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#925798: marked as done (ortp: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 12:04:27 +
with message-id 
and subject line Bug#925798: fixed in ortp 1:1.0.2-1.1
has caused the Debian Bug report #925798,
regarding ortp: ftbfs with GCC-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
925798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ortp
Version: 1:1.0.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/ortp_1.0.2-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -Dortp_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC-Wall 
-Wuninitialized -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/ortp.dir/extremum.c.o   -c /<>/src/extremum.c
[ 14%] Building C object src/CMakeFiles/ortp-static.dir/congestiondetector.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -I/<>/include 
-I/<>/src -I/<>/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall 
-Wuninitialized -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/ortp-static.dir/congestiondetector.c.o   -c 
/<>/src/congestiondetector.c
[ 16%] Building C object src/CMakeFiles/ortp.dir/jitterctl.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -Dortp_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC-Wall 
-Wuninitialized -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/ortp.dir/jitterctl.c.o   -c /<>/src/jitterctl.c
[ 18%] Building C object src/CMakeFiles/ortp.dir/kalmanrls.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -Dortp_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC-Wall 
-Wuninitialized -Werror -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/ortp.dir/kalmanrls.c.o   -c /<>/src/kalmanrls.c
[ 19%] Building C object src/CMakeFiles/ortp.dir/logging.c.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DBCTBX_STATIC 
-DHAVE_CONFIG_H -DORTP_EXPORTS -DORTP_STATIC -Dortp_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu  -g -O2 

Processed: fixed-upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 955660 + fixed-upstream
Bug #955660 [src:mender-client] mender-client: FTBFS: app.DeploymentHook does 
not implement 
"github.com/mendersoftware/log/vendor/github.com/sirupsen/logrus".Hook (wrong 
type for Fire method)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
955660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#944181: marked as done (ghdl: non-standard gcc/g++ used for build (gcc-8))

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 11:49:22 +
with message-id 
and subject line Bug#944181: fixed in ghdl 0.37+dfsg-1
has caused the Debian Bug report #944181,
regarding ghdl: non-standard gcc/g++ used for build (gcc-8)
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.)


-- 
944181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghdl
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-8, gcc-8-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-9/g++-9.

Please keep this report open until the package uses the default
compiler version (or gcc-9) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-8 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.37+dfsg-1
Done: Jonathan McDowell 

We believe that the bug you reported is fixed in the latest version of
ghdl, 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.
Jonathan McDowell  (supplier of updated ghdl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 11:57:15 +0100
Source: ghdl
Architecture: source
Version: 0.37+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Closes: 930890 944181 952110
Changes:
 ghdl (0.37+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 * Refresh modify-install-paths
 * Remove patch allowing LLVM 8 (upstreamed)
 * Fixes build with LLVM 9 (Closes: #952110)
 * Update wrapper for newer releases. Thanks to Pavel Pisa (Closes: #930890)
   * Switch to GCC 9 (Closes: #944181)
Checksums-Sha1:
 060b904cdb0a1918371fc846308a0ac78f632112 2496 ghdl_0.37+dfsg-1.dsc
 40396c115770893eb638a169b14d4bd20875a401 2800780 ghdl_0.37+dfsg.orig.tar.xz
 57c0edad56e41e6bad45e5f86374a2adb6029e1b 17512 ghdl_0.37+dfsg-1.debian.tar.xz
 750a6468c7ea0ba48799bfa1fc3cbddf60d17cde 8972 ghdl_0.37+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 dcd83f3de4d8ece892dbd751e792c83571c4a413753bdd1aac3635e7dbd543b1 2496 
ghdl_0.37+dfsg-1.dsc
 8e784b42f23f41cf2cd207e0f0b09fee5a6380542b91b001f0e27185daba7498 2800780 
ghdl_0.37+dfsg.orig.tar.xz
 820a5bc2ac3bb2facd8ba4d17a7f70b7bd782382807a65c1156e34d3a0644de0 17512 
ghdl_0.37+dfsg-1.debian.tar.xz
 26f9a1f30fbddefe207a2c942e2708647fd8a34c015553f9e9c49c353a5d426a 8972 
ghdl_0.37+dfsg-1_amd64.buildinfo
Files:
 f8438d1948b3cc5ccfdbc5cb53db663d 2496 electronics optional ghdl_0.37+dfsg-1.dsc
 19f7c17a7898cce7614a6fa188c23dd7 2800780 electronics optional 
ghdl_0.37+dfsg.orig.tar.xz
 4c07d07b84e7566880cb8d10d0ff4159 17512 electronics optional 
ghdl_0.37+dfsg-1.debian.tar.xz
 7a96288a1fb57e9c9a52e19adc85780d 8972 electronics optional 
ghdl_0.37+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAl6LE50RHG5vb2RsZXNA
ZWFydGgubGkACgkQSgDzSK903QIUbg/+M31NfSR+NQN2C09TRROLMwAaljFLR1oX
n7sbHvMl/I0xhh5bYsSao8c5XDGDkhhWgOHh+4pAjVBcqPpUnlfUNZcA6uLK2zf6
bF/IvMpfyFaQjd4PVP61A7KjoPRCWlGuZFBR1m2HWjsvSDihTwJXtLWu6NKII76/
d0Ww7kAtUlJ6KXEYAc0B0byIC7VyAiy5yorLu3sQeJe9mI1bTDJRrVB8lA5iF464
iQ8i7HEULI/chbs8hc9gCNOJGxuLlp+XWLKIT0g7iOjqP0J8KnezoGfeLwtJ0hdy
34kK3KBCyUE/dMaE8RC305SK5Er4LmwZNkrKqbnA4h7tLM0gsf0PZCAPof9oCpER
0q59mSHDSqvtWLnfmVr7g0aKgwbMFoa6er6eosyOMSDF6JRenkz9XEESAG8NC2bQ
5zFIG8ozhZobtECWnORtXZdZEJVp6cpXtGs0k4fkpmYyMiYR+qkzEgjeSqNfkK04
DCn5N54MyZyn5m3zLUBfJgCCqCwV6r36XlEchvPV4Jkm43AP36HeC+1EfWXDselo
R/qJlvFJaxDunPRAZdegoAkCGGNstLeP8qVxiNWINTHTEsjdx+Fd/U4s/vy5D0Nf
WpqSVjGbxDl3WPT271+CxqqumCsjTN5UQNQjNXos/bAlxDgD+oarwO1OYz98YvQI
JPkCpeZXlDM=
=c6CB
-END PGP SIGNATURE End Message ---

Bug#952110: marked as done (ghdl FTBFS with LLVM 9)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 11:49:22 +
with message-id 
and subject line Bug#952110: fixed in ghdl 0.37+dfsg-1
has caused the Debian Bug report #952110,
regarding ghdl FTBFS with LLVM 9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghdl
Version: 0.35+git20181129+dfsg-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=ghdl

...

Configuring with llvm backend

if [ -n "1" ]; then \
cd /<>/builddir/llvm; \
../../configure --srcdir=../.. --prefix=/usr \
--libdir=lib/ghdl/llvm --incdir=lib/ghdl/include \
--enable-openieee --with-llvm-config; \
fi
Build machine is: x86_64-linux-gnu
Unhandled version llvm 9.0.1
make[1]: *** [debian/rules:64: override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.37+dfsg-1
Done: Jonathan McDowell 

We believe that the bug you reported is fixed in the latest version of
ghdl, 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.
Jonathan McDowell  (supplier of updated ghdl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 11:57:15 +0100
Source: ghdl
Architecture: source
Version: 0.37+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Closes: 930890 944181 952110
Changes:
 ghdl (0.37+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 * Refresh modify-install-paths
 * Remove patch allowing LLVM 8 (upstreamed)
 * Fixes build with LLVM 9 (Closes: #952110)
 * Update wrapper for newer releases. Thanks to Pavel Pisa (Closes: #930890)
   * Switch to GCC 9 (Closes: #944181)
Checksums-Sha1:
 060b904cdb0a1918371fc846308a0ac78f632112 2496 ghdl_0.37+dfsg-1.dsc
 40396c115770893eb638a169b14d4bd20875a401 2800780 ghdl_0.37+dfsg.orig.tar.xz
 57c0edad56e41e6bad45e5f86374a2adb6029e1b 17512 ghdl_0.37+dfsg-1.debian.tar.xz
 750a6468c7ea0ba48799bfa1fc3cbddf60d17cde 8972 ghdl_0.37+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 dcd83f3de4d8ece892dbd751e792c83571c4a413753bdd1aac3635e7dbd543b1 2496 
ghdl_0.37+dfsg-1.dsc
 8e784b42f23f41cf2cd207e0f0b09fee5a6380542b91b001f0e27185daba7498 2800780 
ghdl_0.37+dfsg.orig.tar.xz
 820a5bc2ac3bb2facd8ba4d17a7f70b7bd782382807a65c1156e34d3a0644de0 17512 
ghdl_0.37+dfsg-1.debian.tar.xz
 26f9a1f30fbddefe207a2c942e2708647fd8a34c015553f9e9c49c353a5d426a 8972 
ghdl_0.37+dfsg-1_amd64.buildinfo
Files:
 f8438d1948b3cc5ccfdbc5cb53db663d 2496 electronics optional ghdl_0.37+dfsg-1.dsc
 19f7c17a7898cce7614a6fa188c23dd7 2800780 electronics optional 
ghdl_0.37+dfsg.orig.tar.xz
 4c07d07b84e7566880cb8d10d0ff4159 17512 electronics optional 
ghdl_0.37+dfsg-1.debian.tar.xz
 7a96288a1fb57e9c9a52e19adc85780d 8972 electronics optional 
ghdl_0.37+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAl6LE50RHG5vb2RsZXNA
ZWFydGgubGkACgkQSgDzSK903QIUbg/+M31NfSR+NQN2C09TRROLMwAaljFLR1oX
n7sbHvMl/I0xhh5bYsSao8c5XDGDkhhWgOHh+4pAjVBcqPpUnlfUNZcA6uLK2zf6
bF/IvMpfyFaQjd4PVP61A7KjoPRCWlGuZFBR1m2HWjsvSDihTwJXtLWu6NKII76/
d0Ww7kAtUlJ6KXEYAc0B0byIC7VyAiy5yorLu3sQeJe9mI1bTDJRrVB8lA5iF464
iQ8i7HEULI/chbs8hc9gCNOJGxuLlp+XWLKIT0g7iOjqP0J8KnezoGfeLwtJ0hdy
34kK3KBCyUE/dMaE8RC305SK5Er4LmwZNkrKqbnA4h7tLM0gsf0PZCAPof9oCpER
0q59mSHDSqvtWLnfmVr7g0aKgwbMFoa6er6eosyOMSDF6JRenkz9XEESAG8NC2bQ
5zFIG8ozhZobtECWnORtXZdZEJVp6cpXtGs0k4fkpmYyMiYR+qkzEgjeSqNfkK04
DCn5N54MyZyn5m3zLUBfJgCCqCwV6r36XlEchvPV4Jkm43AP36HeC+1EfWXDselo
R/qJlvFJaxDunPRAZdegoAkCGGNstLeP8qVxiNWINTHTEsjdx+Fd/U4s/vy5D0Nf
WpqSVjGbxDl3WPT271+CxqqumCsjTN5UQNQjNXos/bAlxDgD+oarwO1OYz98YvQI
JPkCpeZXlDM=
=c6CB
-END PGP SIGNATURE End Message ---

Bug#952324: marked as done (ghdl: FTBFS: Unhandled version llvm 9.0.1)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 11:49:22 +
with message-id 
and subject line Bug#952110: fixed in ghdl 0.37+dfsg-1
has caused the Debian Bug report #952110,
regarding ghdl: FTBFS: Unhandled version llvm 9.0.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghdl
Version: 0.35+git20181129+dfsg-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/builddir/mcode'
> for d in src/std src/synopsys std/v87 ieee/v87 synopsys/v87 std/v93 ieee/v93 
> synopsys/v93 std/v08 src/openieee; do \
>   mkdir -p lib/ghdl/mcode/$d; \
> done
> make[2]: Leaving directory '/<>/builddir/mcode'
> Generate ortho_code-x86-flags.ads
> Generate elf_arch.ads
> Generate default_paths.ads
> 
> 
> Configuring with llvm backend
> 
> if [ -n "1" ]; then \
>   cd /<>/builddir/llvm; \
>   ../../configure --srcdir=../.. --prefix=/usr \
>   --libdir=lib/ghdl/llvm --incdir=lib/ghdl/include \
>   --enable-openieee --with-llvm-config; \
> fi
> Build machine is: x86_64-linux-gnu
> Unhandled version llvm 9.0.1
> make[1]: *** [debian/rules:64: override_dh_auto_configure] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/ghdl_0.35+git20181129+dfsg-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.37+dfsg-1
Done: Jonathan McDowell 

We believe that the bug you reported is fixed in the latest version of
ghdl, 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.
Jonathan McDowell  (supplier of updated ghdl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 11:57:15 +0100
Source: ghdl
Architecture: source
Version: 0.37+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Closes: 930890 944181 952110
Changes:
 ghdl (0.37+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 * Refresh modify-install-paths
 * Remove patch allowing LLVM 8 (upstreamed)
 * Fixes build with LLVM 9 (Closes: #952110)
 * Update wrapper for newer releases. Thanks to Pavel Pisa (Closes: #930890)
   * Switch to GCC 9 (Closes: #944181)
Checksums-Sha1:
 060b904cdb0a1918371fc846308a0ac78f632112 2496 ghdl_0.37+dfsg-1.dsc
 40396c115770893eb638a169b14d4bd20875a401 2800780 ghdl_0.37+dfsg.orig.tar.xz
 57c0edad56e41e6bad45e5f86374a2adb6029e1b 17512 ghdl_0.37+dfsg-1.debian.tar.xz
 750a6468c7ea0ba48799bfa1fc3cbddf60d17cde 8972 ghdl_0.37+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 dcd83f3de4d8ece892dbd751e792c83571c4a413753bdd1aac3635e7dbd543b1 2496 
ghdl_0.37+dfsg-1.dsc
 8e784b42f23f41cf2cd207e0f0b09fee5a6380542b91b001f0e27185daba7498 2800780 
ghdl_0.37+dfsg.orig.tar.xz
 820a5bc2ac3bb2facd8ba4d17a7f70b7bd782382807a65c1156e34d3a0644de0 17512 
ghdl_0.37+dfsg-1.debian.tar.xz
 26f9a1f30fbddefe207a2c942e2708647fd8a34c015553f9e9c49c353a5d426a 8972 
ghdl_0.37+dfsg-1_amd64.buildinfo
Files:
 f8438d1948b3cc5ccfdbc5cb53db663d 2496 electronics optional ghdl_0.37+dfsg-1.dsc
 19f7c17a7898cce7614a6fa188c23dd7 2800780 electronics optional 
ghdl_0.37+dfsg.orig.tar.xz
 4c07d07b84e7566880cb8d10d0ff4159 17512 electronics optional 
ghdl_0.37+dfsg-1.debian.tar.xz
 7a96288a1fb57e9c9a52e19adc85780d 8972 electronics optional 

Processed: Re: [Pkg-javascript-devel] Bug#956027: libjs-popper.js: Upgrading libjs-popper.js buster -> bullseye results in an empty /usr/share/javascript/popper.js

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #956027 [libjs-popper.js] libjs-popper.js: Upgrading libjs-popper.js buster 
-> bullseye results in an empty /usr/share/javascript/popper.js
Severity set to 'serious' from 'important'

-- 
956027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956028: wine-development: FTBFS on arm64, armel, armhf

[Gianfranco Costamagna]

Source: wine-development
Version: 5.5-3
Severity: serious

Hello, the 5.5-3 fixed amd64, but there still is a FTBFS because of install 
failure on arm* architectures.

following a snippet of the build log:


make[1]: Leaving directory '/<>'
   dh_install -a -O--parallel
install -d debian/.debhelper/generated/wine-development
install -d debian/.debhelper/generated/wine32-development
install -d debian/wine64-development//usr/lib/wine-development
cp --reflink=auto -a debian/tmp/usr/lib/wine-development/wine64 
debian/wine64-development//usr/lib/wine-development/
cp --reflink=auto -a ./debian/tmp/wineserver64 
debian/wine64-development/usr/lib/wine-development/
install -d debian/.debhelper/generated/wine64-development
install -d debian/.debhelper/generated/wine32-development-preloader
install -d debian/wine64-development-preloader//usr/lib/wine-development
cp --reflink=auto -a 
debian/tmp/usr/lib/wine-development/wine64-preloader 
debian/wine64-development-preloader//usr/lib/wine-development/
install -d debian/.debhelper/generated/wine64-development-preloader
install -d debian/.debhelper/generated/wine32-development-tools
install -d debian/wine64-development-tools//usr/lib/wine-development
cp --reflink=auto -a debian/tmp/usr/lib/wine-development/widl 
debian/tmp/usr/lib/wine-development/winebuild 
debian/tmp/usr/lib/wine-development/winecpp 
debian/tmp/usr/lib/wine-development/winedump 
debian/tmp/usr/lib/wine-development/wineg\+\+ 
debian/tmp/usr/lib/wine-development/winegcc 
debian/tmp/usr/lib/wine-development/winemaker 
debian/tmp/usr/lib/wine-development/wmc debian/tmp/usr/lib/wine-development/wrc 
debian/wine64-development-tools//usr/lib/wine-development/
install -d debian/wine64-development-tools/usr/bin
cp --reflink=auto -a ./debian/tmp/winegcc-development 
debian/tmp/usr/lib/wine-development/function_grep.pl 
debian/wine64-development-tools/usr/bin/
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.com" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.com
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.dll" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.dll
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.drv" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.drv
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.exe" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.exe
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.acm" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.acm
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.cpl" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.cpl
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.ocx" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.ocx
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.sys" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.sys
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/*/*.tlb" (tried in ., debian/tmp)

dh_install: warning: libwine-development missing files: 
debian/tmp/usr/lib/*/*/*.tlb
dh_install: error: missing files, aborting
install -d debian/.debhelper/generated/wine64-development-tools
install -d debian/.debhelper/generated/libwine-development
install -d debian/.debhelper/generated/libwine-development-dev
make: *** [debian/rules:122: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2



thanks

Gianfranco

Processed: gxneur: diff for NMU version 0.20.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 951971 + patch
Bug #951971 [src:gxneur] gxneur: FTBFS: gtktypeutils.h:236:1: error: 
‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 951971 + pending
Bug #951971 [src:gxneur] gxneur: FTBFS: gtktypeutils.h:236:1: error: 
‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.

-- 
951971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 953576 951722

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 953576 951722
Bug #953576 [src:dovecot] dovecot: flaky arm64 autopkgtest: 
debian/tests/usage/00_setup exited with return code 75
Bug #951722 [src:dovecot] autopkgtest suite flaky on arm64
Added tag(s) sid and bullseye.
Merged 951722 953576
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
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#951971: gxneur: diff for NMU version 0.20.0-2.1

[Adrian Bunk]

Control: tags 951971 + patch
Control: tags 951971 + pending

Dear maintainer,

I've prepared an NMU for gxneur (versioned as 0.20.0-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru gxneur-0.20.0/debian/changelog gxneur-0.20.0/debian/changelog
--- gxneur-0.20.0/debian/changelog	2018-09-12 01:14:50.0 +0300
+++ gxneur-0.20.0/debian/changelog	2020-04-06 12:45:46.0 +0300
@@ -1,3 +1,10 @@
+gxneur (0.20.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build without -Werror. (Closes: #951971)
+
+ -- Adrian Bunk   Mon, 06 Apr 2020 12:45:46 +0300
+
 gxneur (0.20.0-2) unstable; urgency=medium
 
   * d/control: Move Vcs-* to salsa.
diff -Nru gxneur-0.20.0/debian/patches/04-no-werror.patch gxneur-0.20.0/debian/patches/04-no-werror.patch
--- gxneur-0.20.0/debian/patches/04-no-werror.patch	1970-01-01 02:00:00.0 +0200
+++ gxneur-0.20.0/debian/patches/04-no-werror.patch	2020-04-06 12:45:46.0 +0300
@@ -0,0 +1,15 @@
+Description: Build without -Werror
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/951971
+
+--- gxneur-0.20.0.orig/configure.ac
 gxneur-0.20.0/configure.ac
+@@ -85,7 +85,7 @@ AC_DEFINE(PACKAGE_GSETTINGS_DIR, "com."
+ 
+ AC_DEFINE(KB_PROP_COMMAND, "/usr/bin/gnome-control-center region layouts", [Define keyboard properties command])
+ 
+-DEFAULT_CFLAGS="-Wall -Wextra -Werror -g0 -fPIC -std=gnu99"
++DEFAULT_CFLAGS="-Wall -Wextra -g0 -fPIC -std=gnu99"
+ AC_SUBST(DEFAULT_CFLAGS)
+ 
+ AC_OUTPUT([Makefile gxneur.desktop data/Makefile src/Makefile pixmaps/Makefile ui/Makefile po/Makefile.in])
diff -Nru gxneur-0.20.0/debian/patches/series gxneur-0.20.0/debian/patches/series
--- gxneur-0.20.0/debian/patches/series	2018-09-12 00:50:49.0 +0300
+++ gxneur-0.20.0/debian/patches/series	2020-04-06 12:45:46.0 +0300
@@ -1,3 +1,4 @@
 01-gconf.patch
 02-gconf.patch
 03-glib-deprecated.patch
+04-no-werror.patch

Bug#956017: gnome-maps: no results when searching for an address

[Keno Goertz]

Turns out geocode-glib uses https://nominatim.gnome.org, which is
currently down (I don't know since when). The more recent version of
GNOME maps doesn't use geocode-glib for geocoding, so it doesn't
experience this problem.

I will write a mail to the person hosting GNOME's nominatim service.


signature.asc
Description: This is a digitally signed message part

Processed: ortp: diff for NMU version 1:1.0.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 925798 + patch
Bug #925798 [src:ortp] ortp: ftbfs with GCC-9
Added tag(s) patch.
> tags 925798 + pending
Bug #925798 [src:ortp] ortp: ftbfs with GCC-9
Added tag(s) pending.

-- 
925798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#925798: ortp: diff for NMU version 1:1.0.2-1.1

[Sudip Mukherjee]

Control: tags 925798 + patch
Control: tags 925798 + pending

Dear maintainer,

I've prepared an NMU for ortp (versioned as 1:1.0.2-1.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru ortp-1.0.2/debian/changelog ortp-1.0.2/debian/changelog
--- ortp-1.0.2/debian/changelog 2018-10-10 21:50:59.0 +0100
+++ ortp-1.0.2/debian/changelog 2020-04-06 10:50:38.0 +0100
@@ -1,3 +1,10 @@
+ortp (1:1.0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC. (Closes: #925798)
+
+ -- Sudip Mukherjee   Mon, 06 Apr 2020 10:50:38 
+0100
+
 ortp (1:1.0.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ortp-1.0.2/debian/patches/fix_strcat.patch 
ortp-1.0.2/debian/patches/fix_strcat.patch
--- ortp-1.0.2/debian/patches/fix_strcat.patch  1970-01-01 01:00:00.0 
+0100
+++ ortp-1.0.2/debian/patches/fix_strcat.patch  2020-04-06 10:50:17.0 
+0100
@@ -0,0 +1,20 @@
+Description: use strcat() instead of strncat()
+ It is doing strncat() and the length mentioned is the full length of
+ the string. We can use strcat() instead of strncat() with full string.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/925798
+
+---
+
+--- ortp-1.0.2.orig/src/logging.c
 ortp-1.0.2/src/logging.c
+@@ -217,7 +217,7 @@ char * ortp_strcat_vprintf(char* dst, co
+   retlen = strlen(ret);
+ 
+   if ((dst = ortp_realloc(dst, dstlen+retlen+1)) != NULL){
+-  strncat(dst,ret,retlen);
++  strcat(dst,ret);
+   dst[dstlen+retlen] = '\0';
+   ortp_free(ret);
+   return dst;
diff -Nru ortp-1.0.2/debian/patches/series ortp-1.0.2/debian/patches/series
--- ortp-1.0.2/debian/patches/series2018-10-10 21:50:59.0 +0100
+++ ortp-1.0.2/debian/patches/series2020-04-06 10:50:30.0 +0100
@@ -1 +1,2 @@
 fix-spelling
+fix_strcat.patch

Processed: bug 951969 is forwarded to https://github.com/python-social-auth/social-app-django/issues/196

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 951969 
> https://github.com/python-social-auth/social-app-django/issues/196
Bug #951969 [src:social-auth-app-django] social-auth-app-django: FTBFS: 
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" 
--system=custom "--test-args={interpreter} ./manage.py test" returned exit code 
13
Set Bug forwarded-to-address to 
'https://github.com/python-social-auth/social-app-django/issues/196'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
951969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gkrellm-tz: diff for NMU version 0.8-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 951964 + patch
Bug #951964 [src:gkrellm-tz] gkrellm-tz: FTBFS: gtktypeutils.h:236:1: error: 
‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 951964 + pending
Bug #951964 [src:gkrellm-tz] gkrellm-tz: FTBFS: gtktypeutils.h:236:1: error: 
‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.

-- 
951964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951964: gkrellm-tz: diff for NMU version 0.8-1.1

[Adrian Bunk]

Control: tags 951964 + patch
Control: tags 951964 + pending

Dear maintainer,

I've prepared an NMU for gkrellm-tz (versioned as 0.8-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru gkrellm-tz-0.8/debian/changelog gkrellm-tz-0.8/debian/changelog
--- gkrellm-tz-0.8/debian/changelog	2016-04-15 12:34:16.0 +0300
+++ gkrellm-tz-0.8/debian/changelog	2020-04-06 12:35:25.0 +0300
@@ -1,3 +1,10 @@
+gkrellm-tz (0.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build without -Werror. (Closes: #951964)
+
+ -- Adrian Bunk   Mon, 06 Apr 2020 12:35:25 +0300
+
 gkrellm-tz (0.8-1) unstable; urgency=low
 
   * Initial release (Closes: #743902)
diff -Nru gkrellm-tz-0.8/debian/patches/install.patch gkrellm-tz-0.8/debian/patches/install.patch
--- gkrellm-tz-0.8/debian/patches/install.patch	2016-04-14 00:16:45.0 +0300
+++ gkrellm-tz-0.8/debian/patches/install.patch	2020-04-06 09:29:24.0 +0300
@@ -12,7 +12,7 @@
 -CFLAGS	= -fPIC -Wall -Werror -g $(GKRELLM_CFLAGS) -DVERSION=\"$(VERSION)\"
 -LDFLAGS	= -shared $(GKRELLM_LDFLAGS)
 +CFLAGS += $(shell dpkg-buildflags --get CPPFLAGS)
-+CFLAGS += -fPIC -Wall -Werror -g $(GKRELLM_CFLAGS) -DVERSION=\"$(VERSION)\"
++CFLAGS += -fPIC -Wall -g $(GKRELLM_CFLAGS) -DVERSION=\"$(VERSION)\"
 +LDFLAGS += -shared $(GKRELLM_LDFLAGS)
  
  OBJS	= list.o config.o gkrellm-tz.o

Bug#956017: gnome-maps: no results when searching for an address

[Keno Goertz]

I dug into this a little and it seems that this is a problem with
geocode-glib: An exception is caught at geocodeService.js:47 saying:

Gio.IOErrorEnum: Service Unavailable

> when entering an address into the search box of GNOME Maps on Debian
> Stable, I get a loading animation for a few seconds and then "No
> results
> found". The same applies for entering an address into the start or
> end
> point of the routing panel.
> 
> This problem is fixed in newer versions of the package, but I believe
> it
> should also get a bug fix for stable because in its current state,
> GNOME
> Maps doesn't provide the basic functionality users would want from a
> map
> application.
> 
> I'm not quite sure whether Debian provides bug fixes for stable in
> situations like this, though, so sorry if I did something wrong with
> this bug report.


signature.asc
Description: This is a digitally signed message part

Bug#956020: mydumper FTBFS on armel/armhf/mips/mipsel , needs to link against libm.

[peter green]

Package: mydumper
Version: 0.9.5-1
Severity: serious

(note on versioning, this failure was seen with 1.1 I strongly suspect this 
also affects -1, however -1 is currently unbuildable in testing due to a 
missing build-dependency. The history on the reproducible builds site shows 
failures on armhf for -1 but I don't think it has logs available for them).

mydumper is failing to build on armel, armhf, mips and mipsel (and a bunch of 
non-release errors) with the following error.


/usr/bin/cc -Wall -Wno-deprecated-declarations -Wunused -Wwrite-strings 
-Wno-strict-aliasing -Wextra -Wshadow -Werror -O3 -g -I/usr/include/mariadb 
-I/usr/include/mariadb/mysql  -Wl,-z,relro -rdynamic 
CMakeFiles/mydumper.dir/mydumper.c.o CMakeFiles/mydumper.dir/server_detect.c.o 
CMakeFiles/mydumper.dir/g_unix_signal.c.o 
CMakeFiles/mydumper.dir/connection.c.o CMakeFiles/mydumper.dir/getPassword.c.o  
-o mydumper  -lmariadb -lglib-2.0 -lgthread-2.0 -lpcre -lz -lstdc++
/usr/bin/ld: CMakeFiles/mydumper.dir/mydumper.c.o: undefined reference to 
symbol 'ceilf@@GLIBC_2.4'
/usr/bin/ld: /lib/arm-linux-gnueabi/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/mydumper.dir/build.make:152: mydumper] Error 1

This is generally caused by using math functions and forgetting to link against 
libm, you get away with this on some architectures due to use of inline 
implementations by glibc. Please modify your buildsystem to link against libm

Bug#956019: mlpy: needs a source-only upload

[peter green]

Package: mlpy
Version: 3.5.0+ds-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only upload so your package can migrate.

Bug#914151: marked as done (dlz-ldap-enum FTBFS with bind9 9.11.5)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 09:03:41 +
with message-id 
and subject line Bug#914151: fixed in dlz-ldap-enum 1.1.0-1.1
has caused the Debian Bug report #914151,
regarding dlz-ldap-enum FTBFS with bind9 9.11.5
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.)


-- 
914151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dlz-ldap-enum
Version: 1.1.0-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dlz-ldap-enum.html

...
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/build/1st/dlz-ldap-enum-1.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o dlz_ldap_enum_driver.lo 
dlz_ldap_enum_driver.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/build/1st/dlz-ldap-enum-1.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c dlz_ldap_enum_driver.c  -fPIC -DPIC -o 
.libs/dlz_ldap_enum_driver.o
In file included from dlz_ldap_enum_driver.c:73:
sdlz_helper.h:60:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t   direct;
  ^
dlz_ldap_enum_driver.c:357:19: error: unknown type name 'isc_boolean_t'; did 
you mean 'isc_socket_t'?
void *ptr, isc_boolean_t allnodes, char *tel,
   ^
   isc_socket_t
dlz_ldap_enum_driver.c: In function 'ldap_get_results':
dlz_ldap_enum_driver.c:862:12: warning: implicit declaration of function 
'ldap_process_results'; did you mean 'ldap_get_results'? 
[-Wimplicit-function-declaration]
   result = ldap_process_results((LDAP *) dbi->dbconn, ldap_msg,
^~~~
ldap_get_results
dlz_ldap_enum_driver.c:864:17: error: 'isc_boolean_true' undeclared (first use 
in this function); did you mean 'isc_buffer_free'?
ptr, isc_boolean_true, NULL,
 ^~~~
 isc_buffer_free
dlz_ldap_enum_driver.c:864:17: note: each undeclared identifier is reported 
only once for each function it appears in
dlz_ldap_enum_driver.c:871:17: error: 'isc_boolean_false' undeclared (first use 
in this function); did you mean 'isc_buffer_base'?
ptr, isc_boolean_false, tel,
 ^
 isc_buffer_base
make[2]: *** [Makefile:489: dlz_ldap_enum_driver.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: dlz-ldap-enum
Source-Version: 1.1.0-1.1
Done: Tobias Frost 

We believe that the bug you reported is fixed in the latest version of
dlz-ldap-enum, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated dlz-ldap-enum 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, 04 Apr 2020 10:36:06 +0200
Source: dlz-ldap-enum
Architecture: source
Version: 1.1.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Tobias Frost 
Closes: 914151 953450 955722
Changes:
 dlz-ldap-enum (1.1.0-1.1) unstable; urgency=medium
 .
   * Non maintainer upload.
 .
   [ Peter Michael Green ]
   * Add #include  to sdlz_helper.h (Closes: #914151)
 .
   [ Tobias Frost ]
   * Updating the dlz-ldap-enum Uploaders list" (Closes: #953450)
   * Fixing defunct VCS fields by pointing them to salsa.d.o. (Closes: #955722)
Checksums-Sha1:
 cb85b9887d607bcc323c1535e5319297040c82f2 1996 dlz-ldap-enum_1.1.0-1.1.dsc
 5e9d134bf397074fda62a14f586030a5a67db411 3160 
dlz-ldap-enum_1.1.0-1.1.debian.tar.xz
 c0394ade92f0c98b99974a94188a2597cddac3c1 5333 
dlz-ldap-enum_1.1.0-1.1_source.buildinfo
Checksums-Sha256:
 f19cbe9ea020bd47265fe99b7cb320671b9b206c731c2268b4193a5872b5 1996 
dlz-ldap-enum_1.1.0-1.1.dsc
 c20f7fffa6a7a98d3df039ee5bc09c2e70a92deaa72bcd770188f21de9002d92 3160 
dlz-ldap-enum_1.1.0-1.1.debian.tar.xz
 bcb95065f8184a6303c5994b4db709b0b72e7ab35b906bb332d15ef8b02a9148 5333 
dlz-ldap-enum_1.1.0-1.1_source.buildinfo
Files:
 

Bug#813015: marked as done (mlpy: FTBFS: error: unbalanced parenthesis)

[Debian Bug Tracking System]

Your message dated Mon, 6 Apr 2020 10:01:03 +0100
with message-id 
and subject line mlpy: FTBFS: error: unbalanced parenthesis
has caused the Debian Bug report #813015,
regarding mlpy: FTBFS: error: unbalanced parenthesis
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.)


-- 
813015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlpy
Version: 2.2.0~dfsg1-3
Severity: serious


Dear maintainer,

you package currently fails to build from source:

PYTHONPATH=/build/mlpy-2.2.0~dfsg1/build/lib.linux-x86_64-2.7 /usr/bin/make -C 
docs html latex
make[1]: Entering directory '/build/mlpy-2.2.0~dfsg1/docs'
mkdir -p build/html build/doctrees
sphinx-build -b html -d build/doctrees   source build/html
Running Sphinx v1.3.4
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 17 source files that are out of date
updating environment: 17 added, 0 changed, 0 removed
reading sources... [  5%] classification
reading sources... [ 11%] clustering

Exception occurred:
  File "/usr/lib/python2.7/re.py", line 251, in _compile
raise error, v # invalid expression
error: unbalanced parenthesis
The full traceback has been saved in /tmp/sphinx-err-9SC3Xq.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
Makefile:29: recipe for target 'html' failed
make[1]: *** [html] Error 1
make[1]: Leaving directory '/build/mlpy-2.2.0~dfsg1/docs'
debian/rules:18: recipe for target 'doc-stamp' failed
make: *** [doc-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---

Version: 3.5.0+ds-1

The new version built successfully on all release architectures (and most of 
the non-release ones too).--- End Message ---

Bug#956018: iptables-converter needs a source-only upload

[peter green]

Package: iptables-converter
Version: 0.9.8-1.1
Severity: serious
x-debugs-cc: z...@debian.org

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only upload so your package can migrate.

Bug#956017: gnome-maps: no results when searching for an address

[Keno Goertz]

Package: gnome-maps
Version: 3.30.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when entering an address into the search box of GNOME Maps on Debian
Stable, I get a loading animation for a few seconds and then "No results
found". The same applies for entering an address into the start or end
point of the routing panel.

This problem is fixed in newer versions of the package, but I believe it
should also get a bug fix for stable because in its current state, GNOME
Maps doesn't provide the basic functionality users would want from a map
application.

I'm not quite sure whether Debian provides bug fixes for stable in
situations like this, though, so sorry if I did something wrong with
this bug report.


-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-maps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  geoclue-2.0  2.5.2-1
ii  gir1.2-champlain-0.120.12.16-3
ii  gir1.2-clutter-1.0   1.26.2+dfsg-10
ii  gir1.2-cogl-1.0  1.22.2-6
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-geocodeglib-1.0   3.26.1-1
ii  gir1.2-gfbgraph-0.2  0.2.3-3
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-goa-1.0   3.30.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gtkchamplain-0.12 0.12.16-3
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-rest-0.7  0.8.1-1
ii  gir1.2-secret-1  0.18.7-1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-webkit2-4.0   2.26.4-1~deb10u2
ii  gjs  1.54.3-1
ii  libc62.28-10
ii  libchamplain-0.12-0  0.12.16-3
ii  libfolks25   0.11.4-1+b2
ii  libgee-0.8-2 0.20.1-2
ii  libgeocode-glib0 3.26.1-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libglib2.0-bin   2.58.3-2+deb10u2
ii  librest-0.7-00.8.1-1
ii  libxml2  2.9.4+dfsg1-7+b3

gnome-maps recommends no packages.

gnome-maps suggests no packages.

-- no debconf information

Bug#955583: marked as done (ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String into Integer)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 14:01:21 +0530
with message-id <9cyc8q.o6ddz4xpy...@onenetbeyond.org>
and subject line ruby-defaults now Breaks against ruby-bootsnap in testing
has caused the Debian Bug report #955583,
regarding ruby-defaults breaks ruby-mousetrap-rails autopkgtest: TypeError: no 
implicit conversion of String into Integer
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.)


-- 
955583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-defaults, ruby-mousetrap-rails
Control: found -1 ruby-defaults/1:2.7
Control: found -1 ruby-mousetrap-rails/1.4.6-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ruby-defaults the autopkgtest of
ruby-mousetrap-rails fails in testing when that autopkgtest is run with
the binary packages of ruby-defaults from unstable. It passes when run
with only packages from testing. In tabular form:

   passfail
ruby-defaults  from testing1:2.7
ruby-mousetrap-rails   from testing1.4.6-6
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of ruby-defaults to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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=ruby-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-mousetrap-rails/4779223/log.gz

Bundle complete! 19 Gemfile dependencies, 77 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
+ bundle exec rake assets:precompile
rake aborted!
TypeError: no implicit conversion of String into Integer
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in
`block in require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in
`require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in
`block in require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.4.1/lib/active_support/dependencies.rb:291:in
`require'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/boot.rb:4:in
`require'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/boot.rb:4:in
`'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/application.rb:1:in
`require_relative'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/config/application.rb:1:in
`'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/Rakefile:4:in
`require_relative'
/tmp/autopkgtest-lxc.ihw859d4/downtmp/autopkgtest_tmp/foo/Rakefile:4:in
`'
(See full trace by running task with --trace)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

fixed 955583 1:2.7+1--- End Message ---

Processed: ruby-defaults now Breaks against ruby-bootsnap in testing

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 955583 1:2.7+1
Bug #955583 [src:ruby-defaults, src:ruby-mousetrap-rails] ruby-defaults breaks 
ruby-mousetrap-rails autopkgtest: TypeError: no implicit conversion of String 
into Integer
The source 'ruby-mousetrap-rails' and version '1:2.7+1' do not appear to match 
any binary packages
Marked as fixed in versions ruby-defaults/1:2.7+1 and 
ruby-mousetrap-rails/1:2.7+1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
955583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955640: marked as done (r-cran-uwot: autopkgtest regression: Index size is not a multiple of vector size)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 08:21:46 +
with message-id 
and subject line Bug#955640: fixed in r-cran-rcppannoy 0.0.16-2
has caused the Debian Bug report #955640,
regarding r-cran-uwot: autopkgtest regression: Index size is not a multiple of 
vector size
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.)


-- 
955640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-uwot
Version: 0.1.8-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 r-cran-uwot the autopkgtest of r-cran-uwot fails
in testing when that autopkgtest is run with the binary packages of
r-cran-uwot from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
r-cran-uwotfrom testing0.1.8-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=r-cran-uwot

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-uwot/4784519/log.gz
autopkgtest [23:18:13]: test run-unit-test: [---
BEGIN TEST testthat.R

R version 3.6.3 (2020-02-29) -- "Holding the Windsock"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(uwot)
Loading required package: Matrix
>
> test_check("uwot")
Index size is not a multiple of vector size: No such file or directory (2)
── 1. Error: (unknown) (@test_output.R#232)
───
search_k/n_trees settings were unable to find 4 neighbors for all items.
Backtrace:
 1. uwot::umap(...)
 2. uwot:::uwot(...)
 3. uwot:::data2set(...)
 4. uwot:::x2set(...)
 5. uwot:::x2nn(...)
 6. uwot:::find_nn(...)
 7. uwot:::annoy_nn(...)
 8. uwot:::annoy_search(...)
 9. uwot:::annoy_search_parallel(...)

══ testthat results
═══
[ OK: 414 | SKIPPED: 0 | WARNINGS: 0 | FAILED: 1 ]
1. Error: (unknown) (@test_output.R#232)

Error: testthat unit tests failed
Execution halted
autopkgtest [23:18:44]: test run-unit-test: ---]




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-rcppannoy
Source-Version: 0.0.16-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-rcppannoy, 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 955...@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-cran-rcppannoy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 10:01:55 +0200
Source: r-cran-rcppannoy
Architecture: source
Version: 0.0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 955640
Changes:
 r-cran-rcppannoy (0.0.16-2) unstable; urgency=medium
 .
   * Team upload.
   * Add Breaks: r-cran-uwot (<< 0.1.8-1~) (Closes: #955640)
Checksums-Sha1:
 fab2598939e12964cac5438332ef3596af7d3d9a 2118 r-cran-rcppannoy_0.0.16-2.dsc
 af38082663e5c9b784a2ab73f081976e371e25ac 2592 
r-cran-rcppannoy_0.0.16-2.debian.tar.xz
 

Bug#954813: marked as done (r-cran-rlang breaks r-cran-ggplot2 autopkgtest: `out` not identical to `exp`)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 08:21:53 +
with message-id 
and subject line Bug#954813: fixed in r-cran-rlang 0.4.5-2
has caused the Debian Bug report #954813,
regarding r-cran-rlang breaks r-cran-ggplot2 autopkgtest: `out` not identical 
to `exp`
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.)


-- 
954813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rlang, r-cran-ggplot2
Control: found -1 r-cran-rlang/0.4.5-1
Control: found -1 r-cran-ggplot2/3.2.1+dfsg-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of r-cran-rlang the autopkgtest of r-cran-ggplot2
fails in testing when that autopkgtest is run with the binary packages
of r-cran-rlang from unstable. It passes when run with only packages
from testing. In tabular form:

   passfail
r-cran-rlang   from testing0.4.5-1
r-cran-ggplot2 from testing3.2.1+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of r-cran-rlang to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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=r-cran-rlang

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ggplot2/4633837/log.gz

autopkgtest [21:29:08]: test run-unit-test: [---
BEGIN TEST testthat.R

R version 3.6.3 (2020-02-29) -- "Holding the Windsock"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(ggplot2)
>
> test_check("ggplot2")
── 1. Failure: as_facets_list() coerces lists (@test-facet-.r#40)
─
`out` not identical to `exp`.
Component 3: Attributes: < Component “class”: Lengths (2, 1) differ
(string compare on first 1) >

══ testthat results
═══
[ OK: 1072 | SKIPPED: 113 | WARNINGS: 0 | FAILED: 1 ]
1. Failure: as_facets_list() coerces lists (@test-facet-.r#40)

Error: testthat unit tests failed
Execution halted
autopkgtest [21:29:47]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-rlang
Source-Version: 0.4.5-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-rlang, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated r-cran-rlang package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 09:51:00 +0200
Source: r-cran-rlang
Architecture: source
Version: 0.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 954813
Changes:
 r-cran-rlang (0.4.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Add Breaks: r-cran-ggplot2 (<< 3.3.0+dfsg-1~) (Closes: #954813)
   * Testsuite: autopkgtest-pkg-r (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
Checksums-Sha1:
 

Bug#955740: marked as done (kdenlive crash on startup)

[Debian Bug Tracking System]

Your message dated Mon, 6 Apr 2020 10:20:27 +0200
with message-id 
and subject line Re: Bug#955740: kdenlive crash on startup - no longer crashing 
after machine reboot
has caused the Debian Bug report #955740,
regarding kdenlive crash on startup
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.)


-- 
955740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdenlive
Version: 19.12.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
trying to run kdenlive

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
typed kdenlive at the bash prompt.

   * What was the outcome of this action?
run aborted

   * What outcome did you expect instead?
I expected kdenlive to run as normal

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kdenlive depends on:
ii  ffmpeg 7:4.2.2-1+b1
ii  kded5  5.62.0-1+b1
ii  kdenlive-data  19.12.3-1
ii  kinit  5.62.0-1+b1
ii  kio5.62.1-2+b1
ii  libc6  2.30-4
ii  libkf5archive5 5.62.0-1
ii  libkf5bookmarks5   5.62.0-1+b1
ii  libkf5completion5  5.62.0-1+b1
ii  libkf5configcore5  5.62.0-1+b1
ii  libkf5configgui5   5.62.0-1+b1
ii  libkf5configwidgets5   5.62.0-1+b1
ii  libkf5coreaddons5  5.62.0-1
ii  libkf5crash5   5.62.0-1+b1
ii  libkf5dbusaddons5  5.62.0-1
ii  libkf5declarative5 5.62.0-1+b2
ii  libkf5filemetadata35.62.0-1+b1
ii  libkf5guiaddons5   5.62.0-2
ii  libkf5i18n55.62.0-1
ii  libkf5iconthemes5  5.62.0-1+b1
ii  libkf5itemviews5   5.62.0-1+b1
ii  libkf5jobwidgets5  5.62.0-1+b1
ii  libkf5kiocore5 5.62.1-2+b1
ii  libkf5kiofilewidgets5  5.62.1-2+b1
ii  libkf5kiowidgets5  5.62.1-2+b1
ii  libkf5newstuff55.62.0-1+b1
ii  libkf5notifications5   5.62.0-1+b1
ii  libkf5notifyconfig55.62.0-1+b1
ii  libkf5purpose-bin  5.62.0-2+b1
ii  libkf5purpose5 5.62.0-2+b1
ii  libkf5service-bin  5.62.0-1
ii  libkf5service5 5.62.0-1
ii  libkf5solid5   5.62.0-2
ii  libkf5widgetsaddons5   5.62.0-1+b1
ii  libkf5xmlgui5  5.62.0-1+b1
ii  libmlt++3  6.20.0-2+b1
ii  libmlt66.20.0-2+b1
ii  libqt5concurrent5  5.12.5+dfsg-9
ii  libqt5core5a   5.12.5+dfsg-9
ii  libqt5dbus55.12.5+dfsg-9
ii  libqt5gui5 5.12.5+dfsg-9
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5network5 5.12.5+dfsg-9
ii  libqt5qml5 5.12.5-5
ii  libqt5quick5   5.12.5-5
ii  libqt5quickwidgets55.12.5-5
ii  libqt5svg5 5.12.5-2
ii  libqt5webkit5  5.212.0~alpha4-1
ii  libqt5widgets5 5.12.5+dfsg-9
ii  libqt5xml5 5.12.5+dfsg-9
ii  librttr-core0.9.6  0.9.6+dfsg1-3
ii  libstdc++6 10-20200324-1
ii  melt   6.20.0-2+b1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2   5.12.5-5
ii  qml-module-qtquick-controls5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs 5.12.5-1+b1
ii  qml-module-qtquick-layouts 5.12.5-5
ii  qml-module-qtquick-window2 5.12.5-5
ii  qml-module-qtquick25.12.5-5

Versions of packages kdenlive recommends:
ii  breeze-icon-theme  4:5.62.0-1
pn  dvdauthor  
pn  dvgrab 
ii  frei0r-plugins 1.7.0-1
pn  genisoimage
pn  

Bug#955576: marked as done (src:praat: fails to migrate to testing for too long: ftbfs mips64el)

[Debian Bug Tracking System]

Your message dated Mon, 6 Apr 2020 10:04:19 +0200
with message-id <20200406080419.gg24...@laboissiere.net>
and subject line Re: Bug#955576: src:praat: fails to migrate to testing for too 
long: ftbfs mips64el
has caused the Debian Bug report #955576,
regarding src:praat: fails to migrate to testing for too long: ftbfs mips64el
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.)


-- 
955576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: praat
Version: 6.1.08-1
Severity: serious
Control: fixed -1 6.1.09-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:praat in its
current version in unstable has been trying to migrate for 62 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 marked the version in unstable as fixing this bug, 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=praat




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Control: fixed -1 6.1.10-1

I am hereby closing this bug report.  Version 6.1.10-1 of the package 
built fine on all architectures.


Best,

Rafael Laboissière

* Paul Gevers  [2020-04-02 20:45]:


Source: praat
Version: 6.1.08-1
Severity: serious
Control: fixed -1 6.1.09-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:praat in its 
current version in unstable has been trying to migrate for 62 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 marked the version in unstable as fixing this bug, 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=praat


--- End Message ---

Processed: Bug#955640 marked as pending in r-cran-rcppannoy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #955640 [src:r-cran-uwot] r-cran-uwot: autopkgtest regression: Index size 
is not a multiple of vector size
Added tag(s) pending.

-- 
955640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955640: marked as pending in r-cran-rcppannoy

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #955640 in r-cran-rcppannoy 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/r-pkg-team/r-cran-rcppannoy/-/commit/0d54e65c44a5d9843ebde07895c0913683d6e73d


Add Breaks: r-cran-uwot (<< 0.1.8-1~) (Closes: #955640)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/955640

Bug#955687: marked as done (missing libgudev-1.0-dev dependency)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 09:13:58 +0200
with message-id <1612822.ZUa6N3rmVu@thyrus>
and subject line Re: [Pkg-kde-extras] Bug#955687: Bug#955687: wacomtablet: 
FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
has caused the Debian Bug report #955687,
regarding missing libgudev-1.0-dev dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
955687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wacomtablet
Version: 3.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o
> /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=iso9899:1990 
> -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
> -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute 
> -Wwrite-strings -Werror=implicit-function-declaration 
> -DCHECK_FUNCTION_EXISTS=shmat   -o 
> CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o   -c 
> /usr/share/cmake-3.16/Modules/CheckFunctionExists.c
> Linking C executable cmTC_56fac
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_56fac.dir/link.txt 
> --verbose=1
> /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wmissing-format-attribute -Wwrite-strings 
> -Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat  
> -Wl,-z,relro -Wl,-z,now  -rdynamic 
> CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o  -o cmTC_56fac 
> make[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> make[1]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
> 
> dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
> make: *** [debian/rules:8: build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/04/02/wacomtablet_3.2.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libwacom
Source-Version: 1.3-2
Done: Timo Aaltonen 

In data lunedì 6 aprile 2020 09:09:06 CEST, Pino Toscano ha scritto:
> reassign 955687 libwacom-dev libwacom/1.3-1
> retitle 955687 missing libgudev-1.0-dev dependency
> severity 955687 serious
> bts affects 955687 src:wacomtablet
> thanks
> 
> In data venerdì 3 aprile 2020 21:56:25 CEST, Lucas Nussbaum ha scritto:
> > Source: wacomtablet
> > Version: 3.2.0-3
> > Severity: serious
> > Justification: FTBFS on amd64
> > Tags: bullseye sid ftbfs
> > Usertags: ftbfs-20200402 ftbfs-bullseye
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> > 
> > Relevant part (hopefully):
> > > make[2]: Entering directory 
> > > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> > > Building C object CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o
> > > /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> > > 

Processed: affects 955687

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 955687 src:wacomtablet
Bug #955687 [libwacom-dev] missing libgudev-1.0-dev dependency
Added indication that 955687 affects src:wacomtablet
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
955687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: [Pkg-kde-extras] Bug#955687: wacomtablet: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_IN

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 955687 libwacom-dev libwacom/1.3-1
Bug #955687 [src:wacomtablet] wacomtablet: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
Bug reassigned from package 'src:wacomtablet' to 'libwacom-dev'.
No longer marked as found in versions wacomtablet/3.2.0-3.
Ignoring request to alter fixed versions of bug #955687 to the same values 
previously set
Bug #955687 [libwacom-dev] wacomtablet: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
Marked as found in versions libwacom/1.3-1.
> retitle 955687 missing libgudev-1.0-dev dependency
Bug #955687 [libwacom-dev] wacomtablet: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
Changed Bug title to 'missing libgudev-1.0-dev dependency' from 'wacomtablet: 
FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1'.
> severity 955687 serious
Bug #955687 [libwacom-dev] missing libgudev-1.0-dev dependency
Ignoring request to change severity of Bug 955687 to the same value.
> bts affects 955687 src:wacomtablet
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
955687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955687: [Pkg-kde-extras] Bug#955687: wacomtablet: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/

[Pino Toscano]

reassign 955687 libwacom-dev libwacom/1.3-1
retitle 955687 missing libgudev-1.0-dev dependency
severity 955687 serious
bts affects 955687 src:wacomtablet
thanks

In data venerdì 3 aprile 2020 21:56:25 CEST, Lucas Nussbaum ha scritto:
> Source: wacomtablet
> Version: 3.2.0-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[2]: Entering directory 
> > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> > Building C object CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o
> > /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=iso9899:1990 
> > -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
> > -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute 
> > -Wwrite-strings -Werror=implicit-function-declaration 
> > -DCHECK_FUNCTION_EXISTS=shmat   -o 
> > CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o   -c 
> > /usr/share/cmake-3.16/Modules/CheckFunctionExists.c
> > Linking C executable cmTC_56fac
> > /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_56fac.dir/link.txt 
> > --verbose=1
> > /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra 
> > -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
> > -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings 
> > -Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat  
> > -Wl,-z,relro -Wl,-z,now  -rdynamic 
> > CMakeFiles/cmTC_56fac.dir/CheckFunctionExists.c.o  -o cmTC_56fac 
> > make[2]: Leaving directory 
> > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> > make[1]: Leaving directory 
> > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> > 
> > 
> > 
> > dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
> > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> > -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" 
> > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON 
> > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
> > make: *** [debian/rules:8: build] Error 2
> 
> The full build log is available from:
>http://qa-logs.debian.net/2020/04/02/wacomtablet_3.2.0-3_unstable.log

This build was attempted with libwacom 1.3-1, whose libwacom-dev lacked
a dependency and thus the libwacom detection (via pkg-config) in
wacomtablet failed.

This was already fixed in src:libwacom, so I'm reassigning this there,
and closing it after that.

-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.

Bug#948295: marked as done (python-dateutils's autopkg tests fail / Update to 2.8.1 for Python 3.8)

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 07:04:18 +
with message-id 
and subject line Bug#948295: fixed in python-dateutil 2.8.1-1
has caused the Debian Bug report #948295,
regarding python-dateutils's autopkg tests fail / Update to 2.8.1 for Python 3.8
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.)


-- 
948295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-dateutil
Version: 2.7.3-3
Severity: serious
Tags: sid bullseye

python-dateutils's autopkg tests fail for Python2, python-freezegun was already
removed.  Maybe for now just stop testing for Python2.

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dateutil/3890104/log.gz

Please also update to 2.8.1 to support Python 3.8.
--- End Message ---
--- Begin Message ---
Source: python-dateutil
Source-Version: 2.8.1-1
Done: =?utf-8?q?Guido_G=C3=BCnther?= 

We believe that the bug you reported is fixed in the latest version of
python-dateutil, 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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated python-dateutil package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 06 Apr 2020 08:42:05 +0200
Source: python-dateutil
Architecture: source
Version: 2.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 948295
Changes:
 python-dateutil (2.8.1-1) unstable; urgency=medium
 .
   * New upstream version 2.8.1
   * Rediff patches
   * Add salsa-ci
   * Remove Python 2 support
 (Closes: #948295)
Checksums-Sha1:
 2883c1c123256e224259abf6c5ff3cf3cf87553a 2290 python-dateutil_2.8.1-1.dsc
 bd26127e57f83a10f656b62c46524c15aeb844dd 331745 
python-dateutil_2.8.1.orig.tar.gz
 88721bc29e52529b7ff460a50cc3b5467e6b3d0d 833 
python-dateutil_2.8.1.orig.tar.gz.asc
 95f53948365db624340329a7b8deb787331c3553 13856 
python-dateutil_2.8.1-1.debian.tar.xz
 67cd471d7fc1506939d807d16abc1c1450aa6d59 6791 
python-dateutil_2.8.1-1_source.buildinfo
Checksums-Sha256:
 50a23fb3a27cc30ce0b389fad342d86d1ab1a255ccfbf4cded7d1641cc20da62 2290 
python-dateutil_2.8.1-1.dsc
 73ebfe9dbf22e832286dafa60473e4cd239f8592f699aa5adaf10050e6e1823c 331745 
python-dateutil_2.8.1.orig.tar.gz
 f111673b7aa7233062f8bbc4734fbb6eeb7a07d9533aeb24b645317d928f11d7 833 
python-dateutil_2.8.1.orig.tar.gz.asc
 d53a7da4e8e475f6f9888e9608b6bc6ec95010af2c0d4b0c58b825f87a033bbc 13856 
python-dateutil_2.8.1-1.debian.tar.xz
 11277ff1655ae41f72c63dad0835346ec307e6ba793c5d2643fa07ba4ebdb28d 6791 
python-dateutil_2.8.1-1_source.buildinfo
Files:
 1ba49e972abc70665da5dd058974c34b 2290 python optional 
python-dateutil_2.8.1-1.dsc
 f2a1d4b680b297b367a974664ca3a4f6 331745 python optional 
python-dateutil_2.8.1.orig.tar.gz
 89f1a0281c5712bd263035c84913858a 833 python optional 
python-dateutil_2.8.1.orig.tar.gz.asc
 8b1055c54a129dd15829cb15eb0e957c 13856 python optional 
python-dateutil_2.8.1-1.debian.tar.xz
 41aedbdd7529a5454c0b6c921f754d17 6791 python optional 
python-dateutil_2.8.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAl6K0W4ACgkQB7i3sOqY
EgsN3g/9GyjimBs/hM4GYBpzkA6fYb99XKKSC0YLw0MNO6sUjhmWalNg4EbQRCqt
0/29DV44pVlCLw09fnBRA9HijIWsRDYE09lIBimapDfKFLZNqUoij0TQ5Fk8gx/R
fimdEkneF0ORGFE8QF3NRcAwO1G8rIZzwYaBQ4zzZV++eh+1vcRNO78Dpl5kN/zp
YAEovqAHhhWwkrFNeVqpgKRVbnDE8fUUo8jUu4CbiyfXTiA8ngJi6KNzxyRwccFJ
DMoro43j8FN5DPY7QvaUIM6gUB8QS54OvcTiADo+wNY3ho8CQe9PKBujfovMgCDL
qfteRkrj6WZKGnKLWaqMRueyE7LPfQlr51Cvd+Hrz/TNetUg67FH7GvodcqNX/3Z
/03ZWwb0SN+Yj4Dd2HurZ+vN7S63zNuMiPMARN4lRwUDet36YOGOubzBeX59mHKW
61Sg+jI/f8/o/BJ1L0xY9b2qGyfg2Odm4Ynaq+ZMtuqVFzfVC7ELqY5UcEo284WM
N21PaU1JfeBhpyoMq99YxWZ2bjshtdUSCzKv55wHh5olShe2NhRuzQwoBHTvGMZd
kTGX+V/J/Fv9IMobJ5YT9JedMJRgtWFyX0MTH1PlyZusAg5fA7jaV34Dm0fZPfP9
AReTEZVIHrkMd7a27vnOcqGqkGcQb0UZwRaGjmZqSMtK8O88/Fw=
=KgWE
-END PGP SIGNATURE End Message ---

Bug#948295: python-dateutils's autopkg tests fail / Update to 2.8.1 for Python 3.8

[Guido Günther]

Hi,
On Tue, Mar 31, 2020 at 03:59:28PM +0200, Thomas Goirand wrote:
> Hi!
> 
> Please accept and upload the merge request over her adressing this bug:
> 
> https://salsa.debian.org/agx/python-dateutil/-/merge_requests/1

That one would not build for me since the patches weren't rebased and the
so i just fixed it up myself. Uploaded now, sorry for the delay.
 -- Guido

> 
> Alternatively, ping me to NMU.
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 949361 https://github.com/imbs-hl/ranger/issues/498
Bug #949361 [src:r-cran-ranger] r-cran-ranger: autopkgtest regression on some 
architectures
Set Bug forwarded-to-address to 'https://github.com/imbs-hl/ranger/issues/498'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
949361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956013: Fails to install

[David Prévot]

Package: manpages-fr-dev
Version: 4.0.0-2
Severity: serious

Hi,

Thanks for updating those translations. Unfortunately, there is an
unhandled upgrade path (missing Breaks and Replace on manpages-fr-extra
(<< 20151231something), and of course the manpages-fr-extra counterpart
update).

> Preparing to unpack .../manpages-fr-dev_4.0.0-2_all.deb ...
> Unpacking manpages-fr-dev (4.0.0-2) over (3.65d1p1-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/manpages-fr-dev_4.0.0-2_all.deb (--unpack):
>  trying to overwrite '/usr/share/man/fr/man3/libblkid.3.gz', which is also in 
> package manpages-fr-extra 20151231
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/manpages-fr-dev_4.0.0-2_all.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Regards

David


signature.asc
Description: PGP signature

Processed: tagging 950839

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 950839 + ftbfs
Bug #950839 [src:reprounzip] reprounzip autopkg test fails with python 3.8
Bug #951957 [src:reprounzip] reprounzip: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.8 3.7" returned exit code 13
Added tag(s) ftbfs.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
950839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950839
951957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 950910

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 950910 + ftbfs
Bug #950910 [src:wcc] wcc ftbfs with glibc-2.30
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
950910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 951926

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 951926 + ftbfs
Bug #951926 [src:mwic] mwic: FTBFS: dh_auto_test: error: make -j4 test returned 
exit code 2
Bug #946288 [src:mwic] Tests are failing
Added tag(s) ftbfs.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
946288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946288
951926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955655: marked as done (python-peakutils: FTBFS: ModuleNotFoundError: No module named 'matplotlib')

[Debian Bug Tracking System]

Your message dated Mon, 06 Apr 2020 06:03:59 +
with message-id 
and subject line Bug#955655: fixed in python-peakutils 1.3.3+ds-2
has caused the Debian Bug report #955655,
regarding python-peakutils: FTBFS: ModuleNotFoundError: No module named 
'matplotlib'
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.)


-- 
955655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-peakutils
Version: 1.3.3+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> copying peakutils/plot.py -> 
> /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> copying peakutils/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> copying peakutils/baseline.py -> 
> /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> copying peakutils/peak.py -> 
> /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> copying peakutils/prepare.py -> 
> /<>/.pybuild/cpython3_3.7_peakutils/build/peakutils
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
> copying peakutils/plot.py -> 
> /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
> copying peakutils/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
> copying peakutils/baseline.py -> 
> /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
> copying peakutils/peak.py -> 
> /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
> copying peakutils/prepare.py -> 
> /<>/.pybuild/cpython3_3.8_peakutils/build/peakutils
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating PeakUtils.egg-info
> writing PeakUtils.egg-info/PKG-INFO
> writing dependency_links to PeakUtils.egg-info/dependency_links.txt
> writing requirements to PeakUtils.egg-info/requires.txt
> writing top-level names to PeakUtils.egg-info/top_level.txt
> writing manifest file 'PeakUtils.egg-info/SOURCES.txt'
> reading manifest file 'PeakUtils.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_*'
> writing manifest file 'PeakUtils.egg-info/SOURCES.txt'
> running build_ext
> peakutils_test (unittest.loader._FailedTest) ... ERROR
> 
> ==
> ERROR: peakutils_test (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: peakutils_test
> Traceback (most recent call last):
>   File "/usr/lib/python3.7/unittest/loader.py", line 154, in loadTestsFromName
> module = __import__(module_name)
>   File "/<>/tests/peakutils_test.py", line 10, in 
> import pandas as pd
>   File "/usr/lib/python3/dist-packages/pandas/__init__.py", line 182, in 
> 
> import pandas.testing
>   File "/usr/lib/python3/dist-packages/pandas/testing.py", line 7, in 
> from pandas.util.testing import (
>   File "/usr/lib/python3/dist-packages/pandas/util/testing.py", line 18, in 
> 
> from matplotlib.cbook import MatplotlibDeprecationWarning
> ModuleNotFoundError: No module named 'matplotlib'
> 
> 
> --
> Ran 1 test in 0.000s
> 
> FAILED (errors=1)
> Test failed: 
> error: Test failed: 
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: 
> python3.7 setup.py test 
> dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned 
> exit code 13

The full build log is available from:
   

Processed: fixed 955659 in 6.1.10-1, notfixed 955659 in 6.1.09-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 955659 6.1.10-1
Bug #955659 {Done: Laurent Bigonville } [src:praat] praat: 
FTBFS: failed tests
Marked as fixed in versions praat/6.1.10-1.
> notfixed 955659 6.1.09-1
Bug #955659 {Done: Laurent Bigonville } [src:praat] praat: 
FTBFS: failed tests
No longer marked as fixed in versions praat/6.1.09-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
955659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems