Bug#944272: marked as done (openjdk-13 FTCBFS: multiple minor reasons)

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 08:27:00 +0200
with message-id <5ea0e6c1-359d-c21e-a978-5f3b1eec5...@debian.org>
and subject line fixed in 13.0.2+8-2
has caused the Debian Bug report #944272,
regarding openjdk-13 FTCBFS: multiple minor reasons
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.)


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

openjdk-13 fails to cross build from source. The package looks well
prepared for cross building, but it seems to have two bugs. The
immediate failure is a linker error failing to find -lz from the native
linker. When cross building, openjdk has a native pass and that one also
needs zlib1g-dev, so it should depend on zlib1g-dev:native. The next
failure comes after the build, when debian/rules invokes the build
architecture objcopy and strip. These tools should be prefixed with the
host architecture triplet. And that's all to make it cross build. Good
work. Please consider applying the attached patch.

Helmut
diff --minimal -Nru openjdk-13-13.0.1+9/debian/changelog 
openjdk-13-13.0.1+9/debian/changelog
--- openjdk-13-13.0.1+9/debian/changelog2019-10-19 19:32:03.0 
+0200
+++ openjdk-13-13.0.1+9/debian/changelog2019-11-06 23:45:11.0 
+0100
@@ -1,3 +1,12 @@
+openjdk-13 (13.0.1+9-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Missing Build-Depends: zlib1g-dev:native.
++ Use triplet-prefixed objcopy and strip.
+
+ -- Helmut Grohne   Wed, 06 Nov 2019 23:45:11 +0100
+
 openjdk-13 (13.0.1+9-2) unstable; urgency=medium
 
   * Fix the jtreg consistency check when building without jtreg.
diff --minimal -Nru openjdk-13-13.0.1+9/debian/control 
openjdk-13-13.0.1+9/debian/control
--- openjdk-13-13.0.1+9/debian/control  2019-10-18 14:45:39.0 +0200
+++ openjdk-13-13.0.1+9/debian/control  2019-11-06 23:43:17.0 +0100
@@ -12,7 +12,7 @@
   openjdk-13-jdk-headless:native | openjdk-12-jdk-headless:native,
   libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, 
libcups2-dev, libasound2-dev, liblcms2-dev, libfreetype6-dev (>= 2.2.1), 
libxinerama-dev, libkrb5-dev, xsltproc, libpcsclite-dev, libxrandr-dev, 
libelf-dev, libfontconfig1-dev, libgtk2.0-0 | libgtk-3-0,
   libffi-dev,
-  zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, 
+  zlib1g-dev, zlib1g-dev:native, libattr1-dev, libpng-dev, libjpeg-dev, 
libgif-dev, 
   libnss3-dev (>= 2:3.17.1),
   openjdk-13-jdk-headless ,
 Build-Depends-Indep: graphviz, pandoc,
diff --minimal -Nru openjdk-13-13.0.1+9/debian/rules 
openjdk-13-13.0.1+9/debian/rules
--- openjdk-13-13.0.1+9/debian/rules2019-10-18 14:45:36.0 +0200
+++ openjdk-13-13.0.1+9/debian/rules2019-11-06 23:45:10.0 +0100
@@ -607,7 +607,7 @@
 else
   bd_gcc = g++-9 ,
 endif
-bd_syslibs = zlib1g-dev, libattr1-dev,
+bd_syslibs = zlib1g-dev, zlib1g-dev:native, libattr1-dev,
 ifneq (,$(filter $(distrel),squeeze lucid))
   bd_syslibs += libpng12-dev, libjpeg62-dev,
 else ifneq (,$(filter $(distrel),wheezy precise quantal raring saucy))
@@ -1774,18 +1774,18 @@
id=$$(echo $$i | sed -r 's,debian/[^/]+,$(d_dbg)/usr/lib/debug,'); \
echo strip $$i; \
mkdir -p $$(dirname $$id); \
-   objcopy --only-keep-debug $$i $$id; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --only-keep-debug $$i $$id; \
chmod 644 $$id; \
-   strip --remove-section=.comment --remove-section=.note \
+   $(DEB_HOST_GNU_TYPE)-strip --remove-section=.comment 
--remove-section=.note \
  --strip-debug $$i; \
-   objcopy --add-gnu-debuglink $$id $$i; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --add-gnu-debuglink $$id $$i; \
  else \
d=usr/lib/debug/.build-id/$${b_id:0:2}; \
f=$${b_id:2}.debug; \
mkdir -p $(d_dbg)/$$d; \
-   objcopy --only-keep-debug --compress-debug-sections $$i 
$(d_dbg)/$$d/$$f; \
+   $(DEB_HOST_GNU_TYPE)-objcopy --only-keep-debug 
--compress-debug-sections $$i $(d_dbg)/$$d/$$f; \
chmod 644 $(d_dbg)/$$d/$$f; \
-   strip --remove-section=.comment --remove-section=.note $$i; \
+   $(DEB_HOST_GNU_TYPE)-strip --remove-section=.comment 
--remove-section=.note $$i; \
  fi; \
done
 endif
--- End Message ---
--- Begin Message ---
Version: 13.0.2+8-2

Fixed.--- End Message ---

Bug#866052: marked as done (fonts-orya-extra: upgrade does not clean up obsoleted directories)

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 05:48:27 +
with message-id 
and subject line Bug#866052: fixed in fonts-orya-extra 2.0-6
has caused the Debian Bug report #866052,
regarding fonts-orya-extra: upgrade does not clean up obsoleted directories
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.)


-- 
866052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-orya-extra
Version: 2.0-5
Severity: normal


This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.

Today's Sid upgrade brought in a change from having a directory to
having a file of the same name.  However this is not handled by the
package.

-/etc/fonts/conf.avail/65-0-fonts-orya-extra.conf/65-0-fonts-orya-extra.conf
+/etc/fonts/conf.avail/65-0-fonts-orya-extra.conf

This results in the following:

drwxr-xr-x 2 root root 4096 Aug 24  2015 65-0-fonts-beng-extra.conf/
-rw-r--r-- 1 root root 1064 Aug 22  2012 65-0-fonts-beng-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Nov 13  2014 65-0-fonts-deva-extra.conf/
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Jul 31  2016 65-0-fonts-gujr-extra.conf/
-rw-r--r-- 1 root root  687 Jan  7  2012 65-0-fonts-gujr-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Jun 16  2013 65-0-fonts-guru-extra.conf/
-rw-r--r-- 1 root root  689 Feb 25  2012 65-0-fonts-guru-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Sep 12  2016 65-0-fonts-orya-extra.conf/
-rw-r--r-- 1 root root  678 Feb 25  2012 65-0-fonts-orya-extra.conf.dpkg-new

Obviously the goal was to have this instead:

-rw-r--r-- 1 root root 1064 Aug 22  2012 65-0-fonts-beng-extra.conf
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf
-rw-r--r-- 1 root root  687 Jan  7  2012 65-0-fonts-gujr-extra.conf
-rw-r--r-- 1 root root  689 Feb 25  2012 65-0-fonts-guru-extra.conf
-rw-r--r-- 1 root root  678 Feb 25  2012 65-0-fonts-orya-extra.conf

Thank you for maintaining these packages in Debian.

Bob

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fonts-orya-extra
Source-Version: 2.0-6
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated fonts-orya-extra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Apr 2020 07:55:23 +0530
Source: fonts-orya-extra
Architecture: source
Version: 2.0-6
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 854166 866052
Changes:
 fonts-orya-extra (2.0-6) unstable; urgency=low
 .
   * Team upload.
   * debian/preinst:
 + Handle migration of conffile from wrong subdir. Patch from Ubuntu.
   (Closes: #854166, #866052)
   * Added debian/gitlab-ci.yml.
   * Updated debian/copyright.
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Switched to debhelper-compat.
 + Set Maintainer to Debian Fonts Task Force.
 + Updated Vcs-* URLs.
 + Updated package description: Oriya->Odia.
 + Added 'Rules-Requires-Root' field.
Checksums-Sha1:
 d68d32ba5a78308bdbd9752851f39bc8e46bc158 1929 fonts-orya-extra_2.0-6.dsc
 1eb661ab12266f285e70750a671fd93ea20c37c9 2700 
fonts-orya-extra_2.0-6.debian.tar.xz
Checksums-Sha256:
 c8f5da2e79e241a14a52048dc08432366ed63da8609ed34d4723f44fc1c4e2e9 1929 
fonts-orya-extra_2.0-6.dsc
 8b66e396df4ec48952129d7d623e2f5eda8bd5e485052b4ab862feb204621a37 2700 
fonts-orya-extra_2.0-6.debian.tar.xz
Files:
 59b

Bug#854166: marked as done (fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/)

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 05:48:27 +
with message-id 
and subject line Bug#854166: fixed in fonts-orya-extra 2.0-6
has caused the Debian Bug report #854166,
regarding fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/
to be marked as done.

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

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


-- 
854166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-deva-extra
Version: 3.0-3
Severity: normal


Dear Maintainer,

this package (and several other ones maintained by you) creates directories in 
/etc/fonts/conf.avail/ and those directories contain only one file with the 
same name as the directory:

$ ls -l /etc/fonts/conf.avail/65-0-fonts--extra.conf
-rw-r--r-- 1 root root  684 Feb 25  2012 
/etc/fonts/conf.avail/65-0-fonts-telu-extra.conf

/etc/fonts/conf.avail/65-0-fonts-beng-extra.conf:
total 4
-rw-r--r-- 1 root root 1064 Aug 23  2015 65-0-fonts-beng-extra.conf

/etc/fonts/conf.avail/65-0-fonts-deva-extra.conf:
total 8
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf

/etc/fonts/conf.avail/65-0-fonts-gujr-extra.conf:
total 4
-rw-r--r-- 1 root root 687 Jan  7  2012 65-0-fonts-gujr-extra.conf

/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf:
total 4
-rw-r--r-- 1 root root 689 Feb 25  2012 65-0-fonts-guru-extra.conf

/etc/fonts/conf.avail/65-0-fonts-orya-extra.conf:
total 4
-rw-r--r-- 1 root root 678 Feb 25  2012 65-0-fonts-orya-extra.conf


This is most probably an error and it would be simpler and more coherent with 
other font packages to remove those extra directories.


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

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

Versions of packages fonts-deva-extra depends on:
ii  dpkg 1.18.21
ii  fonts-gargi  2.0-4
ii  fonts-sarai  1.0-2

fonts-deva-extra recommends no packages.

fonts-deva-extra suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: fonts-orya-extra
Source-Version: 2.0-6
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated fonts-orya-extra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Apr 2020 07:55:23 +0530
Source: fonts-orya-extra
Architecture: source
Version: 2.0-6
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 854166 866052
Changes:
 fonts-orya-extra (2.0-6) unstable; urgency=low
 .
   * Team upload.
   * debian/preinst:
 + Handle migration of conffile from wrong subdir. Patch from Ubuntu.
   (Closes: #854166, #866052)
   * Added debian/gitlab-ci.yml.
   * Updated debian/copyright.
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Switched to debhelper-compat.
 + Set Maintainer to Debian Fonts Task Force.
 + Updated Vcs-* URLs.
 + Updated package description: Oriya->Odia.
 + Added 'Rules-Requires-Root' field.
Checksums-Sha1:
 d68d32ba5a78308bdbd9752851f39bc8e46bc158 1929 fonts-orya-extra_2.0-6.dsc
 1eb661ab12266f285e70750a671fd93ea20c37c9 2700 
fonts-orya-extra_2.0-6.debian.tar.xz
Checksums-Sha256:
 c8f5da2e79e241a14a52048dc08432366ed63da8609ed34d4723f44fc1c4e2e9 1929 
fonts-orya-extra_2.0-6.dsc
 8b66e396df4ec48952129d7d623e2f5eda8bd5e485052b4ab862feb204621a37 2700 
fonts-orya-extra_2.0-6.debian.tar.xz
Files:
 59b00bc157e567018522ec9c85dca5a9 1929 fonts optional fonts-orya-extra_2.0-6.dsc
 b4668e7f2c3dd3d87f61b5a0a281fadf 2700 fonts optional 
fonts-orya-extra_2.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl6Wkd8ACg

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

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 05:18:36 +
with message-id 
and subject line Bug#938156: fixed in python-scandir 1.10.0-3
has caused the Debian Bug report #938156,
regarding python-scandir: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-scandir

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-scandir
Source-Version: 1.10.0-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-scandir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Apr 2020 00:59:53 -0400
Source: python-scandir
Architecture: source
Version: 1.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938156
Changes:
 python-scandir (1.10.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938156
Checksums-Sha1:
 054d12cb393e8f1aad1c7ac3404fa1459320d61d 2066 python-scandir_1.10.0-3.dsc
 4254026a85e9598f9951bf4df72dc590a341696a 2644 
python-scandir_1.10.0-3.debian.tar.xz
 18ce62c7a26f05253f61e56a3c62271d5f189fca 6375 
python-scandir_1.10.0-3_source.buildinfo
Checksums-Sha256:
 1b12070ec3aea315b015458bd3e752e7d89e61435073a71903c83eda319a85cd 2066 
python-scandir_1.10.0-3.dsc
 9940b34e1e8a34630192b8b701a37155e6443700860cc9d63113df1def2ac304 2644 
python-scandir_1.10.0-3.debian.tar.xz
 33918962c25165fd6eafa

Bug#956394: marked as done (u-boot-sunxi: please add support for A64-OLinuXino with eMMC)

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 02:34:49 +
with message-id 
and subject line Bug#956394: fixed in u-boot 2020.04+dfsg-1
has caused the Debian Bug report #956394,
regarding u-boot-sunxi: please add support for A64-OLinuXino with eMMC
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.)


-- 
956394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: u-boot
Version: 2020.01+dfsg-2
Severity: wishlist

Hi,

could you please enable support for the A64-OLinuXino variant with eMMC?

The relevant config is

configs/a64-olinuxino-emmc_defconfig

Thanks,
Philip



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

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: u-boot
Source-Version: 2020.04+dfsg-1
Done: Vagrant Cascadian 

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

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

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot 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, 14 Apr 2020 17:24:39 -0700
Source: u-boot
Architecture: source
Version: 2020.04+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 956394
Changes:
 u-boot (2020.04+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   [ Vagrant Cascadian ]
   * Update upstream signing key.
   * [arm64] Build arm-trusted-firmware into rockchip/sunxi systems.
   * [arm64] u-boot-sunxi: Add a64-olinuxino-emmc target Thanks to Philip
 Rinn. (Closes: #956394).
 .
   [ Walter Lozano ]
   * debian/targets: Add support for rock-pi-4-rk3399
   * debian/targets: Add target idbloader.img for rk3399 boards
 .
   [ Vagrant Cascadian ]
   * debian/control: Add versioned Build-Depends on arm-trusted-firmware
 for rk3399 support.
   * debian/targets: Add idbloader.img for all rockchip platforms.
   * u-boot-rockchip: Update README.Debian.
   * Remove debian/bin/generate-rksd.
   * u-boot-rockchip: firefly-rk3288: Also install u-boot.img.
   * [arm64] u-boot-rockchip, u-boot-sunxi: Add Built-Using
 arm-trusted-firmware.
Checksums-Sha1:
 92748b97f33a5c9313e15fd21617fc3cfb65bcca 2873 u-boot_2020.04+dfsg-1.dsc
 0802efae564aca183b90251e86efce7d0295f22e 12689768 
u-boot_2020.04+dfsg.orig.tar.xz
 5ae4ed5116f1b4fbb3c097f28843726949520998 42888 
u-boot_2020.04+dfsg-1.debian.tar.xz
 cc1948f7da0f0a8015c879d3d2a7055ceeb18e4d 7885 
u-boot_2020.04+dfsg-1_arm64.buildinfo
Checksums-Sha256:
 3ed9c6bfeb04e63d099e9667e3cd3cdd25ec20dd0344e212e7b481e4f3ff92d9 2873 
u-boot_2020.04+dfsg-1.dsc
 eca1c862264baed2a6447d4f6c4783b5857b0b10550a24381e4ff64f99533fea 12689768 
u-boot_2020.04+dfsg.orig.tar.xz
 14565cd1703eeb4df7557b8be8ea664eea3b6a1bd2cabdd35b71c5b9f16a3772 42888 
u-boot_2020.04+dfsg-1.debian.tar.xz
 598a6d0d8c43dcc5fdfed22624db48d986f83fa2b75a52cd2b2a9e332fac3682 7885 
u-boot_2020.04+dfsg-1_arm64.buildinfo
Files:
 d2a4c75411443674974ce19d052fcf6c 2873 admin optional u-boot_2020.04+dfsg-1.dsc
 f1121d103d35c05ff0db1673f15b3ee4 12689768 admin optional 
u-boot_2020.04+dfsg.orig.tar.xz
 50865068f390a7c4c180d70849eb7de9 42888 admin optional 
u-boot_2020.04+dfsg-1.debian.tar.xz
 e7cf3af5cff987f2ff2c66cff9720979 7885 admin optional 
u-boot_2020.04+dfsg-1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXpZvHxMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqEA0BAJMgc/GE2jeEnEY5vKgNgfJMIiIpuO6h
+L7Lx1/K7vdXAQDcr9onCRee0Wq+ktQa2LgsejIFgIvUKxRta8K0JfPUCg==
=GQNJ
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

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

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

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

Processed: RFS: feedreader/2.10.0-1.1 [NMU, RC] -- simple client for online RSS services like tt-rss and others

[Debian Bug Tracking System]

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

> close 956702
Bug #956702 [sponsorship-requests] RFS: feedreader/2.10.0-1.1 [NMU, RC] -- 
simple client for online RSS services like tt-rss and others
Marked Bug as done
> stop
Stopping processing here.

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

Bug#953017: marked as done (linux-image-amd64: Regression from "mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()")

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 01:32:18 +0100
with message-id 
and subject line Re: Bug#953017: Fixes in Upstream
has caused the Debian Bug report #953017,
regarding linux-image-amd64: Regression from "mm/vmalloc: Sync unmappings in 
__purge_vmap_area_lazy()"
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.)


-- 
953017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.4.13-1~bpo10+1
Severity: important
Tags: upstream patch

Dear Maintainer,

A performance regression stemming from the patch "mm/vmalloc: Sync
unmappings in __purge_vmap_area_lazy()" in all mainline and current
stable kernels, except 3.16.y, was reported by multiple persons [1].
The regression involves any activity that exercises vmalloc a lot,
such as creating threads with CONFIG_VMAP_STACK=y or tty allocation
(for example by SSH servers).

A fix [2] for this was posted last October and was picked up in the
-mm tree last November [3]. However this fix did not make it into
v5.6-rc or any other release. It is still only in the -mm tree.

AFAICT this regression only impacts x86 platforms, as it is the only
platform that has a custom vmalloc_sync_all() instead of the standard
no-op stub.

As per my report to upstream, I currently have one production server
running with the offending patch reverted. I also have another with
the fix applied, and that seems to work well.

Please consider adding the fix to Debian kernel images until upstream
kernels have it.

[1] https://www.spinics.net/lists/stable/msg349763.html
[2] https://patchwork.kernel.org/patch/11181159/
[3] https://www.spinics.net/lists/mm-commits/msg141749.html

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

Kernel: Linux 5.2.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.4.0-0.bpo.3-amd64  5.4.13-1~bpo10+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.5.13-1

On Thu, 2020-04-09 at 13:40 +0800, Chen-Yu Tsai wrote:
> The fix for this issue has been merged in v5.6-rc7 and is part of the
> v5.6 release. The commit in upstream is:
> 
> 763802b53a42 x86/mm: split vmalloc_sync_all()
> 
> This has also been backported to all current LTS kernels except 3.16
> in the following releases:
> 
> v4.4.218
> v4.9.218
> v4.14.175
> v4.19.113
> v5.4.28

...and 5.5.12, so this is fixed in unstable.

Ben.

-- 
Ben Hutchings
It is a miracle that curiosity survives formal education.
  - Albert Einstein




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

Bug#951986: marked as done (feedreader: FTBFS: ../src/Backend/FeedServer.vala:60.98-60.148: error: The name `COLLECTION_CREATE_NONE' does not exist in the context of `Secret.CollectionCreateFlags' (li

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 00:18:35 +
with message-id 
and subject line Bug#951986: fixed in feedreader 2.10.0-1.1
has caused the Debian Bug report #951986,
regarding feedreader: FTBFS: ../src/Backend/FeedServer.vala:60.98-60.148: 
error: The name `COLLECTION_CREATE_NONE' does not exist in the context of 
`Secret.CollectionCreateFlags' (libsecret-1)
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> meson builddir
> The Meson build system
> Version: 0.53.1
> Source dir: /<>
> Build dir: /<>/builddir
> Build type: native build
> Project name: feedreader
> Project version: 2.10.0
> Appending CFLAGS from environment: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now']
> Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
> Appending CFLAGS from environment: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now']
> Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
> C compiler for the host machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-29) 9.2.1 
> 20200220")
> C linker for the host machine: cc GNU ld.bfd 2.34
> Vala compiler for the host machine: valac (valac 0.47.91)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Program afl-fuzz found: NO
> Program gtester found: YES (/usr/bin/gtester)
> Found pkg-config: /usr/bin/pkg-config (0.29)
> Run-time dependency gdk-pixbuf-2.0 found: YES 2.40.0
> Run-time dependency gee-0.8 found: YES 0.20.3
> Run-time dependency glib-2.0 found: YES 2.62.4
> Run-time dependency goa-1.0 found: YES 3.34.1
> Run-time dependency gstreamer-1.0 found: YES 1.16.2
> Run-time dependency gstreamer-pbutils-1.0 found: YES 1.16.2
> Run-time dependency gtk+-3.0 found: YES 3.24.13
> Run-time dependency gumbo found: YES 0.10.1
> Run-time dependency json-glib-1.0 found: YES 1.4.4
> Library curl found: YES
> Run-time dependency libnotify found: YES 0.7.8
> Run-time dependency libpeas-1.0 found: YES 1.22.0
> Run-time dependency libsecret-1 found: YES 0.19.1
> Run-time dependency libsoup-2.4 found: YES 2.68.2
> Run-time dependency libxml-2.0 found: YES 2.9.10
> Library linux found: YES
> Library posix found: YES
> Run-time dependency rest-0.7 found: YES 0.8.1
> Run-time dependency sqlite3 found: YES 3.31.1
> Run-time dependency webkit2gtk-4.0 found: YES 2.26.4
> Run-time dependency webkit2gtk-web-extension-4.0 found: YES 2.26.4
> Found CMake: /usr/bin/cmake (3.16.3)
> Appending CXXFLAGS from environment: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now']
> Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
> Run-time dependency unity found: NO (tried pkgconfig and cmake)
> Configuring @basename@ using configuration
> Library webkit2gtk-web-extension-4.0 found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29)
> Program desktop-file-validate found: NO
> Program appstream-util found: NO
> Library gd-1.0 found: YES
> Library gtkimageview found: YES
> Library htmlclean found: YES
> Library rss-glib-1.0 found: YES
> Library m found: YES
> Message: libUnity support OFF
> Message: Backend Plugin: bazqux ON
> Message: Backend Plugin: decsync ON
> Message: Backend Plugin: feedbin ON
> Message: Backend Plugin: feedhq ON
> Message: Backend Plugin: feedly ON
> Message: Backend Plugin: fresh ON
> Message: Backend Plugin: inoreader ON
> Message: Backend Plugin: local ON
> Message: Backend Plugin: oldreader ON
> Message: Backend Plugin: owncloud ON
> Message: Backend Plugin: ttrss ON
> Message: Share Plugin: Browser ON
> Message: Share Plugin: Email ON
> Message: Share Plugin: Instapaper ON
> Message: Share Plugin: Pocket ON
> Message: Share Plugin: Telegram ON
> Message: Share Plugin: Twitter ON
> Message: Share Plugin: Wallabag ON
> Program build-aux/meson_post_install.py found: YES 
> (/<>/build-aux/meson_post_install.py)
> Build targets in project: 81
> 
> Found ninja-1.10.0 at /u

Bug#925192: marked as done (libappindicator: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 00:03:37 +
with message-id 
and subject line Bug#925192: fixed in libappindicator 0.4.92-8
has caused the Debian Bug report #925192,
regarding libappindicator: please make the build reproducible
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.)


-- 
925192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libappindicator
Version: 0.4.92-7
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that libappindicator could not be built reproducibly as it includes
the absolute build path.

The glib-mkenums documentation recommends using @basename@ over
@filename@ for this reason [1].

Patch attached.

 [0] https://reproducible-builds.org/
 [1] https://developer.gnome.org/gobject/stable/glib-mkenums.html#id-1.5.2.5.4


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/src/app-indicator-enum-types.h.in 2019-03-20 22:12:53.867378949 -0400
--- b/src/app-indicator-enum-types.h.in 2019-03-20 22:16:18.934152095 -0400
@@ -44,7 +44,7 @@
 /*** END file-tail ***/
 
 /*** BEGIN file-production ***/
-/* Enumerations from file: "@filename@" */
+/* Enumerations from file: "@basename@" */
 /*** END file-production ***/
 
 /*** BEGIN value-header ***/
--- End Message ---
--- Begin Message ---
Source: libappindicator
Source-Version: 0.4.92-8
Done: Adam Borowski 

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated libappindicator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 01:28:23 +0200
Source: libappindicator
Architecture: source
Version: 0.4.92-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Closes: 925192 952047
Changes:
 libappindicator (0.4.92-8) unstable; urgency=medium
 .
   * QA upload.
   * Drop -Werror when building the main library.  Closes: #952047.
   * Make the build reproducible (lamby).  Closes: #925192.
Checksums-Sha1:
 14974c2051adf0b33d374e49ac2b9f25eb46f98a 2717 libappindicator_0.4.92-8.dsc
 7b9f8ab746886e3aa1f6bd0ceb0c22bdd3462d63 13756 
libappindicator_0.4.92-8.debian.tar.xz
 be3150b5bdeae3656ff8694a75d8b8d4382d98d7 9370 
libappindicator_0.4.92-8_source.buildinfo
Checksums-Sha256:
 b1419dbb2e97254d588455a19cac4fb1133841f5751eea50645ea52df9eb0c22 2717 
libappindicator_0.4.92-8.dsc
 537ddb7af4e94d9f47cceaaf6ad63a35e82e05e3481066529d977c11896a6455 13756 
libappindicator_0.4.92-8.debian.tar.xz
 f564505a495eac7fedb376a911d59eee5b3ac81b8e5f5eebefdd9e9514d03283 9370 
libappindicator_0.4.92-8_source.buildinfo
Files:
 fad2fb9c33d39d75a625933da5584ca9 2717 oldlibs optional 
libappindicator_0.4.92-8.dsc
 5472cf8709d6cbced53ecbc659f84204 13756 oldlibs optional 
libappindicator_0.4.92-8.debian.tar.xz
 e5708434a494ed9117606033004413c7 9370 oldlibs optional 
libappindicator_0.4.92-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6WRyEUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5tUg/7BtNuW5zSISMA1BWcAsC5v7ZeOKd7
Rave7eBvVPmtjHJ6kV5Nh2cvBLRUUIuzZskfIJMxOgrh6GafXmxlNbQjmr2pe6G+
mMbzCkl5vsaANHH9tqKURR2WNBUZMiiWupFxF0WCCfjK49hLCwLVy/3EFC/sfhbx
9yxWqM/kYpPoWY/Wh259NgQgs6qKem+gdaul72586OF+p5KRM7pWXaY0HxKqLRhQ
5KU+yo3Lp+LPA9kxcw9NVLbXR+6DPtIhidn7+ot6C4Q470KH1ZncchGsiu7cLJW/
jJ2XycciYue6i1HElirnJ67TaDarDLO6TsHP5aJAaY5YkE5J+gnNdwXO8HF/ah2a
4gUaK1dKSOmHZ0W397vLx9a97XhErbgshDJf6OYjVZON2OQPfLrNYun3VAcWQKRd
/JMn/eQPgx4r25pCcrwkekmAVA35OffSBKECqenX08zW5ZMidLCawLeZni7xG+92
3n/hFsPyHT/3iQRDEkm/GrN72EfJ1w58RtA8djiyjop57qz0D6rzK1uW2pvYe71s
vuIj2/8o2Ds/IHcp8KzwYba0QVYcmcn6Qp7Bprp6VEOFFwlVjuMsRFqU4a5y0BC2
XUqkmxo2/TrNsmaV9iji/efl0gb455kb7gf0hvOL3M0q1LNF+xF+dz+aF3NJkbPz
wikd7qIFGqb2E98=
=8PKa
-END P

Bug#952047: marked as done (libappindicator: FTBFS: app-indicator.c:584:13: error: G_ADD_PRIVATE [-Werror])

[Debian Bug Tracking System]

Your message dated Wed, 15 Apr 2020 00:03:37 +
with message-id 
and subject line Bug#952047: fixed in libappindicator 0.4.92-8
has caused the Debian Bug report #952047,
regarding libappindicator: FTBFS: app-indicator.c:584:13: error: G_ADD_PRIVATE 
[-Werror]
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.)


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

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I/<>/./src -I..-pthread -I/usr/include/libindicator-0.4 
> -I/usr/include/libdbusmenu-gtk-0.4 -I/usr/include/libdbusmenu-glib-0.4 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
> -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -Wall -Werror 
> -Wno-deprecated-declarations -DG_LOG_DOMAIN=\"libappindicator\" -g -O2 -c -o 
> libappindicator_la-app-indicator.lo `test -f 'app-indicator.c' || echo 
> '/<>/./src/'`app-indicator.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./src -I.. 
> -pthread -I/usr/include/libindicator-0.4 -I/usr/include/libdbusmenu-gtk-0.4 
> -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -Wall -Werror 
> -Wno-deprecated-declarations -DG_LOG_DOMAIN=\"libappindicator\" -g -O2 -c 
> /<>/./src/app-indicator.c  -fPIC -DPIC -o 
> .libs/libappindicator_la-app-indicator.o
> /<>/./src/app-indicator.c: In function ‘app_indicator_init’:
> /<>/./src/app-indicator.c:584:13: error: G_ADD_PRIVATE [-Werror]
>   584 |  AppIndicatorPrivate * priv = APP_INDICATOR_GET_PRIVATE(self);
>   | ^~~
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:726: libappindicator_la-app-indicator.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/libappindicator_0.4.92-7_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated libappindicator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 01:28:23 +0200
Source: libappindicator
Architecture: source
Version: 0.4.92-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Closes: 925192 952047
Changes:
 libappindicator (0.4.92-8) unstable; urgency=medium
 .
   * QA upload.
   * Drop -Werror when building the main library.  Closes: #952047.
   * Make the build reproducibl

Bug#956268: marked as done (Problems identified in debian/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 23:18:45 +
with message-id 
and subject line Bug#956268: fixed in ublock-origin 1.22.2+dfsg-2
has caused the Debian Bug report #956268,
regarding Problems identified in debian/copyright
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.)


-- 
956268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ublock-origin
Version: 1.25.0+dfsg-1
Severity: serious

I noticed some issues with debian/copyright in this package.

Missing from d/copyright:
- uAssets/thirdparties/hosts-file.net/*
- uAssets/fisters/annoyances.txt
- src/img/fontawesome
- src/js/codemirror
- src/lib/codemirror
- src/lib/publicsuffixlist
- src/lib/punycode.js


Note-1: I believe annoyances.txt is meant to be GPL-3+.
Please consider contacting upstream for clarification.

Note-2: Rather than specifying each file, using globs on
"thirdparty/$location/*" would probably easier for you to maintain.

Note-3: Why are there changelog copies in debian/upstream?
--- End Message ---
--- Begin Message ---
Source: ublock-origin
Source-Version: 1.22.2+dfsg-2
Done: Markus Koschany 

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ublock-origin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 01:03:22 +0200
Source: ublock-origin
Architecture: source
Version: 1.22.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Markus Koschany 
Closes: 956268
Changes:
 ublock-origin (1.22.2+dfsg-2) unstable; urgency=medium
 .
   * Update debian/copyright. Add some missing file paths and the MIT license.
 (Closes: #956268)
Checksums-Sha1:
 08c8771a101de4218a690961be02a75ca6ce4d3f 2476 ublock-origin_1.22.2+dfsg-2.dsc
 0076d715b43135d22990e9e3d3c2ba73d4ce7071 39992 
ublock-origin_1.22.2+dfsg-2.debian.tar.xz
 a34ad1feb93d83a46da5c47d72573631c34d474d 7298 
ublock-origin_1.22.2+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 1ba4603ed5f23b0fb348e86ade70512a527223d183d5d3a7fd8bde2436d8e9a7 2476 
ublock-origin_1.22.2+dfsg-2.dsc
 18046b20b22d7d78b9417a39b4dfb53bf4622cc4fea9e0369d6247398a0fbfcd 39992 
ublock-origin_1.22.2+dfsg-2.debian.tar.xz
 8ef0ed690f03686758015a0f857924a366b5d2878d396e736ba0439ef957a7af 7298 
ublock-origin_1.22.2+dfsg-2_amd64.buildinfo
Files:
 621c0af7cc175cab06b6451f42230c2b 2476 web optional 
ublock-origin_1.22.2+dfsg-2.dsc
 b9cc811b0faf82fb50529efaeafe4deb 39992 web optional 
ublock-origin_1.22.2+dfsg-2.debian.tar.xz
 fe894f17a6a33ffb44312015044d6d0b 7298 web optional 
ublock-origin_1.22.2+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl6WQmlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkHNsQAKivWZOn/TX7tpnWXAQJBxFzGKpQ52MmA7jP
ITmDkrGgSAyMsZNRLojbwuzhUx38piGGMyngPBDQdWWcJjSS+GqKDhA3uUkKVj/m
S3foiVxYtLN+4Xm/fbLpGpPAhuluZAbHfTUoReub/rFXgX49LZ+yA0vDiJm4qKMZ
lKC2b9/3XhrWzCSzZ56eucgTOL9/uBEQzZOmr782D1ZKzaH58xuUeoiQtp89Mi9e
TfvVAzmudt6JPsbaI1u1QjvzE5D6puStNylLsoBkR9XGkLCdLxqa7Shavq7nEZ0F
h1aC1qmhqU46i+p6oo2J1blr2smeaNtYdJotc5nUXRtU7QnImdkmkFr/wElr+fpA
2SxAVexFq5POnb/MafKpePproae6oRHToe1pwnO/XKRxmTkUceWMfyjnsRnV97Xg
TA+2GDBkIxnLdPBXA/5Y9HSX6iNYpPrMp8e9EA2GUZNw43qnL0cpbiaAP7cBYtsV
GNk1RMAhriVc6NjunHEaQNQ88ksdhWO0ma+XiYzo4G2vwU1bsKHoTezpdMlqxdUP
Pmm0dCLVN+vSH+dhc6l/WpbG5fxD4JVEp8hKpHi54pswHCZvXXIDKjhdmVvoBWzl
5ejC3hWaRlVuuKLA+tSylihFG3ZBbyvOwtGi/7HyuROlwO3ZNfPmBkRqEzeLDGPt
W2zsPBbg
=UffO
-END PGP SIGNATURE End Message ---

Bug#956698: marked as done (lintian: package-from-other-python-variant exception: python-pip-whl)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 23:03:54 +0100
with message-id 
and subject line Re: Bug#956698: lintian: package-from-other-python-variant 
exception: python-pip-whl
has caused the Debian Bug report #956698,
regarding lintian: package-from-other-python-variant exception: python-pip-whl
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.)


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

The package python-pip-whl is a special case of a Python package built
to work with either python or python3.  Currently python3-vertualenv
gets the following lintian warning:

W: python3-virtualenv: 
python-package-depends-on-package-from-other-python-variant Depends: 
python-pip-whl

While this is a great warning in general, in this case it's wrong.
Would it be OK to special case python-pip-whl and have it not trigger
this check?

Scott K
--- End Message ---
--- Begin Message ---
Hi Scott,

> I've added on for python3-virtualenv pointing to this bug.  If that's the 
> preference of the lintian maintainers, I have no objection, please close the 
> bug and we have it documented why it's an override.

Thanks; I believe this is the right call, especially as it puts the
documentation of the exception in the place exactly where the "next"
developer would be looking for it.

Closing this bug accordingly.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org 🍥 chris-lamb.co.uk
   ` End Message ---

Bug#956552: marked as done (arno-iptables-firewall: 90-rpc.plugin causes arno to fail to start.)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:48:31 +
with message-id 
and subject line Bug#956552: fixed in arno-iptables-firewall 2.1.0-3
has caused the Debian Bug report #956552,
regarding arno-iptables-firewall: 90-rpc.plugin causes arno to fail to start.
to be marked as done.

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

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


-- 
956552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arno-iptables-firewall
Version: 2.1.0-2
Severity: normal
Tags: patch upstream

Dear Maintainer,

90-rpc.plugin does not see carriage return as a line break when running rpcinfo 
-p |awk "/tcp.*$service/"' { print $4 }' |uniq

this causes arno to fail to start if you have NFS services, and have turned 
this plugin on.

--- 90rpc.plugin~   2020-01-03 10:38:03.0 +
+++ 90rpc.plugin2020-04-10 20:34:11.124131255 +0100
@@ -38,7 +38,7 @@

   echo "${INDENT}Enabling RPC service(s) $RPC_SERVICES for net(s) $RPC_NETS"

-  IFS=' ,'
+  IFS=$" ,\n"
   for service in $RPC_SERVICES; do
ports="$(rpcinfo -p |awk "/tcp.*$service/"' { print $4 }' |uniq)"
 echo "${INDENT}Adding TCP ports $ports for RPC service $service"

fixes it.

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

Kernel: Linux 5.4.0-2-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)
LSM: AppArmor: enabled

Versions of packages arno-iptables-firewall depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  iproute2   5.6.0-1
ii  iptables   1.8.4-3
ii  kmod   27-2
ii  procps 2:3.3.16-4

Versions of packages arno-iptables-firewall recommends:
ii  bind9-dnsutils [dnsutils]  1:9.16.1-2
ii  curl   7.68.0-1
ii  dnsutils   1:9.16.1-2
ii  rsyslog8.2002.0-2

arno-iptables-firewall suggests no packages.

-- Configuration Files:
/etc/arno-iptables-firewall/plugins/rpc.conf changed:
ENABLED=1
RPC_SERVICES="portmapper status statd nfs mountd nlockmgr"
RPC_NETS="10.0.2.0/24"

-- debconf information excluded

-- debsums errors found:
debsums: changed file /usr/share/arno-iptables-firewall/plugins/90rpc.plugin 
(from arno-iptables-firewall package)
--- End Message ---
--- Begin Message ---
Source: arno-iptables-firewall
Source-Version: 2.1.0-3
Done: Sven Geuer 

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

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

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

Debian distribution maintenance software
pp.
Sven Geuer  (supplier of updated arno-iptables-firewall 
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, 14 Apr 2020 23:16:25 +0200
Source: arno-iptables-firewall
Architecture: source
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sven Geuer 
Closes: 956552
Changes:
 arno-iptables-firewall (2.1.0-3) unstable; urgency=medium
 .
   * Backport an upstream fix to the rpc plugin.
 (Closes: #956552)
 - Introduce d/patches/rpc_plugin_fix.patch.
 - Update d/control to suggest rpcbind.
   * Correct header of d/patches/debian_paths.patch.
Checksums-Sha1:
 479a55d8021c937e721471430eaebcb5c4808af5 2138 
arno-iptables-firewall_2.1.0-3.dsc
 67b286ce428bd3dcb1850b0b408a8d0f68ddbcaa 58908 
arno-iptables-firewall_2.1.0-3.debian.tar.xz
 df28da148453130f86c02ae502cb35207c0975f1 5525 
arno-iptables-firewall_2.1.0-3_source.buildinfo
Checksums-Sha256:
 ed3cba748b0591236dd475d5c200ceac692a11ea4a81f33db9ed128c6997308b 2138 
arno-iptables-firewall_2.1.0-3.dsc
 0a8b3acc0fe4a603d8947f8782437c8b1bcfb6b7b0dd934362dd74f6844fcf58 58908 
arno-iptables-firewall_2.1.0-3.debian.tar.xz
 f2dca8ce6ec91d18b1e18795f142ee26cd234599c102b9df5c11e5ae5a305e6b 5525 
arno-iptables-firewall_2.1.0-3_source.buildinfo
F

Bug#956724: marked as done (vokoscreen-ng: use high resolution icon)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:35:18 +
with message-id 
and subject line Bug#956724: fixed in vokoscreen-ng 3.0.3-2
has caused the Debian Bug report #956724,
regarding vokoscreen-ng: use high resolution icon
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.)


-- 
956724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vokoscreen-ng
Version: 3.0.3-1
Severity: minor
Tags: patch

vokoscreen-ng uses a low resolution icon that looks bad on desktop
environments with large icons, e.g. GNOME.
The attached patch fixes this (and also adds a German translation of the
GenericName field).

Best regards

Ronny

diff --git a/debian/install b/debian/install
index 1c36955..99fc869 100644
--- a/debian/install
+++ b/debian/install
@@ -1,4 +1,3 @@
+src/applications/vokoscreenNG.png usr/share/icons/hicolor/256x256/apps
 src/vokoscreenNG  usr/bin
 debian/menu/vokoscreenNG.desktop  usr/share/applications
-debian/menu/vokoscreenNG.xpm  usr/share/pixmap
-debian/menu/vokoscreenNG.png  usr/share/pixmap
diff --git a/debian/menu/vokoscreenNG.desktop b/debian/menu/vokoscreenNG.desktop
index a69cf1a..f7adc61 100644
--- a/debian/menu/vokoscreenNG.desktop
+++ b/debian/menu/vokoscreenNG.desktop
@@ -1,9 +1,10 @@
 [Desktop Entry]
 Name=vokoscreenNG
 GenericName=Screencast Creator
+GenericName[de]=Screencast-Erstellung
 Comment=Easy to use desktop recorder
 Exec=/usr/bin/vokoscreenNG
-Icon=/usr/share/pixmap/vokoscreenNG.xpm
+Icon=vokoscreenNG
 Terminal=false
 Type=Application
 Categories=AudioVideo;Player;Recorder;
--- End Message ---
--- Begin Message ---
Source: vokoscreen-ng
Source-Version: 3.0.3-2
Done: Joao Eriberto Mota Filho 

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated 
vokoscreen-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, 14 Apr 2020 16:34:17 -0300
Source: vokoscreen-ng
Architecture: source
Version: 3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 956724
Changes:
 vokoscreen-ng (3.0.3-2) unstable; urgency=medium
 .
   * Use high resolution icon. Thanks to Ronny Standtke 
.
 Consequently:
   - debian/source/include-binaries: no longer needed. Removed.
   - debian/install: no longer install vokoscreenNG.xpm and 
vokoscreenNG.png.
   - debian/menu/vokoscreenNG.desktop:
   ~ Changed from /usr/share/pixmap/vokoscreenNG.xpm to vokoscreenNG in
 Icon option.
   ~ Moved to debian/.
   - debian/menu/*: removed.
   - Closes: #956724
   * debian/control: updated the Homepage field.
   * debian/upstream/metadata: created.
   * debian/vokoscreenNG.desktop: added a German translation of the GenericName
 field. Thanks to Ronny Standtke . (Closes: #956724)
Checksums-Sha1:
 c431c9c222522c28b3ea4fd7192767faa416c0e7 2050 vokoscreen-ng_3.0.3-2.dsc
 9408c48862d741b6a347b18817304cc4a5128c0b 5956 
vokoscreen-ng_3.0.3-2.debian.tar.xz
 a53c907956506e5671f047bc253e632eaf67f550 11642 
vokoscreen-ng_3.0.3-2_source.buildinfo
Checksums-Sha256:
 4a9bbd30100ac817d5e7a5f4b1c90929a895925bbf2d15e983ed03eb9c3f14b1 2050 
vokoscreen-ng_3.0.3-2.dsc
 bebf7473258468d4abc26cea5419501acc3997e02cff830b1a0843a4619e1cdd 5956 
vokoscreen-ng_3.0.3-2.debian.tar.xz
 0f3d70049a4dd2e3c84f1936e01a41f271ecd2032f8cb7495757328e3604 11642 
vokoscreen-ng_3.0.3-2_source.buildinfo
Files:
 f579e62f52f230578a4f79724a440684 2050 video optional vokoscreen-ng_3.0.3-2.dsc
 e9937813ae498ba3d4f7d32e923402b3 5956 video optional 
vokoscreen-ng_3.0.3-2.debian.tar.xz
 f54db1e68bea2cbbe3d3603e90e4adb5 11642 video optional 
vokoscreen-ng_3.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl6WJmEACgkQ3mO5xwTr
6e/5bg/9HfTh+6dKsfLg5QBCuwGK8J2RNsH1yVtUO+jNTSjB/rjAao6Hfz2L51EW
ftDqH0VNV7bgvL8VHXsQrIIJZ65u7+N+9vJZ3TRZg

Bug#953032: marked as done (xkbcomp: Internal error: Could not resolve keysym XF86FullScreen)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:35:27 +
with message-id 
and subject line Bug#953032: fixed in xorgproto 2020.1-1
has caused the Debian Bug report #953032,
regarding xkbcomp: Internal error: Could not resolve keysym XF86FullScreen
to be marked as done.

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

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


-- 
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-xkb-utils
Version: 7.7+5

journalctl reports thousands of
sh[1052]: The XKEYBOARD keymap compiler (xkbcomp) reports:
sh[1052]: > Internal error:   Could not resolve keysym XF86FullScreen
sh[1052]: Errors from xkbcomp are not fatal to the X server

Versions of packages x11-xkb-utils depends on:
ii  libc62.29-10
ii  libx11-6 2:1.6.9-2
ii  libxaw7  2:1.0.13-1+b2
ii  libxkbfile1  1:1.0.9-2+b12
ii  libxt6   1:1.1.5-1+b3
--- End Message ---
--- Begin Message ---
Source: xorgproto
Source-Version: 2020.1-1
Done: Timo Aaltonen 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 00:18:42 +0300
Source: xorgproto
Architecture: source
Version: 2020.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 953032
Changes:
 xorgproto (2020.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #953032)
   * control, rules: Drop obsolete transitional packages which have no
 reverse dependencies left:
 - x11proto-bigreqs-dev
 - x11proto-composite-dev
 - x11proto-damage-dev
 - x11proto-dmx-dev
 - x11proto-dri3-dev
 - x11proto-fixes-dev
 - x11proto-resource-dev
 - x11proto-xcmisc-dev
 - x11proto-xf86bigfont-dev
Checksums-Sha1:
 cc3f3ff6d724cfe59eab197084e0d1bcdfc1914e 3410 xorgproto_2020.1-1.dsc
 b383dac4e74f704d9616eabe2d281f223c825d1b 1081369 xorgproto_2020.1.orig.tar.gz
 a50830f731bc11bdecf839c5eb9ea642c4c5a62e 659 xorgproto_2020.1.orig.tar.gz.asc
 acdc8daea5f61b648ab9a372012e301c83582328 20627 xorgproto_2020.1-1.diff.gz
 435a08007558a80d70ef31ef4897398b6a0588f7 7167 
xorgproto_2020.1-1_source.buildinfo
Checksums-Sha256:
 227dba0e174e781c68502d33af10527d5d19d692ad969442a75c422a3cbaae6a 3410 
xorgproto_2020.1-1.dsc
 6265b11b125df2f4853eec4895b14067d5621f813553fa077bebef20d7542418 1081369 
xorgproto_2020.1.orig.tar.gz
 00af3777b1b00b5553d0838356202c920f94b3088502aca9c4c37abd704bf39d 659 
xorgproto_2020.1.orig.tar.gz.asc
 b96eb973c1effc4fb5a8545f81983d1acf7a6f01231da230b5911daa4eca35be 20627 
xorgproto_2020.1-1.diff.gz
 6bee58fe880556ca7b3728996b99ab348540b86b2f95aefd6fb3211558e0dfb4 7167 
xorgproto_2020.1-1_source.buildinfo
Files:
 385aa3dfe6975596acab582200590745 3410 x11 optional xorgproto_2020.1-1.dsc
 3223ceaeac5fc377ee99deb6cb69355d 1081369 x11 optional 
xorgproto_2020.1.orig.tar.gz
 a794dfd3b004690fdcf2dc18ccedee0e 659 x11 optional 
xorgproto_2020.1.orig.tar.gz.asc
 087f855cb0f72db67ec10e2e6e345c41 20627 x11 optional xorgproto_2020.1-1.diff.gz
 d3a7e352f14b3df7244461a8b84dc0c0 7167 x11 optional 
xorgproto_2020.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6WKR8ACgkQy3AxZaiJ
hNzKyhAAq32GSVzvd7VjI4W3XGTxbXj9EbpuHVmuKQ0SoUMqsw6h5DmGvaUtthVR
7eSG87yxXFQ8K4oDpnqg04KB9Yd97L1MUNok5jQgROf1+9z9V5I8MsFXQtOVh8FY
LzrgfeQv40pzfmaxo8MRUSSBL3OyY7Og7k+B0CHyIopWjnibcB/Bh8s2hMKMUGBx
3kDd++5Xa+XsBX+EOrD2wu2RzdrZHQX6IyObVHEi0SZ/weNqhyCjWwQ6dKxKSGD3
1tDEbpxrnLNcbx+A61we1HYDQAFdgw6KGFdPcSZOFuYsdhIF5EnPkPh3dR9bswuu
xZrIgn9D81h9wf3NhjKExfZejXh1mXbB/2/wKpi1UpAtkd8TG6uBjMpemJA6Lx/N
rld7jDT77/SEWGA9M44+yGN3l2X1NhQlelSJ4MExYnr1j0LotRFzVNeNQCcszBcH
kJ/c5KJOL3MaJ3VAgbcJny1poJmYnAJTiThbzShlFYMcbNQFlSst4zjRsK+GmeE6
5Kkzfm68IypKFplsuIuFtBH+sAG88KlgR/8w17P+Cx2TKXjgiEgpEMduY7fMRoDH
qgjvwQh7GG40AKRx8jPsM2IHIUOotuuU2QsaXI5aHhgVPXxd4TwzA6bwIWYLcu8B
+domogEONAA+oMV5kzw8d0u+haHUpivznYJmILj9UhaEUMaHKPM=
=mHUz
-EN

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:34:47 +
with message-id 
and subject line Bug#938004: fixed in python-pathlib2 2.3.5-2
has caused the Debian Bug report #938004,
regarding python-pathlib2: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-pathlib2

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-pathlib2
Source-Version: 2.3.5-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-pathlib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 17:16:53 -0400
Source: python-pathlib2
Architecture: source
Version: 2.3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938004
Changes:
 python-pathlib2 (2.3.5-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938004
Checksums-Sha1:
 85f0bb1a36143e99a3496767246d39a4f1f278a1 2079 python-pathlib2_2.3.5-2.dsc
 13e19f43d40c6c54c82eccf4bd4a558163475a48 2580 
python-pathlib2_2.3.5-2.debian.tar.xz
 01d33edd0c1da08291a7055a4420b8230b1d7033 7423 
python-pathlib2_2.3.5-2_amd64.buildinfo
Checksums-Sha256:
 1cf298c1bad8969e077df6b04bdbd345110bffdff8069c4f014557bbcc33824f 2079 
python-pathlib2_2.3.5-2.dsc
 ed5421e009f40f40ded13d69ede981f3c2976f3ee39a4e3b3f9d077f235b03cc 2580 
python-pathlib2_2.3.5-2.debian.tar.xz
 21dba3f237a08f86f91865f724ba99866153eb2a450b04b58ebfac0449e4bf4a 7423 
python-pathlib2_2.3.5-2_am

Bug#900705: marked as done (x42-plugins FTCBFS: many reasons)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:21:48 +
with message-id 
and subject line Bug#900705: fixed in x42-plugins 20200411-1
has caused the Debian Bug report #900705,
regarding x42-plugins FTCBFS: many reasons
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.)


-- 
900705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x42-plugins
Version: 20170428-1.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

x42-plugins fails to cross build from source for a pile of reasons.
First and foremost, the Makefiles hard code the build architecture
pkg-config. Allowing substitution produces quite a big cross.patch, but
that part should be upstreamable. Then the packaging needs to pass cross
compilers and a cross pkg-config to make. Furthermore, stripping (with
the build architecture strip) fails. Stripping not just breaks cross
compilation, but also generation of -dbgsym packages, so disable it
entirely. The attached patch makes x32-plugins cross buildable. Please
consider applying it.

Helmut
diff --minimal -Nru x42-plugins-20170428/debian/changelog 
x42-plugins-20170428/debian/changelog
--- x42-plugins-20170428/debian/changelog   2018-03-20 19:30:37.0 
+0100
+++ x42-plugins-20170428/debian/changelog   2018-06-03 17:13:31.0 
+0200
@@ -1,3 +1,15 @@
+x42-plugins (20170428-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: Allow substituting pkg-config.
++ Let dh_auto_build pass cross CC and CXX to make.
++ Let buildtools.mk set up PKG_CONFIG for dh_auto_install.
++ Disable stripping during build, let dh_strip perform stripping.
+  * Remove useless override_dh_auto_configure.
+
+ -- Helmut Grohne   Sun, 03 Jun 2018 17:13:31 +0200
+
 x42-plugins (20170428-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru x42-plugins-20170428/debian/patches/cross.patch 
x42-plugins-20170428/debian/patches/cross.patch
--- x42-plugins-20170428/debian/patches/cross.patch 1970-01-01 
01:00:00.0 +0100
+++ x42-plugins-20170428/debian/patches/cross.patch 2018-06-03 
17:13:31.0 +0200
@@ -0,0 +1,1098 @@
+--- x42-plugins-20170428.orig/balance.lv2/Makefile
 x42-plugins-20170428/balance.lv2/Makefile
+@@ -9,6 +9,7 @@
+ CXXFLAGS ?= $(OPTIMIZATIONS) -Wall
+ LIBDIR ?= lib
+ 
++PKG_CONFIG?=pkg-config
+ STRIP?=strip
+ STRIPFLAGS=-s
+ UISTRIPFLAGS=-s
+@@ -62,10 +63,10 @@
+ include git2lv2.mk
+ 
+ # check for build-dependencies
+-ifeq ($(shell pkg-config --exists lv2 || echo no), no)
++ifeq ($(shell $(PKG_CONFIG) --exists lv2 || echo no), no)
+   $(error "LV2 SDK was not found")
+ else
+-  override CXXFLAGS+=`pkg-config --cflags lv2`
++  override CXXFLAGS+=`$(PKG_CONFIG) --cflags lv2`
+ endif
+ 
+ # optional UI
+@@ -95,18 +96,18 @@
+   endif
+ endif
+ 
+-HAVE_UI=$(shell pkg-config --exists $(PKG_GL_LIBS) ftgl && echo $(FONT_FOUND))
++HAVE_UI=$(shell $(PKG_CONFIG) --exists $(PKG_GL_LIBS) ftgl && echo 
$(FONT_FOUND))
+ 
+ LV2UIREQ=
+ # check for LV2 idle thread -- requires 'lv2', atleast_version='1.4.6
+-ifeq ($(shell pkg-config --atleast-version=1.4.6 lv2 || echo no), no)
++ifeq ($(shell $(PKG_CONFIG) --atleast-version=1.4.6 lv2 || echo no), no)
+   UICFLAGS+=-DOLD_SUIL
+ else
+   LV2UIREQ=lv2:requiredFeature ui:idleInterface; lv2:extensionData 
ui:idleInterface;
+ endif
+ 
+ # check for lv2_atom_forge_object  new in 1.8.1 deprecates 
lv2_atom_forge_blank
+-ifeq ($(shell pkg-config --atleast-version=1.8.1 lv2 && echo yes), yes)
++ifeq ($(shell $(PKG_CONFIG) --atleast-version=1.8.1 lv2 && echo yes), yes)
+   override CXXFLAGS += -DHAVE_LV2_1_8
+ endif
+ 
+@@ -120,34 +121,34 @@
+ UIDEPS+=pugl/pugl_osx.m
+ UILIBS=pugl/pugl_osx.m -framework Cocoa -framework OpenGL
+ UI_TYPE=CocoaUI
+-UILIBS+=`pkg-config --variable=libdir ftgl`/libftgl.a `pkg-config 
--variable=libdir ftgl`/libfreetype.a -lm -mmacosx-version-min=10.5 
+-UILIBS+=`pkg-config --libs zlib`
++UILIBS+=`$(PKG_CONFIG) --variable=libdir ftgl`/libftgl.a `$(PKG_CONFIG) 
--variable=libdir ftgl`/libfreetype.a -lm -mmacosx-version-min=10.5
++UILIBS+=`$(PKG_CONFIG) --libs zlib`
+   else
+ ifneq ($(XWIN),)
+   UIDEPS+=pugl/pugl_win.cpp
+   UICFLAGS+=-DPTW32_STATIC_LIB
+   UILIBS=pugl/pugl_win.cpp
+-  UILIBS+=`pkg-config --variable=libdir ftgl`/libftgl.a `pkg-config 
--variable=libdir ftgl`/libfreetype.a
+-  UILIBS+=`pkg-config --libs zlib`
++  UILIBS+=`$(PKG_CONFIG) --variable=libdir ftgl`/libftgl.a `$(PKG_CONFIG

Bug#937334: marked as done (ptyprocess: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:20:00 +
with message-id 
and subject line Bug#937334: fixed in ptyprocess 0.6.0-2
has caused the Debian Bug report #937334,
regarding ptyprocess: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ptyprocess
Source-Version: 0.6.0-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated ptyprocess package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 17:04:50 -0400
Source: ptyprocess
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937334
Changes:
 ptyprocess (0.6.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * Use debhelper-compat instead of debian/compat.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set upstream metadata fields: Bug-Database, Repository, Repository-
 Browse.
   * Set upstream metadata fields: Bug-Submit.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937334
Checksums-Sha1:
 59036ab977966d6dd0021fb9cdeaeecc8a01e9c1 1994 ptyprocess_0.6.0-2.dsc
 7bfe8b98bd6ec2bb9f8c46f9f2d58d9b7fd37689 2528 ptyprocess_0.6.0-2.debian.tar.xz
 fe9ff43e9a75ebe7dfc42e4b4070cfe1d1449410 6415 
ptyprocess_0.6.0-2_source.buildinfo
Checksums-Sha256:
 01a1c8ad984c2d07b88ca8efca9c945

Bug#936332: marked as done (contextlib2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:18:38 +
with message-id 
and subject line Bug#936332: fixed in contextlib2 0.6.0-3
has caused the Debian Bug report #936332,
regarding contextlib2: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: contextlib2
Source-Version: 0.6.0-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated contextlib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 17:08:20 -0400
Source: contextlib2
Architecture: source
Version: 0.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936332
Changes:
 contextlib2 (0.6.0-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #936332
Checksums-Sha1:
 e71986ef514ef9445c32fc4b2066bb31e0add90b 2199 contextlib2_0.6.0-3.dsc
 be25673a84854e574e792b7a815856f61c605ef7 4964 contextlib2_0.6.0-3.debian.tar.xz
 7e51786fb1250e910beb90675a660f5f2ee87d04 6625 
contextlib2_0.6.0-3_source.buildinfo
Checksums-Sha256:
 22d56b0e17a36f1d6dd24b99096d6a3a46f70debd2cb6a429ecacaaacd484d51 2199 
contextlib2_0.6.0-3.dsc
 8b81ff3c3bac3e3de5717237fe8e69bbb0d23f7138b6b227ac13152ee5141253 4964 
contextlib2_0.6.0-3.debian.tar.xz
 542b5e4662395b219ec301228d94bf90cad698afeedb29cd370984ad6d968e98 6625 
contextlib2_0.6.0-3_source.buildinfo
Files:
 ffe0f0645b02a88b73834432d942ceac 2199

Bug#937083: marked as done (more-itertools: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:19:55 +
with message-id 
and subject line Bug#937083: fixed in more-itertools 4.2.0-2
has caused the Debian Bug report #937083,
regarding more-itertools: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: more-itertools
Source-Version: 4.2.0-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated more-itertools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 17:01:38 -0400
Source: more-itertools
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937083
Changes:
 more-itertools (4.2.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937083
Checksums-Sha1:
 575dc1d6fb3a1133fd98960cd4e8a40d83f26845 2349 more-itertools_4.2.0-2.dsc
 4b32f25487ed70a4b9e77cc51e101ec7dd223756 2632 
more-itertools_4.2.0-2.debian.tar.xz
 93ddf68f64f10147636824563e776f5caf71658b 7866 
more-itertools_4.2.0-2_amd64.buildinfo
Checksums-Sha256:
 99778edaa4

Bug#956625: marked as done (texlive-luatex fails to install: running `luatex -ini -jobname=optex -progname=optex optex.ini

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 20:39:17 +
with message-id 
and subject line Bug#956625: fixed in texlive-base 2020.20200329-3
has caused the Debian Bug report #956625,
regarding texlive-luatex fails to install: running `luatex -ini   
-jobname=optex -progname=optex optex.ini https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-luatex
Version: 2020.20200329-2
Severity: grave
Justification: fails to install on a clean system

Dear Maintainer,

When trying to run “apt install texlive-luatex” on a clean sid chroot,
I get this error:

  Setting up texlive-luatex (2020.20200329-2) ...
  Processing triggers for libc-bin (2.30-4) ...
  Processing triggers for tex-common (6.13) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
  This may take some time... 
  fmtutil failed. Output has been stored in
  /tmp/fmtutil.zMbmF90b
  Please include this file if you report a bug.

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

The mentioned /tmp/fmtutil.zMbmF90b file is attached.

--
Dmitry Shachnev
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil:   /etc/texmf/web2c/fmtutil.cnf
fmtutil [INFO]: writing formats under /var/lib/texmf/web2c
fmtutil [INFO]: --- remaking luahbtex with luahbtex
fmtutil: running `luahbtex -ini   -jobname=luahbtex -progname=luahbtex 
luatex.ini' ...
This is LuaHBTeX, Version 1.12.0 (TeX Live 2020/Debian)  (INITEX)
 restricted system commands enabled.
(/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/luatex.ini
(/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/luatexconfig.tex
(/var/lib/texmf/tex/generic/config/pdftexconfig.tex))
(/usr/share/texlive/texmf-dist/tex/generic/config/luatexiniconfig.tex)
(/usr/share/texlive/texmf-dist/tex/generic/unicode-data/load-unicode-data.tex

load-unicode-data.tex v1.12 (2020-03-12)
Reading Unicode data
# UnicodeData-13.0.0.txt
# Modified 2020-03-12 11:00:00 GMT [JAW]
) (/usr/share/texlive/texmf-dist/tex/luatex/hyph-utf8/etex.src
(/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers, parameters, fonts, more fonts,
macros, math definitions, output routines, hyphenation
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex
[skipping from \patterns to end-of-file...]))
(/usr/share/texlive/texmf-dist/tex/plain/etex/etexdefs.lib
Skipping module "grouptypes"; Loading module "interactionmodes";
Skipping module "nodetypes"; Skipping module "iftypes";)
(/usr/share/texlive/texmf-dist/tex/generic/config/language.def
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex))
Augmenting the Plain TeX definitions: \tracingall;
Adding new e-TeX definitions: \eTeX, \loggingall, \tracingnone,
register allocation; extended register allocation; 
Recycling: \addlanguage, \@nswer (not defined), \@sk, \b@dresponsetrue,
\b@dresponsefalse, \ch@ckforyn, \mayber@cycle, \et@xabort, \et@xbuf,
\et@xfmtsrc, \et@xfilehdr, \et@xinf, \et@xpatterns, \l@ngdefnfile, \n@xt,
\p@rse (not defined), \pr@mpt (not defined), \pr@mptloop (not defined),
\forcer@cycle, \usef@llback, \usef@llbacktrue, \usef@llbackfalse, 
Retaining: \et@xerr, \et@xinput, \et@xlibhdr, \et@xmsg, \et@xtoks, \et@xwarn,
\et@xl@@d, \et@xl@ad, \et@xload, \et@xlang, \et@xhash, \eTeX, \etexhdrchk,
\etexstatus, \module, \uselanguage, \r@tain, \r@cycle,))
Beginning to dump on file luahbtex.fmt
 (format=luahbtex 2020.4.13)
3354 strings using 10263 bytes
68807 memory locations dumped; current usage is 149&7700
1869 multiletter control sequences
\font\nullfont=nullfont
\font\tenrm=cmr10
\font\preloaded=cmr9
\font\preloaded=cmr8
\font\sevenrm=cmr7
\font\preloaded=cmr6
\font\fiverm=cmr5
\font\teni=cmmi10
\font\preloaded=cmmi9
\font\preloaded=cmmi8
\font\seveni=cmmi7
\font\preloaded=cmmi6
\font\fivei=cmmi5
\font\tensy=cmsy10
\font\preloaded=cmsy9
\font\preloaded=cmsy8
\font\sevensy=cmsy7
\font\preloaded=cmsy6
\font\fivesy=cmsy5
\font\tenex=cmex10
\font\preloaded=cmss10
\font\preloaded=cmssq8
\font\preloaded=cmssi10
\font\preloaded=cmssqi8
\font\tenbf=cmbx10
\font\preloaded=cmbx9
\font\preloaded=cmbx8
\font\sevenbf=cmbx7
\font\preloaded=cmbx6
\font\fivebf=cmbx5
\font\tentt=cmtt10
\font\preloaded=cmtt9
\font\preloaded=cmtt8
\font\preloaded=cmsltt10
\font\tensl=cmsl10
\font\preloaded=cmsl9
\font\preloaded=cmsl8
\font\tenit=cmti10
\font\preloaded=cmti9
\font\preloaded=cmti8
\font\preloaded=cmti7
\font\preloaded=cmu10
\font\preloaded=cmmib10
\font\preloaded=cmbsy10
\font\preloaded=cmcsc10
\font\preloaded=cmssbx10
\font\preloaded=cmdunh10
\font\preloa

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 20:39:25 +
with message-id 
and subject line Bug#955527: fixed in trace-cmd 2.8.3-6
has caused the Debian Bug report #955527,
regarding kernelshark: Crash (SIGSEGV) when pressing the "+" button
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.)


-- 
955527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernelshark
Version:  2.8.3-5
Severity: grave
X-Debbugs-CC: sudipm.mukher...@gmail.com

Dear Debian kernelshark (trace-cmd) maintainer,

When I perform the following actions in kernelshark in Debian Sid, kernel
shark will crash:

1. Open kernelshark
2. Click the "+" button

Partial traceback is as follows:


===
Thread 1 "kernelshark" received signal SIGSEGV, Segmentation fault.
0x76d77918 in ksmodel_zoom (histo=0x7fffde60, r=,
mark=, zoom_in=) at ./kernel-
shark/src/libkshark-model.c:693
693 ./kernel-shark/src/libkshark-model.c: No such file or directionary.
(gdb) bt full
#0  0x76d77918 in ksmodel_zoom (histo=0x7fffde60, r=, mark=, zoom_in=) at ./kernel-
shark/src/libkshark-model.c:693
range = 
min = 
max = 
delta_min = 
delta_tot = 
#1  0x76d77d0a in ksmodel_zoom_in (histo=, r=, mark=) at ./kernel-shark/src/libkshark-model.c:722
No locals.
#2  0x77f591ba in KsGraphModel::zoomIn (this=0x7fffde50, r=0.01,
mark=-1) at ./kernel-shark/src/KsModels.cpp:473
No locals.
#3  0x77f6bb41 in KsTraceGraph::_updateGraphs (this=0x7fffd930,
action=KsTraceGraph::GraphActions::ZoomIn) at ./kernel-
shark/src/KsGLWidget.hpp:72
k = 0.01
bin = 
#4  0x775bc4e8 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#5  0x77aa358d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#6  0x77aa3c6d in QAbstractButton::mousePressEvent(QMouseEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.



Let me know if more information is needed to debug this issue. Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: trace-cmd
Source-Version: 2.8.3-6
Done: Sudip Mukherjee 

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

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

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated trace-cmd 
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, 14 Apr 2020 19:16:58 +0100
Source: trace-cmd
Architecture: source
Version: 2.8.3-6
Distribution: unstable
Urgency: medium
Maintainer: Sudip Mukherjee 
Changed-By: Sudip Mukherjee 
Closes: 955527
Changes:
 trace-cmd (2.8.3-6) unstable; urgency=medium
 .
   * Fix SIGSEGV with Kernelshark. (Closes: #955527)
   * Use secure copyright format uri.
Checksums-Sha1:
 33ad7ce01bb2c541a4ce854531c9292502739bf6 2042 trace-cmd_2.8.3-6.dsc
 4a11635f95d6b0cb3afb18deafb5c333fad469eb 6620 trace-cmd_2.8.3-6.debian.tar.xz
 cc1630a10a6688f4108686e6bc5bfea6d006d78d 12457 
trace-cmd_2.8.3-6_amd64.buildinfo
Checksums-Sha256:
 a9cf934f212b6389d6d2e35da14c0fd71d4b4feeb88a709f4715646821d4f97c 2042 
trace-cmd_2.8.3-6.dsc
 f467a7fb43502a60344b84f5d9a5d408d7fcf1723efd026e3889191636664e8e 6620 
trace-cmd_2.8.3-6.debian.tar.xz
 2c4bbb0bd171b8d96ceba03b2b27b492274b5ac341caa64e6d41df9dc04842aa 12457 
trace-cmd_2.8.3-6_amd64.buildinfo
Files:
 6090760824adece2a041ff61ab77e97a 2042 devel optional trace-cmd_2.8.3-6.dsc
 409ff6f6409fed591301ecaf9e8b7e81 6620 devel optional 
trace-cmd_2.8.3-6.debian.tar.xz
 fa84ed27dd626913fc62bb9b230ae1e5 12457 devel optional 
trace-cmd_2.8.3-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl6WEb4ACgkQR5mjUUbR
KzVHjBAAiTRcxatkdsvY8EexfAOtTfK6pprPyQYJf8QKnwzAmRC7U+yKpc+kV+TA
k4yku73Rmmp2O+2SEg6J2hGtLLkjQHzr9AMJiU4FJhk

Bug#929206: marked as done (lshw: wrong -json output)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 20:34:57 +
with message-id 
and subject line Bug#929206: fixed in lshw 02.18.85-0.4
has caused the Debian Bug report #929206,
regarding lshw: wrong -json output
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.)


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

Dear Maintainer,

Executing lshw -json prints a json with wrong syntax, making it unusuable.

I tried compiling the software directly from the repository of lshw with the 
same results.
The only version that does not fail for me is the one that the original author 
considers stable: B.02.18. Compiling and using this one in my Debian 10 works.

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

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

Versions of packages lshw depends on:
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libstdc++6  8.3.0-6

Versions of packages lshw recommends:
ii  pciutils  1:3.5.2-1
ii  usbutils  1:010-3

lshw suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lshw
Source-Version: 02.18.85-0.4
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated lshw package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 22:07:20 +0200
Source: lshw
Architecture: source
Version: 02.18.85-0.4
Distribution: unstable
Urgency: medium
Maintainer: Ghe Rivero 
Changed-By: Thomas Goirand 
Closes: 929206
Changes:
 lshw (02.18.85-0.4) unstable; urgency=medium
 .
   * Switch to debhelper-compat (= 10).
   * Add revert-Fix_JSON_output_format.patch (Closes: #929206).
Checksums-Sha1:
 01900d53016148d1b93e910b4e94a1a4bd92b97f 1922 lshw_02.18.85-0.4.dsc
 14a80c7d22a3bdfa2252615ac80510fb3e8f09f8 17136 lshw_02.18.85-0.4.debian.tar.xz
 43cb509a6118dfd825353c0f9fd3aa0caae8b88c 11531 
lshw_02.18.85-0.4_amd64.buildinfo
Checksums-Sha256:
 ae529f386b02df6db189dc183a0f0004ba6b2281099cde67e3a07a0a900d2770 1922 
lshw_02.18.85-0.4.dsc
 6d5d36a1eb65ab47d71856e87bbf5e18b89a70e5a0b7c5a22ab5ca6bae4c6639 17136 
lshw_02.18.85-0.4.debian.tar.xz
 c06ee1bd2a61f297e8619cf9cc9a98f5e847e0355e673c062cb7e83dcd04b79e 11531 
lshw_02.18.85-0.4_amd64.buildinfo
Files:
 508ae3134cd167acddc9d662bad6f4b7 1922 utils optional lshw_02.18.85-0.4.dsc
 8eda59a1a38041269740993b7ed45743 17136 utils optional 
lshw_02.18.85-0.4.debian.tar.xz
 8632d4b683d97c20862bec21b85b37f7 11531 utils optional 
lshw_02.18.85-0.4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl6WGaMACgkQ1BatFaxr
Q/7dEg/9EP/ujI/uyN0S0uZ1KfSeHpZea2+81mTI5JGEsNiGq32fvr5JjEpx1//4
rn01KGipK2ZHXCOgNovb7KEtUhcJQ2U2ffiH4WI0Qv2A8z8TvgKNrjlcVg5I+uPe
4I31i0QgX8NeymwCLcbyWxxEggtmsZzWhOrRywqYDaye+sZCR/DoCAq1O/CxC5cC
OQ+1W06TwSqCAT2m6MUB2j+htsNXUszKJB5h57cRflylwi2qrBpa8KeI+EJ6/2X4
42ntyO0PpN0X6LLu0FSrRb8AEGQroO7DC5j16LvWsyzg5RhcJuggEnJT6IFl3e9w
O9Z89US9sFP+Gpjvd1t1SXIF1KgF2fMxcgwXAKTZyyyiCcxs6wvBleU8AONNOVIO
JRbiWuiQdrU3+OptbJX5RuPcAYTV/mhkUq+SAlz9CTpSoAF6F/BGyMZzb6Xxcper
fQnUtFyHuZZijDS5k83qlXbG8NMKDQtmOK0FWJUJVNth4hLNbzzbQU72O2J+6CQR
bf4rHKmAJi8l9OSjQ66SxDRychlstSUCOMET05MD/KZkVStPs7eA8LDncOg1A6l6
HRqGUL9L9tkjbvQZCTzat0btTOVwgFkKnea1XcdSuC6utvFxMWAjL4CGsGIej7A6
kURxsLRo6GGeC3mc0mqWFAnTmGYPZn+L6yQwyTJyqYjRGfynt2Q=
=YD9m
-END PGP SIGNATURE End Message ---

Bug#956672: marked as done (rtkit activation fails, because service unit is installed at the wrong place)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 19:49:59 +
with message-id 
and subject line Bug#956672: fixed in rtkit 0.13-3
has caused the Debian Bug report #956672,
regarding rtkit activation fails, because service unit is installed at the 
wrong place
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.)


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

Hi,

syslog is full with:

Apr 14 08:42:53 host dbus-daemon[940]: [system] Activating via systemd: service 
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by 
':1.158' (uid=1000 pid=156197 comm="/usr/lib/firefox/firefox -contentproc 
-childID 6 -")
Apr 14 08:42:53 host dbus-daemon[940]: [system] Activation via systemd failed 
for unit 'rtkit-daemon.service': Unit rtkit-daemon.service not found.

... and the reason is:

# dpkg -L rtkit | grep rtkit-daemon.service
/usr/lib/x86_64-linux-gnu/systemd/system/rtkit-daemon.service

The unit file should be under /usr/lib/systemd/system.

Regards,
Gabor

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

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

Versions of packages rtkit depends on:
ii  adduser  3.118
ii  dbus 1.12.16-2
ii  libc62.30-4
ii  libcap2  1:2.33-1
ii  libdbus-1-3  1.12.16-2
ii  libsystemd0  245.4-3
ii  policykit-1  0.105-26

rtkit recommends no packages.

rtkit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rtkit
Source-Version: 0.13-3
Done: Felipe Sateler 

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

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

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated rtkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 15:19:09 -0400
Source: rtkit
Architecture: source
Version: 0.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Felipe Sateler 
Closes: 956672
Changes:
 rtkit (0.13-3) unstable; urgency=medium
 .
   * Fix typo and install systemd service at the correct location
 (Closes: #956672)
Checksums-Sha1:
 f09a8b35c05f1135b2acff95882cb3cb2a39739d 2445 rtkit_0.13-3.dsc
 bda775882cc41f7156217d0787ce6381fe46b25d 16092 rtkit_0.13-3.debian.tar.xz
Checksums-Sha256:
 9b26ed10e3ef19edd26f6306b7835e9fa2079b79feb928bac3cc934ee80febae 2445 
rtkit_0.13-3.dsc
 2621618d68e29966b415607d640f004e606590a4c01fcb54701118b99a31242e 16092 
rtkit_0.13-3.debian.tar.xz
Files:
 95e6fd3fbc8b02183c8c93cebf7ae897 2445 admin optional rtkit_0.13-3.dsc
 696cbf525af4a4167a06817c5dcddb66 16092 admin optional 
rtkit_0.13-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAl6WDQ4UHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s8C4w//VJJGMVTy7PFr+7Pn78zuO1pThBRL
kM+EXXnZkejSaIEsmelH1wHMaYpzWjhCBayZeO62Lq93v5rLlpdDGi5xi1Bpbgkp
64qHT+s0avxiEb7kXDEFkkXyxKluvSyJI9Dx7T5tkSBX3svXUnWiNeyFmq9jEIt2
u8vWcSeBk+3sTq5/xpS4AQyW9DxY2cxgtoD1IoRJu6QCv9OuIPwrsmuAXUnF+Aeu
cICh2gyIcbduVfBzP2JEI33mS2LqOnhrErvCM5VuvxRHR+kqKRNCBcki61j4vO9a
vOjnAOdEkinjrIdpmVP1UJiKcbBNRSabV4CgTjrHmg2kFvW97f36mgPAZOeNobR3
X8bNvBC/2S/51gR3XLGCP3E+Qv1lEJX95DE79tvtlgxbGMWMB4jI+53C3nHZDB8t
uYGWklrk/SXdfZ9XdSuHWv7Vn8ugpDVdaMNaKbuSSiy8ALZwyn1jCJ0giCMaJTpU
EYo4OktWu+9KOWLGN4mNLAlCLtD4iam+IldrOmNG8ph1P+5EJUkgqrLzP2SYIxvL
7fXHVglQtwQJdaHagLAhQ65ZJY9sf0mhCF56h1Wt0OTKakgHr01kYflK7cVEUOW7
nWtV6DtulnFGfNY0Hcu5/ZyqTQXHB2g+a1uYKkAh5okMxbAlmJ10l7Tp4J6WJmTb
HErOsHv7pLF/9Qo=
=DRJh
-END PGP SIGNATURE End Message ---

Bug#939363: marked as done (openssl: Older OpenSSL binaries crash on startup, no error messages are shown.)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:14:14 +0200
with message-id <20200414191414.xpq2yyyvy6fau6e5@flow>
and subject line Re: [Pkg-openssl-devel] Bug#939363: openssl: Older OpenSSL 
binaries crash on startup, no error messages are shown.
has caused the Debian Bug report #939363,
regarding openssl: Older OpenSSL binaries crash on startup, no error messages 
are shown.
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.)


-- 
939363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssl
Version: 1.1.1c-1
Severity: important

As title says. Using AppImages with older OpenSSL binaries instantly aborts the
application and I get no error codes. I have tested this with Ripcord and it
will not open.

Hopefully this will be resolved soon. The developer of this application
(ripcord) says that the OpenSSL package is broken and incompatible with older
binaries.



-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages openssl depends on:
ii  libc6  2.28-10
ii  libssl1.1  1.1.1c-1

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20190110

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2019-09-04 21:11:24 [+0200], To Dylan H. wrote:
> On 2019-09-03 21:24:04 [-0400], Dylan H. wrote:
> > As title says. Using AppImages with older OpenSSL binaries instantly aborts 
> > the
> > application and I get no error codes. I have tested this with Ripcord and it
> > will not open.
> 
> can you give some more details? Like what you have installed and what
> have you started. Applications which linked against libssl have symbol
> dependecies which means an older version is either linked to another
> libssl or should work with the current library.
> 
> > Hopefully this will be resolved soon. The developer of this application
> > (ripcord) says that the OpenSSL package is broken and incompatible with 
> > older
> > binaries.
> 
> Can you provide a link to that application? I can't find anything
> usefull. Saying "broken and incompatible" is not helpfull in oder to
> dermine the root cause. There are no problems with the applications in
> the devian archive so it must be limited to something "special".

No more feedback, closing.

Sebastian--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 19:06:17 +
with message-id 
and subject line Bug#938011: fixed in python-pbr 5.4.3-3
has caused the Debian Bug report #938011,
regarding python-pbr: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-pbr

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-pbr
Source-Version: 5.4.3-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-pbr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 14:49:01 -0400
Source: python-pbr
Architecture: source
Version: 5.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Sandro Tosi 
Closes: 938011
Changes:
 python-pbr (5.4.3-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938011
Checksums-Sha1:
 ba12ece82158439ada04a57d5d7a64e8bbc95370 2692 python-pbr_5.4.3-3.dsc
 41ab65f0bc5c44cea4e7423f1ae0969561e090fa 7928 python-pbr_5.4.3-3.debian.tar.xz
 a4996a0906bf7e260d5350fc28d3d50e861a592c 11864 
python-pbr_5.4.3-3_source.buildinfo
Checksums-Sha256:
 478db953d6ce519ca30fbe16058bf11bf40defd466c0f45cafb2d061f9b938fe 2692 
python-pbr_5.4.3-3.dsc
 4416dbcee6911ab0b6968f1322251e18c4a67696553fef745c0ff58efa4fdc55 7928 
python-pbr_5.4.3-3.debian.tar.xz
 a8b21cc3c9eab1c979edd4a966722c980ac3b4b816aa740e19e8c973abe26de3 11864 
python-pbr_5.4.3-3_source.buildinfo
Files:
 139a30ea19598da591c40e065bbdd60f 2692 python optional python-

Bug#952806: marked as done (cbindgen: please package recent version 0.13.1 into experimental)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 19:31:10 +0100
with message-id <8bacb366-1f80-6691-395c-cafe35342...@p10link.net>
and subject line FWIW, cbindgen 0.14.1-1 is already in sid/unstable and perhaps 
will migrate to testing if tomorrow or day after rust-libc migrates
has caused the Debian Bug report #952806,
regarding cbindgen: please package recent version 0.13.1 into experimental
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.)


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

Dear Maintainers of cbindgen,

please consider packaging of cbindgen version >= 0.13 for experiemntal.

I'm trying to work on the current most recent Thunderbird beta version
74.0~b2 and this is requiring cbindgen >= 0.13. So providing cbindgen
within experimental would help me much.

Thanks
Carsten

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

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

Version: 0.13.1-1


FWIW, cbindgen 0.14.1-1 is already in sid/unstable


Indeed, closing this bug.


and perhaps will migrate to testing if tomorrow or day after rust-libc migrates

It's going to take a bit longer than that,Sylvestre and I have been plugging 
through the pile of dependencies but some of the packages don't have functional 
autopkgtests so are subject to the 5 day migration delay and it's possible that 
there is something I missed and/or new issues have popped up since I put 
together my list of breakage.

--- End Message ---

Bug#956393: marked as done (rust-unicode-width: uninstallable featureset packages.)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 19:20:55 +0100
with message-id 
and subject line re: rust-unicode-width: uninstallable featureset packages.
has caused the Debian Bug report #956393,
regarding rust-unicode-width: uninstallable featureset packages.
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.)


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

Source: rust-unicode-width
Version: 0.1.7-1
Severity: serious

librust-unicode-width+std-dev and librust-unicode-width+rustc-dep-of-std-dev 
are not installable as they depend on 
librust-rustc-std-workspace-std-1+default-dev which does not seem to exist in 
debian.

This is blocking the rust-unicode-width source package from migrating to 
testing, which in turn is holding up rust-cbindgen from getting back into 
testing.

googling seems to suggest that "rustc-std-workspace-std" is a "hack for the 
compilers own build system" and not something intended for general use.

Should these featureset packages simply be dropped?
--- End Message ---
--- Begin Message ---

Version: 0.1.7-2

After sylvestre invited me into the rust team and after some discussions on 
IRC, I went ahead and removed the broken featureset packages in unstable.

To allow this change to be reverted if desired without a trip through new I 
first uploaded a copy of the package with the broken featureset packages still 
in place to experimental and made sure my unstable uploads had a lower version 
number than the experimental upload.--- End Message ---

Bug#933991: marked as done (src:libxcomposite: depends on empty transitional package x11proto-composite-dev)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 17:49:18 +
with message-id 
and subject line Bug#933991: fixed in libxcomposite 1:0.4.5-1
has caused the Debian Bug report #933991,
regarding src:libxcomposite: depends on empty transitional package 
x11proto-composite-dev
to be marked as done.

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

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


-- 
933991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libxcomposite
Version: 1:0.4.4-2
Severity: normal

Dear Maintainer,

x11proto-composite-dev is a "transitional dummy package" by its
description, and indeed empty, but I can't remove it from my system
because libxcomposite-dev depends on it (and the libxcomposite source
package build-depends on it).  Please consider dropping this dependency.
(BTW, there are similar problems with the other x11proto-*-dev dummy
packages, libx11(-dev) depends on some of them, etc.)
-- 
Thanks,
Feri.
--- End Message ---
--- Begin Message ---
Source: libxcomposite
Source-Version: 1:0.4.5-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libxcomposite 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, 14 Apr 2020 20:23:54 +0300
Source: libxcomposite
Architecture: source
Version: 1:0.4.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 933991
Changes:
 libxcomposite (1:0.4.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Migrate to x11proto-dev. (Closes: #933991)
   * control, watch: Update git urls.
   * control, rules: Migrate to dh 12.
   * Migrate to dbgsym package.
   * control: Bump policy to 4.5.0.
Checksums-Sha1:
 2b8878c4cd79eb36e5bd91eec77d84c125601aca 2067 libxcomposite_0.4.5-1.dsc
 3dc1c67d5cfefeb44934bce1107ba4e77de2d942 386513 libxcomposite_0.4.5.orig.tar.gz
 8e02014c3bc137a56087668957d75d706a013711 7547 libxcomposite_0.4.5-1.diff.gz
 5b691dbc7133a722a73dbddcba201b5e6cc6fc1e 7240 
libxcomposite_0.4.5-1_source.buildinfo
Checksums-Sha256:
 41b93952b43dfac6b0acde3ea9b6330d44fd7c96b6a38eba6d82094b88e436e8 2067 
libxcomposite_0.4.5-1.dsc
 581c7fc0f41a99af38b1c36b9be64bc13ef3f60091cd3f01105bbc7c01617d6c 386513 
libxcomposite_0.4.5.orig.tar.gz
 b5e99d78f5260a7c27ac4c166f981e8c2eab44cff08f9ab64da3ee7150854410 7547 
libxcomposite_0.4.5-1.diff.gz
 26dbe434043d1d23bede13eb1026f89b07248e65fabad09e23b89fe091aaa743 7240 
libxcomposite_0.4.5-1_source.buildinfo
Files:
 b88bf79e88466c79772bbc3272e1f546 2067 x11 optional libxcomposite_0.4.5-1.dsc
 1886cb780c77c6c894c0869a6b7fe1af 386513 x11 optional 
libxcomposite_0.4.5.orig.tar.gz
 464ca14557452bb70e45b14bbe4e1147 7547 x11 optional 
libxcomposite_0.4.5-1.diff.gz
 4fb39d40a7de8f3285f8da68da3e443c 7240 x11 optional 
libxcomposite_0.4.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6V8ccACgkQy3AxZaiJ
hNwXBw/9FKKwnYoc3f82leEY2u4963pcJKngz0N3Nt5GGHXi5sHGtDNImjjWZoXU
YjS3JGECeK3ERpqizNbOfIsIlZ3GepZbg8xpCCMWurvxxIGCKJCC+nI9gq9KKMvO
afnLAUDGjxpg8oxMBBiDLHV/j2ALbEYpjv10mBtcnHNQ4q+9cPQZinPW/jhTQybO
EEQIaQiiERik787FhuxTCb5HmEKUMoLAT64Nhr7Tq56nYao1FwYbFwYDi1Y+hbQI
2DUa3RSxz5Nnh0AfX20iBZzfGr4CuK43O/XutJ34nyXZWpr53Xu+w2bsN2mvktWY
tbOQiTo1Lc66fHaaySBQIcq+HwGNrcbEUVskEDD+iQsdOnajWSR51V9fjNYMyNLu
zK2xLLggwCuBeBblHfgu8doY+tmNFZU92SVxI/ILxc2zaA4kXczQa2xXyHXks8ex
HFaeQLO7zz38bPCM0ltuQVrI01CyV2rH11716XVHjtvly97X1aLCrPKf8PGdpt2a
JyHXLiO0dpsoTUuoLKD0zjUnHHWTgBcNgbbUnvR89tnYGHiAbPEtoG5S02uf0Knq
cdHxqdUH2vzQQzP5/TEDkmwXUFRjBAdOM612BrfuAY4Hw45fD+LhBa8cRHEgolQ/
gtFmpeSVP1FqU14kNhhWRfwQSzJhRBkvDdmhtbxAnFRFwdrMjYQ=
=mBV+
-END PGP SIGNATURE End Message ---

Processed: src:vtkplotter: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 2020.2.0+dfsg1-1
Bug #956727 [src:vtkplotter] src:vtkplotter: fails to migrate to testing for 
too long
Marked as fixed in versions vtkplotter/2020.2.0+dfsg1-1.
Bug #956727 [src:vtkplotter] src:vtkplotter: fails to migrate to testing for 
too long
Marked Bug as done
> block -1 by 953235
Bug #956727 {Done: Paul Gevers } [src:vtkplotter] 
src:vtkplotter: fails to migrate to testing for too long
956727 was not blocked by any bugs.
956727 was not blocking any bugs.
Added blocking bug(s) of 956727: 953235

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

Processed: src:python-cassandra-driver: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.20.2-2
Bug #956726 [src:python-cassandra-driver] src:python-cassandra-driver: fails to 
migrate to testing for too long
Marked as fixed in versions python-cassandra-driver/3.20.2-2.
Bug #956726 [src:python-cassandra-driver] src:python-cassandra-driver: fails to 
migrate to testing for too long
Marked Bug as done

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

Bug#955152: marked as done (git-rebase ignores or squashes GIT_REFLOG_ACTION)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 17:33:45 +
with message-id 
and subject line Bug#955152: fixed in git 1:2.26.0-2
has caused the Debian Bug report #955152,
regarding git-rebase ignores or squashes GIT_REFLOG_ACTION
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.)


-- 
955152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git, dgit
Control: found -1 git/1:2.26.0-1
Control: found -1 dgit/9.10
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of git the autopkgtest of dgit fails in testing
when that autopkgtest is run with the binary packages of git from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
gitfrom testing1:2.26.0-1
dgit   from testing9.10
all others from testingfrom testing

I copied some of the output at the bottom of this report. Unfortunately
I couldn't spot where the real error is reported.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/4693444/log.gz

TEST FAILED
cwd: /tmp/autopkgtest-lxc.i0ld8_lz/downtmp/autopkgtest_tmp/example
funcs: t-report-failure main
lines: 7 0
files: tests/lib
/tmp/autopkgtest-lxc.i0ld8_lz/downtmp/build.QKl/src/tests/tests/gdr-newupstream
gzip: warning: GZIP environment variable is deprecated; use an alias or
script
 81.5%
autopkgtest [12:39:07]: test gdr-newupstream: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.26.0-2
Done: Jonathan Nieder 

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

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

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

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated git package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 10:09:37 -0700
Source: git
Architecture: source
Version: 1:2.26.0-2
Distribution: unstable
Urgency: low
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Closes: 955152
Changes:
 git (1:2.26.0-2) unstable; urgency=low
 .
   * fixes to the (newly default) rebase --merge backend:
 * honor GIT_REFLOG_ACTION (thx Ian Jackson and Elijah Newren;
   closes: #955152).
 * avoid "nothing to do" error when fast-forwarding a branch with
   rebase.abbreviateCommands=true (thx Jan Alexander Steffens and
   Alban Gruin).
   * debian/control: downgrade Recommends by git-all on git-daemon-run
 to Suggests. The git-all package is a "batteries included" full
 installation of Git. Automatically running a daemon is not useful
 to most of its users.
Checksums-Sha1:
 3f0cf513384f43046d694e496debc0cecf247726 2860 git_2.26.0-2.dsc
 9405a8c5005db4c6ec402d7a37b92de25a934673 645988 git_2.26.0-2.debian.tar.xz
 b5749b6bb9545c7720eb6e66447520541531ded1 12103 git_2.26.0-2_amd64.buildinfo
Checksums-Sha256:
 2e1a9233c87aa3925e86f9ba5736fd79c1b226bd8c878381f2cb561bb0db89b6 2860 
git_2.26.0-2.dsc
 8d8e08dabd62f35e0cd4f69c788a5274ae1a083ded0b29010413e2af5b7f427f 645988 
git_2.26.0-2.debian.tar.xz
 f3530545404f4c9cf1ccf7d2abcc55277a64f25e2e5fabf70eaf0509ab11c533 12103 
git_2.26.0-2_amd64.buildinfo
Files:
 5e1bd868422ffb05feb5b9f1305af6e4 2860 vcs optional git_2.26.0-2.dsc
 20e8c8bfb9eecab7401e33db97c9737d 645988 vcs optional git_2.26.0-2.debian.tar.xz
 6a22027a10814e2a349293417e60d8a0 12103 vcs optional 
git_2.26.0-2_amd64.buildinfo

-BEG

Bug#951964: marked as done (gkrellm-tz: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 17:18:30 +
with message-id 
and subject line Bug#951964: fixed in gkrellm-tz 0.8-2
has caused the Debian Bug report #951964,
regarding gkrellm-tz: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is 
deprecated [-Werror=deprecated-declarations]
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Making gkrellm-tz version 0.8
>   CC   list.o
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
>  from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:33,
>  from list.c:34:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is 
> deprecated [-Werror=deprecated-declarations]
>   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
>  from /usr/include/glib-2.0/gobject/gbinding.h:29,
>  from /usr/include/glib-2.0/glib-object.h:23,
>  from /usr/include/glib-2.0/gio/gioenums.h:28,
>  from /usr/include/glib-2.0/gio/giotypes.h:28,
>  from /usr/include/glib-2.0/gio/gio.h:26,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32,
>  from list.c:34:
> /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
>   679 | {
>   | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
>  from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtk.h:126,
>  from list.c:34:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: error: ‘GTimeVal’ is deprecated: 
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>73 |   GTimeVal last_popdown;
>   |   ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from list.c:33:
> /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
>   551 | struct _GTimeVal
>   |^
> cc1: all warnings being treated as errors
> make[2]: *** [Makefile:56: list.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/gkrellm-tz_0.8-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gkrellm-tz package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Apr 2020 12:35:25 +0300
Source: gkrellm-tz
Architecture: source
Version: 0.8-2
D

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 17:04:00 +
with message-id 
and subject line Bug#938285: fixed in python-zipp 1.0.0-2
has caused the Debian Bug report #938285,
regarding python-zipp: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-zipp

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-zipp
Source-Version: 1.0.0-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-zipp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:45:24 -0400
Source: python-zipp
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938285
Changes:
 python-zipp (1.0.0-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938285
Checksums-Sha1:
 f284b381ceb22e53a0f9a5b193a711c97035491c 2258 python-zipp_1.0.0-2.dsc
 3296130e3b65b8b4088c2b9b594f25093b0430cc 2344 python-zipp_1.0.0-2.debian.tar.xz
 fd03b51e9c8bdd82503837e44dc59619625931ef 8052 
python-zipp_1.0.0-2_amd64.buildinfo
Checksums-Sha256:
 4451ee9bbc2268d5bfaf616333612beba2eb2db8b13814334d0b35cfdf019cda 2258 
python-zipp_1.0.0-2.dsc
 28914e5466683f9662d77723229d5c81c9cb31789e9ad1fb74053684b90522d0 2344 
python-zipp_1.0.0-2.debian.tar.xz
 be38c3c5b6e05fcf0b509b7f626a3234b98153a4b74c1e67a52650220ef68ee1 8052 
python-zipp_1.0.0-2_amd64.buildinfo
Files:
 e1dec98400b7c4829b61bdb877d1fee5 2258 p

Bug#937832: marked as done (python-importlib-metadata: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 17:03:54 +
with message-id 
and subject line Bug#937832: fixed in python-importlib-metadata 1.5.0-2
has caused the Debian Bug report #937832,
regarding python-importlib-metadata: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-importlib-metadata
Source-Version: 1.5.0-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-importlib-metadata 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:42:29 -0400
Source: python-importlib-metadata
Architecture: source
Version: 1.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937832
Changes:
 python-importlib-metadata (1.5.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Run tests requiring pyfakefs but only on Python 3 and PyPy.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937832
Checksums-Sha1:
 283945bb14b60664416f503ab9089a0b489e64c1 2523 
python-importlib-metadata_1.5.0-2.dsc
 010dbc9a36a9ed89680df27403b6721b4fd77c2d 3296 
python-importlib-metadata_1.5.0-2.debian.tar.xz
 be20d74ef81c8fd6bc303ad52c79adc126dc4425 8474 
python-importlib-metadata_1.5.0-2_amd64.buildinfo
Checksums-Sha256:
 a787e12447fe92ed3468d4dd53a5bf0fec1b07f1738e8eab19e434f0f38fe026 2523 
python-

Bug#952060: marked as done (libsignon-glib: FTBFS: signon-auth-service.c:72:13: error: G_ADD_PRIVATE [-Werror])

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 16:48:56 +
with message-id 
and subject line Bug#952060: fixed in libsignon-glib 1.12-2.1
has caused the Debian Bug report #952060,
regarding libsignon-glib: FTBFS: signon-auth-service.c:72:13: error: 
G_ADD_PRIVATE [-Werror]
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.)


-- 
952060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsignon-glib
Version: 1.12-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H   -I.. 
> -I. -I.. -I. -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/signond -Wall 
> -Werror -Wno-error=deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2  
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o 
> libsignon_glib_la-signon-auth-service.lo `test -f 'signon-auth-service.c' || 
> echo './'`signon-auth-service.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I.. -I. -I.. -I. -pthread 
> -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/signond -Wall -Werror -Wno-error=deprecated-declarations 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> signon-auth-service.c  -fPIC -DPIC -o 
> .libs/libsignon_glib_la-signon-auth-service.o
> signon-auth-service.c: In function ‘signon_auth_service_init’:
> signon-auth-service.c:72:13: error: G_ADD_PRIVATE [-Werror]
>72 | SignonAuthServicePrivate);
>   | ^  
> signon-auth-service.c: In function ‘signon_auth_service_class_init’:
> signon-auth-service.c:112:5: warning: ‘g_type_class_add_private’ is 
> deprecated [-Wdeprecated-declarations]
>   112 | g_type_class_add_private (object_class, sizeof 
> (SignonAuthServicePrivate));
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
>  from /usr/include/glib-2.0/gobject/gbinding.h:29,
>  from /usr/include/glib-2.0/glib-object.h:23,
>  from signon-auth-service.h:28,
>  from signon-auth-service.c:34:
> /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
>  1308 | void g_type_class_add_private   (gpointer
> g_class,
>   |  ^~~~
> cc1: all warnings being treated as errors
> make[4]: *** [Makefile:654: libsignon_glib_la-signon-auth-service.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/libsignon-glib_1.12-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libsignon-glib
Source-Version: 1.12-2.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libsignon-glib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 07 Apr 2020 10:42:59 +0300
Source: libsignon-glib
Architecture: source
Version: 1.12-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Adrian Bunk 
Closes: 952060
Changes:
 libsignon-glib (1

Bug#956715: marked as done (openrc FTCBFS: strips with the wrong strip)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 16:49:11 +
with message-id 
and subject line Bug#956715: fixed in openrc 0.40.3-2
has caused the Debian Bug report #956715,
regarding openrc FTCBFS: strips with the wrong strip
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.)


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

openrc fails to cross build from source, because it strips lsb2rcconf
using the build architecture strip. It does so during dh_auto_install,
so it happens to alos break DEB_BUILD_OPTIONS=nostrip as well as
generation of a -dbgsym package. It is best to leave stripping up to
dh_strip. Please consider applying the attached patch.

Helmut
diff --minimal -Nru openrc-0.40.3/debian/changelog 
openrc-0.40.3/debian/changelog
--- openrc-0.40.3/debian/changelog  2019-02-02 16:41:07.0 +0100
+++ openrc-0.40.3/debian/changelog  2020-04-14 17:59:29.0 +0200
@@ -1,3 +1,10 @@
+openrc (0.40.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Defer stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 14 Apr 2020 17:59:29 +0200
+
 openrc (0.40.3-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru openrc-0.40.3/debian/rules openrc-0.40.3/debian/rules
--- openrc-0.40.3/debian/rules  2019-02-02 16:41:07.0 +0100
+++ openrc-0.40.3/debian/rules  2020-04-14 17:59:28.0 +0200
@@ -21,6 +21,7 @@
 export SHLIBDIR = /lib/$(DEB_HOST_MULTIARCH)
 export LIBNAME = lib
 export LIBEXECDIR = /lib/rc
+export STRIP_BINARY = no
 
 ifeq (linux,$(DEB_HOST_ARCH_OS))
 export MKAUDIT = yes
--- End Message ---
--- Begin Message ---
Source: openrc
Source-Version: 0.40.3-2
Done: Adam Borowski 

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated openrc 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, 14 Apr 2020 18:17:58 +0200
Source: openrc
Architecture: source
Version: 0.40.3-2
Distribution: unstable
Urgency: medium
Maintainer: OpenRC Debian Maintainers 
Changed-By: Adam Borowski 
Closes: 956715
Changes:
 openrc (0.40.3-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Helmut Grohne ]
   * Defer stripping to dh_strip. (Closes: #956715)
 .
   [ Adam Borowski ]
   * Drop myself from uploaders.
   * Drop Pre-Dep on pre-Stretch init-system-helpers.
Checksums-Sha1:
 a95f4f0dec89072ebf5ef75129788cd1ce57827e 2244 openrc_0.40.3-2.dsc
 df7608cc92fefd21482dc145e77bc89c5dbe867d 26624 openrc_0.40.3-2.debian.tar.xz
 3925a288097dec4a90b258b7978bbe5f18e73fa3 5987 openrc_0.40.3-2_source.buildinfo
Checksums-Sha256:
 959413ee94646642f61d144135ba6cc752dc00223bc92c6052d09e61f92778e2 2244 
openrc_0.40.3-2.dsc
 d2c379dcb9db7a81e831429038bc4d403bc4d8a90d6cec3d3dae1ddc92183b74 26624 
openrc_0.40.3-2.debian.tar.xz
 5cc14a799f0aa8119be0411b08d46586163ab13422d3bc92024cfce7dac8987a 5987 
openrc_0.40.3-2_source.buildinfo
Files:
 02a84ae5f124d3f718d7329fd4693f38 2244 admin optional openrc_0.40.3-2.dsc
 58ff9992a0f2fddb1a8e069e7ad84592 26624 admin optional 
openrc_0.40.3-2.debian.tar.xz
 045b48372a16eb3ab89fcbc09f7a48e5 5987 admin optional 
openrc_0.40.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6V4kkUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH6ieA/+LpNxaP9LhBx/hsa02z6Xv61qrTlf
V2rYjqb0IiooxtV6CzQOlkMp8yOurbgWtm2jAXCttYfpoDor6sznbXYpFcCox4M/
pybeSoU8fNDiPZKn9TkQy3zc8ZvJFq8Z/u1L/2YWUKsurGFpDaPg/S89RG3vfwku
JIdrFGC0fh3dU3Sha8itqv9ORI8kdNe9NN/ngmsShjFxiQGyBPejIze6+KaUi+Fv
I3h2V7jfX9byQdnBD86FBFmBVIsP+MDudOjW9gvoTGwynyKAUd0NgMFEw4J7d4hs
aFtIz2OY7Zt5MyHIQSteWK9iT3yg6NMyS9IxOZT3X4wdNIfz/jwNZ4k7hGRIA2xX
QbTnHld9j1VtNFQp2H326YPybQq7Bv+DnDy2z4mmjRjR/Us3YvPxGO/Y7GvB+4fO
rzBaYm3T7XilrjHgbDaip7YsgD0HYNgRNBeUxbOl3I5/jJ5Q90v08xpXplBaEK4z
6IjmeiQJDIvXPFhpTkln/MG0HooVatkB/bee6L0u6QOB3pm6gbrgm+yvzmxY

Bug#930674: marked as done (automatically generated menus prevent some applications from running)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 16:38:41 +
with message-id 
and subject line Bug#930674: fixed in wmaker 0.95.9-1
has caused the Debian Bug report #930674,
regarding automatically generated menus prevent some applications from running
to be marked as done.

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

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


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

Package: wmaker
Version: 0.95.8-3

automatically generated menus prevent some applications from running,
e.g. libreoffice will not run complaining that file "%U does not exist"
and others will open an empty file, e.g. %F.

Looking at the code the XDG menu parser does not strip "%X" arguments
from Exec entries, I attached a sample patch as a workaround to this
problem.
Index: wmaker-0.95.8/util/wmmenugen_parse_xdg.c
===
--- wmaker-0.95.8.orig/util/wmmenugen_parse_xdg.c
+++ wmaker-0.95.8/util/wmmenugen_parse_xdg.c
@@ -297,7 +297,7 @@ static void getKey(char **target, const
 static void getStringValue(char **target, const char *line)
 {
 	const char *p;
-	int kstart;
+	int kstart, kend;

 	p = line;
 	kstart = 0;
@@ -311,7 +311,15 @@ static void getStringValue(char **target
 	while (*(p + kstart) && isspace(*(p + kstart)))
 		kstart++;

-	*target = wstrdup(p + kstart);
+	/* skip until first % */
+	kend = kstart + 1;
+	while (*(p + kend) && *(p + kend) != '%')
+		kend++;
+
+	/* strip heading white space if any */
+	if(isspace(*(p + kend -1))) kend--;
+
+	*target = wstrndup(p + kstart, kend - kstart);
 }

 /* get a localized string value from line. allocates target, which must be wfreed later.
--- End Message ---
--- Begin Message ---
Source: wmaker
Source-Version: 0.95.9-1
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated wmaker 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, 14 Apr 2020 18:06:26 +0200
Source: wmaker
Architecture: source
Version: 0.95.9-1
Distribution: experimental
Urgency: low
Maintainer: Debian Window Maker Team 
Changed-By: Andreas Metzler 
Closes: 922284 930674
Changes:
 wmaker (0.95.9-1) experimental; urgency=low
 .
   [ Doug Torrance ]
   * New upstream release.
 - No longer sets GNUSTEP_USER_ROOT environment variable
   (Closes: #922284).
 - Prefers TryExec to Exec when generating menu entries from XDG desktop
   files (closes: #930674).
 - Drop patches previously pulled from upstream GIT:
   10_util-fix-parsing-of-XDG-menus-with-multiple-groups.patch
   11_XDG-menu-categories.patch 12_reference-proplist-menus.patch
   60_fix_pkg-config_variable_typo.patch
 - Unfuzz 75_WPrefs_to_bindir_when_gnustedir_is_set.diff
 - 54_Debian_wmmacros.diff dropped, main functionality included upstream.
   * debian/compat
 - Remove file; compatibility level now handled by debhelper-compat
   package.
   * debian/control
 - Bump Standards-Version to 4.5.0.
 - Switch Build-Depends on debhelper to debhelper-compat for
   compatibility level 12.
   * debian/lib*.symbols
 - Add Build-Depends-Package fields.
   * debian/libwings3.symbols
 - Add new WINGs symbols.
   * debian/patches/10_support_imagemagick6.diff
 - New patch; restore support for ImageMagick v6, as v7 is not in
   Debian yet.
   * debian/patches/.keepme
 - Remove unnecessary file; was causing
   patch-file-present-but-not-mentioned-in-series Lintian warning.
   * debian/README.Debian
 - Fix typo.
   * debian/rules
 - Remove replacement of #wmdatadir# to $(WMSHAREDIR) in some menu
   files; this is now done by upstream during build.
 - Install README's from WindowMaker directory correctly. Avoids
   package-contains-documentation-outside-usr-share-doc Lintian
   warning.
   * debian/wmaker-common.docs
 - Use wildcard to catch all the README's that have been renamed
   

Bug#922284: marked as done (wmaker-common: Should not set GNUSTEP_USER_ROOT; unable to build GNUstep software)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 16:38:41 +
with message-id 
and subject line Bug#922284: fixed in wmaker 0.95.9-1
has caused the Debian Bug report #922284,
regarding wmaker-common: Should not set GNUSTEP_USER_ROOT; unable to build 
GNUstep software
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.)


-- 
922284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wmaker-common
Version: 0.95.8-3
Severity: important
File: /usr/bin/wmaker
Control: affects -1 gnustep

As evident from the prefix, GNUSTEP_USER_ROOT is a GNUstep variable and
Window Maker should not set it.  Furthemore, it has been deprecated for
12 years already.  As of gnustep-make/2.7.0-4 the GNUstep build system
is configured in strict v2 mode which makes it impossible to compile
GNUstep software.  In a terminal started from a Window Maker session:

yavor@aneto:/tmp/gorm.app-1.2.24$ make
This is gnustep-make 2.7.0. Type 'make print-gnustep-make-help' for help.
Running in gnustep-make version 2 strict mode.
rm -f InterfaceBuilder; \
ln -s GormLib InterfaceBuilder
/usr/share/GNUstep/Makefiles/config-noarch.make:121: *** GNUSTEP_USER_ROOT is 
obsolete.  Stop.

It is also impossible to build gnustep-make from pristine upstream
source:

yavor@aneto:/tmp$ wget -q 
ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.7.0.tar.gz
yavor@aneto:/tmp$ tar xzf gnustep-make-2.7.0.tar.gz
yavor@aneto:/tmp$ cd gnustep-make-2.7.0/
yavor@aneto:/tmp/gnustep-make-2.7.0$ ./configure
...
yavor@aneto:/tmp/gnustep-make-2.7.0$ make
config-noarch.make:121: *** GNUSTEP_USER_ROOT is obsolete.  Stop.

Note that the majority of GNUstep users use Window Maker as their window
manager and many of them build GNUstep software from source, mostly
because of the GNUstep Objective-C runtime which depends on Clang
(Debian packages use GCC and the GCC/GNU runtime).

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

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

wmaker-common depends on no packages.

wmaker-common recommends no packages.

Versions of packages wmaker-common suggests:
ii  wmaker  0.95.8-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wmaker
Source-Version: 0.95.9-1
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated wmaker 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, 14 Apr 2020 18:06:26 +0200
Source: wmaker
Architecture: source
Version: 0.95.9-1
Distribution: experimental
Urgency: low
Maintainer: Debian Window Maker Team 
Changed-By: Andreas Metzler 
Closes: 922284 930674
Changes:
 wmaker (0.95.9-1) experimental; urgency=low
 .
   [ Doug Torrance ]
   * New upstream release.
 - No longer sets GNUSTEP_USER_ROOT environment variable
   (Closes: #922284).
 - Prefers TryExec to Exec when generating menu entries from XDG desktop
   files (closes: #930674).
 - Drop patches previously pulled from upstream GIT:
   10_util-fix-parsing-of-XDG-menus-with-multiple-groups.patch
   11_XDG-menu-categories.patch 12_reference-proplist-menus.patch
   60_fix_pkg-config_variable_typo.patch
 - Unfuzz 75_WPrefs_to_bindir_when_gnustedir_is_set.diff
 - 54_Debian_wmmacros.diff dropped, main functionality included upstream.
   * debian/compat
 - Remove file; compatibility level now handled by debhelper-compat
   package.
   * debian/control
 - Bump Standards-Version to 4.5.0.
 - Switch Build-Depends on debhelper to debhelper-compat for
   compatibi

Bug#954923: marked as done (python-azure-storage: move python3-azure-storage to src:python-azure and retire)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 15:05:20 +
with message-id 
and subject line Bug#956706: Removed package(s) from unstable
has caused the Debian Bug report #954923,
regarding python-azure-storage: move python3-azure-storage to src:python-azure 
and retire
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.)


-- 
954923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-azure
Version: 20200130+git-2
Severity: normal
Tags: patch
X-Debbugs-CC: ol...@debian.org antoine.romain.dum...@gmail.com

As discussed in 
https://salsa.debian.org/python-team/modules/python-azure/-/merge_requests/3#note_144855
and https://github.com/Azure/azure-storage-python/issues/655 it seems
most of the new work on python-azure-storage is happening in python-
azure, so we'd like to move the binary package over and build it from
python-azure.

I've done the work and will send an MR out soon.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 20181109+git-2+rm

Dear submitter,

as the package python-azure-storage 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/956706

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#926289: marked as done (python-azure-storage: New upstream version)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 15:05:20 +
with message-id 
and subject line Bug#956706: Removed package(s) from unstable
has caused the Debian Bug report #926289,
regarding python-azure-storage: New upstream version
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.)


-- 
926289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-azure-storage
Version: 20181109+git-1
Severity: wishlist

Dear Maintainer,

Upstream continues to move ever onward, as per 
https://github.com/Azure/azure-storage-python/releases

This is implacting me as 'duplicity' package seems to need a newer
version of python-azure-storage to function

Thanks



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

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

Versions of packages python-azure-storage depends on:
ii  python 2.7.15-3
ii  python-azure   20181112+git-2
ii  python-concurrent.futures  3.2.0-2
ii  python-cryptography2.6.1-3
ii  python-dateutil2.7.3-3
ii  python-requests2.21.0-1

python-azure-storage recommends no packages.

python-azure-storage suggests no packages.

-- no debconf information


Psst! It's possible that this email contains information that is on the super 
secret side of confidential. So if you received it accidentally, let the sender 
know straight away and delete it (and the email you sent them). Also, we should 
let you know that any emails that come and go through Winc™ might be 
scanned, stored or read by Winc™ at its discretion. If you've got a 
question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 
7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it 
sends, but we can't promise that it will be error free. So, please don't hold 
it against us.
--- End Message ---
--- Begin Message ---
Version: 20181109+git-2+rm

Dear submitter,

as the package python-azure-storage 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/956706

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#956669: marked as done (RM: rheolef [mipsel mips64el] -- RoQA; build-deps not available)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 15:04:17 +
with message-id 
and subject line Bug#956669: Removed package(s) from unstable
has caused the Debian Bug report #956669,
regarding RM: rheolef [mipsel mips64el] -- RoQA; build-deps not available
to be marked as done.

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

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


-- 
956669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-debbugs-cc: debian-science-maintain...@lists.alioth.debian.org

This removal would allow rheolef to migrate to testing. rheolef/7.1-1
build-depends on paraview which is not available on mips and mips64el.

Thanks,

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

librheolef-dev |  7.0-3 | mips64el, mipsel
librheolef1 |  7.0-3 | mips64el, mipsel
   rheolef |  7.0-3 | mips64el, mipsel

--- Reason ---
RoQA; build-deps not available
--

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

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

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

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

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

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

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#956670: marked as done (RM: slic3r-prusa [armel] -- RoQA; build-deps not available)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 15:04:44 +
with message-id 
and subject line Bug#956670: Removed package(s) from unstable
has caused the Debian Bug report #956670,
regarding RM: slic3r-prusa [armel] -- RoQA; build-deps not available
to be marked as done.

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

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


-- 
956670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-debbugs-cc: 3dprinter-gene...@lists.alioth.debian.org

This removal would take care of one testing-migration-blocking issue
with slic3r-prusa.

slic3r-prusa/2.2.0+dfsg1-1 build-depends on libcgal-dev which is not
available on armel (#838496).

Thanks,

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

prusa-slicer | 2.1.1+dfsg-2 | armel

--- Reason ---
RoQA; build-deps not available
--

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

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

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

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

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

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

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#956706: marked as done (RM: python-azure-storage -- ROM; binary package taken over by python-azure)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 15:05:13 +
with message-id 
and subject line Bug#956706: Removed package(s) from unstable
has caused the Debian Bug report #956706,
regarding RM: python-azure-storage -- ROM; binary package taken over by 
python-azure
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.)


-- 
956706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: python-modules-t...@lists.alioth.debian.org

Dear FTP Team,

As discussed by members of the Python Modules Team in:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954922
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954923
https://salsa.debian.org/python-team/modules/python-azure/-/merge_requests/3#note_144855
https://github.com/Azure/azure-storage-python/issues/655

We want to move the binary python3-azure-storage package from
src:python-azure-storage to src:python-azure.
The latter's version 20200130+git-3 is newer than the former's
20181109+git-2, so we will do a simple upload, no epochs required.

I believe an RM request is still necessary for the old source package,
but I might be wrong - filing one just in case.

Thanks!

-- 
Kind regards,
Luca Boccassi


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

python-azure-storage | 20181109+git-2 | source
python3-azure-storage | 20181109+git-2 | all

--- Reason ---
ROM; binary package taken over by python-azure
--

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

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

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

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

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

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#940057: marked as done (qemu 4.1: qxl driver does not resize display / received empty monitor config)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:43:42 +
with message-id 
and subject line Bug#940057: fixed in spice 0.14.3-1
has caused the Debian Bug report #940057,
regarding qemu 4.1: qxl driver does not resize display / received empty monitor 
config
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.)


-- 
940057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu
Version: 1:4.1-1+b1
Severity: normal

QEMU 4.1 has a problem when using the vga qxl driver.

$ qemu-system-x86_64 -machine accel=kvm \
-m 1024 -cdrom grml64-full_2018.12.iso -vga qxl \
-spice port=,disable-ticketing



Connect with the Spice viewer and start Grml in Graphical Mode.

$ remote-viewer spice://127.0.0.1: --spice-debug

Now resize with "xrandr -s 1680x1050".

### remote-viewer debug output ###

(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-channel.c:2926 test 
cap 0 in 0x1: yes
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-util.c:270 
spice_make_scancode:  scancode 28
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.601: spice-util.c:270 
spice_make_scancode: release scancode 28
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-cursor.c:542 
cursor-4:0: cursor_handle_reset, init_done: 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-display.c:1951 
display-2:0: 0: FIXME primary destroy, but is display really disabled?
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: spice-widget.c:3046 0:0 
cursor_reset
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: channel-cursor.c:542 
cursor-4:0: cursor_handle_reset, init_done: 0
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.610: spice-widget.c:1926 0:0 
focus_out_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1860 0:0 
leave_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:945 0:0 
ungrab keyboard
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1860 0:0 
leave_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:3046 0:0 
cursor_reset
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:496 0:0 
grab_broken (implicit: 0, keyboard: 1)
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:498 0:0 
grab_broken (SpiceDisplay::GdkWindow 0x560258aaec60, event->grab_window: (nil))
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.611: spice-widget.c:1536 0:0 
release_keys
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-display.c:1909 
surface flags: 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-display.c:947 
display-2:0: Create primary canvas
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: channel-cursor.c:387 
cursor-4:0: set_cursor: flags 1, size 0
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:300 0:0 
update monitor area
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:2573 0:0 
update area +0+0 1024x768
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:2599 0:0 
primary: 1680x1050
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:1300 0:0 
recalc geom monitor: 0:0, guest +0+0:1024x768, window 1024x768, zoom 1
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.640: spice-widget.c:1890 0:0 
focus_in_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.641: spice-channel.c:2926 test 
cap 1 in 0x1052: yes
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.653: spice-widget.c:1845 0:0 
enter_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.653: spice-widget.c:867 0:0 grab 
keyboard
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.654: spice-widget.c:1845 0:0 
enter_event
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.657: channel-display.c:1123 
display-2:0: display_handle_mark
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.660: spice-widget.c:2852 0:0 
widget mark: 1, display 0x560258d60680
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.661: decode-glz.c:352 
decode_header: 1680x1050, id 17193, ref 17187
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.670: channel-display.c:1975 
display-2:0: received empty monitor config
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.670: decode-glz.c:352 
decode_header: 1680x1050, id 17194, ref 17189
(remote-viewer:27616): GSpice-DEBUG: 21:43:36.684: decode-glz.c:352 
decode_header: 1680x1050, id 17195, ref 17192

### remote-viewer debug output ###



If you disconnect the Spice viewer and try to reconnect the viewer only shows 
the text "Connected to graphic server".

### remote-viewer debug output ###

(remote-viewer:27738): GSpice-DEBUG: 21:51:40.422

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:43:42 +
with message-id 
and subject line Bug#954629: fixed in spice 0.14.3-1
has caused the Debian Bug report #954629,
regarding spice: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned 
exit code 2
to be marked as done.

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

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


-- 
954629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice
Version: 0.14.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[7]: Entering directory '/<>/server/tests'
> PASS: test-codecs-parsing
> PASS: test-options
> PASS: test-stream
> PASS: test-agent-msg-filter
> PASS: test-stat-file
> PASS: test-stat
> PASS: test-loop
> PASS: test-vdagent
> ../../test-driver: line 107: 16271 Trace/breakpoint trap   "$@" > $log_file 
> 2>&1
> PASS: test-fail-on-null-core-interface
> FAIL: test-leaks
> PASS: test-empty-success
> PASS: test-record
> PASS: test-stream-device
> PASS: test-channel
> PASS: test-qxl-parsing
> PASS: test-sasl
> ===
>spice 0.14.2: server/tests/test-suite.log
> ===
> 
> # TOTAL: 16
> # PASS:  15
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-leaks
> 
> 
> # random seed: R02Sfc2c3f661a60f8251bd9cee289ff9745
> 1..4
> # Start of server tests
> # Spice-DEBUG: reds.c:3548:do_spice_init: starting 0.14.2
> # Spice-DEBUG: char-device.c:693:red_char_device_reset_dev_instance: sin 
> (nil), char device 0x55cd793c6110
> # Spice-DEBUG: reds.c:2705:reds_init_socket: bound to 0.0.0.0:5922
> # Spice-DEBUG: reds.c:2941:reds_init_ssl: Loaded certificates from 
> /<>/server/tests/pki/server-cert.pem
> # Spice-DEBUG: reds.c:2954:reds_init_ssl: Using private key from 
> /<>/server/tests/pki/server-key.pem
> # Spice-DEBUG: reds.c:2963:reds_init_ssl: Loaded CA certificates from 
> /<>/server/tests/pki/ca-cert.pem
> # Spice-DEBUG: main:0 (0x55cd793ef880): thread_id 0x7f1ffb7849c0
> # Spice-DEBUG: inputs:0 (0x55cd793f0890): thread_id 0x7f1ffb7849c0
> 
> (./test-leaks:16271): GLib-CRITICAL **: 03:15:22.056: Did not see expected 
> message Spice-WARNING **: *SSL_accept failed*
> Bail out! Spice-FATAL-WARNING: error:14095126:SSL 
> routines:ssl3_read_n:unexpected eof while reading
> 
> (./test-leaks:16271): Spice-WARNING **: 03:15:22.056: error:14095126:SSL 
> routines:ssl3_read_n:unexpected eof while reading
> FAIL test-leaks (exit status: 133)
> 
> 
> Testsuite summary for spice 0.14.2
> 
> # TOTAL: 16
> # PASS:  15
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See server/tests/test-suite.log
> Please report to spice-de...@lists.freedesktop.org
> 
> make[7]: *** [Makefile:1340: test-suite.log] Error 1
> make[7]: Leaving directory '/<>/server/tests'
> make[6]: *** [Makefile:1448: check-TESTS] Error 2
> make[6]: Leaving directory '/<>/server/tests'
> make[5]: *** [Makefile:1634: check-am] Error 2
> make[5]: Leaving directory '/<>/server/tests'
> make[4]: *** [Makefile:882: check-recursive] Error 1
> make[4]: Leaving directory '/<>/server'
> make[3]: *** [Makefile:1034: check] Error 2
> make[3]: Leaving directory '/<>/server'
> make[2]: *** [Makefile:537: check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> make[1]: *** [Makefile:831: check] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/spice_0.14.2-4_unstable.log

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

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

We believe that the bug you reported is fixed in t

Bug#938809: marked as done (wcwidth: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:43:47 +
with message-id 
and subject line Bug#938809: fixed in wcwidth 0.1.8+dfsg1-5
has caused the Debian Bug report #938809,
regarding wcwidth: 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.)


-- 
938809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wcwidth
Version: 0.1.7+dfsg1-6
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:wcwidth

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: wcwidth
Source-Version: 0.1.8+dfsg1-5
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated wcwidth package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 09:58:17 -0400
Source: wcwidth
Architecture: source
Version: 0.1.8+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938809
Changes:
 wcwidth (0.1.8+dfsg1-5) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938809
Checksums-Sha1:
 ff5c9605d711557cea0033cace26b640de6de79f 2181 wcwidth_0.1.8+dfsg1-5.dsc
 142b01f149891ed86519c2f3aae152955bb208ec 3748 
wcwidth_0.1.8+dfsg1-5.debian.tar.xz
 a9cfdd7b9c5006cd39df0dcfdf82056215d434e7 8691 
wcwidth_0.1.8+dfsg1-5_amd64.buildinfo
Checksums-Sha256:
 e0fc77e3cc5700059dbb328e2d5f9ab12d41ae468033250a3c811645d9c6ad19 2181 
wcwidth_0.1.8+dfsg1-5.dsc
 19fe269270a4472d68c80bfdf9629c9299ca2d9f2e63b08bc5747cda82ce9797 3748 
wcwidth_0.1.8+dfsg1-5.debian.tar.xz
 611eca04be68ca24e5d2b796794ca4d2997e2c7602f7ac28a6bd22f0e5055c90 8691 
wcwidth_0.1.8+dfsg1-5_amd64.buildinfo
Files:
 c8b438e963f58ba394ddd8fe1c59bf3f

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:39:39 +
with message-id 
and subject line Bug#937781: fixed in python-genty 1.3.0-3
has caused the Debian Bug report #937781,
regarding python-genty: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-genty

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-genty
Source-Version: 1.3.0-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-genty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 09:56:00 -0400
Source: python-genty
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937781
Changes:
 python-genty (1.3.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937781
Checksums-Sha1:
 1ad700e78ad1082ac3a960a2e6c381427488fdd0 2068 python-genty_1.3.0-3.dsc
 7d9e4b1da31a136c47e7ac91a0204e13cefbb35f 22751 python-genty_1.3.0.orig.tar.gz
 eeda0909feeb8e03ab87c5d5524695474132f378 1892 
python-genty_1.3.0-3.debian.tar.xz
 66a62127743101a34b23c014e0019e28ef32bef3 6516 
python-genty_1.3.0-3_source.buildinfo
Checksums-Sha256:
 14182486663df109152ed2c08d297dcebb35b113ae901fb15ebaa0e1c6d72664 2068 
python-genty_1.3.0-3.dsc
 8c480cedf90070160584b6bec1a47a36d4d1c078b9ed24b7afdd21259671fdd3 22751 
python-genty_1.

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:39:45 +
with message-id 
and subject line Bug#937926: fixed in python-mock 3.0.5-2
has caused the Debian Bug report #937926,
regarding python-mock: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-mock
Source-Version: 3.0.5-2
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-mock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 09:44:42 -0400
Source: python-mock
Architecture: source
Version: 3.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937926
Changes:
 python-mock (3.0.5-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937926
Checksums-Sha1:
 d534f2ff3b3edd65c7002cf173a282f70aa0a881 2254 python-mock_3.0.5-2.dsc
 cda918734ea2fb0e673923f59b76b5ae8b54dad0 67887 python-mock_3.0.5.orig.tar.gz
 36d8ef84fb8cb86eb079955db9db3319c4704961 5876 python-mock_3.0.5-2.debian.tar.xz
 d8a0eedaf7af36d1537bcb7691b279fabff16e06 7414 
python-mock_3.0.5-2_source.buildinfo
Checksums-Sha256:
 a2b355fe6df5d99526c02d6ab17501b3af31677647a22d7982cfd4047a68bc35 2254 
python-mock_3.0.5-2.dsc
 ff286cec703de8770f735269575ecb7d1c937b8851eba8de94d800df084e627c 67887 
python-mock_3.0.5.orig.tar.gz

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:39:51 +
with message-id 
and subject line Bug#938032: fixed in python-pluggy 0.13.0-4
has caused the Debian Bug report #938032,
regarding python-pluggy: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-pluggy
Source-Version: 0.13.0-4
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-pluggy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 09:48:09 -0400
Source: python-pluggy
Architecture: source
Version: 0.13.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938032
Changes:
 python-pluggy (0.13.0-4) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938032
Checksums-Sha1:
 13fdbc5fc5e3dab4b328fefe0da2e221ad7d953e 2276 python-pluggy_0.13.0-4.dsc
 b1a581fcc8736e87b8a7fbcfc21157a447b266ab 2696 
python-pluggy_0.13.0-4.debian.tar.xz
 cb858a26f50c315911df92352d8eb18054eb3031 8725 
python-pluggy_0.13.0-4_amd64.buildinfo
Checksums-Sha256:
 bb3112e2c5cfa127ce4fc8e27396e75dac217dd34aef7295d8e025a853a9413b 2276 
python-pluggy_0.13.0-4.dsc
 d42c77b16d9b53c7c82c81f19f2c96ad72c3a1b86f014c140ce1c835e662fbd9 2696 
python-pluggy_0.13.0-4.debian.tar.xz
 32639ba93a579b711f4d8cd404024de9f081c3a59361deac12f0ecd08c508066 8725 
python-pluggy_0.13.0-4_amd64.buildinfo
Files

Bug#954922: marked as done (python-azure: take over python3-azure-storage package from src:python-azure-storage)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:39:32 +
with message-id 
and subject line Bug#954922: fixed in python-azure 20200130+git-3
has caused the Debian Bug report #954922,
regarding python-azure: take over python3-azure-storage package from 
src:python-azure-storage
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.)


-- 
954922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-azure
Version: 20200130+git-2
Severity: normal
Tags: patch
X-Debbugs-CC: ol...@debian.org antoine.romain.dum...@gmail.com

As discussed in 
https://salsa.debian.org/python-team/modules/python-azure/-/merge_requests/3#note_144855
and https://github.com/Azure/azure-storage-python/issues/655 it seems
most of the new work on python-azure-storage is happening in python-
azure, so we'd like to move the binary package over and build it from
python-azure.

I've done the work and will send an MR out soon.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: python-azure
Source-Version: 20200130+git-3
Done: Luca Boccassi 

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

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

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated python-azure 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, 14 Apr 2020 14:51:28 +0100
Source: python-azure
Architecture: source
Version: 20200130+git-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Luca Boccassi 
Closes: 954922
Changes:
 python-azure (20200130+git-3) unstable; urgency=medium
 .
   * Sort modules when acting on them in d/rules, and use LC_ALL=C when
 sorting pydist
   * Add 0002-docs-repro.patch and build-depend on python3-doc for
 reproducibility
   * autopkgtest: remove patch and copy root conftest.py
   * Update d/copyright paths for new source layout
   * Bump debhelper-compat to 12
   * Take over python3-azure-storage from src:python-azure-storage (Closes:
 #954922)
   * Override Lintian warning intra-source-package-circular-dependency
Checksums-Sha1:
 b7711a24568372d2f943ce35f65e3f60fdf61d97 2525 python-azure_20200130+git-3.dsc
 5cbedd2203b1670ed9b907552fe0e8a5add20a91 8988 
python-azure_20200130+git-3.debian.tar.xz
 758c4feecc829043885e03a18529aa8a8c2579af 8159 
python-azure_20200130+git-3_source.buildinfo
Checksums-Sha256:
 33adb3455472ea83c2fc84b764aaf64896232cfd343bb1a1e79bb4d1c0f678c3 2525 
python-azure_20200130+git-3.dsc
 06d2b3ca88fbc3d8223e692223df5be7c8efdd908e763d9654e8051a8db7f0d9 8988 
python-azure_20200130+git-3.debian.tar.xz
 ccea22fe854021638367208f1d2b6266d3ba7d5a80e74915102757e91abb6a73 8159 
python-azure_20200130+git-3_source.buildinfo
Files:
 117dffb8dee548dc746169fe58d7cff0 2525 python optional 
python-azure_20200130+git-3.dsc
 af756ab825c9d7e72b831f6463abc30d 8988 python optional 
python-azure_20200130+git-3.debian.tar.xz
 49effed77e3a26a66496c1331559ae07 8159 python optional 
python-azure_20200130+git-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl6VwdoRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQSylmgFB4UWKqzQf9GBTlXdEpuKddQ8LIo+09rYiVannPZszh
SVnYKQoDSBOncCN0Q6nqbu/eRv+2wqaJcdeQgqzbesehWVLw6nWdVKpAV1VtH2xw
IPm72NlkaRtgQpmfgQMrj7QavortY4gCnM7p3PoaRnElA+FcxtQio2/SYIcUCJYe
cA1VljqdLUN6pWGgSI4g26VZgRUKkquW23u3Rb4eH8u8kXzZfGJ637N40o23PxmM
IDMyIQoVn3IjML4RoJAFEP/f1XkHdZpSI8qNeAvwjlcxkX8pO2LF6s5dy0lel9D9
ip+jFT6E/zRGrJ7S/jB06YuziZp/jIAzUHslGGKXHv8VsrPKjWTWzA==
=cdEU
-END PGP SIGNATURE End Message ---

Bug#937275: marked as done (pexpect: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:38:10 +
with message-id 
and subject line Bug#937275: fixed in pexpect 4.6.0-3
has caused the Debian Bug report #937275,
regarding pexpect: 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.)


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

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: pexpect
Source-Version: 4.6.0-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pexpect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 09:52:58 -0400
Source: pexpect
Architecture: source
Version: 4.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937275
Changes:
 pexpect (4.6.0-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937275
Checksums-Sha1:
 3597693903d3687254704e0db5af56f54be28c22 2114 pexpect_4.6.0-3.dsc
 3d79bb7de5436cd0a8417a6249c765595a33abcf 148966 pexpect_4.6.0.orig.tar.gz
 034471cbeb8734313a9b78ea6e0dde39438169f8 5108 pexpect_4.6.0-3.debian.tar.xz
 cbc6e73368b70e81cbc931a62d98f27c460dde6f 7664 pexpect_4.6.0-3_source.buildinfo
Checksums-Sha256:
 c23358220bcee799877cc2bfcdb087b32e96e148d573e9ca5ddf52d430aebca7 2114 
pexpect_4.6.0-3.dsc
 2a8e88259839571d1251d278476f3eec5db26deb73a70be5ed5dc5435e418aba 148966 
pexpect_4.6.0.orig.tar.gz
 47e3f064f240fc94fc21a447afd80cb5ad6dfd6eb27de05a138176a17082eda9 5108 
pexpect_4.6.0-3.debian.tar.xz
 68d3d3077d1dded90c9fc23cc988600ea40

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 14:38:19 +
with message-id 
and subject line Bug#937586: fixed in python-atomicwrites 1.1.5-4
has caused the Debian Bug report #937586,
regarding python-atomicwrites: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-atomicwrites

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-atomicwrites
Source-Version: 1.1.5-4
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-atomicwrites package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 10:01:02 -0400
Source: python-atomicwrites
Architecture: source
Version: 1.1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937586
Changes:
 python-atomicwrites (1.1.5-4) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937586
Checksums-Sha1:
 9ce6480fb5dee7af4f5bb020adc6d006bb47170b 2280 python-atomicwrites_1.1.5-4.dsc
 9d1929c098b9a9b52c28ec0cbef8dd7ce0eb0cd6 2872 
python-atomicwrites_1.1.5-4.debian.tar.xz
 16de84a9cdefbb2bb1719845bc4dff9456f5fdb1 8691 
python-atomicwrites_1.1.5-4_amd64.buildinfo
Checksums-Sha256:
 e01c87e794ff83e64ec60b8796cb6f6ae189890babaa81f8d1bb8d586d8284f5 2280 
python-atomicwrites_1.1.5-4.dsc
 f25c3b3e0807ca8d18b8be5d777fa08a1bdd962d9ad7553644301925ad18c1f9 2872 
python-atomicwrites_1.1.5-4.debian.tar.xz
 b6277ba83436ce8af00e99102ee08615720f9eab6

Bug#956665: marked as done (libdrm2: Update broke firefox WebGL)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 13:48:29 +
with message-id 
and subject line Bug#956665: fixed in libdrm 2.4.101-2
has caused the Debian Bug report #956665,
regarding libdrm2: Update broke firefox WebGL
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.)


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

Dear Maintainer,

After updating libdrm2 from 2.4.100-4 to 2.4.101-1 WebGL stopped working on
firefox (using esr from repos and tar from mozilla).

After loading a WebGL sample from webglsamples.org the following is message is
shown in the web console:
Error: WebGL warning: : Failed to create WebGL context: WebGL 
creation failed: 
* tryNativeGL
* Exhausted GL driver options.

and in the terminal where firefox was launched:
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information


Looks similar to #907698.

Regards.

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

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

Versions of packages libdrm2 depends on:
ii  libc6  2.30-4
ii  libdrm-common  2.4.101-1

libdrm2 recommends no packages.

libdrm2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libdrm
Source-Version: 2.4.101-2
Done: Timo Aaltonen 

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libdrm 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, 14 Apr 2020 16:32:57 +0300
Source: libdrm
Architecture: source
Version: 2.4.101-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 956665
Launchpad-Bugs-Fixed: 1872586
Changes:
 libdrm (2.4.101-2) unstable; urgency=medium
 .
   * fix-realpath-vs-firefox.diff: Fix webgl on intel with firefox.
 (Closes: #956665) (LP: #1872586)
Checksums-Sha1:
 c2f5ca68142931c4bf3c1dd436663be00bd6b377 3271 libdrm_2.4.101-2.dsc
 7a1b727361d3456f6a5532fc98250d3d3a520b3e 54032 libdrm_2.4.101-2.debian.tar.xz
 f8c7faba818a2d9df3ab2265ea541545e52a70ac 7919 libdrm_2.4.101-2_source.buildinfo
Checksums-Sha256:
 d54baa66baf3edf0f7a4d8cf1ca3433cb0cfa3a2c6d44e104ec7c0af802de84d 3271 
libdrm_2.4.101-2.dsc
 41897da70ac8889c544fb27b8960947754afabcbd0088c7fd9e3ff7f628cf515 54032 
libdrm_2.4.101-2.debian.tar.xz
 cbf3044d0c9e0bfb7482ef74b54866b68a68f7a5d0890520bcea83a948d294f5 7919 
libdrm_2.4.101-2_source.buildinfo
Files:
 c6034f948dad4ac91f568f02c1468547 3271 libs optional libdrm_2.4.101-2.dsc
 691498fc666afb29f2c0e8ae6b8b 54032 libs optional 
libdrm_2.4.101-2.debian.tar.xz
 89eafae6ba559e61e3f013b57d7659df 7919 libs optional 
libdrm_2.4.101-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl6Vu58ACgkQy3AxZaiJ
hNzBrg//SB2bxXy2/4MFgRKHOiYLAYDYxWY9bsMxQ4mi1K3TObGKrdCLc5+q3DTL
QEe0IA3qh05BaeglH4ld7S6E8yUTNY7Xkr/qebFIcQieOUkZ2ORjgt6uVvvhqoJ1
DYkwyD5FV2rqRyZnkUw77cGMQV6DhZlHIZ0sUCsiBnfUvEGZsKqcRtJLJaATA0C1
nUf/bg/ZLL+6VSoFw0j3xVfxhwiLkAqjOLZQu3oSfpRxJ2oWF+QKDASsGn8iiSJg
iV2o8RNfFB+X2nYkYER3rBUwI8OI+oj2HeNICXraWotQAZDpd16w80dO/Ii8Uq5x
7ZCs5BBBlZ2BDBVwyBB32Ast2bTdOA7dNDLJX4QxgcZ1frXKIiKnvWxSzj/P+I4C
NKgtf3QQwxMce8QgX3bpfJIu1DmH3NYE9gnarBgQBtwT7QdwJ+VqufmXDVVaZ1WN
V48HhZMwtlOTl9v5XDoBUqi2wdVH7xRdGDjTir3cAocYBtG0JsUlTMc8Ll0cERyg
b4qtmMZTIPrkDZd9NXP+L5g5YQSLAUAwZhvv+3ptz2gbItqRM9jJvt1b

Bug#943480: marked as done (libspice-server1: qemu crashes on migration due to changes in spice-server cursor handling)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 16:36:18 +0300
with message-id 
and subject line Re: libspice-server1: qemu crashes on migration due to changes 
in spice-server cursor handling
has caused the Debian Bug report #943480,
regarding libspice-server1: qemu crashes on migration due to changes in 
spice-server cursor handling
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.)


-- 
943480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspice-server1
Version: 0.14.0-1.3
Severity: normal
Tags: upstream

qemu relies on specific behaviour in libspice-server for guest cursor resources,
which changed in 0.14.0

there is a fix upstream available under the commit

cursor: Delay release of QXL guest cursor resources
https://gitlab.freedesktop.org/spice/spice/commit/b547919190a6e1615b6ac4ba779210211a120135

which is included in the 0.14.1 release of spice

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

Kernel: Linux 5.0.21-3-pve (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libspice-server1 depends on:
ii  libc6   2.28-10
ii  libglib2.0-02.58.3-2+deb10u1
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblz4-11.8.3-1
ii  libopus01.3-1
ii  liborc-0.4-01:0.4.28-3.1
ii  libpixman-1-0   0.36.0-1
ii  libsasl2-2  2.1.27+dfsg-1
ii  libssl1.1   1.1.1d-0+deb10u2
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages libspice-server1 recommends:
ii  gstreamer1.0-libav 1.15.0.1+git20180723+db823502-2
ii  gstreamer1.0-plugins-base  1.14.4-2
ii  gstreamer1.0-plugins-good  1.14.4-1
ii  gstreamer1.0-plugins-ugly  1.14.4-1

libspice-server1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version:  0.14.2-1

On Fri, 25 Oct 2019 10:12:15 + Dominik Csapak  wrote:
> Package: libspice-server1
> Version: 0.14.0-1.3
> Severity: normal
> Tags: upstream
> 
> qemu relies on specific behaviour in libspice-server for guest cursor 
> resources,
> which changed in 0.14.0
> 
> there is a fix upstream available under the commit
> 
> cursor: Delay release of QXL guest cursor resources
> https://gitlab.freedesktop.org/spice/spice/commit/b547919190a6e1615b6ac4ba779210211a120135
> 
> which is included in the 0.14.1 release of spice

Hi!

It looks like this bugreport has been lost somehow.
0.14.2 version has been uploaded long ago, so closing
this bug now.

Thanks!

/mjt--- End Message ---

Bug#956624: marked as done (qemu: FTBFS on sparc64 due to libseccomp-dev dependency)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 13:22:16 +
with message-id 
and subject line Bug#956624: fixed in qemu 1:4.2-5
has caused the Debian Bug report #956624,
regarding qemu: FTBFS on sparc64 due to libseccomp-dev dependency
to be marked as done.

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

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


-- 
956624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello,

Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.

Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was 
building successfully before:

https://buildd.debian.org/status/logs.php?pkg=qemu&arch=sparc64

Instead of enabling seccomp on linux-any, maybe it could be enabled on 
something like this:

[!alpha !ia64 !m68k !sh4 !sparc64 !hurd-any !kfreebsd-any]

Thanks,
Tom
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-5
Done: Michael Tokarev 

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 15:47:40 +0300
Source: qemu
Architecture: source
Version: 1:4.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 956624
Changes:
 qemu (1:4.2-5) unstable; urgency=medium
 .
   * no error-out on address-of-packet-member in openbios
   * install ui-spice-app.so only if built, spice is optional
   * arm-fix-PAuth-sbox-functions-CVE-2020-10702.patch -
 Closes: CVE-2020-10702, weak signature generation
 in Pointer Authentication support for ARM
   * (temporarily) enable seccomp only on architectures where it can be built
 (Closes: #956624)
   * seccomp has grown up, no need in versioned build-dep
   * do not list librados-dev in build-dep as we only use librbd-dev
 and the latter depends on the former
   * only enable librbd on architectures where it is buildable
Checksums-Sha1:
 28b04e3a5658105914a06f7deefdcc64d99687fe 6695 qemu_4.2-5.dsc
 3767af616ec0554f973158ec7bd5d8c8cfc0b6dc 82580 qemu_4.2-5.debian.tar.xz
 296bbb5e9f1dc95f415c41d8abaccacc9e0dfcb5 8240 qemu_4.2-5_source.buildinfo
Checksums-Sha256:
 3d313b38e85b5623f6a172c73f94cb878d6a79aa2e46299463d5809cc3826a0b 6695 
qemu_4.2-5.dsc
 47b810fe5507c3ca14e47905d73d4919f457817cebe710561fee0a724be76728 82580 
qemu_4.2-5.debian.tar.xz
 1c63ddb23db0eabc0206c39515de8437ea3714138d940787b18e547eb032ec26 8240 
qemu_4.2-5_source.buildinfo
Files:
 39284b743ad59a0dd2bc23bd577d9d3b 6695 otherosfs optional qemu_4.2-5.dsc
 afea89ba5db9a6095ec05b44ffa98ead 82580 otherosfs optional 
qemu_4.2-5.debian.tar.xz
 7ddd87d3921fba50d48cd6e209613505 8240 otherosfs optional 
qemu_4.2-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl6VtLcPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZQVcH/1BJFaZBmOsEVfO31o/AX2mdWxt4VuFF2kGz
YRlfs4tjsZjMVlkYQJh2AMbpZM/M27oq7Svoi5JJ06oTjt/XV/aWhbeEgdib7a4B
I5WLL6BQp8fHXAwOQAHJC+lZIoIbfVts70LrbnOz4ZgmOqIWaKc9a4vau6J8iY9u
5ZZsEvsnYOd2ruhqJHYdAW53G7G7llcVEd0GG4Krq70j26+M+l4YJMnhfpw7DNv7
y8Lmul1Zg+xKJ3TSVwHpu320yS9yTfe9gUmpzU5J7i5+vfAGIgp+hqi37TH0scrZ
gbUnKAUAe8YRK/En8IQCJCZOtbPei4dKSgch35IoF9K+g6/Sw+Y=
=AO71
-END PGP SIGNATURE End Message ---

Bug#956695: marked as done (unrardll: needs binary upload)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 21:30:28 +0900
with message-id <20200414123028.ga63...@bulldog.preining.info>
and subject line Re: Bug#956695: unrardll: needs binary upload
has caused the Debian Bug report #956695,
regarding unrardll: needs binary 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.)


-- 
956695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unrardll
Version: 0.1.3-6
Severity: serious
Tags: ftbfs

Hi Maintainer

The package unrardll requires a binary upload since it is in contrib
and cannot be built on the buildds [1].

Please upload the binary package python3-unrardll_0.1.3-6_amd64.deb to
the archive.
There is no need for another source upload and no need to bump the version.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=unrardll
--- End Message ---
--- Begin Message ---
Hi Graham,

> The package unrardll requires a binary upload since it is in contrib
> and cannot be built on the buildds [1].

Indeed, thanks for the heads-up. I uploaded the binary build, thus
closing this bug.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#956202: marked as done (gnome-calendar crashes immediately after start)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 12:29:37 +0100
with message-id <20200414112937.ga212...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#956202: gnome-calendar crashes immediately after start
has caused the Debian Bug report #956202,
regarding gnome-calendar crashes immediately after start
to be marked as done.

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

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


-- 
956202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-calendar
Version: 3.36.0-1
Severity: critical

Dear Maintainer,

After a recent update to my system, gnome-calendar crashes immediately after 
staring it.

Running it from the terminal:
>> gnome-calendar 
Segmentation fault


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

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

Versions of packages gnome-calendar depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gsettings-desktop-schemas3.36.0-1
ii  libc62.30-4
ii  libcairo21.16.0-4
ii  libdazzle-1.0-0  3.36.0-1
ii  libecal-2.0-13.36.1-1
ii  libedataserver-1.2-243.36.1-1
ii  libedataserverui-1.2-2   3.36.1-1
ii  libgeoclue-2-0   2.5.6-1
ii  libglib2.0-0 2.64.1-1
ii  libgoa-1.0-0b3.36.0-1
ii  libgtk-3-0   3.24.14-1
ii  libgweather-3-16 3.36.0-1
ii  libhandy-0.0-0   0.0.13-2
ii  libical3 3.0.8-1
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libsoup2.4-1 2.70.0-1

Versions of packages gnome-calendar recommends:
ii  evolution-data-server  3.36.1-1

gnome-calendar suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.36.0-2

On Sun, 12 Apr 2020 at 14:22:29 +0100, Simon McVittie wrote:
> It seems to be fixed in the upstream gnome-3-36 branch. Please try version
> 3.36.0-2 from experimental when it becomes available, and report back
> whether that fixes this crash for you.

Fixed in experimental according to feedback in private email.--- End Message ---

Bug#617918: marked as done (chkrootkit: False positive: slice)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 12:49:26 +0200
with message-id <20200414104926.naujbi3w6aa245xh@function>
and subject line Re: False positives in chkrootkit
has caused the Debian Bug report #617918,
regarding chkrootkit: False positive: slice
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.)


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

Hello,

Running chkrootkit with the slice package installed says TH-Sharpe is
installed, while the slice package is simply a wml dependency.

Samuel

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

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages chkrootkit depends on:
ii  binutils   2.21.0.20110302-1 The GNU assembler, linker and bina
ii  cdebconf [debconf-2.0] 0.153 Debian Configuration Management Sy
ii  debconf [debconf-2.0]  1.5.38Debian configuration management sy
ii  libc6  2.11.2-11 Embedded GNU C Library: Shared lib
ii  net-tools  1.60-23   The NET-3 networking toolkit
ii  procps 1:3.2.8-10/proc file system utilities

chkrootkit recommends no packages.

chkrootkit suggests no packages.

-- debconf information excluded

-- 
Samuel Thibault 
 bouhouhouh, b il m'a abandonné. Tout ca parce que je regardais plus mon 
emacs que lui !
 s/lui/ses messages irc/
 -+- #ens-mim esseulé -+-


--- End Message ---
--- Begin Message ---
Hello,

Samuel Wrote:
> > Running chkrootkit with the slice package installed says TH-Sharpe is
> > installed, while the slice package is simply a wml dependency.

Marcos Fouces, le mar. 14 avril 2020 12:39:44 +0200, a ecrit:
> False positives always fall on the safe vs. sorry argument. Please,
> check 
> https://salsa.debian.org/pkg-security-team/chkrootkit/-/blob/debian/master/debian/README.FALSE-POSITIVES
> 
> You can always use the "-e" option or an exclude file (defined in
> /etc/chkrootkit.conf) to avoid this warning.
> 
> I don't believe that is a bug and i would like to close it if you don't
> have any objection.

> > -- System Information:
> > Debian Release: wheezy/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'),

That's a completely outdated report anyway.

Samuel--- End Message ---

Bug#925099: marked as done (Updating the libmnl Uploaders list)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:33:42 +
with message-id 
and subject line Bug#925099: fixed in libmnl 1.0.4-3
has caused the Debian Bug report #925099,
regarding Updating the libmnl Uploaders list
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.)


-- 
925099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmnl
Version: 1.0.4-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

anibal has not been working on
the libmnl package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libmnl
Source-Version: 1.0.4-3
Done: Arturo Borrero Gonzalez 

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

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated libmnl 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, 14 Apr 2020 12:09:01 +0200
Source: libmnl
Architecture: source
Version: 1.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Closes: 925099 942329
Changes:
 libmnl (1.0.4-3) unstable; urgency=medium
 .
   [ Arturo Borrero Gonzalez ]
   * [e542e5f] src:libmnl: reallocate to pkg-netfilter packaging team (and 
salsa)
 (Closes: #925099)
 .
   [ Alberto Molina Coballes ]
   * [fc7598a] d/control: mark libmnl-dev as Multi-Arch: same (Closes: #942329)
 .
   [ Debian Janitor ]
   * [b91f74f] Trim trailing whitespace.
   * [392bb25] Use secure copyright file specification URI.
   * [01df844] Drop custom source compression.
   * [1183b8e] Use secure URI in Homepage field.
   * [b2a05fb] Bump debhelper from old 9 to 10.
   * [2a532d8] Drop unnecessary dependency on dh-autoreconf.
   * [1e14bfb] Use canonical URL in Vcs-Git.
   * [5f69001] Fix day-of-week for changelog entry 1.0.3-2.
 .
   [ Arturo Borrero Gonzalez ]
   * [c79e0db] d/: add salsa gitlab integration
   * [3526970] src:libmnl: drop dh-exec build-dep
   * [80e16a6] src:libmnl: bump std-version to 4.5.0
   * [7e80c86] src:libmnl: bump debhelper-compat to 12 and refresh build-deps
   * [825c810] src:libmnl: downgrade the priority of the package
Checksums-Sha1:
 f2217f34cc5f428c17ec2c056e055dcdd011c583 2071 libmnl_1.0.4-3.dsc
 dd63865c3f9c0b77d5e8c4bc6995d0b3589a29f6 7780 libmnl_1.0.4-3.debian.tar.xz
 7ed50c8fdaec7b94c3172dedf64c575bd901826a 5813 libmnl_1.0.4-3_amd64.buildinfo
Checksums-Sha256:
 9dc308ffade8cc0cb7a7ee8925e25f338121f642a9a9caef535effd893d4830a 2071 
libmnl_1.0.4-3.dsc
 7f5a5c246ee6d6d65efd01db289886c0ea986546f112e70c3006b50d0e6fabc1 7780 
libmnl_1.0.4-3.debian.tar.xz
 fbabaffa343b3e819eb8d7cb48d81577640a01ed543a16e9b80b84ca27af1e1c 5813 
libmnl_1.0.4-3_amd64.buildinfo
Files:
 a0c116591eb7551e96857716b133773a 2071 libs optional libmnl_1.0.4-3.dsc
 432e7e5ea9eef073aa922b0c8d9405a3 7780 libs optional 
libmnl_1.0.4-3.debian.tar.xz
 d9374e7c80e2076ef9d7212898db970f 5813 libs optional 
libmnl_1.0.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAl6VjBIACgkQaOcTmB0V
FfilYw//eIZq+J8N2fsCOtaVzYigpknE4CX2pU8XRAPUPXW1R+mFv0DybqSY4mr4
9ww2II1ji/vnmAlkpsPI3CB9tJdn+MLVIXRrROvqUqyZwv4v+FTRI8kAZ9Vwne0y
xKgD0VOIbSXia2lz/UJdxbqWfhYd54Dj75RYPpn7/bDV+SOszHF/JW+Jcq3Sk20N
cEsReTTuUHbzJHhgK0nwkRNkAump4VFZJifzURJdP2hPRu/wtc2FCHkWTPb34q8O
Oo6Ufo4h/Oja1fQUG/eFjXqSmLXJrvRRPuTq/q4CldcK3ArGcJ12yda0I0BnUrlo
HDHArdoYAS8YYf2Dg5PgI025AayXYa4UmLizqFfBA1X3rt1vQ7c6OyHTMHTLnFEF
tTkDQnRTLxGb2rSmJSUqaZwFmh//ixjaCgl+C/vbkW3KbBtPJzjlPpaCcAIrHwej
lgMeMEkpYqkMH

Bug#942329: marked as done (libmnl-dev: Can't install for two arch simultaneously)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:33:42 +
with message-id 
and subject line Bug#942329: fixed in libmnl 1.0.4-3
has caused the Debian Bug report #942329,
regarding libmnl-dev: Can't install for two arch simultaneously
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.)


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

Dear Maintainer,

I am trying to cross compile a program relying on libipset, but can't install
libipset-dev:amd64 and libipset-dev:arm64 at the same time. I suspect this is
due to libmnl-dev not exposing the correct Multiarch tags (but don't know enough
about this to send a patch).

Steps to reproduce this issue in Docker:

❯ docker run -it debian:buster /bin/bash
root@8fc51df86cd9:/# dpkg --add-architecture arm64
root@8fc51df86cd9:/# apt update > /dev/null
root@8fc51df86cd9:/# apt install libipset-dev:arm64 libipset-dev:amd64 
libmnl-dev:arm64 libmnl-dev:amd64
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libmnl-dev : Conflicts: libmnl-dev:arm64 but 1.0.4-2 is to be installed
 libmnl-dev:arm64 : Conflicts: libmnl-dev but 1.0.4-2 is to be installed
E: Unable to correct problems, you have held broken packages.


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 4.9.184-linuxkit (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libmnl-dev depends on:
ii  libmnl0  1.0.4-2

libmnl-dev recommends no packages.

libmnl-dev suggests no packages.
--- End Message ---
--- Begin Message ---
Source: libmnl
Source-Version: 1.0.4-3
Done: Arturo Borrero Gonzalez 

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

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated libmnl 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, 14 Apr 2020 12:09:01 +0200
Source: libmnl
Architecture: source
Version: 1.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Closes: 925099 942329
Changes:
 libmnl (1.0.4-3) unstable; urgency=medium
 .
   [ Arturo Borrero Gonzalez ]
   * [e542e5f] src:libmnl: reallocate to pkg-netfilter packaging team (and 
salsa)
 (Closes: #925099)
 .
   [ Alberto Molina Coballes ]
   * [fc7598a] d/control: mark libmnl-dev as Multi-Arch: same (Closes: #942329)
 .
   [ Debian Janitor ]
   * [b91f74f] Trim trailing whitespace.
   * [392bb25] Use secure copyright file specification URI.
   * [01df844] Drop custom source compression.
   * [1183b8e] Use secure URI in Homepage field.
   * [b2a05fb] Bump debhelper from old 9 to 10.
   * [2a532d8] Drop unnecessary dependency on dh-autoreconf.
   * [1e14bfb] Use canonical URL in Vcs-Git.
   * [5f69001] Fix day-of-week for changelog entry 1.0.3-2.
 .
   [ Arturo Borrero Gonzalez ]
   * [c79e0db] d/: add salsa gitlab integration
   * [3526970] src:libmnl: drop dh-exec build-dep
   * [80e16a6] src:libmnl: bump std-version to 4.5.0
   * [7e80c86] src:libmnl: bump debhelper-compat to 12 and refresh build-deps
   * [825c810] src:libmnl: downgrade the priority of the package
Checksums-Sha1:
 f2217f34cc5f428c17ec2c056e055dcdd011c583 2071 libmnl_1.0.4-3.dsc
 dd63865c3f9c0b77d5e8c4bc6995d0b3589a29f6 7780 libmnl_1.0.4-3.debian.tar.xz
 7ed50c8fdaec7b94c3172dedf64c575bd901826a 5813 libmnl_1.0.4-3_amd64.buildinfo
Checksums-Sha256:
 9dc308

Bug#954593: marked as done (metaconfig: FTBFS: dh_auto_test: error: pybuild --test --test-nose2 -i python{version} -p "3.7 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:19:27 +
with message-id 
and subject line Bug#954593: fixed in metaconfig 0.1.4a1-7
has caused the Debian Bug report #954593,
regarding metaconfig: FTBFS: dh_auto_test: error: pybuild --test --test-nose2 
-i python{version} -p "3.7 3.8" returned exit code 13
to be marked as done.

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

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


-- 
954593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metaconfig
Version: 0.1.4a1-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.7 setup.py build
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/metaconfig
> copying metaconfig/__init__.py -> build/lib/metaconfig
> copying metaconfig/mconf.py -> build/lib/metaconfig
> running egg_info
> creating metaconfig.egg-info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> python3.8 setup.py build
> running build
> running build_py
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> dh_auto_build
>   pybuild --build --test-nose2 -i python{version} -p "3.7 3.8"
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7/build/metaconfig
> copying metaconfig/__init__.py -> 
> /<>/.pybuild/cpython3_3.7/build/metaconfig
> copying metaconfig/mconf.py -> 
> /<>/.pybuild/cpython3_3.7/build/metaconfig
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/metaconfig
> copying metaconfig/__init__.py -> 
> /<>/.pybuild/cpython3_3.8/build/metaconfig
> copying metaconfig/mconf.py -> 
> /<>/.pybuild/cpython3_3.8/build/metaconfig
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test --test-nose2 -i python{version} -p "3.7 3.8"
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7/build; 
> python3.7 -m nose2 -v 
> test_1 (test_metaconfig.Test1) ... ok
> test_2 (test_metaconfig.Test1) ... ok
> test_3 (test_metaconfig.Test1) ... ok
> test_4 (test_metaconfig.Test1) ... ok
> test_1 (test_metaconfig.Test2) ... ok
> test_2 (test_metaconfig.Test2) ... ok
> test_1 (test_metaconfig.Test3) ... ok
> test_global.transplant_class..C (test_1) ... ERROR
> 
> ==
> ERROR: test_global.transplant_class..C (test_1)
> --
> Traceback (most recent call last):
>   File "/<>/.pybuild/cpython3_3.7/build/test/test_global.py", 
> line 34, in test_1
> assert config.get('foo', 'a') == '42'
>   File "/usr/lib/python3.7/configparser.py", line 780, in get
> d = self._unify_values(section, vars)
>   File "/usr/lib/python3.7/configparser.py", line 1146, in _unify_values
> raise NoSectionError(section) from None
> configparser.NoSectionError: No section: 'foo'
> 
> --
> Ran 8 tests in 0.003s
> 
> FAILED (error

Bug#956145: marked as done (qemu: CVE-2020-11102)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:07:28 +
with message-id 
and subject line Bug#956145: fixed in qemu 1:4.2-4
has caused the Debian Bug report #956145,
regarding qemu: CVE-2020-11102
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.)


-- 
956145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:4.2-3
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for qemu.

CVE-2020-11102[0]:
| hw/net/tulip.c in QEMU 4.2.0 has a buffer overflow during the copying
| of tx/rx buffers because the frame size is not validated against the
| r/w data length.

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-11102
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11102
[1] https://www.openwall.com/lists/oss-security/2020/04/06/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-4
Done: Michael Tokarev 

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:44:43 +0300
Source: qemu
Architecture: source
Version: 1:4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 866756 953910 955741 956145
Changes:
 qemu (1:4.2-4) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * d/rules: build minimal configuration for qboot/microvm usage
   * set microvm to be the default machine type for microvm case
   * install ui-spice-app.so in qemu-system-common
   * do not depend on libattr-dev, functions are now in libc6 (Closes: #953910)
   * net-tulip-check-frame-size-and-r-w-data-length-CVE-2020-11102.patch
 (Closes: #956145, CVE-2020-11102, tulip nic buffer overflow)
   * qemu-system-data: s/highcolor/hicolor/ (Closes: #955741)
   * switch binfmt registration to use update-binfmts --[un]import
 (Closes: #866756)
   * build openbios-ppc & openbios-sparc binaries in qemu-system-data,
 and replace corresponding binary packages.
 Add gcc-sparc64-linux-gnu, fcode-utils & xsltproc to build-depend-indep
   * build and provide/replace qemu-slof too
 .
   [ Aurelien Jarno ]
   * enable support for riscv64 hosts
Checksums-Sha1:
 0be49f2f6ccc59f5dd3e9ab9b63f5c553959a4a1 6581 qemu_4.2-4.dsc
 f0c5abb30e75a2fa5d10dd61bdca7197f5fd3d82 81612 qemu_4.2-4.debian.tar.xz
 3a77d5bad2e211155a642572f8d2bcac7271c372 8240 qemu_4.2-4_source.buildinfo
Checksums-Sha256:
 c9f1e502cf63dacabd803157f7b26cd552a27dcc91bc0de2c69f85a93eb0e593 6581 
qemu_4.2-4.dsc
 55214f5616543c23c15a538acfa0bdda2e4c2a29d85d848d69f96067f169395a 81612 
qemu_4.2-4.debian.tar.xz
 763f2d5d5b95262d0779905b0e83805462ec727a3a3badb0b296a108c299fa98 8240 
qemu_4.2-4_source.buildinfo
Files:
 82f360cc06160d2138a0b38c4ecfc249 6581 otherosfs optional qemu_4.2-4.dsc
 d6a78bbc19b137deb64457204f0abf28 81612 otherosfs optional 
qemu_4.2-4.debian.tar.xz
 40e44a7d223d9b1d7257158528123b14 8240 otherosfs optional 
qemu_4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl6VhrwPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZDHkH+QG6MUeSDduDtzHPtuPeobEvYwbTj1UZtCTZ
d/SarIurdcnk0yYGqTOeSMjETyyrlFHajXNufg7NGEPg07aAY796vSeGsyTEIR2k
4cxcbROJI/8+AOq4egDRow674H/sj9KPyfx/EETJejRku6xdbcTS/e1lEFibo0Tv
6bOj3ex/pDVhaVGSZUL1+LuFFNmDg2PCsc4QZw5wveuv2NSCmQW9RshB41EuIM8U
5i2DHp1KV/GWBZEhn2j3ncSfA4XvBVGIfNcwW77BBBQV83egFtz5PrrYyxsOXEK1
VipnD0mbhAg9R9e22+r2qjv9XYrCbBLGGKNGP3IkJYlk5udT2lM=
=elJg
-END PGP SIGNATURE End Message ---

Bug#953910: marked as done (qemu: Build-Depends on unused libattr1-dev)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:07:28 +
with message-id 
and subject line Bug#953910: fixed in qemu 1:4.2-4
has caused the Debian Bug report #953910,
regarding qemu: Build-Depends on unused libattr1-dev
to be marked as done.

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

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


-- 
953910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-3
Severity: minor

Hi!

This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-4
Done: Michael Tokarev 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:44:43 +0300
Source: qemu
Architecture: source
Version: 1:4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 866756 953910 955741 956145
Changes:
 qemu (1:4.2-4) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * d/rules: build minimal configuration for qboot/microvm usage
   * set microvm to be the default machine type for microvm case
   * install ui-spice-app.so in qemu-system-common
   * do not depend on libattr-dev, functions are now in libc6 (Closes: #953910)
   * net-tulip-check-frame-size-and-r-w-data-length-CVE-2020-11102.patch
 (Closes: #956145, CVE-2020-11102, tulip nic buffer overflow)
   * qemu-system-data: s/highcolor/hicolor/ (Closes: #955741)
   * switch binfmt registration to use update-binfmts --[un]import
 (Closes: #866756)
   * build openbios-ppc & openbios-sparc binaries in qemu-system-data,
 and replace corresponding binary packages.
 Add gcc-sparc64-linux-gnu, fcode-utils & xsltproc to build-depend-indep
   * build and provide/replace qemu-slof too
 .
   [ Aurelien Jarno ]
   * enable support for riscv64 hosts
Checksums-Sha1:
 0be49f2f6ccc59f5dd3e9ab9b63f5c553959a4a1 6581 qemu_4.2-4.dsc
 f0c5abb30e75a2fa5d10dd61bdca7197f5fd3d82 81612 qemu_4.2-4.debian.tar.xz
 3a77d5bad2e211155a642572f8d2bcac7271c372 8240 qemu_4.2-4_source.buildinfo
Checksums-Sha256:
 c9f1e502cf63dacabd803157f7b26cd552a27dcc91bc0de2c69f85a93eb0e593 6581 
qemu_4.2-4.dsc
 55214f5616543c23c15a538acfa0bdda2e4c2a29d85d848d69f96067f169395a 81612 
qemu_4.2-4.debian.tar.xz
 763f2d5d5b95262d0779905b0e83805462ec727a3a3badb0b296a108c299fa98 8240 
qemu_4.2-4_source.buildinfo
Files:
 82f360cc06160d2138a0b38c4ecfc249 6581 otherosfs optional qemu_4.2-4.dsc
 d6a78bbc19b137deb64457204f0abf28 81612 otherosfs optional 
qemu_4.2-4.debian.tar.xz
 40e44a7d223d9b1d7257158528123b14 8240 otherosfs optional 
qemu_4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl6VhrwPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZDHkH+QG6MUeSDduDtzHPtuPeobEvYwbTj1UZtCTZ
d/SarIurdcnk0yYGqTOeSMjETyyrlFHajXNufg7NGEPg07aAY796vSeGsyTEIR2k
4cxcbROJI/8+AOq4egDRow674H/sj9KPyfx/EETJejRku6xdbcTS/e1lEFibo0Tv
6bOj3ex/pDVhaVGSZUL1+LuFFNmDg2PCsc4QZw5wveuv2NSCmQW9RshB41EuIM8U
5i2DHp1KV/GWBZEhn2j3ncSfA4XvBVGIfNcwW77BBBQV83egFtz5PrrYyxsOXEK1
VipnD0mbhAg9R9e22+r2qjv9XYrCbBLGGKNGP3IkJYlk5udT2lM=
=elJg
-END PGP SIGNATURE End Message ---

Bug#866756: marked as done (qemu-user-static should depend on binfmt-support or add a trigger)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:07:28 +
with message-id 
and subject line Bug#866756: fixed in qemu 1:4.2-4
has caused the Debian Bug report #866756,
regarding qemu-user-static should depend on binfmt-support or add a trigger
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.)


-- 
866756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-user-static
Version: 1:2.8+dfsg-6
Severity: minor

Dear Maintainer,

currently qemu-user-static doesn't depend on binfmt-support but tries to use it
in it's postinst. Installing qemu-user-static first and binfmt-support results
in the binfmt registration not being done. I would propose to either add a
dependency to binfmt-support or add a dpkg trigger to do the registration
later.

Cheers Jochen

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

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

qemu-user-static depends on no packages.

Versions of packages qemu-user-static recommends:
ii  binfmt-support  2.1.6-2

Versions of packages qemu-user-static suggests:
pn  sudo  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-4
Done: Michael Tokarev 

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:44:43 +0300
Source: qemu
Architecture: source
Version: 1:4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 866756 953910 955741 956145
Changes:
 qemu (1:4.2-4) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * d/rules: build minimal configuration for qboot/microvm usage
   * set microvm to be the default machine type for microvm case
   * install ui-spice-app.so in qemu-system-common
   * do not depend on libattr-dev, functions are now in libc6 (Closes: #953910)
   * net-tulip-check-frame-size-and-r-w-data-length-CVE-2020-11102.patch
 (Closes: #956145, CVE-2020-11102, tulip nic buffer overflow)
   * qemu-system-data: s/highcolor/hicolor/ (Closes: #955741)
   * switch binfmt registration to use update-binfmts --[un]import
 (Closes: #866756)
   * build openbios-ppc & openbios-sparc binaries in qemu-system-data,
 and replace corresponding binary packages.
 Add gcc-sparc64-linux-gnu, fcode-utils & xsltproc to build-depend-indep
   * build and provide/replace qemu-slof too
 .
   [ Aurelien Jarno ]
   * enable support for riscv64 hosts
Checksums-Sha1:
 0be49f2f6ccc59f5dd3e9ab9b63f5c553959a4a1 6581 qemu_4.2-4.dsc
 f0c5abb30e75a2fa5d10dd61bdca7197f5fd3d82 81612 qemu_4.2-4.debian.tar.xz
 3a77d5bad2e211155a642572f8d2bcac7271c372 8240 qemu_4.2-4_source.buildinfo
Checksums-Sha256:
 c9f1e502cf63dacabd803157f7b26cd552a27dcc91bc0de2c69f85a93eb0e593 6581 
qemu_4.2-4.dsc
 55214f5616543c23c15a538acfa0bdda2e4c2a29d85d848d69f96067f169395a 81612 
qemu_4.2-4.debian.tar.xz
 763f2d5d5b95262d0779905b0e83805462ec727a3a3badb0b296a108c299fa98 8240 
qemu_4.2-4_source.buildinfo
Files:
 82f360cc06160d2138a0b38c4ecfc249 6581 otherosfs optional qemu_4.2-4.dsc
 d6a78bbc19b137deb64457204f0abf28 81612 otherosfs optional 
qemu_4.2-4.debian.tar.xz
 40e44a7d223d9b1d7257158528123b14 8240 otherosfs optional 
qemu_4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl6VhrwPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZDHkH+QG6MUeSDduDtzHPtuPeobEvYwbTj1UZtCTZ
d/SarIurdcnk0yYGqTOeSMjETyyrlFHajXNufg7NGEPg07aAY796vSeGsyTEIR2k
4cxcbROJI/8+AOq4egDRow674H/sj9KPyfx/EETJejRku6xdbcTS/e1lEFibo0Tv
6bOj3ex/pDVhaVGSZUL1+LuFFNmDg2PCsc4QZw5wveuv2NSCmQW9RshB41EuIM

Bug#955741: marked as done (qemu-system-data: qemu.svg icon installed in wrong directory)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:07:28 +
with message-id 
and subject line Bug#955741: fixed in qemu 1:4.2-4
has caused the Debian Bug report #955741,
regarding qemu-system-data: qemu.svg icon installed in wrong directory
to be marked as done.

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

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


-- 
955741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-data
Version: 1:4.2-3
Severity: normal

Hello,

Looks like the qemu.svg file is installed in a wrong directory

It's installed in /usr/share/icons/*high*color/scalable/apps/ but it
should be installed in /usr/share/icons/*hi*color/scalable/apps/
instead.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.5.0-rc5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:4.2-4
Done: Michael Tokarev 

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:44:43 +0300
Source: qemu
Architecture: source
Version: 1:4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 866756 953910 955741 956145
Changes:
 qemu (1:4.2-4) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * d/rules: build minimal configuration for qboot/microvm usage
   * set microvm to be the default machine type for microvm case
   * install ui-spice-app.so in qemu-system-common
   * do not depend on libattr-dev, functions are now in libc6 (Closes: #953910)
   * net-tulip-check-frame-size-and-r-w-data-length-CVE-2020-11102.patch
 (Closes: #956145, CVE-2020-11102, tulip nic buffer overflow)
   * qemu-system-data: s/highcolor/hicolor/ (Closes: #955741)
   * switch binfmt registration to use update-binfmts --[un]import
 (Closes: #866756)
   * build openbios-ppc & openbios-sparc binaries in qemu-system-data,
 and replace corresponding binary packages.
 Add gcc-sparc64-linux-gnu, fcode-utils & xsltproc to build-depend-indep
   * build and provide/replace qemu-slof too
 .
   [ Aurelien Jarno ]
   * enable support for riscv64 hosts
Checksums-Sha1:
 0be49f2f6ccc59f5dd3e9ab9b63f5c553959a4a1 6581 qemu_4.2-4.dsc
 f0c5abb30e75a2fa5d10dd61bdca7197f5fd3d82 81612 qemu_4.2-4.debian.tar.xz
 3a77d5bad2e211155a642572f8d2bcac7271c372 8240 qemu_4.2-4_source.buildinfo
Checksums-Sha256:
 c9f1e502cf63dacabd803157f7b26cd552a27dcc91bc0de2c69f85a93eb0e593 6581 
qemu_4.2-4.dsc
 55214f5616543c23c15a538acfa0bdda2e4c2a29d85d848d69f96067f169395a 81612 
qemu_4.2-4.debian.tar.xz
 763f2d5d5b95262d0779905b0e83805462ec727a3a3badb0b296a108c299fa98 8240 
qemu_4.2-4_source.buildinfo
Files:
 82f360cc06160d2138a0b38c4ecfc249 6581 otherosfs optional qemu_4.2-4.dsc
 d6a78bbc19b137deb64457204f0abf28 81612 otherosfs optional 
qemu_4.2-4.debian.tar.xz
 40e44a7d223d9b1d7257158528123b14 8240 otherosfs optional 
qemu_4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAl6VhrwPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZDHkH+QG6MUeSDduDtzHPtuPeobEvYwbTj1UZtCTZ
d/SarIurdcnk0yYGqTOeSMjETyyrlFHajXNufg7NGEPg07aAY796vSeGsyTEIR2k
4cxcbROJI/8+AOq4egDRow674H/sj9KPyfx/EETJejRku6xdbcTS/e1lEFibo0Tv
6bOj3ex/pDVhaVGSZUL1+LuFFNmDg2PCsc4QZw5wveuv2NSCmQW9RshB41EuIM8U
5i2DHp1KV/GWBZEhn2j3ncSfA4XvBVGIfNcwW77BBBQV83egFtz5PrrYyxsOXEK1
VipnD0mbhAg9R9e22+r2qjv9XYrCbBLGGKNGP3IkJYlk5udT2lM=
=elJg
-EN

Bug#939545: marked as done (Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 12:56:25 +0300
with message-id 
and subject line Re: Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio 
problem with Kernel v 4.19.0-5-amd64 (LTS)
has caused the Debian Bug report #939545,
regarding Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 
4.19.0-5-amd64 (LTS)
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.)


-- 
939545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 4.19.0-5-amd64
Bug Description
Unbearable whistling in headphones plugged into 3,5 mm audio jack port during 
the absence of broadcast (music/movie ended, paused, etc.)
My Dell XPS 9570 with the kernel  4.19.0-5-amd64 (LTS) are impacted by this bug 
;(
I have to use headphones the night for 3-4 hours to make no noise, it hurts my 
ears and this situation starts very seriously to exasperate me.
Best regards.
Philippe--- End Message ---
--- Begin Message ---
Version: 5.4.19-1~bpo10+1

On Mon, 13 Apr 2020 19:54:01 +0200 (CEST) "pham...@bluewin.ch" 
 wrote:
> Problem is solved with Powertop v.2.11 from testing and Kernel 5.4 from 
> backports.
> Thank you very much for your work.
> The ticket can be considered as resolved.
> Powertop v.2.11 should be in backport, it works very fine !!!
> Regards.
> Philippe
Hi!

This can be done by sending mail to <939545-d...@bugs.debian.org> and
I have just done that. Source: https://www.debian.org/Bugs/Developer#closing

Regards,
Juhani--- End Message ---

Bug#956624: marked as done (qemu: FTBFS on sparc64 due to libseccomp-dev dependency)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 12:42:09 +0300
with message-id <6c935349-6348-27ae-c24c-6d38c1cd3...@msgid.tls.msk.ru>
and subject line Re: Bug#956624: qemu: FTBFS on sparc64 due to libseccomp-dev 
dependency
has caused the Debian Bug report #956624,
regarding qemu: FTBFS on sparc64 due to libseccomp-dev dependency
to be marked as done.

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

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


-- 
956624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello,

Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.

Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was 
building successfully before:

https://buildd.debian.org/status/logs.php?pkg=qemu&arch=sparc64

Instead of enabling seccomp on linux-any, maybe it could be enabled on 
something like this:

[!alpha !ia64 !m68k !sh4 !sparc64 !hurd-any !kfreebsd-any]

Thanks,
Tom
--- End Message ---
--- Begin Message ---
13.04.2020 20:55, Tom Turelinckx wrote:
> Source: qemu
> Severity: normal
> User: debian-sp...@lists.debian.org
> Usertags: sparc64
> 
> Hello,
> 
> Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.
> 
> Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was 
> building successfully before:
> 
> https://buildd.debian.org/status/logs.php?pkg=qemu&arch=sparc64
> 
> Instead of enabling seccomp on linux-any, maybe it could be enabled on 
> something like this:

Well, I just followed libseccomp's d/control, which says linux-any.

I think if we need to solve this issue, we should start with libseccomp -
either fix it to build on sparc64, or adjust its Architecture field to
something like you suggested.

I don't think in general it is a good idea to fix FTBFS in other packages
by restricting optional features in other packages. I might be wrong here,
too.

Thanks,

/mjt--- End Message ---

Bug#956580: marked as done (aoflagger: boost update makes aoflagger uninstallable)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:54:57 +0200
with message-id <98d6d3fe-7dfb-0e0c-c5ad-a2151b7d5...@debian.org>
and subject line Re: aoflagger: boost update makes aoflagger uninstallable
has caused the Debian Bug report #956580,
regarding aoflagger: boost update makes aoflagger uninstallable
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.)


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

Dear Maintainer,

the recent update of boost libraries to version 1.67.0-17+b1, in particular
probably of libboost-python1.67.0, apparently broke some dependency of
aoflagger, forcing its removal and making it uninstallable.  I suspect it is
a mere packaging problem but cannot investigate it in detail, since I need
aoflagger and thus pinned the version of boost till this is sorted out.  It
is even possible that this is a problem on the side of boost libraries, if
suitable please feel free to contact their maintainer about this.  Or it may
be due to similar problems simultaneously making libcasa-python3-4
uninstallable as well.

Thanks in advance, best regards
Giacomo Mulas


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

Kernel: Linux 5.5.13-jak (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.utf8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set 
to it_IT.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aoflagger depends on:
ii  libaoflagger0   2.15.0-1+b1
ii  libatkmm-1.6-1v52.28.0-2
ii  libboost-date-time1.67.01.67.0-17
ii  libboost-python1.67.0 [libboost-python1.67.0-py37]  1.67.0-17
ii  libboost-system1.67.0   1.67.0-17
ii  libc6   2.30-4
ii  libcairomm-1.0-1v5  1.12.2-4
ii  libcasa-casa4   3.2.1-4+b2
ii  libcasa-ms4 3.2.1-4+b2
ii  libcasa-tables4 3.2.1-4+b2
ii  libgcc-s1   10-20200411-1
ii  libglibmm-2.4-1v5   2.64.2-1
ii  libgtkmm-3.0-1v53.24.2-1
ii  libpython3.83.8.2-1+b1
ii  libsigc++-2.0-0v5   2.10.2-1
ii  libstdc++6  10-20200411-1

aoflagger recommends no packages.

Versions of packages aoflagger suggests:
ii  aoflagger-dev  2.15.0-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: notfound -1 aoflagger 2.15.0-1+b1

After fixing casacore (#956578), this package compiles well. So, I will
close this.

Cheers

Ole--- End Message ---

Bug#816964: marked as done (snort: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#816964: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #816964,
regarding snort: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
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.)


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

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.

pt_BR.po.gz
Description: application/gzip


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (was /usr/doc/snort-doc)
   * debian/snort.logrotate: Created to install the logrotate file using
 debhelper
   * rename snort.cron.daily to snort-common.cron.daily so it is install
 in the snort-common package by debelper
   * debian/snort.preinst:
 - Instead of recursively changing the logdir change the logdir first
   and then all the files in it (if any) [lintian fix]
   * debian/snort-doc.docs: Remove documents that are already provided by the
 snort package
   * debian/{snort.init-d,snort.postinst}: Use /run instead of /var/run and
  place the PIDFILES under /run/snort, creating it if it is required.
  Also provide the pidfile location to the Snort program, otherwise it
  would be created in /var/log/snort/ (LP: #1006982)
   * debian/snort.init-d: Do not set a default value for DEBIAN_SNORT_HOME_NET,
 if it is not defined then the value is not passed over to Snort. This
 allows users to set an empty value and define the configuration in
 /etc/snort/snort.conf (or /etc/snort/snort.$interface.conf instead.
 (LP: #566543)
   * debian/copyright: Update list of maintainers as well as copyright holders
   * debian/patches/documentation_debian: Create a patch to document Debian
 specific changes and configuration (e.g. alert and logging) describing
 how to read the Snort logs (Closes: 910452)
   * debian/patches/config: Change the configuration to also log an alert file
 log and log also alerts to Syslog
   * debian/snort.config:
   - Try to find the system network interface instead of using a default
 (eth0) name. This should make unattended package installat

Bug#952296: marked as done (snort: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/snort_manual.pdf" (tried in .))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:19 +
with message-id 
and subject line Bug#952296: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #952296,
regarding snort: FTBFS: dh_installdocs: error: Cannot find (any matches for) 
"doc/snort_manual.pdf" (tried in .)
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.)


-- 
952296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snort
Version: 2.9.7.0-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-exec-am'.
>  /bin/mkdir -p '/<>/debian/snort-common/usr//share/man/man8'
>  /usr/bin/install -c -m 644 snort.8 
> '/<>/debian/snort-common/usr//share/man/man8'
>  /bin/mkdir -p '/<>/debian/snort-common/usr//lib/pkgconfig'
>  /usr/bin/install -c -m 644 snort.pc 
> '/<>/debian/snort-common/usr//lib/pkgconfig'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
> rm -f  `pwd`/debian/snort-common/usr/sbin/snort
> # clean dependency_libs
> find `pwd`/debian/snort-common/usr/lib  -name "*.la" -exec \
>   sed -i -e "s,^dependency_libs=.*,dependency_libs=''," {} +
> install -m 755 -o root -g root src/snort-basic 
> `pwd`/debian/snort/usr/sbin/snort
> install -m 644 -o root -g root `pwd`/debian/snort.default 
> `pwd`/debian/snort/etc/default/snort
> install -m 755 -o root -g root `pwd`/debian/snort.init.d 
> `pwd`/debian/snort/etc/init.d/snort
> install -m 755 -o root -g root `pwd`/debian/my/snort.ip-up.d 
> `pwd`/debian/snort/etc/ppp/ip-up.d/snort
> install -m 755 -o root -g root `pwd`/debian/my/snort.ip-down.d 
> `pwd`/debian/snort/etc/ppp/ip-down.d/snort
> install -m 644 -o root -g root `pwd`/debian/snort.logrotate 
> `pwd`/debian/snort/etc/logrotate.d/snort
> mv `pwd`/debian/snort-common/usr/lib/* 
> `pwd`/debian/snort-common-libraries/usr/lib/
> rmdir `pwd`/debian/snort-common/usr/lib/
> rm -rf `pwd`/debian/sort-common/usr/src/
> dh_install -s
> dh_install: warning: Compatibility levels before 9 are deprecated (level 5 in 
> use)
> dh_install: warning: -s/--same-arch is deprecated; please use -a/--arch 
> instead
> dh_install: warning: This feature will be removed in compat 12.
>   cp --reflink=auto -a ./tools/u2boat/u2boat ./tools/u2spewfoo/u2spewfoo 
> debian/snort/usr/bin/
>   install -d debian/.debhelper/generated/snort
>   install -d debian/.debhelper/generated/snort-common
>   install -d debian/.debhelper/generated/snort-doc
>   install -d debian/.debhelper/generated/snort-rules-default
>   install -d debian/.debhelper/generated/snort-common-libraries
> dh_testdir -a
> dh_testroot -a
> dh_installdocs -a
> dh_installdocs: warning: Compatibility levels before 9 are deprecated (level 
> 5 in use)
>   cp --reflink=auto -a ./doc/AUTHORS debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/BUGS debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/CREDITS debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/NEWS debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/README debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/README.PLUGINS 
> debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/USAGE debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./doc/README.csv debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./RELEASE.NOTES debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./debian/my/snort_rules.html 
> debian/snort/usr/share/doc/snort
>   cp --reflink=auto -a ./debian/README.Maintainer 
> debian/snort/usr/share/doc/snort
>   chown -R 0:0 debian/snort/usr/share/doc
>   chmod -R u\+rw,go=rX debian/snort/usr/share/doc
>   install -p -m0644 debian/README.Debian 
> debian/snort/usr/share/doc/snort/README.Debian
>   install -p -m0644 debian/TODO 
> debian/snort/usr/share/doc/snort/TODO.Debian
>   install -p -m0644 debian/copyright 
> debian/snort/usr/share/doc/snort/copyright
>   install -d 
> debian/snort-common-libraries/usr/share/doc/snort-common-libraries
>   install -p -m0644 debian/copyright 
> debian/snort-common-libraries/usr/share/doc/snort-common-libraries/copyright
> dh_installexamples -a
> dh_installexamples: warning: Compatibility levels before 9 are deprecated 
> (level 5 i

Bug#955648: marked as done (seqsero: FTBFS: build-dependency not installable: sra-toolkit)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:50:20 +0200
with message-id <20200414085020.gk18...@an3as.eu>
and subject line Re: Bug#955648: seqsero: FTBFS: build-dependency not 
installable: sra-toolkit
has caused the Debian Bug report #955648,
regarding seqsero: FTBFS: build-dependency not installable: sra-toolkit
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.)


-- 
955648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqsero
Version: 1.0.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-python, python3, bwa, 
> sra-toolkit, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-python, python3, bwa, 
> sra-toolkit, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [393 B]
> Get:5 copy:/<>/apt_archive ./ Packages [473 B]
> Fetched 1823 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: sra-toolkit but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/04/02/seqsero_1.0.1+dfsg-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi Lucas,

this seems to have been a temporary issue.  Seqsero builds fine and all
its (Build-)Depends are available.

> The full build log is available from:
>http://qa-logs.debian.net/2020/04/02/seqsero_1.0.1+dfsg-2_unstable.log

Since this log seem to have vanished I'm closing this bug.

Kind regards

Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#910452: marked as done (No report or readable logs)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#910452: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #910452,
regarding No report or readable logs
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.)


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

Hello,

i did use snort before and i always get an nice daily email with an report.
But in debian stretch i get nothing and in /var/log/snort i only get an 
unreadable logfile.
How can i read the logfile?

It seems that this entries in /etc/snort/snort.debian.conf/ are useless:
DEBIAN_SNORT_SEND_STATS="true"
DEBIAN_SNORT_STATS_RCPT="root"
DEBIAN_SNORT_STATS_THRESHOLD="1"

What must be done to get an daily report as email?

Thanks for any tip!
karsten


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (was /usr/doc/snort-doc)
   * debian/snort.logrotate: Created to install the logrotate file using
 debhelper
   * rename snort.cron.daily to snort-common.cron.daily so it is install
 in the snort-common package by debelper
   * debian/snort.preinst:
 - Instead of recursively changing the logdir change the logdir first
   and then all the files in it (if any) [lintian fix]
   * debian/snort-doc.docs: Remove documents that are already provided by the
 snort package
   * debian/{snort.init-d,snort.postinst}: Use /run instead of /var/run and
  place the PIDFILES under /run/snort, creating it if it is required.
  Also provide the pidfile location to the Snort program, otherwise it
  would be created in /var/log/snort/ (LP: #1006982)
   * debian/snort.init-d: Do not set a default value for DEBIAN_SNORT_HOME_NET,
 if it is not defined then the value is not passed over to Snort. This
 allows users to set an empty value and define the configuration in
 /etc/snort/snort.conf (or /etc/snort/snort.$interface.conf instead.
 (LP: #566543)
   * debian/copyright: Update list of maintainers as well as copyright holders
   * debian/patches/documentation_debian: Create a patch to document Debian
 specific changes and configuration (e.g. alert and logging) describing
 how to read the Snort logs (Closes: 910452)
   * de

Bug#861842: marked as done (snort 2.9.7 is EOL upstream)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#861842: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #861842,
regarding snort 2.9.7 is EOL upstream
to be marked as done.

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

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


-- 
861842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snort
Version: 2.9.7.0-5
Severity: grave
Justification: renders package unusable

Dear maintainer,

The version of snort in Debian testing/sid has reached EOL in March [0], making 
it difficult to provide security updates or rule updates over the lifecycle of
stretch. Since no newer version is packaged yet and stretch is deep into the
freeze, I suggest removing the package from stretch.

[0]
http://blog.snort.org/2017/03/snort-2976-is-end-of-life.html
https://snort.org/eol

Regards,
Lee

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (was /usr/doc/snort-doc)
   * debian/snort.logrotate: Created to install the logrotate file using
 debhelper
   * rename snort.cron.daily to snort-common.cron.daily so it is install
 in the snort-common package by debelper
   * debian/snort.preinst:
 - Instead of recursively changing the logdir change the logdir first
   and then all the files in it (if any) [lintian fix]
   * debian/snort-doc.docs: Remove documents that are already provided by the
 snort package
   * debian/{snort.init-d,snort.postinst}: Use /run instead of /var/run and
  place the PIDFILES under /run/snort, creating it if it is required.
  Also provide the pidfile location to the Snort program, otherwise it
  would be created in /var/log/snort/ (LP: #1006982)
   * debian/snort.init-d: Do not set a default value for DEBIAN_SNORT_HOME_NET,
 if it is not defined then the value is not passed over to Snort. This
 allows users to set an empty value and define the configuration in
 /etc/snort/snort.conf (or /etc/snort/snort.$interface.conf instead.
 (LP: #566543)
   * debian/copyright: Update list of maintainers as well as copyright holders
   * debian/patches/documentation_debian: Create

Bug#827593: marked as done (new upstream (2.9.8.3))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#827593: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #827593,
regarding new upstream (2.9.8.3)
to be marked as done.

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

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


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

Package: snort

Hi,

it would be nice if you could upgrade to the current upstream release 
(2.9.8.3).


Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (was /usr/doc/snort-doc)
   * debian/snort.logrotate: Created to install the logrotate file using
 debhelper
   * rename snort.cron.daily to snort-common.cron.daily so it is install
 in the snort-common package by debelper
   * debian/snort.preinst:
 - Instead of recursively changing the logdir change the logdir first
   and then all the files in it (if any) [lintian fix]
   * debian/snort-doc.docs: Remove documents that are already provided by the
 snort package
   * debian/{snort.init-d,snort.postinst}: Use /run instead of /var/run and
  place the PIDFILES under /run/snort, creating it if it is required.
  Also provide the pidfile location to the Snort program, otherwise it
  would be created in /var/log/snort/ (LP: #1006982)
   * debian/snort.init-d: Do not set a default value for DEBIAN_SNORT_HOME_NET,
 if it is not defined then the value is not passed over to Snort. This
 allows users to set an empty value and define the configuration in
 /etc/snort/snort.conf (or /etc/snort/snort.$interface.conf instead.
 (LP: #566543)
   * debian/copyright: Update list of maintainers as well as copyright holders
   * debian/patches/documentation_debian: Create a patch to document Debian
 specific changes and configuration (e.g. alert and logging) describing
 how to read the Snort logs (Closes: 910452)
   * debian/patches/config: Change the configuration to also log an alert file
 log and log also alerts to Syslog
   * debian/snort.config:
   - Try to find the system network interface instead of using a default
 (eth0) name. This should make unattended package installation work for
 those systems indepently of how their network names are defined (e.g.
 laptops).  This was suggested by Thomas d'Otreppe  in the Ubuntu bugs
 and based on the number of bugs in Ubuntu appears to be a fairly
 common need.
 (LP: #996450, #958

Bug#956575: marked as done (sibelia: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:50:45 +
with message-id 
and subject line Bug#956575: fixed in sibelia 3.0.7+dfsg-3
has caused the Debian Bug report #956575,
regarding sibelia: binary-all FTBFS
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.)


-- 
956575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sibelia
Version: 3.0.7+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sibelia&arch=all&ver=3.0.7%2Bdfsg-2&stamp=1585348179&raw=0

...
   debian/rules override_dh_installman
make[1]: Entering directory '/<>'
dh_installman
mv debian/sibelia/usr/share/man/py/man1/C-Sibelia.1 
debian/sibelia/usr/share/man/man1/C-Sibelia.py.1
mv: cannot stat 'debian/sibelia/usr/share/man/py/man1/C-Sibelia.1': No such 
file or directory
make[1]: *** [debian/rules:20: override_dh_installman] Error 1
--- End Message ---
--- Begin Message ---
Source: sibelia
Source-Version: 3.0.7+dfsg-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated sibelia package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 10:29:51 +0200
Source: sibelia
Architecture: source
Version: 3.0.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 956575
Changes:
 sibelia (3.0.7+dfsg-3) unstable; urgency=medium
 .
   * Enable binary-all builds
 Closes: #956575
Checksums-Sha1:
 296ed4b42d6898c7a6b3ed43450d2de15e8a419f 2132 sibelia_3.0.7+dfsg-3.dsc
 88412f8aeaccc9d9f011c5da4db3637f95d49922 10240 
sibelia_3.0.7+dfsg-3.debian.tar.xz
 05f140d278467ec62ce28840c41b64aef884d657 15435 
sibelia_3.0.7+dfsg-3_source.buildinfo
Checksums-Sha256:
 f40cd1ae4ebec8a77b13120dd1d7632a3282bb463b50be82be19a9dcf76f5c6a 2132 
sibelia_3.0.7+dfsg-3.dsc
 bb7d1255911a04c84c953ff5d55c861386d3473069fbcc6bed9aaf29a06bccd5 10240 
sibelia_3.0.7+dfsg-3.debian.tar.xz
 2808610a61a14b59918d9f9510aa49a203704d76f181deab0b0f87c071981352 15435 
sibelia_3.0.7+dfsg-3_source.buildinfo
Files:
 55869abf4ff2d049b0e8fc8cd3536505 2132 science optional sibelia_3.0.7+dfsg-3.dsc
 388e525dada128486669834bc22336ff 10240 science optional 
sibelia_3.0.7+dfsg-3.debian.tar.xz
 f2ad35a501a1f00320ff6a584f712611 15435 science optional 
sibelia_3.0.7+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6Vdk0OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtE11A/+MkCCL8RBcX1hRlPoLz49gXGg+WtyegOKi0HV
zAtu0ZdcqUGuszP5H4mpbsZa75s98TBkE48cFjxvQE+o6d+pG56yQ2YVrp6uICuk
GWhWuoAk2kddQsxvYYipmW1ZFNpLlTkAAfpTuQHB/Pt0mmWJ085+dNO9veMsknSV
B1LCU6bp4TrW6FO2hqAi2S8RV/MiSR1ycX8kZMY17meBqcqRswJMHsrIpXzHNyd3
PLmzLzHjvKmNLKOFX/QU58k3mzlwS9DyhWQsTXwbpImEufns9TlAUVXr2K+1A6X9
haPFe4QmuIXVISyK+kCo8rDfcg3rGCS+FyNQEhnQtY4K8Dd3INl1HQvzneCiYOhr
2tzC5j4DhebEAZS6JO4xNHdGTGEiKKduf6hdXkBiRIsoz5JifamN/qWJ4sSePnkm
CldbWYcNPJoddvCDusaf1DTUolF7XZ0NpjT4SLAx0NkFLRbZzhmOShHxeFeXIWf0
J3R9rOYTzyuF/ITHT7TwmbgVC561dECITiVpye8SLUxvK3kzOoAO4MIcN9Qnz/7j
abtfw+wOZx5l3gFO9Xa6WMrZBMa6uIgeYvJ5BlmRdezphf/wK9zwqLi6wtAcF3+n
onhwCfRYKbL11ZjEb8L0OJ6cspMR+pZzI0nq8RB0DGdzfdlPQXj+StOHLkM6E2S6
w1zZm4g=
=cF6I
-END PGP SIGNATURE End Message ---

Bug#862100: marked as done (snort: Email alerts don't work in default config)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#862100: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #862100,
regarding snort: Email alerts don't work in default config
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.)


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

The default configuration of snort offers to setup an e-mail alert ... 
which will NEVER work in the default configuration, because the alerting
script only seems to work with textual log files, while the default config
only generates the binary unified2 format log file.

Nothing in the debconf prompting for the alert setup even hints that this
might be a problem, leading to a false sense of security by the
administrator installing the package.

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

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

Versions of packages snort depends on:
ii  adduser  3.115
ii  debconf [debconf-2.0]1.5.60
ii  libc62.24-10
ii  libdaq2  2.0.4-3+b1
ii  libdumbnet1  1.12-7+b1
ii  liblzma5 5.2.2-1.2+b1
ii  libpcap0.8   1.8.1-3
ii  libpcre3 2:8.39-3
ii  logrotate3.11.0-0.1
ii  net-tools1.60+git20161116.90da8a0-1
ii  rsyslog [system-log-daemon]  8.24.0-1
ii  snort-common 2.9.7.0-5
ii  snort-common-libraries   2.9.7.0-5
ii  snort-rules-default  2.9.7.0-5
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages snort recommends:
ii  iproute2  4.9.0-1

Versions of packages snort suggests:
pn  snort-doc  

-- Configuration Files:
/etc/default/snort changed [not included]

-- debconf information:
* snort/stats_treshold: 1
* snort/send_stats: true
* snort/interface: enp1s0
* snort/please_restart_manually:
* snort/address_range: 172.22.0.0/23
* snort/stats_rcpt: beech...@beechwoods.com
* snort/invalid_interface:
  snort/config_parameters:
* snort/options:
* snort/startup: boot
* snort/disable_promiscuous: false
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (wa

Bug#902554: marked as done (snort FTCBFS: configures for the build architecture)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:51:18 +
with message-id 
and subject line Bug#902554: fixed in snort 2.9.15.1-1
has caused the Debian Bug report #902554,
regarding snort FTCBFS: configures for the build architecture
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.)


-- 
902554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snort
Version: 2.9.7.0-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

snort fails to cross build from source, because it configures for the
build architecture. The easiest way of passing the relevant --host flag
is using dh_auto_configure. The attached patch implements that. It
doesn't make snort cross build as there are subsequent failures to be
sorted out. Please consider applying the patch anyway and close this bug
when doing so.

Helmut
diff --minimal -Nru snort-2.9.7.0/debian/changelog 
snort-2.9.7.0/debian/changelog
--- snort-2.9.7.0/debian/changelog  2015-06-30 00:55:04.0 +0200
+++ snort-2.9.7.0/debian/changelog  2018-06-27 19:29:21.0 +0200
@@ -1,3 +1,11 @@
+snort (2.9.7.0-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Improve cross buiding: Let dh_auto_configure pass --host to ./configure.
+(Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Jun 2018 19:29:21 +0200
+
 snort (2.9.7.0-5) unstable; urgency=medium
 
   * debian/control: Depend on perl, not perl-modules (Closes: #779126)
diff --minimal -Nru snort-2.9.7.0/debian/rules snort-2.9.7.0/debian/rules
--- snort-2.9.7.0/debian/rules  2014-12-12 01:55:55.0 +0100
+++ snort-2.9.7.0/debian/rules  2018-06-27 19:29:17.0 +0200
@@ -27,9 +27,8 @@
 
 export CFLAGS
 
-CONFFLAGS= --prefix=/usr \
+CONFFLAGS= \
--bindir=\$$\{exec_prefix\}/sbin \
-   --mandir=\$$\{exec_prefix\}/share/man \
--enable-zlib \
--enable-ipv6 \
--enable-gre \
@@ -76,7 +75,7 @@
dh_testdir
dh_autoreconf
 # Standard package configuration:
-   ./configure $(CONFFLAGS) 
+   dh_auto_configure -- $(CONFFLAGS)
touch $@
 
 # Basic 'flavor' package 
--- End Message ---
--- Begin Message ---
Source: snort
Source-Version: 2.9.15.1-1
Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= 

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated snort 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 21:59:30 +0100
Source: snort
Architecture: source
Version: 2.9.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 816964 827593 861842 862100 902554 910452 952296
Changes:
 snort (2.9.15.1-1) unstable; urgency=medium
 .
   * Updated to latest upstream release (Closes: #861842, #827593)
 (LP: #1669257)
   * debian/patches: Refresh patches with changes of new release
  - config: Update location of libraries from /usr/lib/snort_dynamicengine/
to usr/lib/i386-linux-gnu/snort_dynamicengine/
   * debian/compat Use debhelper compatibility version 12
   * debian/rules: Switch to dh
 - Fixes build errors with the PDF file (Closes: #952296)
 - Fixes configure for the build architecture (Closes: #902554)
   * debian/control:
 - Update sources to point to new repository in Salsa
 - Add additional libraries required by the latest upstream
 - Add dependency on lsb-base in snort as it ships a init.d file
 - Move to https homepage
   * debian/{snort-doc.doc-base.manual,snort-doc.doc-base.paper}: Adjust
 file to new location of file at /usr/doc/snort (was /usr/doc/snort-doc)
   * debian/snort.logrotate: Created to install the logrotate file using
 debhelper
   * rename snort.cron.daily to snort-common.cron.daily so it is install
 in the snort-common package by debelper
   * debian/snort.preinst:
 - Instead of recursively changing the logdir

Bug#866051: marked as done (fonts-guru-extra: upgrade does not clean up obsoleted directories)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:22:52 +
with message-id 
and subject line Bug#866051: fixed in fonts-guru-extra 2.0-5
has caused the Debian Bug report #866051,
regarding fonts-guru-extra: upgrade does not clean up obsoleted directories
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.)


-- 
866051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-guru-extra
Version: 2.0-4
Severity: normal


This is almost certainly related to https://bugs.debian.org/854166
which reported a related issue of which the fix almost certainly
created this one.

Today's Sid upgrade brought in a change from having a directory to
having a file of the same name.  However this is not handled by the
package.

-/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf/65-0-fonts-guru-extra.conf
+/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf

This results in the following:

drwxr-xr-x 2 root root 4096 Aug 24  2015 65-0-fonts-beng-extra.conf/
-rw-r--r-- 1 root root 1064 Aug 22  2012 65-0-fonts-beng-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Nov 13  2014 65-0-fonts-deva-extra.conf/
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Jul 31  2016 65-0-fonts-gujr-extra.conf/
-rw-r--r-- 1 root root  687 Jan  7  2012 65-0-fonts-gujr-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Jun 16  2013 65-0-fonts-guru-extra.conf/
-rw-r--r-- 1 root root  689 Feb 25  2012 65-0-fonts-guru-extra.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Sep 12  2016 65-0-fonts-orya-extra.conf/
-rw-r--r-- 1 root root  678 Feb 25  2012 65-0-fonts-orya-extra.conf.dpkg-new

Obviously the goal was to have this instead:

-rw-r--r-- 1 root root 1064 Aug 22  2012 65-0-fonts-beng-extra.conf
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf
-rw-r--r-- 1 root root  687 Jan  7  2012 65-0-fonts-gujr-extra.conf
-rw-r--r-- 1 root root  689 Feb 25  2012 65-0-fonts-guru-extra.conf
-rw-r--r-- 1 root root  678 Feb 25  2012 65-0-fonts-orya-extra.conf

Thank you for maintaining these packages in Debian.

Bob

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fonts-guru-extra
Source-Version: 2.0-5
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated fonts-guru-extra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:32:45 +0530
Source: fonts-guru-extra
Architecture: source
Version: 2.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 854165 866051
Changes:
 fonts-guru-extra (2.0-5) unstable; urgency=low
 .
   * Team upload.
   * debian/preinst:
 + Handle migration of conffile from wrong subdir. Patch from Ubuntu.
   (Closes: #854165, #866051)
   * Added debian/gitlab-ci.yml.
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Updated Vcs-* URLs.
 + Removed Homepage.
 + Switched to debhelper-compat.
 + Added 'Rules-Requires-Root' field.
 + Set maintainer to Debian Fonts Task Force.
   * Updated debian/copyright.
Checksums-Sha1:
 c42dd17b026e4b103f7bc536d8ca0b280af2d546 1930 fonts-guru-extra_2.0-5.dsc
 3dbe7d29089028749a3869e996aeacdfb628ee63 2828 
fonts-guru-extra_2.0-5.debian.tar.xz
Checksums-Sha256:
 b49a3653b2f07dc087df7865b24efaed6dbf94820b54ccbead8c5640e26ec3c0 1930 
fonts-guru-extra_2.0-5.dsc
 e4b51eeb0114108c3aa58d9a8e5cc2240b4610441c1d999b4e51d3b614614f19 2828 
fonts-guru-extra_2.0-5.debian.tar.xz
Files:
 26ef3e66949a64c33668e622183

Bug#854165: marked as done (fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:22:51 +
with message-id 
and subject line Bug#854165: fixed in fonts-guru-extra 2.0-5
has caused the Debian Bug report #854165,
regarding fonts-deva-extra: unneeded directory in /etc/fonts/conf.avail/
to be marked as done.

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

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


-- 
854165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-deva-extra
Version: 3.0-3
Severity: normal


Dear Maintainer,

this package (and several other ones maintained by you) creates directories in 
/etc/fonts/conf.avail/ and those directories contain only one file with the 
same name as the directory:

$ ls -l /etc/fonts/conf.avail/65-0-fonts--extra.conf
-rw-r--r-- 1 root root  684 Feb 25  2012 
/etc/fonts/conf.avail/65-0-fonts-telu-extra.conf

/etc/fonts/conf.avail/65-0-fonts-beng-extra.conf:
total 4
-rw-r--r-- 1 root root 1064 Aug 23  2015 65-0-fonts-beng-extra.conf

/etc/fonts/conf.avail/65-0-fonts-deva-extra.conf:
total 8
-rw-r--r-- 1 root root 5035 Nov  3  2012 65-0-fonts-deva-extra.conf

/etc/fonts/conf.avail/65-0-fonts-gujr-extra.conf:
total 4
-rw-r--r-- 1 root root 687 Jan  7  2012 65-0-fonts-gujr-extra.conf

/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf:
total 4
-rw-r--r-- 1 root root 689 Feb 25  2012 65-0-fonts-guru-extra.conf

/etc/fonts/conf.avail/65-0-fonts-orya-extra.conf:
total 4
-rw-r--r-- 1 root root 678 Feb 25  2012 65-0-fonts-orya-extra.conf


This is most probably an error and it would be simpler and more coherent with 
other font packages to remove those extra directories.


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

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

Versions of packages fonts-deva-extra depends on:
ii  dpkg 1.18.21
ii  fonts-gargi  2.0-4
ii  fonts-sarai  1.0-2

fonts-deva-extra recommends no packages.

fonts-deva-extra suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message ---
Source: fonts-guru-extra
Source-Version: 2.0-5
Done: Kartik Mistry 

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated fonts-guru-extra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 12:32:45 +0530
Source: fonts-guru-extra
Architecture: source
Version: 2.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 854165 866051
Changes:
 fonts-guru-extra (2.0-5) unstable; urgency=low
 .
   * Team upload.
   * debian/preinst:
 + Handle migration of conffile from wrong subdir. Patch from Ubuntu.
   (Closes: #854165, #866051)
   * Added debian/gitlab-ci.yml.
   * debian/control:
 + Updated Standards-Version to 4.5.0
 + Updated Vcs-* URLs.
 + Removed Homepage.
 + Switched to debhelper-compat.
 + Added 'Rules-Requires-Root' field.
 + Set maintainer to Debian Fonts Task Force.
   * Updated debian/copyright.
Checksums-Sha1:
 c42dd17b026e4b103f7bc536d8ca0b280af2d546 1930 fonts-guru-extra_2.0-5.dsc
 3dbe7d29089028749a3869e996aeacdfb628ee63 2828 
fonts-guru-extra_2.0-5.debian.tar.xz
Checksums-Sha256:
 b49a3653b2f07dc087df7865b24efaed6dbf94820b54ccbead8c5640e26ec3c0 1930 
fonts-guru-extra_2.0-5.dsc
 e4b51eeb0114108c3aa58d9a8e5cc2240b4610441c1d999b4e51d3b614614f19 2828 
fonts-guru-extra_2.0-5.debian.tar.xz
Files:
 26ef3e66949a64c33668e622183f4369 1930 fonts optional fonts-guru-extra_2.0-5.dsc
 2c59911dd191635c48644c20f2a90381 2828 fonts optional 
fonts-guru-extra_2.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl6VbMoACgkQAsHT8ng6
pN7aEA/+JxGOw

Bug#820060: marked as done (python-biom-format: broken on big-endian architectures)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 10:19:13 +0200
with message-id <20200414081913.gi18...@an3as.eu>
and subject line Re: Debian Bug#820060: python-biom-format: broken on 
big-endian architectures
has caused the Debian Bug report #820060,
regarding python-biom-format: broken on big-endian architectures
to be marked as done.

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

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


-- 
820060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-biom-format
Version: 2.1.4+dfsg-1
Severity: serious

As seen at http://buildd.debian.org/python-biom-format, this package fails
to build on all big-endian architectures in the archive (mips, powerpc,
s390x).  While this build failure has only appeared with the upload of
2.1.5+dfsg-1, this is not a regression in that version of the upstream
source; instead, the package was already broken, but what has changed now is
that a new version of dh-python correctly finds the tests and runs them at
build time where before dh_auto_test was silently passing.

I'm not sure if this points to breakage in python-biom-format, or in
something lower down the stack that it depends on.  I've confirmed that
python-numpy autopkgtests run ok on powerpc (except for openblas - and the
tests can't be run on s390x because openblas is not built for that
architecture), and h5py autopkgtests run ok on s390x.  python-scipy's
autopkgtests fail with SIGABRT on both powerpc and s390x, maybe related,
maybe not (test_random_complex_exact (test_basic.TestLstsq) ... *** Error in
`python3.5': free(): invalid pointer: 0x1172c2a8 ***).

And hdf5 itself doesn't have any autopkgtests, and any build-time tests
pass; and h5py in any case should catch any bugs with its own testsuite
before python-biom-format.

So it seems most likely that this is a bug in python-biom-format itself
rather than any of its dependencies, thus assigning here.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi Michael,

On Sun, Apr 12, 2020 at 02:34:26PM +0200, Michael Crusoe wrote:
> I'm not seeing a successful build on big-endian. Of the offically supported
> architectures, only s390x is big-endian and it's build is disabled.

Its disabled due to:

$ git diff 54aa8de1^..54aa8de1
diff --git a/debian/changelog b/debian/changelog
index a105f58..5ad5459 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-biom-format (2.1.5+dfsg-4) UNRELEASED; urgency=medium
+
+  * Restrict build to those architectures not affected by h5py issue
+  https://github.com/h5py/h5py/issues/428
+
+ -- Andreas Tille   Mon, 12 Sep 2016 08:57:29 +0200
+
 python-biom-format (2.1.5+dfsg-3) unstable; urgency=medium
 
   * Use sphinxdoc
diff --git a/debian/control b/debian/control
index e4fdae6..69ded5f 100644
--- a/debian/control
+++ b/debian/control
@@ -35,7 +35,7 @@ Homepage: http://biom-format.org/
 X-Python-Version: >= 2.6
 
 Package: python-biom-format
-Architecture: any
+Architecture: any-amd64 any-arm64 armel armhf any-i386 any-mips64el mipsel 
any-ppc64el
 Depends: ${python:Depends},
  ${misc:Depends},
  ${shlibs:Depends}
@@ -64,7 +64,7 @@ Description: Biological Observation Matrix (BIOM) format 
(Python 2)
  This package provides the BIOM format library for the Python 2 interpreter.
 
 Package: python3-biom-format
-Architecture: any
+Architecture: any-amd64 any-arm64 armel armhf any-i386 any-mips64el mipsel 
any-ppc64el
 Depends: ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends}


Since

https://github.com/h5py/h5py/issues/428 

is not marked as fixed I think Liubov is correct and I hereby close this
bug.

Thanks for pointing this out Liubov

  Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#956595: marked as done (autopkgtest for puppet-beaker is failing with Could not find 'rb-readline' (~> 0.5.3))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 07:48:34 +
with message-id 
and subject line Bug#956595: fixed in puppet-beaker 4.21.0-2
has caused the Debian Bug report #956595,
regarding autopkgtest for puppet-beaker is failing with Could not find 
'rb-readline' (~> 0.5.3)
to be marked as done.

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

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


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

Package: puppet-beaker
Version: 4.21.0-1
Severity: serious
Justification: missing runtime dependency

GEM_PATH= ruby2.7 -e gem\ \"beaker\"
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:311:in `to_specs': Could not 
find 'rb-readline' (~> 0.5.3) among 87 total gem(s) 
(Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0', 
execute `gem env` for more information
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in 
activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
`activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'

from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
from -e:1:in `'
--- End Message ---
--- Begin Message ---
Source: puppet-beaker
Source-Version: 4.21.0-2
Done: Utkarsh Gupta 

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

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

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated puppet-beaker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Apr 2020 13:04:41 +0530
Source: puppet-beaker
Architecture: source
Version: 4.21.0-2
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Utkarsh Gupta 
Closes: 956595
Changes:
 puppet-beaker (4.21.0-2) unstable; urgency=medium
 .
   * Team upload
   * Add patch to fix autopkgtest (Closes: #956595)
   * Tighten dependency on ruby-thor
   * Trim trailing whitespace in d/rules
Checksums-Sha1:
 5cb46e4dbf38fab115efb70cdb9b7f04b774fa56 2288 puppet-beaker_4.21.0-2.dsc
 ecda29c9c3483d6988170516be3eb504ed786b62 2684 
puppet-beaker_4.21.0-2.debian.tar.xz
 a8e0e04bbfe7af3617b569d6adfbedb1a5b2d895 9825 
puppet-beaker_4.21.0-2_amd64.buildinfo
Checksums-Sha256:
 02b066d7d89b985ce0ff2aa0afcdb7d60127496605b47d9c743ed22b09b323d1 2288 
puppet-beaker_4.21.0-2.dsc
 16bfbb017b6d24fcffb46ce3d5149da5e91c0fe88198668f7a1980c32c252c91 2684 
puppet-beaker_4.21.0-2.debian.tar.xz
 7e911fc19b71a3579459402a665d37715171be27d6c7f772bbbf88898cd05178 9825 
puppet-beaker_4.21.0-2_amd64.buildinfo
Files:
 0fb2f0104a3b5aeb64ececac337e2ba2 2288 admin optional puppet-beaker_4.21.0-2.dsc
 21016a957e7a2125b00ce5c53bc41808 2684 admin optional 
puppet-beaker_4.21.0-2.debian.tar.xz
 d1eb1ae0750b1706dad7ed3bf9003b2a 9825 admin optional 
puppet-beaker_4.21.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl6VaEwTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLln1uEACBXW45Wc/KOt34Ib7xuNIrjNepMK5e
uQK6FttEBACN+eZsbBhhLKLWYLw5lTZhR0RcKR75NCcYgSze1fyWMt80/J+gF6QC
+t1j/NX8TTwbcotkH1GemMKskbRMKWGl/jfha/xd4HNeeg+y2aTZs5ID2PPz2574
psxVgtkhJbtkEcjEcJi4KZlYSkNfVdoqzwHiAogrqrPaemjfBr86lfnKow2fkgIg
Lx5hCA7gG57+8JIR76BOQce1FwfFeQFqRsBPFTngzIGHaU4OT7WrR6UvtRXGTJA+
q7ItvRlFsGWuoVI51SGckObXx4VK8aS0BhE4iQ97S0nZoAWd+rh/bQS2HTAsjc6r
4xwv60d4tMfjNGr+4cHH83l/fxD5CZdgRBG8XRb17VhjoOVSeLI0m/4wmNN3Dchr
Zco+tUg2co+JfpdLUE6h0Nep5Tb3qmkwIOGz/C+UUEVqrrcx1hNCbLIZKGEcWFN9
KS2h+NZy8BSVPXCunYUoHCGu+wFmet4Ah0BOD+BltdJZ0+gsV/Xs5/IKo7gRkQvL
sgtg2rJ8yw+upYTncqeweEMfrfj20wA8GUEfTnHKSni6z5zV87h2TkOf+HcfVKE4
xnuB+AI33vuNwNAJNf0PH+WIUz38hz/LWZIUpEB5jsOo9lwmAw7tKKdL6GbH+Yn9
nmmd/wBtasZyHA==
=ON/u