Processed: closing 954563

[Debian Bug Tracking System]

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

> close 954563
Bug #954563 [src:python-dugong] python-dugong: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#959671: marked as done (merkaartor FTCBFS: uses the build architecture qmake)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 06:03:55 +
with message-id 
and subject line Bug#959671: fixed in merkaartor 0.18.4+ds-3
has caused the Debian Bug report #959671,
regarding merkaartor FTCBFS: uses the build architecture qmake
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.)


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

merkaartor fails to cross build from source, because debian/rules runs
the build architecture qmake. A simple way of using the host qmake is
running it through dh_auto_configure. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru merkaartor-0.18.4+ds/debian/changelog 
merkaartor-0.18.4+ds/debian/changelog
--- merkaartor-0.18.4+ds/debian/changelog   2020-04-29 21:49:20.0 
+0200
+++ merkaartor-0.18.4+ds/debian/changelog   2020-05-03 17:55:55.0 
+0200
@@ -1,3 +1,10 @@
+merkaartor (0.18.4+ds-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure use a cross qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 03 May 2020 17:55:55 +0200
+
 merkaartor (0.18.4+ds-2) unstable; urgency=medium
 
   * source-only upload.
diff --minimal -Nru merkaartor-0.18.4+ds/debian/rules 
merkaartor-0.18.4+ds/debian/rules
--- merkaartor-0.18.4+ds/debian/rules   2020-02-07 10:45:40.0 +0100
+++ merkaartor-0.18.4+ds/debian/rules   2020-05-03 17:55:55.0 +0200
@@ -14,7 +14,7 @@
 export QT_SELECT=5
 
 %:
-   dh $@
+   dh $@ --buildsystem=qmake
 
 override_dh_auto_clean:
dh_auto_clean
@@ -26,10 +26,9 @@
 
 override_dh_auto_configure:
cd translations && make release
-   qmake -recursive \
+   dh_auto_configure -- -recursive \
Merkaartor.pro \
TRANSDIR_SYSTEM="/usr/share/qt5/translations/" \
-   PREFIX=/usr \
GDAL=1 \
GEOIMAGE=1 \
GPSDLIB=1 \
--- End Message ---
--- Begin Message ---
Source: merkaartor
Source-Version: 0.18.4+ds-3
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated merkaartor 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, 05 May 2020 05:55:21 +
Source: merkaartor
Architecture: source
Version: 0.18.4+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Jerome Benoit 
Closes: 959671
Changes:
 merkaartor (0.18.4+ds-3) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_configure use a cross qmake (closes: #959671).
 .
   [ Jerome Benoit ]
   * Debianization:
 - debian/control:
   - Maintainer email address, update.
Checksums-Sha1:
 d1d29ae0d151cbf65680c37d807929e399214e32 2996 merkaartor_0.18.4+ds-3.dsc
 fa7de41b0445eb3021e787db652d17d3dfc5982c 13860 
merkaartor_0.18.4+ds-3.debian.tar.xz
 372e776a7644e6a984f6a39cf5c7d9d87e7793f4 16287 
merkaartor_0.18.4+ds-3_source.buildinfo
Checksums-Sha256:
 d2b1ee29ee65f1374dae82cb2d0b0a06cf19bc119868bb8af5f1f267adf72c2b 2996 
merkaartor_0.18.4+ds-3.dsc
 2337f191f924b609281191bfe34f49a9819817ade5c875d99baa0f6dce8cbbb1 13860 
merkaartor_0.18.4+ds-3.debian.tar.xz
 c968c3947f5315f2bd08194c0c1a8acb369b726e66b10059237070b2cb42ba6c 16287 
merkaartor_0.18.4+ds-3_source.buildinfo
Files:
 f2665bc30bc973ceacd356225e30ee53 2996 science optional 
merkaartor_0.18.4+ds-3.dsc
 a9f4c888bd11bbee0ad2acce2454ae44 13860 science optional 
merkaartor_0.18.4+ds-3.debian.tar.xz
 269fdd95a76df4ce3846f5c0176f7696 16287 science optional 
merkaartor_0.18.4+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl6xAGEVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLvMcf/3m8/VUs6dzGPU9BMhHzE4eh5uC+
D2FxFLW6RJ0ofc7KhElQWdT7vzk6R0KsNnh+zKeGyt+27afjEpj/VNcCFBWIFfP8
CZvJ0KJcjR46D2df6RP6fIE

Bug#943824: marked as done ([libeantic0] crashing because of buffer overflow)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 05:33:44 +
with message-id 
and subject line Bug#943824: fixed in e-antic 0.1.5+ds-1
has caused the Debian Bug report #943824,
regarding [libeantic0] crashing because of buffer overflow
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.)


-- 
943824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libeantic0
Version: 0.1.3+ds-3
Severity: normal
Tags: patch

The attached patch fixes a crash caused by a buffer overflow: a sprintf
call in the code uses a fixed size buffer without checking if the string
will actually fit inside it.

I discovered it because an application I am writing crashed over it.

The attached patch should fix the problem. I can NMU if you're ok with it.

Thanks, Giovanni.


--- System information. ---
Architecture: Kernel:   Linux 5.2.0-3-amd64

Debian Release: bullseye/sid
  500 xenial  updates.signal.org   500 unstable-debug
debug.mirrors.debian.org   500 unstabledeb.debian.org   500
testing deb.debian.org   500 stable  repo.skype.com
500 stable  dl.google.com 1 experimentaldeb.debian.org
--- Package information. ---
Depends(Version) | Installed
-+-==
libc6   (>= 2.4) | libflint-2.5.2   |
libflint-arb2  (>= 1:2.17.0) | libgcc1   (>= 1:3.0) |
libgmp10 | libgomp1  (>= 4.2.1) |
libstdc++6(>= 4.1.1) |

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles
diff -Nru e-antic-0.1.3+ds/debian/changelog e-antic-0.1.3+ds/debian/changelog
--- e-antic-0.1.3+ds/debian/changelog	2019-09-27 18:18:49.0 +0200
+++ e-antic-0.1.3+ds/debian/changelog	2019-10-30 12:37:40.0 +0100
@@ -1,3 +1,10 @@
+e-antic (0.1.3+ds-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix buffer overflow on sprintf call.
+
+ -- Giovanni Mascellani   Wed, 30 Oct 2019 12:37:40 +0100
+
 e-antic (0.1.3+ds-3) unstable; urgency=medium
 
   * FTBFS fix release (Closes: #941259), see below.
diff -Nru e-antic-0.1.3+ds/debian/patches/fix_sprintf_buffer_overflow.patch e-antic-0.1.3+ds/debian/patches/fix_sprintf_buffer_overflow.patch
--- e-antic-0.1.3+ds/debian/patches/fix_sprintf_buffer_overflow.patch	1970-01-01 01:00:00.0 +0100
+++ e-antic-0.1.3+ds/debian/patches/fix_sprintf_buffer_overflow.patch	2019-10-30 12:37:35.0 +0100
@@ -0,0 +1,24 @@
+From: Giovanni Mascellani 
+Subject: Fix buffer overflow caused by sprintf
+
+sprintf() is called on a fixed-size buffer, overflowing it
+on some inputs and triggering undefined behaviour. This patch
+ensure that the buffer is sufficiently large.
+
+Index: e-antic-0.1.3+ds/renf_elem/get_str_pretty.c
+===
+--- e-antic-0.1.3+ds.orig/renf_elem/get_str_pretty.c
 e-antic-0.1.3+ds/renf_elem/get_str_pretty.c
+@@ -42,8 +42,10 @@ char * renf_elem_get_str_pretty(renf_ele
+ if (flag & EANTIC_STR_D)
+ {
+ // output of get_d
+-s = flint_malloc(20 * sizeof(char));
+-sprintf(s, "%lf", renf_elem_get_d(a, nf, ARF_RND_NEAR));
++double d = renf_elem_get_d(a, nf, ARF_RND_NEAR);
++int len = snprintf(NULL, 0, "%lf", d);
++s = flint_malloc((len+1) * sizeof(char));
++snprintf(s, len+1, "%lf", d);
+ t = flint_realloc(t, strlen(t) + strlen(s) + 1);
+ strcat(t, s);
+ flint_free(s);
diff -Nru e-antic-0.1.3+ds/debian/patches/series e-antic-0.1.3+ds/debian/patches/series
--- e-antic-0.1.3+ds/debian/patches/series	2019-06-20 19:24:48.0 +0200
+++ e-antic-0.1.3+ds/debian/patches/series	2019-10-30 12:33:26.0 +0100
@@ -1,3 +1,4 @@
 upstream-libtool-versioning.patch
 upstream-libtool-version_script.patch
 debianization.patch
+fix_sprintf_buffer_overflow.patch


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: e-antic
Source-Version: 0.1.5+ds-1
Done: Jerome Benoit 

We believe that the bug you reported is fixed in the latest version of
e-antic, 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 943...@bugs.debian.org,
and the maintainer will reopen

Processed: closing 959738

[Debian Bug Tracking System]

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

> close 959738
Bug #959738 [tensorflow] tensorflow: Package tensorflow
Warning: Unknown package 'tensorflow'
Marked Bug as done
Warning: Unknown package 'tensorflow'
> thanks
Stopping processing here.

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

Bug#957275: marked as done (global: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 5 May 2020 11:48:11 +0900
with message-id 

and subject line Re: global: ftbfs with GCC-10
has caused the Debian Bug report #957275,
regarding global: 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.)


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/global_6.6.4-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I../libparser  -I../libutil -I../libdb -I../libglibc -I../libutil 
-DDATADIR='"/usr/share/global"' -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o user-custom.lo user-custom.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libparser -I../libutil 
-I../libdb -I../libglibc -I../libutil -DDATADIR=\"/usr/share/global\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c user-custom.c  
-fPIC -DPIC -o .libs/user-custom.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libparser -I../libutil 
-I../libdb -I../libglibc -I../libutil -DDATADIR=\"/usr/share/global\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_EXTRA_FIELDS -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c exuberant-ctags.c  -fPIC -DPIC -o 
.libs/universal_ctags_la-exuberant-ctags.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libparser -I../libutil 
-I../libdb -I../libglibc -I../libutil -DDATADIR=\"/usr/share/global\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c pygments-parser.c  
-fPIC -DPIC -o .libs/pygments-parser.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libparser -I../libutil 
-I../libdb -I../libglibc -I../libutil -DDATADIR=\"/usr/share/global\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c exuberant-ctags.c  
-fPIC -DPIC -o .libs/exuberant-ctags.o
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -module -avoid-version -no-undefined -Wl,-z,relro 
-Wl,-z,now -o user-custom.la -rpath /usr/lib/x86_64-linux-gnu/gtags 
user-custom.lo  
libtool: link: gcc -shared  -fPIC -DPIC  .libs/user-custom.o-g -O2 
-fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
-Wl,user-custom.so -o .libs/user-custom.so
libtool: link: ( cd ".libs" && rm -f "user-custom.la" && ln -s 
"../user-custom.la" "user-custom.la" )
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -module -avoid-version -no-undefined -Wl,-z,relro 
-Wl,-z,now -o pygments-parser.la -rpath /usr/lib/x86_64-linux-gnu/gtags 
pygments-parser.lo  
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -module -avoid-version -no-undefined -Wl,-z,relro 
-Wl,-z,now -o exuberant-ctags.la -rpath /usr/lib/x86_64-linux-gnu/gtags 
exuberant-ctags.lo  
/bin/bash ../libtool  --tag=CC   --mode=link gcc -DUSE_EXTRA_FIELDS -g -O2 
-fdebug-pre

Bug#959728: marked as done (rmarkdown: css, fonts, etc missing)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 00:18:44 +
with message-id 
and subject line Bug#959728: fixed in r-cran-rmarkdown 2.1+dfsg-3
has caused the Debian Bug report #959728,
regarding rmarkdown: css, fonts, etc missing
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.)


-- 
959728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-rmarkdown
Version: 2.1+dfsg-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Tests in nascent package pigx-rnaseq.

   * What was the outcome of this action?
This error message in the log file while running
/usr/bin/Rscript --vanilla 
/home/moeller/git/med-team/pigx/pigx-rnaseq/scripts/runDeseqReport.R 
--logo=/home/moeller/git/med-team/pigx/pigx-rnaseq/images/Logo_PiGx.png 
--prefix='analysis1.salmon.transcripts' 
--reportFile=/home/moeller/git/med-team/pigx/pigx-rnaseq/scripts/deseqReport.Rmd
 
--countDataFile=/home/moeller/git/med-team/pigx/pigx-rnaseq/tests/output/feature_counts/raw_counts/counts_from_SALMON.transcripts.tsv
 
--colDataFile=/home/moeller/git/med-team/pigx/pigx-rnaseq/tests/output/colData.tsv
 
--gtfFile=/home/moeller/git/med-team/pigx/pigx-rnaseq/tests/sample_data/sample.gtf
 --caseSampleGroups='HBR' --controlSampleGroups='UHR' --covariates='' 
--workdir=/home/moeller/git/med-team/pigx/pigx-rnaseq/tests/output/report 
--organism='' >> 
/home/moeller/git/med-team/pigx/pigx-rnaseq/tests/output/logs/analysis1.report.salmon.transcripts.log
 2>&1

Can't copy dependency files that don't exist: 
'/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/css', 
'/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/fonts', 
'/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/js', 
'/usr/lib/R/site-library/rmarkdown/rmd/h/bootstrap/shim'

   * What outcome did you expect instead?

Well, one could possibly address this also by a better script of pigx-rnaseq, 
but the Debian package should not make unecessary compromises. We should have 
symlinks in place that point to the respective files in other Debian packages, 
such that the copy operation would have worked out just fine.

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, 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)
LSM: AppArmor: enabled

Versions of packages r-cran-rmarkdown depends on:
ii  fonts-font-awesome   5.0.10+really4.7.0~dfsg-1
ii  libjs-bootstrap  3.4.1+dfsg-1
ii  libjs-highlight.js   9.12.0+dfsg1-5
ii  libjs-jquery 3.3.1~dfsg-3
ii  libjs-jquery-ui  1.12.1+dfsg-5
ii  libjs-modernizr  2.6.2+ds1-3
ii  libjs-prettify   2015.12.04+dfsg-1.1
ii  node-html5shiv   3.7.3+dfsg-3
ii  pandoc   2.5-3+b1
ii  r-base-core [r-api-3.5]  3.6.3-2
ii  r-cran-base64enc 0.1-3-2
ii  r-cran-evaluate  0.14-1
ii  r-cran-htmltools 0.4.0-1
ii  r-cran-jsonlite  1.6.1+dfsg-1
ii  r-cran-knitr 1.28+dfsg-1
ii  r-cran-mime  0.9-1
ii  r-cran-shiny 1.4.0.2+dfsg-1
ii  r-cran-stringr   1.4.0-1
ii  r-cran-tinytex   0.22-1
ii  r-cran-xfun  0.13-1
ii  r-cran-yaml  2.2.1-1

Versions of packages r-cran-rmarkdown recommends:
ii  r-cran-testthat  2.3.2-1

Versions of packages r-cran-rmarkdown suggests:
ii  r-cran-callr 3.4.3-1
ii  r-cran-digest0.6.25-1
pn  r-cran-dygraphs  
ii  r-cran-fs1.4.1+dfsg-1
ii  r-cran-shiny 1.4.0.2+dfsg-1
ii  r-cran-tibble3.0.1-1
pn  r-cran-tufte 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-cran-rmarkdown
Source-Version: 2.1+dfsg-3
Done: Steffen Moeller 

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

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated r-cran-rmarkdown 
package)

(This message was generated automatically at their r

Bug#959570: marked as done (python-fluids: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 05 May 2020 00:18:36 +
with message-id 
and subject line Bug#959570: fixed in python-fluids 0.1.78-1
has caused the Debian Bug report #959570,
regarding python-fluids: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 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.)


-- 
959570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fluids
Version: 0.1.75-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/piping.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/units.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/geometry.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/core.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/drag.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/separator.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/two_phase_voidage.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/saltation.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/mixing.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/safety_valve.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/design_climate.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/flow_meter.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/open_flow.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/particle_size_distribution.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/packed_tower.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/friction.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/vectorized.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/pump.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/packed_bed.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/jet_pump.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/control_valve.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/compressible.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/filters.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/atmosphere.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/fittings.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> copying fluids/two_phase.py -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids
> creating /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 smooth bends Re correction.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/isd-history-cleaned.tsv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 conical contractions K part 2.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 entrances rounded beveled K.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 smooth bends outlet tangent length 
> correction.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 smooth bends Kb.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/residential power.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/ISO 3310-1 sieves.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/3 phase power.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 conical contractions K part 1.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/ASTM E11 sieves.csv -> 
> /<>/.pybuild/cpython3_3.8_fluids/build/fluids/data
> copying fluids/data/Miller 2E 1990 Kb mitre bend.csv -> 
> /<>/.pybuild/cpytho

Bug#942222: marked as done (crash at startup, like #734405 (ValueError: numpy.dtype does not appear to be the correct type object))

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:42:36 +
with message-id 
and subject line Bug#959750: Removed package(s) from unstable
has caused the Debian Bug report #94,
regarding crash at startup, like #734405 (ValueError: numpy.dtype does not 
appear to be the correct type 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.)


-- 
94: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seekwatcher
Version: 0.12+hg20091016-3
Severity: grave

In Debian 10 and current Debian 9:

# seekwatcher
Traceback (most recent call last):
  File "/usr/bin/seekwatcher", line 58, in 
from seekwatcher import rundata
  File "numpy.pxd", line 43, in seekwatcher.rundata (seekwatcher/rundata.c:7885)
ValueError: numpy.dtype does not appear to be the correct type object

Previous report: 
--- End Message ---
--- Begin Message ---
Version: 0.12+hg20091016-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#938462: marked as done (seekwatcher: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:42:36 +
with message-id 
and subject line Bug#959750: Removed package(s) from unstable
has caused the Debian Bug report #938462,
regarding seekwatcher: 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.)


-- 
938462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seekwatcher
Version: 0.12+hg20091016-3
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:seekwatcher

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 ---
Version: 0.12+hg20091016-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#959751: marked as done (RM: telepathy-python -- RoQA; Depends on Python 2, dead upstream)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:42:58 +
with message-id 
and subject line Bug#959751: Removed package(s) from unstable
has caused the Debian Bug report #959751,
regarding RM: telepathy-python -- RoQA; Depends on Python 2, dead upstream
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.)


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

Please remove telepathy-python. It's dead upstream (last commit in 2010)
and was not ported to Python 3.

There's one remaining rdep (python-jarabe from src:sugar), but please
force this one through; src:sugar has been dropped from testing for over
half a year and has a fix pending in NEW.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-telepathy |  0.15.19-3 | all
telepathy-python |  0.15.19-3 | source

--- Reason ---
RoQA; Depends on Python 2, dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959751

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

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

Bug#956722: marked as done (python-gnatpython: Please consider removing this package)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:43:22 +
with message-id 
and subject line Bug#959753: Removed package(s) from unstable
has caused the Debian Bug report #956722,
regarding python-gnatpython: Please consider removing this package
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.)


-- 
956722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gnatpython
Version: 54-3
Severity: serious
X-Debbugs-CC: xavier.gr...@ipno.in2p3.fr xavier.gr...@csnsm.in2p3.fr

Dear Debian python-gnatpython maintainer,

As indicated in the package tracker (
https://tracker.debian.org/pkg/python-gnatpython), package python-gnatpython
in Debian received no upload in the last 8 years and its upstream is also
defunct. Besides, it is affected by the current python2 removal. It also has
no reverse dependencies and reverse build-dependencies.

As a result, I believe this package is suitable to be removed from Debian. I
will consider filing the removal request 21 days later (after May 05, 2020).
If you have any thoughts, please let me know *immediately* so that this issue
could be solved properly in time.

Thanks for your past contribution in Debian and looking forward to your reply.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 54-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#959753: marked as done (RM: python-gnatpython -- RoQA; Upstream Dead; Unmaintained; Affected by Python2 Removal)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:43:19 +
with message-id 
and subject line Bug#959753: Removed package(s) from unstable
has caused the Debian Bug report #959753,
regarding RM: python-gnatpython -- RoQA; Upstream Dead; Unmaintained; Affected 
by Python2 Removal
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.)


-- 
959753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-CC: xavier.gr...@ipno.in2p3.fr

Dear FTP Masters,

As discussed in https://bugs.debian.org/956722 , please remove package python-
gnatpython from Debian archive. It has a dead upstream with no package
maintainer activity in the last 8 years. The package is currrently affected by
the Python2 removal. Its popcon value is also low (8). It also has no reverse
dependencies or reverse build-dependencies. The current package maintainer did
not respond to the package removal request at https://bugs.debian.org/956722 .

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-gnatpython |   54-3 | source
python-gnatpython |54-3+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-gnatpython-doc |   54-3 | all

--- Reason ---
RoQA; Upstream Dead; Unmaintained; Affected by Python2 Removal
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959753

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

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

Bug#959750: marked as done (RM: seekwatcher -- RoQA; Depends on Python 2, dead upstream)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:42:33 +
with message-id 
and subject line Bug#959750: Removed package(s) from unstable
has caused the Debian Bug report #959750,
regarding RM: seekwatcher -- RoQA; Depends on Python 2, dead upstream
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.)


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

Please remove seekwatcher. It depends on Python 2 and is dead upstream,
acked by the maintainer (CCed).

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

seekwatcher | 0.12+hg20091016-3 | source
seekwatcher | 0.12+hg20091016-3+b1 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
RoQA; Depends on Python 2, dead upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959750

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

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

Bug#938642: marked as done (telepathy-python: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:43:02 +
with message-id 
and subject line Bug#959751: Removed package(s) from unstable
has caused the Debian Bug report #938642,
regarding telepathy-python: 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.)


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

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 ---
Version: 0.15.19-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#580689: marked as done (UnboundLocalError: local variable 'openfile')

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:44:13 +
with message-id 
and subject line Bug#959754: Removed package(s) from unstable
has caused the Debian Bug report #580689,
regarding UnboundLocalError: local variable 'openfile'
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.)


-- 
580689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spikeproxy
Version: 1.4.8-4.1
Severity: important

Hello, while using spikeproxy, i ran into the following traceback :

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
self.run()
  File "spkproxy.py", line 928, in run
response = self.sendRequest(myheader,mybody)
  File "spkproxy.py", line 1182, in sendRequest

self.myUI.registerRequestandResponse(myheader,mybody,serverheader,serverbody

   )
  File "/usr/share/spikeproxy/spikeProxyUI.py", line 324, in 
registerRequestandR 
  esponse

result=self.storeRequestandResponse(clientheader,clientbody,serverheader,ser

   verbody)
  File "/usr/share/spikeproxy/spikeProxyUI.py", line 468, in 
storeRequestandResp 
  onse
cPickle.dump(obj,openfile,binary)
UnboundLocalError: local variable 'openfile' referenced before assignment

Hope this helps.

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

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages spikeproxy depends on:
ii  python2.5.4-9An interactive high-level object-o
ii  python-openssl0.10-1 Python wrapper around the OpenSSL 
ii  python-support1.0.8  automated rebuilding support for P

spikeproxy recommends no packages.

spikeproxy suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1.4.8-4.4+rm

Dear submitter,

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

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

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

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

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

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

Bug#737113: marked as done (spikeproxy: Should not ship embedded compy of timeoutsocket)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:44:13 +
with message-id 
and subject line Bug#959754: Removed package(s) from unstable
has caused the Debian Bug report #737113,
regarding spikeproxy: Should not ship embedded compy of timeoutsocket
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.)


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

Dear Maintainer,

It seems to me that spikeproxy embedds a copy of timeoutsocket.py, which seems 
to be potentially duplicated in other packages (although slightly modified from 
looking at other copies).

This isn't optimal to Debian standards.

One solution would be to instead depend on a system package providing 
timeoutsocket (an RFP exists at #736935).

But as timeoutsocket seems to be no longer needed in recent versions of Python 
(see the discussion at [0]), it may as well be removed from the installed 
files, making sure that the necessary patch is applied to upstream code.

Thanks in advance if you can address this.

Best regards,

[0] https://lists.debian.org/debian-python/2014/01/msg00088.html


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1.4.8-4.4+rm

Dear submitter,

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

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

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

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

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

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

Bug#937793: marked as done (python-gnatpython: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:43:22 +
with message-id 
and subject line Bug#959753: Removed package(s) from unstable
has caused the Debian Bug report #937793,
regarding python-gnatpython: 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.)


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

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 ---
Version: 54-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#959754: marked as done (RM: spikeproxy -- RoQA; Depends on Python 2, dead upstream, unmaintained)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:44:09 +
with message-id 
and subject line Bug#959754: Removed package(s) from unstable
has caused the Debian Bug report #959754,
regarding RM: spikeproxy -- RoQA; Depends on Python 2, dead upstream, 
unmaintained
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.)


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

Please remove spikeproxy. It depends on Python 2, is dead upstream and the
last maintainer upload was in 2006.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

spikeproxy |  1.4.8-4.4 | all
  spkproxy |  1.4.8-4.4 | source

--- Reason ---
RoQA; Depends on Python 2, dead upstream, unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959754

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

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

Bug#935208: marked as done (spkproxy: Please port to Python 3 and/or drop Python 2 package)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:44:13 +
with message-id 
and subject line Bug#959754: Removed package(s) from unstable
has caused the Debian Bug report #935208,
regarding spkproxy: Please port to Python 3 and/or drop Python 2 package
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.)


-- 
935208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spkproxy
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello, please port spkproxy to Python3 and/or drop the python 2
package. This will help the goal of removing Python 2 from Debian,
and would also (more immediately) allow to remove packages currently
dependencies of this one.

More info at: https://wiki.debian.org/Python/2Removal

Thanks, Sandro 
--- End Message ---
--- Begin Message ---
Version: 1.4.8-4.4+rm

Dear submitter,

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

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

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

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

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

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

Bug#832865: marked as done (telepathy-python: FTBFS: will not overwrite just-created '/«PKGBUILDDIR»/debian/python-telepathy//usr/lib/python2.7/dist-packages/telepathy/_generated/errors.py' with '_gen

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 22:43:02 +
with message-id 
and subject line Bug#959751: Removed package(s) from unstable
has caused the Debian Bug report #832865,
regarding telepathy-python: FTBFS: will not overwrite just-created 
'/«PKGBUILDDIR»/debian/python-telepathy//usr/lib/python2.7/dist-packages/telepathy/_generated/errors.py'
 with '_generated/errors.py'
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.)


-- 
832865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-python
Version: 0.15.19-2.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/«PKGBUILDDIR»/src'
> make[5]: Nothing to be done for 'install-exec-am'.
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Channel_Interface_Mergeable_Conference.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_Mergeable_Conference.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Call_Content_Codec_Offer.py \
> ../tools/spec-to-python.xsl \
> ../spec/Call_Content_Codec_Offer.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Addressing.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Addressing.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Client_Handler_Future.py \
> ../tools/spec-to-python.xsl \
> ../spec/Client_Handler_Future.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Call_Content_Interface_Mute.py \
> ../tools/spec-to-python.xsl \
> ../spec/Call_Content_Interface_Mute.xml
> xsltproc --nonet --novalid --xinclude -o _generated/template.py \
> ../tools/spec-to-python.xsl \
> ../spec/template.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Forwarding.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Forwarding.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Channel_Interface_Addressing.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_Addressing.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Privacy.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Privacy.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Protocol_Interface_Avatars.py \
> ../tools/spec-to-python.xsl \
> ../spec/Protocol_Interface_Avatars.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Channel_Dispatcher_Future.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Dispatcher_Future.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Channel_Interface_Splittable.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_Splittable.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Call_Content.py \
> ../tools/spec-to-python.xsl \
> ../spec/Call_Content.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Renaming.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Renaming.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Channel_Interface_Room.py 
> \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_Room.xml
> xsltproc --nonet --novalid --xinclude -o _generated/all.py \
> ../tools/spec-to-python.xsl \
> ../spec/all.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Channel_Bundle.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Bundle.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Channel_Type_Call.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Type_Call.xml
> xsltproc --nonet --novalid --xinclude -o _generated/Channel_Interface_HTML.py 
> \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_HTML.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Power_Saving.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Power_Saving.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Connection_Interface_Communication_Policy.py \
> ../tools/spec-to-python.xsl \
> ../spec/Connection_Interface_Communication_Policy.xml
> xsltproc --nonet --novalid --xinclude -o 
> _generated/Channel_Interface_Transfer.py \
> ../tools/spec-to-python.xsl \
> ../spec/Channel_Interface_Tr

Bug#959528: marked as done (RFS: streamlink/1.4.1+dfsg-1~bpo10+1 -- CLI for extracting video streams from various websites to a video player)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:33:13 -0400
with message-id <663f0a2e4ffe894460048790ec076a0e49bbdcdc.ca...@debian.org>
and subject line Re: RFS: streamlink/1.4.1+dfsg-1~bpo10+1 -- CLI for extracting 
video streams from various websites to a video player
has caused the Debian Bug report #959528,
regarding RFS: streamlink/1.4.1+dfsg-1~bpo10+1 -- CLI for extracting video 
streams from various websites to a video player
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.)


-- 
959528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-backpo...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "streamlink" into Debian
buster-backports repository.

 * Package name: streamlink
   Version : 1.4.1+dfsg-1~bpo10+1
   Upstream Author : Streamlink Team
 * URL : https://streamlink.github.io/
 * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
   Section : python

It builds those binary packages:

  python3-streamlink - Python module for extracting video streams from various 
websites
  python3-streamlink-doc - CLI for extracting video streams from various 
websites (documentation)
  streamlink - CLI for extracting video streams from various websites to a 
video player

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/streamlink


Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_1.4.1+dfsg-1~bpo10+1.dsc

More information about streamlink can be obtained at
https://streamlink.github.io/

Changes since the last upload to buster-backports:
streamlink (1.4.1+dfsg-1~bpo10+1) buster-backports; urgency=medium

  * Rebuild for buster-backports.

 -- Alexis Murzeau   Sun, 03 May 2020 12:13:21 +0200

streamlink (1.4.1+dfsg-1) unstable; urgency=medium

  * New upstream version 1.4.1+dfsg
  * Remove upstreamed patch and update others
  * d/control: update description

 -- Alexis Murzeau   Sat, 25 Apr 2020 15:28:44 +0200

Differences from testing package (1.4.1+dfsg-1):
  * Update d/README.source for buster-backports

Regards,
-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F










signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Uploaded, thanks.

-- 
Regards,
Boyuan Yang


On Sun, 3 May 2020 12:54:28 +0200 Alexis Murzeau  wrote:
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-CC: debian-backpo...@lists.debian.org
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "streamlink" into Debian
> buster-backports repository.
> 
>  * Package name: streamlink
>Version : 1.4.1+dfsg-1~bpo10+1
>Upstream Author : Streamlink Team
>  * URL : https://streamlink.github.io/
>  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
>Section : python
> 
> It builds those binary packages:
> 
>   python3-streamlink - Python module for extracting video streams from
various websites
>   python3-streamlink-doc - CLI for extracting video streams from various
websites (documentation)
>   streamlink - CLI for extracting video streams from various websites to a
video player
> 
> To access further information about this package, please visit the
> following URL:
>   https://mentors.debian.net/package/streamlink
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_1.4.1+dfsg-1~bpo10+1.dsc
> 
> More information about streamlink can be obtained at
> https://streamlink.github.io/
> 
> Changes since the last upload to buster-backports:
> streamlink (1.4.1+dfsg-1~bpo10+1) buster-backports; urgency=medium
> 
>   * Rebuild for buster-backports.
> 
>  -- Alexis Murzeau   Sun, 03 May 2020 12:13:21 +0200
> 
> streamlink (1.4.1+dfsg-1) unstable; urgency=medium
> 
>   * New upstream version 1.4.1+dfsg
>   * Remove upstreamed patch and update others
>   * d/control: update description
> 
>  -- Alexis Murzeau   Sat, 25 Apr 2020 15:28:44 +0200
> 
> Differences from testing package (1.4.1+dfsg-1):
>   * Update d/README.source for buster-backports
> 
> Regards,
> -- 
> Alexis Murzeau
> PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F


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

Bug#956846: marked as done (debarchiver: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Tue, 5 May 2020 00:01:32 +0200
with message-id 

and subject line Re: Bug#956846: debarchiver: Please make another source-only 
upload to allow testing migration
has caused the Debian Bug report #956846,
regarding debarchiver: Please make another source-only upload to allow testing 
migration
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.)


-- 
956846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debarchiver
Version: 0.11.4
Severity: important
X-Debbugs-CC: o...@debian.org

Dear debarchiver maintainer,

Your previous upload of package debarchiver was not source-only upload; as a
result, the new verison will not be able to migrate to Debian Testing. The
restriction on non-source-only upload went into effect since the release of
Debian Buster; you may find the detailed announcement at 
https://lists.debian.org/debian-devel-announce/2019/07/msg2.html .

Please make another source-only upload. Details about how to make source-only
uploads can be found at https://wiki.debian.org/SourceOnlyUpload .

Please let me know if there are any questions or issues.

-- 
Regards,
Boyuan Yang


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

Fixed by the upload of 0.11.5. Thank you for reporting.

// Ola

On Wed, 15 Apr 2020 at 22:12, Boyuan Yang  wrote:
>
> Source: debarchiver
> Version: 0.11.4
> Severity: important
> X-Debbugs-CC: o...@debian.org
>
> Dear debarchiver maintainer,
>
> Your previous upload of package debarchiver was not source-only upload; as a
> result, the new verison will not be able to migrate to Debian Testing. The
> restriction on non-source-only upload went into effect since the release of
> Debian Buster; you may find the detailed announcement at
> https://lists.debian.org/debian-devel-announce/2019/07/msg2.html .
>
> Please make another source-only upload. Details about how to make source-only
> uploads can be found at https://wiki.debian.org/SourceOnlyUpload .
>
> Please let me know if there are any questions or issues.
>
> --
> Regards,
> Boyuan Yang



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
|  o...@inguza.como...@debian.org|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
 -- End Message ---

Bug#953654: marked as done (libc6-dbg should be renamed (or at least Provide:) libc6-dbgsym)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#953654: fixed in glibc 2.30-5
has caused the Debian Bug report #953654,
regarding libc6-dbg should be renamed (or at least Provide:) libc6-dbgsym
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.)


-- 
953654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dbg
Version: 2.29-10

Every other debug symbol package in debian is named $foo-dbgsym.  libc6
seems to be the exception.

Can we please rename this package (along with a transitional package to
help folks upgrade from libc6-dbg) and set up an appropriate Provides:
at least?

This can be a stumbling block for people trying to get software
development work done on debian, as evidenced by me screwing up over
here:

https://lists.debian.org/debian-powerpc/2020/03/msg00029.html

 --dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-5
Done: Aurelien Jarno 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict against libgcc-X-dev versions that might need the
 __glibc_has_include macro.
   * debian/patches/any/local-revert-glibc_has_include.diff: drop patch,
 obsolete.
   * debian/control.in/libc: add a Provides: libc6-dbgsym to the libc6-dbg
 package.  Closes: #953654.
   * debian/control.in/libc: qualify the libselinux-dev build-depends with
 .
   * debian/debhelper.in/libc.postinst: drop the code removing
 /etc/ld.so.hwcappkgs, it's not needed anymore since Squeeze.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fixes data race in setting function descriptor during lazy binding on
   hppa. Closes: #941174.
 - debian/patches/any/local-tst-system-disable-shell-tests.diff: obsolete.
 .
   [ Helmut Grohne ]
   * Refactor generation of multilib include symlinks. (Closes: #958674).
   * Initial, minimal support for DPKG_ROOT. (Closes: #910685).
Checksums-Sha1:
 3b3c6a4261a3798cc8a98041eba6998cc5765155 8649 glibc_2.30-5.dsc
 b0a42a939acd662ca2991e725644c4cd1d03ab76 847904 glibc_2.30-5.debian.tar.xz
 878760868cee957900b0b17fe9b7003e9f8c40dc 7622 glibc_2.30-5_source.buildinfo
Checksums-Sha256:
 4b078d541ec8066688d3705d7c967850d3f3fb50dda75ba9ea0e3de9e3c73d25 8649 
glibc_2.30-5.dsc
 ec4d7fc611721314fa3f26a16a2f59a740f6fa27d2c5a2d06229ad33d306f7b5 847904 
glibc_2.30-5.debian.tar.xz
 c9253a39b35cf4ec0ad497f6f1b3840f1eb3af0e7232335985513d08b58db01e 7622 
glibc_2.30-5_source.buildinfo
Files:
 c514204efe096f2b1aac6bbd2776e22f 8649 libs required glibc_2.30-5.dsc
 7ac32873dcaa8d1ecd4ab1acbb032267 847904 libs required 
glibc_2.30-5.debian.tar.xz
 2ebc279f84f54591a5750a03301b99eb 7622 libs required 
glibc_2.30-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU

Bug#955270: marked as done (hurd: fails to update file mtime)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#955270: fixed in glibc 2.30-5
has caused the Debian Bug report #955270,
regarding hurd: fails to update file mtime
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.)


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

I first reported this on the mailing list:
https://lists.debian.org/debian-hurd/2020/03/msg00023.html

Now I logged in on the porterbox (exodar.debian.net) to try and
reproduce, and voilà, I can:

tg@exodar:~$ rm a b
tg@exodar:~$ :>a
tg@exodar:~$ sleep 1
tg@exodar:~$ :>b
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200
tg@exodar:~$ sleep 1
tg@exodar:~$ :>a
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200

For comparison, this is how it looks on GNU/Linux:

tglase@tglase-nb:~ $ rm a b
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>b
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:04.989345171 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:07.001398828 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200

Sub-second timestamps aside, you’ll notice how the first of the
two stat(1) lines updated. This is the common expectation for the
command true, redirected to a file.

Please reassign to the correct package, should I be mistaken.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20191117-486-dbg/Hurd-0.9
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages hurd depends on:
ii  hurd-libs0.3   1:0.9.git20191228-1
ii  libblkid1  2.34-0.1
ii  libc0.32.29-10
ii  libdaemon0 0.14-7
ii  libgcrypt201.8.5-5
ii  liblwip0   2.1.2+dfsg1-6
ii  libncursesw6   6.2-1
ii  libpciaccess0  0.16-1+hurd.1
ii  libtinfo6  6.2-1
ii  libx11-6   2:1.6.9-2
ii  lsb-base   11.1.0
ii  sysv-rc2.96-2.1
ii  xkb-data   2.29-2

Versions of packages hurd recommends:
ii  bf-utf-source  0.08
ii  netdde 0.0.20150828-8

Versions of packages hurd suggests:
pn  hurd-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-5
Done: Aurelien Jarno 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict against libgcc-X-dev versions 

Bug#958674: marked as done (glibc: refactor generation of multilib include symlinks)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#958674: fixed in glibc 2.30-5
has caused the Debian Bug report #958674,
regarding glibc: refactor generation of multilib include symlinks
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.)


-- 
958674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.30-4
Severity: wishlist
Tags: patch
Control: block 798955 by -1

Hi Aurelien,

as you might have noticed, I resumed work on the long-standing multiarch
glibc headers issue. It seems that we're mostly done with prerequisites
now. Most patches with the exception of a qmake one have been filed a
while ago, so it seems like time to move forward a little.

The resulting patch to glibc is not entirely trivial, so I've tried to
split it into more manageable pieces:

 * This bug: Refactor generation of multilib include symlinks. It is
   essentially pulling a pile of duplicated code into a make define. As
   such it can be considered a cleanup patch (net -160 lines) and does
   not affect resulting packages in an observable way. It is readily
   applicable.

 * #798955 will receive an updated patch after applying this one. The
   updated patch is much smaller, which makes it easier to review.

Please don't let this patch sit in the bts for long. Either you like my
approach of splitting the diff and can apply it. Fine. Or you disagree
with it on some level. In that case, I'd like to learn your reason and
have this bug closed and tagged wontfix.

Helmut
diff --minimal -Nru glibc-2.30/debian/changelog glibc-2.30/debian/changelog
--- glibc-2.30/debian/changelog 2020-03-25 13:56:56.0 +0100
+++ glibc-2.30/debian/changelog 2020-04-24 08:02:13.0 +0200
@@ -1,3 +1,10 @@
+glibc (2.30-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Refactor generation of multilib include symlinks. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 24 Apr 2020 08:02:13 +0200
+
 glibc (2.30-4) unstable; urgency=medium
 
   [ Aurelien Jarno ]
diff --minimal -Nru glibc-2.30/debian/rules.d/build.mk 
glibc-2.30/debian/rules.d/build.mk
--- glibc-2.30/debian/rules.d/build.mk  2020-03-25 13:36:06.0 +0100
+++ glibc-2.30/debian/rules.d/build.mk  2020-04-24 08:02:08.0 +0200
@@ -2,6 +2,16 @@
 # PASS_VAR, we need to call all variables as $(call xx,VAR)
 # This little bit of magic makes it possible:
 xx=$(if $($(curpass)_$(1)),$($(curpass)_$(1)),$($(1)))
+define generic_multilib_extra_pkg_install
+set -e; \
+mkdir -p debian/$(1)/usr/include/sys; \
+ln -sf $(DEB_HOST_GNU_TYPE)/bits debian/$(1)/usr/include/; \
+ln -sf $(DEB_HOST_GNU_TYPE)/gnu debian/$(1)/usr/include/; \
+ln -sf $(DEB_HOST_GNU_TYPE)/fpu_control.h debian/$(1)/usr/include/; \
+for i in `ls debian/tmp-libc/usr/include/$(DEB_HOST_GNU_TYPE)/sys`; do \
+   ln -sf ../$(DEB_HOST_GNU_TYPE)/sys/$$i debian/$(1)/usr/include/sys/$$i; 
\
+done
+endef
 
 ifneq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 libc_extra_config_options = $(extra_config_options) 
--disable-sanity-checks \
diff --minimal -Nru glibc-2.30/debian/sysdeps/amd64.mk 
glibc-2.30/debian/sysdeps/amd64.mk
--- glibc-2.30/debian/sysdeps/amd64.mk  2020-03-25 13:36:06.0 +0100
+++ glibc-2.30/debian/sysdeps/amd64.mk  2020-04-24 08:02:08.0 +0200
@@ -20,21 +20,13 @@
 
 define libc6-dev-i386_extra_pkg_install
 
-mkdir -p debian/libc6-dev-i386/usr/include
-ln -sf x86_64-linux-gnu/bits debian/libc6-dev-i386/usr/include/
-ln -sf x86_64-linux-gnu/gnu debian/libc6-dev-i386/usr/include/
-ln -sf x86_64-linux-gnu/fpu_control.h debian/libc6-dev-i386/usr/include/
+$(call generic_multilib_extra_pkg_install,libc6-dev-i386)
 
 mkdir -p debian/libc6-dev-i386/usr/include/x86_64-linux-gnu/gnu
 cp -a debian/tmp-i386/usr/include/gnu/lib-names-32.h \
debian/tmp-i386/usr/include/gnu/stubs-32.h \
debian/libc6-dev-i386/usr/include/x86_64-linux-gnu/gnu
 
-mkdir -p debian/libc6-dev-i386/usr/include/sys
-for i in `ls debian/tmp-libc/usr/include/x86_64-linux-gnu/sys` ; do \
-ln -sf ../x86_64-linux-gnu/sys/$$i 
debian/libc6-dev-i386/usr/include/sys/$$i ; \
-done
-
 endef
 
 define libc6-i386_extra_pkg_install
diff --minimal -Nru glibc-2.30/debian/sysdeps/armel.mk 
glibc-2.30/debian/sysdeps/armel.mk
--- glibc-2.30/debian/sysdeps/armel.mk  2020-03-11 22:13:40.0 +0100
+++ glibc-2.30/debian/sysdeps/armel.mk  2020-04-24 08:02:08.0 +0200
@@ -15,21 +15,13 @@
 #
 #define libc6-dev-armhf_extra_pkg_install
 #
-#mkdir -p debian/libc6-dev-armhf/usr/include
-#ln 

Bug#941174: marked as done (glibc: FTBFS on hppa - new test failures)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#941174: fixed in glibc 2.30-5
has caused the Debian Bug report #941174,
regarding glibc: FTBFS on hppa - new test failures
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.)


-- 
941174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.29-2
Severity: normal

Dear Maintainer,

Since version 2.29-2, glibc fails to build on hppa.  We have the following
test fails:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: nptl/tst-cond21
FAIL: nptl/tst-rwlock19
FAIL: nptl/tst-stackguard1
FAIL: nptl/tst-tls1
FAIL: stdio-common/tst-vfprintf-user-type

These fails are not fully consistent from build to build.  2.29-1 built
successfully.

I did a build outside the buildd and all these tests passed.  One test
failed:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: elf/tst-pldd

dave@mx3210:~/debian/glibc/glibc-2.29$ cat 
./build-tree/hppa-libc/elf/tst-pldd.out
error: xposix_spawn.c:30: posix_spawn to /usr/bin/pldd file failed: No such 
file or directory
error: 1 test failures

It seems like pldd got installed in the wrong place:
mv -f /home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd.new 
/home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd

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.146+ (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)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-5
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict against libgcc-X-dev versions that might need the
 __glibc_has_include macro.
   * debian/patches/any/local-revert-glibc_has_include.diff: drop patch,
 obsolete.
   * debian/control.in/libc: add a Provides: libc6-dbgsym to the libc6-dbg
 package.  Closes: #953654.
   * debian/control.in/libc: qualify the libselinux-dev build-depends with
 .
   * debian/debhelper.in/libc.postinst: drop the code removing
 /etc/ld.so.hwcappkgs, it's not needed anymore since Squeeze.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fixes data race in setting function descriptor during 

Bug#938590: marked as done (sugar-log-activity: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:49:53 +
with message-id 
and subject line Bug#938590: fixed in sugar-log-activity 42-1
has caused the Debian Bug report #938590,
regarding sugar-log-activity: 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.)


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

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: sugar-log-activity
Source-Version: 42-1
Done: =?utf-8?q?El=C3=ADas_Alejandro_A=C3=B1o_Mendoza?= 

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

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

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

Debian distribution maintenance software
pp.
Elías Alejandro Año Mendoza  (supplier of updated 
sugar-log-activity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Apr 2020 06:29:47 -0500
Source: sugar-log-activity
Architecture: source
Version: 42-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Elías Alejandro Año Mendoza 
Closes: 938590
Changes:
 sugar-log-activity (42-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 .
   [ Elías Alejandro ]
   * Extend copyright year
   * Declare compliance with Debian Policy 4.5.0
   * Use debhelper compatibility level 10
   * Build-Depends on python3 modules and dh-python
   * Depends on python3 modules. Closes: #938590
   * Stop rename locale ibo (no longer shipped upstream)
   * Remove lintian override regarding debhelper 9
   * Update lintian override for missing command in desktop file
Checksums-Sha1:
 9b4f90a66fd31d70ed277b60fa199452592b52f4 2115 sugar-log-activity_42-1.dsc
 99802e8392e5113dc

Bug#910685: marked as done (glibc: please support DPKG_ROOT)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#910685: fixed in glibc 2.30-5
has caused the Debian Bug report #910685,
regarding glibc: please support DPKG_ROOT
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.)


-- 
910685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.27-6
Severity: wishlist
Tags: patch
Control: user debian-d...@lists.debian.org
Control: usertag -1 + dpkg-root-support

Hi,

In version 1.18.5, dpkg gained a new way for installing binary packages.
It now supports executing maintainer scripts outside the system it is
operating on. The feature is tracked at
https://wiki.debian.org/Teams/Dpkg/Spec/InstallBootstrap. This is
relevant in two ways:
 * When running debootstrap, ordering postinsts is tricky due to the
   number of dependency loops. By executing them outside the chroot,
   some loops can be broken as utilities of the outer system can be
   used.
 * When creating chroots for foreign architectures, the utilities
   inside such chroots usually cannot be executed at all.

To support this, dpkg now unconditionally exports an environment
variable called DPKG_ROOT. It will point to the installation root with
the trailing slash stripped. That means under normal conditions, it is
empty. Since scripts are normally run under chroot(2) even when passing
--root to dpkg, it is empty in that case as well. Only when explicitly
activating the new mode, the chroot call is skipped and DPKG_ROOT can be
non-empty. It is yet unclear under what conditions this mode should be
enabled, so for the time being the only way to do so is to use
--force-script-chrootless and I stress that this is only meant for
testing.

Currently in Debian sid, there are 57 packages that need to be installed
for the whole Essential:yes set. Most of them Depend (directly or
indirectly) on libc6. Attached patch adds $DPKG_ROOT to a couple of
places of the preinst and postinst of libc6 and that will make 37 of
these 57 install without problems. The patch adds $DPKG_ROOT in more
places than strictly necessary for just installing packages. For example
I didn't test the upgrade scenario. If you like, I can prepare a smaller
patch with only the code paths that I tested.

It would be nice if you could consider applying attached patch because
it is required for the majority of packages in the Essential:yes set to
be successfully installed with the --force-script-chrootless mode.

To test you can run:

dpkg --root "$target" --log "$target/var/log/dpkg.log" 
--force-script-chrootless -i libc6_2.27-6.1_amd64.deb

Thanks!

cheers, josch
diff -Nru glibc-2.27/debian/changelog glibc-2.27/debian/changelog
--- glibc-2.27/debian/changelog 2018-09-04 21:13:02.0 +0200
+++ glibc-2.27/debian/changelog 2018-10-09 06:02:02.0 +0200
@@ -1,3 +1,10 @@
+glibc (2.27-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * support DPKG_ROOT
+
+ -- Johannes 'josch' Schauer   Tue, 09 Oct 2018 06:02:02 
+0200
+
 glibc (2.27-6) unstable; urgency=medium
 
   [ Samuel Thibault ]
diff -Nru glibc-2.27/debian/debhelper.in/libc.postinst 
glibc-2.27/debian/debhelper.in/libc.postinst
--- glibc-2.27/debian/debhelper.in/libc.postinst2018-01-06 
01:49:53.0 +0100
+++ glibc-2.27/debian/debhelper.in/libc.postinst2018-10-09 
06:02:02.0 +0200
@@ -17,14 +17,14 @@
 if [ "$type" = "configure" ]
 then
 # We don't use a registry anymore, remove the old file
-rm -f /etc/ld.so.hwcappkgs
+rm -f "$DPKG_ROOT/etc/ld.so.hwcappkgs"
  
 # /etc/ld.so.nohwcap code:
 __NOHWCAP__
 
 # Load debconf module if available
-if [ -f /usr/share/debconf/confmodule ] ; then
-   . /usr/share/debconf/confmodule
+if [ -f "$DPKG_ROOT/usr/share/debconf/confmodule" ] ; then
+   . "$DPKG_ROOT/usr/share/debconf/confmodule"
 fi
 
 if [ -n "$preversion" ] && [ -x "$(which ischroot)" ] && ! ischroot; then
@@ -41,7 +41,7 @@
__NSS_CHECK__
if [ -n "$services" ]; then
 
-   if [ -f /usr/share/debconf/confmodule ] ; then
+   if [ -f "$DPKG_ROOT/usr/share/debconf/confmodule" ] ; then
db_version 2.0
db_input critical libraries/restart-without-asking || true
db_go || true
@@ -116,7 +116,7 @@
done
echo
if [ -n "$failed" ]; then
-   if [ -f /usr/share/debconf/confmodule ] ; then
+   i

Bug#945002: marked as done (squid should use /run/squid.pid)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:38:17 +
with message-id 
and subject line Bug#932593: fixed in squid 4.11-3
has caused the Debian Bug report #932593,
regarding squid should use /run/squid.pid
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.)


-- 
932593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u2
Severity: normal

Dear Maintainer,

On a Debian Buster system, I've installed the Squid package. It doesn't
start on every boot. On my system, the /var directory is on a separate
partition, mounted at boot. I've updated the squid.service to add a
dependency on this /var mount (see also #932593) :

$ diff  -u /lib/systemd/system/squid.service
/etc/systemd/system/squid.service
--- /lib/systemd/system/squid.service   2019-02-19 06:29:20.0 +0100
+++ /etc/systemd/system/squid.service   2019-09-06 11:22:00.385894559 +0200
@@ -8,7 +8,8 @@
 [Unit]
 Description=Squid Web Proxy Server
 Documentation=man:squid(8)
-After=network.target network-online.target nss-lookup.target
+Requires=var.mount network.target network-online.target nss-lookup.target
+After=   var.mount network.target network-online.target nss-lookup.target

 [Service]
 Type=forking


But even with this modification, the squid.service fails at boot :

# systemctl status squid --no-pager -l
● squid.service - Squid Web Proxy Server
   Loaded: loaded (/etc/systemd/system/squid.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Mon 2019-11-18 09:30:26 CET; 46min 
ago
 Docs: man:squid(8)
  Process: 431 ExecStartPre=/usr/sbin/squid --foreground -z (code=exited, 
status=255/EXCEPTION)

nov. 18 09:30:26 Deve2m squid[431]: WARNING: Cannot write log file: 
/var/log/squid/cache.log
nov. 18 09:30:26 Deve2m squid[431]: /var/log/squid/cache.log: No such file or 
directory
nov. 18 09:30:26 Deve2m squid[431]:  messages will be sent to 'stderr'.
nov. 18 09:30:26 Deve2m squid[431]: 2019/11/18 09:30:26| FATAL: Squid is 
already running: Found fresh instance PID file (/var/run/squid.pid) with PID 541
nov. 18 09:30:26 Deve2m squid[431]: exception location: Instance.cc(121) 
ThrowIfAlreadyRunningWith
nov. 18 09:30:26 Deve2m systemd[1]: squid.service: Control process exited, 
code=exited, status=255/EXCEPTION
nov. 18 09:30:26 Deve2m systemd[1]: squid.service: Failed with result 
'exit-code'.
nov. 18 09:30:26 Deve2m systemd[1]: Failed to start Squid Web Proxy Server.
nov. 18 09:30:27 Deve2m systemd[1]: squid.service: Unit cannot be reloaded 
because it is inactive.
nov. 18 09:30:28 Deve2m systemd[1]: squid.service: Unit cannot be reloaded 
because it is inactive.

When looking at the journal of var.mount and squid units, I can see that
SystemD seems to try squid before var.mount is up :


# journalctl -b -u squid.service -u var.mount -o short-precise --no-pager -l
-- Logs begin at Mon 2019-11-18 09:30:25 CET, end at Mon 2019-11-18 10:17:33 
CET. --
nov. 18 09:30:26.295333 Deve2m squid[431]: WARNING: Cannot write log file: 
/var/log/squid/cache.log
nov. 18 09:30:26.296148 Deve2m squid[431]: /var/log/squid/cache.log: No such 
file or directory
nov. 18 09:30:26.297190 Deve2m squid[431]:  messages will be sent to 
'stderr'.
nov. 18 09:30:26.304463 Deve2m squid[431]: 2019/11/18 09:30:26| FATAL: Squid is 
already running: Found fresh instance PID file (/var/run/squid.pid) with PID 541
nov. 18 09:30:26.304463 Deve2m squid[431]: exception location: 
Instance.cc(121) ThrowIfAlreadyRunningWith
nov. 18 09:30:26.324920 Deve2m systemd[1]: squid.service: Control process 
exited, code=exited, status=255/EXCEPTION
nov. 18 09:30:26.324973 Deve2m systemd[1]: squid.service: Failed with result 
'exit-code'.
nov. 18 09:30:26.325294 Deve2m systemd[1]: Failed to start Squid Web Proxy 
Server.
nov. 18 09:30:26.696846 Deve2m systemd[1]: var.mount: Directory /var to mount 
over is not empty, mounting anyway.
nov. 18 09:30:26.697820 Deve2m systemd[1]: Mounting /var...
nov. 18 09:30:26.733644 Deve2m systemd[1]: Mounted /var.
nov. 18 09:30:27.432368 Deve2m systemd[1]: squid.service: Unit cannot be 
reloaded because it is inactive.
nov. 18 09:30:28.177452 Deve2m systemd[1]: squid.service: Unit cannot be 
reloaded because it is inactive.



Note that starting the squid service once the whole system has booted works.


I had this strange behaviour on Debian 10.1 and tried also recent 10.2, with
the same result.


With regards,
Fred.

-- Package-specific info:

-- System Information:
Debian Release: 10.2
  APT

Bug#932593: marked as done (squid should use /run/squid.pid)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 21:38:17 +
with message-id 
and subject line Bug#932593: fixed in squid 4.11-3
has caused the Debian Bug report #932593,
regarding squid should use /run/squid.pid
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.)


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

Dear Maintainer,

Squid reproducibly fails to start in system boot. Systemd calls Squid before 
local file systems are up. Therefore Squid
does not find its cache directory under "/srv". Boot messages:

[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started udev Kernel Device Manager.
 Starting Network Service...
 Starting Squid Web Proxy Server...
[  OK  ] Started Network Service.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Found device /dev/mmcblk0p3.
[  OK  ] Found device /dev/mmcblk0p1.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-srv.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-export.
[  OK  ] Found device Samsung_SSD_850_EVO_500GB HDD-Swap.
[  OK  ] Reached target Sound Card.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
 Activating swap /dev/disk/by-label/HDD-Swap...
 Starting File System Check…ev/disk/by-label/HDD-export...
 Starting File System Check… /dev/disk/by-label/HDD-srv...
 Starting File System Check on /dev/mmcblk0p1...
 Starting File System Check on /dev/mmcblk0p3...
[  OK  ] Activated swap /dev/disk/by-label/HDD-Swap.
[FAILED] Failed to start Squid Web Proxy Server.
See 'systemctl status squid.service' for details.
[  OK  ] Started File System Check …/dev/disk/by-label/HDD-export.
[  OK  ] Started File System Check on /dev/mmcblk0p1.
[  OK  ] Started File System Check on /dev/mmcblk0p3.
[  OK  ] Started File System Check on /dev/disk/by-label/HDD-srv.
 Mounting /srv...
[  OK  ] Started File System Check Daemon to report status.

Re-installation of Squid didn't help.
I added "local-fs.target" to the squid system unit file (After-clause) without 
success.
After my system is completely up, Squid can be started successfully and is 
working as expected.
I removed "/etc/init.d/squid" without any effect (Squid does not start in boot 
and can be started
manually afterwards).
Other services that depend upon local filesystems and networking (e.g. Samba, 
NFSv4) are started after
the service they depend upon are ready.


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.0-5-armmp-lpae (SMP w/2 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)
LSM: AppArmor: enabled

Versions of packages squid depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcom-err2  1.44.5-1
ii  libdb5.3 5.3.28+dfsg1-0.5
ii  libdbi-perl  1.642-1+b1
ii  libecap3 1.0.1-3.2
ii  libexpat12.2.6-2
ii  libgcc1  1:8.3.0-6
ii  libgnutls30  3.6.7-4
ii  libgssapi-krb5-2 1.17-3
ii  libkrb5-31.17-3
ii  libldap-2.4-22.4.47+dfsg-3
ii  libltdl7 2.4.6-9
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnettle6   3.4.1-1
ii  libpam0g 1.3.1-5
ii  libsasl2-2   2.1.27+dfsg-1
ii  libstdc++6   8.3.0-6
ii  libxml2  2.9.4+dfsg1-7+b3
ii  logrotate3.14.0-4
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  squid-common 4.6-1

Versions of packages squid recommends:
ii  ca-certificates  20190110
ii  libcap2-bin  1:2.25-2

Versions of packages squid suggests:
ii  resolvconf   1.79
ii  smbclient2:4.9.5+dfsg-5
ii  squid-cgi4.6-1
pn  squid-purge  
pn  squidclient  
pn  ufw  
pn  winbind  

-- Configuration Files:
/etc/init.d/squid [Errno 2] No such file or directory: '/etc/init.d/squid'
/etc/squid/squid.conf changed [not included]

-- no debconf information

Regards,

Tilmann Boess
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 4.11-3
Done: Luigi Gangitano 

We believe that the bug you reported is fixed in the latest version of
squid, which is due 

Bug#959691: marked as done (RM: tahoe-lafs -- ROM; python2 only no python3 support is available from upstream)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:51:16 +
with message-id 
and subject line Bug#959691: Removed package(s) from unstable
has caused the Debian Bug report #959691,
regarding RM: tahoe-lafs -- ROM; python2 only no python3 support is available 
from upstream
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.)


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

Package: ftp.debian.org
Severity: normal


Requesting the removal of this package as suggested in [1]. Currently
there is no support of Python3 and package is python2 only. Upstream is
working on Python3 package but there is no clear ETA yet on when it will
be ready. I will reintroduce the package once the usptream ports it to
python3.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938622

Cheers,
Vasudev
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

tahoe-lafs |   1.12.1-5 | source, all

--- Reason ---
ROM; python2 only no python3 support is available from upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959691

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

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

Bug#959736: marked as done (RM: reclass -- RoQA; Depends on Python 2, no reverse deps)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:52:50 +
with message-id 
and subject line Bug#959736: Removed package(s) from unstable
has caused the Debian Bug report #959736,
regarding RM: reclass -- RoQA; Depends on Python 2, no reverse deps
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.)


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

Please remove reclass. It depends on Python 2, no port to Py3
is planned (#938340) and there are no remaining rdeps.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-reclass |  1.4.1-3.1 | all
   reclass |  1.4.1-3.1 | source, all

--- Reason ---
RoQA; Depends on Python 2, no reverse deps
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959736

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

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

Bug#959686: marked as done (RM: python-bloomfilter)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:50:57 +
with message-id 
and subject line Bug#959686: Removed package(s) from unstable
has caused the Debian Bug report #959686,
regarding RM: python-bloomfilter
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.)


-- 
959686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Usertags: rm
User: release.debian@packages.debian.org

Dear FTP master.

Please remove python-bloomfilter from the Debian Archive.

Upstream has no had activity since last 6 years and no python3 support
exists on it. This should close #937615


Thanks,

Dererk

-- 
BOFH excuse #154:

You can tune a file system, but you can't tune a fish (from most tunefs man 
pages)






signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-bloomfilter |  2.0-2 | source, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-bloomfilter |   2.0-2+b1 | amd64

--- Reason ---
ROM; python2 only, no python3 planned
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959686

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

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

Bug#956902: marked as done (python-reclass: Depends on cruft package python-yaml)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:52:54 +
with message-id 
and subject line Bug#959736: Removed package(s) from unstable
has caused the Debian Bug report #956902,
regarding python-reclass: Depends on cruft package python-yaml
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.)


-- 
956902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-reclass
Version: 1.4.1-3.1
Severity: serious

Python-yaml is now NBS and will be removed from Testing at some point.
Python-reclass either needs to drop the python-yaml depends (I haven't
investigated if this is feasible) or move to python3 and depend on
python3-yaml.

I'm aware based on the discussion in #938340 that there is a preference
not to remove reclass entirely to support boxer, but removing it from
Testing won't affect that.

Scott K
--- End Message ---
--- Begin Message ---
Version: 1.4.1-3.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#920414: marked as done (tahoe-lafs: Please package new upstream version 1.13.0)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:51:20 +
with message-id 
and subject line Bug#959691: Removed package(s) from unstable
has caused the Debian Bug report #920414,
regarding tahoe-lafs: Please package new upstream version 1.13.0
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.)


-- 
920414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tahoe-lafs
Version: 1.12.1-5
Severity: wishlist

Dear Maintainer,

I've noticed that a few months ago upstream released a new version of
the package:

https://tahoe-lafs.org/pipermail/tahoe-dev/2018-August/009923.html

I realize that there would be very little time, but do you think it
would be possible to have it in debian buster before the freeze?

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.12.1-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#954458: marked as done (reclass: diff for NMU version 1.4.1-3.1)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:52:54 +
with message-id 
and subject line Bug#959736: Removed package(s) from unstable
has caused the Debian Bug report #954458,
regarding reclass: diff for NMU version 1.4.1-3.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.)


-- 
954458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reclass
Version: 1.4.1-3
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for reclass (versioned as 1.4.1-3.1). The diff
is attached to this message.

Regards.

diff -Nru reclass-1.4.1/debian/changelog reclass-1.4.1/debian/changelog
--- reclass-1.4.1/debian/changelog	2017-03-11 04:14:58.0 -0500
+++ reclass-1.4.1/debian/changelog	2020-03-21 18:01:01.0 -0400
@@ -1,3 +1,10 @@
+reclass (1.4.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop reclass-doc, to reduce reverse dependencies of python-sphinx
+
+ -- Sandro Tosi   Sat, 21 Mar 2020 18:01:01 -0400
+
 reclass (1.4.1-3) unstable; urgency=medium
 
   * Revert d/compat and standards update to allow stretch migration
diff -Nru reclass-1.4.1/debian/control reclass-1.4.1/debian/control
--- reclass-1.4.1/debian/control	2017-03-11 04:14:21.0 -0500
+++ reclass-1.4.1/debian/control	2020-03-21 17:58:44.0 -0400
@@ -6,7 +6,6 @@
 Build-Depends: debhelper (>= 8.9.7),
python,
python-setuptools,
-   python-sphinx,
python-yaml
 Standards-Version: 3.9.6
 XS-Python-Version: all
@@ -63,14 +62,3 @@
  allowed, well-defined, and encouraged), and piece together your infrastructure
  from smaller bits, eliminating redundancy and exposing all important
  parameters to a single location, logically organised.
-
-Package: reclass-doc
-Architecture: all
-Section: doc
-Depends: ${misc:Depends}, ${sphinxdoc:Depends}
-Description: reclass documentation
- reclass is an "external node classifier" (ENC) as can be used with automation
- tools, such as Puppet, Salt, and Ansible. It is also a stand-alone tool for
- merging data sources recursively.
- .
- This package provides the documentation for reclass.
diff -Nru reclass-1.4.1/debian/reclass-doc.docs reclass-1.4.1/debian/reclass-doc.docs
--- reclass-1.4.1/debian/reclass-doc.docs	2017-03-10 02:47:18.0 -0500
+++ reclass-1.4.1/debian/reclass-doc.docs	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-doc/build/html
diff -Nru reclass-1.4.1/debian/reclass.manpages reclass-1.4.1/debian/reclass.manpages
--- reclass-1.4.1/debian/reclass.manpages	2017-03-10 02:47:18.0 -0500
+++ reclass-1.4.1/debian/reclass.manpages	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-doc/build/man/reclass.1
diff -Nru reclass-1.4.1/debian/rules reclass-1.4.1/debian/rules
--- reclass-1.4.1/debian/rules	2017-03-10 05:26:15.0 -0500
+++ reclass-1.4.1/debian/rules	2020-03-21 17:59:19.0 -0400
@@ -4,17 +4,11 @@
 #export DH_VERBOSE=1
 
 DH_BUILDSYSTEM_OPTION=--buildsystem=python_distutils
-DH_OPTIONS=--with python2,sphinxdoc $(DH_BUILDSYSTEM_OPTION)
+DH_OPTIONS=--with python2 $(DH_BUILDSYSTEM_OPTION)
 
 %:
 	dh $@ $(DH_OPTIONS)
 
-override_dh_sphinxdoc:
-	dh_sphinxdoc || :
-
-override_dh_auto_build:
-	PYTHONPATH=.. $(MAKE) -C doc man html
-
 override_dh_install:
 	dh_install
 	mv debian/tmp/usr/bin/reclass-* debian/reclass/usr/share/reclass
@@ -24,4 +18,3 @@
 
 override_dh_clean:
 	dh_clean -O$(DH_BUILDSYSTEM_OPTION)
-	$(MAKE) docsclean
--- End Message ---
--- Begin Message ---
Version: 1.4.1-3.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#938340: marked as done (reclass: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:52:54 +
with message-id 
and subject line Bug#959736: Removed package(s) from unstable
has caused the Debian Bug report #938340,
regarding reclass: 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.)


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

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 ---
Version: 1.4.1-3.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#938622: marked as done (tahoe-lafs: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:51:20 +
with message-id 
and subject line Bug#959691: Removed package(s) from unstable
has caused the Debian Bug report #938622,
regarding tahoe-lafs: 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.)


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

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 ---
Version: 1.12.1-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#959710: marked as done (RM: scamp [armel armhf i386 mipsel] -- RoM; FTBFS (32 no longer supported))

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:51:36 +
with message-id 
and subject line Bug#959710: Removed package(s) from unstable
has caused the Debian Bug report #959710,
regarding RM: scamp [armel armhf i386 mipsel] -- RoM; FTBFS (32 no longer 
supported)
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.)


-- 
959710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Control: block 959540 by -1

Please remove the binary packages of scamp from armel, armhf, i386, and
mipsel. 32 bit archs are no longer supported upstream and lead to
errornous packages (failing in the build time test).

This would allow to migrate the new version of the package to testing.

The package has no reverse dependencies.

Thank you, best regards

Ole
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 scamp | 2.0.4+dfsg-1+b2 | armel, armhf, i386, mipsel

--- Reason ---
RoM; FTBFS (32 no longer supported)
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/959710

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

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

Bug#937615: marked as done (python-bloomfilter: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:51:00 +
with message-id 
and subject line Bug#959686: Removed package(s) from unstable
has caused the Debian Bug report #937615,
regarding python-bloomfilter: 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.)


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

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 ---
Version: 2.0-2+rm

Dear submitter,

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

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

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

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

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

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

Bug#958735: marked as done (dnstwist: autopkgtest needs-internet)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 20:33:51 +
with message-id 
and subject line Bug#958735: fixed in dnstwist 0~20200424-1
has caused the Debian Bug report #958735,
regarding dnstwist: autopkgtest needs-internet
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.)


-- 
958735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnstwist
Version: 0~20190706+ds1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: needs-internet

Dear maintainer(s),

With a recent upload of dnstwist you added an autopkgtest, great.
However, because of the failure on arm64 I noticed that your test
requires unlimited internet access. We recently added the needs-internet
restriction to the autopkgtest definition [1], you should add it to your
autopkgtest declaration.

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

Paul

[1] https://qa.debian.org/excuses.php?package=dnstwist

https://ci.debian.net/data/autopkgtest/testing/arm64/d/dnstwist/4884265/log.gz

autopkgtest [21:14:52]: test testdebiandomain: [---
Found problems in the following lines:


Line 12: Bitsquatting   dabian.org   NS:dns27.hichina.com
MX:mxdomain.qq.com SMTP:"newxmmxsza53.qq.com MX QQ Mail Server."
Line 19: Insertion  derbian.org  NS:ns-108-c.gandi.net
MX:ALT1.ASPMX.L.GOOGLE.COM SMTP:"mx.google.com ESMTP g9si4331087plq.234
- gsmtp"


Dumping full output for further debugging purposes:


$ dnstwist --ssdeep --registered --mxcheck --geoip --banners debian.org
 _   __ _
  __| |_ __  ___| |___  _(_)___| |_
 / _` | '_ \/ __| __\ \ /\ / / / __| __|
| (_| | | | \__ \ |_ \ V  V /| \__ \ |_
 \__,_|_| |_|___/\__| \_/\_/ |_|___/\__| {20190706}

Fetching content from: http://debian.org ... 200 OK (14.4 Kbytes)
Processing 2489 domain variants ..16%.35%.54%..81%.99%.. 22 hits (0%)

Original*  debian.org   128.31.0.62/United States 2001:4f8:1:c::15
NS:dns4.easydns.info MX:mailly.debian.org HTTP:"Apache"
SMTP:"mailly.debian.org ESMTP Exim 4.92 Wed, 08 Apr 2020 21:14:54 +"
SSDEEP:100%
Bitsquatting   febian.org   184.168.131.241/United States
NS:ns75.domaincontrol.com HTTP:"nginx/1.12.2"
Bitsquatting   dabian.org   NS:dns27.hichina.com MX:mxdomain.qq.com
SMTP:"newxmmxsza53.qq.com MX QQ Mail Server."
Bitsquatting   dubian.org   119.146.223.181/China NS:dns7.hichina.com
MX:mxn.mxhichina.com SMTP:"mx1.aliyun-inc.com MX AliMail Server"
Bitsquatting   debaan.org   185.135.241.4/Netherlands
NS:ns1.hosting2go.nl SPYING-MX:debaan.orgHTTP:"Apache"
SMTP:"server4.hosting2go.nl ESMTP"
Homoglyph  diebian.org  119.28.189.104/Hong Kong NS:dns10.hichina.com
Homoglyph  deblan.org   82.237.165.150/France NS:ns-154-c.gandi.net
MX:mail.deblan.org HTTP:"nginx" SMTP:"deblan.fr ESMTP mail.deblan.org"
Homoglyph  deb1an.org   107.181.167.155/United States
NS:ns1.shellhosts.com HTTP:"Apache"
Homoglyph  debiam.org   217.70.184.50/France NS:a.dns.gandi.net
HTTP:"nginx"
Insertion  derbian.org  NS:ns-108-c.gandi.net
MX:ALT1.ASPMX.L.GOOGLE.COM SMTP:"mx.google.com ESMTP g9si4331087plq.234
- gsmtp"
Omission   debin.org104.27.160.17/United States
2606:4700:3030::681b:a011 NS:ajay.ns.cloudflare.com
SPYING-MX:mxa.mailgun.orgHTTP:"cloudflare" SMTP:"ak47 ESMTP ready"
Omission   deian.org75.126.100.29/United States
NS:ns1dhl.name.com MX:mx3.name.com HTTP:"nginx"
Omission   debia.org3.234.181.234/United States
NS:ns1.namebrightdns.com HTTP:"Microsoft-IIS/8.5"
Replacementdevian.org   64.98.145.30/Canada NS:ns1.hover.com
MX:mx.hover.com.cust.hostedemail.com HTTP:"nginx/1.6.2 + Phusion
Passenger 4.0.53" SMTP:"450 4.7.1 Client host rejected: cannot f"
Replacementdebuan.org   146.148.34.125/United States
NS:ns4.dnsauthority.com SPYING-MX:mail.hope-mail.comHTTP:"Apache"
SMTP:"ip-10-130-0-34 ESMTP Haraka/2.8.20 ready"
Replacementdegian.org   3.112.75.141/Japan NS:ns7.alidns.com
Replacementdenian.org   139.224.7.30/China NS:n3381.ns.yunjiasu.com
SPYING-MX:mxbiz1.qq.comHTTP:"Beaver" SMTP:"bizmx5.qq.com MX QQ Mail Server"
Replacementxebian.org   51.77.251.195/France NS:ns-211-b.gandi.net
MX:fb.mail.gandi.net HTTP:"Cherokee/1.2.104 (Debian)"
SMTP:"fb.mail.gandi.net ESMTP Postfix"
Subdomain  de.bian.org  176.221.45.101/Germany 2a00:1158:300::612
HTTP:"Apache/2.4.41"
Transposition  edb

Bug#946779: marked as done (buster-pu: package logrotate/3.14.0-4)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 21:40:21 +0200
with message-id 

and subject line Re: Bug#946779: buster-pu: package logrotate/3.14.0-4
has caused the Debian Bug report #946779,
regarding buster-pu: package logrotate/3.14.0-4
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.)


-- 
946779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

With version 3.14.0 [1] logrotate split the configuration for btmp and
wtmp into separate configuration files.
There are bug reports regarding this issue: 945932, 928516, 922045.

Package version 3.14.0-4+deb10u1 adds a NEWS entry about this change.

The packaging can be found at [2].
An upload can be found at [3].


<> debdiff
diff -Nru logrotate-3.14.0/debian/changelog logrotate-3.14.0/debian/changelog
--- logrotate-3.14.0/debian/changelog   2018-08-29 00:21:11.0 +0200
+++ logrotate-3.14.0/debian/changelog   2019-12-15 18:53:33.0 +0100
@@ -1,3 +1,9 @@
+logrotate (3.14.0-4+deb10u1) stable; urgency=medium
+
+  * d/NEWS: add entry about (b|w)tmp config split
+
+ -- Christian Göttsche   Sun, 15 Dec 2019
18:53:33 +0100
+
 logrotate (3.14.0-4) unstable; urgency=medium

   * d/control:
diff -Nru logrotate-3.14.0/debian/NEWS logrotate-3.14.0/debian/NEWS
--- logrotate-3.14.0/debian/NEWS2018-08-29 00:21:11.0 +0200
+++ logrotate-3.14.0/debian/NEWS2019-12-15 18:53:33.0 +0100
@@ -1,3 +1,17 @@
+logrotate (3.14.0-1) unstable; urgency=medium
+
+  The shipped configurations for "/var/log/btmp" and "/var/log/wtmp" have
+  been split from the main configuration file (/etc/logrotate.conf) into
+  separate standalone files (/etc/logrotate.d/btmp respectively
+  /etc/logrotate.d/wtmp).
+
+  If you had modified /etc/logrotate.conf in this regard, make sure
+  to re-adjust the two new files to your needs and drop any references to
+  (b|w)tmp from the main file, to avoid logrotate skip rotation due to a
+  duplicate definition.
+
+ -- Christian Göttsche   Sun, 15 Dec 2019
18:49:00 +0200
+
 logrotate (3.8.0-1) experimental; urgency=low

   Please note that this update changes the behaviour of logrotate:
<---> debdiff end


Best regards,
 Christian Göttsche

[1] https://github.com/logrotate/logrotate/blob/master/ChangeLog.md
[2] https://salsa.debian.org/debian/logrotate/tree/stable-buster
[3] https://mentors.debian.net/package/logrotate
--- End Message ---
--- Begin Message ---
Closed via adding a section to release notes, see #959191--- End Message ---

Bug#959393: marked as done (ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not found)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 19:33:40 +
with message-id 
and subject line Bug#959393: fixed in ruby2.7 2.7.0-7
has caused the Debian Bug report #959393,
regarding ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not 
found
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.)


-- 
959393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby2.7, diaspora-installer
Control: found -1 ruby2.7/2.7.0-6
Control: found -1 diaspora-installer/0.7.6.1+debian1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ruby2.7 the autopkgtest of diaspora-installer
fails in testing when that autopkgtest is run with the binary packages
of ruby2.7 from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
ruby2.7from testing2.7.0-6
diaspora-installer from testing0.7.6.1+debian1
all others from testingfrom testing

I copied some of the output at the bottom of this report. This change
makes diaspora-installer non-installable.

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

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ruby2.7

https://ci.debian.net/data/autopkgtest/testing/amd64/d/diaspora-installer/5223437/log.gz

Setting up diaspora-installer (0.7.6.1+debian1) ...
Download diaspora tarball version 0.7.6.0 from github.com...
--2020-04-30 19:13:56--
https://github.com/diaspora/diaspora/archive/v0.7.6.0.tar.gz
Resolving github.com (github.com)... 192.30.255.113
Connecting to github.com (github.com)|192.30.255.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.6.0
[following]
--2020-04-30 19:13:56--
https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.6.0
Resolving codeload.github.com (codeload.github.com)... 192.30.255.120
Connecting to codeload.github.com
(codeload.github.com)|192.30.255.120|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘/var/cache/diaspora-installer/diaspora-0.7.6.0.tar.gz’


  /var/cach [<=> ]   0  --.-KB/s

 /var/cache [ <=>]   1.30M  6.40MB/s

/var/cache/diaspora [  <=>   ]   2.71M  7.50MB/sin
0.4s

2020-04-30 19:13:57 (7.50 MB/s) -
‘/var/cache/diaspora-installer/diaspora-0.7.6.0.tar.gz’ saved [2845165]

Checking integrity of download...
/var/cache/diaspora-installer/diaspora-0.7.6.0.tar.gz: OK
Extracting files...
Copying files to /usr/share/diaspora...
diaspora archive to copy: diaspora-0.7.6.0
Copying source tarball to /var/lib/diaspora/public...
Setting up environment varibales...
Using /etc/diaspora.conf...
export DB_NAME=diaspora_production
Using system bundler...
Installing gems with rubygems ...
sh: 1: bundle: not found
dpkg: error processing package diaspora-installer (--configure):
 installed diaspora-installer package post-installation script
subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 autopkgtest-satdep depends on diaspora-installer; however:
  Package diaspora-installer is not configured yet.

dpkg: error processing package autopkgtest-satdep (--configure):
 dependency problems - leaving unconfigured



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby2.7
Source-Version: 2.7.0-7
Done: Lucas Kanashiro 

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated ruby2.7 package)

(This message was generated auto

Bug#884987: marked as done (etckeeper: /etc/cron.daily/etckeeper reports "abort: path contains illegal component: .hg/undo.dirstate")

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:49:05 +
with message-id 
and subject line Bug#884987: fixed in etckeeper 1.18.14-1
has caused the Debian Bug report #884987,
regarding etckeeper: /etc/cron.daily/etckeeper reports "abort: path contains 
illegal component: .hg/undo.dirstate"
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.)


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

I get a daily cron email with the following warnings/errors:

  /etc/cron.daily/etckeeper:
  abort: path contains illegal component: .hg/undo.dirstate
  abort: path contains illegal component: .hg/undo.backup.dirstate

It seems not to be a Debian-specific problem:



But the patch there doesn't apply to the Debian
/etc/etckeeper/pre-commit.d/20warn-problem-files

-Sanjoy

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

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

Versions of packages etckeeper depends on:
ii  darcs  2.12.5-1
ii  debconf [debconf-2.0]  1.5.65
ii  git1:2.15.1-1
ii  mercurial  4.4.1-1

Versions of packages etckeeper recommends:
ii  cron [cron-daemon]  3.0pl1-128.1

Versions of packages etckeeper suggests:
ii  sudo  1.8.21p2-2

-- Configuration Files:
/etc/etckeeper/etckeeper.conf changed:
VCS="hg"
GIT_COMMIT_OPTIONS=""
HG_COMMIT_OPTIONS=""
BZR_COMMIT_OPTIONS=""
DARCS_COMMIT_OPTIONS="-a"
HIGHLEVEL_PACKAGE_MANAGER=apt
LOWLEVEL_PACKAGE_MANAGER=dpkg
PUSH_REMOTE=""


-- debconf information:
  etckeeper/purge: true
--- End Message ---
--- Begin Message ---
Source: etckeeper
Source-Version: 1.18.14-1
Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= 

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated etckeeper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 13:32:38 -0400
Source: etckeeper
Architecture: source
Version: 1.18.14-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Closes: 811180 884987 921447 928177
Changes:
 etckeeper (1.18.14-1) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * New upstream release (Closes: #884987)
   * debian/patches/fix-sh-syntax.diff: drop, merged in 1.18.13
   * merge NMU 1.18.10-1.1 I forgot, below
 .
   [ Mattia Rizzolo ]
   * Import patches from Ubuntu (Closes: #928177):
 + Use a UTF-8 encoding, to ensure stable sorting.
 + Add a Breezy plugin, using Python3.
   * Replace bzr dependencies with brz (bzr is now a transitional package).
   * d/control:
 + Bump Standards-Version to 4.4.1, no changes needed.
 + Set Rules-Requires-Root: no.
 + Drop Conflicts against a very old version of bzr.
 + Drop version requirements against very old versions, all satisfied
   in oldoldstable.
 + Bump debhelper compat level to 12.
   * Build using Python3 instead of Python2 (Closes: #811180, #921447)
 (This stops installing the bzr plugin, instead installing the brz one).
Checksums-Sha1:
 c8efad31cdcb036fadf554b7eca74e673a54d916 1590 etckeeper_1.18.14-1.dsc
 911575137d218cc7831b5fbe95ff13934ca6a3fe 93528 etckeeper_1.18.14.orig.tar.gz
 9b8782e0bb72be44fade1bf082b9174de96ec9d0 25036 
etckeeper_1.18.14-1.debian.tar.xz
 673dd54fe6660376dcc119045713826c93949a30 7071 
etckeeper_1.18.14-1_source.buildinfo
Checksums-Sha256:
 23487e5bfe12d93a61137757011db20ff7aabab1972c26837787560fdcd04d06 1590 
etckeeper_1.18.14-1.dsc
 15924673fa3f15e4b172f9f0111a442ed3f0ee99dcf9ad3c5107736ffb

Bug#883145: marked as done (etckeeper: needs port to Python3)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:49:05 +
with message-id 
and subject line Bug#811180: fixed in etckeeper 1.18.14-1
has caused the Debian Bug report #811180,
regarding etckeeper: needs port to Python3
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.)


-- 
811180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:etckeeper
Version: 5.112-1
User: debian-pyt...@lists.debian.org
Usertags: py2-removal

Please port the package to Python3.
--- End Message ---
--- Begin Message ---
Source: etckeeper
Source-Version: 1.18.14-1
Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= 

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated etckeeper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 13:32:38 -0400
Source: etckeeper
Architecture: source
Version: 1.18.14-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Closes: 811180 884987 921447 928177
Changes:
 etckeeper (1.18.14-1) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * New upstream release (Closes: #884987)
   * debian/patches/fix-sh-syntax.diff: drop, merged in 1.18.13
   * merge NMU 1.18.10-1.1 I forgot, below
 .
   [ Mattia Rizzolo ]
   * Import patches from Ubuntu (Closes: #928177):
 + Use a UTF-8 encoding, to ensure stable sorting.
 + Add a Breezy plugin, using Python3.
   * Replace bzr dependencies with brz (bzr is now a transitional package).
   * d/control:
 + Bump Standards-Version to 4.4.1, no changes needed.
 + Set Rules-Requires-Root: no.
 + Drop Conflicts against a very old version of bzr.
 + Drop version requirements against very old versions, all satisfied
   in oldoldstable.
 + Bump debhelper compat level to 12.
   * Build using Python3 instead of Python2 (Closes: #811180, #921447)
 (This stops installing the bzr plugin, instead installing the brz one).
Checksums-Sha1:
 c8efad31cdcb036fadf554b7eca74e673a54d916 1590 etckeeper_1.18.14-1.dsc
 911575137d218cc7831b5fbe95ff13934ca6a3fe 93528 etckeeper_1.18.14.orig.tar.gz
 9b8782e0bb72be44fade1bf082b9174de96ec9d0 25036 
etckeeper_1.18.14-1.debian.tar.xz
 673dd54fe6660376dcc119045713826c93949a30 7071 
etckeeper_1.18.14-1_source.buildinfo
Checksums-Sha256:
 23487e5bfe12d93a61137757011db20ff7aabab1972c26837787560fdcd04d06 1590 
etckeeper_1.18.14-1.dsc
 15924673fa3f15e4b172f9f0111a442ed3f0ee99dcf9ad3c5107736ffb8c1089 93528 
etckeeper_1.18.14.orig.tar.gz
 005bde48231b2e4641fea5690e7887bd77c7b84c56541beb4ca272e1e3d56f47 25036 
etckeeper_1.18.14-1.debian.tar.xz
 8b1d649c46a5e96e523647e23840e759542315ecfb537fe83044fd92731e42e0 7071 
etckeeper_1.18.14-1_source.buildinfo
Files:
 360418a6b124fae0acaee73fae80f6f8 1590 admin optional etckeeper_1.18.14-1.dsc
 16da85e787dccef11fcf32baddf47d79 93528 admin optional 
etckeeper_1.18.14.orig.tar.gz
 55805914b4b81199284d7436e652a67e 25036 admin optional 
etckeeper_1.18.14-1.debian.tar.xz
 e0170b9945bf1b067120cad19041ca44 7071 admin optional 
etckeeper_1.18.14-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCAAxFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl6wXpITHGFuYXJjYXRA
ZGViaWFuLm9yZwAKCRA+od3dsmHZe08sCACveSzKLVCAo9GsAq7PAUuvIUui7qp5
l51neK4Qk/t8Af/wlsvrjproXkVcxaVLJbStRAzGOiu4Ni4UzsDLWURaSWrQ4keK
9fiJIrRikVvDJvuVjwN6PIdUZVnnC8wwO3SVYnRaTLtrZK7hQu05kgDX1GpsUUqF
t0L2heJ0Kb3M3zbOjK9su8dwfLazSMS3eYzSNlMAlISTL3eQM4PQ/3uzBEhiXsOe
VLQ68dd+AbAvjPpM1lk4C5qv4xVr8727PVeYbjchdYATlRAEBL032jvOSdZeu5ve
qdqTMFQe/ng+UDADT2pvM3lTJNZw3XHiLlVQ+rdEndowW/S3WUpHgtP3
=A4m/
-END PGP SIGNATURE End Message ---

Bug#811180: marked as done (etckeeper: Please port it to python 3)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:49:05 +
with message-id 
and subject line Bug#811180: fixed in etckeeper 1.18.14-1
has caused the Debian Bug report #811180,
regarding etckeeper: Please port it to python 3
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.)


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

Package: etckeeper
Version: 1.18.2-1
Severity: wishlist

It would be great if etckeeper could be ported to python version 3, to
reduce the disk footprint of the FreedomBox system.  If is one of the
last few pieces using python version 2 on the FreedomBox.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: etckeeper
Source-Version: 1.18.14-1
Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= 

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated etckeeper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 13:32:38 -0400
Source: etckeeper
Architecture: source
Version: 1.18.14-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Closes: 811180 884987 921447 928177
Changes:
 etckeeper (1.18.14-1) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * New upstream release (Closes: #884987)
   * debian/patches/fix-sh-syntax.diff: drop, merged in 1.18.13
   * merge NMU 1.18.10-1.1 I forgot, below
 .
   [ Mattia Rizzolo ]
   * Import patches from Ubuntu (Closes: #928177):
 + Use a UTF-8 encoding, to ensure stable sorting.
 + Add a Breezy plugin, using Python3.
   * Replace bzr dependencies with brz (bzr is now a transitional package).
   * d/control:
 + Bump Standards-Version to 4.4.1, no changes needed.
 + Set Rules-Requires-Root: no.
 + Drop Conflicts against a very old version of bzr.
 + Drop version requirements against very old versions, all satisfied
   in oldoldstable.
 + Bump debhelper compat level to 12.
   * Build using Python3 instead of Python2 (Closes: #811180, #921447)
 (This stops installing the bzr plugin, instead installing the brz one).
Checksums-Sha1:
 c8efad31cdcb036fadf554b7eca74e673a54d916 1590 etckeeper_1.18.14-1.dsc
 911575137d218cc7831b5fbe95ff13934ca6a3fe 93528 etckeeper_1.18.14.orig.tar.gz
 9b8782e0bb72be44fade1bf082b9174de96ec9d0 25036 
etckeeper_1.18.14-1.debian.tar.xz
 673dd54fe6660376dcc119045713826c93949a30 7071 
etckeeper_1.18.14-1_source.buildinfo
Checksums-Sha256:
 23487e5bfe12d93a61137757011db20ff7aabab1972c26837787560fdcd04d06 1590 
etckeeper_1.18.14-1.dsc
 15924673fa3f15e4b172f9f0111a442ed3f0ee99dcf9ad3c5107736ffb8c1089 93528 
etckeeper_1.18.14.orig.tar.gz
 005bde48231b2e4641fea5690e7887bd77c7b84c56541beb4ca272e1e3d56f47 25036 
etckeeper_1.18.14-1.debian.tar.xz
 8b1d649c46a5e96e523647e23840e759542315ecfb537fe83044fd92731e42e0 7071 
etckeeper_1.18.14-1_source.buildinfo
Files:
 360418a6b124fae0acaee73fae80f6f8 1590 admin optional etckeeper_1.18.14-1.dsc
 16da85e787dccef11fcf32baddf47d79 93528 admin optional 
etckeeper_1.18.14.orig.tar.gz
 55805914b4b81199284d7436e652a67e 25036 admin optional 
etckeeper_1.18.14-1.debian.tar.xz
 e0170b9945bf1b067120cad19041ca44 7071 admin optional 
etckeeper_1.18.14-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCAAxFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl6wXpITHGFuYXJjYXRA
ZGViaWFuLm9yZwAKCRA+od3dsmHZe08sCACveSzKLVCAo9GsAq7PAUuvIUui7qp5
l51neK4Qk/t8Af/wlsvrjproXkVcxaVLJbStRAzGOiu4Ni4UzsDLWURaSWrQ4keK
9fiJIrRikVvDJvuVjwN6PIdUZVnnC8wwO3SVYnRaTLtrZK7hQu05kgDX1GpsUUqF
t0L2heJ0Kb3M3zbOjK9su8dwfLazSMS3eYzSNlMAlISTL3eQM4PQ/3uzBEhiXsOe
VLQ68dd+AbAvjPpM1lk4C5qv4xVr8727PVeYbjchdYATlRAEBL032jvOSdZeu5ve
qdqTMFQe/ng+UDADT2pvM3lTJNZw3XHiLlVQ+rdEndowW/S3WUpHgtP3
=A4m/
-END PGP SIGNATURE End Message ---

Bug#959730: marked as done (libgtk-3-0-dbgsym (3.22.11-1) out of phase with libgtk-3-0 (3.24.5-1))

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 19:21:25 +0100
with message-id <20200504182125.ga165...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#959730: libgtk-3-0-dbgsym (3.22.11-1) out of phase 
with libgtk-3-0 (3.24.5-1)
has caused the Debian Bug report #959730,
regarding libgtk-3-0-dbgsym (3.22.11-1) out of phase with libgtk-3-0 (3.24.5-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.)


-- 
959730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-3-0-dbgsym
Version: 3.22.11-1

Hi,

While investigating a focus stealing bug in Firefox, which uses 
libgtk-3.0, I noticed that the debug symbol package is out of phase with 
the main package, preventing it from being installed:

# apt install libgtk-3-0-dbgsym
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgtk-3-0-dbgsym : Depends: libgtk-3-0 (= 3.22.11-1) but 3.24.5-1 is to be 
installed
E: Unable to correct problems, you have held broken packages.


Please fix.

Thanks,

Alain
--- End Message ---
--- Begin Message ---
On Mon, 04 May 2020 at 19:58:54 +0200, Alain Knaff wrote:
> On 04/05/2020 19:50, Simon McVittie wrote:
> > I would expect to find libgtk-3-0-dbgsym=3.22.11-1 in:
> > 
> >  deb http://deb.debian.org/debian-debug stretch-debug main
> > 
> > but libgtk-3-0-dbgsym=3.24.5-1 in:
> > 
> >  deb http://deb.debian.org/debian-debug buster-debug main
> 
> Indeed, this was the reason. Probably a left over from when I had Debian 9.

Closing the bug, then.

smcv--- End Message ---

Bug#959698: marked as done (tmux: "incompatible server protocol change" does not seem acceptable)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:05:03 +
with message-id 
and subject line Bug#959698: fixed in tmux 3.1b-1
has caused the Debian Bug report #959698,
regarding tmux: "incompatible server protocol change" does not seem acceptable
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.)


-- 
959698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tmux
Version: 3.1-1
Severity: serious

Hi,

on apt upgrade in testing today I was greeted by this NEWS entry from
tmux saying:

  The server protocol was changed in an incompatible manner, we recommend
  that you close any open tmux sessions before proceeding with the upgrade.

I don't think that's acceptable.  Running upgrades inside screen or
tmux is a best practice, so IMO it needs to work, and people need to be
able to re-attach to existing sessions across the upgrade.  And even if
it was acceptable to do this, NEWS.Debian is displayed 1) too late for
the user to do anything about it, 2) in English.

See #683228 for what seems like a similar issue in screen back in the
day.

Cheers,
Julien

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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tmux depends on:
ii  libc6   2.30-4
ii  libevent-2.1-7  2.1.11-stable-1
ii  libtinfo6   6.2-1
ii  libutempter01.1.6-6

tmux recommends no packages.

tmux suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tmux
Source-Version: 3.1b-1
Done: Romain Francoise 

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

Debian distribution maintenance software
pp.
Romain Francoise  (supplier of updated tmux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 19:18:57 +0200
Source: tmux
Architecture: source
Version: 3.1b-1
Distribution: unstable
Urgency: medium
Maintainer: Romain Francoise 
Changed-By: Romain Francoise 
Closes: 959698
Changes:
 tmux (3.1b-1) unstable; urgency=medium
 .
   * New upstream bugfix release.
   * Clarify 3.1~rc1-1 NEWS entry about protocol change (closes: #959698).
Checksums-Sha1:
 f0f68b7a1ce40540c6a9491378484b98eb85bab1 1916 tmux_3.1b-1.dsc
 52ab7bbc8f5c48955b170f2473f9515cc31653b5 561152 tmux_3.1b.orig.tar.gz
 862dca99d0d5e9f1deec711c545146dbbd46315b 12936 tmux_3.1b-1.debian.tar.xz
 62a25da0fe353933c174b7c025264a02a35a087d 5967 tmux_3.1b-1_source.buildinfo
Checksums-Sha256:
 bf9df2cfc91702f2c0b8697b7b6139604e0cbcf0233a4b60e12218e17255edbc 1916 
tmux_3.1b-1.dsc
 d93f351d50af05a75fe6681085670c786d9504a5da2608e481c47cf5e1486db9 561152 
tmux_3.1b.orig.tar.gz
 9363dfa19527673f4601e42aa9412e7f402321cc2e166561394cfd144606c49a 12936 
tmux_3.1b-1.debian.tar.xz
 f0fde9cf5116e46830fbca6329d4beaf6910d16f1c79556951aae24781785a50 5967 
tmux_3.1b-1_source.buildinfo
Files:
 1e7f32fada22ba1bac90e065dfee8eb6 1916 admin optional tmux_3.1b-1.dsc
 2cdacbf06ac4980d3f5312ad23b37f9b 561152 admin optional tmux_3.1b.orig.tar.gz
 373e3de0ed64b0dd9f8fe3204cb46672 12936 admin optional tmux_3.1b-1.debian.tar.xz
 9ee4a58bfc1862ad365fae6d467d8369 5967 admin optional 
tmux_3.1b-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvjSXQsqYfs1+d+QtrRX0NfBfli0FAl6wUBIACgkQrRX0NfBf
li3/9BAAppenFN7yRBe//jXw/A+8USn1daMTp0j38FYOVyARvRVGqtqJPgU86fBd
8Mn9OIJ8+m5ZmSr8yNk8EVki746ayipuF4w65kL+CHSXpE1MbHTp95H3YT4VTb5E
vMGSYRlmW9LPq+VCc8KzWH6ixigU7Ptd60lkp9dZ1CkHmwQJPEcSaYBmRhaGvrv8
QI5PH9uVHSqdm1r7EI7qWt86FLYe/QVDBlPPqeFzkZf7ucW2lPAsZrlA81ocvbLo
eoCQr8+5yh2bwvNuz439EcOkAMh0091aFHnB/PkXQ7bym+T3gFkNEhlkBCOS7ZVV
6dDFQL6QbyM5RLfHpuVWNYRnhyXV2fVVzOEKnZKpr3bcEou7opSt3EWf

Bug#959575: marked as done (neurodebian: FTBFS: (process:15028): WARNING **: 05:07:11.653: Unable to create profile directory (Permission denied) (13))

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 18:04:24 +
with message-id 
and subject line Bug#959575: fixed in neurodebian 0.40.1
has caused the Debian Bug report #959575,
regarding neurodebian: FTBFS: (process:15028): WARNING **: 05:07:11.653: Unable 
to create profile directory (Permission denied) (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.)


-- 
959575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neurodebian
Version: 0.40.0
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
> # wallpaper
> [ ! -d build/wallpaper ] && mkdir -p build/wallpaper
> xcf2png -o build/wallpaper/neurodebian.png artwork/wallpaper_hotbrain.xcf
> # icons
> [ ! -d build/icons ] && mkdir -p build/icons
> inkscape artwork/icon.svg -w 32 -h 32 \
>   -e build/icons/neurodebian.png
> 
> ** (process:15028): WARNING **: 05:07:11.653: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -e
> make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/neurodebian_0.40.0_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: neurodebian
Source-Version: 0.40.1
Done: Yaroslav Halchenko 

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated neurodebian 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 11:07:11 -0400
Source: neurodebian
Architecture: source
Version: 0.40.1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Closes: 959575
Changes:
 neurodebian (0.40.1) unstable; urgency=medium
 .
   * Be compatible with inkscape >= 1.0~rc1 which changed -e into -o.
 (Closes: #959575)
Checksums-Sha1:
 c94f4562399e3f0cd8e84a0217d1f60b8086cf71 2146 neurodebian_0.40.1.dsc
 d9155c819a5df4832e9b8aafb112495e725bd50b 8318160 neurodebian_0.40.1.tar.xz
 8e08a2952a0127209440944fcefb959e1fccf7a5 11424 
neurodebian_0.40.1_source.buildinfo
Checksums-Sha256:
 5412b7badf520e823ae8d5607e4d6d392df1e9d1c74816cba0d1cb6e3e65afee 2146 
neurodebian_0.40.1.dsc
 fb510f5be0987defb70f4a01548fd0e66049a3435a96dfa213b76570d501be91 8318160 
neurodebian_0.40.1.tar.xz
 ca1685a78dda6ce9f08374cde06705eeda007b3bffdb42506cfae5c6fcaded6c 11424 
neurodebian_0.40.1_source.buildinfo
Files:
 1573f8e60718cdda41dad9a36ced0e98 2146 science optional neurodebian_0.40.1.dsc
 6128171e386e76e8a5df7506f0aae44d 8318160 science optional 
neurodebian_0.40.1.tar.xz
 8fafccda429eba501c8d8ffbe1b09099 11424 science optional 
neurodebian_0.40.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAl6wOUoACgkQot4jUGLa
M/qiOw/9G/JpsV4C4H+uIX66aD8NiiWyYX1LRlfRcvzhZZTnSpIvaEGmA9jaqgKQ
Fog8ET5KlO5xce+leg0hFGTbZxF/uf2EPfhyK/eT7Y90P2Rhoh46htpxc8tJFb9r
lL7xCMTzDnK3G7LYW0/FEoHy+YyX63Rta/6PXvTOxP8JjNGV+g43moGzxVi+0qiA
q9qqm/JZQgIyRLmZemVMX0LX+CCcIF6yUnTMZMtQKUm6f2Kj14P9HGo56+cHAhh9
HjTDXSVYKSpbujaRYlmj8Hq5eThh3WMPVX+8lbuO9I8+Ahqse880T5d71bqukoSx
iD8CaPniVuuOxTXbjXg9MrD5h2Ku3L9hM98n5SOJBoCbSSN+LUXR33/67e+KAWOc
iv3c7useBmC2xAehWA9x37T3ILH8RKwaMRx0tATVm3R9HhhTfaofjUYnnFVkdf5x
FVvpOeN2sAu69a/TtWU7eMpUwCU4uzbSxsZm1CPFla6NxAx62jHi9Tt2fmP5VSAW
zvqrPYGQHaaUYkifoZCf5xydCaDvlM0Bu1wRjEptjOGAgPLUAv9Sdo9TozwIuv+q
bZDyD9Q4HlRmGfr1Yu

Bug#956652: marked as done (svgtune: Should we remove this package?)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:50:29 +
with message-id 
and subject line Bug#956652: fixed in svgtune 0.3.0-1
has caused the Debian Bug report #956652,
regarding svgtune: Should we remove this package?
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.)


-- 
956652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: svgtune
Severity: serious
Version: 0.2.0-2
Tags: sid  bullseye
X-Debbugs-CC: y...@debian.org

Dear package svgtune maintainer,

A new upload of src:lxml was just made to drop package python-lxml from Sid.
Since this is also the dependency of svgtune, package svgtune is now
uninstallable in Sid (and Bullseye).

Since there were no upload for svgtune since 2015 and that it upstream also
had no activity since 2015, it might be reasonable for us to clean up the
Debian repository and remove package svgtune from Sid/Bullseye.

I will submit a removal request 21 days later (After May 04, 2020). If you are
to migrate this package to python3 or have any other thoughts, please let me
know *immediately* so that we could properly save this package in time.

Thank you for your work in Debian and looking forward to your reply.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: svgtune
Source-Version: 0.3.0-1
Done: Yaroslav Halchenko 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 13:00:03 -0400
Source: svgtune
Architecture: source
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Yaroslav Halchenko 
Closes: 956652
Changes:
 svgtune (0.3.0-1) unstable; urgency=medium
 .
   * Fresh "upstream" release compatible with python3 (Closes: #956652)
   * Policy version boost and compat to 10.
Checksums-Sha1:
 4e480b726cb6180bb7ff1c2c3cc664a50d1883d6 1852 svgtune_0.3.0-1.dsc
 56629c335a5d18c16e6d446b11999f201b5c4738 5151 svgtune_0.3.0.orig.tar.gz
 44aa47616f2cff3693627dba325889231241a8d6 1916 svgtune_0.3.0-1.diff.gz
 fc2e7d54b15e8b07f25d950d51ce165f434e0eb7 6255 svgtune_0.3.0-1_source.buildinfo
Checksums-Sha256:
 3bc1f883fb6331254fd1bd94d14c894ed54d2fd1ec875ca9e8c1cff1194796ad 1852 
svgtune_0.3.0-1.dsc
 f442e1e6b720b6d01e4b27af255f883519c79e3297f2332f95f5fc926b23e895 5151 
svgtune_0.3.0.orig.tar.gz
 093533eec37747f5e05c3f393928bfdd52f51b3297dc0ea7037a8f03ab89f836 1916 
svgtune_0.3.0-1.diff.gz
 61ce4bd463a18cca68f7900e5afbee1f8b4d9ceebf8cb075d92a131b86436e3e 6255 
svgtune_0.3.0-1_source.buildinfo
Files:
 4e9e6c96ca06bc8d095b79e120ae8bb9 1852 graphics optional svgtune_0.3.0-1.dsc
 b725e959c91dd042675ed975abbeeb6d 5151 graphics optional 
svgtune_0.3.0.orig.tar.gz
 4b239cd206ae0013ce6b2ba6947a7ca2 1916 graphics optional svgtune_0.3.0-1.diff.gz
 3fcae7bc8f075ca443d1b75f3dd49685 6255 graphics optional 
svgtune_0.3.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAl6wSm8ACgkQot4jUGLa
M/r2rhAAuR+3yU7b9lvbdyrBxDEFq3cGE7KrxRBbrhPPhnLUQ56gJ1Jajt76zLOz
v+FBtKclHBeidBuoPHDQxGzAF9zXocbj9AinajDTgbf4sppx4zad/XsBPQNwLvDZ
DNBOJslHGWazc4Suvt6J0sZBdb54teYg6WcPq09xOIrF/mHvGpn8tXFAAuOPf+nV
FTYPbiZAt8LVgQF5s83NhxBjcSdKubki7tPr3Fs1swgGu6zoL25+J4jx7dtvbrfR
VAEEO6hlVyk+phcvFvpQqdAdC+JJldxtc3HjLp772olfa0S1/2OSwCE+HKKk1Gi6
wSLeBvaCXmJAiyfnhrPP7eomy1ZChqKrNzqxsrkbDTUkulhZVMoy7dYHl+eLFC5X
rcAcIkCKlJo3CqppLfm+YA0nw0ykrqattQTU8vMzOzSut+WsYDIUbkYdtTtMys4C
4+lEDj9Y/MJg3pX4nN3m5d/GvSRyQbHpqrQtZPrvWvaL3C/TETvXYfU6L4gfxr6w
l/EiGwEOSxyRdx9Wq8OwrnQ0R1GEFnnqokKvEDi4ZwpY4y09U7ExRLqUgm9PbDG9
EoYuOFIExfuOsi4aT+qNh8Uovh1wubi6QCBwA6kvahSP9qQgIN5j+kz6oW32Gt3n
FyiFBV8LZBpb0sOOEuR7lK8Oh9pO8vybH0mcOQRXEwczaPd7abE=
=PlSU
-END PGP SIGNATURE End Message ---

Bug#959725: marked as done (RM: svgtune -- RoQA; Inactive Upstream; Unmaintained; Affected by Python2 Removal)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 13:46:15 -0400
with message-id <20200504174615.gk5...@lena.dartmouth.edu>
and subject line Re: Bug#959725: RM: svgtune -- RoQA; Inactive Upstream; 
Unmaintained; Affected by Python2 Removal
has caused the Debian Bug report #959725,
regarding RM: svgtune -- RoQA; Inactive Upstream; Unmaintained; Affected by 
Python2 Removal
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.)


-- 
959725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-CC: deb...@onerussian.com y...@debian.org

Dear FTP Masters,

As discussed in https://bugs.debian.org/956652 , please remove svgtune
from the Debian archive.
This package is python2-only and has not seen upstream activity as
well as Debian packaging activity in the last 5 years. The current
package maintainer did not reply to the package removal request at
https://bugs.debian.org/956652 .

-- 
Regards,
Boyuan Yang
--- End Message ---
--- Begin Message ---

On Mon, 04 May 2020, Mattia Rizzolo wrote:

> Control: tag -1 moreinfo

> On Mon, May 04, 2020 at 12:48:04PM -0400, Yaroslav Halchenko wrote:
> > Please hold off on removal... I will update the package for python3

> Tagging this bug as +moreinfo to hold back on the removal; please close
> this bug once you've done the porting work and uploaded a fixed package.

just uploaded

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


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

Bug#950220: marked as done (autopkg test fails without output on stderr)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:36:20 +
with message-id 
and subject line Bug#950220: fixed in lavacli 1.0-1
has caused the Debian Bug report #950220,
regarding autopkg test fails without output on stderr
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.)


-- 
950220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lavacli
Version: 0.9.8-1
Severity: serious
Tags: sid bullseye

the autopkg test fails without output on stderr.


[...]
=== warnings summary ===
/usr/lib/python3/dist-packages/jinja2/utils.py:485
  /usr/lib/python3/dist-packages/jinja2/utils.py:485: 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 MutableMapping

/usr/lib/python3/dist-packages/jinja2/runtime.py:318
  /usr/lib/python3/dist-packages/jinja2/runtime.py:318: 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

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 198 passed, 2 warnings in 7.54 seconds 
autopkgtest [02:48:36]: test testsuite: ---]
autopkgtest [02:48:36]: test testsuite:  - - - - - - - - - - results - - - - - -
- - - -
testsuiteFAIL stderr: 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.
autopkgtest [02:48:36]: test testsuite:  - - - - - - - - - - stderr - - - - - -
- - - -
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.
autopkgtest [02:48:36]:  summary
testsuiteFAIL stderr: 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.
--- End Message ---
--- Begin Message ---
Source: lavacli
Source-Version: 1.0-1
Done: Remi Duraffort 

We believe that the bug you reported is fixed in the latest version of
lavacli, 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.
Remi Duraffort  (supplier of updated lavacli 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, 29 Jan 2020 14:39:48 +0100
Source: lavacli
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Remi Duraffort 
Closes: 950220
Changes:
 lavacli (1.0-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * autopkgtest: improve testsuite script
   * autopkgtest: reduce set of test dependencies
   * autopkgtest: allow output on stderr (Closes: #950220)
   * gbp.conf: fix settings to build from git repository
 .
   [ Rémi Duraffort ]
   * New upstream release
 + workers: allow one to get and set worker job limit
Checksums-Sha1:
 b24663da32d162781cd4027371e3e6c14c78534c 2151 lavacli_1.0-1.dsc
 b56eb7f8665ed981638e3cf638fb218762d4254d 68815 lavacli_1.0.orig.tar.gz
 3442951e49b41b63ae2a8848196a7df1c02e77c2 14928 lavacli_1.0-1.debian.tar.xz
 18bd50d31dcb91fd9d8243882839090952de5dae 7615 lavacli_1.0-1_amd64.buildinfo
Checksums-Sha256:
 de54cb40fbb57e02bbcc8839bf655be659a55561fd18e710e9f481fe439866da 2151 
lavacli_1.0-1.dsc
 231d15aec8173112db6aab2acf4f38b47e1a2cedc6e2f0e5be6a99d1ad20f69f 68815 
lavacli_1.0.orig.tar.gz
 cf1395ef53c310c98b17410d57d6b9d715d4f8463c264210d67b62e5f550e22c 14928 
lavacli_1.0-1.debian.tar.xz
 ff7d6dd38f864dcfeed9e518acb39ac026ccdc522ce662fe38deb67b700934e0 7615 
lavacli_1.0-1_amd64.buildinfo
Files:
 0cb9a77f890714f5be702fa1d9fb1861 2151 admin optional lavacli_1.0-1.dsc
 afda8898eb566c3b3120678

Bug#957541: marked as done (minidlna: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:19:28 +
with message-id 
and subject line Bug#957541: fixed in minidlna 1.2.1+dfsg-2
has caused the Debian Bug report #957541,
regarding minidlna: 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.)


-- 
957541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:minidlna
Version: 1.2.1+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/minidlna_1.2.1+dfsg-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
  |   ^
In file included from /usr/include/string.h:495,
 from monitor.c:21:
In function ‘strncpy’,
inlined from ‘strncpyt’ at utils.h:56:2,
inlined from ‘check_nfo’ at monitor.c:335:2,
inlined from ‘monitor_insert_file.isra’ at monitor.c:369:17:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
In function ‘strncpy’,
inlined from ‘strncpyt’ at utils.h:56:2,
inlined from ‘monitor_insert_file.isra’ at monitor.c:372:3:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o tivo_utils.o tivo_utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o tivo_beacon.o tivo_beacon.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o tivo_commands.o tivo_commands.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o playlist.o playlist.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o image_utils.o image_utils.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o albumart.o albumart.c
In file included from /usr/include/string.h:495,
 from albumart.c:22:
In function ‘strncpy’,
inlined from ‘strncpyt’ at utils.h:56:2,
inlined from ‘save_resized_album_art’ at albumart.c:67:2:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound 4096 equals destination size 
[-Wstringop-truncation]
  106 |   return __builtin___strncpy

Bug#927393: marked as done (minidlna: Please update package description)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:19:28 +
with message-id 
and subject line Bug#927393: fixed in minidlna 1.2.1+dfsg-2
has caused the Debian Bug report #927393,
regarding minidlna: Please update package description
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.)


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

Dear Maintainer,

The description of the minidlna package mentions the xbmc software, which has 
been renamed into "kodi" for a few years now.
Please update the description of minidlna to reflect this change.

Thanks for maintaining minidlna!

Best regards,
Thomas


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

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

Versions of packages minidlna depends on:
ii  adduser  3.115
ii  libavformat577:3.2.12-1~deb9u1
ii  libavutil55  7:3.2.12-1~deb9u1
ii  libc62.24-11+deb9u4
ii  libexif120.6.21-2+b2
ii  libflac8 1.3.2-1
pn  libid3tag0   
ii  libjpeg62-turbo  1:1.5.1-2
ii  libogg0  1.3.2-1
ii  libsqlite3-0 3.16.2-5+deb9u1
ii  libvorbis0a  1.3.5-4+deb9u2
ii  lsb-base 9.20161125

minidlna recommends no packages.

minidlna suggests no packages.
--- End Message ---
--- Begin Message ---
Source: minidlna
Source-Version: 1.2.1+dfsg-2
Done: Alexander GQ Gerasiov 

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated minidlna package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:01:19 +0300
Source: minidlna
Architecture: source
Version: 1.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Closes: 879541 927393 941410 950270 957541
Changes:
 minidlna (1.2.1+dfsg-2) unstable; urgency=medium
 .
   [ Alexander Gerasiov ]
   * Add 14-fix-gcc10-ftbfs.patch: Fixes FTBFS with gcc10 (Closes: #957541).
   * Move logs to /var/log/minidlna dir.
   * Remove unused START_DAEMON var from default file (Closes: #879541).
   * Add systemd service file (Closes: #950270).
   * Bump debhelper's version to 12.
   * Bump Standards-Version.
   * d/control: Update Vcs headers.
   * d/copyright: Secure links to format and homepage.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Archive, Repository.
 .
   [ Alexander Gerasiov ]
   * Add 15-use-newer-ip_multicast_if-api.patch: (Closes: #941410).
   * d/control: Update description (Closes: #927393).
Checksums-Sha1:
 f8c9cd3b135accc691db181a513012e07f465d45 1706 minidlna_1.2.1+dfsg-2.dsc
 78c47dc68d75f8c8c2486802f555a70f84560976 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 4b5587f6611912617c6a71badb26e51a3170b217 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 ab8a282cb5851696d1628272f1e20720d668e25e0d9b9ac2581e5e2cf4a83dd1 1706 
minidlna_1.2.1+dfsg-2.dsc
 5dd74c5fe02c525dd7aa7c88189d981ebc737ddb9924f6d78ce486925fcf050a 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 c7ce7e297dfefb2c5e9f326ad20cbacd74dbebbb755fa71abfc28b04c5447c96 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Files:
 43752c70461c0fc32f67c75df50336f4 1706 net optional minidlna_1.2.1+dfsg-2.dsc
 366618715c1e9d3d92398c2d48070580 24724 net optional 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 2517557d788a4547ff6008c432cf39b4 8406 net optional 
minidlna_1.2.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAl6wS7oOHG

Bug#879541: marked as done (/etc/default/minidlna is ignored)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:19:28 +
with message-id 
and subject line Bug#879541: fixed in minidlna 1.2.1+dfsg-2
has caused the Debian Bug report #879541,
regarding /etc/default/minidlna is ignored
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.)


-- 
879541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minidlna
Version: 1.2.1+dfsg-1

Apparently minidlna ignores the "-r" set in /etc/default/minidlna.
The version in dmo doesn't.


Regards
Harri
--- End Message ---
--- Begin Message ---
Source: minidlna
Source-Version: 1.2.1+dfsg-2
Done: Alexander GQ Gerasiov 

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated minidlna package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:01:19 +0300
Source: minidlna
Architecture: source
Version: 1.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Closes: 879541 927393 941410 950270 957541
Changes:
 minidlna (1.2.1+dfsg-2) unstable; urgency=medium
 .
   [ Alexander Gerasiov ]
   * Add 14-fix-gcc10-ftbfs.patch: Fixes FTBFS with gcc10 (Closes: #957541).
   * Move logs to /var/log/minidlna dir.
   * Remove unused START_DAEMON var from default file (Closes: #879541).
   * Add systemd service file (Closes: #950270).
   * Bump debhelper's version to 12.
   * Bump Standards-Version.
   * d/control: Update Vcs headers.
   * d/copyright: Secure links to format and homepage.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Archive, Repository.
 .
   [ Alexander Gerasiov ]
   * Add 15-use-newer-ip_multicast_if-api.patch: (Closes: #941410).
   * d/control: Update description (Closes: #927393).
Checksums-Sha1:
 f8c9cd3b135accc691db181a513012e07f465d45 1706 minidlna_1.2.1+dfsg-2.dsc
 78c47dc68d75f8c8c2486802f555a70f84560976 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 4b5587f6611912617c6a71badb26e51a3170b217 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 ab8a282cb5851696d1628272f1e20720d668e25e0d9b9ac2581e5e2cf4a83dd1 1706 
minidlna_1.2.1+dfsg-2.dsc
 5dd74c5fe02c525dd7aa7c88189d981ebc737ddb9924f6d78ce486925fcf050a 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 c7ce7e297dfefb2c5e9f326ad20cbacd74dbebbb755fa71abfc28b04c5447c96 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Files:
 43752c70461c0fc32f67c75df50336f4 1706 net optional minidlna_1.2.1+dfsg-2.dsc
 366618715c1e9d3d92398c2d48070580 24724 net optional 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 2517557d788a4547ff6008c432cf39b4 8406 net optional 
minidlna_1.2.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAl6wS7oOHGdxQGRlYmlh
bi5vcmcACgkQyofp6CqsM/FW0Af+NoVzXOoK1XwOjAB0uuGmKAqez5vPnTOVBi21
m99mEIGw72V1UJQYdFzue3pNVmrvdDdKsSkT8QlaXBPBSklMnpHpEjawGox2LM4Q
anJ6/vqLCRm2+2tqBp4v8hkBUQFHQ2PAz0NE9QeWuTFJ8H0vxUX0e6JipLx6Y5BC
/rGuMcTRaTqXhF/KB1Pi2HXfxE6GKwPQEfLsfZ79bOuVauJWEpE6GNIxkUmctDzQ
I4UYaiNOxCS9ejyKvBHFOsM4mEGx1yfMfpKCZEWDtSz62fVfXU2AmZtWwKYgnRCa
HSzpylRwlIzHlbhpt2a6oDL7WYTwlSDEjX5Cs2LomGmfnb928Q==
=nbbv
-END PGP SIGNATURE End Message ---

Bug#941410: marked as done (minidlna chooses wrong interface when multiple interface are available)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:19:28 +
with message-id 
and subject line Bug#941410: fixed in minidlna 1.2.1+dfsg-2
has caused the Debian Bug report #941410,
regarding minidlna chooses wrong interface when multiple interface are available
to be marked as done.

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

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


-- 
941410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minidlna
Version: 1.2.1+dfsg-1
Tags: patch

Hello,

I ran into a problem where minidlna is not discovered in an
environment with multiple interfaces.

Can you please include the patch at
https://github.com/glebius/minidlna/commit/43573257e45728e070a5f30bd74648c86537e625

Bye,

Joerg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: minidlna
Source-Version: 1.2.1+dfsg-2
Done: Alexander GQ Gerasiov 

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated minidlna package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:01:19 +0300
Source: minidlna
Architecture: source
Version: 1.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Closes: 879541 927393 941410 950270 957541
Changes:
 minidlna (1.2.1+dfsg-2) unstable; urgency=medium
 .
   [ Alexander Gerasiov ]
   * Add 14-fix-gcc10-ftbfs.patch: Fixes FTBFS with gcc10 (Closes: #957541).
   * Move logs to /var/log/minidlna dir.
   * Remove unused START_DAEMON var from default file (Closes: #879541).
   * Add systemd service file (Closes: #950270).
   * Bump debhelper's version to 12.
   * Bump Standards-Version.
   * d/control: Update Vcs headers.
   * d/copyright: Secure links to format and homepage.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Archive, Repository.
 .
   [ Alexander Gerasiov ]
   * Add 15-use-newer-ip_multicast_if-api.patch: (Closes: #941410).
   * d/control: Update description (Closes: #927393).
Checksums-Sha1:
 f8c9cd3b135accc691db181a513012e07f465d45 1706 minidlna_1.2.1+dfsg-2.dsc
 78c47dc68d75f8c8c2486802f555a70f84560976 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 4b5587f6611912617c6a71badb26e51a3170b217 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 ab8a282cb5851696d1628272f1e20720d668e25e0d9b9ac2581e5e2cf4a83dd1 1706 
minidlna_1.2.1+dfsg-2.dsc
 5dd74c5fe02c525dd7aa7c88189d981ebc737ddb9924f6d78ce486925fcf050a 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 c7ce7e297dfefb2c5e9f326ad20cbacd74dbebbb755fa71abfc28b04c5447c96 8406 
minidlna_1.2.1+dfsg-2_source.buildinfo
Files:
 43752c70461c0fc32f67c75df50336f4 1706 net optional minidlna_1.2.1+dfsg-2.dsc
 366618715c1e9d3d92398c2d48070580 24724 net optional 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 2517557d788a4547ff6008c432cf39b4 8406 net optional 
minidlna_1.2.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAl6wS7oOHGdxQGRlYmlh
bi5vcmcACgkQyofp6CqsM/FW0Af+NoVzXOoK1XwOjAB0uuGmKAqez5vPnTOVBi21
m99mEIGw72V1UJQYdFzue3pNVmrvdDdKsSkT8QlaXBPBSklMnpHpEjawGox2LM4Q
anJ6/vqLCRm2+2tqBp4v8hkBUQFHQ2PAz0NE9QeWuTFJ8H0vxUX0e6JipLx6Y5BC
/rGuMcTRaTqXhF/KB1Pi2HXfxE6GKwPQEfLsfZ79bOuVauJWEpE6GNIxkUmctDzQ
I4UYaiNOxCS9ejyKvBHFOsM4mEGx1yfMfpKCZEWDtSz62fVfXU2AmZtWwKYgnRCa
HSzpylRwlIzHlbhpt2a6oDL7WYTwlSDEjX5Cs2LomGmfnb928Q==
=nbbv
-END PGP SIGNATURE End Message ---

Bug#950270: marked as done (minidlna: missing-systemd-service-for-init.d-script)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:19:28 +
with message-id 
and subject line Bug#950270: fixed in minidlna 1.2.1+dfsg-2
has caused the Debian Bug report #950270,
regarding minidlna: missing-systemd-service-for-init.d-script
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.)


-- 
950270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minidlna
Version: 1.2.1+dfsg-1
Severity: normal

Dear Maintainer,

Please consider adding a native systemd service masking the shipped init
script (fixes lintian tag[1] in subject).

The init script looks pretty straight forward so I made an attempt
at writing a service for it. I'm attaching the completely untested
result!
Please note that the equivalent of the init script would have been to
use `Type=forking` (together with PIDFile=), but apparently minidlna
has a special mode of operation called SYSTEMD_MASK specified via the -S
flag so I guess that is preferred and I thus specified that flag in the
service unit and set `Type=simple` instead. (If I read the code
correctly this also means no log file will be written. I assume it will
output to stdout and let the journal handle the logging, but didn't read
that far...)

Please feel free to get in contact about any questions that may remain.
I'm happy to help if you test and review (as I don't personally use
minidlna myself).

While looking at this I also noticed that minidlna init script is using
the "ENABLED" anti-pattern[2]. Please consider getting rid of it.

The service file could also use some additional security hardening[3],
which has been left as a TODO for future improvement.

Regards,
Andreas Henriksson


[1]: 
https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script.html
[2]: 
https://lintian.debian.org/tags/init.d-script-should-always-start-service.html
[3]: 
https://lintian.debian.org/tags/systemd-service-file-missing-hardening-features.html
[Unit]
Documentation=man:minidlnad(1) man:minidlna.conf(5)
After=network.target

[Service]
Type=simple
Environment=CONFIGFILE=/etc/minidlna.conf
EnvironmentFile=-/etc/default/minidlna
ExecStart=/usr/sbin/minidlna -S -f $CONFIGFILE $DAEMON_OPTS
User=minidlna
Group=minidlna
#TODO: security hardening flags

[Install]
WantedBy=multi-user.target
--- End Message ---
--- Begin Message ---
Source: minidlna
Source-Version: 1.2.1+dfsg-2
Done: Alexander GQ Gerasiov 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:01:19 +0300
Source: minidlna
Architecture: source
Version: 1.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Closes: 879541 927393 941410 950270 957541
Changes:
 minidlna (1.2.1+dfsg-2) unstable; urgency=medium
 .
   [ Alexander Gerasiov ]
   * Add 14-fix-gcc10-ftbfs.patch: Fixes FTBFS with gcc10 (Closes: #957541).
   * Move logs to /var/log/minidlna dir.
   * Remove unused START_DAEMON var from default file (Closes: #879541).
   * Add systemd service file (Closes: #950270).
   * Bump debhelper's version to 12.
   * Bump Standards-Version.
   * d/control: Update Vcs headers.
   * d/copyright: Secure links to format and homepage.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Archive, Repository.
 .
   [ Alexander Gerasiov ]
   * Add 15-use-newer-ip_multicast_if-api.patch: (Closes: #941410).
   * d/control: Update description (Closes: #927393).
Checksums-Sha1:
 f8c9cd3b135accc691db181a513012e07f465d45 1706 minidlna_1.2.1+dfsg-2.dsc
 78c47dc68d75f8c8c2486802f555a70f84560976 24724 
minidlna_1.2.1+dfsg-2.debian.tar.xz
 4b5587f6611912617c6a71badb26e51a3170b217 8406 
minidlna_1.2.1

Bug#957942: marked as done (wmcube: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:04:52 +
with message-id 
and subject line Bug#957942: fixed in wmcube 1.0.2-2
has caused the Debian Bug report #957942,
regarding wmcube: 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.)


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/wmcube_1.0.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-a1d63b32-4790-4db9-b95a-e48095c5333e
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package wmcube
dpkg-buildpackage: info: source version 1.0.2-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Doug Torrance 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --sourcedirectory=wmcube
   dh_auto_clean -O--sourcedirectory=wmcube
cd wmcube && make -j1 clean
make[1]: Entering directory '/<>/wmcube'
for i in wmcube.o ../wmgeneral/wmgeneral.o ../wmgeneral/misc.o 
../wmgeneral/list.o ; do \
rm -f $i ; \
done
rm -f wmcube
rm -f *~
make[1]: Leaving directory '/<>/wmcube'
   dh_clean -O--sourcedirectory=wmcube
 debian/rules build
dh build --sourcedirectory=wmcube
   dh_update_autotools_config -O--sourcedirectory=wmcube
   dh_auto_configure -O--sourcedirectory=wmcube
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build --sourcedirectory=wmcube -- \
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security"
cd wmcube && make -j1 "CFLAGS=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security"
make[2]: Entering directory '/<>/wmcube'
gcc -DLINUX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/X11R6/share/include -c wmcube.c -o wmcube.o
gcc -DLINUX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/X11R6/share/include -c ../wmgeneral/wmgeneral.c 
-o ../wmgeneral/wmgeneral.o
gcc -DLINUX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/X11R6/share/include -c ../wmgeneral/misc.c -o 
../wmgeneral/misc.o
gcc -DLINUX -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/X11R6/share/include -c ../wmgeneral/list.c -o 
../wmgeneral/list.o
gcc -Wl,-z,relro -Wl,-z,now -o wmcube wmcube.o ../wmgeneral/wmgeneral.o 
../wmgeneral/misc.o ../wmgeneral/list.o -lXext -L/usr/X11R6/lib -lXpm -lXext 
-lX11 -lm 
/usr/bin/ld: ../wmgeneral/wmgeneral.o:./wmcube/../wmgeneral/wmgeneral.h:39: 
mu

Bug#959585: marked as done (perl6-readline: FTBFS: Errors while processing: rakudo perl6-tap-harness sbuild-build-depends-main-dummy)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:04:36 +
with message-id 
and subject line Bug#959000: fixed in rakudo 2020.02.1-2
has caused the Debian Bug report #959000,
regarding perl6-readline: FTBFS: Errors while processing:  rakudo 
perl6-tap-harness  sbuild-build-depends-main-dummy
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.)


-- 
959000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perl6-readline
Version: 0.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-perl6, perl6-tap-harness, 
> libreadline8, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-perl6, perl6-tap-harness, 
> libreadline8, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [392 B]
> Get:5 copy:/<>/apt_archive ./ Packages [480 B]
> Fetched 1829 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following additional packages will be installed:
>   autoconf automake autopoint autotools-dev bsdmainutils ca-certificates
>   debhelper dh-autoreconf dh-perl6 dh-strip-nondeterminism dwz file
>   fonts-glyphicons-halflings gettext gettext-base groff-base intltool-debian
>   libapt-pkg-perl libarchive-zip-perl libarray-unique-perl libbsd0
>   libcgi-pm-perl libclass-accessor-perl libcroco3 libdebhelper-perl
>   libdebian-source-perl libelf1 libencode-locale-perl liberror-perl
>   libexporter-lite-perl libexporter-tiny-perl libfile-listing-perl
>   libfile-stripnondeterminism-perl libglib2.0-0 libgraph-perl
>   libhtml-form-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl
>   libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl
>   libhttp-message-perl libhttp-negotiate-perl libhttp-server-simple-perl
>   libicu63 libio-html-perl libio-socket-ssl-perl libio-stringy-perl
>   libjs-angularjs libjs-bootstrap liblist-moreutils-perl
>   liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic-mgc libmagic1
>   libnet-http-perl libnet-ssleay-perl libparse-debcontrol-perl
>   libpath-tiny-perl libpipeline1 libreadline8 libsigsegv2 libssl1.1
>   libsub-install-perl libsub-name-perl libsub-override-perl libtie-ixhash-perl
>   libtimedate-perl libtommath1 libtool libtry-tiny-perl libuchardet0
>   liburi-perl libuv1 libwww-mechanize-perl libwww-perl libwww-robotrules-perl
>   libxml2 m4 man-db moarvm netbase nqp openssl perl-openssl-defaults
>   perl6-tap-harness po-debconf rakudo readline-common sensible-utils
> Suggested packages:
>   autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois
>   vacation dh-make gettext-doc libasprintf-dev libgettextpo-dev groff
>   libdata-dump-perl libcrypt-ssleay-perl libtool-doc gfortran
>   | fortran95-compiler gcj-jdk libauthen-ntlm-perl m4-doc apparmor less
>   www-browser libmail-box-perl valgrind readline-doc
> Recommended packages:
>   curl | wget | lynx libcgi-fast-perl libarchive-cpio-perl libglib2.0-data
>   shared-mime-info xdg-user-dirs libhtml-format-perl libunicode-utf8-perl
>   libltdl-dev libdata-dump-perl libmailtools-perl libmail-sendmail-perl
> The following NEW packages will be installed:
>   autoconf automake autopoint autotools-dev bsdmainutils ca-certificates
>   debhelper dh-autoreconf dh-perl6 dh-strip-nondeterminism dwz file
>   fonts-glyphicons-halflings gettext gettext-base groff-base intltool-debian
>   libapt-pkg-perl libarchive-zip-perl libarray-unique-perl libbsd0
>   libcgi-pm-perl libclass-accessor-perl libcroco3 libdebhelper-perl
>   libdebian-source-perl libelf1 libencode-locale-perl li

Bug#959611: marked as done (wmauda: FTBFS: dbus.h:23:10: fatal error: dbus/dbus-glib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:04:46 +
with message-id 
and subject line Bug#959611: fixed in wmauda 0.9-3
has caused the Debian Bug report #959611,
regarding wmauda: FTBFS: dbus.h:23:10: fatal error: dbus/dbus-glib.h: 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.)


-- 
959611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmauda
Version: 0.9-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  -DPIXMAP_DIR="\"/usr/share/pixmaps\"" 
> -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o wmauda.o wmauda.c
> Package dbus-glib-1 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `dbus-glib-1.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'dbus-glib-1' found
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
>  from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:33,
>  from wmauda.c:19:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
> deprecated [-Wdeprecated-declarations]
>   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
>  from /usr/include/glib-2.0/gobject/gbinding.h:29,
>  from /usr/include/glib-2.0/glib-object.h:22,
>  from /usr/include/glib-2.0/gio/gioenums.h:28,
>  from /usr/include/glib-2.0/gio/giotypes.h:28,
>  from /usr/include/glib-2.0/gio/gio.h:26,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32,
>  from wmauda.c:19:
> /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
>   679 | {
>   | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
>  from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtk.h:126,
>  from wmauda.c:19:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is 
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
>73 |   GTimeVal last_popdown;
>   |   ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from /usr/include/glib-2.0/gobject/gbinding.h:28,
>  from /usr/include/glib-2.0/glib-object.h:22,
>  from /usr/include/glib-2.0/gio/gioenums.h:28,
>  from /usr/include/glib-2.0/gio/giotypes.h:28,
>  from /usr/include/glib-2.0/gio/gio.h:26,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32,
>  from wmauda.c:19:
> /usr/include/glib-2.0/glib/gtypes.h:547:8: note: declared here
>   547 | struct _GTimeVal
>   |^
> In file included from wmauda.c:29:
> /usr/include/audacious/dbus.h:23:10: fatal error: dbus/dbus-glib.h: No such 
> file or directory
>23 | #include 
>   |  ^~
> compilation terminated.
> make[1]: *** [

Bug#959000: marked as done (rakudo: fails to configure: missing dependency on libipc-system-simple-perl)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:04:36 +
with message-id 
and subject line Bug#959000: fixed in rakudo 2020.02.1-2
has caused the Debian Bug report #959000,
regarding rakudo: fails to configure: missing dependency on 
libipc-system-simple-perl
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.)


-- 
959000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rakudo
Version: 2020.02.1-1
Severity: serious

Dear Maintainer,

/usr/share/perl6/rakudo-helper.pl uses autodie and system(), which
requires IPC::System::Simple, causing the following error when
installing or upgrading the package:

Setting up rakudo (2020.02.1-1) ...
IPC::System::Simple required for Fatalised/autodying system() at 
/usr/share/perl6/rakudo-helper.pl line 20.
main::BEGIN() called at /usr/share/perl6/rakudo-helper.pl line 20
eval {...} called at /usr/share/perl6/rakudo-helper.pl line 20
BEGIN failed--compilation aborted at /usr/share/perl6/rakudo-helper.pl line 20.
dpkg: error processing package rakudo (--configure):
installed rakudo package post-installation script subprocess returned error 
exit status 2

Manually installing libipc-system-simple-perl allows the upgrade to proceed.

- ilmari
-- 
- Twitter seems more influential [than blogs] in the 'gets reported in
  the mainstream press' sense at least.   - Matt McLeod
- That'd be because the content of a tweet is easier to condense down
  to a mainstream media article.  - Calle Dybedahl
--- End Message ---
--- Begin Message ---
Source: rakudo
Source-Version: 2020.02.1-2
Done: Dominique Dumont 

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated rakudo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 18:42:44 +0200
Source: rakudo
Architecture: source
Version: 2020.02.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Closes: 959000
Changes:
 rakudo (2020.02.1-2) unstable; urgency=medium
 .
   * control: add missing libipc-system-simple-perl dependency
 (Closes: 959000)
   * cleanup old vendor dir in postinst instead of postrm
Checksums-Sha1:
 058818300638876a7d84208bd80a94e4de9a33b8 2404 rakudo_2020.02.1-2.dsc
 ad61d516975149a8ceb6b159380dc8c6c0cc7481 21960 rakudo_2020.02.1-2.debian.tar.xz
 da824abf13487c6fb797aff968e003285b4a570a 6526 
rakudo_2020.02.1-2_source.buildinfo
Checksums-Sha256:
 8f171e020932daada75f8bd16a7b7d9f947342332b4656826489afbf4166c595 2404 
rakudo_2020.02.1-2.dsc
 c052cb25a83c74b6b4354f1e3abdbd48eddcad584dc2cd143870b6964d6d45f8 21960 
rakudo_2020.02.1-2.debian.tar.xz
 8ac997d04d433a1e7b0d90761c34cb31ef8d960afa78cf2cf8aa22c2ce9cb1fb 6526 
rakudo_2020.02.1-2_source.buildinfo
Files:
 3b28eaa289becc4b61919a3f00d3d8f2 2404 interpreters optional 
rakudo_2020.02.1-2.dsc
 8d55bb5ae0de4a2746f81f78890f6bd2 21960 interpreters optional 
rakudo_2020.02.1-2.debian.tar.xz
 5ba4db72bcb8181c31ab48daadd692c0 6526 interpreters optional 
rakudo_2020.02.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAl6wSGgACgkQwx9P2Umr
K2wkww//TNidKjxlrMDGExh7q2HP/yhsFlY6ZlWE1cMkhzFEwKncG60DMu+ebQcc
Y8sEYZQgA2OuPfuvVYKKhdpI7hGCUYT8Hh3SuXzXiGravsqjgl29GePBGeIVSLBa
+Ep5ZoL2l5RHrNJXCo9UT+fpWDrwPtYlWWAsxLzZm7+Aq52d14JnKSSQmH0hMGVM
lk6xMZ7G/wtJK2L56b5+cuLjNBT4RLlbVrCce9+Z4wHkFz/CAShADFI9bAEP5qWM
Qr5PAObBJcdbISQAS1Toxj1DykYEXP7Ewj1Qywjmp8CEv0jiN6TvSiCa/Bi2dTRZ
pUBk15sWcNmFzMKI9BCbF3H1fma73nkyNJY6cLPk+McF3dh8biF2k0SQWMNjUPIv
GHSSNA1FeaZDqoyiSjODfglMcjfSOXY4mYgdghzUCK/0AXpDxhIaDokz27WzHgSc
zTovUKFQFiEN7ivS9mmg61RpRuOeJtx8spgE3uQyhxnf5pusBoc6RBl1yyLDuNM0
bR9eoZCLgx6rkkTiVtDHWKCyEOoyDkoefJJZQbx5tQjMXJJOECFsJytase5DE6II
cNiZfGeZ/6Mp+UpJyK3Lmmn+F8KgQjzLwijGzBRB0gvnpT8wXrGtjw4c5IPUT9Kv
8Z2VnuidLMcSs1pAtqNySaS58v08gHf3R3oqIz58wklH93ucyr0=
=xPZw
-END PGP SIGNATURE End Message ---

Bug#959568: marked as done (perl6-zef: FTBFS: Errors while processing: rakudo perl6-tap-harness sbuild-build-depends-main-dummy)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 17:04:36 +
with message-id 
and subject line Bug#959000: fixed in rakudo 2020.02.1-2
has caused the Debian Bug report #959000,
regarding perl6-zef: FTBFS: Errors while processing:  rakudo perl6-tap-harness  
sbuild-build-depends-main-dummy
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.)


-- 
959000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perl6-zef
Version: 0.8.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), perl6-tap-harness, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), perl6-tap-harness, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [381 B]
> Get:5 copy:/<>/apt_archive ./ Packages [465 B]
> Fetched 1803 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following additional packages will be installed:
>   autoconf automake autopoint autotools-dev bsdmainutils debhelper
>   dh-autoreconf dh-strip-nondeterminism dwz file fonts-glyphicons-halflings
>   gettext gettext-base groff-base intltool-debian libarchive-zip-perl libbsd0
>   libcroco3 libdebhelper-perl libelf1 libfile-stripnondeterminism-perl
>   libglib2.0-0 libgraph-perl libicu63 libjs-angularjs libjs-bootstrap
>   libmagic-mgc libmagic1 libpath-tiny-perl libpipeline1 libsigsegv2
>   libsub-override-perl libtommath1 libtool libuchardet0 libuv1 libxml2 m4
>   man-db moarvm nqp perl6-tap-harness po-debconf rakudo sensible-utils
> Suggested packages:
>   autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois
>   vacation dh-make gettext-doc libasprintf-dev libgettextpo-dev groff
>   libtool-doc gfortran | fortran95-compiler gcj-jdk m4-doc apparmor less
>   www-browser libmail-box-perl valgrind
> Recommended packages:
>   curl | wget | lynx libarchive-cpio-perl libglib2.0-data shared-mime-info
>   xdg-user-dirs libunicode-utf8-perl libltdl-dev libmail-sendmail-perl
> The following NEW packages will be installed:
>   autoconf automake autopoint autotools-dev bsdmainutils debhelper
>   dh-autoreconf dh-strip-nondeterminism dwz file fonts-glyphicons-halflings
>   gettext gettext-base groff-base intltool-debian libarchive-zip-perl libbsd0
>   libcroco3 libdebhelper-perl libelf1 libfile-stripnondeterminism-perl
>   libglib2.0-0 libgraph-perl libicu63 libjs-angularjs libjs-bootstrap
>   libmagic-mgc libmagic1 libpath-tiny-perl libpipeline1 libsigsegv2
>   libsub-override-perl libtommath1 libtool libuchardet0 libuv1 libxml2 m4
>   man-db moarvm nqp perl6-tap-harness po-debconf rakudo
>   sbuild-build-depends-main-dummy sensible-utils
> 0 upgraded, 46 newly installed, 0 to remove and 0 not upgraded.
> Need to get 26.7 MB of archives.
> After this operation, 119 MB of additional disk space will be used.
> Get:1 copy:/<>/apt_archive ./ sbuild-build-depends-main-dummy 
> 0.invalid.0 [888 B]
> Get:2 http://127.0.0.1:12990/debian sid/main amd64 libbsd0 amd64 0.10.0-1 
> [107 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main amd64 bsdmainutils amd64 
> 11.1.2+b1 [191 kB]
> Get:4 http://127.0.0.1:12990/debian sid/main amd64 libuchardet0 amd64 0.0.6-3 
> [64.9 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main amd64 groff-base amd64 1.22.4-4 
> [919 kB]
> Get:6 http://127.0.0.1:12990/debian sid/main amd64 libpipeline1 amd64 1.5.2-2 
> [33.9 kB]
> Get:7 http://127.0.0.1:12990/debian sid/main amd64 man-db amd64 2.9.1-1 [1308 
> kB]
> Get:8 http://127.0.0.1:12990/debian sid/main amd64 sensible-utils all 
> 0.0.12+nmu1 [16.0 kB]
> Get:9 http

Bug#957940: marked as done (wmcore: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:49:13 +
with message-id 
and subject line Bug#957940: fixed in wmcore 0.0.2+ds-2
has caused the Debian Bug report #957940,
regarding wmcore: 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.)


-- 
957940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wmcore
Version: 0.0.2+ds-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/wmcore_0.0.2+ds-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-a6fd3987-6698-44f1-9fc3-f625eebab4bb
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package wmcore
dpkg-buildpackage: info: source version 0.0.2+ds-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Doug Torrance 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/<>'
for i in wmcore.o wmgeneral.o misc.o list.o ; do \
rm -f $i;\
done
rm -f wmcore
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -O3 wmcore.c 
-o wmcore.o
wmcore.c: In function ‘main’:
wmcore.c:86:9: warning: variable ‘token’ set but not used 
[-Wunused-but-set-variable]
   86 |  char * token;
  | ^
wmcore.c:121:4: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  121 |fgets(tmp,200,in);
  |^
wmcore.c:123:6: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  123 |  fgets(tmp,200,in);
  |  ^
wmcore.c:165:10: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  165 |  fgets(tmp,200,in);
  |  ^
wmcore.c:167:12: warning: ignoring return value of ‘fgets’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  167 |fgets(tmp,200,in); // read next line
  |^
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -O3 
wmgeneral.c -o wmgeneral.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -O3 misc.c 
-o misc.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -O3 list.c 
-o list.o
cc -Wl,-z,relro -Wl,-z,now -Wall -o wmcore wmcore.o wmgeneral.o misc.o list.o 
-L/usr/X11R6/lib -lXpm -lXext -lX11
/usr/bin/ld: wmgeneral.o:./wmgeneral.h:39: multiple definition of `display'; 
wmcore.o

Bug#957946: marked as done (wmmisc: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:33:55 +
with message-id 
and subject line Bug#957946: fixed in libdockapp 1:0.7.3-1
has caused the Debian Bug report #957946,
regarding wmmisc: 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.)


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/wmmisc_1.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-1b0a0110-0b0c-4eb2-a06f-38ea52f10db8
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package wmmisc
dpkg-buildpackage: info: source version 1.2-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Doug Torrance 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for library containing nearbyintf... -lm
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DOCKAPP... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
gcc -DPACKAGE_NAME=\"wmmisc\" -DPACKAGE_TARNAME=\"wmmisc\" 
-DPACKAGE_VERSION=\"1.2\" -DPACKAGE_STRING=\"wmmisc\ 1.2\" 
-DPACKAGE_BUGREPORT=\"wmaker-...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"wmmisc\" -DVERSION=\"1.2\" -I.   -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/dockapp_draw.o src/dockapp_draw.c

Bug#957552: marked as done (mmseqs2: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:34:07 +
with message-id 
and subject line Bug#957552: fixed in mmseqs2 11-e1a1c+ds-3
has caused the Debian Bug report #957552,
regarding mmseqs2: 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.)


-- 
957552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mmseqs2
Version: 10-6d92c+ds-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/mmseqs2_10-6d92c+ds-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
[ 34%] Building CXX object 
src/CMakeFiles/mmseqs-framework.dir/clustering/ClusteringAlgorithms.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DAVX2=1 
-DHAVE_BZLIB=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_MADVISE=1 -DHAVE_ZLIB=1 
-DOPENMP=1 -I/<>/lib/tinyexpr -I/<>/lib 
-I/<>/lib/simd -I/<>/lib/alp 
-I/<>/lib/cacode -I/<>/lib/ksw2 
-I/<>/obj-x86_64-linux-gnu/generated 
-I/<>/src/alignment -I/<>/src/clustering 
-I/<>/src/commons -I/<>/src/multihit 
-I/<>/src/prefiltering -I/<>/src/linclust 
-I/<>/src/taxonomy -I/<>/src/util 
-I/<>/src/.  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -mavx2 -mfpmath=sse -Wa,-q-std=c++0x 
-fno-exceptions -pedantic -Wall -Wextra -Wdisabled-optimization  -march=native 
-mavx2 -mfpmath=sse -Wa,-q -fopenmp -o CMakeFiles/mmseqs-framework.di
 r/clustering/ClusteringAlgorithms.cpp.o -c 
/<>/src/clustering/ClusteringAlgorithms.cpp
[ 34%] Building CXX object 
src/CMakeFiles/mmseqs-framework.dir/commons/A3MReader.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DAVX2=1 
-DHAVE_BZLIB=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_MADVISE=1 -DHAVE_ZLIB=1 
-DOPENMP=1 -I/<>/lib/tinyexpr -I/<>/lib 
-I/<>/lib/simd -I/<>/lib/alp 
-I/<>/lib/cacode -I/<>/lib/ksw2 
-I/<>/obj-x86_64-linux-gnu/generated 
-I/<>/src/alignment -I/<>/src/clustering 
-I/<>/src/commons -I/<>/src/multihit 
-I/<>/src/prefiltering -I/<>/src/linclust 
-I/<>/src/taxonomy -I/<>/src/util 
-I/<>/src/.  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -mavx2 -mfpmath=sse -Wa,-q-std=c++0x 
-fno-exceptions -pedantic -Wall -Wextra -Wdisabled-optimization  -march=native 
-mavx2 -mfpmath=sse -Wa,-q -fopenmp -o CMakeFiles/mmseqs-framework.di
 r/commons/A3MReader.cpp.o -c /<>/src/commons/A3MReader.cpp
[ 35%] Building CXX object 
src/CMakeFiles/mmseqs-framework.dir/commons/Application.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DAVX2=1 
-DHAVE_BZLIB=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_MADVISE=1 -DHAVE_ZLIB=1 
-DOPENMP=1 -I/<>/lib/tinyexpr -I/<>/lib 
-I/<>/lib/simd -I/<>/lib/alp 
-I/<>/lib/cacode -I/<>/lib/ksw2 
-I/<>/obj-x86_64-linux-gnu/generated 
-I/<>/src/alignment -I/<>/src/clustering 
-I/<>/src/commons -I/<>/src/multihit 
-I/<>/src/prefiltering -I/<>/src/linclust 
-I/<>/src/taxonomy -I/<>/src/util 
-I/<>/src/.  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -mavx2 -mfpmath=sse -Wa,-q-std=c++0x 
-fno-exceptions -pedantic -Wall -Wextra -Wdisabled-optimization  -march=native 
-mavx2 -mfpmath=sse -Wa,-q -fopenmp -o CMakeFiles/mmseqs-framework.di
 r/commons/Application.cpp.o -c /<>/src/commons/Application.cpp
[ 35%] Building CXX object 
src/CMakeFiles/mmseqs-framework.dir/commons/Ba

Bug#959648: marked as done (uwsgi-apparmor: FTBFS: make[1]: pyversions: Command not found)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:18:35 +
with message-id 
and subject line Bug#959648: fixed in uwsgi-apparmor 
0.0.0+git.2014.09.15.7d6d7bd7eb-3
has caused the Debian Bug report #959648,
regarding uwsgi-apparmor: FTBFS: make[1]: pyversions: Command not found
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.)


-- 
959648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi-apparmor
Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> make: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build
>dh_update_autotools_config
>dh_autoreconf
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> make[1]: pyversions: Command not found
> py3versions: no X-Python3-Version in control file, using supported versions
> uwsgi --build-plugin .
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-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: uwsgi-apparmor
Source-Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-3
Done: Michal Arbet 

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

Debian distribution maintenance software
pp.
Michal Arbet  (supplier of updated uwsgi-apparmor 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 15:49:15 +0200
Source: uwsgi-apparmor
Architecture: source
Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Michal Arbet 
Closes: 959648
Changes:
 uwsgi-apparmor (0.0.0+git.2014.09.15.7d6d7bd7eb-3) unstable; urgency=medium
 .
   * d/rules: Fix generating apparmor_plugin.so (Closes: #959648).
   * d/copyright: Add me to copyright file.
   * d/control: Change VCS urls to openstack-team
Checksums-Sha1:
 4612fb104d0bbff3006c39cd9fef8139f61e9644 2338 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.dsc
 b0bb60bc44eec6a8c4af9c30d16a9463e7c3db93 2172 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.debian.tar.xz
 440346f3698ebafe1fc2ccc472b24bf50b7b25bb 7686 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3_amd64.buildinfo
Checksums-Sha256:
 177f7b557d891212e756b85f535ff8aa9ddc3383b47f5d4ff3f9c5be9e8802ff 2338 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.dsc
 e77269d87eadc28a0703be1b9060b1dead9f4af00c37ba5c541667686644a0a4 2172 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.debian.tar.xz
 ce24c96af67adf3d2416c12b6efa8b310ac00598a7944878705d0fb4fc0366df 7686 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3_amd64.buildinfo
Files:
 c6c3272943907e0e4c10701495be7fcf 2338 net optional 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.dsc
 9497a5feac60f33724361e0c0b3b6f1c 2172 net optional 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3.debian.tar.xz
 0c28ca9e6ce81b83c2667b5987357fa5 7686 net optional 
uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5XQmXq/+PEpA+qGNSgz2OUJ4hOMFAl6wPiMACgkQSgz2OUJ4
hOOyYQ/+Il+Qr46nVbsM1aRn5mil2z8AzUunguB+7OZzekgrQHxuGH1Dt84g03RI
iDPki4EBUP6uNkUTzCIjXPNIbXWSGy1JmlUUTf0F5FfJMVrJAim83Io07e5dd8Yl
dOOhIdJbEM0KYCAUDZSi64HAuWnJ3IRNZYCZ0mOssAoE0UKnWXpx8oexJ6o9VhZk
AP/82j7UV9e71sFO57UWL7cVZg3XAMSF9j6DsIrcLV1t+m1FY/1PKYohcXwd

Bug#957583: marked as done (ncl: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:03:57 +
with message-id 
and subject line Bug#957583: fixed in ncl 6.6.2-2
has caused the Debian Bug report #957583,
regarding ncl: 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.)


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ncl_6.6.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
dh_install: warning: Cannot find (any matches for) "usr/bin/rasgetpal" (tried 
in ., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/rasgetpal
dh_install: warning: Cannot find (any matches for) "usr/bin/rasls" (tried in ., 
debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/rasls
dh_install: warning: Cannot find (any matches for) "usr/bin/rasstat" (tried in 
., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/rasstat
dh_install: warning: Cannot find (any matches for) "usr/bin/rasview" (tried in 
., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/rasview
dh_install: warning: Cannot find (any matches for) "usr/bin/rassplit" (tried in 
., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/rassplit
dh_install: warning: Cannot find (any matches for) "usr/bin/tdpackdemo" (tried 
in ., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/tdpackdemo
dh_install: warning: Cannot find (any matches for) "usr/bin/tgks0a" (tried in 
., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/tgks0a
dh_install: warning: Cannot find (any matches for) "usr/bin/tlocal" (tried in 
., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/tlocal
dh_install: warning: Cannot find (any matches for) "usr/bin/WriteLineFile" 
(tried in ., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/WriteLineFile
dh_install: warning: Cannot find (any matches for) "usr/bin/WriteNameFile" 
(tried in ., debian/tmp)

dh_install: warning: ncl-ncarg missing files: usr/bin/WriteNameFile
install -d debian/ncl-ncarg//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/ctlib debian/ncl-ncarg//usr/bin/
dh_install: warning: Cannot find (any matches for) 
"lib/ncarg/database/PlotcharData" (tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: 
lib/ncarg/database/PlotcharData
dh_install: warning: Cannot find (any matches for) "lib/ncarg/sysresfile" 
(tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: lib/ncarg/sysresfile
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/lib/ncarg/database/*areas" (tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: 
debian/tmp/lib/ncarg/database/*areas
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/lib/ncarg/database/*names" (tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: 
debian/tmp/lib/ncarg/database/*names
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/lib/ncarg/database/*lines" (tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: 
debian/tmp/lib/ncarg/database/*lines
dh_install: warning: Cannot find (any matches for) 
"debian/tmp/lib/ncarg/database/ezmap*" (tried in ., debian/tmp)

dh_install: warning: libncarg-data missing files: 
debian/tmp/lib/ncarg/database/ezmap*
dh_install: warni

Bug#957203: marked as done (ferret-vis: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 16:03:31 +
with message-id 
and subject line Bug#957203: fixed in ferret-vis 7.6.0~beta-1
has caused the Debian Bug report #957203,
regarding ferret-vis: 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.)


-- 
957203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ferret-vis
Version: 7.5.0-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ferret-vis_7.5.0-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
(cd special; make)
make[3]: Entering directory '/<>/fer/special'
gcc -I../../fmt/cmn -I../../fer/common -I//usr/include -I/usr/include 
-I/usr/include/X11 -I../../ppl/include -I../../ppl/tmap_inc -I/usr/include/xgks 
-Dunix -Dgfortran -DNO_OPEN_SHARED -DNO_OPEN_RECORDTYPE -DX_REFRESH 
-Dreclen_in_bytes -DNO_OPEN_READONLY -DMANDATORY_FORMAT_WIDTHS 
-DNO_OPEN_CARRIAGECONTROL -Dxgks -DSTAR_1_SUPPORTED -DFULL_GUI_VERSION 
-DX_REFRESH -DXT_CODE  -DLINUX -DNO_PASSED_CONCAT -Dcrptd_cat_argument 
-DG77_SIGNAL -DG77 -DNEED_IAND -DINTERNAL_READ_FORMAT_BUG -DNO_PREPEND_STRING 
-DNO_DOUBLE_ESCAPE_SLASH -Ddouble_p  -fPIC -Dlint -D_SSIZE_T -DVOID_SIGHANDLER 
-D_POSIX_VERSION -DLINUX -DFULL_GUI_VERSION -DX_REFRESH -DXT_CODE -Dsun4 
`dpkg-buildflags --get CFLAGS` -Wdate-time -D_FORTIFY_SOURCE=2 `dpkg-buildflags 
--get CPPFLAGS` `dpkg-buildflags --get CPPFLAGS`  -c -o FerMem_routines.o 
FerMem_routines.c
gfortran -I../../fmt/cmn -I../../fer/common -I//usr/include -I/usr/include 
-I/usr/include/X11 -I../../ppl/include -I../../ppl/tmap_inc -I/usr/include/xgks 
-Dunix -Dgfortran -DNO_OPEN_SHARED -DNO_OPEN_RECORDTYPE -DX_REFRESH 
-Dreclen_in_bytes -DNO_OPEN_READONLY -DMANDATORY_FORMAT_WIDTHS 
-DNO_OPEN_CARRIAGECONTROL -Dxgks -DSTAR_1_SUPPORTED -DFULL_GUI_VERSION 
-DX_REFRESH -DXT_CODE  -DLINUX -DNO_PASSED_CONCAT -Dcrptd_cat_argument 
-DG77_SIGNAL -DG77 -DNEED_IAND -DINTERNAL_READ_FORMAT_BUG -DNO_PREPEND_STRING 
-DNO_DOUBLE_ESCAPE_SLASH -Ddouble_p  -fPIC -fno-automatic 
-fno-second-underscore -fdollar-ok -ffixed-line-length-132 -ffpe-trap=overflow 
-fdefault-real-8 -fdefault-double-8 -I../../ppl/tmap_inc -I../../fmt/cmn 
-I../../ppl/include -I../../fer/common -I../../external_functions/ef_utility 
`dpkg-buildflags --get FFLAGS` -c aix_routines.F -o aix_routines.o
gfortran -I../../fmt/cmn -I../../fer/common -I//usr/include -I/usr/include 
-I/usr/include/X11 -I../../ppl/include -I../../ppl/tmap_inc -I/usr/include/xgks 
-Dunix -Dgfortran -DNO_OPEN_SHARED -DNO_OPEN_RECORDTYPE -DX_REFRESH 
-Dreclen_in_bytes -DNO_OPEN_READONLY -DMANDATORY_FORMAT_WIDTHS 
-DNO_OPEN_CARRIAGECONTROL -Dxgks -DSTAR_1_SUPPORTED -DFULL_GUI_VERSION 
-DX_REFRESH -DXT_CODE  -DLINUX -DNO_PASSED_CONCAT -Dcrptd_cat_argument 
-DG77_SIGNAL -DG77 -DNEED_IAND -DINTERNAL_READ_FORMAT_BUG -DNO_PREPEND_STRING 
-DNO_DOUBLE_ESCAPE_SLASH -Ddouble_p  -fPIC -fno-automatic 
-fno-second-underscore -fdollar-ok -ffixed-line-length-132 -ffpe-trap=overflow 
-fdefault-real-8 -fdefault-double-8 -I../../ppl/tmap_inc -I../../fmt/cmn 
-I../../ppl/include -I../../fer/common -I../../external_functions/ef_utility 
`dpkg-buildflags --get FFLAGS` -c fake_gks.F -o fake_gks.o
gfortran -I../../fmt/cmn -I../../fer/common -I//usr/include -I/usr/include 
-I/usr/include/X11 -I../../ppl/include -I../../ppl/tmap_inc -I/usr/include/xgks 
-Dunix -Dgfortran -DNO_OPEN_SHARED -DNO_OPEN_RECORDTYPE -DX_REFRESH 
-Dreclen_in_bytes -DNO_OPEN_READONLY -DMANDA

Bug#957295: marked as done (gnustep-gui: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 19:00:35 +0300
with message-id <87sggfbsgs.GNU's_not_UNIX!-ya...@gnu.org>
and subject line FTBFS due to a GCC bug which has been fixed
has caused the Debian Bug report #957295,
regarding gnustep-gui: 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.)


-- 
957295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnustep-gui
Version: 0.27.0-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gnustep-gui_0.27.0-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:745:35: error: expected ‘)’ before ‘::’ token
  745 | GET_IMP(@selector(DPSsetoffset::));
  |  ~^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:751:35: error: expected ‘)’ before ‘::’ token
  751 | GET_IMP(@selector(DPScomposite));
  |  ~^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:753:39: error: expected ‘)’ before ‘::’ token
  753 | GET_IMP(@selector(DPScompositerect:));
  |  ~^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:755:34: error: expected ‘)’ before ‘::’ token
  755 | GET_IMP(@selector(DPSdissolve));
  |  ~   ^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:758:34: error: expected ‘)’ before ‘::’ token
  758 | GET_IMP(@selector(GSDrawImage::));
  |  ~   ^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:764:32: error: expected ‘)’ before ‘::’ token
  764 | GET_IMP(@selector(DPSPrintf::));
  |  ~ ^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:766:35: error: expected ‘)’ before ‘::’ token
  766 | GET_IMP(@selector(DPSWriteData::));
  |  ~^~
NSGraphicsContext.m:524:63: note: in definition of macro ‘GET_IMP’
  524 | #define GET_IMP(X) ((void*) [self instanceMethodForSelector: (X)])
  |   ^
NSGraphicsContext.m:7

Bug#957078: marked as done (cenon.app: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 19:00:35 +0300
with message-id <87sggfbsgs.GNU's_not_UNIX!-ya...@gnu.org>
and subject line FTBFS due to a GCC bug which has been fixed
has caused the Debian Bug report #957078,
regarding cenon.app: 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.)


-- 
957078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cenon.app
Version: 4.0.6+ds1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/cenon.app_4.0.6+ds1-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
done; \
  else \
echo "Warning: .//$l.lproj not found - ignoring"; \
  fi; \
done
cd .; \
/usr/share/GNUstep/Makefiles/mkinstalldirs ./obj
Making all for subproject VHFImport...
cd .; \
/usr/share/GNUstep/Makefiles/mkinstalldirs ./obj/VHFImport.obj/
gcc PSImport.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
   -o obj/VHFImport.obj/PSImport.m.o
gcc DINImport.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
   -o obj/VHFImport.obj/DINImport.m.o
gcc DXFImport.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
   -o obj/VHFImport.obj/DXFImport.m.o
gcc GerberImport.m -c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP 
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 
-DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions 
-D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE 
-Wno-import -g -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-fconstant-string-class=NSConstantString -I.. -I. -I/usr/local/include/GNUstep 
-I/usr/include/GNUstep \
   -o obj/VHFImport.obj/GerberImport.m.o
DXFImport.m: In function ‘-[DXFImport blockScannerFromScanner:]’:
DXFImport.m:147:10: warning: variable ‘location’ set but not used 
[-Wunused-but-set-variable]
  147 | int  location;
  |  ^~~~
DXFImport.m: In function ‘-[DXFImport getGraphicFromData::]’:
DXFImport.m:725:67: error: expected ‘)’ before ‘::’ token
  725 |

Bug#957682: marked as done (pikopixel.app: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 19:00:35 +0300
with message-id <87sggfbsgs.GNU's_not_UNIX!-ya...@gnu.org>
and subject line FTBFS due to a GCC bug which has been fixed
has caused the Debian Bug report #957682,
regarding pikopixel.app: 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.)


-- 
957682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pikopixel.app
Version: 1.0-b9d-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pikopixel.app_1.0-b9d-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
PPGNUstepGlue_WindowStyleOffsets.m:100:68: error: expected ‘)’ before ‘::’ token
  100 | ppSwizzleInstanceMethodWithSelector: 
@selector(styleoffsets::)
  |   ~^~
  |)
PPGNUstepGlue_WindowStyleOffsets.m:101:79: error: expected ‘)’ before ‘::’ token
  101 | forInstanceMethodWithSelector: 
@selector(ppGSPatch_Compiz_Styleoffsets::)];
  | ~   
  ^~
  | 
  )
In file included from PPGNUstepGlue_WindowStyleOffsets.m:38:
PPGNUstepGlue_WindowStyleOffsets.m: In function ‘+[NSObject(PPGNUstepGlue) 
WindowStyleOffsets_ppGSGlue_WindowStyleOffsets_KwinMrcoOpbxWmkrXfwm_InstallPatches]’:
PPGNUstepGlue_WindowStyleOffsets.m:115:76: error: expected ‘)’ before ‘::’ token
  115 | macroSwizzleInstanceMethod(NSClassFromString(@"XGServer"), 
styleoffsets::,
  | 
   ^~
NSObject_PPUtilities.h:53:71: note: in definition of macro 
‘macroSwizzleInstanceMethod’
   53 | [class ppSwizzleInstanceMethodWithSelector: 
@selector(selectorName1)\
  |   
^
NSObject_PPUtilities.h:53:70: note: to match this ‘(’
   53 | [class ppSwizzleInstanceMethodWithSelector: 
@selector(selectorName1)\
  |  ^
PPGNUstepGlue_WindowStyleOffsets.m:115:5: note: in expansion of macro 
‘macroSwizzleInstanceMethod’
  115 | macroSwizzleInstanceMethod(NSClassFromString(@"XGServer"), 
styleoffsets::,
  | ^~
PPGNUstepGlue_WindowStyleOffsets.m:116:76: error: expected ‘)’ before ‘::’ token
  116 | 
ppGSPatch_KwinMrcoOpbxWmkrXfwm_Styleoffsets::);
  | 
   ^~
NSObject_PPUtilities.h:54:66: note: in definition of macro 
‘macroSwizzleInstanceMethod’
   54 | forInstanceMethodWithSelector: 
@selector(selectorName2)]
  |  
^
NSObject_PPUtilities.h:54:65: note: to match this ‘(’
   54 | forInstanceMethodWithSelector: 
@selector(selectorName2)]
  | ^
PPGNUstepGlue_WindowStyleOffsets.m:115:5: note: in expansion of macro 
‘macroSwizzleInstanceMethod’
  115 | macroSwizzleInstanceMethod(NSClassFromString(@"XGServer"), 
styleoffsets::,
  |  

Bug#948330: marked as done (ITP: libsys-info-perl -- Fetch information from the host system)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 17:22:05 +0200
with message-id <0f7a7003-fe26-920b-3bc8-add644e4f...@vu.nl>
and subject line Re: ITP: libsys-info-perl -- Fetch information from the host 
system
has caused the Debian Bug report #948330,
regarding ITP: libsys-info-perl -- Fetch information from the host system
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.)


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

Subject: ITP: libsys-info-perl -- Fetch information from the host system
Package: wnpp
Owner: Michael R. Crusoe 
Severity: wishlist

* Package name: libsys-info-perl
  Version : 0.7811
  Upstream Author : , Burak Gursoy 
* URL : https://metacpan.org/release/Sys-Info
* License : Artistic
  Programming Lang: Perl
  Description : Fetch information from the host system
 Extracts and collects information from the host system.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/libsys-info-perl
--- End Message ---
--- Begin Message ---
Huh, this package was in the archive already. Don't know why I missed it--- End Message ---

Bug#948329: marked as done (ITP: libsys-info-driver-linux-perl -- Linux driver for Sys::Info)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 17:22:54 +0200
with message-id 
and subject line Re: ITP: libsys-info-driver-linux-perl -- Linux driver for 
Sys::Info
has caused the Debian Bug report #948329,
regarding ITP: libsys-info-driver-linux-perl -- Linux driver for Sys::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.)


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

Subject: ITP: libsys-info-driver-linux-perl -- Linux driver for Sys::Info
Package: wnpp
Owner: Michael R. Crusoe 
Severity: wishlist

* Package name: libsys-info-driver-linux-perl
  Version : 0.7905
  Upstream Author : , Burak Gursoy 
* URL : https://metacpan.org/release/Sys-Info-Driver-Linux
* License : Artistic
  Programming Lang: Perl
  Description : Linux driver for Sys::Info
 This is the main module in the Linux driver collection.

Remark: This package is maintained by Michael R. Crusoe at
   https://salsa.debian.org/med-team/libsys-info-driver-linux-perl
--- End Message ---
--- Begin Message ---
Already packaged--- End Message ---

Bug#920552: marked as done (procps: Enable regular file and FIFO protection)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 15:09:25 +0200
with message-id <20200504130925.ga621...@home.ouaza.com>
and subject line Re: Bug#920552: procps:  Enable regular file and FIFO 
protection
has caused the Debian Bug report #920552,
regarding procps:  Enable regular file and FIFO protection
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.)


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

In analogy with bug #889098, procps should by default enabling the regular file
and FIFO protection added in 4.19 by setting:

fs.protected_regular = 1
fs.protected_fifos = 1

This will be done by default in systemd 241, but as Debian does not use
Systemd's sysctl settings, it should be made in procps.

References:
https://github.com/torvalds/linux/commit/30aba6656f
https://github.com/systemd/systemd/commit/2732587540035227fe59e4b64b60127352611b35
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889098



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (400, 'unstable'), (250, 'stable'), (160, 'experimental'), (100, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages procps depends on:
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-5
ii  libncurses6  6.1+20181013-1
ii  libncursesw6 6.1+20181013-1
ii  libprocps7   2:3.3.15-2
ii  libtinfo66.1+20181013-1
ii  lsb-base 10.2018112800

Versions of packages procps recommends:
ii  psmisc  23.2-1

procps suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:3.3.16-1

On Sat, 26 Jan 2019, Frederik Himpe wrote:
> In analogy with bug #889098, procps should by default enabling the
> regular file and FIFO protection added in 4.19 by setting:
> 
> fs.protected_regular = 1
> fs.protected_fifos = 1

This has been implemented in 2:3.3.16-1 already.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS--- End Message ---

Bug#953531: marked as done (glob wildcards not accepted anymore)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 14:34:04 +
with message-id 
and subject line Bug#953531: fixed in apt 2.1.0
has caused the Debian Bug report #953531,
regarding glob wildcards not accepted anymore
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.)


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

Apt does not work any more with jokers.
Before, I used apt in some cases with jokers.
Example : apt install remmina-plugin-*

Now, I have an error message :
# apt install remmina-plugin-*
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
E: Impossible de trouver le paquet remmina-plugin-*

Thank you.

David.
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 2.1.0
Done: Julian Andres Klode 

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated 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: Mon, 04 May 2020 15:58:24 +0200
Source: apt
Architecture: source
Version: 2.1.0
Distribution: unstable
Urgency: medium
Maintainer: APT Development Team 
Changed-By: Julian Andres Klode 
Closes: 953531 956313
Changes:
 apt (2.1.0) unstable; urgency=medium
 .
   [ Frans Spiesschaert ]
   * Dutch manpages translation update (Closes: #956313)
 .
   [ David Kalnischkies ]
   * Refactor MarkInstall fixing various or-group handling issues
 - Discard impossible candidate versions also for non-installed
 - Explore or-groups for Recommends further than first
 - Refactor and reorder MarkInstall code
 - Discard candidate if its dependencies can't be satisfied
 - Split up MarkInstall into private helper methods
 - Fail earlier on impossible Conflicts in MarkInstall
 - Propagate Protected flag to single-option dependencies
 - Prefer upgrading installed orgroup members
 - Protect a package while resolving in MarkInstall
 .
   [ Julian Andres Klode ]
   * Reinstate * wildcards (Closes: #953531) (LP: #1872200)
   * apt list: Fix behavior of regex vs fnmatch vs wildcards
Checksums-Sha1:
 938d62946bbe991dee84e704ab425e4de93805fd 2756 apt_2.1.0.dsc
 50e98e8f2d2a515eabb1a7f5843b8ecb5e4c4b4c 2169024 apt_2.1.0.tar.xz
 f1572c229278fcdc94701eafabdf7f3a31057a01 7319 apt_2.1.0_source.buildinfo
Checksums-Sha256:
 42c4999cadcd4c6e672b2ee5c8b9a928d9b323b5165f3d0b8ba4225c12bf5a00 2756 
apt_2.1.0.dsc
 0ffeab03b8284146e219905c0a400eddcfb3880705080839fa9e5bc5a94c18e1 2169024 
apt_2.1.0.tar.xz
 4a0a158f3b1ef3b7b614ae238202435455513df7be6ce85344d82de0467d08de 7319 
apt_2.1.0_source.buildinfo
Files:
 566b55020ed3246f7cf5c3e1480c49ff 2756 admin important apt_2.1.0.dsc
 470cf73ad2f51a75c406c766379d24e0 2169024 admin important apt_2.1.0.tar.xz
 8e685981598d88d83438cfefb1b2f099 7319 admin important 
apt_2.1.0_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEET7WIqEwt3nmnTHeHb6RY3R2wP3EFAl6wIJkPHGpha0BkZWJp
YW4ub3JnAAoJEG+kWN0dsD9xeygP/iqJOxmTKkVo4y6mHTU2d6/67a6pppfqy243
pi8TwzRxzt4wlRhRmeYS2hhG3TYo3FFQavyfihumdaz33lC75KNteBS4puiyFlOJ
AjIileWIigaqQDrw0C81N0+nKtWL++qJO0DUjl8uJKlw3x7+zed8dcKFLrfN7/Ys
D3YzKVUac9c1HB68K6qXdhtOMpnptLOGERVTVD13FlZMH0OxyUTxdM4WRPpaqrYd
WZXqnkxVKm9+olXeROEoX+IjoPQ90vYHa2L6BiT7KlBe8k++3A0QfC1u1xhnGyNt
t3SFthxTgJx8GCcbRvwS8bPDlX03u3knlA3tnl2HfbgoJwD/bHT8rNDvYLYhM2D9
Q4uBNMFsTRRYj1s7XSwAr1FUAOwdwkpiMOGHSGSdmndfH4Kv5jIyvBAXoc0Vg7zo
lYP+7j1DHw0cPfkiAysQu/FP3S7Bf5y3A7e8Uw5m9RN6V3Ss2Lb8wj76VIefbv+3
h0QSbYAh1k2YAuhuKbG/yc2fDnI5n2QxRvW3pfBVF6U4pIeQpN++ea2p3LZUzFJG
StC5M+FJ4Qpn9NT3fT4Z+1Gv3m9pyYEcFmw3L3I6MRuX5l0kOPVClBcYCs+ETvQx
TGPIH2RAoB9dxZSSjrQf64/YVHy/3bs2NGD+lr2S5RMTIrpjoBTC2Xfj7Yt3DY3e
bQLeihww
=ilvw
-END PGP SIGNATURE End Message ---

Bug#959163: marked as done (fscrypt: Please package fscrypt 0.2.7)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 13:48:42 +
with message-id 
and subject line Bug#959163: fixed in fscrypt 0.2.7-1
has caused the Debian Bug report #959163,
regarding fscrypt: Please package fscrypt 0.2.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.)


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

The 2.7 version chnagelog : The main addition in this release is that we now 
automatically detect support for V2 policies when running fscrypt setup and 
configure /etc/fscrypt.conf appropriately (#205). This allows uses on newer 
kernels to automatically start using V2 policies without manually changing 
/etc/fscrypt.conf. To use these new policies, simply run sudo fscrypt setup and 
your /etc/fscrypt.conf will be automatically updated.

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

Kernel: Linux 5.4.36 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fscrypt depends on:
ii  libc6 2.31-0experimental0
ii  libpam0g  1.3.1-5

fscrypt recommends no packages.

Versions of packages fscrypt suggests:
pn  libpam-fscrypt  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fscrypt
Source-Version: 0.2.7-1
Done: Paride Legovini 

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

Debian distribution maintenance software
pp.
Paride Legovini  (supplier of updated fscrypt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 13:06:29 +
Source: fscrypt
Architecture: source
Version: 0.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Paride Legovini 
Closes: 959163
Changes:
 fscrypt (0.2.7-1) unstable; urgency=medium
 .
   * New upstream version 0.2.7 (closes: #959163).
   * d/rules: run dh_auto_install with --no-source.
   * d/rules: do not try to force -buildmode=pie.
   * d/control: bump the dh compat level to 13.
   * d/control: use the par...@debian.org alias in Uploaders.
Checksums-Sha1:
 cee89819bf32f2add6ca059927dfbf712eb15f77 1970 fscrypt_0.2.7-1.dsc
 4cf1ba24166409a5d5981526c1054ebf7fea5d54 122972 fscrypt_0.2.7.orig.tar.gz
 861053e2c78f91b8a62593191786880361c9e474 5264 fscrypt_0.2.7-1.debian.tar.xz
 b8e63fac6a45109ace3af8e3bb783ca7f40ba9b5 6341 fscrypt_0.2.7-1_amd64.buildinfo
Checksums-Sha256:
 bd5709d71297227f7c4a6286bb31c85fcad2ee8abaed7f0c6a562b9fe6921a64 1970 
fscrypt_0.2.7-1.dsc
 08e7f1bb5481f5ee76a90d79b9d9e2632f167d43100438ba08bd637e2dfb0f22 122972 
fscrypt_0.2.7.orig.tar.gz
 61a17df92f8c27778a9c28ace49f367a3463d1c0c5a0d2d89293cebed5f1307d 5264 
fscrypt_0.2.7-1.debian.tar.xz
 55eabc9a485935d3b0d0ad413cb21daeaf7c597cc4fa6d31e228d0ce7ebfb8f9 6341 
fscrypt_0.2.7-1_amd64.buildinfo
Files:
 232b89e5ee84bd887044b4b03cdd5536 1970 admin optional fscrypt_0.2.7-1.dsc
 40b650d01b93f73cd9156094057d7861 122972 admin optional 
fscrypt_0.2.7.orig.tar.gz
 6656beff1102051d4c80e6d07c2fa4d4 5264 admin optional 
fscrypt_0.2.7-1.debian.tar.xz
 87ddeb301a7a68241fb7527b33c8d147 6341 admin optional 
fscrypt_0.2.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEVhrVhe7XZpIbqN2W1lhhiD4BTbkFAl6wFogSHHBhcmlkZUBk
ZWJpYW4ub3JnAAoJENZYYYg+AU25XrsIAIQmOVCOYyfxSbUDSRg1uAHpVmt2UV1B
cY1oPcZM7k48aYh6vO3lUO0vGSu6cZrnZrq5LuDaeqMPTsKSSpM1xcpExW4r+1e8
HFNn7jjkF6je0fi8oaI5o4x471MszgXp5agXvUHCwKMK4D8KvV2le4WFgTF8bdpz
CreBDtVujIQwzkqBuw3zXgVB90sRJ0z+wjq8lVydHj/qUuuAUjk51vH339n8cwVS
1HgZjLoF2qGrYE9+K3vF69NKMQoykooVzSs1A2khQt5VDnPVCliKkR5P3WUACjfk
85wyW1xbK86QZrW2T1yO5W60HCxWEvGzesrg7aaN4k2rSzWfT3pqKu0=
=wna0
-END PGP SIGNATURE End Message ---

Bug#958379: marked as done (kdenlive: Audio recording fails due to lack of gstreamer1.0plugins-bad package as a dependency)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 13:04:21 +
with message-id 
and subject line Bug#958379: fixed in kdenlive 20.04.0-1
has caused the Debian Bug report #958379,
regarding kdenlive: Audio recording fails due to lack of 
gstreamer1.0plugins-bad package as a dependency
to be marked as done.

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

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


-- 
958379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdenlive
Version: 19.12.3-2
Severity: important
Tags: patch

Dear Maintainer,

The audio recording feature of current kdenlive will only work if
gstreamer1.0-plugins-bad is already installed. Otherwise it will fail
since QMediaRecorder function depends on gstreamer plugins. I tested with
gstreamer1.0-plugins-good and gstreamer1.0-plugins-bad seperately.
gstreamer1.0-plugins-bad install fixed this issue.

Error reported:

  start recording 2
  QMediaRecorder::FormatError : Failed to build media capture pipeline.
    ERROR : QMediarecorder - Capture failed

Please add gstreamer1.0-plugins-bad to the dependency list. 

Thanks,
Akhil

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

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 kdenlive depends on:
ii  ffmpeg 7:4.2.2-1+b1
ii  kded5  5.62.0-1+b1
ii  kdenlive-data  19.12.3-2
ii  kinit  5.62.0-1+b1
ii  kio5.62.1-2+b1
ii  libc6  2.30-4
ii  libkf5archive5 5.62.0-1
ii  libkf5bookmarks5   5.62.0-1+b1
ii  libkf5completion5  5.62.0-1+b1
ii  libkf5configcore5  5.62.0-1+b1
ii  libkf5configgui5   5.62.0-1+b1
ii  libkf5configwidgets5   5.62.0-1+b1
ii  libkf5coreaddons5  5.62.0-1
ii  libkf5crash5   5.62.0-1+b1
ii  libkf5dbusaddons5  5.62.0-1
ii  libkf5declarative5 5.62.0-1+b2
ii  libkf5filemetadata35.62.0-1+b1
ii  libkf5guiaddons5   5.62.0-2
ii  libkf5i18n55.62.0-1
ii  libkf5iconthemes5  5.62.0-1+b1
ii  libkf5itemviews5   5.62.0-1+b1
ii  libkf5jobwidgets5  5.62.0-1+b1
ii  libkf5kiocore5 5.62.1-2+b1
ii  libkf5kiofilewidgets5  5.62.1-2+b1
ii  libkf5kiowidgets5  5.62.1-2+b1
ii  libkf5newstuff55.62.0-1+b1
ii  libkf5notifications5   5.62.0-1+b1
ii  libkf5notifyconfig55.62.0-1+b1
ii  libkf5purpose-bin  5.62.0-2+b1
ii  libkf5purpose5 5.62.0-2+b1
ii  libkf5service-bin  5.62.0-1
ii  libkf5service5 5.62.0-1
ii  libkf5solid5   5.62.0-2
ii  libkf5widgetsaddons5   5.62.0-1+b1
ii  libkf5xmlgui5  5.62.0-1+b1
ii  libmlt++3  6.20.0-2+b1
ii  libmlt66.20.0-2+b1
ii  libqt5concurrent5  5.12.5+dfsg-9
ii  libqt5core5a   5.12.5+dfsg-9
ii  libqt5dbus55.12.5+dfsg-9
ii  libqt5gui5 5.12.5+dfsg-9
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5network5 5.12.5+dfsg-9
ii  libqt5qml5 5.12.5-5
ii  libqt5quick5   5.12.5-5
ii  libqt5quickwidgets55.12.5-5
ii  libqt5svg5 5.12.5-2
ii  libqt5webkit5  5.212.0~alpha4-1
ii  libqt5widgets5 5.12.5+dfsg-9
ii  libqt5xml5 5.12.5+dfsg-9
ii  librttr-core0.9.6  0.9.6+dfsg1-3
ii  libstdc++6 10-20200411-1
ii  melt   6.20.0-2+b1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2   5.12.5-5
ii  qml-module-qtquick-controls5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs 5.12.5-1+b1
ii  qml-module-qtquick-layouts 5.12.5-5
ii  qml-module-qtquick-window2 5.12.5-5
ii  qml-module-qtquick25.12.5-5

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

Bug#959448: marked as done (otrs2: CVE-2020-1774)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 13:04:49 +
with message-id 
and subject line Bug#959448: fixed in otrs2 6.0.28-1
has caused the Debian Bug report #959448,
regarding otrs2: CVE-2020-1774
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.)


-- 
959448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otrs2
Version: 6.0.27-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for otrs2.

CVE-2020-1774[0]:
| When user downloads PGP or S/MIME keys/certificates, exported file has
| same name for private and public keys. Therefore it's possible to mix
| them and to send private key to the third-party instead of public key.
| This issue affects ((OTRS)) Community Edition: 5.0.42 and prior
| versions, 6.0.27 and prior versions. OTRS: 7.0.16 and prior versions.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-1774
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1774
[1] https://otrs.com/release-notes/otrs-security-advisory-2020-11/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: otrs2
Source-Version: 6.0.28-1
Done: =?utf-8?q?Patrick_Matth=C3=A4i?= 

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated otrs2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 13:32:51 +0200
Source: otrs2
Architecture: source
Version: 6.0.28-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Closes: 959448
Changes:
 otrs2 (6.0.28-1) unstable; urgency=high
 .
   * New upstream release.
 - Fixes CVE-2020-1774, also known as OSA-2020-11: When user downloads PGP 
or
   S/MIME keys/certificates, exported file has same name for private and
   public keys. Therefore it’s possible to mix them and to send private key
   to the third-party instead of public key.
   Closes: #959448
   * Add new dependency libmath-random-secure-perl.
   * Upgrade to debhelper-compat 13.
Checksums-Sha1:
 3db7fc57b3da0779cd004769b9d0b8a652fac96a 1817 otrs2_6.0.28-1.dsc
 7168f7094cb11fb9f475b473577aadaaac9e8350 25785989 otrs2_6.0.28.orig.tar.bz2
 086cf44e4740f7fc6607545dce414307fda120f5 30832 otrs2_6.0.28-1.debian.tar.xz
 20cddec92faf688c831e987cfb800b984e5c2d74 5917 otrs2_6.0.28-1_source.buildinfo
Checksums-Sha256:
 f46f317ac8f36b4c24190ebd951b03e4520e89e8d7d97a8c555d351128cb652d 1817 
otrs2_6.0.28-1.dsc
 7c04d581689423863037dc12a37ad5cf48815522c23a19defe46a68d617319b8 25785989 
otrs2_6.0.28.orig.tar.bz2
 1ffa3e67591e87147d2e808fb613cf3f293eb928ee8ba371bc71241a4ea33293 30832 
otrs2_6.0.28-1.debian.tar.xz
 23f31eb2985263bd8d3ccb85a45ae31bf6f5ba311eaf80cc5aef51516beedccc 5917 
otrs2_6.0.28-1_source.buildinfo
Files:
 b3feb520b4157f3ad38b69888b99228a 1817 non-free/web optional otrs2_6.0.28-1.dsc
 70fde076204f5c79234aa3d61b59e74f 25785989 non-free/web optional 
otrs2_6.0.28.orig.tar.bz2
 fbf2a83a3176de606f7d91d4b2640d38 30832 non-free/web optional 
otrs2_6.0.28-1.debian.tar.xz
 04bf8ec672cad344f004c777efa51ec0 5917 non-free/web optional 
otrs2_6.0.28-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAl6wDjoACgkQEtmwSpDL
2OTyaA//XMQ4Mjvfr10Q1RioZiFE+cT/dlCxgtSjiCil3LvX1D+W6tAaCTg0Y8FR
/kPmxa9N++4Kgy6vnBN/7rBdOvfPod9BdBdtpVhBlpVSUvC5TiXa27KB5YOhxY9j
uQIkZzimoe2o8MNQ9ClLwWCgQowniSBeAow+lUknVsehcM+qzh7uH6jDGfNB76eR
wbTarLx5UaMI3INhmXgAjCFZuYxlpmw//hAC2lyn05m9miIjez5f8NBwu+jJSoOR
IT7Zb0DYEJUeIPEJieO2MZMnrZOaZv7IpzMkevUA7QLkmioK2QLrtgCG4uRWEPKX
rpRH4t7FwaCNN7iWOUd4k7rwCwc52LVJpai3a8jXM1YAOdpK/6e+XM4GHl/vxXov
c0pV3MrQYIc6AYnYBlxOSgV+o2v8EMItEYtWhfSD65lKq+UCfE5ZPzhf3uMuR+ey
5phV+ldRl7rDgLcMKds5JbsIrR6oergvyjY3SOPSk

Processed: RFS: vbetool/1.1-5 [ITA] -- run real-mode video BIOS code to alter hardware state

[Debian Bug Tracking System]

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

> close 959660
Bug #959660 [sponsorship-requests] RFS: vbetool/1.1-5 [ITA] -- run real-mode 
video BIOS code to alter hardware state
Marked Bug as done
> stop
Stopping processing here.

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

Bug#959514: marked as done (clementine: Please build again on all architectures)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 12:33:27 +
with message-id 
and subject line Bug#959514: fixed in clementine 
1.4.0~rc1+git174-gcb64d9705+dfsg-2
has caused the Debian Bug report #959514,
regarding clementine: Please build again on all architectures
to be marked as done.

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

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


-- 
959514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clementine
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-1
Severity: normal
Tags: ftbfs

Some of these OpenGL header problems have been fixed,
and clementine builds for me on armel.
--- End Message ---
--- Begin Message ---
Source: clementine
Source-Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-2
Done: Thomas Pierson 

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

Debian distribution maintenance software
pp.
Thomas Pierson  (supplier of updated clementine 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 11:00:20 +0200
Source: clementine
Architecture: source
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Pierson 
Changed-By: Thomas Pierson 
Closes: 959513 959514
Changes:
 clementine (1.4.0~rc1+git174-gcb64d9705+dfsg-2) unstable; urgency=medium
 .
   * Build now on all architectures since Qt/OpenGL build issues have been
 fixed for armel/armhf. (Closes: #959514)
   * Update package description in debian/control file. (Closes: #959513)
   * Update and convert the manpage from docbook to usual groff man format and
 remove build-depend on docbook-to-man.
   * Remove obsolete macros declaration in debian/rules.
   * Use new debhelper compatibility specification by setting a build-depend
 instead of debian/compat and update compatibility to debhelper 13.
   * Remove unnecessary parallel option in debian/rules file with debhelper 13.
Checksums-Sha1:
 a03ca7a7e8ae8116ff196331081669a798a13936 2569 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 e92509817715e219249e59cfa150e58d77bdcb95 19428 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 864f5c2a9e774ddbed72329f15c591af9b42ea00 17408 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 57e688b8b7b40c612094cf7fd15734a4255cd9daae3399da4affc858b211e40a 2569 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 7e16976d7bde21df2f70156a42c264e307944c68702303629ef23f89e54fa5d1 19428 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 44aee2482661bdddc046c73e73ac2cf06d786981bfcb02e0dd7558aa1e690d71 17408 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo
Files:
 82d7aba798f1efff63af10d252fc3138 2569 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 9dc36d51313f0fd1a99a189de9bcea37 19428 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 463736477f392c7d61de14b6157adee3 17408 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE1ep0XAsfqTLrXPfadxdQdm4ccgsFAl6wBdQACgkQdxdQdm4c
cguntg//bp4NoKiAs8gGsr9ZuZ82DKSx21Viu5TtdNrtDQzr8Kp/JkHa05j8cehl
f2ZjUgPVmm+3WIwUvMi09a2biBchbjq18ol3iMs/yxiZtIZlIy1clXb8DSX5JZ1R
pp9LL9+TJd7JqFC/eZjklFo/AB6Bv1ZBcURa2/wjQrsQ1Z0tmff9V2YRt+oZ1RQg
e+W3QnElTbtcCf+/AgG4hskGz1LuK3tqYNirK2PqjQXS3mEtRUXVaZUY4KBuox23
HvZm83nroWmPAxJgwgBXaZvoOoyEG12X6U/QEpzgqfVk1zKNeekr+3UvyS4tN3Yr
BkVqJXpjspIunEhywn9gvh9tO5vmfYdh6FbWYL2k4Y0nfCtORk0RFXdEhzrQP1cj
Nl4wuAWQZMEs/jm9eKK759dUV/zxrBmjTtSup2BFSfVquuCm8B+ut1ndHK2fRuT7
38iwnjwAlMnkhb5OPgEr6l/pHKI8P6lfvly94ho7PB+u1RbxaAd5nuMcH6xJfr1b
1QlsqoDpCCSPyZS18q2SPvwLU030MFyHSHO6i7KiC66B44EkQssiC4pK8W+VRyu2
Mz1UoFnMYAEMf+xNA5fukXaLP/tRkEa4bi6k4U+XYz1sdapZmwagOCb2COEjnVTQ
XGnnzY1ryscPgl3dJJkeBmPIKemPunWS58t9/mUGzeBjL/FvmZM=
=pdPv
-END PGP SIGNATURE End Message ---

Bug#959513: marked as done (clementine: Package descrition needs updating)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 12:33:27 +
with message-id 
and subject line Bug#959513: fixed in clementine 
1.4.0~rc1+git174-gcb64d9705+dfsg-2
has caused the Debian Bug report #959513,
regarding clementine: Package descrition needs updating
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.)


-- 
959513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clementine
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-1
Severity: minor

I haven't checked the rest, but the following looks 10 years old:
 It is largely a port of Amarok 1.4, with some features rewritten to take
 advantage of Qt4.
--- End Message ---
--- Begin Message ---
Source: clementine
Source-Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-2
Done: Thomas Pierson 

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

Debian distribution maintenance software
pp.
Thomas Pierson  (supplier of updated clementine 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 11:00:20 +0200
Source: clementine
Architecture: source
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Pierson 
Changed-By: Thomas Pierson 
Closes: 959513 959514
Changes:
 clementine (1.4.0~rc1+git174-gcb64d9705+dfsg-2) unstable; urgency=medium
 .
   * Build now on all architectures since Qt/OpenGL build issues have been
 fixed for armel/armhf. (Closes: #959514)
   * Update package description in debian/control file. (Closes: #959513)
   * Update and convert the manpage from docbook to usual groff man format and
 remove build-depend on docbook-to-man.
   * Remove obsolete macros declaration in debian/rules.
   * Use new debhelper compatibility specification by setting a build-depend
 instead of debian/compat and update compatibility to debhelper 13.
   * Remove unnecessary parallel option in debian/rules file with debhelper 13.
Checksums-Sha1:
 a03ca7a7e8ae8116ff196331081669a798a13936 2569 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 e92509817715e219249e59cfa150e58d77bdcb95 19428 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 864f5c2a9e774ddbed72329f15c591af9b42ea00 17408 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 57e688b8b7b40c612094cf7fd15734a4255cd9daae3399da4affc858b211e40a 2569 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 7e16976d7bde21df2f70156a42c264e307944c68702303629ef23f89e54fa5d1 19428 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 44aee2482661bdddc046c73e73ac2cf06d786981bfcb02e0dd7558aa1e690d71 17408 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo
Files:
 82d7aba798f1efff63af10d252fc3138 2569 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.dsc
 9dc36d51313f0fd1a99a189de9bcea37 19428 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2.debian.tar.xz
 463736477f392c7d61de14b6157adee3 17408 sound optional 
clementine_1.4.0~rc1+git174-gcb64d9705+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE1ep0XAsfqTLrXPfadxdQdm4ccgsFAl6wBdQACgkQdxdQdm4c
cguntg//bp4NoKiAs8gGsr9ZuZ82DKSx21Viu5TtdNrtDQzr8Kp/JkHa05j8cehl
f2ZjUgPVmm+3WIwUvMi09a2biBchbjq18ol3iMs/yxiZtIZlIy1clXb8DSX5JZ1R
pp9LL9+TJd7JqFC/eZjklFo/AB6Bv1ZBcURa2/wjQrsQ1Z0tmff9V2YRt+oZ1RQg
e+W3QnElTbtcCf+/AgG4hskGz1LuK3tqYNirK2PqjQXS3mEtRUXVaZUY4KBuox23
HvZm83nroWmPAxJgwgBXaZvoOoyEG12X6U/QEpzgqfVk1zKNeekr+3UvyS4tN3Yr
BkVqJXpjspIunEhywn9gvh9tO5vmfYdh6FbWYL2k4Y0nfCtORk0RFXdEhzrQP1cj
Nl4wuAWQZMEs/jm9eKK759dUV/zxrBmjTtSup2BFSfVquuCm8B+ut1ndHK2fRuT7
38iwnjwAlMnkhb5OPgEr6l/pHKI8P6lfvly94ho7PB+u1RbxaAd5nuMcH6xJfr1b
1QlsqoDpCCSPyZS18q2SPvwLU030MFyHSHO6i7KiC66B44EkQssiC4pK8W+VRyu2
Mz1UoFnMYAEMf+xNA5fukXaLP/tRkEa4bi6k4U+XYz1sdapZmwagOCb2COEjnVTQ
XGnnzY1ryscPgl3dJJkeBmPIKemPunWS58t9/mUGzeBjL/FvmZM=
=pdPv
-END PGP SIGNATURE End Message ---

Bug#949927: marked as done (mirror listing update for debian.parspack.com)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 12:24:18 +
with message-id <5eb0097251a4c_3a72af0d4b485bc32...@godard.mail>
and subject line Bug#949927 fixed in mirrors
has caused the Debian Bug report #949927,
regarding mirror listing update for debian.parspack.com
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.)


-- 
949927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: debian.parspack.com
Type: leaf
Archive-architecture: amd64 arm64 i386
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Farid Zarazvand 
Country: IR Iran, Islamic Republic of
Location: Tehran
Sponsor: ParsPack https://parspack.com/




Trace Url: http://debian.parspack.com/debian/project/trace/
Trace Url: http://debian.parspack.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://debian.parspack.com/debian/project/trace/debian.parspack.com
--- End Message ---
--- Begin Message ---
Hello,

Bug #949927 in mirrors reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/mirror-team/masterlist/-/commit/921b7aaf1aa334c1ebc44872a35e848b0528f26b


Add debian.parspack.com

Closes: #949927


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/949927--- End Message ---

Processed: forcibly merging 955112 955059

[Debian Bug Tracking System]

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

> forcemerge 955112 955059
Bug #955112 {Done: Daniele Tricoli } 
[src:sphinxcontrib-spelling] sphinxcontrib-spelling: FTBFS with Sphinx 2.4: 
dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned 
exit code 13
Bug #955059 [src:sphinxcontrib-spelling] django-tables: FTBFS with Sphinx 2.4: 
AttributeError: 'Sphinx' object has no attribute 'info'
Severity set to 'important' from 'serious'
Marked Bug as done
Added indication that 955059 affects src:django-tables
Marked as fixed in versions sphinxcontrib-spelling/4.3.0-1.
Marked as found in versions sphinxcontrib-spelling/4.2.0-2.
Merged 955059 955112
> thanks
Stopping processing here.

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

Bug#959595: marked as done (python-xarray: FTBFS: ImportError: cannot import name 'main' from 'sphinx' (/usr/lib/python3/dist-packages/sphinx/__init__.py))

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 11:49:38 +
with message-id 
and subject line Bug#959595: fixed in python-xarray 0.15.1-2
has caused the Debian Bug report #959595,
regarding python-xarray: FTBFS: ImportError: cannot import name 'main' from 
'sphinx' (/usr/lib/python3/dist-packages/sphinx/__init__.py)
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx3-build -b html -d _build/doctrees   . _build/html
> Traceback (most recent call last):
>   File "/<>/debian/sphinx3-build", line 11, in 
> from sphinx import main, make_main
> ImportError: cannot import name 'main' from 'sphinx' 
> (/usr/lib/python3/dist-packages/sphinx/__init__.py)
> make[2]: *** [Makefile:57: html] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/python-xarray_0.15.1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-xarray 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 12:05:55 +0100
Source: python-xarray
Architecture: source
Version: 0.15.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 959595
Changes:
 python-xarray (0.15.1-2) unstable; urgency=medium
 .
   * Drop obsolete sphinx3-build hack which breaks on sphinx 2.4 ;
 Closes: #959595
Checksums-Sha1:
 3676081cc2e78b992d689d95ff3023b5832d14a1 3289 python-xarray_0.15.1-2.dsc
 853148b57b2cebe606deec64628f4148d42d835f 13372 
python-xarray_0.15.1-2.debian.tar.xz
Checksums-Sha256:
 8c36e419ebbec2fd19969291ada18ef674aae2ac2ff4edfe92fd52558fc35373 3289 
python-xarray_0.15.1-2.dsc
 3fc47f4a1371ef07d886497b221ab96fa9d29d6954ea17b2f2bbf3ddb718af65 13372 
python-xarray_0.15.1-2.debian.tar.xz
Files:
 04ec29d8091910235f1f065cf45ea6f9 3289 python optional 
python-xarray_0.15.1-2.dsc
 a8455222a193cfb1a9632b7bd06e7922 13372 python optional 
python-xarray_0.15.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl6v+6kACgkQy+a7Tl2a
06Un7A//edqJ+y5+HZnr7zxgHudgy2bs/B+jyHQUPJuL0zweeSs4nV7ieUjrCrAN
i1HBqSJx9tFW9tcB+bmaqr45T+Xikwt4pkafyE80i/MuoJSRdIIfD2tC3Nyp23e0
RE0VeHeHgvluFFyqKjAkD8qDDz6N5+4JOWTlpEkdPcao+NOAFycC8chJHTpDksx9
U+W+wIiCnvrRir7YGWSVgKiQdO1XGz1ZTpArQZDe9RdKP7sBoU5Jv5BFvm7U0l1a
RDjM8XWNp76bWeuY79YGqxwAmCJEwcp5E+IALosXLbyzVeATrkxLn7XCAg/tjf16
r/w1xy1quyfyPbzhE18q5ic99o/JUL0aSZH0mTOfOp6wm6HrR8/iBswM1dIm9wIS
8r7AH5mtEZtYli5Du0gdqxCp5DVaXY+XIbbKYbIUAzN+hAJUpRDk8SJl1oZPjqkN
lav19kibMtf97wAkaJIEhzMdZPNvOU5VAI1GuYq3kzFTzFIRDhJMMnvOwYcLQvuq
ieZpyXMc9hrEa1B8dN9gm7mWpDxuW2B8PIRPBHHxdwelFCrGZh4Hli1U9Cmg2dKu
7Vj+FH82GyD1afzbexePI372VlFW13ovCJ1aIkOTb5V7d5nftq98ws0FqVoBb+Ly
i9yxsD9Ol9lMhoBcJbZkWUTZiyNO/LcMDpmYc3DoMkZ77+2cCXo=
=JAUi
-END PGP SIGNATURE End Message ---

Bug#939491: marked as done (compiz-boxmenu: Depends on python2)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 11:33:23 +
with message-id 
and subject line Bug#939491: fixed in compiz-boxmenu 1.1.12-3
has caused the Debian Bug report #939491,
regarding compiz-boxmenu: Depends on python2
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.)


-- 
939491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: compiz-boxmenu
Version: 1.1.12-1
Severity: important
Tags: sid bullseye upstream
Forwarded: https://gitlab.com/compiz/compiz-boxmenu/issues/7
User: debian-pyt...@lists.debian.org
Usertags: py2removal

compiz-boxmenu depends on python2 (and I tried, it's not just a matter
of setting PYTHONBIN to /usr/bin/python3)

Samuel

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

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

Versions of packages compiz-boxmenu depends on:
ii  libc6   2.28-10
ii  libdbus-1-3 1.12.16-1
ii  libdbus-glib-1-20.110-4
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.60.6-2
ii  libgtk2.0-0 2.24.32-3
ii  libpango-1.0-0  1.42.4-7
ii  libwnck22   2.30.7-6

compiz-boxmenu recommends no packages.

compiz-boxmenu suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: compiz-boxmenu
Source-Version: 1.1.12-3
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated compiz-boxmenu 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 13:11:57 +0200
Source: compiz-boxmenu
Binary: compiz-boxmenu compiz-boxmenu-dbgsym
Architecture: source
Version: 1.1.12-3
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 compiz-boxmenu - Compiz Reloaded - daemon and clients providing pop-up menus
Closes: 939491
Changes:
 compiz-boxmenu (1.1.12-3) unstable; urgency=medium
 .
   * patches/clang: Fix build with clang.
   * patches/python3: Add python3 support (Closes: Bug#939491).
   * patches/gerror: Fix accessing GError.
   * control: Drop unused python-dev build-dep. Add missing python and gir
 dependencies.
   * rules: Set PYTHONBIN to /usr/bin/python3.
Checksums-Sha1:
 f871f108520ea4a32d580cc4958a24faf8bc5bdb 1961 compiz-boxmenu_1.1.12-3.dsc
 084fefa8570a02e4f938f6b4a7c33873375652aa 13860 
compiz-boxmenu_1.1.12-3.debian.tar.xz
Checksums-Sha256:
 5f613c1b6b35a03accfcf9a6fe5ace0019e4582bcff261e91e61033038d4dccd 1961 
compiz-boxmenu_1.1.12-3.dsc
 f3ce2751d3f9b39022a5f2f06cdb7fac3b752cce83f798d00adb5c7b1c6417d3 13860 
compiz-boxmenu_1.1.12-3.debian.tar.xz
Files:
 3fe74e6d8b3db57fb7cc0e3e4cff1381 1961 x11 optional compiz-boxmenu_1.1.12-3.dsc
 b4735b9d7a4f9ef3084b06ea9b5765bd 13860 x11 optional 
compiz-boxmenu_1.1.12-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXtnoVvfWxur1EWehjTXDVXILuv0FAl6v+ZQACgkQjTXDVXIL
uv1/fg/+M2ds/VbfTPfNDIygHxqdImqNHJ/cOmFHDhOb+HLeS2U3AS2pGLIjaXDj
JI9tsX5B2GG5wjaQeOLP5D2l58ApcBvvXeD9hIcVMHU7Z5IO0j2vGOU8RsBG6lgC
ZO7gLnW2j28E2gDmS4itdxKRqZnAfUWrGaHPMjQFpKTrPIEbaRirYZe8N/uetD4L
yhbuDZmCEugjQuWstpds1WsPetALTOdz3/vMHu+ZbMzTxDCMx7CQWoDqtfLPZyAg
e1eiSNRzw88lokYfOhf1

Bug#958663: marked as done (libghc-hs-bibutils-dev: FTBFS with new libbibutils7 (library transition))

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 14:27:53 +0300
with message-id <20200504112753.GA18334@localhost>
and subject line Fixed in 6.10.0.0-1
has caused the Debian Bug report #958663,
regarding libghc-hs-bibutils-dev: FTBFS with new libbibutils7 (library 
transition)
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.)


-- 
958663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-hs-bibutils-dev
Version: 6.7.0.0-1
Severity: important
Tags: patch
Control: block 958662 by -1

Dear Haskell Group,

I am preparing the transition from libbibutils6 to libbibutils7, which is in 
experimental.

I have just filed a bug #958662 against release.debian.org to ask for a 
transition slot.

libbibutils6 has 4 reverse dependencies that are maintained inside your group. 
Here are the results of their builds against libbibutils7:

* haskell-hs-bibutils   FTBFS, but can be fixed with a simple patch
* haskell-pandoc-citeproc   build OK
* haskell-blogliteratelybuild OK
* haskell-hakyllbuild OK

This is thus a blocking bug for #958662, which can be solved with the enclosed 
patch. Alternatively, I have just seen that haskell-hs-bibutils' upstream has a 
new version ready, doing exactly the same as my enclosed patch. Thus, as soon 
as libbibutils7 enters unstable, you will be able to package the new upstream 
version and everything should be OK.

Best regards,
Pierre
Description: Changes for the transition to libbibutils7
Author: Pierre Gruet 
Last-Update: 2020-04-18

--- a/src/Text/Bibutils.hsc
+++ b/src/Text/Bibutils.hsc
@@ -137,13 +137,13 @@
 -- | A type for storing the C struct with the bibliography data.
 -- Mostly opaque to the Haskell side. See 'numberOfRefs' to retrieve
 -- the number of references stored in the struct.
-newtype Bibl = Bibl { nrefs :: CLong }
+newtype Bibl = Bibl { n :: CLong }
 
 instance Storable Bibl where
 sizeOf_ = #{size  bibl}
 alignment _ = #{alignment bibl}
-peek p  = #{peek  bibl, nrefs } p >>= return . Bibl
-poke p (Bibl n) = #{poke  bibl, nrefs } p n
+peek p  = #{peek  bibl, n } p >>= return . Bibl
+poke p (Bibl nb) = #{poke  bibl, n } p nb
 
 -- | Initialize the 'Bibl' C struct. Usually the first function being
 -- called.
@@ -160,7 +160,7 @@
 -- | Retrieve the number of references from a 'Bibl' C struct.
 numberOfRefs :: ForeignPtr Bibl -> IO Int
 numberOfRefs b
-= withForeignPtr b $ \cb -> peek cb >>= return . fromIntegral . nrefs
+= withForeignPtr b $ \cb -> peek cb >>= return . fromIntegral . n
 
 -- | A type for storing the Param C struct. It should be accessed with
 -- the functions provided, such as 'setCharsetIn', etc.
@@ -395,7 +395,7 @@
 c_bibl_addtocorps cparam centry
 
 bibl_reporterr :: Status -> IO ()
-bibl_reporterr (Status n) = c_bibl_reporterr n
+bibl_reporterr (Status nb) = c_bibl_reporterr nb
 
 newtype BiblioIn  = BiblioIn  { unBiblioIn  :: CInt }
 deriving ( Eq )
--- End Message ---
--- Begin Message ---
Version: 6.10.0.0-1

https://buildd.debian.org/status/package.php?p=haskell-hs-bibutils&suite=sid

cu
Adrian--- End Message ---

Bug#959542: marked as done (haskell-hs-bibutils: FTBFS: Bibutils.hsc:145:21: error: ‘bibl’ {aka ‘struct ’} has no member named ‘nrefs’; did you mean ‘ref’?)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 14:27:53 +0300
with message-id <20200504112753.GA18334@localhost>
and subject line Fixed in 6.10.0.0-1
has caused the Debian Bug report #958663,
regarding haskell-hs-bibutils: FTBFS: Bibutils.hsc:145:21: error: ‘bibl’ {aka 
‘struct ’} has no member named ‘nrefs’; did you mean ‘ref’?
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.)


-- 
958663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hs-bibutils
Version: 6.7.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> DC-Build-Header: haskell-hs-bibutils 6.7.0.0-1 / 2020-05-03 05:00:29 +
> DC-Task: type:rebuild-full source:haskell-hs-bibutils version:6.7.0.0-1 
> chroot:unstable esttime:94 
> logfile:/tmp/haskell-hs-bibutils_6.7.0.0-1_unstable.log modes:
> DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source 
> --apt-update -d unstable -v --no-run-lintian haskell-hs-bibutils_6.7.0.0-1'
> sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 
> ip-172-31-9-59.eu-central-1.compute.internal
> 
> +==+
> | haskell-hs-bibutils 6.7.0.0-1 (amd64)Sun, 03 May 2020 05:00:29 
> + |
> +==+
> 
> Package: haskell-hs-bibutils
> Version: 6.7.0.0-1
> Source Version: 6.7.0.0-1
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> Build Type: full
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-amd64-sbuild-6d40e279-68ad-4a6a-af56-b0a764770920' 
> with '<>'
> I: NOTICE: Log filtering will replace 
> 'build/haskell-hs-bibutils-NGAJvF/resolver-VeStCY' with '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 http://127.0.0.1:12990/debian sid InRelease [146 kB]
> Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main amd64 Packages.diff/Index [27.9 
> kB]
> Get:4 http://127.0.0.1:12990/debian sid/main Sources 2020-05-02-0208.16.pdiff 
> [3982 B]
> Get:5 http://127.0.0.1:12990/debian sid/main Sources 2020-05-02-0807.49.pdiff 
> [10.9 kB]
> Get:6 http://127.0.0.1:12990/debian sid/main Sources 2020-05-02-1412.30.pdiff 
> [12.9 kB]
> Get:7 http://127.0.0.1:12990/debian sid/main Sources 2020-05-02-2007.10.pdiff 
> [13.4 kB]
> Get:8 http://127.0.0.1:12990/debian sid/main Sources 2020-05-03-0208.39.pdiff 
> [9476 B]
> Get:8 http://127.0.0.1:12990/debian sid/main Sources 2020-05-03-0208.39.pdiff 
> [9476 B]
> Get:9 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-02-0208.16.pdiff [2772 B]
> Get:10 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-02-0807.49.pdiff [3238 B]
> Get:11 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-02-1412.30.pdiff [7641 B]
> Get:12 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-02-2007.10.pdiff [10.5 kB]
> Get:13 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-03-0208.39.pdiff [18.4 kB]
> Get:13 http://127.0.0.1:12990/debian sid/main amd64 Packages 
> 2020-05-03-0208.39.pdiff [18.4 kB]
> Fetched 295 kB in 1s (284 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Calculating upgrade...
> The following packages will be upgraded:
>   gcc-10-base libatomic1 libcc1-0 libgcc-s1 libgomp1 libitm1 liblsan0
>   libquadmath0 libstdc++6 libtsan0 libubsan1
> 11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1636 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://127.0.0.1:12990/debian sid/main amd64 libatomic1 amd64 
> 10-20200502-1 [9048 B]
> Get:2 http://127.0.0.1:12990/debian sid/main amd64 libubsan1 amd64 
> 10-20200502-1 [134 kB]
> Get:3 http://127.0.0.1:12990/debian sid/main amd64 libtsan0 amd64 
> 10-20200502-1 [313 kB]
> Get:4 http://127.0.0.1:12990/debian sid/main amd64 gcc-10-base amd64 
> 10-20200502-1 [197 kB]
> Get:5 http://127.0.0.1:12990/debian sid/main amd64 libstdc++6 amd64 
> 10-20200502-1 [492 kB]
> Get:6 http://127.0.0.

Bug#674887: marked as done (ITA: vbetool -- run real-mode video BIOS code to alter)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 11:19:26 +
with message-id 
and subject line Bug#674887: fixed in vbetool 1.1-5
has caused the Debian Bug report #674887,
regarding ITA: vbetool -- run real-mode video BIOS code to alter
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.)


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

The current maintainer of vbetool, Bradley Smith ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: vbetool
Binary: vbetool
Version: 1.1-2
Maintainer: Bradley Smith 
Build-Depends: debhelper (>= 7), libx86-dev, libpci-dev, quilt
Architecture: i386 amd64 lpia kfreebsd-i386 kfreebsd-amd64
Standards-Version: 3.8.0
Format: 1.0
Files:
 d2e8a68f816515593fd488808e5da062 1183 vbetool_1.1-2.dsc
 fba8f4901f12370ad6df8725d840a33b 182379 vbetool_1.1.orig.tar.gz
 ec280a49700edd8bd1be3bc53e4b7aeb 4221 vbetool_1.1-2.diff.gz
Vcs-Browser: http://git.brad-smith.co.uk/?p=debian/pkg-vbetool.git
Vcs-Git: http://git.brad-smith.co.uk/git/debian/pkg-vbetool.git
Checksums-Sha1:
 c4f53508876c31747f3a0e702e52f30d7ad520b1 1183 vbetool_1.1-2.dsc
 801c9f0d29d6089822f66eeae4a6a2e4ab5a279e 182379 vbetool_1.1.orig.tar.gz
 2150cf2db8b1b20e365b4e41be04ce380a51b3af 4221 vbetool_1.1-2.diff.gz
Checksums-Sha256:
 01957510f16add93d0fa6c46eb9eaa2973018d1d86d7dfbfb56f0d8c13bf70e4 1183 
vbetool_1.1-2.dsc
 55a1e667249b4b38b6d48e74950c1dadd4d8b9802e358956fd4050508aae12d3 182379 
vbetool_1.1.orig.tar.gz
 8ccf7641db227df4d995a05925c0a9e34b7541c9f8bf2cf29a28bb309a42d022 4221 
vbetool_1.1-2.diff.gz
Homepage: http://www.codon.org.uk/~mjg59/vbetool/
Directory: pool/main/v/vbetool
Priority: source
Section: utils

Package: vbetool
Version: 1.1-2
Installed-Size: 60
Maintainer: Bradley Smith 
Architecture: amd64
Depends: libc6 (>= 2.7-1), libpci3, libx86-1 (>= 0.99-1), zlib1g (>= 1:1.1.4)
Description-en: run real-mode video BIOS code to alter hardware state
 vbetool uses lrmi in order to run code from the video BIOS. Currently, it
 is able to alter DPMS states, save/restore video card state and attempt to
 initialize the video card from scratch.
Homepage: http://www.codon.org.uk/~mjg59/vbetool/
Description-md5: 25fb7adf077cdb98dd6d1022be48eba4
Tag: hardware::video, interface::commandline, role::program, scope::utility,
 use::configuring
Section: utils
Priority: optional
Filename: pool/main/v/vbetool/vbetool_1.1-2_amd64.deb
Size: 11250
MD5sum: 1602701d42127b3bb1a808be4acd9302
SHA1: 5ac32cea949c97fa98a933064785aadb89eb4ec1
SHA256: 98bbb559113a6d53476059214c1435dd04a22145dcebcbf5d6e24990b5d430e6



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: vbetool
Source-Version: 1.1-5
Done: Seunghun Han 

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

Debian distribution maintenance software
pp.
Seunghun Han  (supplier of updated vbetool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 May 2020 00:45:10 +0900
Source: vbetool
Architecture: source
Version: 1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Seunghun Han 
Changed-By: Seunghun Han 
Closes: 674887
Changes:
 vbetool (1.1-5) unstable; urgency=medium
 .
   * New maintainer (Closes: #674887)
   * debian/control:
   - Bumped Standards-Version to 4.5.0.
   - Upgraded debhelper to 12.
   - Changed Vcs-* fields.
   - Added Rules-Requires-Root field.
   * debian/rules:
   - Changed the DEB_HOST_ARCH to /usr/share/dpkg/architecture.mk.
   * debian/copyright:
   - Added information to Upstream-Contact.
Checksums-Sha1:
 7dd4d63996b6f0a443c54a350415e3ab1d3e133b 19

Bug#956265: marked as done (sundials ftbfs, failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 14:05:07 +0300
with message-id <20200504110507.GA3249@localhost>
and subject line Re: Bug#956265: sundials ftbfs, failing tests
has caused the Debian Bug report #956265,
regarding sundials ftbfs, failing tests
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.)


-- 
956265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sundials
Version: 3.1.2+dfsg-3
Severity: serious
Tags: sid bullseye

sundials ftbfs, failing tests on all architectures. while seeing that first in
Ubuntu, I rechecked with current unstable, and see at least some tests failing:

[...]
82% tests passed, 16 tests failed out of 87

Total Test time (real) =   7.77 sec

The following tests FAILED:
 56 - test_nvector_mpi_4 (Failed)
 57 - test_nvector_mpi_4_1000_0 (Failed)
 58 - test_sunlinsol_spgmr_parallel_100_1_1_50_1e-3_0 (Failed)
 59 - test_sunlinsol_spgmr_parallel_100_1_2_50_1e-3_0 (Failed)
 60 - test_sunlinsol_spgmr_parallel_100_2_1_50_1e-3_0 (Failed)
 61 - test_sunlinsol_spgmr_parallel_100_2_2_50_1e-3_0 (Failed)
 62 - test_sunlinsol_spfgmr_parallel_100_1_50_1e-3_0 (Failed)
 63 - test_sunlinsol_spfgmr_parallel_100_2_50_1e-3_0 (Failed)
 64 - test_sunlinsol_spbcgs_parallel_100_1_50_1e-3_0 (Failed)
 65 - test_sunlinsol_spbcgs_parallel_100_2_50_1e-3_0 (Failed)
 66 - test_sunlinsol_sptfqmr_parallel_100_1_50_1e-3_0 (Failed)
 67 - test_sunlinsol_sptfqmr_parallel_100_2_50_1e-3_0 (Failed)
 70 - test_nvector_parhyp_4 (Failed)
 71 - test_nvector_parhyp_4_1_0 (Failed)
 86 - test_nvector_petsc_4 (Failed)
 87 - test_nvector_petsc_4_1000_0 (Failed)
Errors while running CTest
make[1]: *** [debian/rules:53: override_dh_auto_test] Error 8
make[1]: Leaving directory '/packages/tmp/p/sundials-3.1.2+dfsg'
make: *** [debian/rules:45: binary] Error 2

failing tests on Ubuntu:
https://launchpad.net/ubuntu/+source/sundials/3.1.2+dfsg-3ubuntu1
--- End Message ---
--- Begin Message ---
On Thu, Apr 09, 2020 at 08:53:07AM +0200, Matthias Klose wrote:
> Package: src:sundials
> Version: 3.1.2+dfsg-3
> Severity: serious
> Tags: sid bullseye
> 
> sundials ftbfs, failing tests on all architectures. while seeing that first in
> Ubuntu, I rechecked with current unstable, and see at least some tests 
> failing:
> 
> [...]
> 82% tests passed, 16 tests failed out of 87
> 
> Total Test time (real) =   7.77 sec
> 
> The following tests FAILED:
>  56 - test_nvector_mpi_4 (Failed)
>  57 - test_nvector_mpi_4_1000_0 (Failed)
>  58 - test_sunlinsol_spgmr_parallel_100_1_1_50_1e-3_0 (Failed)
>  59 - test_sunlinsol_spgmr_parallel_100_1_2_50_1e-3_0 (Failed)
>  60 - test_sunlinsol_spgmr_parallel_100_2_1_50_1e-3_0 (Failed)
>  61 - test_sunlinsol_spgmr_parallel_100_2_2_50_1e-3_0 (Failed)
>  62 - test_sunlinsol_spfgmr_parallel_100_1_50_1e-3_0 (Failed)
>  63 - test_sunlinsol_spfgmr_parallel_100_2_50_1e-3_0 (Failed)
>  64 - test_sunlinsol_spbcgs_parallel_100_1_50_1e-3_0 (Failed)
>  65 - test_sunlinsol_spbcgs_parallel_100_2_50_1e-3_0 (Failed)
>  66 - test_sunlinsol_sptfqmr_parallel_100_1_50_1e-3_0 (Failed)
>  67 - test_sunlinsol_sptfqmr_parallel_100_2_50_1e-3_0 (Failed)
>  70 - test_nvector_parhyp_4 (Failed)
>  71 - test_nvector_parhyp_4_1_0 (Failed)
>  86 - test_nvector_petsc_4 (Failed)
>  87 - test_nvector_petsc_4_1000_0 (Failed)
> Errors while running CTest
> make[1]: *** [debian/rules:53: override_dh_auto_test] Error 8
> make[1]: Leaving directory '/packages/tmp/p/sundials-3.1.2+dfsg'
> make: *** [debian/rules:45: binary] Error 2
> 
> failing tests on Ubuntu:
> https://launchpad.net/ubuntu/+source/sundials/3.1.2+dfsg-3ubuntu1

This seems to have been a temporary breakage in some build dependency 
that got fixed:
https://tests.reproducible-builds.org/debian/history/sundials.html

cu
Adrian--- End Message ---

Bug#958836: marked as done (vulkan-loader: autopkgtest failure: missing test dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 10:50:15 +
with message-id 
and subject line Bug#958836: fixed in vulkan-loader 1.2.135.0-3
has caused the Debian Bug report #958836,
regarding vulkan-loader: autopkgtest failure: missing test dependencies
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.)


-- 
958836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-loader
Version: 1.2.135.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

With a recent upload of vulkan-loader you added an autopkgtest, great.
However, it fails. I copied some of the output at the bottom of this
report. It seems you're missing some test dependencies.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=vulkan-loader

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vulkan-loader/4896628/log.gz

autopkgtest [21:25:19]: test libvulkan-dev: [---
+ CROSS_COMPILE=
+ cat
+ pkg-config --cflags --libs vulkan
/tmp/autopkgtest-lxc.wal_ek51/downtmp/build.IUw/src/debian/tests/libvulkan-dev:
32: pkg-config: not found
+ gcc -osimple simple.c
/tmp/autopkgtest-lxc.wal_ek51/downtmp/build.IUw/src/debian/tests/libvulkan-dev:
32: gcc: not found
autopkgtest [21:25:19]: test libvulkan-dev: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vulkan-loader
Source-Version: 1.2.135.0-3
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated vulkan-loader package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 13:33:06 +0300
Source: vulkan-loader
Architecture: source
Version: 1.2.135.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 958836
Changes:
 vulkan-loader (1.2.135.0-3) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * Add missing autopkgtests dependencies (Closes: #958836)
Checksums-Sha1:
 cb32b30b21fd0bdb3e9a5f26920f3c8d257572d9 2252 vulkan-loader_1.2.135.0-3.dsc
 31ab2675b606c162823edcad2d340166be0c4c34 8488 
vulkan-loader_1.2.135.0-3.debian.tar.xz
 287321ff89488ac838b0c9bf884cbc6971047326 7654 
vulkan-loader_1.2.135.0-3_source.buildinfo
Checksums-Sha256:
 dc5c8f94a65fab90dd0a31aa3832ef61122ee6952d6bf7f754c386ac2a5681c7 2252 
vulkan-loader_1.2.135.0-3.dsc
 411cfb645f771f87efe56689f580fe0c2e56f57abacf09d074a024f943429354 8488 
vulkan-loader_1.2.135.0-3.debian.tar.xz
 dc6ec7c20eaa8dd025831632585b9fe2a4ea71bc273cbd726a4ed482e2eee608 7654 
vulkan-loader_1.2.135.0-3_source.buildinfo
Files:
 6f1312e9117e6caacd65dc7e42c97414 2252 libs optional 
vulkan-loader_1.2.135.0-3.dsc
 6405681caf6c6e978e6efd23d697d70e 8488 libs optional 
vulkan-loader_1.2.135.0-3.debian.tar.xz
 5aca2febc9f6d57efbc11b6aa532c445 7654 libs optional 
vulkan-loader_1.2.135.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6v73gACgkQy3AxZaiJ
hNz5Aw//UCFf8DL84YpcxCtjNr1dQwqNtGV8unA1E/Ei+mc19E590dSapne5ee3W
b5yFAwVsZ2f4i9dG9oNVdHgwplvGS14obBHVIO2GY4eOxJUXcdA7ubqBeX7xj8Vd
fmSRbWQXqnE1VYBC5NVc3jCngED1/yNUOYykFQ7b4CCLnel+/FSyHhKDYmiRXGao
ZJ3XM/sl6/00k+vjxeB6FH8R1wxWf/yLZXiJZqf3/lKTo149vSHLH5JDCnDsKxz6
tdc8hK7AzyONWfvZ/Rdgw0lf4cUSF7vb/jE2s6ncJ7WOQxGPKlxkPZ5o8zQ5AKRa
rDEy0HfKou7FK8eocb0JChxIztwEdx7ac8PmXTlLOJE9t3cnjONR3eHRmlLBzN1c
cQ1Z28IHz9S7SlK1BI2QZqHWV6W4vep1aaDgE6EmV8DZ7q086/eHjFY0c3FYAUA3
rV835WGRfNv1Rl/fQEddPWTWq9e7nS/QLUxfntQrd14y/iRxxRttOYQSkGRsgijs
4ZS4GALRWjlsV1aIe08rBchWwrE82B98/Mx8URzDif4A5wGd4NbLO6P9brwhw1i4
V23F2cNNLpeNF0ajQvvvIJMXvX0anpr

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

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 10:48:39 +
with message-id 
and subject line Bug#956170: fixed in gnome-shell-extension-show-ip 8-6
has caused the Debian Bug report #956170,
regarding gnome-shell-extension-show-ip: 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.)


-- 
956170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-show-ip
Version: 8-5
Severity: important
Tags: bullseye sid upstream
Control: block 954422 by -1

GNOME Shell 3.36.x is currently in experimental, and should hopefully
be heading to unstable soon. Please check whether this extension is
compatible.

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 launches
gnome-shell-extension-prefs.desktop, which is now named
org.gnome.Extensions.desktop as a result of upstream changes.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-show-ip
Source-Version: 8-6
Done: Kyle Robbertze 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-show-ip, 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.
Kyle Robbertze  (supplier of updated 
gnome-shell-extension-show-ip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 12:36:44 +0200
Source: gnome-shell-extension-show-ip
Architecture: source
Version: 8-6
Distribution: unstable
Urgency: medium
Maintainer: Kyle Robbertze 
Changed-By: Kyle Robbertze 
Closes: 956170
Changes:
 gnome-shell-extension-show-ip (8-6) unstable; urgency=medium
 .
   * Make compatible with GNOME Shell 3.36.x (Closes: #956170)
   * Refresh patches
   * Bump Standards-Version to 4.5.0 (no change)
   * Add Rules-Requires-Root
Checksums-Sha1:
 c71748c2e451ce1968fa890d7310014d1560f18f 2106 
gnome-shell-extension-show-ip_8-6.dsc
 7f4555f0472e80d2377d33c00e0d39210517f497 5892 
gnome-shell-extension-show-ip_8-6.debian.tar.xz
 ee4120d12c1c6fb3b30d13418de4724c8ec321ae 5836 
gnome-shell-extension-show-ip_8-6_amd64.buildinfo
Checksums-Sha256:
 59b0530e9a7db3d3d0200b12050e8185bb3589e6ddeb164fc698f025e4f66dfa 2106 
gnome-shell-extension-show-ip_8-6.dsc
 f34351d86505add95c9d116e47f9324d3f2fc6519ff4a88db73d9d608b8629a7 5892 
gnome-shell-extension-show-ip_8-6.debian.tar.xz
 156cb0c6155592ac734222151a90a23efa7564d8a94122a67394793855335d4c 5836 
gnome-shell-extension-show-ip_8-6_amd64.buildinfo
Files:
 26d841dc34f4ffe58ebf7a2bb5239dae 2106 gnome optional 
gnome-shell-extension-show-ip_8-6.dsc
 5dac3dbe77295d41f3c99c531fbe8a2e 5892 gnome optional 
gnome-shell-extension-show-ip_8-6.debian.tar.xz
 bf72d5c622c32d66e075dc76866de991 5836 gnome optional 
gnome-shell-extension-show-ip_8-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEElqWPGCu4+bgcXyczhU8Hvggt8U8FAl6v8N0YHHBhZGRhdHJh
cHBlckBkZWJpYW4ub3JnAAoJEIVPB74ILfFPBRsQAI6K2/d8Ps1wuHUbMSUdlawp
rMjDqIrWPtK2gDWu5P5RQVSCEJ+DttPUif/DTx1hjzmWDoEYdIfU5WARKuC+8O0z
Hy2rnxGQ/N9tcxiZGHk2lf8ccY8yAzEWfotWEX5V1Hb4Q8DV49rTWUVTOisKEhXs
jfyjky9RAxSIjmna43m9XzAHAmnuAi+2DpDasOpfmOiti15kNbScjVenBLUTM9xd
RsFdmQdqq327YpEw7+iiKX9skOgBF95zJLdPqnHRAaamuLQac5cAwGUxj9ABbsLR
vp7U+xDUWFfaOwrpjWmsAjtIUmAuioxEbl4Qc3SMqjX+CB8p3F9uQp6t+B/VJ6iZ
SrcwOFB0PmeKfHsBPJ0sP+a0l2ZeQbvdaKJ7uKTiAufGP9K7w9vEq9K6SzgrECJo
V0FATv0i2SDmR58yzS99obcmHigPnIvdhmsFvz7KFpMSI9NrsENmF+cyG+yW2oj0
DVQ7ufjfcclx+oTFiog4rw7w1clAIMN0suF21eRyrJoGZUPUGGWwgPVEqA1G6Vuy
sFuyA8utQuBRFW9du+spYBsGZEepcTEu8FKTlZJrmT+uCAjfSbRsbE2Zw4H1TiGj
MPly+rJO1A7r1c7Zgtaz5Ab3osTr0pq3ZSPE+w8q5AjM6eJoJIEhz7JVt+BojGFB
C66wsBIovTSP61lSk+No
=YnEK
-END PGP SIGNATURE End Message ---

Bug#941077: marked as done (xserver-xorg-video-ast: sourceless firmware in AST_DP501_firmware in src/ast_dp501fw.h)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 12:32:05 +0200
with message-id <20200504103205.GA323689@chou>
and subject line Re: Bug#941077: xserver-xorg-video-ast: sourceless firmware in 
AST_DP501_firmware in src/ast_dp501fw.h
has caused the Debian Bug report #941077,
regarding xserver-xorg-video-ast: sourceless firmware in AST_DP501_firmware in 
src/ast_dp501fw.h
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.)


-- 
941077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-ast
Version: 1.1.5-1.1
Severity: serious
Justification: DFSG item 2

The AST_DP501_firmware array in src/ast_dp501fw.h contains a sourceless
firmware blob. I think this means that xserver-xorg-video-ast needs to
move to non-free, or it could use ast_dp501_fw.bin from the firmware
directory like the Linux kernel does and then move to contrib.

xserver-xorg-video-ast-1.1.5/ $ grep -C1 0x src/ast_dp501fw.h | head -n3
UCHAR AST_DP501_firmware[] = {\
0x00,0x00,0x00,0x00,0x00,0x00,0x04,0x00,\
0x00,0x00,0x04,0x56,0x00,0x00,0x04,0x56,\

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.1.5-1.1+rm

On Tue, Sep 24, 2019 at 06:05:18PM +0800, Paul Wise wrote:
> Source: xserver-xorg-video-ast
> Version: 1.1.5-1.1
> Severity: serious
> Justification: DFSG item 2
> 
> The AST_DP501_firmware array in src/ast_dp501fw.h contains a sourceless
> firmware blob. I think this means that xserver-xorg-video-ast needs to
> move to non-free, or it could use ast_dp501_fw.bin from the firmware
> directory like the Linux kernel does and then move to contrib.
> 
This is now moot as the package was removed in bug #955603.

Cheers,
Julien--- End Message ---

Bug#953032: marked as done (xkbcomp: Internal error: Could not resolve keysym XF86FullScreen)

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 12:21:22 +0200
with message-id <20200504102122.GA323246@chou>
and subject line Re: Bug#953032: xkbcomp: Internal error: Could not resolve 
keysym XF86FullScreen
has caused the Debian Bug report #953032,
regarding xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
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.)


-- 
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-xkb-utils
Version: 7.7+5

journalctl reports thousands of
sh[1052]: The XKEYBOARD keymap compiler (xkbcomp) reports:
sh[1052]: > Internal error:   Could not resolve keysym XF86FullScreen
sh[1052]: Errors from xkbcomp are not fatal to the X server

Versions of packages x11-xkb-utils depends on:
ii  libc62.29-10
ii  libx11-6 2:1.6.9-2
ii  libxaw7  2:1.0.13-1+b2
ii  libxkbfile1  1:1.0.9-2+b12
ii  libxt6   1:1.1.5-1+b3
--- End Message ---
--- Begin Message ---
On Sat, Apr 18, 2020 at 01:02:33PM +0200, Reiner Herrmann wrote:
> Control: reopen -1
> 
> Reopening, as the same error is still thrown, as can be seen [0] in the
> autopkgtest runs [1] of src:awesome.

I just scheduled libx11 binNMUs which should make this go away.

It was never a critical bug though.

Cheers,
Julien--- End Message ---

Bug#933214: marked as done (fdisk: program loops with "Do you really want to quit?")

[Debian Bug Tracking System]

Your message dated Mon, 4 May 2020 11:51:05 +0200
with message-id <20200504095105.wwen6vcfaqyuv...@zeha.at>
and subject line Re: Bug#933214: fdisk: program loops with "Do you really want 
to quit?"
has caused the Debian Bug report #933214,
regarding fdisk: program loops with "Do you really want to quit?"
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.)


-- 
933214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fdisk
Version: 2.33.1-0.1
Severity: minor

Dear Maintainer,

The program can be tricked inot a situation where

  Do you really want to quit?
  Command (m for help):

is printed over and over by issuing the following command sequence:

  g
  n
  
  
  
--- End Message ---
--- Begin Message ---
Version: 2.35.1-1

Hi Yangfl,

* Yangfl  [200504 05:15]:
> Chris Hofstaedtler  于2020年5月4日周一 上午3:37写道：
> > * Yangfl  [200503 19:35]:
[..]
> > I've tried this on 2.35.1 and could not reproduce it. If you still
> > see this problem, please contact upstream, as this can't be a
> > Debian-only problem, and let us know the upstream bug URL.
> >
> > Thanks,
> > Chris
> >
> 
> Seen on 2.34-0.1 but not 2.35.1-1. Not sure if that is
> (unintentionally) fixed by upstream.

Thanks for the feedback. Marking as done in 2.35.1-1.

Chris--- End Message ---

Bug#959553: marked as done (python-mpd: FTBFS: Builder name devhelp not registered or available through entry point)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 09:33:50 +
with message-id 
and subject line Bug#959553: fixed in python-mpd 1.1.0-2
has caused the Debian Bug report #959553,
regarding python-mpd: FTBFS: Builder name devhelp not registered or available 
through entry point
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b devhelp -d _build/doctrees   . _build/devhelp
> Running Sphinx v2.4.3
> 
> Sphinx error:
> Builder name devhelp not registered or available through entry point
> make[2]: *** [Makefile:93: devhelp] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/python-mpd_1.1.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated python-mpd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2020 09:56:09 +0100
Source: python-mpd
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: mpd maintainers 
Changed-By: Simon McVittie 
Closes: 959553
Changes:
 python-mpd (1.1.0-2) unstable; urgency=medium
 .
   * Build-Depend on python3-sphinxcontrib.devhelp.
 This used to be part of python3-sphinx, but was separated in sphinx 2.x.
 (Closes: #959553)
   * python-mpd-doc: Add Built-Using: ${sphinxdoc:Built-Using}
   * d/p/Automatically-use-current-version-number-in-the-documenta.patch:
 Improve patch, and mark as forwarded upstream
   * d/p/asyncio-Initialize-__idle_task.patch,
 d/p/tests-Add-a-way-to-allow-slow-tests-to-be-run.patch:
 Add test coverage for async connect() timing out
   * Run slow tests in autopkgtest. They're not *that* slow.
   * Run autopkgtest for all supported Python 3 versions
Checksums-Sha1:
 b25a7a924cc63ca2f230a2f4dee0292ff758c6c5 2438 python-mpd_1.1.0-2.dsc
 99877fb4f9ef5cbe6fb33192c5cf73024f554097 6524 python-mpd_1.1.0-2.debian.tar.xz
 e0c017403009c9c33422110ca327864f60ed09c8 7303 
python-mpd_1.1.0-2_source.buildinfo
Checksums-Sha256:
 da49990ad3be78aa3aec95f55086bd857ced8ea340895756dc0b0459f1a980d1 2438 
python-mpd_1.1.0-2.dsc
 9cb83f8fcb30446db9f9f758498a2fe433e8eaa8e0ce095516517f18c84b3639 6524 
python-mpd_1.1.0-2.debian.tar.xz
 77ced48d8603478cc129230b1dd40cfeb8c0361be5b319f400e2024b85997c2f 7303 
python-mpd_1.1.0-2_source.buildinfo
Files:
 aeef40b5abb3ed23aa7298ca07e83406 2438 python optional python-mpd_1.1.0-2.dsc
 ddf58cd58dda4e2e9d6ce7bd94bc7bfc 6524 python optional 
python-mpd_1.1.0-2.debian.tar.xz
 f4c83da0035e27bbe0d07ced12b2fc06 7303 python optional 
python-mpd_1.1.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl6v3IgQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT/60D/wONmGcNQxiexjjsCuTGT8sbtqOzOwF7ZYt
dQo/0zHXJsadRM94tbTYauFzbPS9PTSA5j814Sf62cpLJmAmtTpKUmfI/OIHToIV
ljvNyokZ3XTj1YACWneD0fk5OqTaRAhgQnIWZx0ompB92a7nsFCSZUvmrlSVw0E2
niTfzDMtA8HN4BS/sHFMAcfohpALlNPp61fFd+wz0z219W51I44GFH7ewYOm9HLP
1uYoZxOK3e2wiZHQ6LrVHOg0Xzi1Lwx9P9+NAax9XK6+osKqcJt5KSwR4b7YQMye
22q5U/zeJTpmzQgyi1UdNPCK1fLWy2lhTI6vnemntAdTT9jhlVh/3e7OvDflB5PE
PYZwdaRR5LH6e1kpdz0E0uU04xDXZWj3y6tD1jH91oPh0g

Processed: closing 953707

[Debian Bug Tracking System]

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

> close 953707 0.1.3-3
Bug #953707 [src:libsoxr] src:libsoxr: fails to migrate to testing for too long
Marked as fixed in versions libsoxr/0.1.3-3.
Bug #953707 [src:libsoxr] src:libsoxr: fails to migrate to testing for too long
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#954558: marked as done (python-portpicker: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 09:18:51 +
with message-id 
and subject line Bug#954558: fixed in python-portpicker 1.3.1-4
has caused the Debian Bug report #954558,
regarding python-portpicker: FTBFS: tests failed
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.)


-- 
954558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-portpicker
Version: 1.3.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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=src python3 src/tests/portpicker_test.py
> ..sss...
> --
> Ran 16 tests in 0.036s
> 
> OK (skipped=3)
> PYTHONPATH=src python3 src/tests/portserver_test.py
> I0322 03:19:52.222 139770363705152 portserver.py:191] Port 22 unexpectedly in 
> use, last owning pid 0.
> I0322 03:19:52.222 139770363705152 portserver.py:191] Port 18862 unexpectedly 
> in use, last owning pid 0.
> I0322 03:19:52.222 139770363705152 portserver.py:195] All ports in use.
> ..I0322 03:19:52.224 139770363705152 portserver.py:191] Port 12344 
> unexpectedly in use, last owning pid 0.
> I0322 03:19:52.224 139770363705152 portserver.py:187] Can't read start time 
> for pid 12345.
> .I0322 03:19:52.224 139770363705152 portserver.py:191] Port 12345 
> unexpectedly in use, last owning pid 0.
> I0322 03:19:52.224 139770363705152 portserver.py:187] Can't read start time 
> for pid 12345.
> ..W0322 03:19:52.226 139770363705152 portserver.py:247] Could not parse 
> request: invalid literal for int() with base 10: b''
> W0322 03:19:52.226 139770363705152 portserver.py:247] Could not parse 
> request: invalid literal for int() with base 10: b'\n'
> W0322 03:19:52.226 139770363705152 portserver.py:247] Could not parse 
> request: invalid literal for int() with base 10: b'99Z\n'
> W0322 03:19:52.226 139770363705152 portserver.py:247] Could not parse 
> request: invalid literal for int() with base 10: b'99 8\n'
> .I0322 03:19:52.227 139770363705152 portserver.py:250] Request on behalf of 
> pid 6.
> I0322 03:19:52.228 139770363705152 portserver.py:251] cmdline:  name='_get_process_command_line()' id='139770352359264'>
> .I0322 03:19:52.229 139770363705152 portserver.py:250] Request on behalf of 
> pid 5.
> I0322 03:19:52.229 139770363705152 portserver.py:251] cmdline:  name='_get_process_command_line()' id='139770352464848'>
> .I0322 03:19:52.231 139770363705152 portserver.py:250] Request on behalf of 
> pid 8.
> I0322 03:19:52.231 139770363705152 portserver.py:251] cmdline:  name='_get_process_command_line()' id='139770352541552'>
> D0322 03:19:52.232 139770363705152 portserver.py:261] Allocated port 999 to 
> pid 8
> ...E0322 03:19:52.240 139770363705152 portserver.py:345] No ports.  
> Invalid port ranges in --portserver_static_pool?
> I0322 03:19:52.242 139770363705152 portserver.py:359] Serving on @TST-14928
> I0322 03:19:52.242 139770363705152 portserver.py:363] Stopping due to ^C.
> I0322 03:19:52.243 139770363705152 portserver.py:267] Dumping statistics:
> I0322 03:19:52.243 139770363705152 portserver.py:277] client-request-errors 0
> I0322 03:19:52.243 139770363705152 portserver.py:277] denied-allocations 0
> I0322 03:19:52.243 139770363705152 portserver.py:277] num-ports-managed 1
> I0322 03:19:52.243 139770363705152 portserver.py:277] 
> num-ports-checked-for-last-request 0
> I0322 03:19:52.243 139770363705152 portserver.py:277] total-allocations 0
> I0322 03:19:52.243 139770363705152 portserver.py:370] Goodbye.
> F.E0322 03:19:52.244 139770363705152 portserver.py:312] Ignoring unparsable 
> port range ''.
> E0322 03:19:52.245 139770363705152 portserver.py:312] Ignoring unparsable 
> port range 'not'.
> E0322 03:19:52.245 139770363705152 portserver.py:312] Ignoring unparsable 
> port range 'numbers'.
> E0322 03:19:52.245 139770363705152 portserver.py:312] Ignoring unparsable 
> port range '8080-8081x'.
> E0322 03:19:52.245 139770363705152 portserver.py:315] Ignoring out of bounds 
> port range '0-1138'.
> E0322 03:19:52.245 139770363705152 portserver.py:315] Ignoring out of bounds 
> port range '1138-65536'.
> .I0322 03:19:52.245 139770363705152 portserver.py:111] Not allocating a port 
> to invalid pid
> I0322 03:19:52.245 139770363705152 portserver.py:116] Not allocating a port 
> to init.
> I0322 03:19:52.246 139770363705152 portserver.py:121] Not a

Bug#959616: marked as done (node-postcss: FTBFS: Cannot read property 'bindings' of null)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 08:49:48 +
with message-id 
and subject line Bug#959616: fixed in node-postcss 7.0.17-1
has caused the Debian Bug report #959616,
regarding node-postcss: FTBFS: Cannot read property 'bindings' of null
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.)


-- 
959616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-postcss
Version: 6.0.23-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
> gulp compile
> [05:09:19] Local modules not found in /<>
> [05:09:19] Try running: npm install
> [05:09:19] Using globally installed gulp
> [05:09:19] Using gulpfile /<>/gulpfile.js
> [05:09:19] Starting 'compile'...
> [05:09:19] 'compile' errored after 443 ms
> [05:09:19] TypeError in plugin "gulp-babel"
> Message:
> Cannot read property 'bindings' of null
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/node-postcss_6.0.23-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-postcss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:02:22 +0530
Source: node-postcss
Architecture: source
Version: 7.0.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Closes: 958777 959616
Changes:
 node-postcss (7.0.17-1) unstable; urgency=medium
 .
   * New upstream version 7.0.17
   * Build with babel 7 (Closes: #958777, #959616)
   * Add work around to replace gulp:compile with babeljs-7 command
Checksums-Sha1:
 e8f14bf1b619c234b42e47d1b0387450483f7528 2243 node-postcss_7.0.17-1.dsc
 1949dcb5304e7be5db5df88565fa481b0f93280b 256431 node-postcss_7.0.17.orig.tar.gz
 dfaefb8349123bce8ec758409f1c0653b606d731 10244 
node-postcss_7.0.17-1.debian.tar.xz
 c34d9ac1a8104567da1bd0abf7645f0352cc4dc5 20295 
node-postcss_7.0.17-1_source.buildinfo
Checksums-Sha256:
 4b7809eba235cb42b10127aeba0289f0873196f6dd2daf0df6d2f6883e62c4af 2243 
node-postcss_7.0.17-1.dsc
 acbcd760e87fb72c7f17b9e9387076c063482a4ccdf9326ae5d4f47b050e24a0 256431 
node-postcss_7.0.17.orig.tar.gz
 55df61c4c3f27c50a12ba7baa6cf4d2157121385d21fd5706ec82067f5063d28 10244 
node-postcss_7.0.17-1.debian.tar.xz
 8906ece362af17550ff7ed8b775155b6dc6839c06d5f7cc0768d7cfcb6fb076c 20295 
node-postcss_7.0.17-1_source.buildinfo
Files:
 11221e03b04f03ef51940c444a504f1b 2243 javascript optional 
node-postcss_7.0.17-1.dsc
 f5f117900289c3eefdb4054f7cac32ac 256431 javascript optional 
node-postcss_7.0.17.orig.tar.gz
 ab4922f7a73a1b9f3d204fb22d024bf5 10244 javascript optional 
node-postcss_7.0.17-1.debian.tar.xz
 eafecf5f847c7d09e1c47d1bda7be717 20295 javascript optional 
node-postcss_7.0.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl6v1IIACgkQj1PgGTsp
S3W2Mg//SQBrbOUGBVyK1tPR3bw+icjJvaNenTOBzG3+7JWrux1CQE7Oh0gjsWgo
W7A6anMXl6IuIvBVv138Jcwh3xRXMXrNAMICB1PEPYJc7j3R/cqay87+/ZNqXQfN
108J3YalwlKj9s5B81zDyWw9BgfDYsq3ycdPaaH9re5ELPEgBQ2xoJ+DAUefeHKK
Lwqs9lWUxr4WKK5lppMzadFmfOc/H8S7320ecK+t1fiIRPSoDuGcBgjLCmtaLqc8
Gu+vnz0SWj8ExhzWJB57q021N12QX9U+C0NvxJ67F01MR1viTN84qP4N0kp26qLu
YLUEx29ip99jxw

Bug#958777: marked as done (node-postcss: Package fail to build with node-gulp-babel 8.8.0)

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 08:49:48 +
with message-id 
and subject line Bug#958777: fixed in node-postcss 7.0.17-1
has caused the Debian Bug report #958777,
regarding node-postcss: Package fail to build with node-gulp-babel 8.8.0
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.)


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

This package fails to build with node-gulp-babel 8.0.0 (available in
experimental dist). Maybe just a missing dependency to a node-babel
(6) package. 
--- End Message ---
--- Begin Message ---
Source: node-postcss
Source-Version: 7.0.17-1
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-postcss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 May 2020 14:02:22 +0530
Source: node-postcss
Architecture: source
Version: 7.0.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Closes: 958777 959616
Changes:
 node-postcss (7.0.17-1) unstable; urgency=medium
 .
   * New upstream version 7.0.17
   * Build with babel 7 (Closes: #958777, #959616)
   * Add work around to replace gulp:compile with babeljs-7 command
Checksums-Sha1:
 e8f14bf1b619c234b42e47d1b0387450483f7528 2243 node-postcss_7.0.17-1.dsc
 1949dcb5304e7be5db5df88565fa481b0f93280b 256431 node-postcss_7.0.17.orig.tar.gz
 dfaefb8349123bce8ec758409f1c0653b606d731 10244 
node-postcss_7.0.17-1.debian.tar.xz
 c34d9ac1a8104567da1bd0abf7645f0352cc4dc5 20295 
node-postcss_7.0.17-1_source.buildinfo
Checksums-Sha256:
 4b7809eba235cb42b10127aeba0289f0873196f6dd2daf0df6d2f6883e62c4af 2243 
node-postcss_7.0.17-1.dsc
 acbcd760e87fb72c7f17b9e9387076c063482a4ccdf9326ae5d4f47b050e24a0 256431 
node-postcss_7.0.17.orig.tar.gz
 55df61c4c3f27c50a12ba7baa6cf4d2157121385d21fd5706ec82067f5063d28 10244 
node-postcss_7.0.17-1.debian.tar.xz
 8906ece362af17550ff7ed8b775155b6dc6839c06d5f7cc0768d7cfcb6fb076c 20295 
node-postcss_7.0.17-1_source.buildinfo
Files:
 11221e03b04f03ef51940c444a504f1b 2243 javascript optional 
node-postcss_7.0.17-1.dsc
 f5f117900289c3eefdb4054f7cac32ac 256431 javascript optional 
node-postcss_7.0.17.orig.tar.gz
 ab4922f7a73a1b9f3d204fb22d024bf5 10244 javascript optional 
node-postcss_7.0.17-1.debian.tar.xz
 eafecf5f847c7d09e1c47d1bda7be717 20295 javascript optional 
node-postcss_7.0.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl6v1IIACgkQj1PgGTsp
S3W2Mg//SQBrbOUGBVyK1tPR3bw+icjJvaNenTOBzG3+7JWrux1CQE7Oh0gjsWgo
W7A6anMXl6IuIvBVv138Jcwh3xRXMXrNAMICB1PEPYJc7j3R/cqay87+/ZNqXQfN
108J3YalwlKj9s5B81zDyWw9BgfDYsq3ycdPaaH9re5ELPEgBQ2xoJ+DAUefeHKK
Lwqs9lWUxr4WKK5lppMzadFmfOc/H8S7320ecK+t1fiIRPSoDuGcBgjLCmtaLqc8
Gu+vnz0SWj8ExhzWJB57q021N12QX9U+C0NvxJ67F01MR1viTN84qP4N0kp26qLu
YLUEx29ip99jxw6BqyFqrcn0iDqeeBd+kKvcsBrq9NB8CyStu/dNDpd/njaupYSm
uZYklgK2Y3OhzIr6SlGh6EgeqrIaRQ6LBYJRcjUb40Sb/FP7+u8W/qvERThYGTHO
Gwv7O0ipOASoefsR3ghh129rloLtwLGuJGijhBgfba1JuncV8QerYOFsIYkrKuJv
MkMbA/rZjKZFUwreY1+WhUZeYgowq0txIXHmSdYksSZHdjJNi4z1g+Y8jjXS8tQi
AtKvxjVY9o8C4c/4UpSuAl1fAdBveDmayg2+JeZHXrS47tA3yhB4blLiQ/qm1IGN
yz+Ug4C07cMmr26uDZ7fUDj70+F2kwaeDoUcbQPBMBUPOtqfyYw=
=gfOV
-END PGP SIGNATURE End Message ---

Bug#959139: marked as done (numpy breaks scikit-learn arm64 autopkgtest: assert_uniform_grid(Y, try_name))

[Debian Bug Tracking System]

Your message dated Mon, 04 May 2020 08:49:56 +
with message-id 
and subject line Bug#959139: fixed in scikit-learn 0.22.2.post1+dfsg-6
has caused the Debian Bug report #959139,
regarding numpy breaks scikit-learn arm64 autopkgtest: assert_uniform_grid(Y, 
try_name)
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.)


-- 
959139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numpy, scikit-learn
Control: found -1 numpy/1:1.18.3-1
Control: found -1 scikit-learn/0.22.2.post1+dfsg-5
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of numpy the autopkgtest of scikit-learn fails in
testing on arm64 when that autopkgtest is run with the binary packages
of numpy from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
numpy  from testing1:1.18.3-1
scikit-learn   from testing0.22.2.post1+dfsg-5
all others from testingfrom testing

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

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

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=numpy

https://ci.debian.net/data/autopkgtest/testing/arm64/s/scikit-learn/5194679/log.gz

=== FAILURES
===
 test_uniform_grid[barnes_hut]
_

method = 'barnes_hut'

@pytest.mark.parametrize('method', ['barnes_hut', 'exact'])
def test_uniform_grid(method):
"""Make sure that TSNE can approximately recover a uniform 2D grid

Due to ties in distances between point in X_2d_grid, this test
is platform
dependent for ``method='barnes_hut'`` due to numerical imprecision.

Also, t-SNE is not assured to converge to the right solution
because bad
initialization can lead to convergence to bad local minimum (the
optimization problem is non-convex). To avoid breaking the test
too often,
we re-run t-SNE from the final point when the convergence is not
good
enough.
"""
seeds = [0, 1, 2]
n_iter = 500
for seed in seeds:
tsne = TSNE(n_components=2, init='random', random_state=seed,
perplexity=20, n_iter=n_iter, method=method)
Y = tsne.fit_transform(X_2d_grid)

try_name = "{}_{}".format(method, seed)
try:
>   assert_uniform_grid(Y, try_name)

/usr/lib/python3/dist-packages/sklearn/manifold/tests/test_t_sne.py:784:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

Y = array([[ 52.326397  , -15.92225   ],
   [ 46.679527  , -20.175953  ],
   [ 40.870537  , -24.181147  ],
   ...[-35.291374  ,  22.122814  ],
   [-42.2738,  18.793724  ],
   [-48.922283  ,  15.606232  ]], dtype=float32)
try_name = 'barnes_hut_1'

def assert_uniform_grid(Y, try_name=None):
# Ensure that the resulting embedding leads to approximately
# uniformly spaced points: the distance to the closest neighbors
# should be non-zero and approximately constant.
nn = NearestNeighbors(n_neighbors=1).fit(Y)
dist_to_nn = nn.kneighbors(return_distance=True)[0].ravel()
assert dist_to_nn.min() > 0.1

smallest_to_mean = dist_to_nn.min() / np.mean(dist_to_nn)
largest_to_mean = dist_to_nn.max() / np.mean(dist_to_nn)

assert smallest_to_mean > .5, try_name
>   assert largest_to_mean < 2, try_name
E   AssertionError: barnes_hut_1
E   assert 6.67359409617653 < 2

/usr/lib/python3/dist-packages/sklearn/manifold/tests/test_t_sne.py:807:
AssertionError

During handling of the above exception, another exception occurred:

method = 'barnes_hut'

@pytest.mark.parametrize('method', ['barnes_hut', 'exact'])
def test_uniform_grid(method):
"""Make sure that TSNE can approximately recover a uniform 2D grid

Due to ties in distances between point in X_2d_grid, this test
is platform
de