Bug#962323: python-django: CVE-2020-13254 CVE-2020-13596

[Sébastien Delafond]

On 15/06 10:49, Chris Lamb wrote:
> > The full debdiffs are attached. Can you especially check the
> > versioning scheme and distribution fields for me? I often get this
> > wrong and end up confusing myself. Really appreciated.
> 
> They are now attached.

They look fine, please upload to security-master.

Cheers,

-- 
Seb

Bug#962944: marked as done (python3-biopython needs Breaks: cnvkit (<< 0.9.7-1~))

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2020 05:19:02 +
with message-id 
and subject line Bug#962944: fixed in python-biopython 1.77+dfsg-2
has caused the Debian Bug report #962944,
regarding python3-biopython needs Breaks: cnvkit (<< 0.9.7-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.)


-- 
962944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-biopython
Version: 1.77+dfsg-1
Severity: serious
Control: block 959587 by -1

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cnvkit/5912015/log.gz

...
Unpacking python3-biopython (1.77+dfsg-1) ...
...
Unpacking cnvkit (0.9.6-3) ...
...
Traceback (most recent call last):
  File "/usr/bin/cnvkit", line 8, in 
from cnvlib import commands
  File "/usr/lib/python3/dist-packages/cnvlib/__init__.py", line 5, in 
from .commands import *
  File "/usr/lib/python3/dist-packages/cnvlib/commands.py", line 32, in 
from . import (access, antitarget, autobin, batch, call, core, coverage,
  File "/usr/lib/python3/dist-packages/cnvlib/autobin.py", line 11, in 
from . import coverage, samutil
  File "/usr/lib/python3/dist-packages/cnvlib/coverage.py", line 15, in 
from Bio._py3k import StringIO
ModuleNotFoundError: No module named 'Bio._py3k'
make: *** [Makefile:51: build/reference-picard.cnn] Error 1
--- End Message ---
--- Begin Message ---
Source: python-biopython
Source-Version: 1.77+dfsg-2
Done: Etienne Mollier 

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

Debian distribution maintenance software
pp.
Etienne Mollier  (supplier of updated 
python-biopython 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, 16 Jun 2020 22:12:00 +0200
Source: python-biopython
Architecture: source
Version: 1.77+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Etienne Mollier 
Closes: 962944
Changes:
 python-biopython (1.77+dfsg-2) unstable; urgency=medium
 .
   * Declared python3-biopython breaks: cnvkit (<< 0.9.7-1~) (Closes: #962944)
Checksums-Sha1:
 ee805fc94c8d91559124ec286066c3a34eb4494f 3245 python-biopython_1.77+dfsg-2.dsc
 f4bdf561dd1a6ad3afd89230cb751cf97353cb31 15660 
python-biopython_1.77+dfsg-2.debian.tar.xz
 1472caa3aba7036bc4004ecc3729048467d5c344 13314 
python-biopython_1.77+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 b5b0d7ecc1b4a48abd53eef49640b94b4b64ab0ccd6ebec04950d5d921025808 3245 
python-biopython_1.77+dfsg-2.dsc
 f12dddc0834bc7f6632cfefabceee1e74cd39f6b4bc20dcf7fc1afb8929652de 15660 
python-biopython_1.77+dfsg-2.debian.tar.xz
 87dbbcc17a19e22db27bae06329442caa5ae67adfcafbd023af95c3be9b5c0af 13314 
python-biopython_1.77+dfsg-2_amd64.buildinfo
Files:
 b7350778255e76a8f257dce65f11918c 3245 python optional 
python-biopython_1.77+dfsg-2.dsc
 67d72f3468bf4ddbef01119ca35ca492 15660 python optional 
python-biopython_1.77+dfsg-2.debian.tar.xz
 ed6ba33b7e0325e21f23957e5d4ede11 13314 python optional 
python-biopython_1.77+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7ppP4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEmzg//eimFH6F7YzGEaxtVlO4kK7DMT7jOJ85q
Yuoz++Ruf8tOcaNfOnpqZW+hYjoH21+Asz5lCjsaqymSGKfFVA89ns/nrouQ0N9+
Q29ZsSP85RwP/xnJv6K4bE2FZWwmqqGFjwCtcQJ4k50ETruwWOn7fdx0HJMIggAO
LMAR5yljc3V8dPuMuXtMan+Gfi9gNL36fEoDBKoAZtE2mnXMHGqNlmYtvlfvV804
eBTGJm0Y6EHbJ8BE3yruep4EKxumy8eaOFmC43aIYIpJEy+Ek13kVZQ0i037QT0S
hUpCdxCWeZnxcdkoMwOdG9psQ+uYdj0AzcYpqPUvXj4dT9/IS8XqNWHXGii1j/KT
h5Qs2NXr/5TtRfwWMfgREF7IYTR9ZsOo3whIryqUOxUoyp2QxGFnnrSuoWv9Tw/S
K5HcyxZaE/QUxtsJOPRWPkW1WoyU/BlvoLlfVpErHZ3IfrPaQcCWm924fJcvE7uS
dZcPlmrrdw7iuKcw9W0YrE3dZZsE6ZFiDVDjiKMFvv3qWkXT+l9fA94HBtoY3mCi
elzxbBWMjlr4evWr7WxU92tW3TIOcT8sN/9QEekmoaxb443bgcrgZS+kqYoPSHID
Blqz40d9GlXk9t0gLDKe2YYXVtUq5SqlMQR1fV/LVTWRCq7C6sMV9eWuRhI2dG1A
fZXZlF+YmFM=
=6wGz
-END PGP SIGNATURE End Message ---

Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl

[Salvatore Bonaccorso]

Hi,

On Tue, Jun 16, 2020 at 08:58:49PM -0400, J. Bruce Fields wrote:
> On Tue, Jun 16, 2020 at 06:16:58PM +0200, Salvatore Bonaccorso wrote:
> > This might be unneeded to test but as additional datapoint which
> > confirms the suspect: I tried check the commit around 47057abde515
> > ("nfsd: add support for the umask attribute") in 4.10-rc1
> > 
> > A kernel built with 47057abde515~1, and mounting from an enough recent
> > client which has at least dff25ddb4808 ("nfs: add support for the
> > umask attribute") does not show the observed behaviour, the server
> > built with 47057abde515 does.
> 
> Thanks for the confirmation!
> 
> I think I'll send the following upstream.
> 
> --b.
> 
> commit 595ccdca9321
> Author: J. Bruce Fields 
> Date:   Tue Jun 16 16:43:18 2020 -0400
> 
> nfsd: apply umask on fs without ACL support
> 
> The server is failing to apply the umask when creating new objects on
> filesystems without ACL support.
> 
> To reproduce this, you need to use NFSv4.2 and a client and server
> recent enough to support umask, and you need to export a filesystem that
> lacks ACL support (for example, ext4 with the "noacl" mount option).
> 
> Filesystems with ACL support are expected to take care of the umask
> themselves (usually by calling posix_acl_create).
> 
> For filesystems without ACL support, this is up to the caller of
> vfs_create(), vfs_mknod(), or vfs_mkdir().
> 
> Reported-by: Elliott Mitchell 
> Reported-by: Salvatore Bonaccorso 
> Fixes: 47057abde515 ("nfsd: add support for the umask attribute")
> Signed-off-by: J. Bruce Fields 
> 
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index 0aa02eb18bd3..8fa3e0ff3671 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -1225,6 +1225,9 @@ nfsd_create_locked(struct svc_rqst *rqstp, struct 
> svc_fh *fhp,
>   iap->ia_mode = 0;
>   iap->ia_mode = (iap->ia_mode & S_IALLUGO) | type;
>  
> + if (!IS_POSIXACL(dirp))
> + iap->ia_mode &= ~current_umask();
> +
>   err = 0;
>   host_err = 0;
>   switch (type) {
> @@ -1457,6 +1460,9 @@ do_nfsd_create(struct svc_rqst *rqstp, struct svc_fh 
> *fhp,
>   goto out;
>   }
>  
> + if (!IS_POSIXACL(dirp))
> + iap->ia_mode &= ~current_umask();
> +
>   host_err = vfs_create(dirp, dchild, iap->ia_mode, true);
>   if (host_err < 0) {
>   fh_drop_write(fhp);

Thank you, could test this on my test setup and seem to work properly.

Should it also be CC'ed to sta...@vger.kernel.org so it is picked up
by the current supported stable series?

Regards,
Salvatore

Processed: retitle 962254 to NFSv4.2: umask not applied on filesystem without ACL support

[Debian Bug Tracking System]

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

> retitle 962254 NFSv4.2: umask not applied on filesystem without ACL support
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Changed Bug title to 'NFSv4.2: umask not applied on filesystem without ACL 
support' from 'NFS v4.2 broken between 4.9 and 4.15'.
Changed Bug title to 'NFSv4.2: umask not applied on filesystem without ACL 
support' from 'nfs-common: Umask ignored, all files created world-writable on 
NFS'.
> thanks
Stopping processing here.

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

Bug#962973: haskell-readline: Removal notice: broken and unmaintained

[Sean Whitton]

Hello,

On Tue 16 Jun 2020 at 07:55PM +03, Ilias Tsitsimpis wrote:

> Source: haskell-readline
> Version: 1.0.3.0-9
> Severity: grave
> Justification: renders package unusable
>
> This package seems to be unmaintained (last upstream upload in 2013).
> Does not build with GHC 8.8, is not part of Stackage and has no rev
> dependencies.
>
> I intend to remove this package.

keysafe, in experimental, depends on haskell-readline.

CCing upstream: Joey, do you think it would be possible for keysafe to
migrate to use something maintained?

-- 
Sean Whitton

Processed: Updating Bug #959640

[Debian Bug Tracking System]

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

> owner 959640 Nick Morrott 
Bug #959640 [src:firmware-microbit-micropython] firmware-microbit-micropython: 
FTBFS: make[2]: python: Command not found
Owner recorded as Nick Morrott .
> tags 959640 + pending
Bug #959640 [src:firmware-microbit-micropython] firmware-microbit-micropython: 
FTBFS: make[2]: python: Command not found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#954805: marked as done (src:xapers: Fails autopkgtest due to test assumptions about paths)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2020 02:37:28 +
with message-id 
and subject line Bug#923327: fixed in xapers 0.9.0-1
has caused the Debian Bug report #923327,
regarding src:xapers: Fails autopkgtest due to test assumptions about paths
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.)


-- 
923327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xapers
Version: 0.8.2-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

The following autopkgtest log extracted from [1] should be enough to
show the problem.  It is currently showing up as a regression for
python3.8 as default, but this doesn't seem related at all.

Scott K

Note: Using FTBFS as a tag because it is the closest we have for
autopkgtest failures.

 FAIL   search --output=bibtex single
--- all.48.expected 2020-03-23 13:11:53.768226199 +
+++ all.48.output   2020-03-23 13:11:53.768226199 +
@@ -3,6 +3,6 @@
 title = "Creation of the γ-verses",
 year = "2011",
 eprint = "1235",
-file = ":XAPERS_ROOT/01/1.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.cg\_m28kl/downtmp/build.i4p/src/test/tmp.all/docs/01/1.pdf:pdf"
 }

 FAIL   bibtex multiple
--- all.49.expected 2020-03-23 13:11:53.940223633 +
+++ all.49.output   2020-03-23 13:11:53.936223692 +
@@ -10,7 +10,7 @@
 year = "2012",
 month = "Sep",
 pages = "2092",
-file = ":XAPERS_ROOT/02/2 file.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.cg\_m28kl/downtmp/build.i4p/src/test/tmp.all/docs/02/2
 file.pdf:pdf"
 }

 @article{arxiv:1235,
@@ -18,7 +18,7 @@
 title = "Creation of the γ-verses",
 year = "2011",
 eprint = "1235",
-file = ":XAPERS_ROOT/01/1.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.cg\_m28kl/downtmp/build.i4p/src/test/tmp.all/docs/01/1.pdf:pdf"
 }

 @article{30929234,
No bibtex for doc id:5.

[1] https://ci.debian.net/data/autopkgtest/testing/amd64/x/xapers/4639691/log.gz
--- End Message ---
--- Begin Message ---
Source: xapers
Source-Version: 0.9.0-1
Done: Jameson Graef Rollins 

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

Debian distribution maintenance software
pp.
Jameson Graef Rollins  (supplier of updated xapers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 May 2020 11:25:56 -0700
Source: xapers
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jameson Graef Rollins 
Changed-By: Jameson Graef Rollins 
Closes: 923327
Changes:
 xapers (0.9.0-1) unstable; urgency=medium
 .
   * New release (Closes: #923327)
   * Update standards version 4.5.0
Checksums-Sha1:
 6b6ceb3bdb533d9e7345e6e54e81bbd3daa45530 1321 xapers_0.9.0-1.dsc
 e54c6719f6f5b1a22ba348187e58dfb23486be2b 159928 xapers_0.9.0.orig.tar.gz
 4cb5d6832d7b9e8d803f10769afec7a6e680f3a8 3108 xapers_0.9.0-1.debian.tar.xz
 3f43435b85f031fa8a55866696afc39066fb519f 8015 xapers_0.9.0-1_amd64.buildinfo
Checksums-Sha256:
 4bec33f69c6bdce56ff2bb2b660b58e38a9d6348cc930f16efda7fae76e65ffd 1321 
xapers_0.9.0-1.dsc
 30f3ead9fb063d7515e6f69e3092e054208c23e387448051a1b19c2a7b71 159928 
xapers_0.9.0.orig.tar.gz
 fa2f2f935f9e7b650c8f28efe4ec019ec2cc93e4e1cea52262090c3134b3 3108 
xapers_0.9.0-1.debian.tar.xz
 bbc80edaa20d420bb622ccb0b63caf3b0a51f6b1f982ef6549c8e23291cc4cf2 8015 
xapers_0.9.0-1_amd64.buildinfo
Files:
 67259cc7b323e049caad4a0e7fe50244 1321 text optional xapers_0.9.0-1.dsc
 ccb61ae31c3243c6edc2d2e426be3125 159928 text optional xapers_0.9.0.orig.tar.gz
 daf094f9124be932ae9cc7529ce8d759 3108 text optional 
xapers_0.9.0-1.debian.tar.xz
 62d3eec0eae11e6cca046ad7b372b75a 8015 text optional 
xapers_0.9.0-1_amd64.buildinfo

-BEGIN 

Bug#923327: marked as done (xapers: intermittent autopkgtest failures (escaped underscores in XAPERS_ROOT?))

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2020 02:37:28 +
with message-id 
and subject line Bug#923327: fixed in xapers 0.9.0-1
has caused the Debian Bug report #923327,
regarding xapers: intermittent autopkgtest failures (escaped underscores in 
XAPERS_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.)


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

https://ci.debian.net/packages/x/xapers/unstable/amd64/ shows that
there are intermittent failures in the autopkgtest.

I suspect that the issue is when XAPERS_ROOT contains an underscore,
then the filtering (sed "s|$XAPERS_ROOT|XAPERS_ROOT|") doesn't behave
as expected.

why the underscore is escaped in the first place, i don't know!

here's the snippet of failing tests:


FAIL   search --output=bibtex single
--- all.48.expected 2019-02-12 09:56:55.994607258 +
+++ all.48.output   2019-02-12 09:56:55.994607258 +
@@ -3,6 +3,6 @@
 title = "Creation of the γ-verses",
 year = "2011",
 eprint = "1235",
-file = ":XAPERS_ROOT/01/1.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.9v\_4vmuj/downtmp/build.8os/src/test/tmp.all/docs/01/1.pdf:pdf"
 }
 
 FAIL   bibtex multiple
--- all.49.expected 2019-02-12 09:56:56.158602082 +
+++ all.49.output   2019-02-12 09:56:56.158602082 +
@@ -10,7 +10,7 @@
 year = "2012",
 month = "Sep",
 pages = "2092",
-file = ":XAPERS_ROOT/02/2 file.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.9v\_4vmuj/downtmp/build.8os/src/test/tmp.all/docs/02/2
 file.pdf:pdf"
 }
 
 @article{arxiv:1235,
@@ -18,7 +18,7 @@
 title = "Creation of the γ-verses",
 year = "2011",
 eprint = "1235",
-file = ":XAPERS_ROOT/01/1.pdf:pdf"
+file = 
":/tmp/autopkgtest-lxc.9v\_4vmuj/downtmp/build.8os/src/test/tmp.all/docs/01/1.pdf:pdf"
 }
 
 @article{30929234,
No bibtex for doc id:5.


   --dkg


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

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

Versions of packages xapers depends on:
ii  poppler-utils  0.71.0-2
ii  python33.7.2-1
ii  python3-pkg-resources  40.7.1-1
ii  python3-pybtex 0.21-2
ii  python3-xapian 1.4.10-1

Versions of packages xapers recommends:
ii  python3-pycurl  7.43.0.2-0.1
ii  python3-urwid   2.0.1-2+b1
ii  xclip   0.13-1
ii  xdg-utils   1.1.3-1

xapers suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xapers
Source-Version: 0.9.0-1
Done: Jameson Graef Rollins 

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

Debian distribution maintenance software
pp.
Jameson Graef Rollins  (supplier of updated xapers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 May 2020 11:25:56 -0700
Source: xapers
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jameson Graef Rollins 
Changed-By: Jameson Graef Rollins 
Closes: 923327
Changes:
 xapers (0.9.0-1) unstable; urgency=medium
 .
   * New release (Closes: #923327)
   * Update standards version 4.5.0
Checksums-Sha1:
 6b6ceb3bdb533d9e7345e6e54e81bbd3daa45530 1321 xapers_0.9.0-1.dsc
 e54c6719f6f5b1a22ba348187e58dfb23486be2b 

Bug#949472: marked as done (python-pex's autopkg tests are failing)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2020 01:34:31 +
with message-id 
and subject line Bug#949472: fixed in python-pex 1.1.14-3.1
has caused the Debian Bug report #949472,
regarding python-pex's autopkg tests are failing
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.)


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

python-pex's autopkg tests are failing both in testing and unstable:

Removing autopkgtest-satdep (0) ...
autopkgtest [20:27:54]: test execute.sh: [---
+ export http_proxy=127.0.0.1:9
+ export https_proxy=127.0.0.1:9
+ pex -m textwrap -vv -o script
pex: Building pex
pex: Building pex :: Resolving interpreter
pex: Building pex :: Resolving interpreter :: Setting up interpreter
/usr/bin/python3.7
pex: Building pex :: Resolving distributions
pex: Building pex: 3.7ms
pex:   Resolving interpreter: 2.7ms
pex: Setting up interpreter /usr/bin/python3.7: 2.7ms
pex:   Resolving distributions: 0.1ms
Saving PEX file to script
+ ./script
Hello there.
  This is indented.
autopkgtest [20:27:55]: test execute.sh: ---]
autopkgtest [20:27:55]: test execute.sh:  - - - - - - - - - - results - - - - -
- - - - -
execute.sh   FAIL non-zero exit status 120
--- End Message ---
--- Begin Message ---
Source: python-pex
Source-Version: 1.1.14-3.1
Done: Gleisson Jesuino Joaquim Cardoso 

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

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

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

Debian distribution maintenance software
pp.
Gleisson Jesuino Joaquim Cardoso  (supplier of updated 
python-pex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jun 2020 02:55:26 -0300
Source: python-pex
Architecture: source
Version: 1.1.14-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Gleisson Jesuino Joaquim Cardoso 
Closes: 949472
Changes:
 python-pex (1.1.14-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/source/options: created to ignore changes in 'requires.txt' file.
   * debian/tests/execute.sh: fixed errors in autopkgtest, thanks to Matthias 
Klose,
 Emmanuel Arias and Gianfranco Costamagna. (Closes: #949472)
Checksums-Sha1:
 32e4abb20f645dace4d86fd1d2f161b6f9072f4d 2202 python-pex_1.1.14-3.1.dsc
 78797868441bf34702ea95b5dc121f5ff6bc7fb7 5764 
python-pex_1.1.14-3.1.debian.tar.xz
 1956c6acad05b3deacbd2ff77d8d2d97c8c50a65 6859 
python-pex_1.1.14-3.1_source.buildinfo
Checksums-Sha256:
 66359fe59b1f372f243e347334d26f7667e409d339120eac4fccd638003d254a 2202 
python-pex_1.1.14-3.1.dsc
 79f3c70c4e9cf2a2cda8c74b2886e8b1a38d2b4acc608d1e738beae56f192a1f 5764 
python-pex_1.1.14-3.1.debian.tar.xz
 4cdef216835d34d70876879301624dd1933b9985ed0f85398298df3ae5174f22 6859 
python-pex_1.1.14-3.1_source.buildinfo
Files:
 c6227d105e6c24b4d3012b89e0cf368f 2202 python optional python-pex_1.1.14-3.1.dsc
 e072d30d3d1ac32a5c2832eea1aa8495 5764 python optional 
python-pex_1.1.14-3.1.debian.tar.xz
 c8815f3cceead71edada226c23307de8 6859 python optional 
python-pex_1.1.14-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7ldj0ACgkQ3mO5xwTr
6e+GpA/+PKbt8hMza4vlAsQVI0Fqc1+aDfMp21lIgY02Jho5sa/DSQbqBsrDjDTq
dXxAT3Dw+kzZ2tKtrGrbhxSyivBsGzHqXuvRZ3GVKYizxiHuEpat4vgRgDn59Rnq
ftzvUHDx75/SkTOo6iHwyML+w9JQ8it0YQIRthj1J8trZCLXuSfadGXUawJutEVs
uMVxXshFDNlvZ6mXqHcZ3uEUvjm71zGIsvYwmxXNzWm8yEtIgwqt3yUANiPERlLT
Pq3zWpjQIFO9Fp5wvY89uqEP/sIyB8qqoiOLBM2OipANf52zeaA8D0SAIGRBxKuU
3VsTR5MsB9NuOrGwGzOm2VKYDewHt1CcpgtgvyUHfH0xQjdt7NrQjxBznuQf5qUm
6/GbfoTOsOFuCCKtWLORKGlqUJyT6AEhHRmadzmQOERJZjb2//IUFZA355icKGlJ
XAWs6V7GwPSCUtJZIwyJI5wK6h0uMI68rigCQzXKCcHmCj3hIqr6Y3JECy6Q9iXc
FQVKmqYdWxv4kg4uY8Us2MBCEV6mTpvUWu0sNBpEuE2wk4qsFTarcp9FAanG2tTo
MKD6VO6TGb1u4Iewv61wDR0OTeECvPcPel0UOuByADD46mCDD8wcOzND24TppPzv
O5YbfB1dGWyI7PiSjS5iSZrmHj1C/PwitC/CfuRFf5t6y3UM27s=
=qd1J
-END PGP SIGNATURE End Message ---

Bug#962937: marked as done (python-oauthlib: FTBFS with newer python-mock)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2020 01:19:33 +
with message-id 
and subject line Bug#962937: fixed in python-oauthlib 3.1.0-2
has caused the Debian Bug report #962937,
regarding python-oauthlib: FTBFS with newer python-mock
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.)


-- 
962937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oauthlib
Version: 3.1.0-1
Severity: serious
Tags: ftbfs

python-oauthlib 3.1.0-1 FTBFS and autopkgtest fails with newer python-mock 
4.0.2-1.

Thanks for fixing.

__ AuthorizationCodeGrantTest.test_invalid_request_duplicates __

self = 


def test_invalid_request_duplicates(self):
request = mock.MagicMock(wraps=self.request)
request.grant_type = 'authorization_code'
request.duplicate_params = ['client_id']
>   self.assertRaises(errors.InvalidRequestError, 
> self.auth.validate_token_request,
  request)

tests/oauth2/rfc6749/grant_types/test_authorization_code.py:159: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/grant_types/authorization_code.py:453:
 in validate_token_request
raise errors.InvalidRequestError(description='Duplicate %s parameter.' % 
param,
/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/errors.py:49: in __init__
if request:
/usr/lib/python3/dist-packages/mock/mock.py:2160: in __get__
return self.create_mock()
/usr/lib/python3/dist-packages/mock/mock.py:2156: in create_mock
_set_return_value(parent, m, entry)
/usr/lib/python3/dist-packages/mock/mock.py:2053: in _set_return_value
method._mock_wraps = getattr(mock._mock_wraps, name)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def __getattr__(self, name):
if name in self._params:
return self._params[name]
else:
>   raise AttributeError(name)
E   AttributeError: __bool__

/usr/lib/python3/dist-packages/oauthlib/common.py:436: AttributeError

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: python-oauthlib
Source-Version: 3.1.0-2
Done: Daniele Tricoli 

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

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated python-oauthlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jun 2020 02:52:07 +0200
Source: python-oauthlib
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Daniele Tricoli 
Closes: 962937
Changes:
 python-oauthlib (3.1.0-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Daniele Tricoli ]
   * Add upstream patch to use unittest.mock instead of external mock.
 Thanks to Ondřej Nový for the report. (Closes: #962937)
   * Remove python3-mock dependency.
   * Fix lintian runtime-test-file-uses-installed-python-versions.
Checksums-Sha1:
 04389314dc6ff11f876c05dc3366b465181cfff3 2239 python-oauthlib_3.1.0-2.dsc
 448959d6b8144d692a35799e43250d783e00b8af 6572 
python-oauthlib_3.1.0-2.debian.tar.xz
 34d5bb42a0104987745a20fcc5e6cc544988990a 6525 
python-oauthlib_3.1.0-2_amd64.buildinfo
Checksums-Sha256:
 afb980138fc67eb77a45fe02c18d823538b429fa1c6528bf071f88c9054ff5f8 2239 
python-oauthlib_3.1.0-2.dsc
 

Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2)

[J. Bruce Fields]

On Tue, Jun 16, 2020 at 06:16:58PM +0200, Salvatore Bonaccorso wrote:
> This might be unneeded to test but as additional datapoint which
> confirms the suspect: I tried check the commit around 47057abde515
> ("nfsd: add support for the umask attribute") in 4.10-rc1
> 
> A kernel built with 47057abde515~1, and mounting from an enough recent
> client which has at least dff25ddb4808 ("nfs: add support for the
> umask attribute") does not show the observed behaviour, the server
> built with 47057abde515 does.

Thanks for the confirmation!

I think I'll send the following upstream.

--b.

commit 595ccdca9321
Author: J. Bruce Fields 
Date:   Tue Jun 16 16:43:18 2020 -0400

nfsd: apply umask on fs without ACL support

The server is failing to apply the umask when creating new objects on
filesystems without ACL support.

To reproduce this, you need to use NFSv4.2 and a client and server
recent enough to support umask, and you need to export a filesystem that
lacks ACL support (for example, ext4 with the "noacl" mount option).

Filesystems with ACL support are expected to take care of the umask
themselves (usually by calling posix_acl_create).

For filesystems without ACL support, this is up to the caller of
vfs_create(), vfs_mknod(), or vfs_mkdir().

Reported-by: Elliott Mitchell 
Reported-by: Salvatore Bonaccorso 
Fixes: 47057abde515 ("nfsd: add support for the umask attribute")
Signed-off-by: J. Bruce Fields 

diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index 0aa02eb18bd3..8fa3e0ff3671 100644
--- a/fs/nfsd/vfs.c
+++ b/fs/nfsd/vfs.c
@@ -1225,6 +1225,9 @@ nfsd_create_locked(struct svc_rqst *rqstp, struct svc_fh 
*fhp,
iap->ia_mode = 0;
iap->ia_mode = (iap->ia_mode & S_IALLUGO) | type;
 
+   if (!IS_POSIXACL(dirp))
+   iap->ia_mode &= ~current_umask();
+
err = 0;
host_err = 0;
switch (type) {
@@ -1457,6 +1460,9 @@ do_nfsd_create(struct svc_rqst *rqstp, struct svc_fh *fhp,
goto out;
}
 
+   if (!IS_POSIXACL(dirp))
+   iap->ia_mode &= ~current_umask();
+
host_err = vfs_create(dirp, dchild, iap->ia_mode, true);
if (host_err < 0) {
fh_drop_write(fhp);

Bug#962988: When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists

[Andrey ``Bass'' Shcheglov]

Related to bug #962989 
.



signature.asc
Description: OpenPGP digital signature

Bug#962988: When started, xfstt doesn't listen at any sockets (neither unix nor tcp) if /tmp/.font-unix/ directory already exists

[Andrey ``Bass'' Shcheglov]

Package: xfstt
Version: 1.10-1
Severity: grave
Tags: upstream

During its start-up, xfstt creates the `/tmp/.font-unix/` directory in order to 
place its socket there.

If, however, the above directory already exists, xfstt:

 - doesn't create the unix socket there if the socket file doesn't exist,
 - doesn't re-use the existing socket file, and
 - fails to listen at a TCP socket even if configured so.

STR:

 1. Make sure xfstt isn't running or stop it first.
 2. As root, create the /tmp/.font-unix/ directory.
 3. Delete /tmp/.font-unix/fs7101 (the socket file).
 4. Start xfstt.
 5. The daemon will start w/o any error:

> # service xfstt status
> [ ok ] xfstt is running.
> 
> # ps -ef | grep xfstt | grep -v grep
> root 31878 1  0 02:00 ?00:00:00 /usr/bin/xfstt --daemon 
> --port 7101 --unstrap --encoding iso8859-1

 6. In spite of the above, the socket file won't be re-created:

> # ls -l /tmp/.font-unix/
> total 0

 7. Additionally, xfstt will no longer be listening at TCP port 7101:

> # lsof -p 31878
> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFFNODE NAME
> xfstt   31878 root  cwdDIR  254,212288 1314666 
> /usr/share/fonts/truetype
> xfstt   31878 root  rtdDIR  254,1 4096   2 /
> xfstt   31878 root  txtREG  254,2   129224  805495 /usr/bin/xfstt
> xfstt   31878 root  memREG  254,4   311653  134640 
> /var/cache/xfstt/ttname.dir
> xfstt   31878 root  memREG  254,1  18244962028 
> /lib/x86_64-linux-gnu/libc-2.28.so
> xfstt   31878 root  memREG  254,1   100712 661 
> /lib/x86_64-linux-gnu/libgcc_s.so.1
> xfstt   31878 root  memREG  254,1  15794483929 
> /lib/x86_64-linux-gnu/libm-2.28.so
> xfstt   31878 root  memREG  254,2  1570256 2104093 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25
> xfstt   31878 root  memREG  254,472536  134639 
> /var/cache/xfstt/ttinfo.dir
> xfstt   31878 root  memREG  254,1   1656321889 
> /lib/x86_64-linux-gnu/ld-2.28.s

Normally, I'm also expecting 3 sockets in lsof output:

> xfstt   1663 root0u  unix 0x8838fffb7800  0t0 4774342 
> /tmp/.font-unix/fs7101 type=STREAM
> xfstt   1663 root1u  IPv44774346  0t0 TCP *:7101 
> (LISTEN)
> xfstt   1663 root2u  IPv64774347  0t0 TCP *:7101 
> (LISTEN)

If I re-start xfstt, it'll remove and re-create the /tmp/.font-unix/ directory, 
but this directory
shouldn't be managed by xfstt alone as it may be shared between multiple X font 
servers (e. g.: xfs).

The problem stems from the following fragment in xfstt.cc:

> if (mkdir(sockdir, 01777) < 0) {
> error(_("cannot make socket directory %s!\n"), 
> sockdir);
> close(sd);
> return -1;
> }

If the directory already exists and has the right permissions, xfstt should 
just proceed.

If the directory already exists but lacks some permissions, xfstt should 
attempt to change those (when running as root).

BTW, /etc/init.d/x11-common script from x11-common already does the job of 
creating X11 socket directories,
so it could be enhanced to take care of /tmp/.font-unix, too.

-- System Information:
Distributor ID: Debian
Description:Devuan GNU/Linux 3 (beowulf)
Release:3
Codename:   beowulf
Architecture: x86_64

Kernel: Linux 4.9.0-11-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xfstt depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libgcc11:8.3.0-6
ii  libstdc++6 8.3.0-6
ii  lsb-base   10.2019051400

xfstt recommends no packages.

xfstt suggests no packages.

-- debconf information:
* xfstt/listen_tcp: true

Bug#937437: pyfeed: Python2 removal in sid/bullseye

[Thomas Preud'homme]

Hi Moritz,

I've filled #962985 and #962986. I don't see why these library packages should 
be kept without reverse dependency.

Best regards,

Thomas.

Bug#906765: marked as done (libxsmm: baseline violation on amd64 and FTBFS everywhere else)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 22:19:17 +
with message-id 
and subject line Bug#906765: fixed in libxsmm 1.9-2
has caused the Debian Bug report #906765,
regarding libxsmm: baseline violation on amd64 and FTBFS everywhere else
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.)


-- 
906765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxsmm
Version: 1.9-1
Severity: serious
Tags: ftbfs patch

libxsmm builds with -msse4.2 on amd64 and FTBFS everywhere else:
https://buildd.debian.org/status/package.php?p=libxsmm=sid

Fix for the baseline violation:

--- debian/rules.old2018-08-19 15:06:38.277886761 +
+++ debian/rules2018-08-19 15:08:40.141885599 +
@@ -3,6 +3,8 @@
 
 export PREFIX=/usr
 
+export TARGET=-""
+
 %:
dh $@
 


The FTBFS problems on !amd64 don't seem easily fixable,
and it is unclear whether this would be worth the effort.
If fixing is not easily possible, an option would be
  Architecture: any-amd64
--- End Message ---
--- Begin Message ---
Source: libxsmm
Source-Version: 1.9-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated libxsmm 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, 16 Jun 2020 18:04:22 -0400
Source: libxsmm
Architecture: source
Version: 1.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Boyuan Yang 
Closes: 906765 936943
Changes:
 libxsmm (1.9-2) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.5.0.
   * Bump debhelper compat to v13.
   * debian/control:
 + Limit package architecture to any-amd64 only.
   * debian/patches: Add patch to force using python3. (Closes: #936943)
   * debian/watch: Monitor upstream GitHub release.
   * debian/rules: Apply patch to fix FTBFS and baseline violation.
 (Closes: #906765)
Checksums-Sha1:
 c9cd91b1d4c8114bcb521f37a3d330618e46a8c9 1971 libxsmm_1.9-2.dsc
 cee96833347944513c12df969176b4025cbc91dd 4952 libxsmm_1.9-2.debian.tar.xz
 e6d8ce0e1a3f5274947a9d61cb2edc1202dbfc3a 6407 libxsmm_1.9-2_amd64.buildinfo
Checksums-Sha256:
 f5653766e1ba4ba37cfbd588a82293a9e7d3e245d6e77348bda2bc2e018a9f2d 1971 
libxsmm_1.9-2.dsc
 1cf570d2a3e3ceff706ccc1400341b8c8827288f78ef2b04c228bf0139caeb13 4952 
libxsmm_1.9-2.debian.tar.xz
 dec91ce8ea14e9b3161eacaca551956cb5dd9d918f92cd6a58eeabf8da347e1e 6407 
libxsmm_1.9-2_amd64.buildinfo
Files:
 5c87e2ef3bae59ed79ee0bb96e0d310b 1971 libs optional libxsmm_1.9-2.dsc
 0d3170197c45058c041bf9edf06c9f1b 4952 libs optional libxsmm_1.9-2.debian.tar.xz
 d1dcb282afb1746f79d60f451c47b113 6407 libs optional 
libxsmm_1.9-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl7pQwkACgkQwpPntGGC
Ws7F2w/+L23H16Cmwz5ZEqHOeu7MQUfB9EB3Z4fdF1IARBIMSoB1jUWX27TR5Hfr
3jNsWvM54xspB7ggnIKND7tJ7zIrNEDIgfm37OM5odw7kTTqlb6mV1AsAM2FfF7/
lcBwsgHYKhK559c1AEz8epfOoxgn09KA/3XhREw0xqSN+B280AwCESIUP+B5Ucuj
zS7xvwjG+h/TX6rjO+iFpzyuYXEQsyBwpVW7odxZYR1EjBVk66L+yVPPLyX392ti
4nTOgZvkdgJa2gJv8pB1ataqP/glva0PBoiZLpMyKx0ZZRW02pN7vQlZh26AwnHA
prRsqtzjR34Y0s24/LoJVz06kcgMjbaxn5LjbTj4PKK5/wuTIkoR43P7mEGey+JK
f6QfeZz5dLOzbhnan3yrCZtfhiPcH+FmvlJ7GFksKVl4VKGWp6FY7VWdu0ay4Wgn
kTHvIW6eFI8feoh7pwetCEm2KksDOkJHRAWkGhhjItoxJtxtCH4K6FnzDBcwlG7C
Qd+QDki8eSAgtFTkHgYrjoiSaKHH3ohKdJoDfTKCDKb+V1nWidsoCKzPkmMDyXmM
ZawabV6056+EtFAL3wIXLPiJUg7gIUdyYK7w2M3MvCqgv9gg9RMWCRsDdVN1bHZm
i8+KTN3NBvTfOVMsGv9u9VdrmBm3wAiNL/3wvSxCmzH93GD3i4I=
=m/ZX
-END PGP SIGNATURE End Message ---

Bug#932296: qa.debian.org: getwatch filling up /tmp

[Lucas Nussbaum]

On 16/06/20 at 21:07 +0100, Adam D. Barratt wrote:
> On Tue, 2020-06-16 at 16:40 +0200, Julien Cristau wrote:
> > On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote:
> > > Control: severity -1 serious
> > > 
> > > On Thu, Aug 08, 2019 at 01:45:27PM +0200, Julien Cristau wrote:
> > > > On Wed, Jul 17, 2019 at 10:11:39PM +0200, Lucas Nussbaum wrote:
> > > > > On 17/07/19 at 14:01 +0200, Julien Cristau wrote:
> > > > > > something in udd seems to extract entire source packages to
> > > > > > /tmp/getwatch.*.  This fills up the disk.  Please make it not
> > > > > > do that.
> [...]
> > > This happened again.  If it won't get fixed I'll go ahead and
> > > disable that job.
> > > 
> > Done now, removed the "upstream" importer from the config file.
> > 
> 
> It looks like that wasn't enough, as ullmann filled its disk again.
> 
> I've now also updated rudd.conf to disable the importer there.

I emptied the 'upstream' UDD table (no data is better than wrong data).

In a previous message, it was proposed to use temporary space under
/srv, but /srv only has 3.1 GB left. Could you maybe create a
/srv/udd.debian.org/tmp with maybe 10G ?

Also, does DSA offer the service to send icinga notifications to service
owners? Apparently the condition where this happens is quite rare
occurences on 08/2019, 12/2019, 06/2020), so notifying me after the
files were cleaned up from /tmp makes it hard to identify which packages
cause this issue. If I could get notified when a warning limit is
reached, it would be much easier to debug.

Lucas

Bug#937553: marked as done (pysycache: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:36:27 +
with message-id 
and subject line Bug#962980: Removed package(s) from unstable
has caused the Debian Bug report #937553,
regarding pysycache: 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.)


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

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

Dear submitter,

as the package pysycache 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/962980

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#912504: marked as done (pysycache: Please migrate to python3-pygame)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:36:27 +
with message-id 
and subject line Bug#962980: Removed package(s) from unstable
has caused the Debian Bug report #912504,
regarding pysycache: Please migrate to python3-pygame
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.)


-- 
912504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pysycache
Severity: wishlist
User: python-modules-t...@lists.alioth.debian.org
Usertags: python3-migration

Dear maintainer,

thanks for maintaining a pygame-based game in Debian!

As you might have heard, Python 2 will be end of life in the not so
far future. Thus, I would like to start to get the reverse
dependencies of the Python 2 version of pygame down, so this can be
done with some time and not in a hurried effort that probably makes
us loose games from Debian.

If you already know that your game will work with Python 3, please
build against and depend on python3-pygame, which has long been
available in sid and will migrate to buster shortly.

If you do not yet know whether this will work, your chances that it
will just work are still quite good, so please just give it a shot.

If you find your package does not work with Python 3 yet, you can…

a) …check what to do with upstream

b) …try to patch it (and forward your patch upstream)

c) …tag this bug report help - the next pygame-fluent kangaroo

is reserved for you!

Feel free to ask any questions if you are unsure what to do.

Cheers, Nik 
--- End Message ---
--- Begin Message ---
Version: 3.1-3.3+rm

Dear submitter,

as the package pysycache 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/962980

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#931888: marked as done (pymvpa2 FTBFS: test_assert_objectarray_equal / test_vector_alignment_find_rotation_illegal_inputs)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:35:37 +
with message-id 
and subject line Bug#962908: Removed package(s) from unstable
has caused the Debian Bug report #931888,
regarding pymvpa2 FTBFS: test_assert_objectarray_equal / 
test_vector_alignment_find_rotation_illegal_inputs
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.)


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

Source: pymvpa2
Version: 2.6.5-1
Severity: serious

This package FTBFS in sid (plain dpkg-buildpackage) with these test 
failures (which are different from the ones in #906399, but the same as 
the ones in reproducible-builds).


This bug was found during statsmodels 0.9 transition testing, but also 
occurs with current (0.8) statsmodels.


As this is a Python 2 only package (in Debian, I didn't check upstream), 
it may make sense to remove it rather than try to fix this.


==
ERROR: mvpa2.tests.test_testing.test_assert_objectarray_equal
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in 
runTest

self.test(*self.arg)
  File 
"/home/test1/pymvpa2-2.6.5/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_testing.py", 
line 39, in test_assert_objectarray_equal

assert_objectarray_equal(a, a.copy(), strict=strict)
  File 
"/home/test1/pymvpa2-2.6.5/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/testing/tools.py", 
line 472, in assert_objectarray_equal

assert_array_equal(x, y)
  File 
"/usr/lib/python2.7/dist-packages/numpy/testing/_private/utils.py", line 
896, in assert_array_equal

verbose=verbose, header='Arrays are not equal')
  File 
"/usr/lib/python2.7/dist-packages/numpy/testing/_private/utils.py", line 
827, in assert_array_compare

raise ValueError(msg)
ValueError:
error during assertion:

Traceback (most recent call last):
  File 
"/usr/lib/python2.7/dist-packages/numpy/testing/_private/utils.py", line 
803, in assert_array_compare

max_abs_error = error.max()
  File "/usr/lib/python2.7/dist-packages/numpy/core/_methods.py", line 
28, in _amax

return umr_maximum(a, axis, None, out, keepdims, initial)
ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()



Arrays are not equal
 x: array([array([0, 1]), array(1)], dtype=object)
 y: array([array([0, 1]), array(1)], dtype=object)

==
FAIL: test_vector_alignment_find_rotation_illegal_inputs 
(mvpa2.tests.test_surfing_surface.SurfingSurfaceTests)

--
Traceback (most recent call last):
  File 
"/home/test1/pymvpa2-2.6.5/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_surfing_surface.py", 
line 97, in test_vector_alignment_find_rotation_illegal_inputs

vector_alignment_find_rotation, *illegal_arg)
AssertionError: (, 'exceptions.IndexError'>) not raised


--
Ran 577 tests in 234.985s

FAILED (SKIP=22, errors=1, failures=1)
--- End Message ---
--- Begin Message ---
Version: 2.6.5-1+rm

Dear submitter,

as the package pymvpa2 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/962908

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#937485: marked as done (pymvpa2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:35:37 +
with message-id 
and subject line Bug#962908: Removed package(s) from unstable
has caused the Debian Bug report #937485,
regarding pymvpa2: 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.)


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

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.6.5-1+rm

Dear submitter,

as the package pymvpa2 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/962908

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#906399: marked as done (pymvpa2: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:35:37 +
with message-id 
and subject line Bug#962908: Removed package(s) from unstable
has caused the Debian Bug report #906399,
regarding pymvpa2: FTBFS in buster/sid (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.)


-- 
906399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymvpa2
Version: 2.6.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2 --buildsystem=python_distutils 
--builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=python_distutils 
-O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
mkdir -p /<>/build
cp -rp debian/intersphinx doc/source/
which swig >/dev/null || ln -s /usr/bin/swig2.0 /<>/build/swig
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'

[... snipped ...]

self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_hdf5.py",
 line 83, in test_h5py_dataset_typecheck
assert_raises(ValueError, AttrDataset.from_hdf5, fpath2)
  File "/usr/lib/python2.7/unittest/case.py", line 473, in assertRaises
callableObj(*args, **kwargs)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/dataset.py",
 line 573, in from_hdf5
if isinstance(source, h5py.highlevel.File):
AttributeError: 'module' object has no attribute 'highlevel'

==
ERROR: mvpa2.tests.test_hdf5.test_class_oldstyle
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/testing/tools.py",
 line 291, in newfunc
func(*(arg + (filename,)), **kw)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_hdf5.py",
 line 155, in test_class_oldstyle
assert_raises(HDF5ConversionError, save, co, fname, compression='gzip')
  File "/usr/lib/python2.7/unittest/case.py", line 473, in assertRaises
callableObj(*args, **kwargs)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/dataset.py",
 line 1274, in save
if isinstance(destination, h5py.highlevel.File):
AttributeError: 'module' object has no attribute 'highlevel'

==
ERROR: mvpa2.tests.test_hdf5.test_dataset_without_chunks
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/testing/tools.py",
 line 291, in newfunc
func(*(arg + (filename,)), **kw)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_hdf5.py",
 line 172, in test_dataset_without_chunks
save(ds, fname, compression='gzip')
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/dataset.py",
 line 1274, in save
if isinstance(destination, h5py.highlevel.File):
AttributeError: 'module' object has no attribute 'highlevel'

--
Ran 577 tests in 170.523s

FAILED (SKIP=22, errors=4)
make[1]: *** [debian/rules:49: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End 

Bug#945702: marked as done (qmail-tools: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 21:35:18 +
with message-id 
and subject line Bug#962907: Removed package(s) from unstable
has caused the Debian Bug report #945702,
regarding qmail-tools: 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.)


-- 
945702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmail-tools
Version: 0.1.0
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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
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 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.1.0+rm

Dear submitter,

as the package qmail-tools 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/962907

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#932296: qa.debian.org: getwatch filling up /tmp

[Adam D. Barratt]

On Tue, 2020-06-16 at 16:40 +0200, Julien Cristau wrote:
> On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote:
> > Control: severity -1 serious
> > 
> > On Thu, Aug 08, 2019 at 01:45:27PM +0200, Julien Cristau wrote:
> > > On Wed, Jul 17, 2019 at 10:11:39PM +0200, Lucas Nussbaum wrote:
> > > > On 17/07/19 at 14:01 +0200, Julien Cristau wrote:
> > > > > something in udd seems to extract entire source packages to
> > > > > /tmp/getwatch.*.  This fills up the disk.  Please make it not
> > > > > do that.
[...]
> > This happened again.  If it won't get fixed I'll go ahead and
> > disable that job.
> > 
> Done now, removed the "upstream" importer from the config file.
> 

It looks like that wasn't enough, as ullmann filled its disk again.

I've now also updated rudd.conf to disable the importer there.

Regards,

Adam

Processed: bolt: FTBFS: dh_auto_test: error

[Debian Bug Tracking System]

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

> severity 952626 normal
Bug #952626 [src:bolt] bolt: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned 
exit code 1
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#952626: cont...@bugs.debian.org

[Sebastien Bacher]

severity 952626 normal
thanks

The current version built fine, seems rather a flacky test if anything
Could you perhaps try if you see the issue still with 0.9?
https://buildd.debian.org/status/package.php?p=bolt=unstable

Bug#962893: marked as done (syslog-ng: autopkgtest regression: Depends on syslog-ng-mod-snmptrapd-parser)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 19:34:05 +
with message-id 
and subject line Bug#962893: fixed in syslog-ng 3.27.1-2
has caused the Debian Bug report #962893,
regarding syslog-ng: autopkgtest regression: Depends on 
syslog-ng-mod-snmptrapd-parser
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.)


-- 
962893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.27.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
syslog-ng  from testing3.27.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems there
is still a test for a dropped package. The changelog hints that this has
been merged into some other package. Shouldn't that other package
Provides syslog-ng-mod-snmptrapd-parser?

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

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
syslog-ng/3.27.1-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=syslog-ng

https://ci.debian.net/data/autopkgtest/testing/amd64/s/syslog-ng/5899607/log.gz




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.27.1-2
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated syslog-ng 
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, 16 Jun 2020 19:04:17 +0200
Source: syslog-ng
Architecture: source
Version: 3.27.1-2
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers 

Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 962893
Changes:
 syslog-ng (3.27.1-2) unstable; urgency=medium
 .
   * Fix self-tests as mod-snmptrapd-parser merged to mod-snmp package
 (closes: #962893).
   * Update Standards-Version to 4.5.0 .
Checksums-Sha1:
 5f9d72f6106566c1d0f46174708184c2c48d2d6b 4425 syslog-ng_3.27.1-2.dsc
 e4cba60d5c7ed6e5a9bfe51d111c1730ff918315 44108 syslog-ng_3.27.1-2.debian.tar.xz
Checksums-Sha256:
 3a13851d3714b78d9a62bd348a1a8981f9cabdf314f33d06cf6d7b829c6af64c 4425 
syslog-ng_3.27.1-2.dsc
 6ebd5c5693b132802ebd532fb85bfb4a14dea89c7ca73e81f54b080b79e80825 44108 
syslog-ng_3.27.1-2.debian.tar.xz
Files:
 d0d36cf931617cd8028360669487db9a 4425 admin optional syslog-ng_3.27.1-2.dsc
 c0b4a987cc936bf4bc119187ca14abf2 44108 admin optional 
syslog-ng_3.27.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl7pG0UACgkQ3OMQ54ZM
yL+7MBAApkNWtqJn1SQdmVng2YNvzbs1I0p3NVh1/8e141xKVk7p2PLtHoMGMASa
cFt+3LPD4OmfWAV7SilXFJFV2ajunZyWxhtfsIOkEuXE9lDAKEQ7hQl7ha6oslnD
zkSk8tyA5dDr30Shp7C5JbS4VaOGXsKgPmojRn0uBSYZHuNAIAeUbgpbQ3+c9v6b
VbM71j7OqlsSyIg+6OdFLYWc76XFFVTP6tfmYsGTTGufQkr4CQ7Z0/Ll3ebU5Fbr
/WTtGttmk5QhzH2OsAKFIp0pr8K/U/0KqEXI4NQmFrkxGWg8POoIca05evtjMBA0
E1rRVTVFayHMJ8dIDjw/I5lujGNu1NTrSb+j/DFkQ8hyle0uBPSewAbkV20aCK5M
EBIuNvvcUXsEAoKc0sMvXs4RbhMCFEBG0/NWo+i2OamJ3JZagoN72+M1xpLIL7L2
s2GYVND8LeUEb+kqNjNxwDdPKkyAfJDy3DGSiAr5m1zsXRk0S8JTVdOBfg66clSy
rQ2v19HNyrmYByh3R+5/FG1pkfOMALmEZ+2b5vTCg7cVBr3jacuy0kaxjMHi89Es

Bug#911569: src:haskell-hit: dead upstream, not worth the maintenance burden?

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-hit -- ROM; broken and dead upstream
Control: severity -1 normal

Hi,

Please remove haskell-hit from Debian. It is unmaintained and doesn't
work with the latest version of GHC.

Thanks,

-- 
Ilias

Processed: Re: Bug#911569: src:haskell-hit: dead upstream, not worth the maintenance burden?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #911569 [src:haskell-hit] src:haskell-hit: dead upstream, not worth the 
maintenance burden?
Bug reassigned from package 'src:haskell-hit' to 'ftp.debian.org'.
No longer marked as found in versions haskell-hit/0.6.3-8.
Ignoring request to alter fixed versions of bug #911569 to the same values 
previously set
> retitle -1 RM: haskell-hit -- ROM; broken and dead upstream
Bug #911569 [ftp.debian.org] src:haskell-hit: dead upstream, not worth the 
maintenance burden?
Changed Bug title to 'RM: haskell-hit -- ROM; broken and dead upstream' from 
'src:haskell-hit: dead upstream, not worth the maintenance burden?'.
> severity -1 normal
Bug #911569 [ftp.debian.org] RM: haskell-hit -- ROM; broken and dead upstream
Severity set to 'normal' from 'serious'

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

Bug#962588: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright

[Thorsten Glaser]

Ben Hutchings dixit:

>This is the dpkg bug where it fails to replace a directory with a
>symlink.  For some reason that requires workarounds in every other
>package instead of being fixed in dpkg.

Yeah, this is annoying, but AIUI they call it a feature; a local
admin can symlink directories around if they suddenly lack space
on a partition (this was before bind mounts existed).

Thanks,
//mirabilos
-- 
 Beware of ritual lest you forget the meaning behind it.
 yeah but it means if you really care about something, don't
ritualise it, or you will lose it. don't fetishise it, don't
obsess. or you'll forget why you love it in the first place.

Processed: tagging 962962

[Debian Bug Tracking System]

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

> tags 962962 + bullseye sid
Bug #962962 [src:haskell-hstatsd] haskell-hstatsd: Removal notice: broken and 
unmaintained
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 962958

[Debian Bug Tracking System]

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

> tags 962958 + bullseye sid
Bug #962958 [src:haskell-edison-core] haskell-edison-core: Removal notice: 
broken and unuseful
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 962970

[Debian Bug Tracking System]

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

> tags 962970 + bullseye sid
Bug #962970 [src:haskell-permutation] haskell-permutation: Removal notice: 
broken and unmaintained
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: tagging 962959

[Debian Bug Tracking System]

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

> tags 962959 + bullseye sid
Bug #962959 [src:haskell-edison-api] haskell-edison-api: Removal notice: broken 
and unuseful
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 962973

[Debian Bug Tracking System]

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

> tags 962973 + bullseye sid
Bug #962973 [src:haskell-readline] haskell-readline: Removal notice: broken and 
unmaintained
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: tagging 962961

[Debian Bug Tracking System]

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

> tags 962961 + bullseye sid
Bug #962961 [src:haskell-gnutls] haskell-gnutls: Removal notice: broken and 
unmaintained
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: tagging 962955

[Debian Bug Tracking System]

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

> tags 962955 + bullseye sid
Bug #962955 [src:haskell-crypto-pubkey-openssh] haskell-crypto-pubkey-openssh: 
Removal notice: broken and unmaintained
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#946308: freespace2: diff for NMU version 3.7.4+repack-1.1

[Adrian Bunk]

On Wed, Jun 17, 2020 at 12:36:23AM +1000, Dmitry Smirnov wrote:
> On Wednesday, 17 June 2020 12:05:19 AM AEST Adrian Bunk wrote:
> > I've prepared an NMU for freespace2 (versioned as 3.7.4+repack-1.1) and
> > uploaded it to DELAYED/14. Please feel free to tell me if I should
> > cancel it.
> 
> Thank you very much for your help.

Thanks, rescheduled for immediate upload.

> Cheers,
>  Dmitry Smirnov.

cu
Adrian

Processed: reopening 962588

[Debian Bug Tracking System]

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

> reopen 962588
Bug #962588 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64:amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Bug #942861 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Bug reopened
Ignoring request to alter fixed versions of bug #962588 to the same values 
previously set
Ignoring request to alter fixed versions of bug #942861 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright

[Debian Bug Tracking System]

Processing control commands:

> notfixed 942861 5.3.9-1
Bug #942861 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
No longer marked as fixed in versions linux/5.3.9-1.
> forcemerge 942861 -1
Bug #942861 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Bug #962588 [linux-image-amd64] linux-image-amd64:amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Marked Bug as done
Marked as found in versions linux-signed-amd64/5.3.7+1.
Bug #942861 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Marked as found in versions linux-signed-amd64/5.3.2+1~exp1 and 
linux-signed-amd64/5.6.14+2.
Merged 942861 962588

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

Bug#962588: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright

[Ben Hutchings]

Control: notfixed 942861 5.3.9-1
Control: forcemerge 942861 -1

On Tue, 2020-06-16 at 17:44 +0100, Ben Hutchings wrote:
> Control: found -1 5.3.2-1~exp1
> 
> On Wed, 10 Jun 2020 13:55:17 +0200 Thorsten Glaser  wrote:
> > Package: linux-image-amd64
> > Version: 5.6.14-2
> > Severity: serious
> > Justification: Policy 2.3
> > 
> > tglase@tglase:~ $ ll /usr/share/doc/linux-image-amd64/
> > total 0
> > tglase@tglase:~ $ ll -d /usr/share/doc/linux-image-amd64
> > drwxr-xr-x 2 root root 4096 Okt 21  2019 /usr/share/doc/linux-image-amd64/
> 
> This is the dpkg bug where it fails to replace a directory with a
> symlink.  For some reason that requires workarounds in every other
> package instead of being fixed in dpkg.
> 
> This instance was introduced by:
> 
> commit 70af1a4e805ba7f355fb69b3a041b3fdb9b977dd
> Author: Ben Hutchings 
> Date:   Tue Oct 1 22:27:29 2019 +0100
> 
> Require metapackage dependencies to be the same version, and link doc dirs

Actually you already reported this as #942861 and I applied the
workaround, but it looks like I specified the wrong prior-version to
dpkg-maintscript-helper.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.
It's the only way to be sure.



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

Bug#962973: haskell-readline: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-readline
Version: 1.0.3.0-9
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (last upstream upload in 2013).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias

Bug#902901: FTBFS: Tests fail

[Ilias Tsitsimpis]

This package is still unbuildable after 2 years, with no response from
upstream. Since there are no rev dependencies for this package, I intend
to remove it from Debian.

-- 
Ilias

Bug#962971: python3-ruamel.yaml.clib: overwrites files from python3-ruamel.yaml without Replaces

[Simon McVittie]

Package: python3-ruamel.yaml.clib
Version: 0.2.0-1
Severity: serious
Justification: Policy 7.6.1

Steps to reproduce:
* Have python3-ruamel.yaml from testing
* Upgrade

Expected result: successful upgrade

Actual result:

> Preparing to unpack .../25-python3-ruamel.yaml.clib_0.2.0-1_amd64.deb ...
> Unpacking python3-ruamel.yaml.clib (0.2.0-1) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-w9QDSF/25-python3-ruamel.yaml.clib_0.2.0-1_amd64.deb 
> (--unpack):
>  trying to overwrite 
> '/usr/lib/python3/dist-packages/_ruamel_yaml.cpython-38-x86_64-linux-gnu.so', 
> which is also in package python3-ruamel.yaml 0.15.89-3+b2
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Preparing to unpack .../26-python3-ruamel.yaml_0.16.10-2_all.deb ...
> Unpacking python3-ruamel.yaml (0.16.10-2) over (0.15.89-3+b2) ...
> Errors were encountered while processing:
>  /tmp/apt-dpkg-install-w9QDSF/25-python3-ruamel.yaml.clib_0.2.0-1_amd64.deb

Workaround: retry the upgrade until apt decides to upgrade
python3-ruamel.yaml before installing python3-ruamel.yaml.clib.

This looks like the "Split, new A always requires new B" case from
. The solution is usually
to have:

Package: python3-ruamel.yaml
Depends: python3-ruamel.yaml.clib (>= some version)

Package: python3-ruamel.yaml.clib
Breaks: python3-ruamel.yaml (<< 0.16.10)
Replaces: python3-ruamel.yaml (<< 0.16.10)

so that they have to be upgraded together, with python3-ruamel.yaml
temporarily broken during the upgrade transaction.

Thanks,
smcv

Processed: unarchiving 942861

[Debian Bug Tracking System]

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

> unarchive 942861
Bug #942861 {Done: Ben Hutchings } [linux-image-amd64] 
linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Unarchived Bug 942861
> thanks
Stopping processing here.

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

Bug#962970: haskell-permutation: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-permutation
Version: 0.5.0.5-3
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (last upstream upload in 2015).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias

Bug#962588: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright

[Ben Hutchings]

Control: found -1 5.3.2-1~exp1

On Wed, 10 Jun 2020 13:55:17 +0200 Thorsten Glaser  wrote:
> Package: linux-image-amd64
> Version: 5.6.14-2
> Severity: serious
> Justification: Policy 2.3
> 
> tglase@tglase:~ $ ll /usr/share/doc/linux-image-amd64/
> total 0
> tglase@tglase:~ $ ll -d /usr/share/doc/linux-image-amd64
> drwxr-xr-x 2 root root 4096 Okt 21  2019 /usr/share/doc/linux-image-amd64/

This is the dpkg bug where it fails to replace a directory with a
symlink.  For some reason that requires workarounds in every other
package instead of being fixed in dpkg.

This instance was introduced by:

commit 70af1a4e805ba7f355fb69b3a041b3fdb9b977dd
Author: Ben Hutchings 
Date:   Tue Oct 1 22:27:29 2019 +0100

Require metapackage dependencies to be the same version, and link doc dirs

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.
It's the only way to be sure.



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

Processed: Re: linux-image-amd64:amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.3.2-1~exp1
Bug #962588 [linux-image-amd64] linux-image-amd64:amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
Marked as found in versions linux-signed-amd64/5.3.2+1~exp1.

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

Processed: tagging 936580, tagging 935677

[Debian Bug Tracking System]

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

> tags 936580 + pending
Bug #936580 [src:ganeti] ganeti: Python2 removal in sid/bullseye
Added tag(s) pending.
> tags 935677 + pending
Bug #935677 [ganeti-2.16] ganeti-2.16: Depends on to be removed packages 
(python2/python-ipaddr specifically)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#816640: ruby-eventmachine: FTBFS under pbuilder with USENETWORK=no: TestResolver fails (no implicit conversion of nil into String)

[duck]

Quack,

Andreas, could you explain to me why you reopened this ticket? Did you 
stumble on another test using the network? I built the package locally 
and on Salsa and it seemed to be fixed.


Also I don't understand why you merged it with #919085 which seem to 
address a broader problem. I see one test failing on mipsel and other 
failures in non-releasing arches, but it seems the situation is 
different from the original report. I'm not sure how to fix this test 
yet.


Regards.
\_o<

--
Marc Dequènes

Processed: found 962254 in 4.10-1~exp1

[Debian Bug Tracking System]

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

> found 962254 4.10-1~exp1
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Marked as found in versions linux/4.10-1~exp1.
Marked as found in versions linux/4.10-1~exp1.
> thanks
Stopping processing here.

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

Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2)

[Salvatore Bonaccorso]

Hi Bruce,

On Mon, Jun 15, 2020 at 10:42:12PM -0400, J. Bruce Fields wrote:
> On Mon, Jun 15, 2020 at 10:38:20PM -0400, J. Bruce Fields wrote:
> > Thanks for the detailed reproducer.
> > 
> > It's weird, as the server is basically just setting the transmitted
> > umask and then calling into the vfs to handle the rest, so it's not much
> > different from any other user.  But the same reproducer run just on the
> > ext4 filesystem does give the right permissions
> > 
> > Oh, but looking at the system call, fs_namei.c:do_mkdirat(), it does:
> > 
> > if (!IS_POSIXACL(path.dentry->d_inode))
> > mode &= ~current_umask();
> > error = security_path_mkdir(, dentry, mode);
> > if (!error)
> > error = vfs_mkdir(path.dentry->d_inode, dentry, mode);
> > 
> > whereas nfsd just calls into vfs_mkdir().
> > 
> > And that IS_POSIXACL() check is exactly a check whether the filesystem
> > supports ACLs.  So I guess it's the responsibility of the caller of
> > vfs_mkdir() to handle that case.
> 
> But, that's unsatisfying: why isn't vfs_mkdir() taking care of this
> itself?  And what about that security_path_mkdir() call?  And are the
> other cases of that switch in fs/nfsd/vfs.c:nfsd_create_locked()
> correct?  I think there may be some more cleanup here called for, I'll
> poke around tomorrow.

This might be unneeded to test but as additional datapoint which
confirms the suspect: I tried check the commit around 47057abde515
("nfsd: add support for the umask attribute") in 4.10-rc1

A kernel built with 47057abde515~1, and mounting from an enough recent
client which has at least dff25ddb4808 ("nfs: add support for the
umask attribute") does not show the observed behaviour, the server
built with 47057abde515 does.

Regards,
Salvatore

Bug#962630: marked as done (dovecot: FTBFS: test failures on 32-bit ARM)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 15:48:28 +
with message-id 
and subject line Bug#962630: fixed in dovecot 1:2.3.10.1+dfsg1-2
has caused the Debian Bug report #962630,
regarding dovecot: FTBFS: test failures on 32-bit ARM
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.)


-- 
962630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dovecot
Version: 1:2.3.10.1+dfsg1-1
Severity: serious
Justification: FTBFS on armel and armhf
Tags: sid

Dovecot currently fails to to build on 32-bit arm architectures.

The failure is in the upstream test suite, with the following output:

test-backtrace.c:19: Assert failed: backtrace_append(bt) == 0
test-backtrace.c:21: Assert failed: strstr(str_c(bt), "main") != NULL
backtrace_append . : FAILED
test-backtrace.c:43: Assert failed: backtrace_get() == 0
/bin/bash: line 1: 15381 Segmentation fault  ./$bin
make[5]: *** [Makefile:3409: check-local] Error 1
make[5]: Leaving directory '/<>/src/lib'
make[4]: *** [Makefile:2796: check-am] Error 2
make[4]: Leaving directory '/<>/src/lib'
make[3]: *** [Makefile:2798: check] Error 2
make[3]: Leaving directory '/<>/src/lib'
make[2]: *** [Makefile:563: check-recursive] Error 1
make[2]: Leaving directory '/<>/src'
make[1]: *** [Makefile:681: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:79: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

The specific failing test is:

static void test_backtrace_get(void)
{
test_begin("backtrace_get");
const char *bt = NULL;
#if (defined(HAVE_LIBUNWIND))
test_assert(backtrace_get() == 0);
/* Check that there's a usable function in the backtrace.
   Note that this function may be inlined, so don't check for
   test_backtrace_get() */
test_assert(strstr(bt, "test_backtrace") != NULL);
/* make sure the backtrace_get is not */
test_assert(strstr(bt, " backtrace_get") == NULL);
#elif (defined(HAVE_BACKTRACE_SYMBOLS) && defined(HAVE_EXECINFO_H)) || \
  (defined(HAVE_WALKCONTEXT) && defined(HAVE_UCONTEXT_H))
test_assert(backtrace_get() == 0);
/* it should have some kind of main in it */
test_assert(strstr(bt, "main") != NULL);
#else
/* should not work in this context */
test_assert(backtrace_get() == -1);
#endif
test_end();
}

The assertion failure and segfault happen in the second conditional
preprocessor block.  Do we execute the first block on systems where this
passes?  I wonder if backtrace_get() works at all in the second case?
--- End Message ---
--- Begin Message ---
Source: dovecot
Source-Version: 1:2.3.10.1+dfsg1-2
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated dovecot 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, 16 Jun 2020 08:29:02 -0700
Source: dovecot
Architecture: source
Version: 1:2.3.10.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Dovecot Maintainers 
Changed-By: Noah Meyerhans 
Closes: 951722 962630
Changes:
 dovecot (1:2.3.10.1+dfsg1-2) unstable; urgency=medium
 .
   * Support sd_notify with systemd (Closes: #951722)
   * Add necessary CFLAGS and LDFLAGS settings to ensure functional backtrace
 generation.  (Closes: #962630)
   * Suppress additional library-not-linked-against-libc lintian warnings some
 plugins as false-positives, observed on armel systems
 .
   [ Andreas Hasenack ]
   * d/t/control, d/t/testmails: cherry-pick updated autopkgtests from
 Ubuntu's 1:2.2.35-2ubuntu1:
 - d/t/testmails: dropped the hardcoded "Ubuntu" name from the banner
   text and made it distribution agnostic
 - d/t/control: added lsb-release to test dependencies, used to get the
   distribution name

Bug#962964: haskell-io-choice: Removal notice: broken and obsolete

[Ilias Tsitsimpis]

Source: haskell-io-choice
Version: 0.0.7-1
Severity: grave
Justification: renders package unusable

Since GHC 8.0, IO is now an instance of Alternative, making this package
obsolete (see https://github.com/kazu-yamamoto/io-choice/issues/6).
Newer versions of mighttpd2 do not depend on it anymore, so there are
no rev dependencies left.

I intend to remove this package.

-- 
Ilias

Bug#962875: [Debian-iot-maintainers] Processed: block 962875 with 962876 962877 962878 962879 962880 962881 962882 962883 962884 962885 962886 962887

[Nicolas Mora]

This bug will be resolved when Glewlwyd 2.x will be packaged into unstable.

I'm currently waiting for iddawc in the NEW queue to be accepted in
experimental to move on.



signature.asc
Description: OpenPGP digital signature

Processed: bug 962913 is forwarded to https://github.com/snoyberg/http-client/issues/400

[Debian Bug Tracking System]

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

> forwarded 962913 https://github.com/snoyberg/http-client/issues/400
Bug #962913 [src:haskell-http-conduit] haskell-http-conduit: FTBFS on IPv6-only 
host
Set Bug forwarded-to-address to 
'https://github.com/snoyberg/http-client/issues/400'.
> thanks
Stopping processing here.

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

Bug#962962: haskell-hstatsd: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-hstatsd
Version: 0.1-7
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (last upstream upload in 2013).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias

Bug#962961: haskell-gnutls: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-gnutls
Version: 0.2-6
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (homepage returns 404, last upload
from 2015). It does not build with GHC 8.8, is not part of Stackage and
has no rev dependencies.

I intend to remove this package.

-- 
Ilias

Bug#962959: haskell-edison-api: Removal notice: broken and unuseful

[Ilias Tsitsimpis]

Source: haskell-edison-api
Version: 1.3.1-5
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/robdockins/edison/pull/16

This package does not build with GHC 8.8 and is not part of Stackage.
Agda replaced Edison with Data.Sequence in the latest version, so there
are no rev dependencies anymore.

I intend to remove this package.

-- 
Ilias

Bug#816756: marked as done (php-pimple: Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 11:03:07 -0400
with message-id <0e947a8d-47e8-e4d5-4729-48ad53f74...@mailbox.org>
and subject line Re: #816756 php-pimple: Useless in Debian
has caused the Debian Bug report #816756,
regarding php-pimple: Useless in Debian
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.)


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

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing, and not let it block the PHP 7.0 transition. ]

I packaged php-pimle as used by owncloud, but owncloud is going away,
see #816376. There is a priori little point to ship php-pimple in a
stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.3.0-1

php-pimple is needed (at least temporarily) for php-slim 3.x, which is used by 
shaarli (ITP #864559).
This bug can be re-opened after shaarli moves to php-slim 4.x.



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

Bug#962958: haskell-edison-core: Removal notice: broken and unuseful

[Ilias Tsitsimpis]

Source: haskell-edison-core
Version: 1.3.2.1-3
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/robdockins/edison/pull/16

This package does not build with GHC 8.8 and is not part of Stackage.
Agda replaced Edison with Data.Sequence in the latest version, so there
are no rev dependencies anymore.

I intend to remove this package.

-- 
Ilias

Processed: found 962254 in 5.6.14-2, found 962254 in 5.7~rc5-1~exp1

[Debian Bug Tracking System]

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

> found 962254 5.6.14-2
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Marked as found in versions linux/5.6.14-2.
Marked as found in versions linux/5.6.14-2.
> found 962254 5.7~rc5-1~exp1
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Marked as found in versions linux/5.7~rc5-1~exp1.
Marked as found in versions linux/5.7~rc5-1~exp1.
> thanks
Stopping processing here.

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

Bug#962955: haskell-crypto-pubkey-openssh: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Source: haskell-crypto-pubkey-openssh
Version: 0.2.7-9
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/knsd/crypto-pubkey-openssh/pull/23

This package seems to be unmaintained (last upstream upload in 2015).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias

Bug#932296: qa.debian.org: getwatch filling up /tmp

[Julien Cristau]

On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote:
> Control: severity -1 serious
> 
> On Thu, Aug 08, 2019 at 01:45:27PM +0200, Julien Cristau wrote:
> > On Wed, Jul 17, 2019 at 10:11:39PM +0200, Lucas Nussbaum wrote:
> > > On 17/07/19 at 14:01 +0200, Julien Cristau wrote:
> > > > something in udd seems to extract entire source packages to
> > > > /tmp/getwatch.*.  This fills up the disk.  Please make it not do that.
> > > 
> > > Hi,
> > > 
> > > Thanks for reporting.
> > > 
> > > It needs to extract the source packages to get the watch file. I don't
> > > think there's a way to ask dpkg-source to only extract a single file,
> > > and I don't want to re-implement dpkg-source.
> > > 
> > It would be a single call to tar or patch though, which doesn't seem
> > like a huge amount of effort.
> > 
> > > Reviewing the code, there was a path where the tmp dir was not removed.
> > > I've fixed that. I'm not 100% sure this fixes everything, but it should
> > > clearly help.
> > > 
> > There were quite a few getwatch temp dirs before I rebooted ullmann just
> > now because it was out of space.
> > 
> > > However, I also note that /tmp is on /, and / is quite small (only 5.3
> > > GB remaining). Would it be possible to add some disk space for /tmp or /
> > > on ullmann?
> > > 
> > I'd dispute the "quite small" bit, extracting watch files shouldn't need
> > more than 5g.  But you could also put your temp files somewhere under
> > /srv?
> > 
> This happened again.  If it won't get fixed I'll go ahead and disable that 
> job.
> 
Done now, removed the "upstream" importer from the config file.

Cheers,
Julien

Bug#946308: freespace2: diff for NMU version 3.7.4+repack-1.1

[Dmitry Smirnov]

On Wednesday, 17 June 2020 12:05:19 AM AEST Adrian Bunk wrote:
> I've prepared an NMU for freespace2 (versioned as 3.7.4+repack-1.1) and
> uploaded it to DELAYED/14. Please feel free to tell me if I should
> cancel it.

Thank you very much for your help.

-- 
Cheers,
 Dmitry Smirnov.

---

A foolish faith in authority is the worst enemy of truth.
-- Albert Einstein


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

Bug#946308: freespace2: diff for NMU version 3.7.4+repack-1.1

[Adrian Bunk]

Control: tags 946308 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru freespace2-3.7.4+repack/debian/changelog freespace2-3.7.4+repack/debian/changelog
--- freespace2-3.7.4+repack/debian/changelog	2018-07-12 11:57:59.0 +0300
+++ freespace2-3.7.4+repack/debian/changelog	2020-06-16 16:22:34.0 +0300
@@ -1,3 +1,10 @@
+freespace2 (3.7.4+repack-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove -march=native usage. (Closes: #946308)
+
+ -- Adrian Bunk   Tue, 16 Jun 2020 16:22:34 +0300
+
 freespace2 (3.7.4+repack-1) unstable; urgency=medium
 
   * New upstream release [July 2016].
diff -Nru freespace2-3.7.4+repack/debian/patches/i386-baseline.patch freespace2-3.7.4+repack/debian/patches/i386-baseline.patch
--- freespace2-3.7.4+repack/debian/patches/i386-baseline.patch	1970-01-01 02:00:00.0 +0200
+++ freespace2-3.7.4+repack/debian/patches/i386-baseline.patch	2020-06-16 16:22:31.0 +0300
@@ -0,0 +1,15 @@
+Description: SSE is not part of the i386 baseline
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/946308
+
+--- freespace2-3.7.4+repack.orig/configure.ac
 freespace2-3.7.4+repack/configure.ac
+@@ -158,7 +158,7 @@ case "$target" in
+ 		fs2_os_linux="yes"
+ 
+ 		if test "$fs2_generic_architecture" = "yes" ; then
+-			D_CFLAGS="$D_CFLAGS -mtune=generic -mfpmath=sse -msse -msse2"
++			D_CFLAGS="$D_CFLAGS -mtune=generic"
+ 		else
+ 			D_CFLAGS="$D_CFLAGS -march=native"
+ 		fi
diff -Nru freespace2-3.7.4+repack/debian/patches/series freespace2-3.7.4+repack/debian/patches/series
--- freespace2-3.7.4+repack/debian/patches/series	2015-04-16 04:46:03.0 +0300
+++ freespace2-3.7.4+repack/debian/patches/series	2020-06-16 16:22:31.0 +0300
@@ -0,0 +1 @@
+i386-baseline.patch
diff -Nru freespace2-3.7.4+repack/debian/rules freespace2-3.7.4+repack/debian/rules
--- freespace2-3.7.4+repack/debian/rules	2018-07-12 11:47:25.0 +0300
+++ freespace2-3.7.4+repack/debian/rules	2020-06-16 16:22:31.0 +0300
@@ -15,7 +15,7 @@
 $(info DEB_BUILD_MAINT_OPTIONS:$(origin DEB_BUILD_MAINT_OPTIONS)=$(DEB_BUILD_MAINT_OPTIONS))
 
 #LDFLAGS+= -Wl,--as-needed
-CONF_O=--bindir=/usr/games --disable-silent-rules --enable-speech
+CONF_O=--bindir=/usr/games --disable-silent-rules --enable-speech --enable-generic-architecture
 
 %:
 	dh $@

Processed: freespace2: diff for NMU version 3.7.4+repack-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 946308 + pending
Bug #946308 [freespace2] /usr/games/fs2_open: fs2_open crashes immediately 
(illegal instruction)
Added tag(s) pending.

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

Bug#960424: marked as done (simgear: FTBFS with boost 1.71)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 13:18:43 +
with message-id 
and subject line Bug#960424: fixed in simgear 1:2020.1.2+dfsg-1
has caused the Debian Bug report #960424,
regarding simgear: FTBFS with boost 1.71
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.)


-- 
960424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simgear
Version: 1:2019.1.1+dfsg-3
Severity: important
User: team+bo...@tracker.debian.org
Usertags: boost1.71

simgear fails to build with boost 1.71. See
https://people.debian.org/~gio/boost_migration/simgear.log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: simgear
Source-Version: 1:2020.1.2+dfsg-1
Done: to...@debian.org (Dr. Tobias Quathamer)

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

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated simgear package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Jun 2020 14:43:20 +0200
Source: simgear
Architecture: source
Version: 1:2020.1.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew 
Changed-By: Dr. Tobias Quathamer 
Closes: 960424
Changes:
 simgear (1:2020.1.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 2020.1.2+dfsg
 - Fixes FTBFS with boost 1.71. Closes: #960424
 - Refresh patches
   * Use debhelper-compat 13
   * Update Standards-Version to 4.5.0, no changes needed
Checksums-Sha1:
 dead681b4eb193b38c227f84818e156248f784bf 2209 simgear_2020.1.2+dfsg-1.dsc
 947290593170f5dc004e1bbae2922447f7758545 1140916 
simgear_2020.1.2+dfsg.orig.tar.xz
 8bf2bcd3a4c87c35c04cca8ce5a80edd0aba1b0b 16812 
simgear_2020.1.2+dfsg-1.debian.tar.xz
 ee4170ae9cf22a9768baf7da4842344f965dcd89 13857 
simgear_2020.1.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 7e9941d097d95a57acfed12d6e0202d103a2a6c63866adf970c57a03d21f3d27 2209 
simgear_2020.1.2+dfsg-1.dsc
 c6bff434dc58ae834d7839be85af7c3a432f3f794e3f8ca2a72c09779e21f85d 1140916 
simgear_2020.1.2+dfsg.orig.tar.xz
 4d1c6e0acc3671d9e0385271f40c55a0e59e400da40c50afe160da01b6f9c1c7 16812 
simgear_2020.1.2+dfsg-1.debian.tar.xz
 498bce68fc64963fda18e95aefb00c9f4fc67f354d4fc3929ab2740fe50965ca 13857 
simgear_2020.1.2+dfsg-1_amd64.buildinfo
Files:
 e92ee0cb9f414a8fa0bc8bdf9407a2ee 2209 libs optional simgear_2020.1.2+dfsg-1.dsc
 ab54af2e00c1352a067d2c102b7249ba 1140916 libs optional 
simgear_2020.1.2+dfsg.orig.tar.xz
 7fa76433e4882add424a279ba4382c62 16812 libs optional 
simgear_2020.1.2+dfsg-1.debian.tar.xz
 fd59234c0bc9ec916a946ae68052fca2 13857 libs optional 
simgear_2020.1.2+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl7owI8ACgkQEwLx8Dbr
6xnVIg/8DAirJvg7JhsknL2bJBNNm5Fu7zH5UD8hwLeCcUisx5jizqm0WloqCxD/
DgicSBVgyNapFZ7KDNu1pW9Uyf7cvvKY4HMRmTlZ61z5yIpuDCK8AHYbKw0j+sR7
AGPKmjtW+owJ2m6jMMidHKOLfSHSTj2ZbYfTlPDlAklvpd1BVQ/ihHd1ZUud1jby
skQYasutg9TW92u32+GTiKrdla3yIdRmIptZw/nT+djXiQBxW7hol29hCMZthylH
N8w7MigV/aUWyvK5ugSSt/r084hgMRQT2ipeFplBVilA+WzXdORMc/nb8oax2bS2
WuRk2iDShHRsA9NnbCoaPrQsa6uM8k/rvfDOlI7KeJ/bE9dhrnD5qvE0Vh43IhZH
qAt6njsTJyNrQ4rJ5selouKEIwz2bUibemgaXG67aX8tbBEBzGH03bpAzsygrEV1
TfDJQRYfifO8Tn4pVzl0g30pTWBYg11O89SL3B++zyM9rwDgxRDP8oMxmvvaKIuY
YU0b52ah8VfXotL08K2DIwP43vqatIYmfheFlwXE8WjxgbeqG04jYhETFltlnoyF
2GbUpLsPJ7gai5ZBwNeO9EL9e9ze3VmUdPt0HidWMxIq76IlkGl3SY9cwKIU6gPq
cbfUVt4hpg3eqjRocgQ/aHmtWfgW2jvh30lvWqWWe3GBWxx1veQ=
=rvDo
-END PGP SIGNATURE End Message ---

Bug#960424: simgear: diff for NMU version 1:2019.1.1+dfsg-3.1

[Dr. Tobias Quathamer]

Am 16.06.20 um 13:57 schrieb Sudip Mukherjee:
> Control: tags 960424 + patch
> Control: tags 960424 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for simgear (versioned as 1:2019.1.1+dfsg-3.1) and
> uploaded it to mentors for sponsoring. Please feel free to tell me if I
> should remove it.

Hi Sudip,

thanks a lot for your patch! However, I did not use it, because it
finally motivated me to update the package to the latest upstream
version. With that update, the FTBFS is also fixed.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#953028: marked as done (node-nodedbi: Not compatible with Node.js ≥ 12)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 12:03:52 +
with message-id 
and subject line Bug#953028: fixed in node-nodedbi 1.0.13+dfsg-2
has caused the Debian Bug report #953028,
regarding node-nodedbi: Not compatible with Node.js ≥ 12
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.)


-- 
953028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-nodedbi
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

node-nodedbi is not compatible with Node.js ≥ 12. This RC bug will
permit to remove this (useless for now) package from testing to permit
Node.js 12 migration.
--- End Message ---
--- Begin Message ---
Source: node-nodedbi
Source-Version: 1.0.13+dfsg-2
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
node-nodedbi, 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.
Xavier Guimard  (supplier of updated node-nodedbi 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, 16 Jun 2020 13:31:42 +0200
Source: node-nodedbi
Architecture: source
Version: 1.0.13+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 953028
Changes:
 node-nodedbi (1.0.13+dfsg-2) unstable; urgency=medium
 .
   [ Xavier Guimard ]
   * Declare compliance with policy 4.5.0
 .
   [ Jérémy Lal ]
   * Add fix for nodejs ≥ 12 (Closes: #953028)
Checksums-Sha1: 
 c2767f4f4a164cd9e4861d48566e09d8f3b21077 2157 node-nodedbi_1.0.13+dfsg-2.dsc
 60ed6c220f9e135377c39e1211c559e7cfa1ce33 5132 
node-nodedbi_1.0.13+dfsg-2.debian.tar.xz
Checksums-Sha256: 
 a8751d624a1e1b259a4cfe0b3758e852fc3132316632015fb0e521e482ca5d23 2157 
node-nodedbi_1.0.13+dfsg-2.dsc
 b227f158fb38e771194cd14fd1bbeddcba482baf8d4924faff36c4d11b909a0f 5132 
node-nodedbi_1.0.13+dfsg-2.debian.tar.xz
Files: 
 004a602742ea58a86ea5e01a4b4253fe 2157 javascript optional 
node-nodedbi_1.0.13+dfsg-2.dsc
 694dbb79c16032a9c476d36c721e9269 5132 javascript optional 
node-nodedbi_1.0.13+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl7osCIACgkQ9tdMp8mZ
7umt6w/+Pl8/ldwbWUA02Xyq8aiLS0GGUds/t44mSoGJzJsa+EYO7ww1fVU59q2i
ACSbhV22WjUrCdJr80Hm2+TrX+42yE2kPhxWahJpbwSGhRKtwMkhvUgkF0dCc85+
5NBtr31sdc80QxiQG/eyW0IfooHqQOuyaOEn4LqqwezSG5g0vfvgaz4SFZdylrNJ
JqR01lXYUnPb6PWDzhD/ynw+0k/be0q05Ywsl8aKdfeB67lmfepkxgXN6UgsAUmA
z7cTKQMivBQyzp2rLVC3fwaM9+w5KPWdwzGt1vcKMxxSf30uh1KdQI1DnZ2aY96L
t/RQMdDukaC0BXr9pc9Niru+p4hYiid8GkvrgELKxmFazWFiidGFpQmy6DURdez7
cp8nMoPbUX2BPtd9/1HXGaIjXTXY1jXIoX8AI/rSIYjZ3f4fWRSuArB7RH03W+tw
GdQbQW1LtqhMM5Ne21Ip21sZEdGjYgR98xpOOgGHDPMJHtcPdbly7eUNKnfMConn
uiQXRLElGVTnWyfd9EiFNPXRInDxqKPXIp3ujTL4e0+g19WbS0NKt5T6HrndHWZu
E5vWBGcJFpHGvjd/zAQjHXbOrRLru6lHJoToc5jrWZH/U8u6zNZrF82K6XWrt+5/
ni8iPa5PAs7ByB7SnsJOY7BV06hma7bFuNfegAR4UxzuBACmVgw=
=trUv
-END PGP SIGNATURE End Message ---

Bug#960424: simgear: diff for NMU version 1:2019.1.1+dfsg-3.1

[Sudip Mukherjee]

Control: tags 960424 + patch
Control: tags 960424 + pending

Dear maintainer,

I've prepared an NMU for simgear (versioned as 1:2019.1.1+dfsg-3.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru simgear-2019.1.1+dfsg/debian/changelog 
simgear-2019.1.1+dfsg/debian/changelog
--- simgear-2019.1.1+dfsg/debian/changelog  2019-11-14 08:01:57.0 
+
+++ simgear-2019.1.1+dfsg/debian/changelog  2020-06-16 12:29:15.0 
+0100
@@ -1,3 +1,11 @@
+simgear (1:2019.1.1+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with boost 1.71. (Closes: #960424)
+- Fix breaking change with osgText.
+
+ -- Sudip Mukherjee   Tue, 16 Jun 2020 12:29:15 
+0100
+
 simgear (1:2019.1.1+dfsg-3) unstable; urgency=medium
 
   * Team upload
diff -Nru 
simgear-2019.1.1+dfsg/debian/patches/0001-osgText.getActiveFont-Breaking-change-within-OSG.patch
 
simgear-2019.1.1+dfsg/debian/patches/0001-osgText.getActiveFont-Breaking-change-within-OSG.patch
--- 
simgear-2019.1.1+dfsg/debian/patches/0001-osgText.getActiveFont-Breaking-change-within-OSG.patch
1970-01-01 01:00:00.0 +0100
+++ 
simgear-2019.1.1+dfsg/debian/patches/0001-osgText.getActiveFont-Breaking-change-within-OSG.patch
2020-06-16 12:29:15.0 +0100
@@ -0,0 +1,79 @@
+From d883ab278d10c89580d5bbc4473d2e9fc375b7b9 Mon Sep 17 00:00:00 2001
+From: Scott Giese 
+Date: Sun, 4 Aug 2019 02:27:57 -0500
+Subject: [PATCH] [osgText.getActiveFont] Breaking change within OSG
+
+---
+
+upstream link: 
https://github.com/FlightGear/simgear/commit/d883ab278d10c89580d5bbc4473d2e9fc375b7b9
+issue link: 
https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/d3396d2b-0ce6-490e-b32f-42174895b...@flightgear.org/
+
+ simgear/canvas/elements/CanvasText.cxx | 22 +-
+ 1 file changed, 17 insertions(+), 5 deletions(-)
+
+diff --git a/simgear/canvas/elements/CanvasText.cxx 
b/simgear/canvas/elements/CanvasText.cxx
+index 3051045f..060436e1 100644
+--- a/simgear/canvas/elements/CanvasText.cxx
 b/simgear/canvas/elements/CanvasText.cxx
+@@ -53,10 +53,13 @@ namespace canvas
+   TextLine lineAt(size_t i) const;
+ 
+   /// Get nearest line to given y-coordinate
++#if OSG_VERSION_LESS_THAN(3,6,5)
+   TextLine nearestLine(float pos_y) const;
+-
+-
+   SGVec2i sizeForWidth(int w) const;
++#else
++  TextLine nearestLine(float pos_y);
++  SGVec2i sizeForWidth(int w);
++#endif
+ 
+   osg::BoundingBox
+ #if OSG_VERSION_LESS_THAN(3,3,2)
+@@ -319,9 +322,14 @@ namespace canvas
+   }
+ 
+   
//
++#if OSG_VERSION_LESS_THAN(3,6,5)
+   TextLine Text::TextOSG::nearestLine(float pos_y) const
++#else
++  TextLine Text::TextOSG::nearestLine(float pos_y)
++#endif
+   {
+-osgText::Font const* font = getActiveFont();
++auto font = getActiveFont();
++
+ if( !font || lineCount() <= 0 )
+   return TextLine(0, this);
+ 
+@@ -343,12 +351,16 @@ namespace canvas
+   // simplified version of osgText::Text::computeGlyphRepresentation() to
+   // just calculate the size for a given weight. Glpyh calculations/creating
+   // is not necessary for this...
++#if OSG_VERSION_LESS_THAN(3,6,5)
+   SGVec2i Text::TextOSG::sizeForWidth(int w) const
++#else
++  SGVec2i Text::TextOSG::sizeForWidth(int w)
++#endif
+   {
+ if( _text.empty() )
+   return SGVec2i(0, 0);
+ 
+-osgText::Font* activefont = const_cast(getActiveFont());
++auto activefont = getActiveFont();
+ if( !activefont )
+   return SGVec2i(-1, -1);
+ 
+@@ -727,7 +739,7 @@ namespace canvas
+   }
+ 
+ #else
+-  void Text::TextOSG::computePositionsImplementation() 
++  void Text::TextOSG::computePositionsImplementation()
+   {
+   TextBase::computePositionsImplementation();
+   }
+-- 
+2.11.0
+
diff -Nru simgear-2019.1.1+dfsg/debian/patches/fix_boost.patch 
simgear-2019.1.1+dfsg/debian/patches/fix_boost.patch
--- simgear-2019.1.1+dfsg/debian/patches/fix_boost.patch1970-01-01 
01:00:00.0 +0100
+++ simgear-2019.1.1+dfsg/debian/patches/fix_boost.patch2020-06-16 
12:12:52.0 +0100
@@ -0,0 +1,34 @@
+Description: Fix FTBFS with boost 1.71
+ The macro Boost_VERSION returned 1.71.0. Based on: 
https://cmake.org/cmake/help/v3.15/module/FindBoost.html
+ we should use Boost_VERSION_MACRO to get the version in the form of 107100.
+ Fixing boost dependency brought out the problem with include folder.
+ The header files were created in build/simgear folder and the source files
+ included 'simgear/simgear_config.h' which was not found as 'build' was
+ not in the include path.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/960424
+
+---
+
+--- simgear-2019.1.1+dfsg.orig/CMakeLists.txt
 simgear-2019.1.1+dfsg/CMakeLists.txt
+@@ -519,6 +519,7 @@ include(CheckCXXFeatures)
+ # use BEFORE to ensure local directories are used first,
+ # 

Processed: simgear: diff for NMU version 1:2019.1.1+dfsg-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 960424 + patch
Bug #960424 [src:simgear] simgear: FTBFS with boost 1.71
Added tag(s) patch.
> tags 960424 + pending
Bug #960424 [src:simgear] simgear: FTBFS with boost 1.71
Added tag(s) pending.

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

Processed: ppl: diff for NMU version 1:1.2-8.1

[Debian Bug Tracking System]

Processing control commands:

> tags 959623 + patch
Bug #959623 [src:ppl] ppl: FTBFS: swi_cfli.hh:351:35: error: cannot convert 
‘int*’ to ‘size_t*’ {aka ‘long unsigned int*’}
Added tag(s) patch.
> tags 959623 + pending
Bug #959623 [src:ppl] ppl: FTBFS: swi_cfli.hh:351:35: error: cannot convert 
‘int*’ to ‘size_t*’ {aka ‘long unsigned int*’}
Added tag(s) pending.

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

Bug#959623: ppl: diff for NMU version 1:1.2-8.1

[Adrian Bunk]

Control: tags 959623 + patch
Control: tags 959623 + pending

Dear maintainer,

I've prepared an NMU for ppl (versioned as 1:1.2-8.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru ppl-1.2/debian/changelog ppl-1.2/debian/changelog
--- ppl-1.2/debian/changelog	2020-03-04 09:08:43.0 +0200
+++ ppl-1.2/debian/changelog	2020-06-16 12:46:14.0 +0300
@@ -1,3 +1,10 @@
+ppl (1:1.2-8.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS with swi-prolog 8.2. (Closes: #959623)
+
+ -- Adrian Bunk   Tue, 16 Jun 2020 12:46:14 +0300
+
 ppl (1:1.2-8) unstable; urgency=medium
 
   * Add latex_include_ifthen_package.patch. (Closes: #943451)
diff -Nru ppl-1.2/debian/patches/series ppl-1.2/debian/patches/series
--- ppl-1.2/debian/patches/series	2020-02-22 13:52:51.0 +0200
+++ ppl-1.2/debian/patches/series	2020-06-16 12:46:14.0 +0300
@@ -4,3 +4,4 @@
 fix_latex_build.patch
 fix_AC_CHECK_SWI_PROLOG.patch
 latex_include_ifthen_package.patch
+swi82.patch
diff -Nru ppl-1.2/debian/patches/swi82.patch ppl-1.2/debian/patches/swi82.patch
--- ppl-1.2/debian/patches/swi82.patch	1970-01-01 02:00:00.0 +0200
+++ ppl-1.2/debian/patches/swi82.patch	2020-06-16 12:46:14.0 +0300
@@ -0,0 +1,166 @@
+Description: Fix FTBFS with swi-prolog 8.2
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/959623
+
+--- ppl-1.2.orig/interfaces/Prolog/Ciao/ciao_cfli.hh
 ppl-1.2/interfaces/Prolog/Ciao/ciao_cfli.hh
+@@ -296,7 +296,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ inline int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   *ap = ciao_structure_name(t);
+   *ip = ciao_structure_arity(t);
+--- ppl-1.2.orig/interfaces/Prolog/GNU/gprolog_cfli.hh
 ppl-1.2/interfaces/Prolog/GNU/gprolog_cfli.hh
+@@ -420,7 +420,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ inline int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   Rd_Compound_Check(t, ap, ip);
+   return 1;
+--- ppl-1.2.orig/interfaces/Prolog/SICStus/sicstus_cfli.h
 ppl-1.2/interfaces/Prolog/SICStus/sicstus_cfli.h
+@@ -134,7 +134,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+ 
+ PCFLI_DECLSPEC int
+ Prolog_get_compound_name_arity(Prolog_term_ref t,
+-   Prolog_atom& name, int& arity);
++   Prolog_atom& name, size_t& arity);
+ 
+ PCFLI_DECLSPEC int
+ Prolog_get_arg(int i, Prolog_term_ref t, Prolog_term_ref a);
+--- ppl-1.2.orig/interfaces/Prolog/SICStus/sicstus_cfli.ic
 ppl-1.2/interfaces/Prolog/SICStus/sicstus_cfli.ic
+@@ -262,7 +262,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ PCFLI_EXTERN_INLINE int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   return SP_get_functor(t, ap, ip);
+ }
+--- ppl-1.2.orig/interfaces/Prolog/SWI/swi_cfli.hh
 ppl-1.2/interfaces/Prolog/SWI/swi_cfli.hh
+@@ -346,7 +346,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ inline int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   return PL_get_name_arity(t, ap, ip);
+ }
+--- ppl-1.2.orig/interfaces/Prolog/XSB/xsb_cfli.hh
 ppl-1.2/interfaces/Prolog/XSB/xsb_cfli.hh
+@@ -314,7 +314,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ inline int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   *ap = p2c_functor(t);
+   *ip = p2c_arity(t);
+--- ppl-1.2.orig/interfaces/Prolog/YAP/yap_cfli.hh
 ppl-1.2/interfaces/Prolog/YAP/yap_cfli.hh
+@@ -313,7 +313,7 @@ Prolog_get_atom_name(Prolog_term_ref t,
+   The behavior is undefined if \p t is not a Prolog compound term.
+ */
+ inline int
+-Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, int* ip) {
++Prolog_get_compound_name_arity(Prolog_term_ref t, Prolog_atom* ap, size_t* ip) {
+   assert(Prolog_is_compound(t));
+   YAP_Functor f = YAP_FunctorOfTerm(t);
+   *ap = YAP_NameOfFunctor(f);
+--- ppl-1.2.orig/interfaces/Prolog/ppl_interface_generator_prolog_cc_code.m4
 

Bug#962944: python3-biopython needs Breaks: cnvkit (<< 0.9.7-1~)

[Adrian Bunk]

Package: python3-biopython
Version: 1.77+dfsg-1
Severity: serious
Control: block 959587 by -1

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cnvkit/5912015/log.gz

...
Unpacking python3-biopython (1.77+dfsg-1) ...
...
Unpacking cnvkit (0.9.6-3) ...
...
Traceback (most recent call last):
  File "/usr/bin/cnvkit", line 8, in 
from cnvlib import commands
  File "/usr/lib/python3/dist-packages/cnvlib/__init__.py", line 5, in 
from .commands import *
  File "/usr/lib/python3/dist-packages/cnvlib/commands.py", line 32, in 
from . import (access, antitarget, autobin, batch, call, core, coverage,
  File "/usr/lib/python3/dist-packages/cnvlib/autobin.py", line 11, in 
from . import coverage, samutil
  File "/usr/lib/python3/dist-packages/cnvlib/coverage.py", line 15, in 
from Bio._py3k import StringIO
ModuleNotFoundError: No module named 'Bio._py3k'
make: *** [Makefile:51: build/reference-picard.cnn] Error 1

Processed: python3-biopython needs Breaks: cnvkit (<< 0.9.7-1~)

[Debian Bug Tracking System]

Processing control commands:

> block 959587 by -1
Bug #959587 {Done: =?utf-8?q?Dylan_A=C3=AFssi?= } 
[src:python-biopython] python-biopython: FTBFS: AssertionError: False is not 
true
959587 was not blocked by any bugs.
959587 was not blocking any bugs.
Added blocking bug(s) of 959587: 962944

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

Bug#962928: marked as done (python-pymzml FTBFS: LaTeX Error: Unknown graphics extension: .svg)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 11:34:51 +
with message-id 
and subject line Bug#962928: fixed in python-pymzml 2.4.7-2
has caused the Debian Bug report #962928,
regarding python-pymzml FTBFS: LaTeX Error: Unknown graphics extension: .svg
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.)


-- 
962928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pymzml
Version: 2.4.7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-pymzml=all=2.4.7-1=1592254701=0

...
Running 'pdflatex   -recorder  "pymzML.tex"'

Latexmk: applying rule 'pdflatex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./pymzML.tex
LaTeX2e <2020-02-02> patch level 5
L3 programming layer <2020-05-15> (./sphinxmanual.cls
Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2019/12/20 v1.4l Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty)
(/usr/share/texlive/texmf-dist/tex/latex/fncychap/fncychap.sty) (./sphinx.sty
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty)
(/usr/share/texlive/texmf-dist/tex/latex/titlesec/titlesec.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tabulary/tabulary.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
(/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty)
(/usr/share/texlive/texmf-dist/tex/latex/varwidth/varwidth.sty)
(./sphinxmulticell.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
(/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty)
(./footnotehyper-sphinx.sty)
(/usr/share/texlive/texmf-dist/tex/latex/float/float.sty)
(/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/parskip/parskip.sty
(/usr/share/texlive/texmf-dist/tex/latex/parskip/parskip-2001-04-09.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty)
(/usr/share/texlive/texmf-dist/tex/latex/upquote/upquote.sty)
(/usr/share/texlive/texmf-dist/tex/latex/capt-of/capt-of.sty)
(/usr/share/texlive/texmf-dist/tex/latex/needspace/needspace.sty)
(./sphinxhighlight.sty)
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
(/usr/share/texlive/texmf-dist/tex/generic/iftex/ifvtex.sty
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/latex/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))

Bug#953028: marked as pending in node-nodedbi

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #953028 in node-nodedbi reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-nodedbi/-/commit/7f29824eaaeb6ecaa38c0289dd4fc2616e6d5a10


Update patch

Closes: #953028


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953028

Processed: Bug#953028 marked as pending in node-nodedbi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953028 [node-nodedbi] node-nodedbi: Not compatible with Node.js ≥ 12
Ignoring request to alter tags of bug #953028 to the same tags previously set

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

Processed: reassign 934160 to src:linux, forcibly merging 962254 934160 ..., tagging 962254

[Debian Bug Tracking System]

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

> reassign 934160 src:linux
Bug #934160 [nfs-common] nfs-common: Umask ignored, all files created 
world-writable on NFS
Bug reassigned from package 'nfs-common' to 'src:linux'.
No longer marked as found in versions nfs-utils/1:1.3.4-2.5.
Ignoring request to alter fixed versions of bug #934160 to the same values 
previously set
> forcemerge 962254 934160
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-nfs/20200616052835.ga19...@lorien.valinor.li/T/#m9c41f33123a7c44cdd7fa07611c678c1b0dace61'.
Marked as found in versions linux/4.19.118-2.
Merged 934160 962254
> forwarded 962254 
> https://lore.kernel.org/linux-nfs/20200616052835.ga19...@lorien.valinor.li/T/#m9c41f33123a7c44cdd7fa07611c678c1b0dace61
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Ignoring request to change the forwarded-to-address of bug#962254 to the same 
value
Ignoring request to change the forwarded-to-address of bug#934160 to the same 
value
> tags 962254 + upstream
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Bug #934160 [src:linux] nfs-common: Umask ignored, all files created 
world-writable on NFS
Added tag(s) upstream.
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 962254 is forwarded to https://lore.kernel.org/linux-nfs/20200616052835.ga19...@lorien.valinor.li/T/#m9c41f33123a7c44cdd7fa07611c678c1b0dace61

[Debian Bug Tracking System]

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

> forwarded 962254 
> https://lore.kernel.org/linux-nfs/20200616052835.ga19...@lorien.valinor.li/T/#m9c41f33123a7c44cdd7fa07611c678c1b0dace61
Bug #962254 [src:linux] NFS v4.2 broken between 4.9 and 4.15
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-nfs/20200616052835.ga19...@lorien.valinor.li/T/#m9c41f33123a7c44cdd7fa07611c678c1b0dace61'.
> thanks
Stopping processing here.

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

Processed: notfound 962858 in 0.7.0-3

[Debian Bug Tracking System]

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

> notfound 962858 0.7.0-3
Bug #962858 {Done: Emmanuel Thomas-Maurin } [src:tickr] 
tickr FTBFS on several architectures: must be linked with libm
No longer marked as found in versions tickr/0.7.0-3.
> thanks
Stopping processing here.

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

Bug#962858: marked as done (tickr FTBFS on several architectures: must be linked with libm)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 11:09:40 +0200
with message-id <105de96d-60f2-017f-adc5-e00c62bd8...@gmail.com>
and subject line Fixed in version 0.7.0-3 which *is* linked with libm
has caused the Debian Bug report #962858,
regarding tickr FTBFS on several architectures: must be linked with libm
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.)


-- 
962858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tickr
Version: 0.7.0-1
Severity: serious
Tags: ftbfs

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

...
gcc -O2 -Wall -Wextra -Wunused-parameter -Wshadow -Wpointer-arith -ffast-math 
-pedantic -Wno-variadic-macros -fmax-errors=5 -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/arm-linux-gnueabihf/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/arm-linux-gnueabihf/glib-2.0/include 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libxml2 -I/usr/include/p11-kit-1 -I/usr/include/fribidi -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,defs -Wl,--as-needed ../libetm-0.5.0/libetm.a 
-Wl,-z,relro -o tickr tickr-tickr_main.o tickr-tickr_resource.o 
tickr-tickr_render.o tickr-tickr_params.o tickr-tickr_clock.o 
tickr-tickr_feedparser.o tickr-tickr_list.o tickr-tickr_feedpicker.o 
tickr-tickr_prefwin.o tickr-tickr_otherwins.o tickr-tickr_misc.o 
tickr-tickr_helptext.o tickr-tickr_opml.o tickr-tickr_http.o 
tickr-tickr_connectwin.o tickr-tickr_quickfeedpicker.o tickr-tickr_quicksetup.o 
tickr-tickr_check4updates.o tickr-tickr_error.o tickr-tickr_tls.o 
../libetm-0.5.0/libetm.a -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 
-lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 
-lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lxml2 -lgnutls -lfribidi
/usr/bin/ld: ../libetm-0.5.0/libetm.a(libetm_a-str_mem.o): undefined reference 
to symbol 'floor@@GLIBC_2.4'
/usr/bin/ld: /lib/arm-linux-gnueabihf/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:420: tickr] Error 1
--- End Message ---
--- Begin Message ---
Source: tickr
Version: 0.7.0-1

Fixed in version 0.7.0-3 which *is* linked with libm.

-- 
Emmanuel Thomas-Maurin--- End Message ---

Bug#953028: marked as pending in node-nodedbi

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #953028 in node-nodedbi reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-nodedbi/-/commit/7f29824eaaeb6ecaa38c0289dd4fc2616e6d5a10


Update patch

Closes: #953028


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953028

Processed: Bug#953028 marked as pending in node-nodedbi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953028 [node-nodedbi] node-nodedbi: Not compatible with Node.js ≥ 12
Added tag(s) pending.

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

Bug#960326: marked as done (json-c: CVE-2020-12762)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 08:33:37 +
with message-id 
and subject line Bug#960326: fixed in json-c 0.13.1+dfsg-8
has caused the Debian Bug report #960326,
regarding json-c: CVE-2020-12762
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.)


-- 
960326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: json-c
Version: 0.13.1+dfsg-7
Severity: important
Tags: security upstream
Forwarded: https://github.com/json-c/json-c/pull/592

Hi,

The following vulnerability was published for json-c.

CVE-2020-12762[0]:
| json-c through 0.14 has an integer overflow and out-of-bounds write
| via a large JSON file, as demonstrated by printbuf_memappend.


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-12762
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12762
[1] https://github.com/json-c/json-c/pull/592

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: json-c
Source-Version: 0.13.1+dfsg-8
Done: Gianfranco Costamagna 

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated json-c 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Jun 2020 09:45:32 +0200
Source: json-c
Binary: libjson-c4 libjson-c-dev libjson-c-doc libjson-c4-udeb
Architecture: source
Version: 0.13.1+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gianfranco Costamagna 
Description:
 libjson-c-dev - JSON manipulation library - development files
 libjson-c-doc - JSON manipulation library - documentation files
 libjson-c4 - JSON manipulation library - shared library
 libjson-c4-udeb - JSON manipulation library - shared library (udeb) (udeb)
Closes: 960326
Changes:
 json-c (0.13.1+dfsg-8) unstable; urgency=medium
 .
   [ Leonidas S. Barbosa ]
   * SECURITY UPDATE: Integer overflows
 - debian/patches/CVE-2020-12762-*.patch: fix a series of
   integer overflows adding checks in linkhash.c, printbuf.c, test4.c
   test4.expected.
 - CVE-2020-12762
 .
   [ Gianfranco Costamagna ]
   * QA upload
   * Import Ubuntu patch (Closes: #960326)
Checksums-Sha1:
 1cce30d4212b8e1185b44cf8d30d6aeda037e0d7 2072 json-c_0.13.1+dfsg-8.dsc
 bd1698ca95d41cef49875140c3ecb1ddf485876c 9980 
json-c_0.13.1+dfsg-8.debian.tar.xz
 deaa02f9c23b75c3965eaa3cb5ff540175c7bf58 7347 
json-c_0.13.1+dfsg-8_source.buildinfo
Checksums-Sha256:
 003cb09d1dc78e3b54f04245ff1ece878253b9c07234a8fa1dfc3c9857affeac 2072 
json-c_0.13.1+dfsg-8.dsc
 f3b53b1a1f9f22558d86ace861937cfad077507fafefdcb528ac5a8f8a829530 9980 
json-c_0.13.1+dfsg-8.debian.tar.xz
 18d4c7deda5faf7ab7910f09b90f9fce4db1058d44ab8fc67b6da9d2691750a2 7347 
json-c_0.13.1+dfsg-8_source.buildinfo
Files:
 3e6765ccebe115b177311faafac52196 2072 libs optional json-c_0.13.1+dfsg-8.dsc
 adec1a144234e57c59e66106dcb896ba 9980 libs optional 
json-c_0.13.1+dfsg-8.debian.tar.xz
 bc3d83fc4b87d18523ea21967ddbfaf8 7347 libs optional 
json-c_0.13.1+dfsg-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl7oegAACgkQ808JdE6f
Xdm8ug/9H97ISB9483O4xxK3pWXD+rZGlcSoyOjDp/weDMDgfbCAYg8G9rPKMKpp
ZSklhK3vdCzYRCzCbqcOMkpwsD8AcGKvS+p62Cr2XibwtKQFIkb3SHi97ytvMi33
qNg10oPAmH4hHEWZXYf2kIwioZSqK8AE5v66BOdHCQMp4XIco99z5wndIydqREcM
7dmZs49fFbq5e+uo6JLd+0skQ7X54GG3UKHFJWHAHQbXoYu5n7uPmra8E6JPCMHn
8jEWBJUp8IoC1dy0VbQTuYAR57rA/89sCF2CGXVOiicIdSD3JLEEe8+otaE1+beM
cOdG2ADuUDQY/tFwQgEv/7dKm7IqTePN7n83tDKJKfDYLlnvXyiEh5miqpULzlyx
PvQQJUyUX0FUXBoSrpXrW+JyzaiZqg53lRwq1XACTiXEYC/Xwzs8afP32znMhvk2
PtJN0tw+TMjv7F3+0YHbpoNnurXVN8mUr1Cni7mR2lc7RlzlL4niyKZN0c5LEeaI
cljegzBNdJk61gSQ0HqV1CNCGN1wb2UYBDR0SdN1Sfah1cBFsAwxZ3HdaIwM2fWr

Bug#962938: lasagne: autopkgtest fails with newer python-mock

[Ondřej Nový]

Source: lasagne
Version: 0.1+git20200419.5d3c63c+ds-1
Severity: serious

lasagne's autopkgtest fails with newer python-mock 4.0.2-1.

Fails are in layers/test_helper.py, see:
https://ci.debian.net/data/autopkgtest/testing/amd64/l/lasagne/5909523/log.gz

Thanks for fixing.

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

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

Bug#954711: sight: diff for NMU version 19.0.0-6.1

[Flavien Bridault]

Hi Andreas and Adrian,

We are polishing Sight 20.0 and we should release by the end of the week
or maybe next week, with the included fix (or somehow, because we simply
stopped using ::boost::regex). However I can not ensure the update of
the package will be smooth, so having a working package based 19.0.0 in
the meantime is probably safer.

Thanks for your work !

Le 15/06/2020 à 21:36, Andreas Tille a écrit :
> Hi Adrian,
>
> thanks a lot for your effort.  I've injected the diff into Git.
>
> Flavien, it would be great if you could integrate this upstream
> and issue a new release.
>
> Kind regards
>
>Andreas.
>
> On Mon, Jun 15, 2020 at 06:35:02PM +0300, Adrian Bunk wrote:
>> Control: tags 954711 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for sight (versioned as 19.0.0-6.1) and uploaded
>> it to DELAYED/2. Please feel free to tell me if I should cancel it.
>>
>> cu
>> Adrian
>> diff -Nru sight-19.0.0/debian/changelog sight-19.0.0/debian/changelog
>> --- sight-19.0.0/debian/changelog2020-04-25 15:47:51.0 +0300
>> +++ sight-19.0.0/debian/changelog2020-06-15 18:20:23.0 +0300
>> @@ -1,3 +1,11 @@
>> +sight (19.0.0-6.1) unstable; urgency=high
>> +
>> +  * Non-maintainer upload.
>> +  * Add patch from Giovanni Mascellani for FTBFS with Boost 1.71.
>> +(Closes: #954711)
>> +
>> + -- Adrian Bunk   Mon, 15 Jun 2020 18:20:23 +0300
>> +
>>  sight (19.0.0-6) unstable; urgency=medium
>>  
>>[ Etienne Mollier ]
>> diff -Nru sight-19.0.0/debian/patches/0007-Fix-FTBFS-with-Boost-1.71.patch 
>> sight-19.0.0/debian/patches/0007-Fix-FTBFS-with-Boost-1.71.patch
>> --- sight-19.0.0/debian/patches/0007-Fix-FTBFS-with-Boost-1.71.patch 
>> 1970-01-01 02:00:00.0 +0200
>> +++ sight-19.0.0/debian/patches/0007-Fix-FTBFS-with-Boost-1.71.patch 
>> 2020-06-15 18:20:20.0 +0300
>> @@ -0,0 +1,34 @@
>> +From: Giovanni Mascellani 
>> +Date: Sun, 22 Mar 2020 14:34:26 +0100
>> +Subject: Fix FTBFS with Boost 1.71.
>> +
>> +Apparently CMake expects library names to be lowercase.
>> +---
>> + Bundles/ui/guiQml/CMakeLists.txt | 2 +-
>> + Bundles/ui/guiQt/CMakeLists.txt  | 2 +-
>> + 2 files changed, 2 insertions(+), 2 deletions(-)
>> +
>> +diff --git a/Bundles/ui/guiQml/CMakeLists.txt 
>> b/Bundles/ui/guiQml/CMakeLists.txt
>> +index 42c008e..7f9c228 100644
>> +--- a/Bundles/ui/guiQml/CMakeLists.txt
>>  b/Bundles/ui/guiQml/CMakeLists.txt
>> +@@ -1,6 +1,6 @@
>> + fwLoadProperties()
>> + 
>> +-find_package(Boost QUIET COMPONENTS Regex REQUIRED)
>> ++find_package(Boost QUIET COMPONENTS regex REQUIRED)
>> + find_package(Qt5 QUIET COMPONENTS Core Gui Quick Qml QuickControls2 
>> REQUIRED)
>> + 
>> + 
>> +diff --git a/Bundles/ui/guiQt/CMakeLists.txt 
>> b/Bundles/ui/guiQt/CMakeLists.txt
>> +index 3aff5d1..ff52b89 100644
>> +--- a/Bundles/ui/guiQt/CMakeLists.txt
>>  b/Bundles/ui/guiQt/CMakeLists.txt
>> +@@ -1,6 +1,6 @@
>> + fwLoadProperties()
>> + 
>> +-find_package(Boost QUIET COMPONENTS Regex REQUIRED)
>> ++find_package(Boost QUIET COMPONENTS regex REQUIRED)
>> + find_package(Qt5 QUIET COMPONENTS Core Gui Widgets REQUIRED)
>> + 
>> + 
>> diff -Nru sight-19.0.0/debian/patches/series 
>> sight-19.0.0/debian/patches/series
>> --- sight-19.0.0/debian/patches/series   2020-04-25 15:47:51.0 
>> +0300
>> +++ sight-19.0.0/debian/patches/series   2020-06-15 18:20:20.0 
>> +0300
>> @@ -4,3 +4,4 @@
>>  fix_launcher_library_path.patch
>>  fix_dcmtk_scp_cfg.patch
>>  revert_qVTK_widget.patch
>> +0007-Fix-FTBFS-with-Boost-1.71.patch
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
>
-- 
*Flavien BRIDAULT*
Software Development Director

flavien.brida...@ircad.fr
+33 (0)3 88 119 201

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 




signature.asc
Description: OpenPGP digital signature

Bug#962937: python-oauthlib: FTBFS with newer python-mock

[Ondřej Nový]

Source: python-oauthlib
Version: 3.1.0-1
Severity: serious
Tags: ftbfs

python-oauthlib 3.1.0-1 FTBFS and autopkgtest fails with newer python-mock 
4.0.2-1.

Thanks for fixing.

__ AuthorizationCodeGrantTest.test_invalid_request_duplicates __

self = 


def test_invalid_request_duplicates(self):
request = mock.MagicMock(wraps=self.request)
request.grant_type = 'authorization_code'
request.duplicate_params = ['client_id']
>   self.assertRaises(errors.InvalidRequestError, 
> self.auth.validate_token_request,
  request)

tests/oauth2/rfc6749/grant_types/test_authorization_code.py:159: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/grant_types/authorization_code.py:453:
 in validate_token_request
raise errors.InvalidRequestError(description='Duplicate %s parameter.' % 
param,
/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/errors.py:49: in __init__
if request:
/usr/lib/python3/dist-packages/mock/mock.py:2160: in __get__
return self.create_mock()
/usr/lib/python3/dist-packages/mock/mock.py:2156: in create_mock
_set_return_value(parent, m, entry)
/usr/lib/python3/dist-packages/mock/mock.py:2053: in _set_return_value
method._mock_wraps = getattr(mock._mock_wraps, name)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def __getattr__(self, name):
if name in self._params:
return self._params[name]
else:
>   raise AttributeError(name)
E   AttributeError: __bool__

/usr/lib/python3/dist-packages/oauthlib/common.py:436: AttributeError

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

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

Bug#962936: sane-backends: please still keep libsane transitional package around

[Gianfranco Costamagna]

Hello,

after thinking a little bit more, a Provides might even be enough to satisfy 
the dependency.

To reproduce this issue:
pbuilder-dist sid login
apt-get install sane-utils
add experimental repo:

apt-get dist-upgrade -t experimental
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  acl cpp-9 fontconfig-config fonts-dejavu-core g++-9 gcc-9 libavahi-client3 
libavahi-common-data libavahi-common3 libbsd0 libdbus-1-3 libexif12 libexpat1 
libfontconfig1 libfreetype6 libgcc-9-dev libgd3
  libgphoto2-6 libgphoto2-port12 libicu67 libieee1284-3 libjbig0 
libjpeg62-turbo libkmod2 libpci3 libpng16-16 libsane-common libsensors-config 
libsensors5 libsnmp-base libsnmp35 libssl1.1
  libstdc++-9-dev libtiff5 libusb-1.0-0 libwebp6 libwrap0 libx11-6 libx11-data 
libxau6 libxcb1 libxdmcp6 libxml2 libxpm4 pci.ids sensible-utils ucf udev 
update-inetd
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libsane sane-utils
The following NEW packages will be installed:
  cpp-10 g++-10 gcc-10 libasan6 libgcc-10-dev libstdc++-10-dev
The following packages will be upgraded:
  binutils binutils-common binutils-x86-64-linux-gnu cpp dpkg dpkg-dev 
e2fsprogs g++ gcc libaudit-common libaudit1 libbinutils libc-bin libc-dev-bin 
libc6 libc6-dev libcom-err2 libctf-nobfd0 libctf0
  libdbus-1-3 libdpkg-perl libext2fs2 libjpeg62-turbo libsane-common 
libselinux1 libsepol1 libss2 linux-libc-dev logsave
29 upgraded, 6 newly installed, 2 to remove and 0 not upgraded.
Need to get 57.3 MB/57.3 MB of archives.
After this operation, 140 MB of additional disk space will be used.
Do you want to continue? [Y/n] 


Looks like it is trying to remove libsane and sane-utils instead of upgrading 
the latter

G.

Bug#961865: marked as done (picard-tools needs a source-only upload.)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jun 2020 07:33:39 +
with message-id 
and subject line Bug#961865: fixed in picard-tools 2.22.8+dfsg-1
has caused the Debian Bug report #961865,
regarding picard-tools needs a source-only upload.
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.)


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

Package: picard-tools
Version: 2.18.25+dfsg-3
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only upload so your package can migrate.
--- End Message ---
--- Begin Message ---
Source: picard-tools
Source-Version: 2.22.8+dfsg-1
Done: Olivier Sallou 

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

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

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

Debian distribution maintenance software
pp.
Olivier Sallou  (supplier of updated picard-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 29 May 2020 08:25:43 +
Source: picard-tools
Architecture: source
Version: 2.22.8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Closes: 961865
Changes:
 picard-tools (2.22.8+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Source only upload
 Closes: #961865
Checksums-Sha1:
 9223ced47ccc3138089588f95e6218fb026ae605 2715 picard-tools_2.22.8+dfsg-1.dsc
 d816bc84e03d6a84421313badcc5b2355293ae97 19302684 
picard-tools_2.22.8+dfsg.orig.tar.xz
 20473adec0dea33e26d2047930fa996acd3b0bf4 18368 
picard-tools_2.22.8+dfsg-1.debian.tar.xz
 45efe6a45b9bb8ee9bf379c71235c60be1f7ff63 17095 
picard-tools_2.22.8+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 a3b5a98202d7a795d772bf31bbf9d200279b71c66f9f4d5cadc91e9f8f5cfb66 2715 
picard-tools_2.22.8+dfsg-1.dsc
 cf83cb4699c9e6bab27d6957fedb6bd4d7c9d87efd37b86bcff0077475131dee 19302684 
picard-tools_2.22.8+dfsg.orig.tar.xz
 b94a4e8114d1200a221471c1a9b216702d323f3507a6f3cc20c0b698b1a52246 18368 
picard-tools_2.22.8+dfsg-1.debian.tar.xz
 4e82fed1d639b2d72f5e8d6f0b86e8fdcb0848e646ae3d393340655ae5a30486 17095 
picard-tools_2.22.8+dfsg-1_amd64.buildinfo
Files:
 942504ea598aadbc9d026c12d2da8b41 2715 science optional 
picard-tools_2.22.8+dfsg-1.dsc
 8df94d5a7d5e0fe2b4b880d474f29ad2 19302684 science optional 
picard-tools_2.22.8+dfsg.orig.tar.xz
 05ec94319ccce8aa1c4401cbf79dab90 18368 science optional 
picard-tools_2.22.8+dfsg-1.debian.tar.xz
 adf93c040a71a097c9dc6e0b9a3cf5d7 17095 science optional 
picard-tools_2.22.8+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEX7Rvg9O5UgRjNdJteNxo2zJthDgFAl7ocasTHG9zYWxsb3VA
ZGViaWFuLm9yZwAKCRB43GjbMm2EOAixD/93RZhYtSpug5nIVSuTCvrLp9HfZmAj
PkZN4nSzAKBwuQ1VLoWGmkCN/rrn26/ItOvR//4eA2jSOO/+HMA8z2HcGTTdKgDy
VWDpD+WcJalQPb7jWtL6ct5NQ8ltdsmiVchJ6FsAcPCD8TPBELHd9E0d4deeBq3M
a0NisOmDcRTBvvDOJ+tkU69Rvnw7rJVZhKdbO+dzMNn3S7xTa64f24YL0XFq/vUe
ZSLzGfjmvd2InJvEDSUE/yf4+2Cxu9tIW0IwtuYy35Ho3ArBESpciesUmGreaZf9
wS4UD0GAWu6jSpKHR/yLPxjEzBFMJpfEFXB50/ih30nmOHLH4Y5vDxu4XupzuvuN
H28aEcfZHFqG24kRPUDaRCQUfMZScsgS++cakidU0/09m2BLPrjPUtMbIJ676E24
0VpRkZySor4TgpDuy1JwWwJlImpUvu/i1F1z8VPQpSeCRCwyQ0vNJ1HVx8VBp5yl
JfbKbXnKxuKR9POQPNGSpjni4/CDlKp79TZINXFfxjDNWwPXKwscqntnUz/xy6Fh
7W25Tz5OW9nPH68clS7rtSbbGhVOEgZF0/WgTn1bjA4AccBCUMSIWwZnxEZugm5V
B4cRyJH3oDDkVnEvbT242q6wrNV3WFX9WSg235Fs9oakKle7fxS3NoA7yAaFTLa1
EWCX1xEgTK2Sbw==
=UB9R
-END PGP SIGNATURE End Message ---

Processed: bug 959544 is forwarded to https://github.com/maxmind/MaxMind-DB-Reader-python/commit/3aac426e354f91814f6fd0829baee137b0bb093f

[Debian Bug Tracking System]

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

> forwarded 959544 
> https://github.com/maxmind/MaxMind-DB-Reader-python/commit/3aac426e354f91814f6fd0829baee137b0bb093f
Bug #959544 [src:python-maxminddb] python-maxminddb: FTBFS: ImportError: cannot 
import name 'Feature' from 'setuptools' 
(/usr/lib/python3/dist-packages/setuptools/__init__.py)
Set Bug forwarded-to-address to 
'https://github.com/maxmind/MaxMind-DB-Reader-python/commit/3aac426e354f91814f6fd0829baee137b0bb093f'.
> thanks
Stopping processing here.

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

Bug#962936: sane-backends: please still keep libsane transitional package around

[Gianfranco Costamagna]

Source: sane-backends
Version: 1.0.30-1~experimental2
Severity: serious

Hello, I tried to upgrade from the old sane-backends to the new one, and 
libsane in some condition
was not removed, and sane-utils were removed as result.

I don't know how and why, but adding back libsane as transitional package 
helped in doing the upgrade in a smooth
way.

The trivial patch uploaded in Ubuntu is here:

diff -Nru sane-backends-1.0.30/debian/changelog 
sane-backends-1.0.30/debian/changelog
--- sane-backends-1.0.30/debian/changelog   2020-05-31 07:23:01.0 
+
+++ sane-backends-1.0.30/debian/changelog   2020-06-14 11:36:40.0 
+
@@ -1,3 +1,11 @@
+sane-backends (1.0.30-1~experimental2ubuntu1) groovy; urgency=medium
+
+  * Sync from debian experimental, Remaining changes:
+- add back libsane transitional package, to ease upgrades.
+  (this can be dropped after 22.04)
+
+ -- Gianfranco Costamagna   Sun, 14 Jun 2020 
13:36:40 +0200
+
 sane-backends (1.0.30-1~experimental2) experimental; urgency=medium
 
   * debian/not-installed:
diff -Nru sane-backends-1.0.30/debian/control 
sane-backends-1.0.30/debian/control
--- sane-backends-1.0.30/debian/control 2020-05-26 10:15:40.0 +
+++ sane-backends-1.0.30/debian/control 2020-06-14 11:36:38.0 +
@@ -131,3 +131,24 @@
  .
  This package contains the files needed to build your applications
  using SANE.
+
+Package: libsane
+Architecture: any
+Multi-Arch: same
+Section: oldlibs
+Depends:
+ libsane1 (>= ${source:Version}),
+ ${misc:Depends}
+Description: API library for scanners [transitional package]
+ SANE stands for "Scanner Access Now Easy" and is an application
+ programming interface (API) that provides standardized access to any
+ raster image scanner hardware (flatbed scanner, hand-held scanner,
+ video- and still-cameras, frame-grabbers, etc.). The SANE standard is
+ free and its discussion and development are open to everybody. The
+ current source code is written to support several operating systems,
+ including GNU/Linux, OS/2, Win32 and various Unices and is available
+ under the GNU General Public License (commercial applications and
+ backends are welcome, too, however).
+ .
+ This package is here to ensure smooth upgrades. It can be removed when
+ you see fit.

thanks for considering it!

Gianfranco

Bug#962692: puppet: Crashes due to "missing" facts.d directories

[Wilmer van der Gaast]

>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962320 I guess
swapping libboost library versions may be a more proper fix. Though I
haven't tried this myself yet.

Bug#962935: budgie-extras: autopkgtest fails with newer pycodestyle

[Ondřej Nový]

Source: budgie-extras
Version: 1.0.2-1
Severity: serious

budgie-extras autopkgtest fails when run with newest pycodestyle 2.6.0:

./budgie-wswitcher/wswitcher_run:51:34: E741 ambiguous variable name 'l'

Thanks for fixing.

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

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

Bug#959507: dub: diff for NMU version 1.19.0-1.1

[Adrian Bunk]

Control: tags 959507 + patch
Control: tags 959507 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru dub-1.19.0/debian/changelog dub-1.19.0/debian/changelog
--- dub-1.19.0/debian/changelog	2020-01-12 02:04:18.0 +0200
+++ dub-1.19.0/debian/changelog	2020-06-16 09:55:55.0 +0300
@@ -1,3 +1,11 @@
+dub (1.19.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add a needs-internet restriction to the autopkgtest.
+(Closes: #959507)
+
+ -- Adrian Bunk   Tue, 16 Jun 2020 09:55:55 +0300
+
 dub (1.19.0-1) unstable; urgency=medium
 
   [ Matthias Klumpp ]
diff -Nru dub-1.19.0/debian/tests/control dub-1.19.0/debian/tests/control
--- dub-1.19.0/debian/tests/control	2019-08-31 21:47:11.0 +0300
+++ dub-1.19.0/debian/tests/control	2020-06-16 09:55:52.0 +0300
@@ -1,2 +1,3 @@
 Tests: run
 Depends: dub
+Restrictions: needs-internet

Processed: dub: diff for NMU version 1.19.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 959507 + patch
Bug #959507 [src:dub] dub: flaky autopkgtest: Package dub not found for 
registry at https://code.dlang.org/
Added tag(s) patch.
> tags 959507 + pending
Bug #959507 [src:dub] dub: flaky autopkgtest: Package dub not found for 
registry at https://code.dlang.org/
Added tag(s) pending.

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