date:20200416

Bug#956946: marked as done (sprai FTCBFS: does not pass cross tools to make)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 06:34:14 +
with message-id 
and subject line Bug#956946: fixed in sprai 0.9.9.23+dfsg1-2
has caused the Debian Bug report #956946,
regarding sprai FTCBFS: does not pass cross tools to make
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.)


-- 
956946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sprai
Version: 0.9.9.23+dfsg1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

sprai fails to cross build from source, because it does not pass cross
tools to make. dh thinks that this is an autoconf project, so
dh_auto_build doesn't do it for you, but configure is something entirely
different and therefore skipped by debian/rules. A better solution is to
tell dh what kind of buildsystem it is dealing with and doing so makes
sprai cross buildable. Please consider applying the attached patch.

Helmut
diff --minimal -Nru sprai-0.9.9.23+dfsg1/debian/changelog 
sprai-0.9.9.23+dfsg1/debian/changelog
--- sprai-0.9.9.23+dfsg1/debian/changelog   2020-04-15 17:01:52.0 
+0200
+++ sprai-0.9.9.23+dfsg1/debian/changelog   2020-04-17 07:11:31.0 
+0200
@@ -1,3 +1,10 @@
+sprai (0.9.9.23+dfsg1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: use the makefile buildsystem. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 17 Apr 2020 07:11:31 +0200
+
 sprai (0.9.9.23+dfsg1-1) unstable; urgency=medium
 
   [ Adrian Bunk ]  
diff --minimal -Nru sprai-0.9.9.23+dfsg1/debian/rules 
sprai-0.9.9.23+dfsg1/debian/rules
--- sprai-0.9.9.23+dfsg1/debian/rules   2020-04-15 17:01:52.0 +0200
+++ sprai-0.9.9.23+dfsg1/debian/rules   2020-04-17 07:11:29.0 +0200
@@ -4,10 +4,7 @@
 include /usr/share/dpkg/buildflags.mk
 
 %:
-   dh $@
-
-override_dh_auto_configure:
-   echo Skip
+   dh $@ --buildsystem=makefile
 
 override_dh_install:
mkdir -p $(CURDIR)/debian/sprai/usr/lib/sprai
--- End Message ---
--- Begin Message ---
Source: sprai
Source-Version: 0.9.9.23+dfsg1-2
Done: Helmut Grohne 

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

Debian distribution maintenance software
pp.
Helmut Grohne  (supplier of updated sprai 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: Fri, 17 Apr 2020 07:11:31 +0200
Source: sprai
Architecture: source
Version: 0.9.9.23+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Helmut Grohne 
Closes: 956946
Changes:
 sprai (0.9.9.23+dfsg1-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTCBFS: use the makefile buildsystem. (Closes: #956946)
Checksums-Sha1:
 cbe2cad086455ce5863abd56b6add1762be8280a 2020 sprai_0.9.9.23+dfsg1-2.dsc
 5706a8ee1f8c6d1ac32220e5b0dd4e138311cd73 1446536 
sprai_0.9.9.23+dfsg1-2.debian.tar.xz
 a90e8124e71ba34ab6ecf8b34caf0832fea1c0f1 5791 
sprai_0.9.9.23+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 bdf9123615779963e5bf7dceabcbe6e4bd4445d5c4c518be4ff6a66c4c00843a 2020 
sprai_0.9.9.23+dfsg1-2.dsc
 a8e0ced7a51f5d8b96cf05f41a80a62d8dcba10ab2807f4a15ae0a3fbea4a1fb 1446536 
sprai_0.9.9.23+dfsg1-2.debian.tar.xz
 dbfed90f461b0129aa96ba76429cd429a2932510932b5ab60d9dfc1ea7924afa 5791 
sprai_0.9.9.23+dfsg1-2_amd64.buildinfo
Files:
 3490cfee281f4c59dc56428899307f12 2020 science optional 
sprai_0.9.9.23+dfsg1-2.dsc
 23dd12d505b4c89ab7a0998250389728 1446536 science optional 
sprai_0.9.9.23+dfsg1-2.debian.tar.xz
 d61e29f31c5ad7d416299d2941faaf4c 5791 science optional 
sprai_0.9.9.23+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6ZShsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG31BAAkn8+MmAaT4eUX4RW8c9CTXpVO2EoiTw2
A4/j2u0256eByD+lkP/QBSr2EOOnioef16qA+M1bgzYXNs1JajPOlsvTgia0J9LA
Y7gugsJZRcxudGUAS4uQ8EilYciSvixCRWJMDFCyhjgFw5wLEAa9OfECA4QVxVH+
PirbWbS4dqeOpi9ix4NmvY75uO9Z4KUB/ZeAWY0PGjBW3TT20IJ+A8ss45+aRKJf
9nki/5aAVwmnP3HaQMIe29WR0YeJWgmBhcH3VIiSpJg7MOtmFgM0vRpedp0k+VP4
K2MW41fwSKSVhgxxpyiUCK3Q+JtJrKaXMDukEt/8TJPq1/+lLq

Bug#718248: marked as done (nsca-client: Random segmentation faults of send_nsca)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 06:03:28 +
with message-id 
and subject line Bug#718248: fixed in nsca 2.10.0-1
has caused the Debian Bug report #718248,
regarding nsca-client: Random segmentation faults of send_nsca
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.)


-- 
718248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nsca-client
Version: 2.9.1-2
Severity: important

Hi,

Our NSCA installation has random segmentation faults:

Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:20 backup8 kernel: [5668958.752572] send_nsca[10854]: segfault
at 7fff2d847000 ip 004014b0 sp 7fff2d842fd0 error 6 in
send_nsca[40+5000]
Jul 29 00:33:21 backup8 kernel: [5668959.786642] send_nsca[10856]: segfault
at 7fffb1512000 ip 004014b0 sp 7fffb150ddc0 error 6 in
send_nsca[40+5000]

This seems to appear when the system is under extremely heavy I/O, CPU,
memory usage and when send_nsca is called frequently, about 1 time per
second with bursts to probably 20/s.

I can reproduce this issue on at least 3 machines under the same condition
(heavy I/O/CPU/memory usage) under squeeze and wheezy.

On machines with less I/Os, send_nsca is running just fine.

What information would you need from me in order to reproduce and fix this
issue?

Please do not hesitate to ask me for more debug information.

Regards,

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nsca-client depends on:
ii  libc6   2.17-7
ii  libmcrypt4  2.5.8-3.1

nsca-client recommends no packages.

nsca-client suggests no packages.

-- no debconf information
-- 
 ,''`.
: :' :  Cyril Bouthors
`. `' Debian.org
  `-
--- End Message ---
--- Begin Message ---
Source: nsca
Source-Version: 2.10.0-1
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated nsca 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: Fri, 17 Apr 2020 07:09:56 +0200
Source: nsca
Architecture: source
Version: 2.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Closes: 605469 718248
Changes:
 nsca (2.10.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 (closes: #605469, #718248)
   * Bump Standards-Version to 4.5.0, no changes.
   * Bump debhelper compat to 10, changes:
 - Don't explicitly enable autoreconf, enabled by default
 - Drop dh-autoreconf build dependency
   * Update watch file to use GitHub releases.
   * Drop patches applied upstream, refresh remaining patches.
   * Update filenames for docs.
   * Add systemd service & tmpfiles.d conf

Bug#605469: marked as done (send_nsca: consider adding --quiet option)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 06:03:28 +
with message-id 
and subject line Bug#605469: fixed in nsca 2.10.0-1
has caused the Debian Bug report #605469,
regarding send_nsca: consider adding --quiet option
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.)


-- 
605469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nsca
Version: 2.7.2
Severity: wishlist

When I use send_nsca from cronjobs like

#!/bin/sh
set -e
dumpdir=/data/mysqldump
dumper="mysqldump --defaults-file=/etc/mysql/debian.cnf -h localhost -u 
debian-sys-maint"
$dumper tau TauDatabase tau_measure > $dumpdir/tau.dump
...
...
report="$(find $dumpdir/*.dump -printf "%f %s, ")"
printf "data\tbackup-mysqldump\t0\t$report\n" | /usr/sbin/send_nsca -H nagios | 
grep -v "sent to host successfully."

it is really annoying that I need to use the grep to suppress output
that is printed when everything goes as requested.

Please consider the attached patch. It adds a --quiet option that does
not print "sent to host successfully" if at least one result was sent.

(There is only long option since I figured plain "-q" might collide
with something that upstream might add in the future.)

diff --git a/src/send_nsca.c b/src/send_nsca.c
index 868a9cb..543baef 100644
--- a/src/send_nsca.c
+++ b/src/send_nsca.c
@@ -43,6 +43,7 @@ struct crypt_instance *CI=NULL;
 int show_help=FALSE;
 int show_license=FALSE;
 int show_version=FALSE;
+int verbose=TRUE;
 
 
 int process_arguments(int,char **);
@@ -284,7 +285,8 @@ int main(int argc, char **argv){
 	/* close the connection */
 	close(sd);
 
-	printf("%d data packet(s) sent to host successfully.\n",total_packets);
+	if (total_packets == 0 || verbose)
+		printf("%d data packet(s) sent to host successfully.\n",total_packets);
 
 	/* exit cleanly */
 	do_exit(STATE_OK);
@@ -385,6 +387,10 @@ int process_arguments(int argc, char **argv){
 		else if(!strcmp(argv[x-1],"-V") || !strcmp(argv[x-1],"--version"))
 			show_version=TRUE;
 
+		/* be quiet unless there are errors */
+		else if(!strcmp(argv[x-1],"--quiet"))
+			verbose=FALSE;
+
 		/* server name/address */
 		else if(!strcmp(argv[x-1],"-H")){
 			if(xdiff --git a/debian/send_nsca.1 b/debian/send_nsca.1
index 0392254..246d6a2 100644
--- a/debian/send_nsca.1
+++ b/debian/send_nsca.1
@@ -3,7 +3,7 @@
 send_nsca \- send passive check results to an NSCA daemon
 
 .SH SYNOPSIS
-.B send_nsca \-H  [\-p port] [\-to to_sec] [\-d delim] [ \-c config_file]
+.B send_nsca \-H  [\-p port] [\-to to_sec] [\-d delim] [ \-c config_file] [ \-\-quiet ]
 .br
 .Xc
 
@@ -37,6 +37,9 @@ Delimiter to use when parsing input (defaults to a tab)
 .TP
 config_file
 Name of config file to use
+.TP
+\fB\-\-quiet\fR
+Do not print anything unless there are errors (or input contained no reports).
 
 .SH SEE ALSO
 .TP



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5+lindi.5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages nsca depends on:
ii  debconf [debconf-2.0]  1.5.36Debian configuration management sy
ii  libc6  2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib
ii  libmcrypt4 2.5.8-3.1 De-/Encryption Library

nsca recommends no packages.

Versions of packages nsca suggests:
pn  nagios (no description available)
ii  nagios-plugins1.4.15-2   Plugins for the nagios network mon
ii  nagios-plugins-basic  1.4.15-2   Plugins for the nagios network mon

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: nsca
Source-Version: 2.10.0-1
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated nsca 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

Bug#950780: marked as done (Can't open DBIP database)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 04:49:07 +
with message-id 
and subject line Bug#950780: fixed in xtables-addons 3.9-1
has caused the Debian Bug report #950780,
regarding Can't open DBIP database
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.)


-- 
950780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons
Version: 3.8-2

# ls *.csv
GeoLite2-Country-Blocks-IPv4.csv   GeoLite2-Country-Locations-en.csv
 GeoLite2-Country-Locations-ja.csv GeoLite2-Country-Locations-zh-CN.csv
GeoLite2-Country-Blocks-IPv6.csv   GeoLite2-Country-Locations-es.csv
 GeoLite2-Country-Locations-pt-BR.csv
GeoLite2-Country-Locations-de.csv  GeoLite2-Country-Locations-fr.csv
 GeoLite2-Country-Locations-ru.csv

# /usr/lib/xtables-addons/xt_geoip_build -D /usr/share/xt_geoip -S .
Can't open DBIP database

This issue also happens with 3.8-1, but not with previous versions.
-- 
Jean-Christophe
--- End Message ---
--- Begin Message ---
Source: xtables-addons
Source-Version: 3.9-1
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated xtables-addons 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: Fri, 17 Apr 2020 14:34:48 +1000
Source: xtables-addons
Architecture: source
Version: 3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Dmitry Smirnov 
Closes: 950780
Changes:
 xtables-addons (3.9-1) unstable; urgency=medium
 .
   * New upstream release.
   * New patch to download geodata from db-ip.com (Closes: #950780).
 Thanks, Simone Rossetto.
Checksums-Sha1:
 2daf4e61d6349846a100b09fe5fc6fbc39c02e57 2135 xtables-addons_3.9-1.dsc
 3e627df39020a8fd960e85171e1ac58cd307bd59 324380 xtables-addons_3.9.orig.tar.xz
 20336b68cc8826b34ec6e9061fb1a4ddbb2e4a06 12036 
xtables-addons_3.9-1.debian.tar.xz
 0f803080db21fea46bb8a1e1ff37ab2112e1f257 7009 
xtables-addons_3.9-1_amd64.buildinfo
Checksums-Sha256:
 c216a7c454a79dd79d276e6e481a2d83b76906b15d37c6c54d1b0b0e4324f582 2135 
xtables-addons_3.9-1.dsc
 064dd68937d98e6cfcbdf51ef459310d9810c17ab31b21285bc7a76cdcef7c49 324380 
xtables-addons_3.9.orig.tar.xz
 813c7fa0d266b9fdaeaf89906cbc5de2e8e23b25082ced7caef4b02e5956c7c5 12036 
xtables-addons_3.9-1.debian.tar.xz
 8ae34e288de201e9f78f505a4c936cf02659c287110910f68a18fea6d695c409 7009 
xtables-addons_3.9-1_amd64.buildinfo
Files:
 272d87cb436e3a5ee2857d7ec0a865a3 2135 admin optional xtables-addons_3.9-1.dsc
 8b548e7dbd5fee845cd08a687ae2073c 324380 admin optional 
xtables-addons_3.9.orig.tar.xz
 f0a185bb9a4544c3eaf490273c26055e 12036 admin optional 
xtables-addons_3.9-1.debian.tar.xz
 9a1d4420263dfeac4b7ec255738dc9e2 7009 admin optional 
xtables-addons_3.9-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl6ZMsMACgkQUra72VOW
jRttjQ//e0WwycT2+GB7e217u06IhU0VxUvXCDXlUPDT+5kMJPnvnOyiu0kQRVNv
ZEfOVOC8/y3gAj50CP8tmEQKRzc77kShFDfJCAc3v565rPyHDCK/8eEfq4zc3AIE
DC+pvo4mNt+aQKOlhGKzeoyw9kIhZbXK4FKbIYKZbdp80O3sSigAfvUoRrkFXhPa
WV2G+PeOhrDEnedg4BYEfZ513b69iFq0GYOTw8oRoG27b8Ncr0FBZ8bG+JRLSlic
ZoqUaYquPQ+22JrDSq2jS7JmEKiVvdm3vQOn2r9+NW7cFsH12YDUq43l7CbfmZ02
72sCI7lSdhSkvMMaB+qEBWjrFQFx0/wgaL1RzsJRNXB8Yl/Y1Q2fVdbHoHbK4qHE
l3OrqF5UNv9xAvLA9Ji70lRRIrbhU/PXDFoougMtw1jmMFyp4qG+ayQKUexEmfFh
TOGUwka4BZrI0/jliXCXk3gT4Q3Q7O13ROniLeTImQaIjYxNn0RPOQuWpyBlRiIG
JcCaPefQctsdzF5yG0nZ8tzJpUcOIwhFWcM/Be07ATwmfHGilKTDzUiOsgM10zBz
XYtWDv2D4xiymDq2zVvrTIUzm7dDeUBKZteqOTYuHy4nOfSI9rkBvQSSRqSYClVN
hJeNAiwV8joAoXsxSkIRufG3YyNze3riH4KeZ0uIgfv2MzbRjJg=
=RN7j
-END PGP SIGNATURE End Message ---

Bug#923722: marked as done (golang-github-appc-cni: Please upgrade to new upstream 0.7.0-alpha1)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 11:16:08 +0800
with message-id 

and subject line Fixed in 0.7.1-2
has caused the Debian Bug report #923722,
regarding golang-github-appc-cni: Please upgrade to new upstream 0.7.0-alpha1
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.)


-- 
923722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-appc-cni
Severity: wishlist

Hi,

Please update to new upstream version of 0.7.0-alpha1. I need it as a
build dependency of http://github.com/containers/buildah

In fact, I've done so locally, and would be happy to upload it as a Team
Upload. I was running into issues while doing so. Unlike the git
repositories created by the dh-make-golang tool, the git repository on
salsa at
https://salsa.debian.org/go-team/packages/golang-github-appc-cni does
not include full sources in the packaging branch. I am unfamiliar with
that workflow and it is inconsistent with how the vast majority of the
packages in the golang team are handled. I therefore decided to start
off from a 'dgit clone' created repository.

Dimtry, I wonder what your thoughts on this issue are.  Would you be OK
with switching the workflow? If not, could you please upload
0.7.0-alpha1 to experimental soon? Alternatively, I could upload the
package that I have locally to experimental, and leave updating salsa to
you (or someone else) whenever time permits.

What does the rest of the team think about competing git repository
workflows within the team? At least to me, this seems undesireable
because it prompts convesations like this (which I really don't enjoy
having).

Best,
-rt


-- System Information:
Debian Release: 9.7
  APT prefers stable
  APT policy: (500, 'stable'), (75, 'testing'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: golang-github-appc-cni
Source-Version: 0.7.1-2--- End Message ---

Bug#955366: marked as done (Enable CONFIG_KSM in the cloud kernel)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#955366: fixed in linux 5.5.17-1
has caused the Debian Bug report #955366,
regarding Enable CONFIG_KSM in the cloud kernel
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.)


-- 
955366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.98-1
Severity: wishlist
Owner: no...@debian.org

Relaying a request on behalf of an Amazon EC2 customer.  The generic
kernel enables CONFIG_KSM, but the cloud kernel disables this.  The
customer makes extensive use of KSM features in EC2 and would like to
request that the feature be enabled for the cloud kernel.

Since the cloud kernel is intended to be optimized for boot time and
size for common cloud usecases, it's worth understanding how much code
is actually enabled by CONFIG_KSM, and how this affects the size and
boot time (if at all).

noah
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.

Bug#948298: marked as done (linux-image-5.3.0-0.bpo.2-armmp: please enable armada 38x comphy driver for armmp)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#951409: fixed in linux 5.5.17-1
has caused the Debian Bug report #951409,
regarding linux-image-5.3.0-0.bpo.2-armmp: please enable armada 38x comphy 
driver for armmp
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.)


-- 
951409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.9-2~bpo10+1sr1
Severity: normal
Tags: patch

Dear Maintainer,

As of Linux v5.1 a special comphy driver was introduced for Armada 38x SoCs.
It is actively referenced by the dts for the Clearfog Base and Clearfog Pro -
and used by the new Clearfog GTR (which has its device-tree posted to lkml in 
v3).

Please enable this driver as a module for the armmp kernel flavour.
I am attaching the patch to enable this module - and the dmesg of when I 
verified that
the resulting kernel works as expected.

Also, it would be nice if this change could make it into buster-backports ;)

Yours sincerely
Josua Mayer

-- Package-specific info:
** Version:
Linux version 5.3.0-0.bpo.2-armmp (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 5.3.9-2~bpo10+1sr1 (2020-01-06)

** Command line:
  console=ttyS0,115200 log_level=7 net.ifnames=0

** Not tainted

** Kernel log:

** Model information
[6.952015] usb 4-1: Manufacturer: TOSHIBA
[6.956130] usb 4-1: SerialNumber: 0E70657012733A39
[6.967191] usb-storage 4-1:1.0: USB Mass Storage device detected
[6.973990] scsi host4: usb-storage 4-1:1.0
[6.978439] usbcore: registered new interface driver usb-storage
[6.985921] usbcore: registered new interface driver uas
[6.986841] libphy: mdio: probed
[7.118832] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[7.181531] libphy: mdio: probed
[7.299011] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[7.352811] libphy: mdio: probed
[7.478658] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[7.541070] libphy: mdio: probed
[7.655533] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[7.716804] libphy: mdio: probed
[7.832195] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[7.895216] libphy: mdio: probed
[8.004389] scsi 4:0:0:0: Direct-Access TOSHIBA  TransMemory  5.00 
PQ: 0 ANSI: 0 CCS
[8.017642] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[8.026886] sd 4:0:0:0: [sda] 2013184 512-byte logical blocks: (1.03 GB/983 
MiB)
[8.034467] sd 4:0:0:0: [sda] Write Protect is off
[8.039301] sd 4:0:0:0: [sda] Mode Sense: 23 00 00 00
[8.039469] sd 4:0:0:0: [sda] No Caching mode page found
[8.044814] sd 4:0:0:0: [sda] Assuming drive cache: write through
[8.054320]  sda: sda1
[8.058169] sd 4:0:0:0: [sda] Attached SCSI removable disk
[8.080803] libphy: mdio: probed
[8.212177] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[8.275624] libphy: mdio: probed
[8.397802] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[8.460802] libphy: mdio: probed
[8.580273] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[8.643294] libphy: mdio: probed
[8.763092] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[8.830193] libphy: mdio: probed
[8.900734] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[8.967203] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[9.028725] libphy: mdio: probed
[9.110343] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 
88E6390, revision 1
[9.141298] Not activating Mandatory Access Control as /sbin/tomoyo-init 
does not exist.
[9.172705] libphy: mdio: probed
[9.954303] systemd[1]: Inserted module 'autofs4'
[   10.019965] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
[   10.041719] systemd[1]: Detected architecture arm.
[   10.068617] systemd[1]: Set hostname to .
[   10.081427] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid 
argument
[   10.595635] mv8

Bug#954025: marked as done (Please enable CONFIG_DEFERRED_STRUCT_PAGE_INIT)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#954025: fixed in linux 5.5.17-1
has caused the Debian Bug report #954025,
regarding Please enable CONFIG_DEFERRED_STRUCT_PAGE_INIT
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.)


-- 
954025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-cloud-amd64
Severity: wishlist

Please consider enabling CONFIG_DEFERRED_STRUCT_PAGE_INIT for both the
cloud variant and and the standard kernel. This substantially improves
boot time on systems with lots of memory.

- Josh Triplett

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

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

Versions of packages linux-image-cloud-amd64 depends on:
pn  linux-image-5.4.0-4-cloud-amd64
pn  linux-image-5.5.0-rc5-cloud-amd64  

linux-image-cloud-amd64 recommends no packages.

linux-image-cloud-amd64 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII

Bug#951409: marked as done (Marvell A38x ClearFog mvneta eth device regression)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#951409: fixed in linux 5.5.17-1
has caused the Debian Bug report #951409,
regarding Marvell A38x ClearFog mvneta eth device regression
to be marked as done.

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

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


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

Package: src:linux
Version: 5.4.19-1
Severity: important

Recent armmp kernels fail to enable all available ethernet devices using 
the mvneta driver. On a ClearFog Base, booting the 4.19 Buster kernels 
works as expected, with eth0/eth1/eth2 all being present and available 
for use.


However, in booting more recent kernels, only the single eth0 device is 
available for use. The mvneta module is loaded and used in all cases, 
but doesn't seem to even acknowledge the existence of the other two 
devices.


The device tree for the ClearFog maps ethernet devices as 
f107.ethernet, f103.ethernet, and f1034000.ethernet. According 
to dmesg boot output, the f107 device is the only one which is 
available on newer kernels.


I've tested with 4.19.67-2+deb10u2 and confirmed it working, and tested 
with linux-image-5.2.0-2-armmp version 5.2.7-1 from snapshots and 
confirmed that it is not working as of that 5.2 build.


Thanks,
Joel
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation

Bug#951543: marked as done (Please enable SECO HDMI CEC driver)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#951543: fixed in linux 5.5.17-1
has caused the Debian Bug report #951543,
regarding Please enable SECO HDMI CEC driver
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.)


-- 
951543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Severity: wis hlist
Tags: patch

Dear Maintainer,

Could you please enable CONFIG_VIDEO_SECO_CEC ?
That device is found on x86 board from UDOO, it would be very cool
to not have to rebuild the kernel by hand :-)

Thanks.

Sébastien

--- a/config-5.4.13
+++ b/config-5.4.13
@@ -4797,6 +4797,7 @@
 # CONFIG_REGULATOR_TPS65132 is not set
 # CONFIG_REGULATOR_TPS6524X is not set
 CONFIG_CEC_CORE=y
+CONFIG_CEC_NOTIFIER=y
 CONFIG_RC_CORE=m
 CONFIG_RC_MAP=m
 CONFIG_LIRC=y
@@ -5122,7 +5123,9 @@
 # CONFIG_VIDEO_VIM2M is not set
 # CONFIG_VIDEO_VICODEC is not set
 # CONFIG_DVB_PLATFORM_DRIVERS is not set
-# CONFIG_CEC_PLATFORM_DRIVERS is not set
+CONFIG_CEC_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_SECO_CEC=m
+CONFIG_VIDEO_SECO_RC=y
 # CONFIG_SDR_PLATFORM_DRIVERS is not set
 
 #
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is

Bug#951482: marked as done (CX2072X SoC audio modules)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#951482: fixed in linux 5.5.17-1
has caused the Debian Bug report #951482,
regarding CX2072X SoC audio modules
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.)


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


Package: linux-image-amd64
Version: 5.4.19-1


Please enable modules for CX2072X audio [1] (included in mainline from 
5.3 [2] )


CONFIG_SND_SOC_INTEL_BYT_CHT_CX2072X_MACH
CONFIG_SND_SOC_CX2072X

[1] https://bugzilla.kernel.org/show_bug.cgi?id=115531
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a497a4363706b3eb208c64e66e5b485bb3b186ac


Thanks
Peter
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
 - bnxt_en: Free context memory after disabling PCI in probe error path.
 - bnxt_en: Reset rings if ring reservation fails during open()
 - net: ena: fix incorrect setting of the number of msix v

Bug#956173: marked as done (linux: please enable HighDPI font FONT_TER16x32)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#956173: fixed in linux 5.5.17-1
has caused the Debian Bug report #956173,
regarding linux: please enable HighDPI font FONT_TER16x32
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.)


-- 
956173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.5.13-2
Severity: wishlist


Hi.

Since quite a while now Linux seems to support a font for HighDPI
displays.

It woudl just need to be enabled:
CONFIG_FONT_TER16x32

Seems it will be auto-selected when appropriate:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dfd19a5004eff03755967086aa04254c3d91b8ec


Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
 - bnxt_en: Free context memory after disabling PCI in probe error path.
 - bnxt_en: Reset rings if ring reservation fails during open()
 - net: ena: fix incorrect setting of the number of ms

Bug#948576: marked as done (linux: please enable support for the layerscape SoCs and the Honeycomb workstation board)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#948576: fixed in linux 5.5.17-1
has caused the Debian Bug report #948576,
regarding linux: please enable support for the layerscape SoCs and the 
Honeycomb workstation board
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.)


-- 
948576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: wishlist
Tags: patch

Dear Maintainer,

Please enable a set of drivers requried for the layerscape based arm64 
honeycomb board.
It is a mini-itx board for use as a workstation machine. Its support in 
mainline is not complete yet,
but many bits are already functional.

I am attaching a patch for enabling the options I have found through reading 
the dts from RMKs cex7 branch.
Changes were tested on 5.5-rc5 built from the debian kernel packaging tree.

Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y
^^ Not sure how you decide when to make options explicit, and when not ... so 
these are *not* included in my attached patch!

The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled. 

Yours sincerely
Josua Mayer

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.5.0-rc5-arm64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
>From 216cdc9faf2cdcbdd593af90a8b7bacc4195c2ac Mon Sep 17 00:00:00 2001
From: Josua Mayer 
Date: Thu, 9 Jan 2020 23:36:15 +
Subject: [PATCH] enable support for the Honeycomb arm64 workstation

This enables support for the Layerscape architecture in general,
as well as
- drivers for the Soc listed in (fsl-lx2160a.dtsi)
- drivers for peripherals listed in (fsl-lx2160a-cex7.dtsi)
.

Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y

The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled.

Signed-off-by: Josua Mayer 
---
 debian/config/arm64/config | 51 ++
 1 file changed, 51 insertions(+)

diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index 9841e44ce42f..285d881310fc 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -67,6 +67,7 @@ CONFIG_ARCH_THUNDER2=y
 CONFIG_ARCH_VEXPRESS=y
 CONFIG_ARCH_XGENE=y
 CONFIG_ARCH_ZYNQMP=y
+CONFIG_ARCH_LAYERSCAPE=y
 
 ##
 ## file: drivers/acpi/Kconfig
@@ -102,6 +103,7 @@ CONFIG_AHCI_MVEBU=m
 CONFIG_AHCI_TEGRA=m
 CONFIG_AHCI_XGENE=m
 CONFIG_SATA_AHCI_SEATTLE=m
+CONFIG_AHCI_QORIQ=m
 
 ##
 ## file: drivers/bluetooth/Kconfig
@@ -116,6 +118,11 @@ CONFIG_HISILICON_LPC=y
 CONFIG_QCOM_EBI2=y
 CONFIG_TEGRA_ACONNECT=y
 
+##
+## file: drivers/bus/fsl-mc/Kconfig
+##
+CONFIG_FSL_MC_BUS=y
+
 ##
 ## file: drivers/char/hw_random/Kconfig
 ##
@@ -147,6 +154,7 @@ CONFIG_TCG_TIS_I2C_INFINEON=m
 CONFIG_COMMON_CLK_RK808=y
 CONFIG_COMMON_CLK_HI655X=y
 CONFIG_COMMON_CLK_XGENE=y
+CONFIG_CLK_QORIQ=y
 
 ##
 ## file: drivers/clk/bcm/Kconfig
@@ -181,6 +189,7 @@ CONFIG_SUN8I_DE2_CCU=y
 CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
 ## end choice
 CONFIG_CPUFREQ_DT=m
+CONFIG_QORIQ_CPUFREQ=m
 
 ##
 ## file: drivers/cpufreq/Kconfig.arm
@@ -202,6 +211,11 @@ CONFIG_CRYPTO_DEV_QCE=m
 CONFIG_CRYPTO_DEV_QCOM_RNG=m
 CONFIG_CRYPTO_DEV_SAFEXCEL=m
 
+##
+## file: drivers/crypto/caam/Kconfig
+##
+CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m
+
 ##
 ## file: drivers/crypto/cavium/cpt/Kconfig
 ##
@@ -250,6 +264,7 @@ CONFIG_QCOM_HIDMA=m
 CONFIG_EDAC=y
 CONFIG_EDAC_THUNDERX=m
 CONFIG_EDAC_XGENE=m
+CONFIG_EDAC_LAYERSCAPE=m
 
 ##
 ## file: drivers/extcon/Kconfig
@@ -277,6 +292,7 @@ CONFIG_GPIO_ZYNQ=m
 CONFIG_GPIO_PCA953X=y
 CONFIG_GPIO_PCA953X_IRQ=y
 CONFIG_GPIO_MAX77620=y
+CONFIG_GPIO_MPC8XXX=y
 
 ##
 ## file: drivers/gpu/drm/Kconfig
@@ -388,6 +404,7 @@ CONFIG_I2C_HID=m
 ## file: drivers/hw

Bug#949171: marked as done (linux: Please, enable COMPACTION for armel/marvell to mitigate OOMs)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#949171: fixed in linux 5.5.17-1
has caused the Debian Bug report #949171,
regarding linux: Please, enable COMPACTION for armel/marvell to mitigate OOMs
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.)


-- 
949171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.19.67-2+deb10u2
Severity: important
X-Debbugs-CC: debian-...@lists.debian.org

Hi, Ben and others.

I've been getting some OOM errors on my armel/kirkwood device running Debian
stable. One of the reasons for this is, according to the dmesg logs, that
COMPACT (memory compaction) is tried, but not available:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
$ grep -i compact /boot/config-4.19.0-6-marvell 
# CONFIG_COMPACTION is not set
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Here is a snippet of the relevant part of the dmesg logs from an earlier
kernel, but the problem still manifests:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(...)
[3558478.729941] kswapd0: page allocation failure: order:0, 
mode:0x480020(GFP_ATOMIC), nodemask=(null)
[3558478.738990] CPU: 0 PID: 20 Comm: kswapd0 Not tainted 4.19.0-5-marvell #1 
Debian 4.19.37-5
[3558478.747317] Hardware name: Marvell Orion5x (Flattened Device Tree)
[3558478.753697] [] (unwind_backtrace) from [] 
(show_stack+0x18/0x1c)
[3558478.761620] [] (show_stack) from [] 
(warn_alloc+0x90/0x13c)
[3558478.769110] [] (warn_alloc) from [] 
(__alloc_pages_nodemask+0x5c4/0xa30)
[3558478.25] [] (__alloc_pages_nodemask) from [] 
(page_frag_alloc+0x64/0x150)
[3558478.786693] [] (page_frag_alloc) from [] 
(__netdev_alloc_skb+0x84/0xfc)
[3558478.795268] [] (__netdev_alloc_skb) from [] 
(rxq_refill+0x74/0x174 [mv643xx_eth])
[3558478.804739] [] (rxq_refill [mv643xx_eth]) from [] 
(mv643xx_eth_poll+0x524/0x558 [mv643xx_eth])
[3558478.815289] [] (mv643xx_eth_poll [mv643xx_eth]) from 
[] (net_rx_action+0x124/0x380)
[3558478.824857] [] (net_rx_action) from [] 
(__do_softirq+0x1c0/0x2b0)
[3558478.832862] [] (__do_softirq) from [] 
(irq_exit+0x80/0xd4)
[3558478.840273] [] (irq_exit) from [] 
(__handle_domain_irq+0x7c/0xa8)
[3558478.848298] [] (__handle_domain_irq) from [] 
(orion_handle_irq+0x7c/0x88)
[3558478.857002] [] (orion_handle_irq) from [] 
(__irq_svc+0x68/0x84)
[3558478.864818] Exception stack(0xc79a9d10 to 0xc79a9d58)
[3558478.870045] 9d00: c0731338 b4ace000 
c795f5a0 c23fe858
[3558478.878392] 9d20: c79a9d74 c0aad000 0001 c059e4fa 0319 c04829bd 
0001 b4ace000
[3558478.886733] 9d40: 00cd914f c79a9d60 c011dcc8 c011dbb0 a013 
[3558478.893548] [] (__irq_svc) from [] 
(page_vma_mapped_walk+0x40/0x168)
[3558478.901830] [] (page_vma_mapped_walk) from [] 
(page_referenced_one+0x54/0x164)
[3558478.910969] [] (page_referenced_one) from [] 
(rmap_walk_anon+0x94/0x12c)
[3558478.919588] [] (rmap_walk_anon) from [] 
(page_referenced+0x140/0x174)
[3558478.927937] [] (page_referenced) from [] 
(shrink_active_list+0x2c0/0x408)
[3558478.936636] [] (shrink_active_list) from [] 
(shrink_node+0x350/0x764)
[3558478.944981] [] (shrink_node) from [] 
(kswapd+0x41c/0x5d4)
[3558478.952293] [] (kswapd) from [] (kthread+0x120/0x138)
[3558478.959264] [] (kthread) from [] 
(ret_from_fork+0x14/0x34)
[3558478.966640] Exception stack(0xc79a9fb0 to 0xc79a9ff8)
[3558478.971864] 9fa0:   
 
[3558478.980211] 9fc0:       
 
[3558478.988552] 9fe0:     0013 
[3558478.995319] Mem-Info:
[3558478.997805] active_anon:3221 inactive_anon:2017 isolated_anon:32
  active_file:9147 inactive_file:8585 isolated_file:0
  unevictable:0 dirty:199 writeback:0 unstable:0
  slab_reclaimable:3447 slab_unreclaimable:1480
  mapped:3434 shmem:1 pagetables:422 bounce:0
  free:985 free_pcp:6 free_cma:0
[3558479.031259] Node 0 active_anon:12884kB inactive_anon:8068kB 
active_file:36588kB inactive_file:34340kB unevictable:0kB isolated(anon):128kB 
isolated(file):0kB mapped:13736kB dirty:796kB writeback:0kB shmem:4kB 
writeback_tmp:0kB unstable:0kB all_unreclaimable? no
[3558479.054496] Normal free:3940kB min:2048kB low:2560kB high:3072kB 
active_anon:12884kB inactive_anon:8068kB active_file:3

Bug#947759: marked as done (Configuration optimizations for the cloud variant)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 03:00:10 +
with message-id 
and subject line Bug#947759: fixed in linux 5.5.17-1
has caused the Debian Bug report #947759,
regarding Configuration optimizations for the cloud variant
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.)


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

A few requests for changes to the cloud configuration:

- Please disable CONFIG_ACPI_BGRT; a cloud kernel doesn't need to spend
  time or code space looking for a boot logo that won't exist.

- Please disable the CONFIG_CPU_SUP_* options for CPUs that no cloud
  provider uses.

- Please disable CONFIG_GNSS_*, which won't be hooked up to a cloud
  server.

- Please disable CONFIG_GTP for the same reason.

- Please configure CONFIG_INPUT_MOUSEDEV as a module, not built-in, as
  most cloud servers won't have a mouse and probing for one takes time.

- Please consider changing the default kernel compression to GZIP, which
  decompresses faster and thus boots faster.

- Please change CONFIG_NET_MPLS_GSO from y to m (and consider doing this
  for the non-cloud kernel too); it doesn't need to be built into the
  kernel.

- Please change CONFIG_NF_NAT_* and CONFIG_NF_MASQUERADE_* from y to m,
  as many systems won't need those modules and shouldn't need to load
  their code.

- Please compile in the NVME driver and the EXT4 filesystem; this will
  allow many cloud systems to avoid using an initramfs at all, which
  substantially improves boot time.

- Please disable CONFIG_NUMA_EMU, only used to create fake-NUMA systems
  for debugging.

- Please disable CONFIG_PCIPCWATCHDOG, CONFIG_PPS, and CONFIG_RMI4_*,
  which won't appear on a cloud server.

- Please enable CONFIG_SCHED_MC_PRIO (on both cloud and non-cloud
  kernels).

- Please disable CONFIG_VFIO_PCI_VGA and CONFIG_VGA_SWITCHEROO, which
  won't appear on cloud.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.5.17-1
Done: Ben Hutchings 

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux
Architecture: source
Version: 5.5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 947759 948576 949171 951409 951482 951543 954025 955366 956173
Changes:
 linux (5.5.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050

Bug#855413: marked as done (xautolock: Typo in xautolock man page)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 02:49:20 +
with message-id 
and subject line Bug#855413: fixed in xautolock 1:2.2-7
has caused the Debian Bug report #855413,
regarding xautolock: Typo in xautolock man page
to be marked as done.

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

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


-- 
855413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xautolock
Version: 1:2.2-5.1
Severity: minor

Dear Maintainer,

There is a typo in the documentation of --detectsleep in xautolock's man page:

This option is typically used to avoid locker program to be
launched when awaking a laptop computer.

I suggest the following change:

This  option is typically used to prevent the locker program from
being launched when awaking a laptop computer

Thanks!

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages xautolock depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  libxss1   1:1.2.2-1

Versions of packages xautolock recommends:
ii  i3lock  2.8-1
ii  suckless-tools  42-2

xautolock suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xautolock
Source-Version: 1:2.2-7
Done: Antoni Villalonga 

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

Debian distribution maintenance software
pp.
Antoni Villalonga  (supplier of updated xautolock 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: Fri, 17 Apr 2020 01:55:23 +0200
Source: xautolock
Architecture: source
Version: 1:2.2-7
Distribution: unstable
Urgency: medium
Maintainer: Antoni Villalonga 
Changed-By: Antoni Villalonga 
Closes: 579066 855413
Changes:
 xautolock (1:2.2-7) unstable; urgency=medium
 .
   * Added debian/patches/15-rephrase-manpage.patch (Closes: #855413)
   * Added debian/patches/16-unlimit-maxtimes.patch (Closes: #579066)
   * d/control Bump standards to 4.5.0
   * Rename salsa-ci file and edit
   * Use secure URI in Homepage field.
   * Add simple tests
Checksums-Sha1:
 3a2c5969286f4396d3230cce01f6df8d24c30414 1994 xautolock_2.2-7.dsc
 818acd40411faee4b751a7f84a480e7d75c98cd8 7976 xautolock_2.2-7.debian.tar.xz
 65cdd270482bd752cd848e225073def2721e7647 5880 xautolock_2.2-7_source.buildinfo
Checksums-Sha256:
 657c8d63e59d1440220ca624c5095972ee50eae1d691e0a84985fb520158d7a2 1994 
xautolock_2.2-7.dsc
 c98664a17195ff86c8d3a617ea263ea3bb1ee11f761cb078bf81f1883c1bf560 7976 
xautolock_2.2-7.debian.tar.xz
 24ac177177f1d2a9406499086f3b6135d2ab44fabe1e6f4480f3ed267cad53a6 5880 
xautolock_2.2-7_source.buildinfo
Files:
 f79b8fa8334ac6993aa2015c0a3d54ba 1994 x11 optional xautolock_2.2-7.dsc
 bc7c08fa4cdb8a138bb4100cb9738197 7976 x11 optional 
xautolock_2.2-7.debian.tar.xz
 b18d331b563033e6934687deaa9ae78d 5880 x11 optional 
xautolock_2.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6ZFvkACgkQweDZLphv
fH5GFRAA61hosPUqaEaWZp7nOfWy4AKaZJVm9N8XLWJ9WQs9OQL0DNto1Q+dbF9/
Zp8vmeBe1OODP+N8svwhp+vfrRqvY5OzOY05kr8D+81uUN4eUrPytnfEotV+naxV
TQ2jaS/heEZMpsmA9S533/DEZdxM3jZ1vKRTmSN1Iq4V0vpvkzEg974qjW4brbr3
aSGFBbVq+9Iwshp4bTBCjc2XZ/ycNeQT0an32yqoievJOsSewTXAYxJS+ZWyjaQ/
ZBeLHUMn8XaqJjdVZLe/yWQ6T3pze2irP4O3XSZa1YS7qVp+GRhOD2qy/YgSPuxB
EUfXLF8CwPCaZMIoFwai0Xsqp64gEHPO0bLZ9HMlXRUGfACutNcqqhJvoec+DhNv
ax5NX0OKQ7bSkwFqGRrXKeikUHPFw7PsIx53DcDYHkPeeJW72EnBe9M7uwtuzcOW
h+AoAjXVMIHLt1lyHqYIjmsgHeNuxevwYxZFAa7sgd01csueXgWDBlltVxwWCqQd
2DyFW7Khe3ONrA4oVV68QJ/R0uqw/6v1fEGoHAbY0ubnitdrV1DlSue0r2MwGkqT
RpGDqmlZavIdx/F9Az0c37kZKHXIgIqL0H25P2aneDQg6PAAE/JDZAFLAhw41Dih
6iH36nsGbIQgFGkA5/OaYUKAoTeld5bVvKFB9xNT7Z8n8k/H9WU=
=O6hW
-END PGP SIGNATURE End Message ---

Bug#579066: marked as done (maximum lock time limit)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 02:49:20 +
with message-id 
and subject line Bug#579066: fixed in xautolock 1:2.2-7
has caused the Debian Bug report #579066,
regarding maximum lock time limit
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.)


-- 
579066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xautolock
Version: 1:2.2-1
Severity: wishlist

Is there any reason for the arbitrary limit of 1 hour of the
'time'/Xautolock.time setting? Can this restriction be removed entirely?

xautolock seems to be plastered with arbitrary limits for no reason.
I would understand a minimum lock time of 10 seconds (just as a
precaution), but not all the others.
 
Thanks.


--- End Message ---
--- Begin Message ---
Source: xautolock
Source-Version: 1:2.2-7
Done: Antoni Villalonga 

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

Debian distribution maintenance software
pp.
Antoni Villalonga  (supplier of updated xautolock 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: Fri, 17 Apr 2020 01:55:23 +0200
Source: xautolock
Architecture: source
Version: 1:2.2-7
Distribution: unstable
Urgency: medium
Maintainer: Antoni Villalonga 
Changed-By: Antoni Villalonga 
Closes: 579066 855413
Changes:
 xautolock (1:2.2-7) unstable; urgency=medium
 .
   * Added debian/patches/15-rephrase-manpage.patch (Closes: #855413)
   * Added debian/patches/16-unlimit-maxtimes.patch (Closes: #579066)
   * d/control Bump standards to 4.5.0
   * Rename salsa-ci file and edit
   * Use secure URI in Homepage field.
   * Add simple tests
Checksums-Sha1:
 3a2c5969286f4396d3230cce01f6df8d24c30414 1994 xautolock_2.2-7.dsc
 818acd40411faee4b751a7f84a480e7d75c98cd8 7976 xautolock_2.2-7.debian.tar.xz
 65cdd270482bd752cd848e225073def2721e7647 5880 xautolock_2.2-7_source.buildinfo
Checksums-Sha256:
 657c8d63e59d1440220ca624c5095972ee50eae1d691e0a84985fb520158d7a2 1994 
xautolock_2.2-7.dsc
 c98664a17195ff86c8d3a617ea263ea3bb1ee11f761cb078bf81f1883c1bf560 7976 
xautolock_2.2-7.debian.tar.xz
 24ac177177f1d2a9406499086f3b6135d2ab44fabe1e6f4480f3ed267cad53a6 5880 
xautolock_2.2-7_source.buildinfo
Files:
 f79b8fa8334ac6993aa2015c0a3d54ba 1994 x11 optional xautolock_2.2-7.dsc
 bc7c08fa4cdb8a138bb4100cb9738197 7976 x11 optional 
xautolock_2.2-7.debian.tar.xz
 b18d331b563033e6934687deaa9ae78d 5880 x11 optional 
xautolock_2.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6ZFvkACgkQweDZLphv
fH5GFRAA61hosPUqaEaWZp7nOfWy4AKaZJVm9N8XLWJ9WQs9OQL0DNto1Q+dbF9/
Zp8vmeBe1OODP+N8svwhp+vfrRqvY5OzOY05kr8D+81uUN4eUrPytnfEotV+naxV
TQ2jaS/heEZMpsmA9S533/DEZdxM3jZ1vKRTmSN1Iq4V0vpvkzEg974qjW4brbr3
aSGFBbVq+9Iwshp4bTBCjc2XZ/ycNeQT0an32yqoievJOsSewTXAYxJS+ZWyjaQ/
ZBeLHUMn8XaqJjdVZLe/yWQ6T3pze2irP4O3XSZa1YS7qVp+GRhOD2qy/YgSPuxB
EUfXLF8CwPCaZMIoFwai0Xsqp64gEHPO0bLZ9HMlXRUGfACutNcqqhJvoec+DhNv
ax5NX0OKQ7bSkwFqGRrXKeikUHPFw7PsIx53DcDYHkPeeJW72EnBe9M7uwtuzcOW
h+AoAjXVMIHLt1lyHqYIjmsgHeNuxevwYxZFAa7sgd01csueXgWDBlltVxwWCqQd
2DyFW7Khe3ONrA4oVV68QJ/R0uqw/6v1fEGoHAbY0ubnitdrV1DlSue0r2MwGkqT
RpGDqmlZavIdx/F9Az0c37kZKHXIgIqL0H25P2aneDQg6PAAE/JDZAFLAhw41Dih
6iH36nsGbIQgFGkA5/OaYUKAoTeld5bVvKFB9xNT7Z8n8k/H9WU=
=O6hW
-END PGP SIGNATURE End Message ---

Bug#855854: marked as done (O: xautolock -- Program launcher for idle X sessions)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 04:41:25 +0200
with message-id <20200417024125.ga1...@angband.pl>
and subject line already done
has caused the Debian Bug report #837785,
regarding O: xautolock -- Program launcher for idle X sessions
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.)


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

I intend to orphan the xautolock package.

The package description is:
 Xautolock monitors input devices under the X Window System, and launches a
 program of your choice if there is no activity after a user-configurable
 period of time.  You can use this to automatically start up a screen locker
--- End Message ---
--- Begin Message ---
Version: 1:2.2-5.3

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄--- End Message ---

Bug#837785: marked as done (O: xautolock -- Program launcher for idle X sessions)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 04:41:25 +0200
with message-id <20200417024125.ga1...@angband.pl>
and subject line already done
has caused the Debian Bug report #837785,
regarding O: xautolock -- Program launcher for idle X sessions
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.)


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

I request an adopter for the xautolock package. I don't have much time to
work on it anymore.

The package description is:
 Xautolock monitors input devices under the X Window System, and launches a
 program of your choice if there is no activity after a user-configurable
 period of time.  You can use this to automatically start up a screen locker
--- End Message ---
--- Begin Message ---
Version: 1:2.2-5.3

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄--- End Message ---

Processed: Re: Bug#956889: Acknowledgement (buster-pu: package zfs-linux/0.7.12-2+deb10u2)

2020-04-16 Thread Debian Bug Tracking System

Processing control commands:

> close -1
Bug #956889 [release.debian.org] buster-pu: package zfs-linux/0.7.12-2+deb10u2
Marked Bug as done

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

Bug#956928: marked as done (tex-common: Fails to install on hppa - missing engine luajithbtex)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 01:48:47 +
with message-id 
and subject line Bug#956928: fixed in tex-common 6.14
has caused the Debian Bug report #956928,
regarding tex-common: Fails to install on hppa - missing engine luajithbtex
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.)


-- 
956928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.13
Severity: normal

Dear Maintainer,

Install fails as follows:

Setting up tex-common (6.13) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.WljFgC6Y
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned 
error exit status 1

We have in /tmp/fmtutil.WljFgC6Y:
fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/texsis.log
fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/texsis.fmt installed.
fmtutil [ERROR]: not building luajithbtex due to missing engine: luajithbtex
fmtutil [INFO]: disabled formats: 1
fmtutil [INFO]: successfully rebuilt formats: 35
fmtutil [INFO]: not available formats: 1
fmtutil [INFO]: failed to build: 1 (luajithbtex/luajithbtex)
fmtutil [INFO]: total formats: 38
fmtutil [INFO]: exiting with status 1

On hppa, luajithbtex is not in texlive-binaries.

Regards,
Dave Anglin

-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

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

Versions of packages tex-common depends on:
ii  dpkg  1.19.7
ii  ucf   3.0038+nmu1

tex-common recommends no packages.

Versions of packages tex-common suggests:
ii  debhelper  13

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libpaper-utils 1.1.28
ii  sensible-utils 0.0.12+nmu1
ii  texlive-binaries   2020.20200327.54578-3
ii  ucf3.0038+nmu1
ii  xdg-utils  1.1.3-2

Versions of packages texlive-base recommends:
ii  lmodern  2.004.5-6

Versions of packages texlive-base suggests:
ii  ghostscript [postscript-viewer]   9.52~dfsg-1
ii  gv [postscript-viewer]1:3.7.4-2
pn  perl-tk   
pn  xzdec 
ii  zathura-pdf-poppler [pdf-viewer]  0.3.0-1

Versions of packages texlive-binaries depends on:
ii  dpkg1.19.7
ii  install-info6.7.0.dfsg.2-5
ii  libc6   2.30-4
ii  libcairo2   1.16.0-4
ii  libfontconfig1  2.13.1-3
ii  libfreetype62.10.1-2
ii  libgcc-s4   10-20200411-1
ii  libgmp102:6.2.0+dfsg-4
ii  libgraphite2-3  1.3.14-1
ii  libharfbuzz0b   2.6.4-1
ii  libice6 2:1.0.9-2
ii  libicu6363.2-3
ii  libkpathsea62020.20200327.54578-3
ii  libmpfr64.0.2-1
ii  libpaper1   1.1.28
ii  libpixman-1-0   0.36.0-1
ii  libpng16-16 1.6.37-2
ii  libptexenc1 2020.20200327.54578-3
ii  libsm6  2:1.2.3-1
ii  libstdc++6  10-20200411-1
ii  libsynctex2 2020.20200327.54578-3
ii  libteckit0  2.5.8+ds2-5
ii  libtexlua53 2020.20200327.54578-3
ii  libx11-62:1.6.9-2
ii  libxaw7 2:1.0.13-1+b2
ii  libxext62:1.3.3-1+b2
ii  libxi6  2:1.7.9-1
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.1.5-1
ii  libzzip-0-130.13.62-3.2
ii  perl5.30.0-9
ii  t1utils 1.41-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages texlive-binaries recommends:
ii  dvisvgm   2.9.1-1
ii  texlive-base  2020.20200329-3

-- debconf information:
  texlive-base/texconfig_ignorant:
  tex-common/check_texmf_wrong:
  texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi
  tex-common/check_texmf_missing:
--- End Message ---
--- Begin Message ---
Source: tex-common
Source-Version: 6.14
Done: Norbert Preining 

We believe that the bug you reported is fixed in the latest version of
tex-common, 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

Bug#956001: marked as done (cinnamon-common: Python SyntaxWarning in package setup - bad identity comparisons against literals)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 00:48:44 +
with message-id 
and subject line Bug#956001: fixed in cinnamon 4.4.8-4
has caused the Debian Bug report #956001,
regarding cinnamon-common: Python SyntaxWarning in package setup - bad identity 
comparisons against literals
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.)


-- 
956001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cinnamon-common
Version: 4.4.8-3
Severity: important

During upgrade, I saw the following warnings:

Setting up cinnamon-common (4.4.8-3) ...
/usr/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py:197: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  name_valid = name_text is not ""
/usr/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py:239: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  valid = (name_text is not "")
/usr/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py:284: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  name_valid = name_text is not ""
/usr/share/cinnamon/cinnamon-settings/bin/ChooserButtonWidgets.py:342: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if show_seconds is 'default':
/usr/share/cinnamon/cinnamon-settings/bin/ChooserButtonWidgets.py:346: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if show_seconds is 'true':
/usr/share/cinnamon/cinnamon-settings/bin/ChooserButtonWidgets.py:348: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif show_seconds is 'false':
/usr/share/cinnamon/cinnamon-settings/bin/JsonSettingsWidgets.py:242: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if key[:1] is '!':
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:422: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if category.int_name is not "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:431: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if category.int_name is "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:446: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if category.int_name is "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:456: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if entry is not "_invalid_":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:539: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if cat[2].int_name is "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:577: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if cat[2].int_name is "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:603: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if cat[2].int_name is "custom":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:694: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if entry is not "":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:734: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if entry is not "":
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:780: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  ok_enabled = self.name_entry.get_text().strip() is not "" and 
self.command_entry.get_text().strip() is not ""
/usr/share/cinnamon/cinnamon-settings/modules/cs_keyboard.py:780: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  ok_enabled = self.name_entry.get_text().strip() is not "" and 
self.command_entry.get_text().strip() is not ""
/usr/share/cinnamon/cinnamon-slideshow/cinnamon-slideshow.py:121: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if len(files) is not 0:


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

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

Versions of packages cinnamon-common depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gettext  0.19.8.1-10
ii  gir1.2-cinnamondesktop-3.0   4.4.1-3
ii  gir1.2-meta-muffin-0.0

Bug#955826: marked as done (cinnamon: Build-Depends on deprecated dbus-glib, but doesn't need to)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Fri, 17 Apr 2020 00:48:44 +
with message-id 
and subject line Bug#955826: fixed in cinnamon 4.4.8-4
has caused the Debian Bug report #955826,
regarding cinnamon: Build-Depends on deprecated dbus-glib, but doesn't need to
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.)


-- 
955826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cinnamon
Version: 4.4.8-3
Severity: normal
Tags: upstream
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: dbus-glib-deprecation

dbus-glib is a deprecated D-Bus library with some significant design
flaws, and is essentially unmaintained. As announced in [0], I would
like to minimize its use, and eventually remove it from Debian.

cinnamon Build-Depends on libdbus-glib-1-dev, checks for dbus-glib-1.pc
in configure.ac, and has #include  in src/main.c.

However, from a quick check, it seems that its only uses of dbus-glib
are for a few constants with names starting with DBUS_, which actually
come from  in dbus-1.pc (libdbus-1-dev).

If this is true, please either change it to use libdbus-1-dev, dbus-1.pc
and  instead, or hard-code the values of those constants
in cinnamon (they are part of the D-Bus "wire protocol" documented in
the D-Bus Specification[1], and will not change) and drop the dependency
completely.

If cinnamon has other uses of dbus-glib that I have missed, please see
[0] for how to proceed.

Thanks,
smcv

[0] https://lists.debian.org/debian-devel/2020/03/msg00272.html
[1] 
https://dbus.freedesktop.org/doc/dbus-specification.html#bus-messages-request-name
--- End Message ---
--- Begin Message ---
Source: cinnamon
Source-Version: 4.4.8-4
Done: Norbert Preining 

We believe that the bug you reported is fixed in the latest version of
cinnamon, 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.
Norbert Preining  (supplier of updated cinnamon 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: Fri, 17 Apr 2020 08:28:33 +0900
Source: cinnamon
Architecture: source
Version: 4.4.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Cinnamon Team 
Changed-By: Norbert Preining 
Closes: 955826 956001
Changes:
 cinnamon (4.4.8-4) unstable; urgency=medium
 .
   * drop dbus-glib necessity (Closes: #955826)
   * fix python 3.8 noisiness (Closes: #956001), thanks Joshua Peisach
Checksums-Sha1:
 1c6cd88437c44569bf331f887de43672ca1ba6c7 2526 cinnamon_4.4.8-4.dsc
 427b2bf25160f327bf2fbbb24aa2a75a3dfc8c5f 101548 cinnamon_4.4.8-4.debian.tar.xz
 a6ed784cb5b271cc9e260415ccb3a5ec3c0e7229 18827 
cinnamon_4.4.8-4_source.buildinfo
Checksums-Sha256:
 e822e8691143d439164d519624c2d2bc4b445f125eba8e9b2cd6dc7a1960691f 2526 
cinnamon_4.4.8-4.dsc
 167798d6c37d347a7566493b663c43382def410d99b655ff26472bd977b48f0f 101548 
cinnamon_4.4.8-4.debian.tar.xz
 957187dece90eb3a4ec64afcad8b04ff8bcfbf045b6f236caf448ee78e22d98c 18827 
cinnamon_4.4.8-4_source.buildinfo
Files:
 c47ac678e770138eaf6dbf7fc62e79a2 2526 x11 optional cinnamon_4.4.8-4.dsc
 1f7ffe243bbfdf935f1eba9f6f85fdda 101548 x11 optional 
cinnamon_4.4.8-4.debian.tar.xz
 f346151dc751e7cc0722554725ad7cf4 18827 x11 optional 
cinnamon_4.4.8-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl6Y60AACgkQ2A4JsIcU
AGa06AgAp1HizlNB6sxVlHpJG7OH8RQXG/iPeNzstssjKKixYTyldRJusRV88CgI
a7GFQosw7FcbtIbMrQFMNXTfL0yndvVQ//RlKDOv1JJ41+MO2xq5LtX1E4PGcZZA
RCMOpsaDQ9QCT3JWjWMMj+22waPP7b+CVpQPDpa1eOEs47QmXVj4xF9t3D19XBzY
Pueu1VJtip66135BtdkywWbUBnJO4tf3nb/Irqz4hSpQ4/llML19H/dFU9wfHBTA
KMqtdXD/NOPEniHUbWMR+Fe4iB0f1BrP9RuB9hVCi11lCN+3LX3ScFCSZSn/NBsl
t8jaktoWzBU2XZdLIHfIJXiQ9EqRGg==
=bVD/
-END PGP SIGNATURE End Message ---

Bug#956893: marked as done (wireguard-dkms-1.0.20200413-2 not build on Kernel 5.5.0-1)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 19:20:46 -0400
with message-id <87ftd3xbjl@fifthhorseman.net>
and subject line Re: Bug#956893: wireguard-dkms-1.0.20200413-2 not build on 
Kernel 5.5.0-1
has caused the Debian Bug report #956893,
regarding wireguard-dkms-1.0.20200413-2 not build on Kernel 5.5.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.)

-- 
956893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wireguard-dkms
Version: 1.0.20200413-2
Severity: normal

Dear Maintainer,

wireguard-dkms-1.0.20200413-2 not build on Kernel 5.5.0-1

Loading new wireguard-1.0.20200413 DKMS files...
Building for 5.5.0-1-amd64
Building initial module for 5.5.0-1-amd64
Error!  The /var/lib/dkms/wireguard/1.0.20200413/5.5.0-1-amd64/x86_64/dkms.conf
for module wireguard includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.

Holger...

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

Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wireguard-dkms depends on:
ii  dkms  2.8.1-5
ii  perl  5.30.0-9

Versions of packages wireguard-dkms recommends:
pn  wireguard
pn  wireguard-tools  

wireguard-dkms suggests no packages.
--- End Message ---
--- Begin Message ---
Control: affects 956893 + dkms

On Thu 2020-04-16 14:27:57 +0200, Holger Schröder wrote:
> Loading new wireguard-1.0.20200413 DKMS files...
> Building for 5.5.0-1-amd64
> Building initial module for 5.5.0-1-amd64
> Error!  The 
> /var/lib/dkms/wireguard/1.0.20200413/5.5.0-1-amd64/x86_64/dkms.conf
> for module wireguard includes a BUILD_EXCLUSIVE directive which
> does not match this kernel/arch.  This indicates that it should not be built.
> Skipped.

Yep -- this is deliberate.  building wireguard isn't necessary because
5.5.0-1 already ships with wireguard.ko!

If you read
/var/lib/dkms/wireguard/1.0.20200413/5.5.0-1-amd64/x86_64/dkms.conf
(mentioned in the verbose dkms message above) you'll see that we have a
special carveout there to accomodate for this nice backport.  (see also
#956241)

The "Error!" message is unfortunate, because it's not actually an error
at all. But that comes from dkms, and it's not something we can change
directly in the wireguard-dkms package.

I'm closing this bug report because everything is working as intended.
you should even be able to use wireguard with your new 5.5.0-1 kernel
without the wireguard-dkms package at all!

If I'm misunderstanding this and you're actually having problems with
wireguard on 5.5.0-1, feel free to reopen this report and give me more
detail about the problem.

Regards,

--dkg

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

Bug#937439: marked as done (pyflakes: Python2 removal in sid/bullseye)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 22:49:16 +
with message-id 
and subject line Bug#937439: fixed in pyflakes 2.1.1-3
has caused the Debian Bug report #937439,
regarding pyflakes: 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.)


-- 
937439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyflakes
Version: 2.1.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pyflakes

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: pyflakes
Source-Version: 2.1.1-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyflakes 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: Thu, 16 Apr 2020 18:39:15 -0400
Source: pyflakes
Architecture: source
Version: 2.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 937439
Changes:
 pyflakes (2.1.1-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937439
Checksums-Sha1:
 feca147630e2f8fa5094307838d71faf1cc7627f 2146 pyflakes_2.1.1-3.dsc
 9083621e0cd0ffe5f25ab932a0fa2482e8375505 7156 pyflakes_2.1.1-3.debian.tar.xz
 f794626b81e33d7c32317f86c55811b9d7f10175 6513 pyflakes_2.1.1-3_source.buildinfo
Checksums-Sha256:
 943d2182ab4965e3a127fac80ce6c08ae46951d8ef3d96f83d282f3c36981d68 2146 
pyflakes_2.1.1-3.dsc
 ea7882f6b80ba1d1cdefb89c51e52b240624e53c05883548ee5010fedbbeebb2 7156 
pyflakes_2.1.1-3.debian.tar.xz
 4b7ba743993014a7afe96a709912ec8d42ee6a0584d53685168218237ef9cc3a 6513 
pyflakes_2.1.1-3_source.buildinfo
Files:
 323c77e5d99c7ab46f83a945008957ba 2146 python optional pyflakes_2.1.1-3.dsc

Bug#955447: marked as done (hurd: FTBFS with gcc-10)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 22:04:13 +
with message-id 
and subject line Bug#955447: fixed in hurd 1:0.9.git20200416-1
has caused the Debian Bug report #955447,
regarding hurd: FTBFS with gcc-10
to be marked as done.

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

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


-- 
955447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hurd
Severity: normal
Tags: upstream fixed-upstream pending

Just to document and for tracking: the hurd package currently FTBFS with
gcc-10 due to the now-default -fno-common option. A patch was committed
upstream, and will land in Debian soon.

Samuel
--- End Message ---
--- Begin Message ---
Source: hurd
Source-Version: 1:0.9.git20200416-1
Done: Samuel Thibault 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 19:22:44 +
Source: hurd
Binary: hurd hurd-dbgsym hurd-dev hurd-dev-dbgsym hurd-doc hurd-libs0.3 
hurd-libs0.3-dbgsym
Built-For-Profiles: noudeb noprof
Architecture: source all
Version: 1:0.9.git20200416-1
Distribution: unstable
Urgency: medium
Maintainer: GNU Hurd Maintainers 
Changed-By: Samuel Thibault 
Description:
 hurd   - GNU Hurd
 hurd-dev   - GNU Hurd (development files)
 hurd-doc   - GNU Hurd manual
 hurd-libs0.3 - GNU Hurd (libraries)
Closes: 955447
Changes:
 hurd (1:0.9.git20200416-1) unstable; urgency=medium
 .
   * New upstream snapshot.
 - Fixes build with gcc-10 (Closes: Bug#955447).
 - control: Add librumpdisk-dev build-depend.
 - hurd-udeb.install.in: Add /hurd/rumpdisk.
   * debian/rules: Pass includedir=/usr/include.
   * debian/hurd-dev.install.in: Install sys/ headers in multiarch directory,
 to avoid sys/procfs.h conflict with libc linux headers. Also move ddekit
 headers there. Ideally we will move all other hurd headers too, but that
 will need glibc >= 2.30-5.
   * debian/hurd-headers-dev.install.in: Likewise.
   * debian/control,rules: Drop stage2 and rename stage3 to stage2.
   * patches/build-rump: Really enable building rumpdisk.
Checksums-Sha1:
 c26f50b1104b914d6e96c5a44e38ee46cd2123a0 4467 hurd_0.9.git20200416-1.dsc
 679dd84ceb1d318984b97948d339b7ddf5b86e6b 18075 
hurd_0.9.git20200416.orig-eth-filter.tar.bz2
 0ae06e7d06b3cd6a5958209525ab346cd27f28b7 3346625 
hurd_0.9.git20200416.orig-libdde-linux26.tar.bz2
 a4fe02e35014ba93f54b03335dad8b70a9d14551 19458 
hurd_0.9.git20200416.orig-libddekit.tar.bz2
 29676e94aaf1bddc1e9a0b9b50e9f4ca6c895d5f 17003 
hurd_0.9.git20200416.orig-libmachdevdde.tar.bz2
 5c9fda61b141b92dfce5b384151539368e5fa175 2127727 
hurd_0.9.git20200416.orig.tar.bz2
 d764f13dd7fde71060276b1e4d1a35cd03d2d208 69964 
hurd_0.9.git20200416-1.debian.tar.xz
 c7443a9d4c4122495c675b44199fb4d00b9b7a63 175216 
hurd-doc_0.9.git20200416-1_all.deb
Checksums-Sha256:
 5b13b4c685ccf26daa50fcaf8962a9e5483b7578d6ac36c3faaf4df4a6ffc1d3 4467 
hurd_0.9.git20200416-1.dsc
 d21a9f134c0a4bdb8a477f7719ec9a717a87687fdd25c0b8590a4c1a8420e4fc 18075 
hurd_0.9.git20200416.orig-eth-filter.tar.bz2
 539ef77526a8942c2cb0d9a4af07d1420d4ca87c64ad447fda9685b9eae61e28 3346625 
hurd_0.9.git20200416.orig-libdde-linux26.tar.bz2
 78d13ce73ff431c7c54ac54d84b17f50c0cfae89b78fc8e79960ead9a845ddcf 19458 
hurd_0.9.git20200416.orig-libddekit.tar.bz2
 448c7a0f075b0804bcdf966e987c0d4f4bf9396b136c81d079b16c17528f2403 17003 
hurd_0.9.git20200416.orig-libmachdevdde.tar.bz2
 589b6af6335d23ad89e6c794c2d46e39e72c05c682bddf8eb51470a8948bf1ff 2127727 
hurd_0.9.git20200416.orig.tar.bz2
 84140412f3108ad259d7868641e67d944c28606718395ec1123d517184b4aac0 69964 
hurd_0.9.git20200416-1.debian.tar.xz
 e8f0a1f03ea87050680ea6627ded7a1f2dcfecf2f1c73f47a47eb5052b89191e 175216 
hurd-doc_0.9.git20200416-1_all.deb
Files:
 27b82701ac95359961b53d4b61ee5c0f 4467 admin required hurd_0.9.git20200416-1.dsc
 a04f3c4c5ffc7f7747c3014d6d770554 18075 admin required 
hurd_0.9.git20200416.orig-

Bug#920494: marked as done (mark htmldoc Multi-Arch: foreign)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 21:34:10 +
with message-id 
and subject line Bug#920494: fixed in htmldoc 1.9.8-2
has caused the Debian Bug report #920494,
regarding mark htmldoc Multi-Arch: foreign
to be marked as done.

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

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


-- 
920494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: htmldoc
Version: 1.9.3-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:mathomatic

mathomatic fails to cross build from source, because it fails running
htmldoc with an Exec format error. Given that htmldoc exclusively deals
with architecture-independent file formats (html, pdf, etc.) marking it
Multi-Arch: foreign is the way to fix that. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru htmldoc-1.9.3/debian/changelog 
htmldoc-1.9.3/debian/changelog
--- htmldoc-1.9.3/debian/changelog  2018-04-11 20:04:27.0 +0200
+++ htmldoc-1.9.3/debian/changelog  2019-01-26 09:10:55.0 +0100
@@ -1,3 +1,9 @@
+htmldoc (1.9.3-2) UNRELEASED; urgency=medium
+
+  * Mark htmldoc Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 26 Jan 2019 09:10:55 +0100
+
 htmldoc (1.9.3-1) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru htmldoc-1.9.3/debian/control htmldoc-1.9.3/debian/control
--- htmldoc-1.9.3/debian/control2018-04-11 20:04:27.0 +0200
+++ htmldoc-1.9.3/debian/control2019-01-26 09:10:52.0 +0100
@@ -16,6 +16,7 @@
 
 Package: htmldoc
 Architecture: any
+Multi-Arch: foreign
 Depends: htmldoc-common,
  ${misc:Depends},
  ${shlibs:Depends}
--- End Message ---
--- Begin Message ---
Source: htmldoc
Source-Version: 1.9.8-2
Done: Niels Thykier 

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated htmldoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 21:16:16 +
Source: htmldoc
Architecture: source
Version: 1.9.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Niels Thykier 
Closes: 920494
Changes:
 htmldoc (1.9.8-2) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Niels Thykier ]
   * Bump debhelper-compat to 13.
 .
   [ Helmut Grohne ]
   * Mark htmldoc Multi-Arch: foreign. (Closes: #920494)
Checksums-Sha1:
 aec9c83b2707f11cbc6541cddb59c0a77ae01d24 2138 htmldoc_1.9.8-2.dsc
 b0449632bfe7fdb71009d706e0466f50fdcb90b7 16312 htmldoc_1.9.8-2.debian.tar.xz
 9cdbad89a5171ded055deac25825c2c7d0ea7cd9 7590 htmldoc_1.9.8-2_source.buildinfo
Checksums-Sha256:
 26ce55dceeca1ec8f6d61c3f1f66920862d8a1171431d04131167fc7228bf828 2138 
htmldoc_1.9.8-2.dsc
 0d40507664669b7511a5a2e5e9effe57668e76c08c08d1541233c4996f9c1936 16312 
htmldoc_1.9.8-2.debian.tar.xz
 e815995e088fbccdb16c374bdb549f65a0c6029b7751ffa2bc8a052db0e74537 7590 
htmldoc_1.9.8-2_source.buildinfo
Files:
 a392608cbcedd60ff5dc0f85e0fe928a 2138 web optional htmldoc_1.9.8-2.dsc
 1da34bf112b06dbb0829390f4d20754c 16312 web optional 
htmldoc_1.9.8-2.debian.tar.xz
 3f2f3b5b39db28527595e5d0266677f7 7590 web optional 
htmldoc_1.9.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAl6Yy0ASHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqs5YYQAKsWApaaNWn41/1dYRktytMt3n0yMeKo
sl+Krusz38DzZrFuIWC694QbKW3w/hFp3lJpuPXBXj0nzdKYypxsF2lSDP39ynHG
kmADugOn3RJaIpCSrH8R2NcTS0prYYO9pNDGkdYuLTHOedVEUP/ZZDykGP6HYUsb
bvi9X6qf+DqhrfOJGg37Qpt11xTnfXJSw0X2KPWIDzZjbhPXJ69+3zcUc6KBkt/7
CQoi9dDiOoc+82wiXZz1Yf7zuuawd+UMG5z7HxNa6b8b0zH11djruIVRBlZ0ShaD
z68sjhKoXyCIRp/LB4PzvSir4iwFETTUXIdaXBZC/1ZljyQ4DteopJTAbRPT8tJJ
zXapIDz1pYhap5jkQzopaX8Y/Iq9RVJEWg2iXqF3iP7MLBN8TUwB0zM+Xy81SFds
0Nb/f/FFzFQ80vQh6BaIVk+LfHpNWCyXx9L1gO7vXzKTDUVi6btr56CnaM7D8ECa
1hNUC5W1GuSnXtZFYEwlGSEHsbmWgOsjNN/sj9851S334sb201x0j2tTl2D1h9OS
VVevlM0bag0Gq+TraT9mqKEJhDhlrtkeu1AT7GQDB5jDTaBcMqudQXT4nJs4J5cp
sU6fmYjTrmqkpJ0bixsb3EBYXKLysP59ZxAhtYNCP6RPn8tlnAlhEYF9

Processed: RFS: libutempter/1.1.6-6 -- privileged helper for utmp/wtmp updates (development)

2020-04-16 Thread Debian Bug Tracking System

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

> close 956918
Bug #956918 [sponsorship-requests] RFS: libutempter/1.1.6-6 -- privileged 
helper for utmp/wtmp updates (development)
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: apngasm/2.91-2 [QA] -- assemble APNG animation from PNG/TGA image sequence

2020-04-16 Thread Debian Bug Tracking System

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

> close 956915
Bug #956915 [sponsorship-requests] RFS: apngasm/2.91-2 [QA] -- assemble APNG 
animation from PNG/TGA image sequence
Marked Bug as done
> stop
Stopping processing here.

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

Bug#956910: marked as done (gnome-shell: System hangs with GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)))

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956910: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956910,
regarding gnome-shell: System hangs with 
GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: 
(GNOME_BG_IS_SLIDE_SHOW (object))
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.)


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

Package: gnome-shell
Version: 3.34.4-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After today's upgrade the system hangs with

GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)).


This happens with and without wayland.

The gnome-shell errors about OpenGL and glamor and keymap are normal.

Apr 16 10:43:21 debian gnome-shell[838]: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Apr 16 10:43:21 debian gnome-shell[838]: Failed to find schema: 
org.gnome.settings-daemon.plugins.xsettings
Apr 16 10:43:23 debian gnome-shell[838]: can't load 
/usr/lib/i386-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/i386-linux-gnu/spa/support/libspa-support.so: cannot open 
shared object file: No such file or directory
Apr 16 10:43:24 debian gnome-shell[910]: Require OpenGL version 2.1 or 
later.

Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor
Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor, 
falling back to sw
Apr 16 10:43:24 debian snapd[468]: daemon.go:539: gracefully waiting for 
running hooks
Apr 16 10:43:24 debian snapd[468]: daemon.go:541: done waiting for 
running hooks
Apr 16 10:43:24 debian snapd[468]: daemon stop requested to wait for 
socket activation

Apr 16 10:43:24 debian systemd[1]: snapd.service: Succeeded.
Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] 
Activating via systemd: service name='org.gtk.vfs.Metadata' 
unit='gvfs-metadata.service' requested by ':1.3' (uid=117 pid=749 
comm="/usr/libexec/tracker-extract ")
Apr 16 10:43:27 debian systemd[648]: Starting Virtual filesystem 
metadata service...
Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] 
Successfully activated service 'org.gtk.vfs.Metadata'
Apr 16 10:43:27 debian systemd[648]: Started Virtual filesystem metadata 
service.
Apr 16 10:43:28 debian gnome-shell[922]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
Apr 16 10:43:28 debian gnome-shell[922]: > Internal error: Could not 
resolve keysym XF86FullScreen
Apr 16 10:43:28 debian gnome-shell[922]: Errors from xkbcomp are not 
fatal to the X server
Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] 
Activating via systemd: service name='org.a11y.Bus' 
unit='at-spi-dbus-bus.service' requested by ':1.24' (uid=117 pid=838 
comm="/usr/bin/gnome-shell ")

Apr 16 10:43:28 debian systemd[648]: Starting Accessibility services bus...
Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] 
Successfully activated service 'org.a11y.Bus'

Apr 16 10:43:28 debian systemd[648]: Started Accessibility services bus.
Apr 16 10:43:34 debian gnome-shell[838]: cannot register existing type 
'GnomeBGSlideShow'
Apr 16 10:43:34 debian gnome-shell[838]: cannot add private field to 
invalid (non-instantiatable) type ''

Apr 16 10:43:34 debian gnome-shell[838]: **
Apr 16 10:43:34 debian gnome-shell[838]: 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 10:43:34 debian gnome-shell[838]: Bail out! 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 10:43:34 debian gnome-shell[838]: == Stack trace for context 
0x1c70be0 ==
Apr 16 10:43:34 debian gnome-shell[838]: #0    1f66cf8 i 
resource:///org/gnome/shell/ui/background.js:636 (abfb7a10 @ 47)
Apr 16 10:43:34 debian gnome-shell[838]: #1    1f66c80 i 
resource:///org/gnome/shell/ui/background.js:177 (abfb2d30 @ 316)
Apr 16 10:43:34 debian gnome-shell[838]: #2    1f66c18 i 
resource:///org/gnome/shell/ui/background.js:444 (abfb7560 @ 70)
Apr 16 10:43:34 debian gnome-shell[838]: #3    1f66bb0 i 
resource:///org/gnome/shell/ui/background.js:479 (abfb76a0 @ 58)
Apr 16 10:43:34 debian gnome-shell[838]: #4    1f66b48 i 
resource:///org/gnome/shell/ui/background.js:494 (abfb76f0 @

Bug#956894: marked as done (upgrade-reports: display of gnome login screen failed /gnome crashes after applying dist-upgrade on 16th of April 2020)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956894: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956894,
regarding upgrade-reports: display of gnome login screen failed /gnome crashes 
after applying dist-upgrade on 16th of April 2020
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.)


-- 
956894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   Since today's dist-upgrade Gnome does not start to lock screen and crashes 
before. Graphical error message is displayed.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Checked journalctl /usr/bin/gnome-shell(-session) logs for gnome realted 
issues: Since the update I see a assertion failed for 
"gnome_bg_slide_show_set_property" in "gnome-bg-slide_show.c:83"
   g_once_init_leave: assertion: 'result!=0' failed
   Can not register existing type 'GnomeBGSlideShow'

   * What was the outcome of this action?
   I have not taken any action yet as I currently don't exactly know why this 
issue occures

   * What outcome did you expect instead?


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

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 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
--- End Message ---
--- Begin Message ---
Source: gnome-desktop3
Source-Version: 3.36.1-3
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-desktop3 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: Thu, 16 Apr 2020 18:59:16 +0100
Source: gnome-desktop3
Architecture: source
Version: 3.36.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956866 956870 956885 956894 956896 956910
Changes:
 gnome-desktop3 (3.36.1-3) unstable; urgency=medium
 .
   * Team upload
   * Add a lockstep dependency on gnome-desktop3-data and Breaks on older
 SONAMEs of libgnome-desktop3.
 This should prevent updated packages from migrating to testing or
 being installable until everything has been rebuilt, avoiding GNOME
 Shell crashes when two SONAMEs get pulled into the same process by
 indirect dependencies, for example libgnome-desktop-3-18 and
 libgnome-desktop-3-19 in the GNOME 3.36 transition.
 (Closes: #956910, #956885, #956870, #956894, #956896, #956866)
   * Standards-Version: 4.5.0 (no changes required)
Checksums-Sha1:
 69812a0db51c4063efc232accecd560963a45a30 3165 gnome-desktop3_3.36.1-3.dsc
 69a9e8bf7516add352a30898f014f8263a79e6f2 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 dbfd8c8d66b3a14973d4fbdc72bce21aa5e72a9f 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Checksums-Sha256:
 d02c4227c9f9c2bd7a3d7ddf30ee2d512edc4ab8dcfa20ad6b7e513ccda0c354 3165 
gnome-desktop3_3.36.1-3.dsc
 c7f7b9f849d570aa87fe362a0c659c0254a06b2e016388d9971f5bbc66623d1b 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 af45fb7e5b7528c4c3af9f5ee8b7dd5a9aef9dcff995a2599b38aaf1d0780203 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Files:
 394fb3a7ed9568d75f5cc2744b4359d1 3165 gnome optional 
gnome-desktop3_3.36.1-3.dsc
 5e12eaa0ea6e97efef827a1ba3f0303a 25740 gnome optional 
gnome-desktop3_3.36.1-3.debian.tar.xz
 bc3d448961f2adf3489c91623f3b6835 14802 gnome optional 
gnome-desktop3_3.36.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl6YvCwQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMTzoEEACAa0pPLc8oUhjt+ZtTtv6h3kX

Bug#956896: marked as done (gnome-shell crashes at gdm3)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956896: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956896,
regarding gnome-shell crashes at gdm3
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.)


-- 
956896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.34.4-1
Severity: important

I'm on Debian testing with all packages updated. Today after updating the
following packages- gnome-desktop3-data, libgnome-desktop-3-19,
gnome-settings-daemon, gir1.2-gnomedesktop-3.0, the system wouldn't get to
the login screen. Instead, a gray screen with "Oh no! Something has gone
wrong." message is shown.

Furthermore, in journalctl there is an "Unrecoverable failure in required
component org.gnome.Shell.desktop" error. Because there is a line, "ERROR:
... libgnome-desktop/gnome-bg-slide-show ... " nearby, the error might be
originating from libgnome-desktop. But the updated package is 3-19 and
gnome-shell's dependency is 3-18. So I'm not really sure.

Is there a way I can bypass this error until an update fixes this? I'm
unable to send error logs because I can't login to the system.
--- End Message ---
--- Begin Message ---
Source: gnome-desktop3
Source-Version: 3.36.1-3
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-desktop3 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: Thu, 16 Apr 2020 18:59:16 +0100
Source: gnome-desktop3
Architecture: source
Version: 3.36.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956866 956870 956885 956894 956896 956910
Changes:
 gnome-desktop3 (3.36.1-3) unstable; urgency=medium
 .
   * Team upload
   * Add a lockstep dependency on gnome-desktop3-data and Breaks on older
 SONAMEs of libgnome-desktop3.
 This should prevent updated packages from migrating to testing or
 being installable until everything has been rebuilt, avoiding GNOME
 Shell crashes when two SONAMEs get pulled into the same process by
 indirect dependencies, for example libgnome-desktop-3-18 and
 libgnome-desktop-3-19 in the GNOME 3.36 transition.
 (Closes: #956910, #956885, #956870, #956894, #956896, #956866)
   * Standards-Version: 4.5.0 (no changes required)
Checksums-Sha1:
 69812a0db51c4063efc232accecd560963a45a30 3165 gnome-desktop3_3.36.1-3.dsc
 69a9e8bf7516add352a30898f014f8263a79e6f2 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 dbfd8c8d66b3a14973d4fbdc72bce21aa5e72a9f 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Checksums-Sha256:
 d02c4227c9f9c2bd7a3d7ddf30ee2d512edc4ab8dcfa20ad6b7e513ccda0c354 3165 
gnome-desktop3_3.36.1-3.dsc
 c7f7b9f849d570aa87fe362a0c659c0254a06b2e016388d9971f5bbc66623d1b 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 af45fb7e5b7528c4c3af9f5ee8b7dd5a9aef9dcff995a2599b38aaf1d0780203 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Files:
 394fb3a7ed9568d75f5cc2744b4359d1 3165 gnome optional 
gnome-desktop3_3.36.1-3.dsc
 5e12eaa0ea6e97efef827a1ba3f0303a 25740 gnome optional 
gnome-desktop3_3.36.1-3.debian.tar.xz
 bc3d448961f2adf3489c91623f3b6835 14802 gnome optional 
gnome-desktop3_3.36.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl6YvCwQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMTzoEEACAa0pPLc8oUhjt+ZtTtv6h3kX4XCgH8BiG
i4wydRrEte4aolt9Z0flZ6AhA6o9PGzJvlKIz7KlXqU1+zjytzd3O5+SVgxz9ZNY
HpLz7K+yNtqqP8eiGPMcuuq5ildmURhjtY6nh4HCUzzprDeAFhypHv+Lrb3efGzV
jvfYuo7cStifB+cZE+q5HxMQ7dChyhvl8gmPfAvCkkI+NLcxfutr/mhpcjMY3DNI
Cc1ge2CDLoKeTYCr6jNVWMhfMMbDEROFjMxghLBtZTAjetQ5t9/h5G+6QIUJt5mr
fAm4qXkQ8uWkI0Rr24ePkk9ygtZX36sIUv5tHE3vq8bVGiirWxC1Bfk86ioIE55k
Hwq6qyACnDRPTJcbCJ/g5CjO76Ou/duNPkpAoOggr+Sow5tS9c89oe3xuY6N6x7A
3Cdv9VTqKzoZ3t4c2iyuEBJGGgIgzIs0EqZpE81sufeuSR9J0ZR52dGNOtCQlqzJ
/vdr1/6ch4mxBbxo4GZq6PZDC

Bug#956870: marked as done (gnome-shell: Incompatible versions in testing)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956870: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956870,
regarding gnome-shell: Incompatible versions in testing
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.)


-- 
956870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.36.1-5
Severity: important

Dear Maintainer,

this morning, I ran apt upgrade on a debian testing system, which
upgraded a number of packages, including some gnome-related ones

2020-04-16 07:55:37 upgrade nvidia-opencl-common:amd64 440.64-2 440.82-1
2020-04-16 07:55:37 upgrade nvidia-vulkan-common:amd64 440.64-2 440.82-1
2020-04-16 07:55:37 upgrade nvidia-vulkan-icd:amd64 440.64-2 440.82-1
2020-04-16 07:55:38 upgrade libnvidia-glvkspirv:amd64 440.64-2 440.82-1
2020-04-16 07:55:38 upgrade nvidia-driver:amd64 440.64-2 440.82-1
2020-04-16 07:55:39 upgrade nvidia-driver-libs:amd64 440.64-2 440.82-1
2020-04-16 07:55:39 upgrade libgl1-nvidia-glvnd-glx:amd64 440.64-2 440.82-1
2020-04-16 07:55:39 upgrade libgl1-nvidia-glvnd-glx:i386 440.64-2 440.82-1
2020-04-16 07:55:40 upgrade libglx-nvidia0:i386 440.64-2 440.82-1
2020-04-16 07:55:40 upgrade libglx-nvidia0:amd64 440.64-2 440.82-1
2020-04-16 07:55:40 upgrade xserver-xorg-video-nvidia:amd64 440.64-2 440.82-1
2020-04-16 07:55:41 upgrade libnvidia-glcore:amd64 440.64-2 440.82-1
2020-04-16 07:55:42 upgrade libnvidia-glcore:i386 440.64-2 440.82-1
2020-04-16 07:55:43 upgrade nvidia-egl-common:amd64 440.64-2 440.82-1
2020-04-16 07:55:43 upgrade libgles-nvidia2:amd64 440.64-2 440.82-1
2020-04-16 07:55:43 upgrade nvidia-egl-icd:amd64 440.64-2 440.82-1
2020-04-16 07:55:44 upgrade libegl-nvidia0:amd64 440.64-2 440.82-1
2020-04-16 07:55:44 upgrade libnvidia-eglcore:amd64 440.64-2 440.82-1
2020-04-16 07:55:45 upgrade nvidia-smi:amd64 440.64-2 440.82-1
2020-04-16 07:55:45 upgrade libnvidia-ml1:amd64 440.64-2 440.82-1
2020-04-16 07:55:45 upgrade nvidia-driver-bin:amd64 440.64-2 440.82-1
2020-04-16 07:55:46 upgrade nvidia-vdpau-driver:amd64 440.64-2 440.82-1
2020-04-16 07:55:46 upgrade nvidia-kernel-support:amd64 440.64-2 440.82-1
2020-04-16 07:55:46 upgrade nvidia-kernel-dkms:amd64 440.64-2 440.82-1
2020-04-16 07:56:02 upgrade libnvidia-cfg1:amd64 440.64-2 440.82-1
2020-04-16 07:56:03 upgrade nvidia-opencl-icd:amd64 440.64-2 440.82-1
2020-04-16 07:56:03 upgrade libnvcuvid1:amd64 440.64-2 440.82-1
2020-04-16 07:56:04 upgrade libnvidia-opticalflow1:amd64 440.64-2 440.82-1
2020-04-16 07:56:04 upgrade libnvidia-ifr1:amd64 440.64-2 440.82-1
2020-04-16 07:56:04 upgrade libnvidia-fbc1:amd64 440.64-2 440.82-1
2020-04-16 07:56:05 upgrade libnvidia-encode1:amd64 440.64-2 440.82-1
2020-04-16 07:56:05 upgrade libcuda1:amd64 440.64-2 440.82-1
2020-04-16 07:56:05 upgrade nvidia-alternative:amd64 440.64-2 440.82-1
2020-04-16 07:56:06 upgrade libnvidia-compiler:amd64 440.64-2 440.82-1
2020-04-16 07:56:07 upgrade libnvidia-fatbinaryloader:amd64 440.64-2 440.82-1
2020-04-16 07:56:07 upgrade libnvidia-ptxjitcompiler1:amd64 440.64-2 440.82-1
2020-04-16 07:56:08 upgrade nvidia-legacy-check:amd64 440.64-2 440.82-1
2020-04-16 07:56:08 upgrade cdbs:all 0.4.159 0.4.161
2020-04-16 07:56:09 upgrade libcheese8:amd64 3.34.0-1+b1 3.34.0-1+b2
2020-04-16 07:56:09 upgrade libcheese-gtk25:amd64 3.34.0-1+b1 3.34.0-1+b2
2020-04-16 07:56:09 upgrade gnome-desktop3-data:all 3.34.2-2 3.36.1-2
2020-04-16 07:56:10 upgrade cheese:amd64 3.34.0-1+b1 3.34.0-1+b2
2020-04-16 07:56:10 upgrade libcupsfilters1:amd64 1.27.3-1 1.27.4-1+b1
2020-04-16 07:56:11 upgrade cups-filters-core-drivers:amd64 1.27.3-1 1.27.4-1+b1
2020-04-16 07:56:11 upgrade libfontembed1:amd64 1.27.3-1 1.27.4-1+b1
2020-04-16 07:56:12 upgrade cups-filters:amd64 1.27.3-1 1.27.4-1+b1
2020-04-16 07:56:12 upgrade eog:amd64 3.36.1-1 3.36.1-1+b1
2020-04-16 07:56:14 upgrade gir1.2-gnomedesktop-3.0:amd64 3.34.2-2 3.36.1-2
2020-04-16 07:56:15 upgrade nautilus:amd64 3.36.1.1-1 3.36.1.1-1+b1
2020-04-16 07:56:16 upgrade libnautilus-extension-dev:amd64 3.36.1.1-1 
3.36.1.1-1+b1
2020-04-16 07:56:16 upgrade libnautilus-extension1a:amd64 3.36.1.1-1 
3.36.1.1-1+b1
2020-04-16 07:56:16 upgrade gir1.2-nautilus-3.0:amd64 3.36.1.1-1 3.36.1.1-1+b1
2020-04-16 07:56:17 upgrade libtotem0:amd64 3.34.1-2 3.34.1-2+b1
2020-04-16 07:56:17 upgrade totem-plugins:amd64 3.34.1-2 3.34.1-2+b1
2020-04-16 07:56:17 upgrade totem:amd64 3.34.1-2 3.34.1-2+b1
2020-04-16 07:56:18 upgrade gir1.2-totem-1.0:amd64 3.34.1-2 3.34.1-2+b1
2020-04-16 07:56:18 upgrade gnome-clock

Bug#956885: marked as done (gnome: gdm fails to start up after bullseye upgrade)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956885: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956885,
regarding gnome: gdm fails to start up after bullseye upgrade
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.)


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

Dear Maintainer,

after performing a dist-ugprade on my bullseye distribution today (not a
release upgrade) my desktop system has stopped working. Instead of the
login screen I get a white screen with the message

"Oh no! Something has gone wrong. A problem has occurred and the system
can't recover. Plese contact a system administrator"

In the syslog I see gnome-shell errors that relate to libgnome-desktop
and I have noticed that with the upgrade the gnome package has become
dependend on a second version of libgnome-desktop-3-19 alongside the
previous libgnome-desktop 3-18. I have tried uninstalling both
libgnome-desktop versions and then reinstalling gnome, but that has not
changed anything.

Excerpt from syslog:

Apr 16 11:04:41 zeus gnome-shell[1161]: mesa: for the   
--simplifycfg-sink-common option: may only occur zero or one times!
Apr 16 11:04:41 zeus gnome-shell[1161]: mesa: for the   --global-isel-abort 
option: may only occur zero or one times!
Apr 16 11:04:42 zeus gnome-shell[1161]: can't load 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared 
object file: No such file or directory
Apr 16 11:04:42 zeus gnome-shell[1304]: The XKEYBOARD keymap compiler (xkbcomp) 
reports:
Apr 16 11:04:42 zeus gnome-shell[1304]: > Internal error:   Could not resolve 
keysym XF86FullScreen
Apr 16 11:04:42 zeus gnome-shell[1304]: Errors from xkbcomp are not fatal to 
the X server
Apr 16 11:04:42 zeus dbus-daemon[1088]: [session uid=117 pid=1088] Activating 
via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' 
requested by ':1.31' (uid=117 pid=1161 comm="/usr/bin/gnome-shell ")
Apr 16 11:04:42 zeus gnome-shell[1161]: cannot register existing type 
'GnomeBGSlideShow'
Apr 16 11:04:42 zeus gnome-shell[1161]: **
Apr 16 11:04:42 zeus gnome-shell[1161]: 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property:
 assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 11:04:42 zeus gnome-shell[1161]: Bail out! 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property:
 assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 11:04:42 zeus gnome-shell[1161]: == Stack trace for context 
0x562a2c5ca3c0 ==
Apr 16 11:04:42 zeus gnome-shell[1161]: #0   562a2cb130e0 i   
resource:///org/gnome/shell/ui/background.js:636 (261f2a0faa60 @ 47)
Apr 16 11:04:42 zeus gnome-shell[1161]: #1   562a2cb13038 i   
resource:///org/gnome/shell/ui/background.js:177 (261f2a0f4718 @ 316)
Apr 16 11:04:42 zeus gnome-shell[1161]: #2   562a2cb12fa0 i   
resource:///org/gnome/shell/ui/background.js:444 (261f2a0fa358 @ 70)
Apr 16 11:04:42 zeus gnome-shell[1161]: #3   562a2cb12f08 i   
resource:///org/gnome/shell/ui/background.js:479 (261f2a0fa538 @ 58)
Apr 16 11:04:42 zeus gnome-shell[1161]: #4   562a2cb12e70 i   
resource:///org/gnome/shell/ui/background.js:494 (261f2a0fa5b0 @ 106)
Apr 16 11:04:42 zeus gnome-shell[1161]: #5   562a2cb12db8 i   
resource:///org/gnome/shell/ui/background.js:261 (261f2a0f49e8 @ 501)
Apr 16 11:04:42 zeus gnome-shell[1161]: cannot add private field to invalid 
(non-instantiatable) type ''
Apr 16 11:04:42 zeus gnome-shell[1161]: #6   562a2cb12d00 i   
resource:///org/gnome/shell/ui/background.js:590 (261f2a0fa880 @ 426)
Apr 16 11:04:42 zeus gnome-shell[1161]: #7   562a2cb12c60 i   
resource:///org/gnome/shell/ui/background.js:751 (261f2a0fae98 @ 39)
Apr 16 11:04:42 zeus gnome-shell[1161]: #8   562a2cb12bb0 i   
resource:///org/gnome/shell/ui/background.js:687 (261f2a0fabc8 @ 269)
Apr 16 11:04:42 zeus gnome-shell[1161]: #9   562a2cb12af8 i   
resource:///org/gnome/shell/ui/screenShield.js:601 (375db47d4880 @ 191)
Apr 16 11:04:42 zeus gnome-shell[1161]: #10   562a2cb12a58 i   
resource:///org/gnome/shell/ui/screenShield.js:619 (375db47d48f8 @ 181)
Apr 16 11:04:42 zeus gnome-shell[1161]: #11   562a2cb12990 i   
resource:///org/gnome/shell/ui/screenShield.js:467 (375db47d4448 @ 546)
Apr 16 11:04:42 zeus gnome-shell[1161]: #12   562a2cb128f0 i   
res

Bug#956690: marked as done (pympress: depends on python3.7)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:36:05 +
with message-id 
and subject line Bug#956690: fixed in pympress 1.5.1+dfsg-4
has caused the Debian Bug report #956690,
regarding pympress: depends on python3.7
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.)


-- 
956690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pympress
Version: 1.5.1+dfsg-3
Severity: serious
Tags: bullseye sid

The binary package pympress has a dependency on python3.7 [1].
Since this is an arch:all package, it cannot be binNMU'd.
Please make a source-only upload so that it picks up a dependency on
python3.8 instead.

Regards
Graham


[1] https://packages.debian.org/unstable/pympress
--- End Message ---
--- Begin Message ---
Source: pympress
Source-Version: 1.5.1+dfsg-4
Done: Christopher Hoskin 

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated pympress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 20:41:58 +0100
Source: pympress
Architecture: source
Version: 1.5.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin 
Changed-By: Christopher Hoskin 
Closes: 956690 956840
Changes:
 pympress (1.5.1+dfsg-4) unstable; urgency=medium
 .
   * Fix "Raise an error at start" by adding missing dependencies
 (Closes: #956840)
   * Fix "depends on python3.7" by new upload
 (Closes: #956690)
Checksums-Sha1:
 6b252f20dd777548b8d8ba0b3c5075ab583268de 1983 pympress_1.5.1+dfsg-4.dsc
 5ac5e9d5cbdc8dec9b31fc4767fcf62bb2a81fb0 8016 
pympress_1.5.1+dfsg-4.debian.tar.xz
 a81f7809eb3c81554511251fb0b6934eca117413 7571 
pympress_1.5.1+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 e70b53b75f235819d503c79d8c772a5beb7a1c223d9da985eeaf7aec1c9fc809 1983 
pympress_1.5.1+dfsg-4.dsc
 8152a7919c336c3949a7955a49bc21ffdf37498ff207fdcac0c723fc847ba407 8016 
pympress_1.5.1+dfsg-4.debian.tar.xz
 4948f2765c3a5342954653cf9514e8dee1db7a9f457582ce92195f5b1b37302f 7571 
pympress_1.5.1+dfsg-4_amd64.buildinfo
Files:
 a8d59c8e9f40e1739f1314770064bd3b 1983 misc optional pympress_1.5.1+dfsg-4.dsc
 3720bc5af05f064cc8441143389cf5e5 8016 misc optional 
pympress_1.5.1+dfsg-4.debian.tar.xz
 c6581e4be1902508d9f4161c9b511d23 7571 misc optional 
pympress_1.5.1+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAl6YuGYACgkQf6qUsnUU
SprYvg/+KA2hY8+lr6ws5TrjOFfLR+8dwCOZpiJZoZ2Mo0vTrdjo3Hb1rC4Poxim
PiGr/1Dd5O/dDSuD0uayO/4OcmtmitcrMK40t0u+xYqUbI21m7aLbO4LADZI6Yzk
ylcXQSh2f9nXPlWKZmB1t8kIi2Cp0vUDqt7ekvphvMk8tnEIpV1ICTjtQeiCS2CA
FqF6PaiJtj/CSRPJx67O3jsK0BYRXnMKcLxEuta8bREn0bdwIVlqRVDaKwTn3naH
tU7eV0TbQqZHekz5TeR70qjgZhpctMFj+tbOUe0LY7gUdbWQAOFsNVFRS9vVsz9h
FiInFvAtxpYbMw2+pJ8zdDT0vVx2zC6IH6pHgR9KX1KgD1picqnx22ordkL/e4ju
M+bcyTTXtbimmLnt1CIX5xqJcKAoLUk+5gFUhKFghnN/IgEo+qYgoi+SCcasL2VY
MfYr/idt+iI3q+X3TiMP7FqaVGpuXw+EN7jDA1ilwbwqW/R/DF4T8DINGYvydSml
/UHg3nmA0iUF+XWUAymBd9K2/Mo98VQC+6Cv5l/LUvlicIsjtaEH/gRYMLQxFN59
s9gVjWcsin+MUTFiB7873rQSxEqO7r9kkD2dIQ0ufwlmbDiSxlARhaAMGV7+42wp
/2rTj5fZ8J9U8y4VQxURE+U7t0XT9i06ANG7aKpjfS/he1xw8EU=
=GYTg
-END PGP SIGNATURE End Message ---

Bug#956866: marked as done (gnome-desktop3: GDM and GNOME fail to load.)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:34:36 +
with message-id 
and subject line Bug#956866: fixed in gnome-desktop3 3.36.1-3
has caused the Debian Bug report #956866,
regarding gnome-desktop3: GDM and GNOME fail to load.
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.)


-- 
956866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-desktop3
Severity: important

Dear Maintainer,

After an update tonight GDM just showed a "white screen of death" and a 
suggestion that I contact my sysadmin. 
Switching to SLiM worked but then the GNOME desktop failed to load. 
It seems possible something in the transition to 3.36 is disagreeing with 
GDM/GNOME.

Thanks for your work here!
Damon

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 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
--- End Message ---
--- Begin Message ---
Source: gnome-desktop3
Source-Version: 3.36.1-3
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-desktop3 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: Thu, 16 Apr 2020 18:59:16 +0100
Source: gnome-desktop3
Architecture: source
Version: 3.36.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956866 956870 956885 956894 956896 956910
Changes:
 gnome-desktop3 (3.36.1-3) unstable; urgency=medium
 .
   * Team upload
   * Add a lockstep dependency on gnome-desktop3-data and Breaks on older
 SONAMEs of libgnome-desktop3.
 This should prevent updated packages from migrating to testing or
 being installable until everything has been rebuilt, avoiding GNOME
 Shell crashes when two SONAMEs get pulled into the same process by
 indirect dependencies, for example libgnome-desktop-3-18 and
 libgnome-desktop-3-19 in the GNOME 3.36 transition.
 (Closes: #956910, #956885, #956870, #956894, #956896, #956866)
   * Standards-Version: 4.5.0 (no changes required)
Checksums-Sha1:
 69812a0db51c4063efc232accecd560963a45a30 3165 gnome-desktop3_3.36.1-3.dsc
 69a9e8bf7516add352a30898f014f8263a79e6f2 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 dbfd8c8d66b3a14973d4fbdc72bce21aa5e72a9f 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Checksums-Sha256:
 d02c4227c9f9c2bd7a3d7ddf30ee2d512edc4ab8dcfa20ad6b7e513ccda0c354 3165 
gnome-desktop3_3.36.1-3.dsc
 c7f7b9f849d570aa87fe362a0c659c0254a06b2e016388d9971f5bbc66623d1b 25740 
gnome-desktop3_3.36.1-3.debian.tar.xz
 af45fb7e5b7528c4c3af9f5ee8b7dd5a9aef9dcff995a2599b38aaf1d0780203 14802 
gnome-desktop3_3.36.1-3_source.buildinfo
Files:
 394fb3a7ed9568d75f5cc2744b4359d1 3165 gnome optional 
gnome-desktop3_3.36.1-3.dsc
 5e12eaa0ea6e97efef827a1ba3f0303a 25740 gnome optional 
gnome-desktop3_3.36.1-3.debian.tar.xz
 bc3d448961f2adf3489c91623f3b6835 14802 gnome optional 
gnome-desktop3_3.36.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl6YvCwQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMTzoEEACAa0pPLc8oUhjt+ZtTtv6h3kX4XCgH8BiG
i4wydRrEte4aolt9Z0flZ6AhA6o9PGzJvlKIz7KlXqU1+zjytzd3O5+SVgxz9ZNY
HpLz7K+yNtqqP8eiGPMcuuq5ildmURhjtY6nh4HCUzzprDeAFhypHv+Lrb3efGzV
jvfYuo7cStifB+cZE+q5HxMQ7dChyhvl8gmPfAvCkkI+NLcxfutr/mhpcjMY3DNI
Cc1ge2CDLoKeTYCr6jNVWMhfMMbDEROFjMxghLBtZTAjetQ5t9/h5G+6QIUJt5mr
fAm4qXkQ8uWkI0Rr24ePkk9ygtZX36sIUv5tHE3vq8bVGiirWxC1Bfk86ioIE55k
Hwq6qyACnDRPTJcbCJ/g5CjO76Ou/duNPkpAoOggr+Sow5tS9c89oe3xuY6N6x7A
3Cdv9VTqKzoZ3t4c2iyuEBJGGgIgzIs0EqZpE81sufeuSR9J0ZR52dGNOtCQlqzJ
/vdr1/6ch4mxBbxo4GZq6PZDCHoAbz+51pLuiNovDS0EOv4XbMdYngh7UZc+LUZ4
S8pYUsMkMriTBkNxz/RVVLtZBc+8S5Qfx

Bug#956840: marked as done (pympress: Raise an error at start)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:36:05 +
with message-id 
and subject line Bug#956840: fixed in pympress 1.5.1+dfsg-4
has caused the Debian Bug report #956840,
regarding pympress: Raise an error at start
to be marked as done.

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

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


-- 
956840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pympress
Version: 1.5.1+dfsg-3
Severity: critical

Dear Maintainer,

After installing pympress, I try to run it and get the trace below.  This makes 
the package unusable.

Best,
C.


Traceback (most recent call last):
  File "/usr/bin/pympress", line 11, in 
load_entry_point('pympress==1.5.1', 'gui_scripts', 'pympress')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2852, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2443, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2449, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/pympress/__main__.py", line 66, in 

import gi
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 42, in 
from . import _gi
ImportError: cannot import name '_gi' from 'gi' 
(/usr/lib/python3/dist-packages/gi/__init__.py)



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'stable'), (100, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages pympress depends on:
ii  python3   3.8.2-3
ii  python3-vlc   3.0.7110-2
ii  python3-watchdog  0.9.0-3
ii  python3.7 3.7.7-1+b1

pympress recommends no packages.

pympress suggests no packages.

-- no debconf information


smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
Source: pympress
Source-Version: 1.5.1+dfsg-4
Done: Christopher Hoskin 

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated pympress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 20:41:58 +0100
Source: pympress
Architecture: source
Version: 1.5.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin 
Changed-By: Christopher Hoskin 
Closes: 956690 956840
Changes:
 pympress (1.5.1+dfsg-4) unstable; urgency=medium
 .
   * Fix "Raise an error at start" by adding missing dependencies
 (Closes: #956840)
   * Fix "depends on python3.7" by new upload
 (Closes: #956690)
Checksums-Sha1:
 6b252f20dd777548b8d8ba0b3c5075ab583268de 1983 pympress_1.5.1+dfsg-4.dsc
 5ac5e9d5cbdc8dec9b31fc4767fcf62bb2a81fb0 8016 
pympress_1.5.1+dfsg-4.debian.tar.xz
 a81f7809eb3c81554511251fb0b6934eca117413 7571 
pympress_1.5.1+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 e70b53b75f235819d503c79d8c772a5beb7a1c223d9da985eeaf7aec1c9fc809 1983 
pympress_1.5.1+dfsg-4.dsc
 8152a7919c336c3949a7955a49bc21ffdf37498ff207fdcac0c723fc847ba407 8016 
pympress_1.5.1+dfsg-4.debian.tar.xz
 4948f2765c3a5342954653cf9514e8dee1db7a9f457582ce92195f5b1b37302f 7571 
pympress_1.5.1+dfsg-4_amd64.buildinfo
Files:
 a8d59c8e9f40e1739f1314770064bd3b 1983 misc optional pympress_1.5.1+dfsg-4.dsc
 3720bc5af05f064cc8441143389cf5e5 8016 misc optional 
pympress_1.5.1+dfsg-4.debian.tar.xz
 c6581e4be1902508d9f4161c9b511d23 7571 misc optional 
pympress_1.5.1+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbctJ5K6JlvFs

Bug#956693: marked as done (spyder: depends on python3.7)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 16:33:20 -0400
with message-id <300360bae2246ad984256fe1a27428296d0b3158.ca...@debian.org>
and subject line Re: spyder: depends on python3.7
has caused the Debian Bug report #956693,
regarding spyder: depends on python3.7
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.)

-- 
956693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder
Version: 3.3.6+dfsg1-4
Severity: serious
Tags: bullseye sid

The binary package spyder has a dependency on python3.7 [1].
Since this is an arch:all package, it cannot be binNMU'd.
Please make a source-only upload so that it picks up a dependency on
python3.8 instead.

Regards
Graham

[1] https://packages.debian.org/unstable/spyder
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg1-5

The latest source-only upload should be enough to solve this bug.

-- 
Regards,
Boyuan Yang

On Tue, 14 Apr 2020 14:15:39 +0200 Graham Inggs  wrote:
> Source: spyder
> Version: 3.3.6+dfsg1-4
> Severity: serious
> Tags: bullseye sid
> 
> The binary package spyder has a dependency on python3.7 [1].
> Since this is an arch:all package, it cannot be binNMU'd.
> Please make a source-only upload so that it picks up a dependency on
> python3.8 instead.
> 
> Regards
> Graham
> 
> 
> [1] https://packages.debian.org/unstable/spyder

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

Bug#922222: marked as done (adapt 7doc_manuals cron script to use the multiple git repos in Salsa)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 22:22:20 +0200
with message-id <2020041620.611d23088e279469f1c04...@mailbox.org>
and subject line Re: Bug#92: adapt 7doc_manuals cron script to use the 
multiple git repos in Salsa
has caused the Debian Bug report #92,
regarding adapt 7doc_manuals cron script to use the multiple git repos in Salsa
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.)

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

Package: www.debian.org
Severity: normal

Hello
I am opening a bug so this is not forgotten.
Kind regards

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

 Mensaje reenviado 
Asunto: Re: 7doc_manuals cron script fails (trying to access svn repo in Alioth)
Resent-Date: Wed, 21 Nov 2018 15:20:02 + (UTC)
Resent-From: debian-...@lists.debian.org
Fecha: Wed, 21 Nov 2018 15:51:35 +0100
De: Laura Arjona Reina 
Para: debian-...@lists.debian.org
CC: debian-www 

Hello web and documentation teams,

El 31/5/18 a las 23:57, Laura Arjona Reina escribió:

Hello Debian Documentation team:

One of the scripts that we use to build the Debian website
(www.debian.org), 7doc_manuals, does not work anymore.

Source code:

https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals

It tries to access svn repo(s) in alioth:

svn export --force svn://svn.debian.org/svn/ddp/manuals . > svn.log 2>&1

and they are not available anymore.

Can you update it to access the corresponding repo in salsa? (or give us
a hint about what to do).

I've been looking at the code of the 7doc_manuals script:

https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals

and the current organisation of the ddp repos in Salsa.

I've listed all the manuals that were built from the original SVN "manuals" 
repo, reviewed case by case, and this is my proposal:

1.- The following manuals show "Obsolete documentation" in their first page of 
the content, and also are hosted now under https://salsa.debian.org/ddp-team/attic:

apt-howto
book-suggestions
ddp-policy  -> would close #147164 www.debian.org: DDP: DDP policy is too out of 
date

dictionary
debian-euro-support
meta
network-administrator
programmer
repository-howto
system-administrator
tutorial
user
users-guide

 so I propose remove them from the "7doc_manuals" build script and remove the 
manuals from the Debian website. Then, in the pages where we link to them, 
change the link to point to the corresponding attic repo and add a note about 
"obsolete documentation" (if it's not there yet). The person wanting to get the 
obsolete manuals, can download the repo and build themselves.

2.- The following manuals don't include the text "Obsolete documentation", but 
they are hosted in https://salsa.debian.org/ddp-team/attic, so I'm not sure what 
to do:

debian-bugs (in attic)
distribute-deb (in attic)
dselect-beginner (in attic)
fr/debian-fr-howto
intro-i18n

For now, I propose to remove them from the build script and keep the copy built 
in May 2018 in the Debian website. Maybe add a README file in the webwml repo in 
english/doc explaining where are the repos for the case it's needed to build 
them again.

3.- The following manuals are current, so I (if nobody beats me to it) will 
adapt the script to get the last changes from the current git repo, and build:

https://salsa.debian.org/ddp-team/hamradio-handbook.git

https://salsa.debian.org/ddp-team/java-faq.git

4.- The following manuals are current, but the current "make" command in the 
7doc_manuals script would not work even if we get the git repos. I appreciate 
help to adapt the 7doc_manuals script for these:

https://salsa.debian.org/ddp-team/project-history.git
make -C project-history publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals 
install_file="install -p -m 664" install_dir="install -d -m 2775"

make: *** No rule to make target 'publish'.  Stop.

https://salsa.debian.org/ddp-team/securing-debian-manual.git
make -C securing-howto publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals 
install_file="install -p -m 664" install_dir="install -d -m 2775"

make: *** No rule to make target 'publish'.  Stop.

Comments welcome.
Kind regards

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
--- End Message ---
--- Begin Message ---
Hi,

Holger Wansing  wrote:
> Hi,
> 
> Holger Wansing  wrote:
> > > If noone objects, I will implement this solution then.
> > 
> > In a first step, I have now added debian-history to 7doc as well.
> > Will see how i

Bug#930710: marked as done (apngasm FTCBFS: uses the build architecture compiler)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:58:30 +0100
with message-id <20200416195830.wbgkvbp6h6mzthio@debian>
and subject line Re: apngasm FTCBFS: uses the build architecture compiler
has caused the Debian Bug report #930710,
regarding apngasm FTCBFS: uses the build architecture compiler
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.)


-- 
930710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apngasm
Version: 2.7-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

apngasm fails to cross build from source, because it uses the build
architecture compiler as a make default. The easiest way of fixing that
- using dpkg's buildtools.mk - makes apngasm cross buildable. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru apngasm-2.7/debian/changelog apngasm-2.7/debian/changelog
--- apngasm-2.7/debian/changelog2016-05-26 12:36:23.0 +0200
+++ apngasm-2.7/debian/changelog2019-06-19 06:20:52.0 +0200
@@ -1,3 +1,9 @@
+apngasm (2.7-3) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Let dpkg's buildtools.mk supply $(CC). (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 19 Jun 2019 06:20:52 +0200
+
 apngasm (2.7-2) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru apngasm-2.7/debian/rules apngasm-2.7/debian/rules
--- apngasm-2.7/debian/rules2013-06-04 18:13:59.0 +0200
+++ apngasm-2.7/debian/rules2019-06-19 06:20:51.0 +0200
@@ -2,7 +2,7 @@
 
 PACKAGE = apngasm
 BIN= $(PACKAGE)
-CC ?= gcc
+-include /usr/share/dpkg/buildtools.mk
 LIBS   = -lz -lpng
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
--- End Message ---
--- Begin Message ---
Version: 2.91-1

debian/rules has been redone with this update and is now cross-building
properly. I have tested with a cross-build on arm64.


--
Regards
Sudip--- End Message ---

Bug#954157: marked as done (ftp.debian.org,autopkgtest: conflicting advice on tests that require internet access)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 19:48:35 +
with message-id 
and subject line Bug#954157: fixed in autopkgtest 5.13
has caused the Debian Bug report #954157,
regarding ftp.debian.org,autopkgtest: conflicting advice on tests that require 
internet access
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.)


-- 
954157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org,autopkgtest
Severity: normal

According to a recent addition to
:
> Tests, including autopkgtests, are part of our build process. Packages
> in Main can only require packages in Main to run their tests (both
> build time and autopkgtest). Downloading unpackaged programs, depending
> on contrib/non-free packages, etc. are not acceptable for Main. We are
> just adding this now as it turns out this wasn't nearly as obvious to
> some of you as it was to the FTP Team.

This seems somewhat inconsistent with the design decision that
autopkgtests are allowed to assume that Internet access is available:


> In general, tests are also allowed to access the internet. As this
> usually makes tests less reliable, this should be kept to a minimum;
> but for many packages their main purpose is to interact with remote
> web services and thus their testing should actually cover those too,
> to ensure that the distribution package keeps working with their
> corresponding web service.

This text was added after I proposed a "needs-internet" restriction in
#851556, and was told that such a restriction was unnecessary because
the designers of autopkgtest intended that all tests may assume they
have internet access.

Do the ftp team make a distinction between tests that download and
execute unpackaged executable code, and tests that access unpackaged
online resources that are not executable code? For example, under this
interpretation, it would be unacceptable for a Python package to download
test libraries from PyPI via pip during autopkgtest, but it would be
acceptable for youtube-dl to have an autopkgtest that asserts that it
is still able to download a video from Youtube (which is its purpose).

Or are the ftp team deliberately contradicting that design point and
saying that, while the autopkgtest framework was designed to support
tests that access the internet, such tests are acceptable for Debian
main? (If so, this would be similar to the way dpkg is designed to
support debian/patches/ubuntu.series, but Policy says such packages are
not allowed in the Debian archive.)

smcv
--- End Message ---
--- Begin Message ---
Source: autopkgtest
Source-Version: 5.13
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
autopkgtest, 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.
Paul Gevers  (supplier of updated autopkgtest 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: Thu, 16 Apr 2020 21:07:58 +0200
Source: autopkgtest
Architecture: source
Version: 5.13
Distribution: unstable
Urgency: medium
Maintainer: Debian CI team 
Changed-By: Paul Gevers 
Closes: 954157 956338
Changes:
 autopkgtest (5.13) unstable; urgency=medium
 .
   [ Gordon Ball ]
   * Use pyflakes3 instead of pyflakes (Closes: #956338)
 .
   [ Paul Gevers ]
   * Add support for needs-internet restriction
   * Add note about ftp-master ruling (Closes: #954157)
   * README.package-tests.rst: add documentation about needs-internet
 restriction
   * Update 5.12 changelog entry with bug number for qemu on ppc64el item
Checksums-Sha1:
 0da9cd9d91d332f4512b2ef91e0f75ccee25faa3 1688 autopkgtest_5.13.dsc
 a14158b415d099e7c2b0b9bece415514bd1ad588 184080 autopkgtest_5.13.tar.xz
Checksums-Sha256:
 e0271b91d95a7ac2b764928a0b48e685382da492b2f129ddd97512d59c968287 1688 
autopkgtest_5.13.dsc
 121e60b4b2445b75be72e7fd6c27416c99058f6d2282bf669cedb34941558619 184080 
autopkgtest_5.13.tar.xz
Files:
 cce7f

Bug#956338: marked as done (autopkgtest: please remove pyflakes (not pyflakes3))

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 19:48:35 +
with message-id 
and subject line Bug#956338: fixed in autopkgtest 5.13
has caused the Debian Bug report #956338,
regarding autopkgtest: please remove pyflakes (not pyflakes3)
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.)


-- 
956338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.10
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello,
as part of the py2removal effort, i noticed autopkgtest still uses (at least it
refers to it as a dependencies) `pyflakes` (not to be confused with
`pyflakes3`).

Can you please remove such dependencies?

I found a conditional b-d and a autopkgtest test that should be removed. This
will help in reducing the number of rdeps of pyflakes, which can then be
removed once it reaches 0 (currently there are only 2 packages keeping pyflakes
in, and one is autopkgtest indeed).

Let me know if i can help you by uploading the package or in any other way.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages autopkgtest depends on:
ii  apt-utils   1.8.2
ii  libdpkg-perl1.19.7
ii  procps  2:3.3.15-2
ii  python3 3.7.5-3
ii  python3-debian  0.1.35

Versions of packages autopkgtest recommends:
ii  autodep8  0.18

Versions of packages autopkgtest suggests:
pn  lxc   
pn  lxd   
pn  ovmf  
pn  qemu-efi-aarch64  
pn  qemu-efi-arm  
pn  qemu-system   
pn  qemu-utils
ii  schroot   1.6.10-6+b1
pn  vmdb2 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: autopkgtest
Source-Version: 5.13
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated autopkgtest 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: Thu, 16 Apr 2020 21:07:58 +0200
Source: autopkgtest
Architecture: source
Version: 5.13
Distribution: unstable
Urgency: medium
Maintainer: Debian CI team 
Changed-By: Paul Gevers 
Closes: 954157 956338
Changes:
 autopkgtest (5.13) unstable; urgency=medium
 .
   [ Gordon Ball ]
   * Use pyflakes3 instead of pyflakes (Closes: #956338)
 .
   [ Paul Gevers ]
   * Add support for needs-internet restriction
   * Add note about ftp-master ruling (Closes: #954157)
   * README.package-tests.rst: add documentation about needs-internet
 restriction
   * Update 5.12 changelog entry with bug number for qemu on ppc64el item
Checksums-Sha1:
 0da9cd9d91d332f4512b2ef91e0f75ccee25faa3 1688 autopkgtest_5.13.dsc
 a14158b415d099e7c2b0b9bece415514bd1ad588 184080 autopkgtest_5.13.tar.xz
Checksums-Sha256:
 e0271b91d95a7ac2b764928a0b48e685382da492b2f129ddd97512d59c968287 1688 
autopkgtest_5.13.dsc
 121e60b4b2445b75be72e7fd6c27416c99058f6d2282bf669cedb34941558619 184080 
autopkgtest_5.13.tar.xz
Files:
 cce7f897b24db37ca39dffc28d42 1688 devel optional autopkgtest_5.13.dsc
 74ed37a84f4a47320b013a2786765243 184080 devel optional autopkgtest_5.13.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl6YsUYACgkQnFyZ6wW9
dQplmgf+LyJHQ8ETlVmW93ZPZ/2Nwp2S00O3MQAatnLDwXdrs5lrZzLGSksNdkZq
/EKrFpOiBiV8neErfSoVx8hvSIp45fo19CL6zK1bAEY9ZntOciA5VSik/eWhBVlu
KEFjVOZ0jm0eBT0rakoLsCh6zNbu3NHRyK9MsdsJBV2BXvZMv2bGGXYW/Cv3Ou1D
qyIh4GdrUPUdU/Xma9MGptM4SfemIexkSSP/goCOAkO7hS

Bug#955666: marked as done (txtorcon: FTBFS: builtins.TypeError: cannot use a bytes pattern on a string-like object)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 20:36:31 +0100
with message-id <802bf136-f7d2-af2c-0da0-806be54aa...@debian.org>
and subject line cannot reproduce
has caused the Debian Bug report #955666,
regarding txtorcon: FTBFS: builtins.TypeError: cannot use a bytes pattern on a 
string-like object
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.)


-- 
955666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: txtorcon
Version: 19.0.0-2
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[1]: Entering directory '/<>'
> PYTHONPATH=. trial3 --reporter=text test
> ./<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_controller/FilesystemOnionFactoryTests/test_happy_path/rio7c53z/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_controller/FilesystemOnionFactoryTests/test_happy_path/rio7c53z/temp'
> ..EEE.../<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_endpoints/EndpointTests/test_basic_auth/g2urtmv1/temp) is relative 
> and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_basic_auth/g2urtmv1/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/ps9ewttv/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/ps9ewttv/temp'
> ../<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_multiple_disk/vbtomr74/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_multiple_disk/vbtomr74/temp'
> ../<>/txtorcon/onion.py:156: 
> UserWarning: Onions service directory 
> (test.test_endpoints/EndpointTests/test_stealth_auth/poj5dpdg/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_stealth_auth/poj5dpdg/temp'
> .../<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/a6f2y49x/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_e/a6f2y49x/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/fy2rzv44/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/fy2rzv44/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/rq_0b7fm/temp)
>  is relative and has been resolved to 
> '/<>/_trial_temp/test.test_endpoints/EndpointTests/test_system_tor_explit_dir_not_r/rq_0b7fm/temp'
> ../<>/txtorcon/onion.py:156:
>  UserWarning: Onions service directory 
> (test.test_onion/OnionServiceTest/test_dir_ioerror/mm_jc7wu/temp) is relative 
> and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror/mm_jc7wu/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_onion/OnionServiceTest/test_dir_ioerror_v3/k7df4980/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_dir_ioerror_v3/k7df4980/temp'
> ./<>/txtorcon/onion.py:156: 
> UserWarning: Onions service directory 
> (test.test_onion/OnionServiceTest/test_old_tor_version/rjbqyv3u/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_old_tor_version/rjbqyv3u/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory 
> (test.test_onion/OnionServiceTest/test_prop224_private_key/26ze6yif/temp) is 
> relative and has been resolved to 
> '/<>/_trial_temp/test.test_onion/OnionServiceTest/test_prop224_private_key/26ze6yif/temp'
> ./<>/txtorcon/onion.py:156: UserWarning: Onions service 
> directory (test.test_onion/OnionServiceTest/test_set_dir/kshugvyi/temp) is 
> rel

Processed: closing 883818

2020-04-16 Thread Debian Bug Tracking System

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

> close 883818
Bug #883818 [python-xlib,python3-xlib] python{,3}-xlib: broken symlink: 
/usr/share/doc/python{,3}-xlib/html/index.html -> python-xlib_toc.html
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 543483, closing 543483

2020-04-16 Thread Debian Bug Tracking System

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

> # the feature is removed in 1.0
> close 543483 1.0~alpha-1
Bug #543483 [inkscape] access to local clipart library
Bug #693876 [inkscape] Import from clipart library should use openclipart2-svg
Marked as fixed in versions inkscape/1.0~alpha-1.
Marked as fixed in versions inkscape/1.0~alpha-1.
Bug #543483 [inkscape] access to local clipart library
Bug #693876 [inkscape] Import from clipart library should use openclipart2-svg
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#926945: marked as done (autopkgtest - autopkgtest-build-qemu on ppc64el)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 21:20:10 +0200
with message-id <671b5f1a-50d3-d468-e0f3-fe6803303...@debian.org>
and subject line forgot to close bug 926945 autopkgtest-build-qemu on ppc64el
has caused the Debian Bug report #926945,
regarding autopkgtest - autopkgtest-build-qemu on ppc64el
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.)


-- 
926945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.10
Severity: important
Tag: autopkgtest qemu patch buster vmdb2
Usertags: ppc64el


While using debci, create-tesbed command for backends/qemu launches
   autopkgtest-build-qemu unstable
/var/lib/debci/qemu/unstable-ppc64el.img http://deb.debian.org/debian
*ppc64el* backends/qemu/customize.sh

1) it fails with   E: Unable to locate package
/*linux-image-ppc64el*/

the proper name should be linux-image-powerpc64le, so on line 123 I
would add the following entry for architecture ppc64el

/*  (ppc64el)*//*
*//*    kernel=linux-image-powerpc64le*//*
*//*    ;;*/

2) Then it calls vmdb2 with an entry:   grub: bios

which calls /usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py
which wants to install package

    grub_package = 'grub-pc'   for grub_target = 'i386-pc'

problem is that grub-pc package doesn't exist on ppc64el
at least*2 solutions there *- either in autopkgtest-build-qemu
conditionally sending the grub: option and install what's needed in
customize.sh script

   either modify vmdb2 to use grub2 package
and target=powerpc-ieee1275

_NOTE:_ because grub-install doesn't install on /dev/loop0 - send a
message : grub-install: error: the chosen partition is not a PReP partition

I was successfull doing /grub-install ... /dev/sda1 but image is not
bootable because slash not found - Not a bootable device !/

/A bit stuck right now !
/


Thanks for your help

Regards


-- 
Thierry Fauck @ fr.ibm.com

--- End Message ---
--- Begin Message ---
Version: 5.12

autopkgtest (5.12) unstable; urgency=medium

  [ Dan Streetman ]
  * tools/autopkgtest-build-lxd: pass /dev/null on stdin to lxc launch
(LP: #1845037)
  * autopkgtest: When finding src pkg, skip binary pkgs for other archs
(LP: #1845157) (Closes: #939790)
  * autopkgtest: when checking binary pkg arch, allow *-$ARCH-* values also

  [ Antonio Terceiro ]
  * Drop unpacking of dependencies to temporary dir

  [ Iain Lane ]
  * setup-testbed: Install rng-tools
  * lib/adt_testbed.py, runner/autopkgtest: Run --shell-fail in more
situations
  * adt_testbed: Run the debug-fail command in more circumstances

  [ Sébastien Delafond ]
  * Add kali support

  [ Simon McVittie ]
  * lxd: Actually exit the awk loop after the first apt source
  * build-lxd: Quote MIRROR and RELEASE properly
  * d/README.source: Document how to test various backends

  [ Paul Gevers ]
  * adt_testbed.py: add date to the start of log so we always have it
(Closes: #954366)
  * Do not ignore distributions that have dashes in their name
  * lxc/lxd: wait for sysvinit services to finish
Thanks to Lars Kruse (Closes: #953655)
  * lxc: increase timeout around reboot
  * tests/lxd: add skip-not-installable (Closes: #952594)

  [ Jelmer Vernooĳ ]
  * Document that $HOME will exist and will be writeable.

  [ Thierry Fauck ]
  * autopkgtest-build-qemu: create primary partition of type Prep to
support ppc64el with grub2
  * Add proper kernel release name for ppc64el

 -- Paul Gevers   Thu, 02 Apr 2020 10:36:09 +0200



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

Bug#956236: marked as done (SyntaxWarnings with updated python3-imexam)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 18:49:03 +
with message-id 
and subject line Bug#956236: fixed in imexam 0.9.1-1
has caused the Debian Bug report #956236,
regarding SyntaxWarnings with updated python3-imexam
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.)


-- 
956236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-imexam
Version: 0.8.1-2+b1
Severity: normal


Dear Maintainer,
Got a few SyntaxWarnings while updating python3-imexam. Please fix
them whenever possible -

Setting up python3-gammapy (0.16-1+b1) ...
/usr/lib/python3/dist-packages/gammapy/cube/fov.py:52: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  if self.method is "fit":
Setting up python3-imexam (0.8.1-2+b1) ...
/usr/lib/python3/dist-packages/imexam/imexamine.py:715: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
  if fitform.name is not "Polynomial1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:743: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  if fitform.name is "Gaussian1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:747: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "Moffat1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:750: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "MexicanHat1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:753: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "Polynomial1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:757: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "AiryDisk2D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:767: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  if fitform.name is "AiryDisk2D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:798: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  if fitform.name is "Gaussian1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:808: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "Moffat1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:816: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "MexicanHat1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:822: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "Polynomial1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:827: SyntaxWarning:
"is" with a literal. Did you mean "=="?
  elif fitform.name is "AiryDisk2D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:1087:
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if fitform.name is "Gaussian1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:1103:
SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif fitform.name is "Moffat1D":
/usr/lib/python3/dist-packages/imexam/imexamine.py:1118:
SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif fitform.name is "MexicanHat1D":

  Please fix the above if possible.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (100,
'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50,
'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages python3-imexam depends on:
ii  libc6   2.30-4
ii  libxpa1 2.1.19-1
ii  python3 3.8.2-2
ii  python3-astropy 4.0-4
ii  python3-matplotlib  3.1.2-2

Versions of packages python3-imexam recommends:
ii  ipython3   7.13.0-1
ii  python3-ginga  3.0.0-1
ii  python3-scipy  1.3.3-3
ii  saods9 8.1+repack-1
ii  xpa-tools  2.1.19-1

Versions of packages python3-imexam suggests:
pn  python-imexam-doc  

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
--- End Message ---
--- Begin Message ---
Source: imexam
Source-Version: 0.9.1-1
Done: Ole Streicher 

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

A summary of the changes between this version and the pre

Bug#955115: marked as done (imexam: FTBFS with Sphinx 2.4: AttributeError: can't set attribute)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 18:49:03 +
with message-id 
and subject line Bug#955115: fixed in imexam 0.9.1-1
has caused the Debian Bug report #955115,
regarding imexam: FTBFS with Sphinx 2.4: AttributeError: can't set attribute
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.)


-- 
955115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imexam
Version: 0.8.1-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

imexam fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> python3 setup.py build_sphinx
> running build_sphinx
> running build
> running build_py
> running build_ext
> Running Sphinx v2.4.3
> photutils not installed, photometry functionality in imexam() not available
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> /<>/astropy_helpers/astropy_helpers/sphinx/local/python3_local_links.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/numpy/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from http://matplotlib.org/objects.inv...
> loading intersphinx inventory from 
> http://docs.astropy.org/en/stable/objects.inv...
> loading intersphinx inventory from 
> http://ginga.readthedocs.io/en/latest/objects.inv...
> intersphinx inventory has moved: http://matplotlib.org/objects.inv -> 
> https://matplotlib.org/objects.inv
> intersphinx inventory has moved: 
> http://ginga.readthedocs.io/en/latest/objects.inv -> 
> https://ginga.readthedocs.io/en/latest/objects.inv
> [autosummary] generating autosummary for: imexam/comparison_iraf.rst, 
> imexam/current_capability.rst, imexam/dependencies.rst, 
> imexam/description.rst, imexam/example1.rst, imexam/example2.rst, 
> imexam/example3.rst, imexam/example4.rst, imexam/example5.rst, 
> imexam/examples.rst, imexam/imexam_command.rst, imexam/iraf_imexam.rst, 
> imexam/reference_api.rst, imexam/updates.rst, imexam/walkthrough.rst, 
> imexam/xpa_commands.rst, index.rst
> [automodsumm] imexam/reference_api.rst: found 5 automodsumm entries to 
> generate
> building [mo]: all of 0 po files
> building [html]: all source files
> updating environment: [new config] 22 added, 0 changed, 0 removed
> reading sources... [  4%] api/imexam.connect.Connect
> reading sources... [  9%] api/imexam.ds9_viewer.ds9
> reading sources... [ 13%] api/imexam.ginga_viewer.ginga
> reading sources... [ 18%] api/imexam.ginga_viewer.ginga_general
> reading sources... [ 22%] api/imexam.imexamine.Imexamine
> reading sources... [ 27%] imexam/comparison_iraf
> reading sources... [ 31%] imexam/current_capability
> reading sources... [ 36%] imexam/dependencies
> reading sources... [ 40%] imexam/description
> reading sources... [ 45%] imexam/example1
> reading sources... [ 50%] imexam/example2
> reading sources... [ 54%] imexam/example3
> reading sources... [ 59%] imexam/example4
> reading sources... [ 63%] imexam/example5
> reading sources... [ 68%] imexam/examples
> reading sources... [ 72%] imexam/imexam_command
> reading sources... [ 77%] imexam/iraf_imexam
> reading sources... [ 81%] imexam/reference_api
> /usr/lib/python3/dist-packages/astropy/config/configuration.py:557: 
> ConfigurationMissingWarning: Configuration defaults will be used due to 
> FileNotFoundError:2 on None
>   warn(ConfigurationMissingWarning(msg))
> WARNING: CacheMissingWarning: Remote data cache could not be accessed due to 
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/sbuild-nonexistent/.astropy' [astropy.utils.data]
> WARNING: CacheMissingWarning: Not clearing data cache - cache inaccessible 
> due to FileNotFoundError: [Errno 2] No such file or directory: 
> '/sbuild-nonexistent/.astropy' [astropy.utils.data]
> WARNING: CacheMissingWarning: ('Cache directory cannot be read or created, 
> providing data in temporary file instead.', 
> '/tmp/astropy-download-18637-1l6317ug') [astropy.utils.data]
> /<>/build/lib.linux-x86_64-3.8/imexam/imexamine.py:715: 
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
>   if fitform.name is not "Polynomial1D":
> /<>/build/lib.linux-x86_64-3.8/imexam/imexamine.py:743: 
> SyntaxWarning: "is" with a literal. Did you mean "=="?
>   if fitform.name

Bug#953401: marked as done (libqt5dbus5: crash on exit due to use-after-free of a QSocketNotifier)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 17:35:13 +
with message-id 
and subject line Bug#953401: fixed in qtbase-opensource-src 5.12.5+dfsg-10
has caused the Debian Bug report #953401,
regarding libqt5dbus5: crash on exit due to use-after-free of a QSocketNotifier
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.)


-- 
953401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5dbus5
Version: 5.12.5+dfsg-9
Severity: normal

Dear Maintainer,

while debugging another crash with valgrind, I noticed errors of invalid
access in the thread used by QDBus. It seems the event loop is still
expecting input on a socket, whose socket notifier should have been
deleted and unregistered. Note that this is not directly related to the
other crash, or at least I don't know how it could be (if anything, it
should cause a deadlock).

The backtrace is here:



binJR1yI21t6F.bin
Description: Binary data

Do you have any ideas why this could be?

Regards
Jiri Palecek

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: i386 (i686)
Foreign Architectures: amd64

Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ 
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5dbus5 depends on:
ii  libc6 2.29-8
ii  libdbus-1-3   1.12.16-2
ii  libqt5core5a [qtbase-abi-5-12-5]  5.12.5+dfsg-9
ii  libstdc++610-20200222-1

libqt5dbus5 recommends no packages.

libqt5dbus5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.12.5+dfsg-10
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated qtbase-opensource-src 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 20:05:12 +0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.12.5+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 948676 953401
Changes:
 qtbase-opensource-src (5.12.5+dfsg-10) unstable; urgency=medium
 .
   * Enable accessibility on Linux when org.a11y.Status IsEnabled is true.
 Thanks to Samuel Thibault (closes: #948676).
   * Backport upstream patch to fix use-after-free in GLib event dispatcher
 (closes: #953401).
Checksums-Sha1:
 465a4f468ff3ea4466818667883086da8e7e30b3 5467 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 7867ff24ce520d373046defe86f0e7b8f8027246 256604 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 bcb95cb2a77077cacb6cc32c39e92eef07a4b8b4 18393 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo
Checksums-Sha256:
 b64910aaf41d024d46dd46a243e95387df3367367ba8c8eb9129c13823f83bb0 5467 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 a9f9b6767277f72d01641618c0022606d5110b920822132b49ce8f106d702730 256604 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 e001e430332d87e6ea966974988277d5a76afdfe6c8bae1515957d44751048df 18393 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo
Files:
 677afdc079ede7a3d4bb9c0a68cf956a 5467 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 1b2253e8c85e5dbb785153ca0ab914c4 256604 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 6d99598deba3187fe93ea6eb8985da36 18393 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl6YkmMTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy2OLD/9ffZArQGpd

Bug#948676: marked as done (at-spi2-core: /etc/X11/Xsession.d/90qt-a11y does not enable Qt5 support as the Wiki indicates)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 17:35:13 +
with message-id 
and subject line Bug#948676: fixed in qtbase-opensource-src 5.12.5+dfsg-10
has caused the Debian Bug report #948676,
regarding at-spi2-core: /etc/X11/Xsession.d/90qt-a11y does not enable Qt5 
support as the Wiki indicates
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.)


-- 
948676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: at-spi2-core
Version: 2.34.0-3
Severity: normal

https://wiki.debian.org/accessibility-devel says it should export
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 but it doesn’t.

Exporting that before starting MuseScore makes the latter show up
in “orca -l” output, so it’s probably needed.

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

Kernel: Linux 5.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages at-spi2-core depends on:
ii  libatspi2.0-0  2.34.0-3
ii  libc6  2.29-7
ii  libdbus-1-31.12.16-2
ii  libglib2.0-0   2.62.4-1
ii  libx11-6   2:1.6.8-1
ii  libxtst6   2:1.2.3-1

at-spi2-core recommends no packages.

at-spi2-core suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.12.5+dfsg-10
Done: Dmitry Shachnev 

We believe that the bug you reported is fixed in the latest version of
qtbase-opensource-src, 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.
Dmitry Shachnev  (supplier of updated qtbase-opensource-src 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 20:05:12 +0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.12.5+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 948676 953401
Changes:
 qtbase-opensource-src (5.12.5+dfsg-10) unstable; urgency=medium
 .
   * Enable accessibility on Linux when org.a11y.Status IsEnabled is true.
 Thanks to Samuel Thibault (closes: #948676).
   * Backport upstream patch to fix use-after-free in GLib event dispatcher
 (closes: #953401).
Checksums-Sha1:
 465a4f468ff3ea4466818667883086da8e7e30b3 5467 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 7867ff24ce520d373046defe86f0e7b8f8027246 256604 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 bcb95cb2a77077cacb6cc32c39e92eef07a4b8b4 18393 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo
Checksums-Sha256:
 b64910aaf41d024d46dd46a243e95387df3367367ba8c8eb9129c13823f83bb0 5467 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 a9f9b6767277f72d01641618c0022606d5110b920822132b49ce8f106d702730 256604 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 e001e430332d87e6ea966974988277d5a76afdfe6c8bae1515957d44751048df 18393 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo
Files:
 677afdc079ede7a3d4bb9c0a68cf956a 5467 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10.dsc
 1b2253e8c85e5dbb785153ca0ab914c4 256604 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10.debian.tar.xz
 6d99598deba3187fe93ea6eb8985da36 18393 libs optional 
qtbase-opensource-src_5.12.5+dfsg-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl6YkmMTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy2OLD/9ffZArQGpdLOEJRl0IOCIdaKDK2YQf
ff1dxWqGTaT4RsMcLhsFuLF/yIn5qLdXfd3aPdjmXd7UiXP5M7zPB6SeDkFEg7Aw
4io1dGNJ9m/nzS3qQ0GdiMLlXF6rtRmE6qocxo29BYfRNoNbreP7eoafhlVz4MWC
lFVm0XTEBA/mEEurFEu1pxeasW9il+w2vpQqGY1OkqH+WZ5tW6jtNRPCN9qXrcEW
CFpc9Rf8B0i0LW+4a+vMD4ShC+5dnp0PFoCud6u+y/XvkHdqRYiMrA9kfxGVAj/e
h3LY8gQhLWu2hYpyIPj08jUL2sKLggFbhmAOVyC5mEWfX7X4NURCze66MCTwT893
SKwtq0jV15BJ4PIYvNXIduQEdte1oVpVVxlPk1o6NcMoEQoTH32/Y3ZMFxzVowaw
gmsQDLTYTdKdnvsX7qgticYnFDi7Dlp3SpehzefcOrjlFv5A27kyA1Z1bU/xMDoN
J

Bug#955553: marked as done (haproxy - unreachable maintainer)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 17:03:35 +
with message-id 
and subject line Bug#93: fixed in haproxy 2.0.14-1
has caused the Debian Bug report #93,
regarding haproxy - unreachable maintainer
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.)


-- 
93: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haproxy
Severity: serious

Mail to the maintainer address hapr...@tracker.debian.org bounces:

| host ticharich.debian.org [2607:f8f0:614:1::1274:64]
| SMTP error from remote mail server after RCPT 
TO:: 
| 550 Unrouteable address

Do you mean team+hapr...@tracker.debian.org?

Regards,
Bastian

-- 
You!  What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
--- End Message ---
--- Begin Message ---
Source: haproxy
Source-Version: 2.0.14-1
Done: Vincent Bernat 

We believe that the bug you reported is fixed in the latest version of
haproxy, 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.
Vincent Bernat  (supplier of updated haproxy 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: Thu, 16 Apr 2020 18:34:22 +0200
Source: haproxy
Architecture: source
Version: 2.0.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HAProxy Maintainers 
Changed-By: Vincent Bernat 
Closes: 93
Changes:
 haproxy (2.0.14-1) unstable; urgency=medium
 .
   * New upstream release.
 - BUG/CRITICAL: hpack: never index a header into the headroom after
 wrapping
 - BUG/MAJOR: http-ana: Always abort the request when a tarpit is
  triggered
 - BUG/MAJOR: list: fix invalid element address calculation
 - BUG/MAJOR: proxy_protocol: Properly validate TLV lengths
   * d/control: fix maintainer address. Closes: #93.
Checksums-Sha1:
 c7064f7591c84d937104a7f57af60bc9c2936f99 2309 haproxy_2.0.14-1.dsc
 ed06d1f83c987dd2a0de6e38fe199b10aa7218ac 2651320 haproxy_2.0.14.orig.tar.gz
 10ffcfec90b6dc1a04b9219fdfdc2f3ee517dbbb 68900 haproxy_2.0.14-1.debian.tar.xz
 936e6e87d2f7344a5fb46b8109ef8b8b346c04f4 8596 haproxy_2.0.14-1_amd64.buildinfo
Checksums-Sha256:
 24e5423ef5a89414298c0d04d51be779c3cb0bf7fa0a7b5f3cc78094e49d6779 2309 
haproxy_2.0.14-1.dsc
 552a708b8b6efd0f241f5d9fd7ad4168d37ce17cdb6dcb6239c2e519f0a63c75 2651320 
haproxy_2.0.14.orig.tar.gz
 35aa5691298b843a77d90900c25db034f8cf758a0cc729ff6a2451b64cf6bbdd 68900 
haproxy_2.0.14-1.debian.tar.xz
 48ab907e00ef9e81cceb1c49d17ff58b70f877b4218071d4d9d33c4985263550 8596 
haproxy_2.0.14-1_amd64.buildinfo
Files:
 c66157fbaf1ea84f4744c2256abe52b3 2309 net optional haproxy_2.0.14-1.dsc
 62fe30b1394ef2c0221061679e30d7fa 2651320 net optional 
haproxy_2.0.14.orig.tar.gz
 90f49c4eb3306de49b98a1310980caae 68900 net optional 
haproxy_2.0.14-1.debian.tar.xz
 4e8ce1338e0427455ede81fd334bfd1b 8596 net optional 
haproxy_2.0.14-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl6Yin8SHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5eecQAIoVaROOiENUa/BzCWeEJe7G4LcETZ1Z
VDRnanwGn1JxWFdGbbVyHIpd8HMseYWnCFYBLwLftOYTwzsBM4Y13tsWkY3IuloZ
MK5BjFUkRMKWDnFrUozWuefB9IzzedGbpulbSLV8ZPx2jgXb+yfxzOXg3iZsCft9
6VYPxnBA1pXJexfkYDdHP5JO2T59kHf3/g05qD7N7djS6Sc9wanlPVG+zB5Z6BTf
kOBK014vlL6LlaqfB4OepRCo2oo5Ag7J8wpjXApWr92qrBfWg2gfop6WYbgxFBkX
xbjkFM/EmBJo04XpztMRI54DcMH9LJ/JQ2NpWoA6BZ1wMlvON+amCOl0jc4l/arP
ofQFzgbY7aL1lK4Z3hp2wEnx9daZrytfYleZvQkZZzVsP+DtP2Yh0vpWkqZ4uonZ
+fERqvp2WO6gA899upAJ5iNAefi8ilfYZG3LFLTP020GBnD6ZX9TbKi9gdudcYag
Vm1j7amXQE1ds5RVp5rq+HHEISo6nHu2HCHRwxle/uX3MMwF4gDynFFLnzBb+Cjl
G1IWwPiyvtOUOirHvO73xUe3bdEU0f+cHldkDXHtup43imk3X1u8l1rELOr9sFZd
YAuZ0nvvPo7/OCDURU/EZ30WmrPRk1PDY592vSGCNI6HutqO37RJ9D1+IHsJKr5Z
+jsbgz1LNOj8
=ivMp
-END PGP SIGNATURE End Message ---

Bug#956875: marked as done (brotli: autopkgtest failure)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 18:18:32 +0200
with message-id <4deb8433-e86d-c72b-1148-adcf28e6b...@xs4all.nl>
and subject line Re: brotli: autopkgtest failure
has caused the Debian Bug report #956875,
regarding brotli: autopkgtest failure
to be marked as done.

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

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


-- 
956875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brotli
Version: 1.0.7-6
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for your package failed:

 autopkgtest [03:41:53]: test python3: [---
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3/dist-packages/brotli.py", line 8, in 
 import _brotli
 ModuleNotFoundError: No module named '_brotli'
 autopkgtest [03:41:53]: test python3: ---]
 autopkgtest [03:41:53]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
 python3  FAIL non-zero exit status 1
 autopkgtest [03:41:53]: test python3:  - - - - - - - - - - stderr - - - - - - 
- - - -
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3/dist-packages/brotli.py", line 8, in 
 import _brotli
 ModuleNotFoundError: No module named '_brotli'
 autopkgtest [03:41:53]:  summary
 python3  FAIL non-zero exit status 1

https://ci.debian.net/data/autopkgtest/testing/amd64/b/brotli/4952836/log.gz


This is a blocker for gcc-10:

 https://qa.debian.org/excuses.php?package=gcc-10

And other packages that depend on gcc-10.


The attached patch uses `py3version -s` to only test the supported python3 
versions.


Kind Regards,

Bas
diff -Nru brotli-1.0.7/debian/changelog brotli-1.0.7/debian/changelog
--- brotli-1.0.7/debian/changelog   2020-01-02 00:09:12.0 +0100
+++ brotli-1.0.7/debian/changelog   2020-04-16 10:07:13.0 +0200
@@ -1,3 +1,10 @@
+brotli (1.0.7-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use `py3versions -s` for autopkgtest.
+
+ -- Bas Couwenberg   Thu, 16 Apr 2020 10:07:13 +0200
+
 brotli (1.0.7-6) unstable; urgency=medium
 
   * Drop python2 support; Closes: #936242
diff -Nru brotli-1.0.7/debian/tests/python3 brotli-1.0.7/debian/tests/python3
--- brotli-1.0.7/debian/tests/python3   2020-01-02 00:09:12.0 +0100
+++ brotli-1.0.7/debian/tests/python3   2020-04-16 09:59:15.0 +0200
@@ -1,6 +1,6 @@
 #!/bin/sh -eu
 
-for python3 in $(py3versions -r 2>/dev/null); do
+for python3 in $(py3versions -s 2>/dev/null); do
 ${python3} -c 'import brotli as b; assert b.decompress(b.compress(b"x")) 
== b"x"'
 echo "${python3}: OK"
 done
--- End Message ---
--- Begin Message ---
notfound 956875 brotli/1.0.7-6
severity 956875 normal
thanks

On 4/16/20 10:18 AM, Bas Couwenberg wrote:
> The attached patch uses `py3version -s` to only test the supported python3 
> versions.

Which is effectively the same as `py3version -r` without
X-Python3-Version in d/control.

After retrying the autopkgtest it is no longer a failure.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Processed: RFS: pyenv/1.2.15-1 -- Python version manager

2020-04-16 Thread Debian Bug Tracking System

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

> close 945749
Bug #945749 [sponsorship-requests] RFS: pyenv/1.2.15-1 -- Python version manager
Marked Bug as done
> stop
Stopping processing here.

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

Bug#956163: marked as done (gnome-shell-extension-dashtodock: please check compatibility with GNOME Shell 3.36.x)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 14:33:34 +
with message-id 
and subject line Bug#956163: fixed in gnome-shell-extension-dashtodock 
67+git20200225-1
has caused the Debian Bug report #956163,
regarding gnome-shell-extension-dashtodock: please check compatibility with 
GNOME Shell 3.36.x
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.)


-- 
956163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-dashtodock
Version: 67-1
Severity: important
Tags: bullseye sid
Control: block 954422 by -1
Forwarded: https://github.com/micheleg/dash-to-dock/pull/1097

GNOME Shell 3.36.x is currently in experimental, and should hopefully
be heading to unstable soon. Please check whether this extension is
compatible. It looks as though the answer is "no" at the moment: see
the Github pull request above for current progress.

You'll probably want to add a Recommends or even Depends on
gnome-shell-extension-prefs, a new package split out from gnome-shell that
is meant to be taking over responsibility for enabling and disabling
extensions from gnome-tweaks (at the moment they both offer this,
but there's a gnome-tweaks merge request open to remove the duplicate
functionality).

One thing that is definitely not compatible is that this extension runs:

Util.spawn(["gnome-shell-extension-prefs", Me.metadata.uuid]);

This is no longer supported since GNOME Shell 3.36.1:
gnome-shell-extension-prefs no longer takes a UUID as a command-line
argument. Some of the Debian GNOME team have wondered whether it's
feasible to patch back in, but the code involved is surprisingly
extensive, so the answer might be no.

As far as I can tell from GNOME Shell's upstream commit history, the
preferred way to launch extension preferences in sufficiently recent
versions is to call imports.misc.extensionUtils.openPrefs(), which
was added by gnome-shell!1163. It isn't in 3.36.1, but the version
in experimental (which is halfway between upstream 3.36.1 and 3.36.2)
does have it.

To support older GNOME versions, fall back to the spawn call if
imports.misc.extensionUtils doesn't have an openPrefs method.

Sample code:
https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/pull/203

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 67+git20200225-1
Done: =?utf-8?q?Marco_Trevisan_=28Trevi=C3=B1o=29?= 

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

Debian distribution maintenance software
pp.
Marco Trevisan (Treviño)  (supplier of updated 
gnome-shell-extension-dashtodock 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, 25 Feb 2020 19:04:26 +0100
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 67+git20200225-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Marco Trevisan (Treviño) 
Closes: 956163
Changes:
 gnome-shell-extension-dashtodock (67+git20200225-1) unstable; urgency=medium
 .
   [ Marco Trevisan (Treviño) ]
   * New upstream release with git snapshot
   * debian/control: Depend on gnome-shell 3.35.90
   * d/p/appIcons-windowPreview-Use-vfunc-instead-of-signals.patch,
 d/p/general-Update-to-gnome-shell-3.36-code-with-more-actor-i.patch,
 d/p/metadata-Set-extension-compatible-with-shell-3.36-only.patch,
 d/p/utils-Use-more-ES6-compliant-code-to-override-calls.patch,
 d/p/windowPreview-Only-hide-the-close-button-if-no-entry-chil.patch:
 - Support gnome-shell 3.36
 .
   [ Jonathan Carter ]
   * Update standards version to 4.5.0
   * Merge MR#1 (see changes above, thank you Marco) (Closes: #956163)
   * Add gnome-shell-extension-prefs to recommends
Checksums-Sha1:
 ec41a3d890533d8b711dcb6eca5b6a95bb9eb649 2320 
gnome-shell-extension-dashtodock_67+git20200225-1.dsc
 e5301b84f5c065b1f4e58b015ff1af7a36f0d527 311466 
gnome-shell-extension-dashtodock_67+git20200225.orig.tar.gz

Bug#955061: marked as done (python-bumps: FTBFS with Sphinx 2.4: mv: cannot stat '*.png': No such file or directory)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 14:33:44 +
with message-id 
and subject line Bug#955061: fixed in python-bumps 0.7.14-3
has caused the Debian Bug report #955061,
regarding python-bumps: FTBFS with Sphinx 2.4: mv: cannot stat '*.png': No such 
file or directory
to be marked as done.

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

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


-- 
955061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bumps
Version: 0.7.14-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-bumps fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd build/texinfo; \
> for p in *.png; do mv $p bumps-$p; done; \
> sed "s/@image{/@image{bumps-/" -i bumps.texi; \
> makeinfo bumps.texi
> mv: cannot stat '*.png': No such file or directory
> bumps.texi:1439: warning: could not find @image file 
> `bumps-bumps-figures/curve-11.txt' nor alternate text
> bumps.texi:3514: warning: could not find @image file 
> `bumps-bumps-figures/var.txt' nor alternate text
> bumps.texi:3527: warning: could not find @image file 
> `bumps-bumps-figures/corr.txt' nor alternate text
> bumps.texi:3537: warning: could not find @image file 
> `bumps-bumps-figures/error.txt' nor alternate text
> bumps.texi:5578: warning: could not find @image file 
> `bumps-bumps-figures/entropy-discrete.txt' nor alternate text
> bumps.texi:5606: warning: could not find @image file 
> `bumps-bumps-figures/entropy-continuous.txt' nor alternate text
> dh_installinfo
> dh_installinfo: error: Cannot find (any matches for) 
> "build/texinfo/bumps-*.png" (tried in ., debian/tmp)
> 
> make[1]: *** [debian/rules:54: override_dh_installinfo-indep] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/26/python-bumps_0.7.14-2_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: 
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

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: python-bumps
Source-Version: 0.7.14-3
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
python-bumps, 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.
Drew Parsons  (supplier of updated python-bumps 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: Thu, 16 Apr 2020 21:49:15 +0800
Source: python-bumps
Architecture: source
Version: 0.7.14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 955061
Changes:
 python-bumps (0.7.14-3) unstable; urgency=medium
 .
   * info file generated by sphinx 2.4 no longer links to png image
 files. Closes: #955061.
Checksums-Sha1:
 f48453a909c4132995063824260aff32e3b2398d 2612 python-bumps_0.7.14-3.dsc
 ce34faed56562fc2b86b9ce076b1dcb13e571f08 12996 
python-bumps_0.7.14-3.debian.tar.xz
Checksums-Sha256:
 30f32d5aa7d096620e11b9e26d812f3ca48a10d1f614086dd414900dfa2a0836 2612 
python-bumps_0.7.14-3.dsc
 4817991df3f126fd76b8f89f4bf01bc820c75768b8c10bbfd6a20a06cf70bc38 12996 
python-bumps_0.7.14-3.debian.tar.xz
Files:
 5d6a0ce0ca0512dae8ad9d970cb54b06 2612 science optional 
python-bumps_0

Processed: Close #954762

2020-04-16 Thread Debian Bug Tracking System

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

> close 954762
Bug #954762 [systraq] systraq: Annoying as Hell
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#955098: marked as done (python-os-api-ref: FTBFS with Sphinx 2.4: ImportError: cannot import name 'AutoDirective' from 'sphinx.ext.autodoc' (unknown location))

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 13:34:30 +
with message-id 
and subject line Bug#955098: fixed in sphinx-testing 1.0.1-0.1
has caused the Debian Bug report #955098,
regarding python-os-api-ref: FTBFS with Sphinx 2.4: ImportError: cannot import 
name 'AutoDirective' from 'sphinx.ext.autodoc' (unknown location)
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.)


-- 
955098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-os-api-ref
Version: 1.6.2+dfsg1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-os-api-ref fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + PKGOS_USE_PY2=no
> + shift
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.7 3.8
> + [ yes = no ]
> + [ no = yes ]
> + [ disabled = disabled ]
> + continue
> + [ 3.7 = disabled ]
> + echo 3.7
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + [ 3 = 3 ]
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -x /usr/bin/python3-stestr ]
> + STESTR=stestr
> + rm -rf .stestr
> + PYTHON=python3.7 stestr run --parallel --subunit
> + subunit2pyunit
> os_api_ref.tests.test_os_api_ref.TestOs_api_ref.test_something
> os_api_ref.tests.test_os_api_ref.TestOs_api_ref.test_something ... ok
> os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all
> os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all ... FAIL
> os_api_ref.tests.test_microversions.TestMicroversions.test_js_declares
> os_api_ref.tests.test_microversions.TestMicroversions.test_js_declares ... 
> FAIL
> os_api_ref.tests.test_basic_example.TestBasicExample.test_parameters
> os_api_ref.tests.test_basic_example.TestBasicExample.test_parameters ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_empty_parameter_file
> os_api_ref.tests.test_warnings.TestWarnings.test_empty_parameter_file ... FAIL
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_method
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_method ... FAIL
> os_api_ref.tests.test_microversions.TestMicroversions.test_mv_selector
> os_api_ref.tests.test_microversions.TestMicroversions.test_mv_selector ... 
> FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_invalid_parameter_definition
> os_api_ref.tests.test_warnings.TestWarnings.test_invalid_parameter_definition 
> ... FAIL
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_response
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_response ... 
> FAIL
> os_api_ref.tests.test_microversions.TestMicroversions.test_parameters_table
> os_api_ref.tests.test_microversions.TestMicroversions.test_parameters_table 
> ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_field
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_field ... FAIL
> os_api_ref.tests.test_microversions.TestMicroversions.test_rest_method
> os_api_ref.tests.test_microversions.TestMicroversions.test_rest_method ... 
> FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_lookup_name
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_lookup_name ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_path_parameter_in_stanza
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_path_parameter_in_stanza
>  ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_no_parameters_set
> os_api_ref.tests.test_warnings.TestWarnings.test_no_parameters_set ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_out_of_order
> os_api_ref.tests.test_warnings.TestWarnings.test_out_of_order ... FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
> os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist ... 
> FAIL
> 
> ==
> FAIL: os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all
> os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all
> -

Bug#955101: marked as done (sphinx-testing: FTBFS with Sphinx 2.4: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 13:34:30 +
with message-id 
and subject line Bug#955101: fixed in sphinx-testing 1.0.1-0.1
has caused the Debian Bug report #955101,
regarding sphinx-testing: FTBFS with Sphinx 2.4: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.7 3.8" returned exit code 13
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.)


-- 
955101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-testing
Version: 0.8.1-1.2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

sphinx-testing fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -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_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/tmpdir.py -> 
> /<>/.pybuild/cpython3_3.7_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/util.py -> 
> /<>/.pybuild/cpython3_3.7_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/path.py -> 
> /<>/.pybuild/cpython3_3.7_sphinx-testing/build/sphinx_testing
> running egg_info
> writing src/sphinx_testing.egg-info/PKG-INFO
> writing dependency_links to src/sphinx_testing.egg-info/dependency_links.txt
> writing requirements to src/sphinx_testing.egg-info/requires.txt
> writing top-level names to src/sphinx_testing.egg-info/top_level.txt
> reading manifest file 'src/sphinx_testing.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/sphinx_testing.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/tmpdir.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/util.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-testing/build/sphinx_testing
> copying src/sphinx_testing/path.py -> 
> /<>/.pybuild/cpython3_3.8_sphinx-testing/build/sphinx_testing
> running egg_info
> writing src/sphinx_testing.egg-info/PKG-INFO
> writing dependency_links to src/sphinx_testing.egg-info/dependency_links.txt
> writing requirements to src/sphinx_testing.egg-info/requires.txt
> writing top-level names to src/sphinx_testing.egg-info/top_level.txt
> reading manifest file 'src/sphinx_testing.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/sphinx_testing.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.7_sphinx-testing/build; python3.7 -m 
> nose -v tests
> test_abspath (test_path.TestPath) ... ok
> test_basename (test_path.TestPath) ... ok
> test_copytree (test_path.TestPath) ... ok
> test_dirname (test_path.TestPath) ... ok
> test_exists (test_path.TestPath) ... ok
> test_instantiate (test_path.TestPath) ... ok
> test_isabs (test_path.TestPath) ... ok
> test_isdir (test_path.TestPath) ... ok
> test_isfile (test_path.TestPath) ... ok
> test_islink (test_path.TestPath) ... ok
> test_ismount (test_path.TestPath) ... ok
> test_jonpath (test_path.TestPath) ... ok
> test_listdir (test_path.TestPath) ... ok
> test_makedirs (test_path.TestPath) ... ok
> test_move (test_path.TestPath) ... ok
> test_read_bytes (test_path.TestPath) ... ok
> test_read_text (test_path.TestPath) ... ok
> test_rmtree (test_path.TestPath) ... ok
> test_suffix (test_path.TestPath) ... ok
> test_unlink (test_path.TestPath) ... ok
> test_utime (test_path.TestPath) ... ok
> test_write_bytes (test_path.TestPath) ... ok
> test_write_text (test_path.TestPath) ... ok
> test_mkdtemp (test_tmpdir.TestTmpdir) ... ok
> test_with_tmpdir (test_tmpdir.TestTmpdir) ... ok
> test_TestApp (test_util.TestSphinxTesting) ... ERROR
> test_TestApp_cleanup (test_util.TestSphinxTesting) ... ERROR
> test_TestApp_cleanup_w

Bug#937009: marked as done (mercurial: Python2 removal in sid/bullseye)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 13:33:44 +
with message-id 
and subject line Bug#937009: fixed in mercurial 5.3.2-1+exp1
has caused the Debian Bug report #937009,
regarding mercurial: 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.)


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

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: mercurial
Source-Version: 5.3.2-1+exp1
Done: Julien Cristau 

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 10:37:41 +0200
Source: mercurial
Architecture: source
Version: 5.3.2-1+exp1
Distribution: experimental
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Julien Cristau 
Closes: 937009
Changes:
 mercurial (5.3.2-1+exp1) experimental; urgency=medium
 .
   * Use python3 (closes: #937009).
   * mercurial Provides python3-mercurial so extensions can depend on
 that instead of a hazardous versioned dependency.
   * Add Breaks on all extensions.  To be updated as we don't know what
 version will use python3.
   * Pull patches from upstream repo to fix python3.8 compat.
Checksums-Sha1:
 95244c8319c9418b5cd2f1d3a836c36fc6639acd 2802 mercurial_5.3.2-1+exp1.dsc
 ca6d926a7e59ecd2944c07d167d302459db69941 59436 
mercurial_5.3.2-1+exp1.debian.tar.xz
Checksums-Sha256:
 8b6aa7074aea183d17238f7bfaeeeb6d90dfe8d5bf796335e00332a02acab10a 2802 
mercurial_5.3.2-1+exp1.dsc
 22d4bdc58bff26d9c5b552994

Bug#953427: marked as done (micro and dch does not work well together)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 13:03:52 +
with message-id 
and subject line Bug#953427: fixed in micro 2.0.3-1
has caused the Debian Bug report #953427,
regarding micro and dch does not work well together
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.)


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

Package: devscripts,micro
Severity: important

When EDITOR is set to micro all dch commands first opens a blank buffer 
and only after closing the blank buffer debian/changelog.dch file is 
shown. This is a confusing behaviour and may not be obvious to most 
users. I'm not sure if it is a bug in micro or dch. Probably micro is 
not properly handling the way it is called by dch.
--- End Message ---
--- Begin Message ---
Source: micro
Source-Version: 2.0.3-1
Done: Utkarsh Gupta 

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated micro 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: Thu, 16 Apr 2020 17:53:55 +0530
Source: micro
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Utkarsh Gupta 
Closes: 953427
Changes:
 micro (2.0.3-1) unstable; urgency=medium
 .
   * New upstream version 2.0.3
 - Support +LINE:COL flag syntax for cursor position (Closes: #953427)
   * Make d/watch cleaner
   * Refresh patch
Checksums-Sha1:
 de8677990e3e42946daa9c6004966e509f513be8 2711 micro_2.0.3-1.dsc
 de9bda9766a691638d1b7ce89026002f2835c8e7 771983 micro_2.0.3.orig.tar.gz
 9b161196db19c58627ca3a5eab9f5f808ea9f410 4960 micro_2.0.3-1.debian.tar.xz
 fa44b96ca0a407eed1c249580be1670e8f401b77 7987 micro_2.0.3-1_amd64.buildinfo
Checksums-Sha256:
 a8469275f22f51e4d39d07db94db857946ee763572824b6ba85d39010f006eaf 2711 
micro_2.0.3-1.dsc
 5924ad1af80417907e403482af49bc709087221538ddfdd9bb54d966551a0460 771983 
micro_2.0.3.orig.tar.gz
 c1b2f5f3ba4792a1847fb294aa9275552e64d209c1888a997971bd2c21ead69e 4960 
micro_2.0.3-1.debian.tar.xz
 2cc7898cfde5e28ff9978fd8837bf3ebfcbdf78962a7ffbdacb00cc5a14f7ef6 7987 
micro_2.0.3-1_amd64.buildinfo
Files:
 abb63843feb99045e9cc1f13fc590c74 2711 editors optional micro_2.0.3-1.dsc
 d996d733dc25da4bb67cde3dd0332bf3 771983 editors optional 
micro_2.0.3.orig.tar.gz
 2d8bdff34adcfa166bd487f3db916186 4960 editors optional 
micro_2.0.3-1.debian.tar.xz
 6f6262da6fabc99edc00a494b04e4420 7987 editors optional 
micro_2.0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl6YUHgTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLllZCD/9spWaVioglDpQBNY+n6NNmjpNaX1w1
DAyhESEpT+qXlANzYCI9MPAmPKKY7ej2N1XmcDNkB1ldbmVC0pXmRYDtl3TsL/7p
+Pa3IPGKRdVXC3OZkg+l/Z80sjtRdsDXbbiYsDXJaXQ9GJUUYyHJdBI5wOQPTe0o
9SIo44BKHKx8GIoug3ATsyiCxHuWZU/m7jW664pAHChLiFdiPus7ZQ64XgnSa3HA
lNWRkvEX01mfJCzDuLOkZfbGciwSSsGuDFqgAWej2i0pir6YvAIgPi4KysCMdnI2
5ziZ3ZNTGO3exz2JL1PYX5yxaUTzlcN/S4K56a0DGHnqdr6AnEsNdcmsLxKNm6gZ
83gkundYrsFMvvmKjvROEZ6MTV/19q8tnQasVgz+/dVdhBnx4wPCx87iUXaM7rc5
fwKIZtdxd6AHoefL6nDEvq88zH9jbIgdutb3PJo2CkBxVLx5rXB6kt2Hrx0FryWG
j6nBh06A+RVuvINvO07He/0VvVcJraUJ/adtxi66696KALXu41ev+syV21KbUUqf
U+wftvzs8pZl6gtRI5GLNF+12bqhFDVYmLi72nOIgRFRxEPosC/JDMuOPTN3W7a6
8ETCQgPZ6DXZsUb+bul1ZFFvNvwOZ+MFB2L4InUoPpW2R30ORe7NIWoW+ZI8wWJR
KBGWBuku83PdHA==
=Owki
-END PGP SIGNATURE End Message ---

Bug#956450: marked as done (libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 12:45:41 +
with message-id 
and subject line Bug#956450: fixed in libreoffice 1:6.4.3-1
has caused the Debian Bug report #956450,
regarding libreoffice-common: Upgrade fail because of Application.xba file 
conflict with libreoffice-base
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.)


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

Package: libreoffice-common
Version: 1:6.4.2-3
Severity: serious

Setting RC severity because this break 'apt dist-upgrade' and leave the
machine in a problematic state.  Did not find an existing report, but
might have missed one among the pile in bts.

Upgrading a KDE desktop from from buster to bullseye using 'apt
dist-upgrade' fail because apt aborts halfway in the process when trying
to unpack libreoffice-common version 1:6.4.2-3 over version
1:6.1.5-3+deb1@u5, because the new package contain the file
/usr/lib/libreoffice/share/basic/Access2Base/Application.xba which is
also in the package libreoffice-base 1:6.1.5-3+deb1@u5.

Not sure which one of these packages have this problem, but found it
best to report the issue anyway.

Missing breaks/replaces?

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.4.3-1
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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: Fri, 10 Apr 2020 18:51:13 +0200
Source: libreoffice
Architecture: source
Version: 1:6.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 956450
Changes:
 libreoffice (1:6.4.3-1) unstable; urgency=medium
 .
   * LibreOffice 6.4.3 final release (identical to rc2)
 .
   * upload to unstable
 .
   * debian/patches/fix-lo-xlate-lang-nb.diff: norwegian -> norwegian_bokmal
 for nb
 .
   * merge from Ubuntu:
 - libreoffice-common: Add Replaces libreoffice-base (<< 1:6.4.0~beta1-2~)
   (closes: #956450)
Checksums-Sha1:
 98f060afa338a7ffa601d563804371a9d1bdb1fb 30493 libreoffice_6.4.3-1.dsc
 874b413315d60e70ce74bfd0f4bc79cf9fe976d2 87697072 
libreoffice_6.4.3.orig-helpcontent2.tar.xz
 e144e0629e187f4b602c6243561931c56e6b3292 172707348 
libreoffice_6.4.3.orig-translations.tar.xz
 c4e54155123ac14796f0241a0d37e45c1ebedd08 230409812 
libreoffice_6.4.3.orig.tar.xz
 6358e097b6bfb087e0dc64aa17b2391b35e51aab 833 libreoffice_6.4.3.orig.tar.xz.asc
 98012467da33775e983f69f7f5e2c578ca678598 10904736 
libreoffice_6.4.3-1.debian.tar.xz
 8d6cd7a685c64eb2a5028a2e0cf93e7309c1762a 39800 
libreoffice_6.4.3-1_source.buildinfo
Checksums-Sha256:
 a9f3b1e62651cda42cfe0e732261363ee2b76430f04e4e3cf48626cdfef62a51 30493 
libreoffice_6.4.3-1.dsc
 8002f5ab9e020af4543777f7d2a07cc5cf90360b8d3912f4b000a6870259cd82 87697072 
libreoffice_6.4.3.orig-helpcontent2.tar.xz
 361a7262ae444133636d1689d49fd7b4c4cc1b994f24c14ad6becbae8ddff036 172707348 
libreoffice_6.4.3.orig-translations.tar.xz
 bc14547c188efa15f4cb36cfb3da7cacb3037a7448d1bba8a58ed6a320ccabb2 230409812 
libreoffice_6.4.3.orig.tar.xz
 f5fe411d44c29c8fbb173458508c9b97a8f525718681fb587da7d0c31f518c54 833 
libreoffice_6.4.3.orig.tar.xz.asc
 465f472cb09eaeec6a7dd1fdb12126750f9a0648b5d3fb02c0fa7409d84c 10904736 
libreoffice_6.4.3-1.debian.tar.xz
 0cf1593503e06791ee6e323aea3c25ae0ae625f9c4364412ecdd27136b61b534 39800 
libreoffice_6.4.3-1_source.buildinfo
Files:
 70e088e63739f66c3ffb0a7459deba2c 30493 editors optional libreoffice_6.4.3-1.dsc
 03b5f211af9b59055a0959de60b538ee 87697072 editors optional 
libreoffice_6.4.3.orig-helpcontent2.tar.xz
 4659143e34d101b0a384ea740fb27a75 172707348 editors optional 
libreoffice_6.4.3.orig-translations.tar.xz
 56ffec862a6dc2ae19d74e71260e8155 230409812 editors optional 
libreoffice_6.4.3.orig.tar.xz
 d9dabbaa733dd3b5d968375ce16c7853 833 editors optiona

Bug#952286: marked as done (libpostscriptbarcode: FTBFS: GPL Ghostscript 9.50: Unrecoverable error, exit code 1)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 13:31:35 +0100
with message-id 

and subject line Bug#952286: libpostscriptbarcode: FTBFS: GPL Ghostscript 9.50: 
Unrecoverable error, exit code 1
has caused the Debian Bug report #952286,
regarding libpostscriptbarcode: FTBFS: GPL Ghostscript 9.50: Unrecoverable 
error, 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.)


-- 
952286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpostscriptbarcode
Version: 20140312-2
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[1]: Entering directory '/<>'
> build/make_deps src/upca.ps build/resource/Resource 
> build/packaged_resource/Resource >src/upca.d
> build/make_deps src/gs1-cc.ps build/resource/Resource 
> build/packaged_resource/Resource >src/gs1-cc.d
> build/make_deps src/hibcqrcode.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibcqrcode.d
> build/make_deps src/hibcmicropdf417.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibcmicropdf417.d
> build/make_deps src/hibccodablockf.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibccodablockf.d
> build/make_deps src/databarstackedcomposite.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databarstackedcomposite.d
> build/make_deps src/postnet.ps build/resource/Resource 
> build/packaged_resource/Resource >src/postnet.d
> build/make_deps src/gs1qrcode.ps build/resource/Resource 
> build/packaged_resource/Resource >src/gs1qrcode.d
> build/make_deps src/msi.ps build/resource/Resource 
> build/packaged_resource/Resource >src/msi.d
> build/make_deps src/pdf417.ps build/resource/Resource 
> build/packaged_resource/Resource >src/pdf417.d
> build/make_deps src/isbn.ps build/resource/Resource 
> build/packaged_resource/Resource >src/isbn.d
> build/make_deps src/hibccode128.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibccode128.d
> build/make_deps src/royalmail.ps build/resource/Resource 
> build/packaged_resource/Resource >src/royalmail.d
> build/make_deps src/databarstackedomni.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databarstackedomni.d
> build/make_deps src/renlinear.ps build/resource/Resource 
> build/packaged_resource/Resource >src/renlinear.d
> build/make_deps src/azteccode.ps build/resource/Resource 
> build/packaged_resource/Resource >src/azteccode.d
> build/make_deps src/ismn.ps build/resource/Resource 
> build/packaged_resource/Resource >src/ismn.d
> build/make_deps src/databartruncated.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databartruncated.d
> build/make_deps src/databarexpanded.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databarexpanded.d
> build/make_deps src/upce.ps build/resource/Resource 
> build/packaged_resource/Resource >src/upce.d
> build/make_deps src/onecode.ps build/resource/Resource 
> build/packaged_resource/Resource >src/onecode.d
> build/make_deps src/databarexpandedstackedcomposite.ps 
> build/resource/Resource build/packaged_resource/Resource 
> >src/databarexpandedstackedcomposite.d
> build/make_deps src/databarstacked.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databarstacked.d
> build/make_deps src/gs1-128composite.ps build/resource/Resource 
> build/packaged_resource/Resource >src/gs1-128composite.d
> build/make_deps src/hibcdatamatrix.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibcdatamatrix.d
> build/make_deps src/hibccode39.ps build/resource/Resource 
> build/packaged_resource/Resource >src/hibccode39.d
> build/make_deps src/issn.ps build/resource/Resource 
> build/packaged_resource/Resource >src/issn.d
> build/make_deps src/pzn.ps build/resource/Resource 
> build/packaged_resource/Resource >src/pzn.d
> build/make_deps src/renmatrix.ps build/resource/Resource 
> build/packaged_resource/Resource >src/renmatrix.d
> build/make_deps src/code32.ps build/resource/Resource 
> build/packaged_resource/Resource >src/code32.d
> build/make_deps src/telepen.ps build/resource/Resource 
> build/packaged_resource/Resource >src/telepen.d
> build/make_deps src/databartruncatedcomposite.ps build/resource/Resource 
> build/packaged_resource/Resource >src/databartruncatedcomposite.d
> build/make_deps src/planet.ps build/resource/Resource 
> build/packaged_resource

Bug#955076: marked as done (python-periodictable: FTBFS with Sphinx 2.4: mv: cannot stat '*.png': No such file or directory)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 11:33:55 +
with message-id 
and subject line Bug#955076: fixed in python-periodictable 1.5.2-3
has caused the Debian Bug report #955076,
regarding python-periodictable: FTBFS with Sphinx 2.4: mv: cannot stat '*.png': 
No such file or directory
to be marked as done.

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

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


-- 
955076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-periodictable
Version: 1.5.2-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-periodictable fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd build/texinfo; \
> for p in *.png; do mv $p periodictable-$p; done; \
> sed "s/@image{/@image{periodictable-/" -i periodictable.texi; \
> makeinfo periodictable.texi
> mv: cannot stat '*.png': No such file or directory
> periodictable.texi:233: warning: could not find @image file 
> `periodictable-periodictable-figures/sld_plot1.txt' nor alternate text
> periodictable.texi:432: warning: could not find @image file 
> `periodictable-periodictable-figures/magnetic_ff1.txt' nor alternate text
> periodictable.texi:3335: warning: could not find @image file 
> `periodictable-periodictable-figures/density_plot1.txt' nor alternate text
> dh_installinfo
> dh_installinfo: error: Cannot find (any matches for) 
> "build/texinfo/periodictable-*.png" (tried in ., debian/tmp)
> 
> make[1]: *** [debian/rules:27: override_dh_installinfo] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/26/python-periodictable_1.5.2-2_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: 
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

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: python-periodictable
Source-Version: 1.5.2-3
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
python-periodictable, 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.
Drew Parsons  (supplier of updated python-periodictable 
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: Thu, 16 Apr 2020 19:15:36 +0800
Source: python-periodictable
Architecture: source
Version: 1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 955076
Changes:
 python-periodictable (1.5.2-3) unstable; urgency=medium
 .
   * png images no longer referenced in info file
 (generated by sphinx 2.4) Closes: #955076.
Checksums-Sha1:
 07e058fca8dd8a57e1141ab26092c0075918c2cb 2450 python-periodictable_1.5.2-3.dsc
 47dd891d477e4fa873823f65b2f8514da6936bf8 5988 
python-periodictable_1.5.2-3.debian.tar.xz
Checksums-Sha256:
 d7a097785207d10bb12345053ec8e7d07b21d59a480d5f47a349d3c71e8a1703 2450 
python-periodictable_1.5.2-3.dsc
 b7aeeb4ae98b166219417e81ecc6628822c3863a2ee6c40324c19aa6da7936d8 5988 
python-periodictable_1.5.2-3.debian.tar.xz
Files:
 b61e567e972271bfbdbfd8506698604f 2450 science optional 
python-periodictable_1.5.2-3.dsc
 0a8133418b6b3ee258e3ebf45c07875e 5988 science optional 
python-periodictable_1.5.2-3.debian.tar.xz

-B

Bug#955088: marked as done (sahara: FTBFS with Sphinx 2.4: ValueError: invalid literal for int() with base 10: '800px')

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 11:04:28 +
with message-id 
and subject line Bug#955088: fixed in sahara 1:11.0.0-4
has caused the Debian Bug report #955088,
regarding sahara: FTBFS with Sphinx 2.4: ValueError: invalid literal for int() 
with base 10: '800px'
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.)


-- 
955088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sahara
Version: 1:11.0.0-3
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

sahara fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> PYTHONPATH=. python3 -m sphinx -D html_last_updated_fmt="March 22, 2020" -b 
> html doc/source 
> /<>/debian/sahara-doc/usr/share/doc/sahara-doc/html
> Running Sphinx v2.4.3
> connecting events for openstackdocstheme
> making output directory... done
> [oslo_config.sphinxconfiggen] reading config generator instructions from 
> /<>/doc/source/config-generator.conf
> [oslo_config.sphinxconfiggen] writing sample configuration to 
> /<>/doc/source/sample.config
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> adding role barbican-doc to link to 
> https://docs.openstack.org/barbican/train/%s
> adding role castellan-doc to link to 
> https://docs.openstack.org/castellan/train/%s
> adding role designate-doc to link to 
> https://docs.openstack.org/designate/train/%s
> adding role devstack-doc to link to 
> https://docs.openstack.org/devstack/train/%s
> adding role ironic-doc to link to https://docs.openstack.org/ironic/train/%s
> adding role keystone-doc to link to 
> https://docs.openstack.org/keystone/train/%s
> adding role keystoneauth-doc to link to 
> https://docs.openstack.org/keystoneauth/train/%s
> adding role kolla-ansible-doc to link to 
> https://docs.openstack.org/kolla-ansible/train/%s
> adding role neutron-doc to link to https://docs.openstack.org/neutron/train/%s
> adding role nova-doc to link to https://docs.openstack.org/nova/train/%s
> adding role oslo.messaging-doc to link to 
> https://docs.openstack.org/oslo.messaging/train/%s
> adding role oslo.middleware-doc to link to 
> https://docs.openstack.org/oslo.middleware/train/%s
> adding role sahara-plugin-ambari-doc to link to 
> https://docs.openstack.org/sahara-plugin-ambari/train/%s
> adding role sahara-plugin-cdh-doc to link to 
> https://docs.openstack.org/sahara-plugin-cdh/train/%s
> adding role sahara-plugin-mapr-doc to link to 
> https://docs.openstack.org/sahara-plugin-mapr/train/%s
> adding role sahara-plugin-spark-doc to link to 
> https://docs.openstack.org/sahara-plugin-spark/train/%s
> adding role sahara-plugin-storm-doc to link to 
> https://docs.openstack.org/sahara-plugin-storm/train/%s
> adding role sahara-plugin-vanilla-doc to link to 
> https://docs.openstack.org/sahara-plugin-vanilla/train/%s
> adding role tooz-doc to link to https://docs.openstack.org/tooz/train/%s
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 53 source files that are out of date
> updating environment: [new config] 53 added, 0 changed, 0 removed
> reading sources... [  1%] admin/advanced-configuration-guide
> reading sources... [  3%] admin/configs-recommendations
> reading sources... [  5%] admin/configuration-guide
> reading sources... [  7%] admin/index
> reading sources... [  9%] admin/upgrade-guide
> reading sources... [ 11%] cli/index
> reading sources... [ 13%] cli/sahara-status
> reading sources... [ 15%] configuration/descriptionconfig
> loading config file tools/config/config-generator.sahara.conf
> reading sources... [ 16%] configuration/index
> reading sources... [ 18%] configuration/sampleconfig
> reading sources... [ 20%] contributor/adding-database-migrations
> reading sources... [ 22%] contributor/apiv2
> reading sources... [ 24%] contributor/dashboard-dev-environment-guide
> reading sources... [ 26%] contributor/development-environment
> reading sources... [ 28%] contributor/development-guidelines
> reading sources... [ 30%] contributor/devstack
> reading sources... [ 32%] contributor/gerrit
> reading sources... [ 33%] contributor/how-to-build-oozie
> reading sources... [ 35%] contributor/how-to-participate
> reading sources... [ 37%] contributor/image-gen
> reading sources... [ 39%] contributor/inde

Bug#955649: marked as done (nordugrid-arc: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 10:49:13 +
with message-id 
and subject line Bug#955649: fixed in nordugrid-arc 6.5.0-3
has caused the Debian Bug report #955649,
regarding nordugrid-arc: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


-- 
955649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nordugrid-arc
Version: 6.5.0-2
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[7]: Entering directory '/<>/src/hed/libs/credential/test'
> ..F.F.F.F.
> 
> CredentialTest.cpp:168:Assertion
> Test name: CredentialTest::testhostcert
> assertion failed
> - Expression: host_cert.GetVerification()
> 
> CredentialTest.cpp:221:Assertion
> Test name: CredentialTest::testusercert
> assertion failed
> - Expression: user_cert.GetVerification()
> 
> CredentialTest.cpp:282:Assertion
> Test name: CredentialTest::testproxy
> assertion failed
> - Expression: user_proxy.GetVerification()
> 
> CredentialTest.cpp:338:Assertion
> Test name: CredentialTest::testproxy2proxy
> assertion failed
> - Expression: user_proxy1.GetVerification()
> 
> Failures !!!
> Run: 6   Failure total: 4   Failures: 4   Errors: 0
> FAIL: CredentialTest
> .F
> 
> VOMSUtilTest.cpp:132:Assertion
> Test name: VOMSUtilTest::VOMSTrustListTest
> equality assertion failed
> - Expected: 1
> - Actual  : 0
> 
> Failures !!!
> Run: 1   Failure total: 1   Failures: 1   Errors: 0
> FAIL: VOMSUtilTest
> .
> 
> OK (1)
> PASS: listfuncTest
> ===
> 2 of 3 tests failed
> Please report to http://bugzilla.nordugrid.org/
> ===
> make[7]: *** [Makefile:823: check-TESTS] Error 1
> make[7]: Leaving directory '/<>/src/hed/libs/credential/test'
> make[6]: *** [Makefile:950: check-am] Error 2
> make[6]: Leaving directory '/<>/src/hed/libs/credential/test'
> make[5]: *** [Makefile:906: check-recursive] Error 1
> make[5]: Leaving directory '/<>/src/hed/libs/credential'
> make[4]: *** [Makefile:563: check-recursive] Error 1
> make[4]: Leaving directory '/<>/src/hed/libs'
> make[3]: *** [Makefile:605: check-recursive] Error 1
> make[3]: Leaving directory '/<>/src/hed'
> make[2]: *** [Makefile:550: check-recursive] Error 1
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:616: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/04/02/nordugrid-arc_6.5.0-2_unstable.log

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

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: nordugrid-arc
Source-Version: 6.5.0-3
Done: Mattias Ellert 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 08:19:10 +0200
Source: nordugrid-arc
Architecture: source
Version: 6.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Closes: 955649
Changes:
 nordugrid-arc (6.5.0-3) unstable; urgency=medium
 .
   * Adapt to openssl 1.1.1f (Closes: #955649)
Checksums-Sha1:
 71f3483a6f3461e55893ad495bcc7878f9569ff3 4709 nordugrid-arc_6.5.0-3.dsc
 7b9d94d77e9743fe11178e6f25290879464da9b0 24880 
nordugrid-arc_6.5.0-3.debian.tar.xz
 139f1197308fbf8e791656b

Bug#949169: marked as done (appstream-glib FTBFS in the year 2020)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 10:33:41 +
with message-id 
and subject line Bug#949169: fixed in appstream-glib 0.7.17-1
has caused the Debian Bug report #949169,
regarding appstream-glib FTBFS in the year 2020
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.)


-- 
949169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-glib
Version: 0.7.14-1
Severity: serious
Tags: ftbfs fixed-upstream
Forwarded: 
https://github.com/hughsie/appstream-glib/commit/953c8e529d7291e60a95e580967ed79ce2c9ccf0

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/appstream-glib.html

...
As:ERROR:../libappstream-glib/as-self-test.c:2009:as_test_app_validate_check: 
assertion failed (message == "not-found"): (" timestamp is in the 
future" == "not-found")
...
Ok:0
Expected Fail: 0
Fail:  1
Unexpected Pass:   0
Skipped:   0
Timeout:   0
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=16 
ninja test returned exit code 1
make[1]: *** [debian/rules:38: override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: appstream-glib
Source-Version: 0.7.17-1
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated appstream-glib 
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: Thu, 16 Apr 2020 11:32:17 +0200
Source: appstream-glib
Architecture: source
Version: 0.7.17-1
Distribution: unstable
Urgency: medium
Maintainer: PkgUtopia Team 
Changed-By: Laurent Bigonville 
Closes: 949169
Changes:
 appstream-glib (0.7.17-1) unstable; urgency=medium
 .
   * Team upload.
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Repository, Repository-
 Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Laurent Bigonville ]
   * New upstream version 0.7.17 (Closes: #949169)
   * debian/control: Bump libglib2.0-dev (build-)dependency to 2.58.0
   * d/p/0001-Properly-initialize-unique_id_mutex.patch: Fix FTBFS on non-linux
   * debian/control: Add severals -doc packages to the BDI to fix links between
 doc files
   * debian/libappstream-glib8.symbols: Remove as_app_parse_desktop_kf, never
 meant to be public
   * debian/libappstream-glib8.symbols: Add Build-Depends-Package field
   * debian/control: Make the -dev and gir pkg ma:same and -doc ma:foreign
   * debian/control: Bump Standards-Version to 4.5.0 (no further changes)
Checksums-Sha1:
 7cb4da7dd3f65b9f1952dd743bedb9a5bb32a265 2391 appstream-glib_0.7.17-1.dsc
 810eac556229883f7826c2300817b8a23b4a2b54 2245372 
appstream-glib_0.7.17.orig.tar.xz
 17cf44f391b1de7b8a4580c3f6888c66a7c10ada 10728 
appstream-glib_0.7.17-1.debian.tar.xz
 858deca5afe6b2001b503c4ce466ece43eff57bb 14380 
appstream-glib_0.7.17-1_source.buildinfo
Checksums-Sha256:
 099a48da119fdd55030959e5fef60cb7ab231cc5deb7050ffddcb62a31f6f56c 2391 
appstream-glib_0.7.17-1.dsc
 7ca7e91d4accefa1c0d2c6e310cb3fe2686c017810e23b3f82d9f5724345e549 2245372 
appstream-glib_0.7.17.orig.tar.xz
 aee018fc5561b4a281c69307e058a4f7d25684a6912ed8baf3442e419c3d022c 10728 
appstream-glib_0.7.17-1.debian.tar.xz
 04b0f1cb29d1868240bd55ed2f6da8ceb13626795c9bc778a76111c358920ef7 14380 
appstream-glib_0.7.17-1_source.buildinfo
Files:
 146af641745f1897bafaf3f79b5e4896 2391 admin optional 
appstream-glib_0.7.17-1.dsc
 67d441fb0fb3e14551b47db656565fc4 2245372 admin optional 
appstream-glib_0.7.17.orig.tar.xz
 4eca9f3a863a0d8248afbec2dae960e9 10728 admin optional 
appstream-glib_0.7.17-1.debian.tar.xz
 95d237375b0c0bf7c546d384db27e9f3 14380 admin optional 
appstream-glib_0.7.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl6YJ1MRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9V3xAf+PJOwuHXqMF9O4c9M2UDGJBfO5EXwIm9K
Fbk+r8ufaxWUWwalzBkComfVmECA62FjI3NZARtVaToJh6dVIFZ0

Bug#956372: marked as done (cbp2make: Binary missing after rebuild)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 10:04:20 +
with message-id 
and subject line Bug#956372: fixed in cbp2make 147+dfsg-3
has caused the Debian Bug report #956372,
regarding cbp2make: Binary missing after rebuild
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.)


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

Package: cbp2make
Version: 147+dfsg-2
Severity: normal

Dear Maintainer,

This issue was originally reported in Ubuntu as
https://bugs.launchpad.net/ubuntu/+source/cbp2make/+bug/1871579.
Since the only difference between the Debian and Ubuntu verison was
a rebuild, that seemed strange.

After confirming the binary was still missing after a rebuild in the
Ubuntu development version, I tried the same on Sid.

The current version of the Debian package contains the following:
$ dpkg -L cbp2make
/.
/usr
/usr/bin
/usr/bin/cbp2make
/usr/share
/usr/share/doc
/usr/share/doc/cbp2make
/usr/share/doc/cbp2make/README.Debian
/usr/share/doc/cbp2make/changelog.Debian.gz
/usr/share/doc/cbp2make/changelog.gz
/usr/share/doc/cbp2make/copyright
/usr/share/doc/cbp2make/usage.txt
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/cbp2make.1.gz

If I do a local rebuild without any changes, I end up with:
$ dpkg -L cbp2make
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/cbp2make
/usr/share/doc/cbp2make/README.Debian
/usr/share/doc/cbp2make/changelog.Debian.gz
/usr/share/doc/cbp2make/changelog.gz
/usr/share/doc/cbp2make/copyright
/usr/share/doc/cbp2make/usage.txt
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/cbp2make.1.gz

I am not sure why, but when rebuilding this package the resulting
binary package is missing the actual binary.

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

Kernel: Linux 5.5.0-1-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cbp2make depends on:
ii  libc62.30-4
ii  libgcc-s1 [libgcc1]  10-20200402-1
ii  libgcc1  1:10-20200402-1
ii  libstdc++6   10-20200402-1
ii  libtinyxml2.6.2v52.6.2-4

cbp2make recommends no packages.

cbp2make suggests no packages.

-- no debconf information


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: cbp2make
Source-Version: 147+dfsg-3
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated cbp2make package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 09:35:31 +
Source: cbp2make
Architecture: source
Version: 147+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Graham Inggs 
Closes: 956372
Changes:
 cbp2make (147+dfsg-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jelmer Vernooĳ ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
 .
   [ Graham Inggs ]
   * Rename build-arch to override_dh_auto_build-arch,
 thanks Niels Thykier (Closes: #956372)
   * Switch to debhelper 12
   * Set Rules-Requires-Root: no
   * Set Vcs-Browser to canonical URI
   * Bump Standards-Version to 4.5.0, no changes
Checksums-Sha1:
 fbba88eb83ea799097cb7e0b2505b3fc1d8ec475 1966 cbp2make_147+dfsg-3.dsc
 cebf895925f15c2cd3850578ed38473c865c2015 6668 cbp2make_147+dfsg-3.debian.tar.xz
Checksums-Sha256:
 87e2bf0ad14a0ec7d5b2ac86aaa0d7efae51a7bef531fdee441307d8bc3d75f6 1966 
cbp2make_147+dfsg-3.dsc
 bef609b77c5f01bfc34417607f27985966e62468a122a1aaf1a71eea6e348a25 6668 
cbp2make_147+dfsg-3.debian.tar.xz
Files:
 38a2924cda27b24b0722870e050c30b5 1966 devel optional cbp2make_147+dfsg-3.dsc
 dac33d7f7acd2a8665cc6bd7fc5b05ac 6668 devel optional 
cbp2make_

Bug#955103: marked as done (nitime: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 10:04:47 +
with message-id 
and subject line Bug#955103: fixed in nitime 0.8.1-3
has caused the Debian Bug report #955103,
regarding nitime: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no 
attribute 'info'
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.)


-- 
955103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitime
Version: 0.8.1-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

nitime fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> ../tools/make_examples.py --no-exec
> python3 ../tools/build_modref_templates.py
> WARNING: Empty - nitime
> WARNING: Empty - nitime.algorithms
> WARNING: Empty - nitime.analysis
> WARNING: Empty - nitime.fmri
> WARNING: Empty - nitime.version
> 26 files written
> Build API docs finished.
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v2.4.3
> /<>/doc/conf.py:34: MatplotlibDeprecationWarning: 
> The mpl_toolkits.axes_grid module was deprecated in Matplotlib 2.1 and will 
> be removed two minor releases later. Use mpl_toolkits.axes_grid1 and 
> mpl_toolkits.axisartist, which provide the same functionality instead.
>   __import__(package, fromlist=parts)
> WARNING: while setting up extension ipython_console_highlighting: extension 
> 'ipython_console_highlighting' has no setup() function; is it really a Sphinx 
> extension module?
> /usr/lib/python3/dist-packages/sphinx/util/docutils.py:285: 
> RemovedInSphinx30Warning: function based directive support is now deprecated. 
> Use class based directive instead.
>   warnings.warn('function based directive support is now deprecated. '
> WARNING: while setting up extension only_directives: node class 'html_only' 
> is already registered, its visitors will be overridden
> WARNING: while setting up extension only_directives: node class 'html_only' 
> is already registered, its visitors will be overridden
> WARNING: while setting up extension only_directives: node class 'latex_only' 
> is already registered, its visitors will be overridden
> WARNING: while setting up extension only_directives: node class 'latex_only' 
> is already registered, its visitors will be overridden
> 
> Exception occurred:
>   File "/<>/doc/sphinxext/github.py", line 149, in setup
> app.info('Initializing GitHub plugin')
> AttributeError: 'Sphinx' object has no attribute 'info'
> The full traceback has been saved in /tmp/sphinx-err-6g3piye3.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!
> make[2]: *** [Makefile:35: htmlonly] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/26/nitime_0.8.1-2_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: 
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

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: nitime
Source-Version: 0.8.1-3
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
nitime, 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.
Andreas Tille  (supplier of updated n

Bug#956864: marked as done (python3-adios: alternative path adios_mpi.cpython-37m-x86_64-linux-gnu.so doesn't exist)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 09:03:36 +
with message-id 
and subject line Bug#956864: fixed in adios 1.13.1-22
has caused the Debian Bug report #956864,
regarding python3-adios: alternative path 
adios_mpi.cpython-37m-x86_64-linux-gnu.so doesn't exist
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.)


-- 
956864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-adios
Version: 1.13.1-21+b2
Severity: serious
Justification: prevents package configuration

binNMU 1.13.1-21+b2 removed python3.7 builds, and seems to have broken
python3-adios:

Errors were encountered while processing:
 python3-adios
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 Setting up python3-adios (1.13.1-21+b2) ...
 update-alternatives: error: alternative path
/usr/lib/python3/dist-packages/adios_openmpi/adios_mpi.cpython-37m-x86_64-linux-gnu.so
doesn't exist
dpkg: error processing package python3-adios (--configure):
 installed python3-adios package post-installation script subprocess
returned error exit status 2

It's making the package uninstallable.


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

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

Versions of packages python3-adios depends on:
ii  libblosc1  1.17.1+ds1-1
ii  libbz2-1.0 1.0.8-2
ii  libc6  2.30-4
ii  libgcc-s1 [libgcc-s1]  10-20200402-1
ii  libhdf5-openmpi-103-1  1.10.6+repack-1
ii  liblz4-1   1.9.2-2
ii  libmpich12 3.4~a2+really3.3.2-1
ii  libnetcdf-mpi-15   1:4.7.3-2+b1
ii  libopenmpi34.0.3-5
ii  libstdc++6 10-20200402-1
ii  libsz2 1.0.4-1
ii  python33.8.2-3
ii  zlib1g 1:1.2.11.dfsg-2

python3-adios recommends no packages.

python3-adios suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-22
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated adios 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, 11 Apr 2020 19:43:38 +0100
Source: adios
Architecture: source
Version: 1.13.1-22
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 956864
Changes:
 adios (1.13.1-22) unstable; urgency=medium
 .
   * Change update-alternatives code in postinst to dynamically detect
 python3 version. Closes: #956864
Checksums-Sha1:
 b9501b133975e39880e280c34becbe20b8f8f248 3049 adios_1.13.1-22.dsc
 e7d130bff0f85c9388aabb0f9bdd83668fdae669 23268 adios_1.13.1-22.debian.tar.xz
Checksums-Sha256:
 2918723948c87be7b006e4162c36fe1daad692419bccbf8e5b6f685455b29e18 3049 
adios_1.13.1-22.dsc
 01993ca4e01c8e5ec2f9c3c8c1844b866700bd7949c07556a53e71f13eb76418 23268 
adios_1.13.1-22.debian.tar.xz
Files:
 883e1042d83697a2b02e7cd98a0d0909 3049 science optional adios_1.13.1-22.dsc
 60fde0f1f4f7d947a01b84bb576c83d9 23268 science optional 
adios_1.13.1-22.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl6YGsAACgkQy+a7Tl2a
06X6uBAAn8oWieJunxYUySKQ9y953PmGE6fjymSm3hS8CfF/qHIHEcW9L1MEzJlE
CnmK0Wqs+Wc/5s0zSJADo9yJ+bCr1b+OMVkaTVR2FjQ8Esb/zuTKucFc1s4l4CC6
kwifstiFpP+GGNLAGgyfoa5D/CaS3My0jcsjYBdgE3ZB4aJjHFFEvaa0O8WSYvEg
MQ1K9ki7rZEkr36/wygDAccGj3tO/GnHeKBDsAIzfxtKfyUvyNH1bZOudGmwtR6b
4zpDesd7oUJuVGGWhmEQiDt3+JY3ZDPiwBpogUOF2oWMnAF3do5UbU1cxPpmYZLv
bGdH55P4U+5ytKICrTecenz11A4UKju93/Ul5zSMqE3aCrqDKei52J+xTtizpOi8
j/D1eAI

Bug#954919: marked as done (bind9-libs: libisc not properly linked?)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:48:58 +
with message-id 
and subject line Bug#954919: fixed in bind9 1:9.16.2-1
has caused the Debian Bug report #954919,
regarding bind9-libs: libisc not properly linked?
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.)


-- 
954919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9-libs
Version: 1:9.16.1-2
Severity: important

Hi,

I'm trying to build bind-dyndb-ldap against the new bind9 (with bind9-dev 
added), but
it's failing because (at least) libisc seems to be missing something?

/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_new_int64'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_new_string'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `deflate'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `deflateInit_'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `xmlTextWriterWriteString'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `deflateEnd'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_object_add'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `xmlTextWriterStartElement'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_new_int'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_array_add'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_new_array'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `xmlTextWriterWriteFormatString'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `xmlTextWriterEndElement'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_new_object'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `xmlTextWriterWriteElement'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libisc.so: undefined 
reference to `json_object_put'
collect2: error: ld returned 1 exit status

ldd returns:

linux-vdso.so.1 (0x7ffd1e8f2000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7ff9b2824000)
libuv.so.1 => /usr/lib/x86_64-linux-gnu/libuv.so.1 (0x7ff9b27f3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff9b27d2000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff9b27cd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff9b260a000)
/lib64/ld-linux-x86-64.so.2 (0x7ff9b2b8f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ff9b25ff000

when the old version from 9.11 returns:

linux-vdso.so.1 (0x7fff0f981000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7f7d18d09000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f7d18b05000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f7d188e8000)
libjson-c.so.3 => /lib/x86_64-linux-gnu/libjson-c.so.3 
(0x7f7d186dd000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f7d184be000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x7f7d180fd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7d17d0c000)
/lib64/ld-linux-x86-64.so.2 (0x7f7d19451000)
libicuuc.so.60 => /usr/lib/x86_64-linux-gnu/libicuuc.so.60 
(0x7f7d17954000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f7d1772e000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7d1739)
libicudata.so.60 => /usr/lib/x86_64-linux-gnu/libicudata.so.60 
(0x7f7d157e7000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f7d1545e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f7d15246000)
--- End Message ---

Bug#952946: marked as done (bind9: Replace PKCS11 headers provided by OASIS)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:48:58 +
with message-id 
and subject line Bug#952946: fixed in bind9 1:9.16.2-1
has caused the Debian Bug report #952946,
regarding bind9: Replace PKCS11 headers provided by OASIS
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.)


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

Since headers provided by OASIS PKCS11 are not-exactly free license
(they do not allow modification),

You can use an alternative header like p11-kit which is licensed under
a more liberal license.

bind9/lib/isc/include/pkcs11

Regards,
Alvin Chen
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.16.2-1
Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Ondřej Surý  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 10:07:07 +0200
Source: bind9
Architecture: source
Version: 1:9.16.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 947978 952946 954919
Changes:
 bind9 (1:9.16.2-1) unstable; urgency=medium
 .
   * Update d/copyright (Closes: #947978)
   * New upstream version 9.16.2 (Closes: #952946, #954919)
Checksums-Sha1:
 0fd030fc8fd0cc9281b7292fc1e936f25034875a 2794 bind9_9.16.2-1.dsc
 985a6ac0ef8242bfb5e3d11794b612d910f860ac 4559216 bind9_9.16.2.orig.tar.xz
 7f98a58fe226fa35951abf3a354d9c09a7a3dac3 61756 bind9_9.16.2-1.debian.tar.xz
 568a6e4230d208dd6d7bec191d3529ab8b34cb4a 11456 bind9_9.16.2-1_amd64.buildinfo
Checksums-Sha256:
 44ce4c83488c1a502b2d362836c219003e82f3163e7559589ee650915bc3b3c6 2794 
bind9_9.16.2-1.dsc
 d9e5b77cfca5ccad97f19cddc87128758ec15c16e6585000c6b2f84fc225993f 4559216 
bind9_9.16.2.orig.tar.xz
 d8d530e15602b1eb8610e439bd13ae69aaadf6bc12a82c54b2e4219e9e062b40 61756 
bind9_9.16.2-1.debian.tar.xz
 f5c2c5ef51fd8a2a55b68c93b9be6e7ff2b14f70547f049804f627351c8497e2 11456 
bind9_9.16.2-1_amd64.buildinfo
Files:
 9c9f9e9d0500d3252a5a2d2f4f18eba2 2794 net optional bind9_9.16.2-1.dsc
 2f65f53ad0eab3701138332282b9b526 4559216 net optional bind9_9.16.2.orig.tar.xz
 707eb6a3863bcdca90763c05bc6a6101 61756 net optional 
bind9_9.16.2-1.debian.tar.xz
 e55c9af01ba75502c218a764d7153e58 11456 net optional 
bind9_9.16.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl6YFp9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcITxA//eLw9+kx+Pac6O9FS80Ix6+ASJFVLhFwcnfSNqc5sQ7J7L3eyGycaDvD/
EQ2B6aAR56I3sllbWn2GXzrc/eCdxzwB0bck8PZxcvaHEgyZpgop+FcXM1tQR6bK
JAfxJyUv4FnLimbaIfSoNOfXfM5XfkLLrFWfp24KbzfobMjyzTFr0Xey9Mx7IELm
DCT2lS/jRY1hzMcbHBqye1QuT/V6Yl8tEXNkjylc56FJrXXB9+phCNvkVSxMPdy6
+UynAdJ+0y9uL8dyC8ywT+maux40tH5AUq7hfQJv/awTMUZLhW+Pv2Hk4m7ONKEz
jk4BCHE7BFQ0Sdc1NGNbk8ZAunmCFklzz6hXi1+mQTKLJCvVx+BcdmsPO0afntPG
JKTFfOVsoXnbxYj12Ic/Y4XsX6GOu5tfw+/EOXK2nYoRcSMsqrtUlY8gZz5o17kG
YzuCFpmDQept1AJJLrb+6aYfvV+eFb4PRu0uq1pCxK0E9J2zmHwF7vk/Nu5Wq4/b
d6KG3WWZkXo0ZoO5A/QL3lGgNkSfEMPrwjPjTpmXUOenndb93VKuhu/I/kNOyQhM
sS5/D56BZZyVdW9aCfIlWhZ46wdsjupDJdhe1Vgk6naQGbLxX4NXLq4x36xAVawj
oBCinQI29sIa2nSGEdL7mt7MkaKBUSTF6IzBkPtO5fZjfUBCe/E=
=Dqx9
-END PGP SIGNATURE End Message ---

Bug#947978: marked as done (license problem)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:48:57 +
with message-id 
and subject line Bug#947978: fixed in bind9 1:9.16.2-1
has caused the Debian Bug report #947978,
regarding license problem
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.)


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

Package: bind9
Version: 1:9.15.5-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
thanks

Hi,

our hardworking trainees added a note to your package:

 d/copyright mentions that this source is:
  License: MPL-2.0 and ISC and BSD-2-clause and BSD-3-clause
 However, LICENSE only says MPL-2.0. I see no indication that the majority
 of source files are quadruple-licensed. Rather, the majority seem to be
 only MPL-2.0.

 The directories lim/isccc/ and m4/ have a number of copyright holders not
 that are not mentioned in d/copyright.

 lib/irs/getnameinfo.c also has a copyright holder (WIDE Project) that is
 not mentioned in d/copyright.


Please take care of these issues.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.16.2-1
Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 

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

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

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 10:07:07 +0200
Source: bind9
Architecture: source
Version: 1:9.16.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 947978 952946 954919
Changes:
 bind9 (1:9.16.2-1) unstable; urgency=medium
 .
   * Update d/copyright (Closes: #947978)
   * New upstream version 9.16.2 (Closes: #952946, #954919)
Checksums-Sha1:
 0fd030fc8fd0cc9281b7292fc1e936f25034875a 2794 bind9_9.16.2-1.dsc
 985a6ac0ef8242bfb5e3d11794b612d910f860ac 4559216 bind9_9.16.2.orig.tar.xz
 7f98a58fe226fa35951abf3a354d9c09a7a3dac3 61756 bind9_9.16.2-1.debian.tar.xz
 568a6e4230d208dd6d7bec191d3529ab8b34cb4a 11456 bind9_9.16.2-1_amd64.buildinfo
Checksums-Sha256:
 44ce4c83488c1a502b2d362836c219003e82f3163e7559589ee650915bc3b3c6 2794 
bind9_9.16.2-1.dsc
 d9e5b77cfca5ccad97f19cddc87128758ec15c16e6585000c6b2f84fc225993f 4559216 
bind9_9.16.2.orig.tar.xz
 d8d530e15602b1eb8610e439bd13ae69aaadf6bc12a82c54b2e4219e9e062b40 61756 
bind9_9.16.2-1.debian.tar.xz
 f5c2c5ef51fd8a2a55b68c93b9be6e7ff2b14f70547f049804f627351c8497e2 11456 
bind9_9.16.2-1_amd64.buildinfo
Files:
 9c9f9e9d0500d3252a5a2d2f4f18eba2 2794 net optional bind9_9.16.2-1.dsc
 2f65f53ad0eab3701138332282b9b526 4559216 net optional bind9_9.16.2.orig.tar.xz
 707eb6a3863bcdca90763c05bc6a6101 61756 net optional 
bind9_9.16.2-1.debian.tar.xz
 e55c9af01ba75502c218a764d7153e58 11456 net optional 
bind9_9.16.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl6YFp9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcITxA//eLw9+kx+Pac6O9FS80Ix6+ASJFVLhFwcnfSNqc5sQ7J7L3eyGycaDvD/
EQ2B6aAR56I3sllbWn2GXzrc/eCdxzwB0bck8PZxcvaHEgyZpgop+FcXM1tQR6bK
JAfxJyUv4FnLimbaIfSoNOfXfM5XfkLLrFWfp24KbzfobMjyzTFr0Xey9Mx7IELm
DCT2lS/jRY1hzMcbHBqye1QuT/V6Yl8tEXNkjylc56FJrXXB9+phCNvkVSxMPdy6
+UynAdJ+0y9uL8dyC8ywT+maux40tH5AUq7hfQJv/awTMUZLhW+Pv2Hk4m7ONKEz
jk4BCHE7BFQ0Sdc1NGNbk8ZAunmCFklzz6hXi1+mQTKLJCvVx+BcdmsPO0afntPG
JKTFfOVsoXnbxYj12Ic/Y4XsX6GOu5tfw+/EOXK2nYoRcSMsqrtUlY8gZz5o17kG
YzuCFpmDQept1AJJLrb+6aYfvV+eFb4PRu0uq1pCxK0E9J2zmHwF7vk/Nu5Wq4/b
d6KG3WWZkXo0ZoO5A/QL3lGgNkSfEMPrwjPjTpmXUOenndb93VKuhu/I/kNOyQhM
sS5/D56BZZyVdW9aCfIlWhZ46wdsjupDJdhe1Vgk6naQGbLxX4NXLq4x36xAVawj
oBCinQI29sIa2nSGEdL7mt7MkaKBUSTF6IzBkPtO5fZjfUBCe/E=
=Dqx9
-END PGP SIGNATURE End Message ---

Bug#956177: marked as done (fail2ban: daemon startup should not access /root/.local)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:35:26 +
with message-id 
and subject line Bug#956177: fixed in fail2ban 0.11.1-2
has caused the Debian Bug report #956177,
regarding fail2ban: daemon startup should not access /root/.local
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.)


-- 
956177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 0.11.1-1
Severity: normal

type=AVC msg=audit(1586313861.749:37): avc:  denied  { search } for  pid=704 
comm="fail2ban-server" name=".local" dev="sdb2" ino=31516 
scontext=system_u:system_r:fail2ban_t:s0 
tcontext=unconfined_u:object_r:xdg_data_t:s0 tclass=dir permissive=0

Above is a SE Linux audit message generated by fail2ban starting on system
boot.  It is trying to access /root/.local which is inappropriate for a daemon.
No system configuration should be under /root/ and any daemon which accesses
that could give unexpected results.

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages fail2ban depends on:
ii  lsb-base  11.1.0
ii  python3   3.8.2-2

Versions of packages fail2ban recommends:
ii  iptables   1.8.4-3
pn  python3-pyinotify  
pn  python3-systemd
ii  whois  5.5.6

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20180807cvs-1+b1
ii  monit1:5.26.0-4
ii  rsyslog [system-log-daemon]  8.2002.0-2
pn  sqlite3  

-- Configuration Files:
/etc/fail2ban/paths-debian.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.11.1-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated fail2ban package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 11:44:23 +0200
Source: fail2ban
Architecture: source
Version: 0.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sylvestre Ledru 
Closes: 956177 956681
Changes:
 fail2ban (0.11.1-2) unstable; urgency=medium
 .
   * Do not rotate log if empty. Thanks to Ron Varburg for the patch
 (Closes: #956681)
   * Add Environment="PYTHONNOUSERSITE=yes" to the service file to avoid
 fail2ban to read /root/.local/. Thanks to Russell Coker for the
 investigation (Closes: #956177)
Checksums-Sha1:
 8c98353cbe62ac09187b4ea6cd4021c21fed7cbe 2095 fail2ban_0.11.1-2.dsc
 95a994f615bc2f06ccb9b02b1ae3b37409558b1e 28604 fail2ban_0.11.1-2.debian.tar.xz
 6e2b57da9d32fdffadabe0e6ab25ab8a83d6ec2e 6116 fail2ban_0.11.1-2_amd64.buildinfo
Checksums-Sha256:
 4cae056a51e9e7b05b98e10d3d600479ccd83e59ec6cc292e6c3b3af5ee03650 2095 
fail2ban_0.11.1-2.dsc
 1d28a519cfec2cf4b3afb83cb8c3e87e6037a4b31e31b1b8d28d0a7f33c20e95 28604 
fail2ban_0.11.1-2.debian.tar.xz
 934abd43d74880c55f6d7c35c1985b229fc3061d36c92de74694a784a5c401c1 6116 
fail2ban_0.11.1-2_amd64.buildinfo
Files:
 da1d8cf43798bc68499542cd1e53828e 2095 net optional fail2ban_0.11.1-2.dsc
 e8e60c2fd72452c82ded95f62abe06e7 28604 net optional 
fail2ban_0.11.1-2.debian.tar.xz
 c3b1168438db0dd1cfe6b9f229585e05 6116 net optional 
fail2ban_0.11.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl6YEwkACgkQfmUo2nUv
G+EDsxAAk5O47Sip42r7Tg151Ct13Hvi24ZcrYeRw9K2yezCF1wRJvM9reWUPKPs
3iH6uXjC5dc99HAWbulzJELAYGqtTQ3PQDuaPjISF3QPlQcpD7FEGIRmWEicgrMK
7m3l9OkBx8nv/liemCPv1yUWqYrRSwhiZtFGVmyEFuMDKQKp+tChPbKv9Uogq9ys
VeeAXB3CtYB1ad5r4UUnjysOGGbMIFyM4KcHrPFGtO0KgR2

Bug#956681: marked as done (/etc/logrotate.d/fail2ban cause logrotate failures when fail2ban isn't running.)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:35:26 +
with message-id 
and subject line Bug#956681: fixed in fail2ban 0.11.1-2
has caused the Debian Bug report #956681,
regarding /etc/logrotate.d/fail2ban cause logrotate failures when fail2ban 
isn't running.
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.)


-- 
956681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
Tags: patch

The following patch:
1. Prevents logrotate failures when fail2ban doesn't run for any reason.
When fail2ban  isn't running, fail2ban-client flushlogs exits with an error
code. I think announcing fail2ban isn't running should not be made by
making logrotate to fail.
2. Doesn't rotate empty log files.

--- a/etc/logrotate.d/fail2ban   2018-04-04 04:47:53.0 +
+++ b/etc/logrotate.d/fail2ban   2020-04-13 09:58:32.995426248 +
@@ -1,5 +1,6 @@
 /var/log/fail2ban.log {

+notifempty
 weekly
 rotate 4
 compress
@@ -7,7 +8,7 @@
 delaycompress
 missingok
 postrotate
-   fail2ban-client flushlogs 1>/dev/null
+   fail2ban-client flushlogs 1>/dev/null  ||  true
 endscript
 
 # If fail2ban runs as non-root it still needs to have write access
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 0.11.1-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated fail2ban package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 11:44:23 +0200
Source: fail2ban
Architecture: source
Version: 0.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sylvestre Ledru 
Closes: 956177 956681
Changes:
 fail2ban (0.11.1-2) unstable; urgency=medium
 .
   * Do not rotate log if empty. Thanks to Ron Varburg for the patch
 (Closes: #956681)
   * Add Environment="PYTHONNOUSERSITE=yes" to the service file to avoid
 fail2ban to read /root/.local/. Thanks to Russell Coker for the
 investigation (Closes: #956177)
Checksums-Sha1:
 8c98353cbe62ac09187b4ea6cd4021c21fed7cbe 2095 fail2ban_0.11.1-2.dsc
 95a994f615bc2f06ccb9b02b1ae3b37409558b1e 28604 fail2ban_0.11.1-2.debian.tar.xz
 6e2b57da9d32fdffadabe0e6ab25ab8a83d6ec2e 6116 fail2ban_0.11.1-2_amd64.buildinfo
Checksums-Sha256:
 4cae056a51e9e7b05b98e10d3d600479ccd83e59ec6cc292e6c3b3af5ee03650 2095 
fail2ban_0.11.1-2.dsc
 1d28a519cfec2cf4b3afb83cb8c3e87e6037a4b31e31b1b8d28d0a7f33c20e95 28604 
fail2ban_0.11.1-2.debian.tar.xz
 934abd43d74880c55f6d7c35c1985b229fc3061d36c92de74694a784a5c401c1 6116 
fail2ban_0.11.1-2_amd64.buildinfo
Files:
 da1d8cf43798bc68499542cd1e53828e 2095 net optional fail2ban_0.11.1-2.dsc
 e8e60c2fd72452c82ded95f62abe06e7 28604 net optional 
fail2ban_0.11.1-2.debian.tar.xz
 c3b1168438db0dd1cfe6b9f229585e05 6116 net optional 
fail2ban_0.11.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl6YEwkACgkQfmUo2nUv
G+EDsxAAk5O47Sip42r7Tg151Ct13Hvi24ZcrYeRw9K2yezCF1wRJvM9reWUPKPs
3iH6uXjC5dc99HAWbulzJELAYGqtTQ3PQDuaPjISF3QPlQcpD7FEGIRmWEicgrMK
7m3l9OkBx8nv/liemCPv1yUWqYrRSwhiZtFGVmyEFuMDKQKp+tChPbKv9Uogq9ys
VeeAXB3CtYB1ad5r4UUnjysOGGbMIFyM4KcHrPFGtO0KgR2a+5JnT6jFbMuIrEtj
9NE8TVYhcz+sSiDSQ9ukvpKPQzp2scWSYr8/t47D1DcRwjz/+ab4nLmgEDjL//Tq
CGhknXTPS2Xrw2SC3gh+sHOsQB9LthoOdYQ0yxATbtEZtsqSURwn2m5t57jtgj0Y
aIEk0IVrHPHSx0eWs1iGgYeOXhpuvVOq+0d6BiYmo6+ndOogBBqGfiRdAjnmkMXo
GWJlr/36ZGpGSfKRVifPnbGQS7ktI2AB5garw+cY8C3Q2vV5wpm1YQlbVu76mxe6
Dhtolp05dlJS4yNoHDaXeITGMXJiqpn6B7i9BAq7N0uJnSsSJiMh3lHAdaViFlt7
h03E7HK7wDj79yNmKsJ9N7CtX3HHAZ52lKbTBiRErAGNU6X+IZGFldzjelQ04QZR
4tSheQHjXNeGbX8AQwuwY949cU3Tb4AQbIF4uKMmCgJ8DdTjbIo=
=aSw7
-END PGP SIGNATURE End Message ---

Bug#955106: marked as done (python-can: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'warn')

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:37:45 +
with message-id 
and subject line Bug#955106: fixed in sphinxcontrib-programoutput 0.16-1
has caused the Debian Bug report #955106,
regarding python-can: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object 
has no attribute 'warn'
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.)


-- 
955106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-can
Version: 3.3.2.final~github-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-can fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/interface.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/listener.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/broadcastmanager.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/message.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/ctypesutil.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/logger.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/viewer.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/util.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/player.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/thread_safe_bus.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/CAN.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/bus.py -> /<>/.pybuild/cpython3_3.7_can/build/can
> copying can/notifier.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can
> creating /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/nican.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/canalystii.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/iscan.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/virtual.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> copying can/interfaces/slcan.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces
> creating /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/sqlite.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/csv.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/blf.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/asc.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/canutils.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/generic.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/logger.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/player.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> copying can/io/printer.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/io
> creating 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/vector
> copying can/interfaces/vector/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/vector
> copying can/interfaces/vector/canlib.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/vector
> copying can/interfaces/vector/vxlapi.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/vector
> copying can/interfaces/vector/exceptions.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/vector
> creating /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> copying can/interfaces/ixxat/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> copying can/interfaces/ixxat/canlib.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> copying can/interfaces/ixxat/constants.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> copying can/interfaces/ixxat/exceptions.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> copying can/interfaces/ixxat/structures.py -> 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/ixxat
> creating 
> /<>/.pybuild/cpython3_3.7_can/build/can/interfaces/socketcan
> copying can/interfaces/socketcan/__init__.py -> 
> /<>/.pybuild/cpytho

Bug#953899: marked as done (caja-eiciel: Build-Depends on unused libattr1-dev)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:35:11 +
with message-id 
and subject line Bug#953899: fixed in caja-eiciel 1.20.1-2
has caused the Debian Bug report #953899,
regarding caja-eiciel: Build-Depends on unused libattr1-dev
to be marked as done.

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

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


-- 
953899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caja-eiciel
Source-Version: 1.20.1-1
Severity: minor

Hi!

This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: caja-eiciel
Source-Version: 1.20.1-2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated caja-eiciel 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: Thu, 16 Apr 2020 09:45:00 +0200
Source: caja-eiciel
Architecture: source
Version: 1.20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 953899
Changes:
 caja-eiciel (1.20.1-2) unstable; urgency=medium
 .
   * debian/{compat,control}:
 + Use debhelper-compat notation. Bump to DH compat level version 12.
   * debian/control:
 + Add Rules-Requires-Root: field and set it to no.
 + Bump Standards-Version: to 4.5.0. No changes needed.
 + Drop from B-D: libattr. (Closes: #953899).
Checksums-Sha1:
 22465022ba61c886158959268a370463ff4352ce 2160 caja-eiciel_1.20.1-2.dsc
 46553bbb3093b71c97388e1ebbf67182a06423d2 4856 
caja-eiciel_1.20.1-2.debian.tar.xz
 156abfe3d57b86a737dcfc1d8c1216706d710064 14993 
caja-eiciel_1.20.1-2_source.buildinfo
Checksums-Sha256:
 07d3cd22a69148ea914d2c5e1aade9b26d2c2ab77dbc823e2cd9c675c496a432 2160 
caja-eiciel_1.20.1-2.dsc
 0117911e91574bbfea95197968d18e31041eb5446acaafafe2f90ffbbc3c2543 4856 
caja-eiciel_1.20.1-2.debian.tar.xz
 34ab773bdad5d9fa53a71ad107cb60faff37753b1558b50b4a7ec59bf0a15f5e 14993 
caja-eiciel_1.20.1-2_source.buildinfo
Files:
 64815bc48383e40b426f491ec7e3afc4 2160 admin optional caja-eiciel_1.20.1-2.dsc
 27456910c6eb4391a2a4c9923f6afcf7 4856 admin optional 
caja-eiciel_1.20.1-2.debian.tar.xz
 b1291de629817d8d515319ea87b58a29 14993 admin optional 
caja-eiciel_1.20.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl6YDTUVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxEgYQAIowCRBConoLBovWA699JfqaDd3c
O+bA9stLOcJYha4dzp7q85N8/1neBztVfYyOo56qEsSEM/g/gE9yPl3s572FK0hv
lxhZTixlhzAN3g/5coOm1nCauImFu0D0wVsCZ+ORzQqkGHNrTCJJEqtby3RkyThr
E3zg3H5M10KqOmAlzNJvAu8r6uEy5TIsKI6F1QaGc9rf7+3E0e1he0OS9TRMuOkP
i5LTFh8GaOInhRv93r9weTUe65Ow9IskEfZG8tCEdGp/yVe2HjXghuFzd4j1AYAt
XLuvMCmzp1nnola8Yfk1rTX+R+cqjt+Iub+8g2L1yO29xjuAcsHG4nk45eIiUOrd
IP5XBh5JlPN2A7nKO26GZ/EApPh+8e9bkR1hAV0ckITLu1V0ua7/4TofXYKjv2KH
Ryh0r6mGUdg9Ea2h/xol7C9AhXUpGq0RjG/SR7VJGBkRd2qMmPa6LUmpsMzpQ6Da
tuP3Gp/0yFixgSjX/bdQO2hRi2t/IMhcLk4ZK7J+mwkiAnAhquiNuoNOzmozESP4
4z7t9sG61k91XX2rsA2kaZVE2B3/ep+/uAypKEw85od0QfCYC9LTxVHeCghwTEFX
PlXOZoN2hE5vmVBoCJ/TIM2AjLy2tSOwtLVZIvzhWQ5Q89JYJVPVzOxihSkOrcKS
7zEnB2Rq39n5kGk6
=3y5s
-END PGP SIGNATURE End Message ---

Bug#955077: marked as done (sphinxcontrib-programoutput: FTBFS with Sphinx 2.4: AssertionError: 'Unexpected return code 1 from command' not found in "node class 'toctree' is already registered, its vi

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:37:45 +
with message-id 
and subject line Bug#955077: fixed in sphinxcontrib-programoutput 0.16-1
has caused the Debian Bug report #955077,
regarding sphinxcontrib-programoutput: FTBFS with Sphinx 2.4: AssertionError: 
'Unexpected return code 1 from command' not found in "node class 'toctree' is 
already registered, its visitors will be overridden"
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.)


-- 
955077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-programoutput
Version: 0.11-5
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

sphinxcontrib-programoutput fails to build with Sphinx 2.4, currently available 
in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for i in 3.7 3.8 ; do \
>   PYTHONPATH=. PYTHON=python$i python$i setup.py test ; \
> done
> 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 src/sphinxcontrib_programoutput.egg-info
> writing src/sphinxcontrib_programoutput.egg-info/PKG-INFO
> writing dependency_links to 
> src/sphinxcontrib_programoutput.egg-info/dependency_links.txt
> writing namespace_packages to 
> src/sphinxcontrib_programoutput.egg-info/namespace_packages.txt
> writing requirements to src/sphinxcontrib_programoutput.egg-info/requires.txt
> writing top-level names to 
> src/sphinxcontrib_programoutput.egg-info/top_level.txt
> writing manifest file 'src/sphinxcontrib_programoutput.egg-info/SOURCES.txt'
> reading manifest file 'src/sphinxcontrib_programoutput.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/sphinxcontrib_programoutput.egg-info/SOURCES.txt'
> running build_ext
> test_cache_pickled (sphinxcontrib.programoutput.tests.test_cache.TestCache) 
> ... /usr/lib/python3/dist-packages/jinja2/sandbox.py:19: DeprecationWarning: 
> Using or importing the ABCs from 'collections' instead of from 
> 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop 
> working
>   from collections import Mapping
> ok
> test_hidden_standard_error 
> (sphinxcontrib.programoutput.tests.test_cache.TestCache) ... ok
> test_nonzero_return_code 
> (sphinxcontrib.programoutput.tests.test_cache.TestCache) ... ok
> test_nonzero_return_code_shell 
> (sphinxcontrib.programoutput.tests.test_cache.TestCache) ... ok
> test_working_directory 
> (sphinxcontrib.programoutput.tests.test_cache.TestCache) ... ok
> test_working_directory_shell 
> (sphinxcontrib.programoutput.tests.test_cache.TestCache) ... ok
> test_execute (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... 
> ok
> test_execute_with_hidden_standard_error 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_execute_with_shell 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_from_programoutput_node 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_from_programoutput_node_extraargs 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output (sphinxcontrib.programoutput.tests.test_command.TestCommand) 
> ... ok
> test_get_output_non_zero 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output_with_hidden_standard_error 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_get_output_with_working_directory 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_list 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_list_hashable 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_new_with_string_command 
> (sphinxcontrib.programoutput.tests.test_command.TestCommand) ... ok
> test_slice_empty (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_no_int (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_simple (sphinxcontrib.programoutput.tests.test_util.TestSlice) ... 
> ok
> test_slice_too_many (sphinxcontrib.programoutput.tests.test_util.TestSlice) 
> ... ok
> test_command (sphinxcontrib.programoutput.tests.test_directive.Test

Bug#937579: marked as done (python-apt: Python2 removal in sid/bullseye)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 08:37:15 +
with message-id 
and subject line Bug#937579: fixed in python-apt 2.1.0
has caused the Debian Bug report #937579,
regarding python-apt: 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.)


-- 
937579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-apt
Version: 1.8.4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-apt

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-apt
Source-Version: 2.1.0
Done: Julian Andres Klode 

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

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

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated python-apt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Apr 2020 09:46:49 +0200
Source: python-apt
Architecture: source
Version: 2.1.0
Distribution: unstable
Urgency: medium
Maintainer: APT Development Team 
Changed-By: Julian Andres Klode 
Closes: 937579
Changes:
 python-apt (2.1.0) unstable; urgency=medium
 .
   [ Gordon Ball ]
   * Use pyflakes3 instead of (python 2) pyflakes
 .
   [ Julian Andres Klode ]
   * Stop building for Python 2 (Closes: #937579)
   * Remove Python 2 autopkgtests
Checksums-Sha1:
 5e2e35cb13b99a3bc2cdf7d19d427fbfffb571b1 2330 python-apt_2.1.0.dsc
 8c923cbd3b78375f0229c12058ccc287794f3e44 346348 python-apt_2.1.0.tar.xz
 b8a7006ec6f7a190ef455ee42272bb26c47c56c5 9125 python-apt_2.1.0_source.buildinfo
Checksums-Sha256:
 5cbe73fb43aa811ded7718dd430cb782543bd4f6c3185050520be4819600ecea 2330 
python-apt_2.1.0.dsc
 b791e253f88787ee59b5e23d53e1218ae242f734ae110e37ebfc94704db45dba 346348 
python-apt_2.1.0.tar.xz
 023382e013c567e9c2f9ab043922749a6ed8020ca

Processed: closing 888169

2020-04-16 Thread Debian Bug Tracking System

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

> close 888169
Bug #888169 [bind9] seccomp support for bind9
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 767798

2020-04-16 Thread Debian Bug Tracking System

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

> close 767798
Bug #767798 [bind9] bind9: ignores OPTIONS from /etc/default/bind9 w/ systemd
Bug #787264 [bind9] systemd bind9.service doestn't use options in 
/etc/default/bind9
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#956689: marked as done (pluma: Please witch to enchant-2 instead of enchant(1))

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 07:50:54 +
with message-id 
and subject line Bug#956689: fixed in pluma 1.24.0-2
has caused the Debian Bug report #956689,
regarding pluma:  Please witch to enchant-2 instead of enchant(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.)


-- 
956689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pluma
Version: 1.24.0-1
Severity: important
Control: block 947979 by -1

Hello,

Could you please switch from enchant(1) to the enchant-2 library?

We are trying to get rid of enchant(1) for the bullseye release

Switching the libenchant-dev BD to libenchant-2-dev should be enough.

Kind regards,
Laurent Bigonville

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

Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Source: pluma
Source-Version: 1.24.0-2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated pluma 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: Thu, 16 Apr 2020 09:21:03 +0200
Source: pluma
Architecture: source
Version: 1.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 956689
Changes:
 pluma (1.24.0-2) unstable; urgency=medium
 .
   [ Martin Wimpress ]
   * debian/control:
 + Update versioned B-D on mate-common (>= 1.24.0-1~).
 .
   [ Mike Gabriel ]
   * debian/control:
 + Bump B-D from libenchant-dev to libenchant-2-dev. (Closes: #956689).
Checksums-Sha1:
 ff9ea6a4fc7675e5904a9c9dbd267499d55e5d14 2584 pluma_1.24.0-2.dsc
 8241d3aba5829b73272e35fa72a2ca805be4c165 13960 pluma_1.24.0-2.debian.tar.xz
 eca8bc3c9a81c7331b57b5674ee9f44dce689d91 17417 pluma_1.24.0-2_source.buildinfo
Checksums-Sha256:
 b0f3eb1fb885e8ee7796aa1e8d0fea244d56db5e50378e848a97f202ade070be 2584 
pluma_1.24.0-2.dsc
 0352e855a9dacf9f2c457934e36106bd913f0951d62d18ee6255a61037670a9f 13960 
pluma_1.24.0-2.debian.tar.xz
 7b033c53501f1f8cebf8ad81e50cd85d528b270918b959d36a84f8e9b5a29b29 17417 
pluma_1.24.0-2_source.buildinfo
Files:
 f8e489a08b5a5d886615b00bc74e15b6 2584 x11 optional pluma_1.24.0-2.dsc
 35d66f890f7d250791995b3cfb52054c 13960 x11 optional 
pluma_1.24.0-2.debian.tar.xz
 6e394991e465ace6bfd44b76ba244bd8 17417 x11 optional 
pluma_1.24.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl6YB4MVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxjvYP/0YliWZ+sOd9Dtx1DAXv7SEaILal
AUa+fQTLk4+waYbC7ArS6OMsH6k2GWTFWYTyyV1P7EmDVyRhBq4LUrPXCZADnx6h
OlzoQfF2+ePsU4/FTS2tXPSMRMDHZTH5n+4mKE5V1YqOwp4v3IwcN6V2dXeJmpU+
ccCXf8IN1GxY+rLAEwVKrcx6qcZ62yDSJIQoN5wjhI0w0czxWSVcflaT8lsPRFmi
NS26qCqLaq7eurzSlGeE9GDPyJZyX8DL7BJRUI68FJ11hhMjVyLCSB4epcOf4AET
eJlunlt/3IxC1I+36xceyQFAGSND3pOg3JD0JNaV8jAPPMDRbrbeBpNUX+bP2zOC
3o7Yfh+yRmEzWJ4wY8iQU32OxnwdNldhONoY0VvO1IRD2iaDUMZKBMIFIF0ALxbe
BD58yqhYnChePVGpB7rQvDeWAAtsQZlIbKn9IjZPKnCQFcKHPVTYj4yz3LS77WC1
EPRevD1uWvg1Reupa33ZWmuEnNKQ7VUio4iVx73CKewT7Cdfow2i3UjF3ElJbPV5
1C1IOycxCuw495MEATk+yhbZngH0pii7paOtB5Al87NRZr8udAn35y5JTQ3SvufA
nfaG6RZ8EdzXC3KLSS9NOCqCghNmmqJWaVyoWfIikn+S4DfLr3VvOeYpG6MzOLyF
XyXUdPLCLlrWIv4H
=XEoj
-END PGP SIGNATURE End Message ---

Processed: src:keepass2: fails to migrate to testing for too long

2020-04-16 Thread Debian Bug Tracking System

Processing control commands:

> close -1 2.44+dfsg-1
Bug #956873 [src:keepass2] src:keepass2: fails to migrate to testing for too 
long
Marked as fixed in versions keepass2/2.44+dfsg-1.
Bug #956873 [src:keepass2] src:keepass2: fails to migrate to testing for too 
long
Marked Bug as done

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

Processed: src:frr: fails to migrate to testing for too long: ftbfs on mipsel

2020-04-16 Thread Debian Bug Tracking System

Processing control commands:

> close -1 7.2.1-1
Bug #956872 [src:frr] src:frr: fails to migrate to testing for too long: ftbfs 
on mipsel
Marked as fixed in versions frr/7.2.1-1.
Bug #956872 [src:frr] src:frr: fails to migrate to testing for too long: ftbfs 
on mipsel
Marked Bug as done
> block -1 by 955067
Bug #956872 {Done: Paul Gevers } [src:frr] src:frr: fails to 
migrate to testing for too long: ftbfs on mipsel
956872 was not blocked by any bugs.
956872 was not blocking any bugs.
Added blocking bug(s) of 956872: 955067

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

Processed: src:django-sekizai: fails to migrate to testing for too long: autopkgtest regression

2020-04-16 Thread Debian Bug Tracking System

Processing control commands:

> close -1 1.1.0-2
Bug #956871 [src:django-sekizai] src:django-sekizai: fails to migrate to 
testing for too long: autopkgtest regression
Marked as fixed in versions django-sekizai/1.1.0-2.
Bug #956871 [src:django-sekizai] src:django-sekizai: fails to migrate to 
testing for too long: autopkgtest regression
Marked Bug as done

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

Bug#902241: marked as done (python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised))

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 09:46:05 +0200
with message-id <48374395-b678-206f-c8dc-e473002d5...@debian.org>
and subject line No activity: closing this bug
has caused the Debian Bug report #902241,
regarding python-proliantutils: FTBFS in stretch (AssertionError: 
IloConnectionError not raised)
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.)


-- 
902241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-proliantutils
Version: 2.1.11-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch and it failed:


[...]
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_not_to_upload_firmware_file
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_not_to_upload_firmware_file
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_to_upload_firmware_file
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_asks_to_upload_firmware_file
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_calls_extract_of_fw_extractor_object
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_calls_extract_of_fw_extractor_object
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_failed_extraction
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_failed_extraction
 ... ok
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_unknown_firmware_file_format
proliantutils.tests.test_utils.UtilsTestCase.test_process_firmware_image_throws_for_unknown_firmware_file_format
 ... ok

==
FAIL: 
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageUploaderTestCase.test__get_socket_throws_exception_in_case_of_failed_connection_2
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageUploaderTestCase.test__get_socket_throws_exception_in_case_of_failed_connection_2
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/ddt.py", line 129, in wrapper
return func(self, *args, **kwargs)
  File "proliantutils/tests/ilo/test_firmware_controller.py", line 566, in 
test__get_socket_throws_exception_in_case_of_failed_connection
self.assertRaises(expected_exception_type, fw_img_uploader._get_socket)
  File "/usr/lib/python2.7/unittest/case.py", line 473, in assertRaises
callableObj(*args, **kwargs)
  File "/usr/lib/python2.7/unittest/case.py", line 116, in __exit__
"{0} not raised".format(exc_name))
AssertionError: IloConnectionError not raised


--
Ran 473 tests in 5.071s

FAILED (failures=1)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I admit this is strange because it seems to build ok in the
reproducible builds autobuilders.

However, I've decided to report it anyway because I've tried to build
it 55 times and it failed 55 times, on 23 different autobuilders:

https://people.debian.org/~sanvila/build-logs/python-proliantutils/

I can even reproduce it with plain dpkg-buildpackage (i.e. without sbuild)
on a brand new machine from Digital Ocean, so if you could not reproduce
this, please contact me privately. As a last resort, I could give you
access to one of such machines.

Thanks.
--- End Message ---
--- Begin Message ---
It doesn't look like anyone is interested in fixing this bug. I'm myself
too busy to care about FTBFS if oldstable.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#909058: marked as done (fonts-telu-extra: adequate reports broken symlink for fonts-telu-extra)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 07:21:10 +
with message-id 
and subject line Bug#909058: fixed in fonts-telu-extra 2.0-5
has caused the Debian Bug report #909058,
regarding fonts-telu-extra: adequate reports broken symlink for fonts-telu-extra
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.)


-- 
909058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-telu-extra
Version: 2.0-4
Severity: normal

Dear Maintainer,
Thank you for maintaining indic fonts. While troubleshooting
yesterday, I purged and installed fonts-telu. Interestingly, it wanted
to install fonts-telu-extra as well -

 $ sudo aptitude install fonts-telu
 [97%]
The following NEW packages will be installed:
  fonts-telu fonts-telu-extra{a}
0 packages upgraded, 2 newly installed, 0 to remove and 91 not upgraded.
Need to get 0 B/185 kB of archives. After unpacking 457 kB will be used.
Do you want to continue? [Y/n/?] n
Abort.

sudo aptitude install fonts-telu fonts-telu-extra
  [97%]
The following NEW packages will be installed:
  fonts-telu fonts-telu-extra
0 packages upgraded, 2 newly installed, 0 to remove and 91 not upgraded.
Need to get 0 B/185 kB of archives. After unpacking 457 kB will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
(Reading database ... 806597 files and directories currently installed.)
Preparing to unpack .../fonts-telu-extra_2.0-4_all.deb ...
Unpacking fonts-telu-extra (2.0-4) ...
Selecting previously unselected package fonts-telu.
Preparing to unpack .../fonts-telu_2%3a1.2_all.deb ...
Unpacking fonts-telu (2:1.2) ...
Setting up fonts-telu-extra (2.0-4) ...
Setting up fonts-telu (2:1.2) ...
Processing triggers for fontconfig (2.13.0-5) ...
adequate found packaging bugs
-

fonts-telu-extra: broken-symlink
/etc/fonts/conf.d/65-0-fonts-telu-extra.conf ->
../conf.avail/65-0-fonts-telu-extra.conf

Interestingly, if you purge the packages it doesn't clean itself
properly as well .

$ sudo aptitude purge fonts-telu fonts-telu-extra -y
The following packages will be REMOVED:
  fonts-telu{p} fonts-telu-extra{p}
0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 457 kB will be freed.
(Reading database ... 413598 files and directories currently installed.)
Removing fonts-telu (2:1.2) ...
Removing fonts-telu-extra (2.0-4) ...
Processing triggers for fontconfig (2.13.0-5) ...
(Reading database ... 413588 files and directories currently installed.)
Purging configuration files for fonts-telu-extra (2.0-4) ...
dpkg: warning: while removing fonts-telu-extra, directory
'/usr/share/fonts/truetype/fonts-telu-extra' not empty so not removed
Processing triggers for fontconfig (2.13.0-5) ...

/usr/share/fonts/truetype/fonts-telu-extra$ ls
/usr/share/fonts/truetype/fonts-telu-extra$

Could you please fix fonts-telu-extra ?


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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_IN.UTF-8), LANGUAGE=en_IN.UTF-8
(charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- Configuration Files:
/etc/fonts/conf.avail/65-0-fonts-telu-extra.conf [Errno 2] No such
file or directory: '/etc/fonts/conf.avail/65-0-fonts-telu-extra.conf'

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: fonts-telu-extra
Source-Version: 2.0-5
Done: Kartik Mistry 

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

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

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

Bug#854162: marked as done (fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 07:21:10 +
with message-id 
and subject line Bug#854162: fixed in fonts-telu-extra 2.0-5
has caused the Debian Bug report #854162,
regarding fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/
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.)


-- 
854162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-deva-extra
Version: 3.0-3
Severity: normal


Dear Maintainer,

this package (and several other ones maintained by you) creates directories in 
/etc/fonts/conf.avail/ and those directories contain only one file with the 
same name as the directory:

$ ls -l /etc/fonts/conf.avail/65-0-fonts--extra.conf
-rw-r--r-- 1 root root  684 Feb 25  2012 
/etc/fonts/conf.avail/65-0-fonts-telu-extra.conf

/etc/fonts/conf.avail/65-0-fonts-beng-extra.conf:
total 4
-rw-r--r-- 1 root root 1064 Aug 23  2015 65-0-fonts-beng-extra.conf

/etc/fonts/conf.avail/65-0-fonts-deva-extra.conf:
total 8
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf

/etc/fonts/conf.avail/65-0-fonts-gujr-extra.conf:
total 4
-rw-r--r-- 1 root root 687 Jan  7  2012 65-0-fonts-gujr-extra.conf

/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf:
total 4
-rw-r--r-- 1 root root 689 Feb 25  2012 65-0-fonts-guru-extra.conf

/etc/fonts/conf.avail/65-0-fonts-orya-extra.conf:
total 4
-rw-r--r-- 1 root root 678 Feb 25  2012 65-0-fonts-orya-extra.conf


This is most probably an error and it would be simpler and more coherent with 
other font packages to remove those extra directories.


-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fonts-deva-extra depends on:
ii  dpkg 1.18.21
ii  fonts-gargi  2.0-4
ii  fonts-sarai  1.0-2

fonts-deva-extra recommends no packages.

fonts-deva-extra suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: fonts-telu-extra
Source-Version: 2.0-5
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated fonts-telu-extra 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: Thu, 16 Apr 2020 11:51:46 +0530
Source: fonts-telu-extra
Architecture: source
Version: 2.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 854162 909058
Changes:
 fonts-telu-extra (2.0-5) unstable; urgency=low
 .
   * Team upload.
   * debian/preinst:
 + Handles migration of conffile, patch from Ubuntu (from other packages)
   (Closes: #854162, #909058)
   * debian/control:
 + Set maintainer to Debian Fonts Task Force.
 + Updated Standards-Version to 4.5.0
 + Updated Vcs-* URLs.
 + Switched to debhelper-compat.
 + Added 'Rules-Requires-Root' field.
   * Updated debian/copyright.
   * Added debian/gitlab-ci.yml.
Checksums-Sha1:
 5dde5e19b6982f7620fb1a3c7de61584f1dc2ca5 1933 fonts-telu-extra_2.0-5.dsc
 374fec86adedbfe1447c5045ed02d20e9903999a 2364 
fonts-telu-extra_2.0-5.debian.tar.xz
Checksums-Sha256:
 34429bc6c03c9d5749498489b5c43a12c8bcdd9767625458545654820cbea3b7 1933 
fonts-telu-extra_2.0-5.dsc
 bc23ede4e4357dc69eea43a7010a883612793ea59067b3dd2ffd1becafccf2d5 2364 
fonts-telu-extra_2.0-5.debian.tar.xz
Files:
 0ad12804a57acc40378d09409cb9baa2 1933 fonts optional fonts-telu-extra_2.0-5.dsc
 f7548a78b434644680ff0b9dd72fc68c 2364 fonts optional 
fonts-telu-extra_2.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl6YAX0ACgkQAsHT8ng6
pN5izBAAinJDKV0QHm4+0haYrbWMSeq3Qf

Bug#955550: marked as done (unavailable test dependency libstdc++-riscv32-unknown-elf-newlib-nano)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 07:21:02 +
with message-id 
and subject line Bug#90: fixed in binutils-riscv64-unknown-elf 
2.32.2020.04+dfsg-2
has caused the Debian Bug report #90,
regarding unavailable test dependency libstdc++-riscv32-unknown-elf-newlib-nano
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.)


-- 
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:binutils-riscv64-unknown-elf
Version: 2.32.2019.08+dfsg-1
Severity: serious
Tags: sid bullseye

unavailable test dependency libstdc++-riscv32-unknown-elf-newlib-nano. tests are
always failing.
--- End Message ---
--- Begin Message ---
Source: binutils-riscv64-unknown-elf
Source-Version: 2.32.2020.04+dfsg-2
Done: Keith Packard 

We believe that the bug you reported is fixed in the latest version of
binutils-riscv64-unknown-elf, 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.
Keith Packard  (supplier of updated 
binutils-riscv64-unknown-elf 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: Wed, 15 Apr 2020 23:26:00 -0700
Source: binutils-riscv64-unknown-elf
Architecture: source
Version: 2.32.2020.04+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Keith Packard 
Closes: 90
Changes:
 binutils-riscv64-unknown-elf (2.32.2020.04+dfsg-2) unstable; urgency=medium
 .
   * Remove tests. Files needed from GCC are not available.
 Closes: #90.
   * Clean up debian bits
Checksums-Sha1:
 66e401cf6fca1d4ca98c4cc0118d2c1aa6245c4d 2306 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.dsc
 75e9042ebf486be2d1f88952079d66bbbf6bae61 10816 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.debian.tar.xz
 f888b4558765f493da8ec94b4c75f82df400ba29 7369 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 a54bfa22d319b5a371f113627f2fe40192dd4c6167202c824b74206e52907719 2306 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.dsc
 488b09b85d8e8c50f324d7071898d43a52dfcb5fb97cb9ad05103934f9006a5c 10816 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.debian.tar.xz
 1dd5b8dfaa32a9275069dc3e9751705acfe656bcd7fc21d4a34b5c4a91fc90d8 7369 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2_amd64.buildinfo
Files:
 5e6aecb886a4cfa1295d27525551b564 2306 devel optional 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.dsc
 77a5e94cfc1c43e2d0df2d7d93f1e6e9 10816 devel optional 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2.debian.tar.xz
 7007382516701dbc0470ca3fce55c998 7369 devel optional 
binutils-riscv64-unknown-elf_2.32.2020.04+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl6YBOYACgkQ2yIaaQAA
ABEk5w/8C7ak0LgwQ88Ho7lsoaVvseXfktvLGmmW/ooqJdFCEva+E58NSkCPXVcH
MUKB8XhtnoyKqhN8ESFw9Z4mAfDOobStyenAnyRr9AuTGhLTHa0p5stdcudemOAW
Mqyjl1dZ5nZSdUKxcc90ib6a+NCdWV/UrvbubaKhdQFm5dGLgiJGraHNEkcFG6Wj
ZL7DhZc3ZkZt9NH4hR5c/nxXMRfN8oQdOlSBS0piWDqJTgBf6BT1ylJ9fYxZR8zi
Bt3j6TZ6Y0ojf6TbhrHau3QFJRWyrHZAcMH10N4npRmawgt6Rb3nZF1KcDozwZlP
2Yvp33NlQrFI6757pdPOCzqG1bef7llo/CZKWV7FkZMC2Y52GCNA8dWlVE9i67gj
gvkTg/1xJ4G3gcWiryiWcfStlgSbFCz/qvH4KYoDJlLZjnIaaBzLtI6UgIpArNV8
Sb2D+BDk/mOELswrCzUeTLzQHOT3352sdZgSpYzWaHyj8XUn8z4WnJivuYuR8foP
YvAsI93bpH2PXEgoMHkTk6PVp3C8VGjKkzPA65ZQNCsgGTZdOBAjHLqvZcfE4v2W
6lQuWt0aR96FyFaKKCxfc1UZagVzNTVoXaoO9nbhhHX8y/GITUlVmPAXl06juJ9z
tQSROIo203UAtB5WUFzNj8Iyx4XQgSVuK0PXJk2KsHc2z16/LBs=
=GC2a
-END PGP SIGNATURE End Message ---

Bug#954024: marked as done (mate-terminal: URL highlighting is broken)

2020-04-16 Thread Debian Bug Tracking System

Your message dated Thu, 16 Apr 2020 06:49:26 +
with message-id 
and subject line Bug#954024: fixed in mate-terminal 1.24.0-2
has caused the Debian Bug report #954024,
regarding mate-terminal: URL highlighting is broken
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.)


-- 
954024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-terminal
Version: 1.24.0-1
Severity: important

Hi,

either the mate-terminal update or the vte update has broken url
highlighting. See also https://github.com/mate-desktop/mate-terminal/issues/329

Best


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

Kernel: Linux 5.5.9 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mate-terminal depends on:
ii  gsettings-desktop-schemas  3.36.0-1
ii  libatk1.0-02.34.1-1
ii  libc6  2.30-2
ii  libcairo2  1.16.0-4
ii  libdconf1  0.36.0-1
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-3
ii  libglib2.0-0   2.64.0-2
ii  libgtk-3-0 3.24.14-1
ii  libice62:1.0.9-2
ii  libpango-1.0-0 1.42.4-8
ii  libsm6 2:1.2.3-1
ii  libvte-2.91-0  0.60.0-2
ii  libx11-6   2:1.6.9-2
ii  mate-desktop-common1.24.0-2
ii  mate-terminal-common   1.24.0-1

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mate-terminal
Source-Version: 1.24.0-2
Done: Mike Gabriel 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Mar 2020 10:58:22 +0100
Source: mate-terminal
Architecture: source
Version: 1.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 954024
Changes:
 mate-terminal (1.24.0-2) unstable; urgency=medium
 .
   * debian/patches:
 + Add 0001_fix-url-highlighting.patch. Fix URL highlighting broken
   since vte 0.60. (Closes: #954024). Thanks to Norbert Preining for
   providing the patch.
Checksums-Sha1:
 3d56c1a7c916738178dc660cc93e17394292c8c3 2494 mate-terminal_1.24.0-2.dsc
 27030fdf5a2139b09d319787f983398c4930370c 9740 
mate-terminal_1.24.0-2.debian.tar.xz
 b79e4a8368fc4ab9185069db122265451b16162b 14774 
mate-terminal_1.24.0-2_source.buildinfo
Checksums-Sha256:
 d8edf04629ee1e7173b94e2ed5c27bd9f2c6b6d30b5dc1a11f46a1379a48fb34 2494 
mate-terminal_1.24.0-2.dsc
 6ff665b6544d41be4e6deb36306bf262f5747ed96017f2850b2dcf38d82d3625 9740 
mate-terminal_1.24.0-2.debian.tar.xz
 2cbc4db6cb4e61f7187e05a1212fa13edfd6ff90b2a7b02da1bc9089d44c2144 14774 
mate-terminal_1.24.0-2_source.buildinfo
Files:
 3f5ba45998cb1cdbfa94cd8b0d72bea7 2494 x11 optional mate-terminal_1.24.0-2.dsc
 566d8637d09a899eb40f71eaa006e071 9740 x11 optional 
mate-terminal_1.24.0-2.debian.tar.xz
 b50f70210f4bdb77b6c41f64c4b30b57 14774 x11 optional 
mate-terminal_1.24.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl57GFsVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxDFQQAJIUFHcP/fstG9p8OjQzZQ+bcdq/
vcMgpfwGzXZQzp0oufttPGVZWET8mdiLuDqYyF+Ob4kUfjCow6w9Yr9SxAe6hYi9
dwfjK9YtdU/ZnLVejWVAgk2eU7lO5y6u0ICP+2Y05JHLttCaNilNFCeE1sc/N5MA
ZjeS9RPnR0rBNcRmQITzG2938Dmih2pCytQ/dfePZmUeoE+qVbBFfSxyS0GrVSVq
o0PxKWywJaORDoZh03KddDgFmB0KrJ4KKhQZjJbOM41OIih0au8//CF8V4DjB1IN
HVF47l+ueFgdiTZfCx/fHcF/KqmuZBCLNBB6wZawQ1JvvFhlloOTY6HKGjCqE52I
BLtmmUJNm6jw9MpFhUXV57XDUGDG

89 matches

Mail list logo