Processed: RFS: xsd/4.0.0-8 -- XML Data Binding for C++

[Debian Bug Tracking System]

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

> close 956667
Bug #956667 [sponsorship-requests] RFS: xsd/4.0.0-8 -- XML Data Binding for C++
Marked Bug as done
> stop
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> close #956135
Bug #956135 [blueman] blueman   v. 2.0.8-1
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#899295: marked as done (python-cloudflare: Invalid address letsencrypt-de...@lists.alioth.debian.org in Uploaders: field)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 05:18:42 +
with message-id 
and subject line Bug#899295: fixed in python-cloudflare 2.6.5-1
has caused the Debian Bug report #899295,
regarding python-cloudflare: Invalid address 
letsencrypt-de...@lists.alioth.debian.org in Uploaders: field
to be marked as done.

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

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


-- 
899295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cloudflare
Version: 2.0.4-1
Severity: normal
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-uploaders

Dear maintainer of the python-cloudflare package,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package python-cloudflare since the list address
letsencrypt-de...@lists.alioth.debian.org used in the Uploaders: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time ago.
Therefore your package now has an invalid address in the Uploaders:
list. Please fix this since when convient.

Your options:

* Upload another version with that address removed or replaced,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
letsencrypt-de...@lists.alioth.debian.org is 17.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-cloudflare
Source-Version: 2.6.5-1
Done: Harlan Lieberman-Berg 

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated 
python-cloudflare 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 00:51:30 -0400
Source: python-cloudflare
Architecture: source
Version: 2.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
Changed-By: Harlan Lieberman-Berg 
Closes: 899295
Changes:
 python-cloudflare (2.6.5-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Harlan Lieberman-Berg ]
   * New upstream version 2.6.5
   * Switch to debhelper 12
   * Update S-V to 4.5, add R-R-R
   * Update emails from lists.alioth.debian.org to tracker.debian.org
 (Closes: #899295)
   * Add manual smoke test.
Checksums-Sha1:
 a93c37442f58edaae607e2fda2a2b15009d08c49 2650 python-cloudflare_2.6.5-1.dsc
 b9b073382f957cde6f5d19ccdf430e5b41fb94ae 59582 
python-cloudflare_2.6.5.orig.tar.gz
 7102c157e92f2c1d7e454098f3bf0c1b50b7d36b 858 
python-cloudflare_2.6.5.orig.tar.gz.asc
 8b5ac5d468df05370159033d0d1d8aebbcb01fe7 5616 
python-cloudflare_2.6.5-1.debian.tar.xz
 62efbb41834acca432e5f4062a504d3736589da9 6606 
python-cloudflare_2.6.5-1_amd64.buildinfo
Checksums-Sha256:
 adab4ff626fc10b0f6fcc4f9eb48f9aed34acb29132ee571a72540513554c039 2650 
python-cloudflare_2.6.5-1.dsc
 4463d5f2927338384169315f34c2a8ac0840075b59489f8d1d773b91caba6c39 59582 
python-cloudflare_2.6.5.orig.tar.gz
 cbb63b3ab44cddcc78ea072ef757f100b87a459ab8774dc8b6e769b1221afb4a 858 
python-cloudflare_2.6.5.orig.tar.gz.asc
 71f17be58d09fdefc7151fd86af566b2983a195ba946138f77f90d2c1

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 05:03:45 +
with message-id 
and subject line Bug#866049: fixed in fonts-deva-extra 3.0-5
has caused the Debian Bug report #866049,
regarding fonts-deva-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.)


-- 
866049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-deva-extra
Version: 3.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 to 2.0-5 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-deva-extra.conf/65-0-fonts-deva-extra.conf
+/etc/fonts/conf.avail/65-0-fonts-deva-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)

Versions of packages fonts-deva-extra depends on:
ii  dpkg  1.18.24

Versions of packages fonts-deva-extra recommends:
ii  fonts-gargi  2.0-4
ii  fonts-sarai  1.0-2

fonts-deva-extra suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fonts-deva-extra
Source-Version: 3.0-5
Done: Kartik Mistry 

We believe that the bug you reported is fixed in the latest version of
fonts-deva-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-deva-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: Mon, 13 Apr 2020 21:46:10 +0530
Source: fonts-deva-extra
Architecture: source
Version: 3.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force 
Changed-By: Kartik Mistry 
Closes: 866049
Changes:
 fonts-deva-extra (3.0-5) unstable; urgency=low
 .
   * Team upload.
   * Added debian/gitlab-ci.yml.
   * debian/control:
 + Set maintainer to Debian Fonts Task Force.
 + Updated Standards-Version to 4.5.0
 + Updated Vcs-* URLs.
 + Removed Homepage.
 + Switched to debhelper-compat.
 + Added 'Rules-Requires-Root' field.
   * Updated debian/copyright.
   * debian/rules:
 + Do not use custom compression setting.
   * debian/preinst:
 + Handle migration of conffile from wrong subdir. Patch from Ubuntu.
   (Closes: #866049)
Checksums-Sha1:
 553a6b1a85f41bba71fdba53aa906c681ee9ebd2 1933 fonts-deva-extra_3.0-5.dsc
 0eb474da53f6df629a77375bb0858ae27e320df5 3112 
fonts-deva-extra_3.0-5.debian.tar.x

Bug#938750: marked as done (u-msgpack-python: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 05:04:27 +
with message-id 
and subject line Bug#938750: fixed in u-msgpack-python 2.3.0-2
has caused the Debian Bug report #938750,
regarding u-msgpack-python: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:u-msgpack-python

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

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

We believe that the bug you reported is fixed in the latest version of
u-msgpack-python, 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 u-msgpack-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 22:47:02 -0400
Source: u-msgpack-python
Architecture: source
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938750
Changes:
 u-msgpack-python (2.3.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938750
Checksums-Sha1:
 2a9047367623c9eed5f65dfd9ce22e79c0b1e38b 2060 u-msgpack-python_2.3.0-2.dsc
 b12fcef535e86bdd114e6c1a56e143571cf6b588 11644 
u-msgpack-python_2.3.0.orig.tar.gz
 ca7f5baa21f9f8a199a2c88ee1ecece7ea070472 2064 
u-ms

Bug#937558: marked as done (pytest: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 05:04:16 +
with message-id 
and subject line Bug#937558: fixed in pytest 4.6.9-3
has caused the Debian Bug report #937558,
regarding pytest: 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.)


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

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: pytest
Source-Version: 4.6.9-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
pytest, 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 pytest 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 00:44:22 -0400
Source: pytest
Architecture: source
Version: 4.6.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937558
Changes:
 pytest (4.6.9-3) unstable; urgency=medium
 .
   * debian/control
 - decorate python3-twisted with nocheck, as it's only used by unittests
   * Drop python2 support; Closes: #937558
Checksums-Sha1:
 daaccda56fb46f772a2c38210ab5f82950f8bcee 2818 pytest_4.6.9-3.dsc
 1571ab4be107a5a1d368445285674f7a86161a72 11768 pytest_4.6.9-3.debian.tar.xz
 294cdc5b89d088eda4bc5d1c40f8c882adade5af 8273 pytest_4.6.9-3_source.buildinfo
Checksums-Sha256:
 8eee6ef2446be3fa449629d85628ec8805dbd1a900267fa201bd4e479fd8f2aa 2818 
pytest_4.6.9-3.dsc
 f270df77df40d500bf2d6feabbc588c93c7a1d41f4c0d2d6dab168bef8f8859d 11768 
pytest_4.6.9-3.debian.tar.xz
 d42abe48b7b913d3249ba62f53cba9fa0ff8943f9c55ef86e9f9cb44e3c14167 8273 
pytest_4.6.9-3_source.buildinfo
Files:
 869a35fb17035e

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 03:05:00 +
with message-id 
and subject line Bug#937758: fixed in python-flaky 3.6.1-3
has caused the Debian Bug report #937758,
regarding python-flaky: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-flaky

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-flaky
Source-Version: 3.6.1-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
python-flaky, 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-flaky package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 22:43:32 -0400
Source: python-flaky
Architecture: source
Version: 3.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937758
Changes:
 python-flaky (3.6.1-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937758
Checksums-Sha1:
 808da88b235ed2e02030de57cab2ca81ddcfd0b7 2114 python-flaky_3.6.1-3.dsc
 a3204941c8fce14fcad8b070f7150d71cd1e2aec 2484 
python-flaky_3.6.1-3.debian.tar.xz
 5618f1bc1c957f9683531e25e8125f77aa1f3a56 6980 
python-flaky_3.6.1-3_source.buildinfo
Checksums-Sha256:
 ba4c3132bbd1fd7b25cd63a8402bc4a5fd0dacf3de1bb1f29f4469fd9b63ce21 2114 
python-flaky_3.6.1-3.dsc
 f0613e9ed8e8d7e1ae3aee7aba01f24c71ca53f224dc2cfed45f25b047296be6 2484 
python-flaky_3.6.1-3.debian.tar.xz
 a658181c134e455f39434e6502fe1bb89e2a252e019984954ded9538e6f47027 6980 
python-flaky_3.6.1-3_source.buildinfo
Files:
 2ac288a6a878dce1dfad1

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:44 +
with message-id 
and subject line Bug#956645: Removed package(s) from unstable
has caused the Debian Bug report #937844,
regarding python-ipcalc: 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.)


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

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.99.0-3.1+rm

Dear submitter,

as the package python-ipcalc 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/956645

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#945271: marked as done (O: python-ipcalc -- Python IP subnet calculator)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:44 +
with message-id 
and subject line Bug#956645: Removed package(s) from unstable
has caused the Debian Bug report #945271,
regarding O: python-ipcalc -- Python IP subnet calculator
to be marked as done.

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

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


-- 
945271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ipcalc
Version: 1.99.0-3.1
Severity: important

Hi community,

I'm going to orphan this package.

TL;DR I'm fine to have this package removed from the debian project.
IMHO it's dead and will not come back to life.

sshfp is the only package having python-ipcalc as a dependency, but this
code has been touched last time 2015. So it is pure python2 and will
probably be also removed soon.

I don't recommend to use python-ipcalc for any projects. It is old and
having all the drawbacks you have when maintaining python2 and python3
support at the same time.
Also upstream is looking dead. There are open issues since years and
there was only one commit in the last two years.

Cheers
Florian

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

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

Versions of packages python-ipcalc depends on:
ii  python  2.7.13-2

python-ipcalc recommends no packages.

python-ipcalc suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 1.99.0-3.1+rm

Dear submitter,

as the package python-ipcalc 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/956645

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#956651: marked as done (RM: backports.functools-lru-cache -- ROM; python2-only; backport of a python3.3 module; no rdeps)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:54:15 +
with message-id 
and subject line Bug#956651: Removed package(s) from unstable
has caused the Debian Bug report #956651,
regarding RM: backports.functools-lru-cache -- ROM; python2-only; backport of a 
python3.3 module; no rdeps
to be marked as done.

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

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


-- 
956651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

backports.functools-lru-cache |  1.5-3 | source
pypy-backports.functools-lru-cache |  1.5-3 | all
python-backports.functools-lru-cache |  1.5-3 | all

--- Reason ---
ROM; python2-only; backport of a python3.3 module; no rdeps
--

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/956651

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#936179: marked as done (backports.functools-lru-cache: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:54:20 +
with message-id 
and subject line Bug#956651: Removed package(s) from unstable
has caused the Debian Bug report #936179,
regarding backports.functools-lru-cache: 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.)


-- 
936179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:backports.functools-lru-cache
Version: 1.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:backports.functools-lru-cache

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

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

Dear submitter,

as the package backports.functools-lru-cache 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/956651

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#956622: marked as done (RM: drobo-utils -- RoQA; Depends on Python 2, dead upstream)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:51:57 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #956622,
regarding RM: drobo-utils -- RoQA; Depends on Python 2, dead upstream
to be marked as done.

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

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


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

Please remove drobo-utils. It depends on Python 2 and
https://github.com/petersilva/drobo-utils states:

| Is it Still Supported ?
| Not really. I no longer have any hardware to test with, so cannot
| validate anything. I switched to QNAP instead, which was more
| appropriate for my needs. The package is python2 and will never
| be ported to python3

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

drobo-utils | 0.6.1+repack-2 | source, all

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

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

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

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

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

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

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#956623: marked as done (RM: ibniz -- RoQA; Depends on Python 2, dead upstream, unmaintained)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:21 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #956623,
regarding RM: ibniz -- RoQA; Depends on Python 2, dead upstream, unmaintained
to be marked as done.

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

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


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

Please remove ibniz. It depends on Python 2, is dead upstream (last
commit eight years ago) and the last (and only) upload was in 2013.

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

 ibniz | 1.18-1 | source
 ibniz |  1.18-1+b1 | amd64, arm64, armel, armhf, i386, mipsel

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:49 +
with message-id 
and subject line Bug#956642: Removed package(s) from unstable
has caused the Debian Bug report #938189,
regarding python-sptest: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-sptest

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

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

Dear submitter,

as the package python-sptest 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/956642

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#956645: marked as done (RM: python-ipcalc -- RoQA; Depends on Python 2, no reverse deps, orphaned)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:37 +
with message-id 
and subject line Bug#956645: Removed package(s) from unstable
has caused the Debian Bug report #956645,
regarding RM: python-ipcalc -- RoQA; Depends on Python 2, no reverse deps, 
orphaned
to be marked as done.

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

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


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

Please remove python-ipcalc. It depends on Python 2, there are no reverse deps,
it's orphaned and the former maintainer (CCed) suggested it's removal in 
#945271.

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

python-ipcalc | 1.99.0-3.1 | source, all

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

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/956645

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#592010: marked as done (python-xmpp: Please, update to 0.5.0rc1)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #592010,
regarding python-xmpp: Please, update to 0.5.0rc1
to be marked as done.

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

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


-- 
592010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: wishlist

Hi,
Please, could you update the package to the latst available version,
namely xmpppy 0.5.0rc1.
I'd like to use the anonymous connection feature of that version, so I
can package another software for debian.

Thank you !

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

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

Versions of packages python-xmpp depends on:
ii  python2.6.5-11   interactive high-level object-orie
ii  python-central0.6.16 register and build utility for Pyt

Versions of packages python-xmpp recommends:
ii  python-dnspython  1.8.0-1DNS toolkit for Python

python-xmpp suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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#725005: marked as done (ibniz: minor typo in package description (s/Mainsteam/Mainstream/))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:29 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #725005,
regarding ibniz: minor typo in package description (s/Mainsteam/Mainstream/)
to be marked as done.

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

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


-- 
725005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibniz
Version: 1.18-1
Severity: wishlist
Tags: patch

The package description contains the line:

  Mainsteam software engineering aspects are considered totally irrelevant.
^
Missing letter.

-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru ibniz-1.18.pristine/debian/control ibniz-1.18/debian/control
--- ibniz-1.18.pristine/debian/control	2013-09-23 02:36:56.0 +0100
+++ ibniz-1.18/debian/control	2013-09-30 13:17:26.687229303 +0100
@@ -15,5 +15,5 @@
  IBNIZ is a virtual machine designed for extremely compact low-level
  audiovisual programs. The leading design goal is usefulness as a
  platform for demoscene productions, glitch art and similar projects.
- Mainsteam software engineering aspects are considered totally
+ Mainstream software engineering aspects are considered totally
  irrelevant.
--- End Message ---
--- Begin Message ---
Version: 1.18-1+rm

Dear submitter,

as the package ibniz 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/956623

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#935078: marked as done (Wrong name in DroboIOctl.py)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #935078,
regarding Wrong name in DroboIOctl.py
to be marked as done.

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

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


-- 
935078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drobo-utils
Version: 0.6.1+repack-2
Followup-For: Bug #614830

Dear Maintainer,

Detection of Drobo storage does not work.
The name in DroboIOctl.py is still wrong.

if ( id[4].startswith("TRUSTED") or id[4].startswith("DROBO") )
that line should reflect Drobo as name and not DROBO.

this seems to be fixed uppstream in the drobo-utils-0.6.2 version.

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

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

Versions of packages drobo-utils depends on:
ii  python  2.7.16-1

Versions of packages drobo-utils recommends:
ii  parted  3.2-25
ii  sudo1.8.27-1
--- End Message ---
--- Begin Message ---
Version: 0.6.1+repack-2+rm

Dear submitter,

as the package drobo-utils 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/956622

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#875459: marked as done (O: python-xmpp -- Python library for communication with XMPP (Jabber) servers)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #875459,
regarding O: python-xmpp -- Python library for communication with XMPP (Jabber) 
servers
to be marked as done.

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

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


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

The current maintainers of python-xmpp,
Alexey Nezhdanov , and Cosimo
Alfarano  are apparently not active anymore.
Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: python-xmpp
Binary: python-xmpp
Version: 0.4.1-cvs20080505.4
Maintainer: Alexey Nezhdanov 
Uploaders: Cosimo Alfarano 
Build-Depends: debhelper (>= 5.0.37.2)
Build-Depends-Indep: python (>= 2.6.6-3~)
Architecture: all
Standards-Version: 3.8.0
Format: 1.0
Files:
 5d50f6c589fd87632ad3d69d2c0a0f42 1790 python-xmpp_0.4.1-cvs20080505.4.dsc
 ca36d685643f2c56ab07323a09ece9e4 473698 python-xmpp_0.4.1.orig.tar.gz
 bd26b5f0a9f1ac7750976be504307742 6268 python-xmpp_0.4.1-cvs20080505.4.diff.gz
Checksums-Sha256:
 ec1e75fef25287aeff0bba244ab808ced294dbf3c98057c00bc6ca3426dd6df1 1790 
python-xmpp_0.4.1-cvs20080505.4.dsc
 1724d3ffd3210b3ca48e218954d8c2c10821bce1d0f5c66ec3e70de6389b38eb 473698 
python-xmpp_0.4.1.orig.tar.gz
 0918c4f700dd6a129eeca23a44ff98ca21ded05df0ac0a50d46e6e1ac630f5e7 6268 
python-xmpp_0.4.1-cvs20080505.4.diff.gz
Package-List: 
 python-xmpp deb python optional arch=all
Directory: pool/main/p/python-xmpp
Priority: source
Section: python

Package: python-xmpp
Version: 0.4.1-cvs20080505.4
Installed-Size: 4431
Maintainer: Alexey Nezhdanov 
Architecture: all
Replaces: python2.3-xmpp, python2.4-xmpp
Depends: python (>= 2.7), python (<< 2.8)
Recommends: python-dnspython | python-dnspython
Conflicts: jabber-irc (<< 0.2), python2.3-xmpp, python2.4-xmpp
Description: Python library for communication with XMPP (Jabber) servers
Description-md5: e3950480fe48cbeb66024e9275785e7f
Tag: devel::lang:python, devel::library, implemented-in::python,
 protocol::jabber
Section: python
Priority: optional
Filename: pool/main/p/python-xmpp/python-xmpp_0.4.1-cvs20080505.4_all.deb
Size: 265040
MD5sum: 9236828acd0375537a0b1ea76882a09f
SHA256: 778281fb914ed1bc8710a460dbf4f98d22948e58aa8b72ec3d252c85d7578e2f


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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#956644: marked as done (RM: python-xmpp -- RoQA; Depends on Python 2, dead upstream, orphaned/unmaintained)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:08 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #956644,
regarding RM: python-xmpp -- RoQA; Depends on Python 2, dead upstream, 
orphaned/unmaintained
to be marked as done.

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

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


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

Please remove python-xmpp. It's dead upstream, depends on Python 2 and orphaned
since 2017 without an adopter.

There's one reverse dependency (dvcs-autosync), but it's being ported away from
python-xmpp (936459) and it's RC-buggy and dropped from testing, so seem fair
enough to not block the removal of python-xmpp with it.

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

python-xmpp | 0.4.1-cvs20080505.4 | source, all

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

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

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

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

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

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

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#869906: marked as done (python-xmpp: dns resolver throws exception)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #869906,
regarding python-xmpp: dns resolver throws exception
to be marked as done.

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

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


-- 
869906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.4
Severity: important
Tags: patch



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

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

Versions of packages python-xmpp depends on:
ii  python  2.7.9-1

Versions of packages python-xmpp recommends:
ii  python-dnspython  1.12.0-1

python-xmpp suggests no packages.

-- no debconf information


When connecting to a xmpp server the library prints out a dns exception
error which can be tracked down to a wrong, maybe old, useage of the API.

The following patch fixes the issue:

--- transports.py   2015-03-21 15:36:01.0 +0100
+++ transports.py.fix   2017-07-27 16:00:04.913835081 +0200
@@ -77,7 +77,7 @@
 for query in possible_queries:
 try:
 if HAVE_DNSPYTHON:
-answers = [x for x in dns.resolver.query(query,
'SRV')]
+answers = [x for x in dns.resolver.query(query,
rdtype=dns.rdatatype.SRV)]
 if answers:
 host = str(answers[0].target)
 port = int(answers[0].port)



Kind Regards,
Markus Wigge
--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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#799453: marked as done (ibniz: building with DEB_BUILD_OPTIONS=nostrip still strips debug symbols)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:29 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #799453,
regarding ibniz: building with DEB_BUILD_OPTIONS=nostrip still strips debug 
symbols
to be marked as done.

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

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


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

When I was debugging #799408, I noticed that building with
DEB_BUILD_OPTIONS=nostrip [1] still strips debug symbols so I couldn't
get a proper backtrace. The fix for this appears to be to remove the -s
option from the compiler invocation in the upstream Makefile. I think
this should be fixed either upstream or with a patch (edit the Makefile
, run dpkg-source --commit, enter relevant metadata[2] and save the
patch) in the Debian package.

1. https://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules-options
2. http://dep.debian.net/deps/dep3/

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'),
(850, 'buildd-testing-proposed-updates'), (800, 'unstable'), (790,
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages ibniz depends on:
ii  libc62.19-19
ii  libsdl1.2debian  1.2.15-11
ii  libx11-6 2:1.6.3-1

ibniz recommends no packages.

ibniz suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Dear submitter,

as the package ibniz 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/956623

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#630525: marked as done (please ignore (configuration) caches for dnspython too)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #630525,
regarding please ignore (configuration) caches for dnspython too
to be marked as done.

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

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


-- 
630525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: important
Tags: upstream patch

Hi,

while using Rene's great dvcs-autosync, I stumbled over a bug in xmpppy (which
dvcs-autosync uses inderectly through python-jabberbot, both authors CC'ed).

I've booted my machine at the university and also started dvcs-autosync there.
At this time my /etc/resolv.conf contained 192.168.10.1 as the only available
nameserver. After finishing work I sent my laptop to sleep and went home where
I resumed the laptop. After some time I accidenally looked at the console
dvcs-autosync was running in, and it was flooded with the following message:

 An error occurred while looking up _xmpp-client._tcp.example.com
 ERROR:jabberbot:unable to connect to server example.com.

I checked my WiFi, my resolver and all was fine, I could get SRV for
_xmpp-client._tcp.example.com without any problems, just not in the running
dvcs-autosync process. Then I realized the nameserver change, as the ns at home
is running on 192.168.0.1 and xmpppy was still trying to query 192.168.10.1.

A short look at the code and in the dnspython docs resulted in the attached
patch. Yes, it creates a new dns.resolver.Resolver object every time, but who
cares? :)

FIY: checked 0.5.0rc1, the problem ain't fixed there.

FIY2: marking as important as it affects every "long" running process on a
roaming machine, which should be pretty common in 2011 ;)

Regards
Evgeni

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

Kernel: Linux 2.6.38-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

Versions of packages python-xmpp depends on:
ii  python2.6.6-14   interactive high-level object-orie
ii  python-central0.6.17 register and build utility for Pyt

Versions of packages python-xmpp recommends:
ii  python-dnspython  1.8.0-1DNS toolkit for Python

python-xmpp suggests no packages.

-- no debconf information
--- a/xmpp/transports.py2011-06-14 20:56:48.426738823 +0200
+++ b/xmpp/transports.py2011-06-14 21:07:57.900328939 +0200
@@ -77,7 +77,9 @@
 for query in possible_queries:
 try:
 if HAVE_DNSPYTHON:
-answers = [x for x in dns.resolver.query(query, 'SRV')]
+# new resolver, no cache of old configuration :)
+resolver = dns.resolver.Resolver()
+answers = [x for x in resolver.query(query, 'SRV')]
 if answers:
 host = str(answers[0].target)
 port = int(answers[0].port)
--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #938280,
regarding python-xmpp: 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.)


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

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

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

Dear submitter,

as the package python-xmpp 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/956644

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:29 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #943127,
regarding ibniz: 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.)


-- 
943127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibniz
Version: 1.18-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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.18-1+rm

Dear submitter,

as the package ibniz 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/956623

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#890574: marked as done (ibniz: unused Build-Depends: perl)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:29 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #890574,
regarding ibniz: unused Build-Depends: perl
to be marked as done.

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

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


-- 
890574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibniz
Version: 1.18-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

ibniz Build-Depends on perl, but it really only needs perl-base which
happens to be essential. Thus the perl dependency can simply be dropped.

The perl dependency happens to make ibniz Build-Depends
cross-unsatisfiable. If you really need perl as a build tool, please use
"perl:any" or "perl:native". After dropping the dependency, ibniz cross
builds successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru ibniz-1.18/debian/changelog ibniz-1.18/debian/changelog
--- ibniz-1.18/debian/changelog 2013-09-23 00:55:14.0 +0200
+++ ibniz-1.18/debian/changelog 2018-02-16 06:42:08.0 +0100
@@ -1,3 +1,10 @@
+ibniz (1.18-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused perl build dependency: perl-base is sufficient. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 16 Feb 2018 06:42:08 +0100
+
 ibniz (1.18-1) unstable; urgency=low
 
   * Initial release (Closes: #724249)
diff --minimal -Nru ibniz-1.18/debian/control ibniz-1.18/debian/control
--- ibniz-1.18/debian/control   2013-09-23 03:36:56.0 +0200
+++ ibniz-1.18/debian/control   2018-02-16 06:42:08.0 +0100
@@ -2,7 +2,7 @@
 Section: graphics
 Priority: optional
 Maintainer: maxigas 
-Build-Depends: debhelper (>= 9), libsdl1.2-dev, python-docutils, perl
+Build-Depends: debhelper (>= 9), libsdl1.2-dev, python-docutils
 Standards-Version: 3.9.4
 Homepage: http://pelulamu.net/ibniz/
 #Vcs-Git: git://git.debian.org/collab-maint/ibniz.git
--- End Message ---
--- Begin Message ---
Version: 1.18-1+rm

Dear submitter,

as the package ibniz 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/956623

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#956642: marked as done (RM: python-sptest -- RoQA; Depends on Python 2, dead upstream, unmaintained)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:42 +
with message-id 
and subject line Bug#956642: Removed package(s) from unstable
has caused the Debian Bug report #956642,
regarding RM: python-sptest -- RoQA; Depends on Python 2, dead upstream, 
unmaintained
to be marked as done.

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

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


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

Please remove python-sptest. It depends on Python 2, is dead upstream (last 
commit
from 2008) and there hasn't been a maintainer upload since 2008 either.

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

python-sptest |0.2.1-3 | source, all

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #936445,
regarding drobo-utils: 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.)


-- 
936445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:drobo-utils
Version: 0.6.1+repack-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:drobo-utils

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.6.1+repack-2+rm

Dear submitter,

as the package drobo-utils 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/956622

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#593836: marked as done (python-xmpp: control file "Recommends" section recommends twice the same package python-dnspython)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #593836,
regarding python-xmpp: control file "Recommends" section recommends twice the 
same package python-dnspython
to be marked as done.

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

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


-- 
593836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: normal

python-xmpp recommends twice python-dnspython in the control file, the
package appears twice too in aptitude interface (even though the information is
correct in the System Information below, don't know/understand why).

debian/control:
Recommends: python-dnspython | python-dnspython

I guess it should recommend python-dns instead as shown below.

Cheers,
Geoff

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable'), (700, 'unstable'), (600, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (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/dash

Versions of packages python-xmpp depends on:
ii  python   2.6.5-11interactive high-level object-orie
ii  python-central   0.6.14+nmu2 register and build utility for Pyt

Versions of packages python-xmpp recommends:
pn  python-dnspython | python-dns  (no description available)

python-xmpp suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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#887260: marked as done (drobo-utils should depend on e2fsprogs explicitly)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #887260,
regarding drobo-utils should depend on e2fsprogs explicitly
to be marked as done.

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

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


-- 
887260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drobo-utils
Version: 0.6.1+repack-2
User: helm...@debian.org
Usertags: nonessentiale2fsprogs

Dear maintainer,

We want to make removing e2fsprogs from installations possible. For standard
installations this is not useful, but embedded applications and chroots benefit
from such an option.  For getting there all packages that use e2fsprogs must be
identified and gain a dependency on it as e2fsprogs currently is essential.

drobo-utils was identified as potentially needing such a dependency,
because it mentions tool names from e2fsprogs in the following files:

/usr/lib/python2.7/dist-packages/Drobo.py contains mke2fs. According to file it 
is a Python script, ASCII text executable, with very long lines
/usr/lib/python2.7/dist-packages/DroboGUI.py contains mke2fs. According to file 
it is a Python script, ASCII text executable, with very long lines

Please investigate whether these cases are actually uses of a tool from
e2fsprogs. Care has been taken to shrink the number of candidates as much as
possible, but a few false positives will remain. After doing so, do one of the
following:

 * Add e2fsprogs to Depends.
 * Add e2fsprogs to Recommends.
 * Close this bug explaining why e2fsprogs is not used by this package.

Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC
severity. Please note that lintian will warn about such a dependency before
lintian 2.5.56.

Thanks for your help

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.6.1+repack-2+rm

Dear submitter,

as the package drobo-utils 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/956622

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#799408: marked as done (ibniz: crashes after pressing F12 then Ctrl+s)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:29 +
with message-id 
and subject line Bug#956623: Removed package(s) from unstable
has caused the Debian Bug report #799408,
regarding ibniz: crashes after pressing F12 then Ctrl+s
to be marked as done.

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

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


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

When I run ibniz, press F12 then Ctrl+s, ibniz crashes:

$ gdb -batch -n -ex 'set height 0' -ex run -ex bt -ex 'thread apply all bt 
full' --args ibniz
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec999700 (LWP 32513)]
[Thread 0x7fffec999700 (LWP 32513) exited]
[New Thread 0x7fffec999700 (LWP 32514)]

Program received signal SIGSEGV, Segmentation fault.
0x00402a5f in inserttosrc (line=0x406faa "\\#file untitled.ib\n") at 
ui_sdl.c:515
515   for(;i>=0;i--) ed.textbuffer[i+linelgt]=ed.textbuffer[i];
#0  0x00402a5f in inserttosrc (line=0x406faa "\\#file untitled.ib\n") 
at ui_sdl.c:515
#1  0x00403274 in ed_save () at ui_sdl.c:682
#2  0x00403d61 in interactivemode (codetoload=0x4066b8 "\n\n\n\n\\ 
IBNIZ 1.1180\n\\\n\\ Press f12 for help.\n") at ui_sdl.c:992
#3  0x00404459 in main (argc=1, argv=0x7fffda20) at ui_sdl.c:1175

Thread 3 (Thread 0x7fffec999700 (LWP 32514)):
#0  0x772305ff in __GI_ppoll (fds=0xa62ff0, nfds=2, timeout=, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:56
resultvar = 18446744073709551102
oldtype = 2
tval = {tv_sec = 5723991, tv_nsec = -8089022027776091392}
result = 
#1  0x76823e5d in ppoll (__ss=0x0, __timeout=, 
__nfds=, __fds=) at 
/usr/include/x86_64-linux-gnu/bits/poll2.h:77
No locals.
#2  pa_mainloop_poll (m=m@entry=0xa69c50) at pulse/mainloop.c:852
ts = {tv_sec = 10918992, tv_nsec = 10755664}
__func__ = "pa_mainloop_poll"
__PRETTY_FUNCTION__ = "pa_mainloop_poll"
#3  0x7682444e in pa_mainloop_iterate (m=0xa69c50, block=block@entry=1, 
retval=retval@entry=0x0) at pulse/mainloop.c:926
r = 0
#4  0x77b785ab in PULSE_WaitAudio (this=0xa41e50) at 
./src/audio/pulse/SDL_pulseaudio.c:310
size = 
#5  0x77b4ba20 in SDL_RunAudio (audiop=audiop@entry=0xa41e50) at 
./src/audio/SDL_audio.c:222
audio = 0xa41e50
stream = 0xa69a40 ""
stream_len = 512
udata = 0x0
fill = 0x4021f4 
silence = 0
#6  0x77b542f8 in SDL_RunThread (data=0xa64070) at 
./src/thread/SDL_thread.c:204
args = 0xa64070
userfunc = 0x77b4b940 
userdata = 0xa41e50
statusloc = 0xa6f860
#7  0x77b96e99 in RunThread (data=) at 
./src/thread/pthread/SDL_systhread.c:47
No locals.
#8  0x75a650a4 in start_thread (arg=0x7fffec999700) at 
pthread_create.c:309
__res = 
pd = 0x7fffec999700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737162876672, 
-5277215324536198629, 0, 10755472, 19, 140737162876672, 5277173867839072795, 
5277229013450861083}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, 
data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#9  0x7723907d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
No locals.

Thread 1 (Thread 0x77f338c0 (LWP 32509)):
#0  0x00402a5f in inserttosrc (line=0x406faa "\\#file untitled.ib\n") 
at ui_sdl.c:515
linelgt = 19
i = 2050
#1  0x00403274 in ed_save () at ui_sdl.c:682
f = 0x77db62c0 
fn = 0x0
#2  0x00403d61 in interactivemode (codetoload=0x4066b8 "\n\n\n\n\\ 
IBNIZ 1.1180\n\\\n\\ Press f12 for help.\n") at ui_sdl.c:992
sym = 115
mod = 64
t = 0
codechanged = 0
prevtimevalue = 0
e = {type = 2 '\002', active = {type = 2 '\002', gain = 0 '\000', state 
= 1 '\001'}, key = {type = 2 '\002', which = 0 '\000', state = 1 '\001', keysym 
= {scancode = 39 '\'', sym = SDLK_s, mod = KMOD_LCTRL, unicode = 19}}, motion = 
{type = 2 '\002', which = 0 '\000', state = 1 '\001', x = 39, y = 0, xrel = 
115, yrel = 0}, button = {type = 2 '\002', which = 0 '\000', button = 1 '\001', 
state = 0 '\000', x = 39, y = 0}, jaxis = {type = 2 '\002', which = 0 '\000', 
axis = 1 '\001', value = 39}, jba

Bug#680942: marked as done (drobo-utils: Drobo reports second LUN with incorrect size)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #680942,
regarding drobo-utils: Drobo reports second LUN with incorrect size
to be marked as done.

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

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


-- 
680942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drobo-utils
Version: 0.6.1+repack-1
Severity: normal

I was wondering why I have two 2 TiB LUNs showing up over Firewire, as
seen here:

  # fdisk -s
  /dev/sda: 488386584
  /dev/sdb: 2147483580
  /dev/sdc: 2147483580
  total: 4783353744 blocks

When I installed drobo-utils, I found that the Drobo contains four 930
GiB disks, obviously in RAID 5 as per the total physical space reported
in the "query capacity result" section below.  However, something is
obviously wrong because the second LUN should only be 751 GiB in size.
(In the "query luninfo result" section, a second LUN with ID 0 and size
0 is showing up in addition to the real one.)

See Peter Silva's comment at
https://groups.google.com/d/msg/drobo-talk/NF5YfvRP4d4/uyOoPErcuZAJ

Also, should I be worried that the real LUN's type shows as ['FAT32']
when it contains an ext3 filesystem?

See attached dmesg output.

  # drobom info
  -
  Info about Drobo Name: Drobo disk pack   Devices:
  /dev/sdb:/dev/sdc
  -
  query config result: 
  (4, 16, 2199023185408L)
  max lun size is:  2199023185408

  query capacity result:
  (807266607104L, 2182374301696L, 2989640908800L, 0)
  Physical space... used:  2182374301696  free:  807266607104  Total:
  2989640908800

  query protocol version result: 
  (0, 11)

  query settings result:
  (1340161646, 8, 'Drobo disk pack')
  Drobo time is Wed Jun 20 11:07:26 2012

  query slotinfo result:  number of slots: 4
  [(0, 1000204886016L, 0, 'green', 'WDC WD10EACS-00ZJB0', 'WDC
  WD10EACS-00Z'), (1, 1000204886016L, 0, 'green', 'WDC WD10EACS-00ZJB0',
  'WDC WD10EACS-00Z'), (2, 1000204886016L, 0, 'green', 'WDC
  WD10EADS-00L5B1', 'WDC WD10EADS-00L'), (3, 1000204886016L, 0, 'green',
  'WDC WD10EACS-32D6B1', 'WDC WD10EACS-32D')]
  query firmware result:
  (1, 248, 15408, 13, 6, 'Dec  2 2008,10:24:08', 'ArmMarvell', '1.3.0',
  ['NO_AUTO_REBOOT', 'NO_FAT32_FORMAT', 'USED_CAPACITY_FROM_HOST',
  'DISKPACKSTATUS', 'ENCRYPT_NOHEADER', 'CMD_STATUS_QUERIABLE',
  'VARIABLE_LUN_SIZE_1_16', 'PARTITION_LUN_GPT_MBR',
  'FAT32_FORMAT_VOLNAME', 'SUPPORTS_DROBOSHARE', 'SUPPORTS_NEW_LUNINFO2',
  'feature x0800', 'feature x2000 '])
  drobo says firmware revision:  1 . 248 ( 15408 ) was built:  Dec  2
  2008,10:24:08

  query status result:
  ([], 0)

  query options result:
  {'RedThreshold': 95, 'YellowThreshold': 85}
  query luninfo result:
  (0, 2199023185920L, 2182374301696L, 'No Partitions', ['FAT32'])
  (0, 0, 0, 'No Partitions', ['NTFS'])

  -

-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages drobo-utils depends on:
ii  python  2.6.6-3+squeeze7 interactive high-level object-orie
ii  python-support  1.0.10   automated rebuilding support for P

Versions of packages drobo-utils recommends:
ii  parted   2.3-5   The GNU Parted disk partition resi
ii  sudo 1.7.4p4-2.squeeze.3 Provide limited super user privile

Versions of packages drobo-utils suggests:
pn  gparted(no description available)
ii  python-qt44.7.3-1+b1 Python bindings for Qt4

-- no debconf information
[0.975832] firewire_ohci: Added fw-ohci device :03:09.0, OHCI version 
1.10
[1.476566] firewire_core: created device fw0: GUID 000108017a2b, S800
[1.478211] firewire_core: created device fw1: GUID 001a620282721064, S800
[1.478215] firewire_core: phy config: card 0, new root=ffc0, gap_count=5
[2.601328] udev[347]: starting version 164
[2.959116] scsi4 : SBP-2 IEEE-1394
[3.157227] firewire_sbp2: fw1.0: logged in to LUN  (0 retries)
[3.159361] scsi 4:0:0:0: Direct-Access TRUSTED  Mass Storage 2.00 
PQ: 0 ANSI: 5
[   

Bug#782707: marked as done (python-xmpp: PLAIN Authentication error when JID and password have specific length (base64 trailing newline))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #782707,
regarding python-xmpp: PLAIN Authentication error when JID and password have 
specific length (base64 trailing newline)
to be marked as done.

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

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


-- 
782707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: important
Tags: upstream patch

Dear Maintainer,

TL;DR: python-xmpp adds a trailing newline to the base64 encoded string
   when doing PLAIN authentication. When the jid+password have a
   specific length the resulting base64 string is not padded with =.
   A base64 string without badding and trailing newline breaks
   authentication in ejabberd in Jessie, but not in Wheezy.

We have just upgraded our Jabber server to Jessie. A local bot (using
python-xmpp) could not authenticate to the server anymore. All
authentication attempts resulted in 

DEBUG: socket   got   
  


We have debugged this extensively and have found the root cause for this
issue.

When building the XML stanza for plain authentication the node adds the
full base64.encodestring result, which contains a trailing \n

auth.py:144


node=Node('auth',attrs={'xmlns':NS_SASL,'mechanism':'PLAIN'},payload=[base64.encodestring(sasl_data)])

DEBUG: socket   sent  cHl4bXBwLXRlc3RAbHJ6LmRlAHB5eG1wcC10ZXN0AHNvb2Q4YWhUdTlhZXpR\n
DEBUG: socket   got   
  


when however the length of password or jid is changed so that the
resulting base64 is padded with = the authentication works fine.

DEBUG: socket   sent  cHl4bXBwLXRlc3RAbHJ6LmRlAHB5eG1wcC10ZXN0AHNvb2Q4YWhUdTlhZXo=\n
DEBUG: socket   got   

Our current assumption is that the ejabberd base64 parser just stops
parsing when it hits the padding. However, if the string has the right
lenght and does not have any padding it hits the newline and bails out.
This is a minor bug in ejabberd itself, but according to my
understanding the newline isn't legal.


The fix is pretty easy. Change line 144 to either

node=Node('auth',attrs={'xmlns':NS_SASL,'mechanism':'PLAIN'},payload=[base64.encodestring(sasl_data).replace('\r','').replace('\n','')])

(this has prior art in line 202 of the same file, but looks ugly as
hell)

or

node=Node('auth',attrs={'xmlns':NS_SASL,'mechanism':'PLAIN'},payload=[base64.b64encode(sasl_data)])

b64encode is available since Python 2.4

I have found a fork of python-xmpp on github which uses the first fix,
but there is no commit with that fix

https://github.com/ArchipelProject/xmpppy/blob/master/auth.py

Best Regards,
Bernhard
--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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#776114: marked as done (drobo-utils: Git directory present in source tarball)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #776114,
regarding drobo-utils: Git directory present in source tarball
to be marked as done.

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

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


-- 
776114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drobo-utils
Severity: minor

The source package for bppsuite contains a git directory. This should be
removed.



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.6.1+repack-2+rm

Dear submitter,

as the package drobo-utils 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/956622

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#614830: marked as done (Fix detecting drobo device)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:52:07 +
with message-id 
and subject line Bug#956622: Removed package(s) from unstable
has caused the Debian Bug report #614830,
regarding Fix detecting drobo device
to be marked as done.

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

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


-- 
614830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drobo-utils
Version: 0.6.1+repack-1

DroboElite connected by iSCSI

[7802979.745570] scsi6 : iSCSI Initiator over TCP/IP
[7802980.285741] scsi 6:0:0:0: Direct-Access DroboDroboElite
1.00 PQ: 0 ANSI: 5
[7802980.285741] sd 6:0:0:0: [sdh] Very big device. Trying to use READ
CAPACITY(16).
[7802980.285741] sd 6:0:0:0: [sdh] 34359738368 512-byte hardware
sectors (17592186 MB)
[7802980.285741] sd 6:0:0:0: [sdh] Write Protect is off
[7802980.285774] sd 6:0:0:0: [sdh] Mode Sense: 1b 00 10 00
[7802980.289767] sd 6:0:0:0: [sdh] Got wrong page
[7802980.289767] sd 6:0:0:0: [sdh] Assuming drive cache: write through
[7802980.289767] sd 6:0:0:0: [sdh] Very big device. Trying to use READ
CAPACITY(16).
[7802980.289767] sd 6:0:0:0: [sdh] 34359738368 512-byte hardware
sectors (17592186 MB)
[7802980.289767] sd 6:0:0:0: [sdh] Write Protect is off
[7802980.289767] sd 6:0:0:0: [sdh] Mode Sense: 1b 00 10 00
[7802980.289767] sd 6:0:0:0: [sdh] Got wrong page
[7802980.289826] sd 6:0:0:0: [sdh] Assuming drive cache: write through
[7802980.294530]  sdh: unknown partition table
[7802999.051352] sd 6:0:0:0: [sdh] Attached SCSI disk
[7802999.051461] sd 6:0:0:0: Attached scsi generic sg10 type 0

But drobom can't find my brand new DroboElite.

xenian0:~# drobom -v 16 info status
examining:  /dev/sda
id:  (2, 2, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdb
id:  (2, 3, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdc
id:  (2, 4, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdd
id:  (2, 0, 1, 0, 'Dell')
rejected: vendor is Dell (not from DRI)
examining:  /dev/sdg
id:  (2, 5, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdh
id:  (6, 0, 0, 0, 'Drobo   ')
rejected: vendor is Drobo(not from DRI)
returning list:  []
No Drobos discovered

But with this easy patch...

+--- a/DroboIOctl.py
 b/DroboIOctl.py
+@@ -313,7 +313,8 @@
+  print "id: ", id
+
+   thisdev="%02d%02d%02d" % (id[0], id[1], id[2])
+-  if ( id[4].startswith("TRUSTED") or
id[4].startswith("DROBO") ):  # you have a Drobo!
++  vendor=id[4].upper()
++  if ( vendor.startswith("TRUSTED") or
vendor.startswith("DROBO") ):  # you have a Drobo!
+  if debugflags & Drobo.DBG_Detection:
+ print "found a Drobo"
+  if thisdev == previousdev :  # multi-lun drobo...

xenian0:~# drobom -v 16 info status
examining:  /dev/sda
id:  (2, 2, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdb
id:  (2, 3, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdc
id:  (2, 4, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdd
id:  (2, 0, 1, 0, 'Dell')
rejected: vendor is Dell (not from DRI)
examining:  /dev/sdg
id:  (2, 5, 0, 0, 'ATA ')
rejected: vendor is ATA  (not from DRI)
examining:  /dev/sdh
id:  (6, 0, 0, 0, 'Drobo   ')
found a Drobo
appending new lundevs to devices: []
returning list:  [['/dev/sdh']]
trying:  ['/dev/sdh']
cfg:  (8, 0, 36893505739605147136L)
settings:  (1298485938, 8, 'DroboElite')
found  [['/dev/sdh']]
cfg:  (8, 0, 36893505739605147136L)
settings:  (1298485938, 8, 'DroboElite')
([], 0)


Drobo != DROBO ??

Thanks in advance
PD: this is a backport version running on lenny
diff -ruN '--exclude=.svn' squeeze//debian/changelog trunk//debian/changelog
--- squeeze//debian/changelog	2011-02-23 17:32:23.0 +0100
+++ trunk//debian/changelog	2011-02-23 17:32:23.0 +0100
@@ -1,3 +1,23 @@
+drobo-utils (0.6.1+repack-1~bpo50+2) bvmc; urgency=low
+
+  * Rebuild for BVMC.
+  * debian/README.source:
+- Added quilt info 
+  * debian/rules:
+- Added quilt rules
+  * debian/control:
+- Added quilt to Build-Depends
+  * Created debian/patches:
+- Added patch 0001_fixing_drobo_identify_devices.patch
+
+ -- Victor Seva   Wed, 23 Feb 2011 13:10:33 +0100
+
+drobo-utils (0.6.1+repack-1~bpo50+1) bvmc; urgency=low
+
+  * Rebuild for BVMC.
+
+ -- Victor Seva   Wed, 23 Feb 2011 10:10:52 +0100
+
 drobo-utils (0.6.1+repack-1) unstable; urgency=low

Bug#585341: marked as done (python-xmpp: Python string exceptions no more allowed in Python 2.6)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:53:20 +
with message-id 
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #585341,
regarding python-xmpp: Python string exceptions no more allowed in Python 2.6
to be marked as done.

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

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


-- 
585341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: minor
User: debian-pyt...@lists.debian.org
Usertags: python2.6

Hello,
One of the changes brought by Python 2.6 is the removal of string
exceptions, so they won't work in Python 2.6 (just a side note: they
were also buggy before, since they were not guaranteed to work
reliable even in <2.6); as an example:

$ python2.5 -c "raise 'eggs'"
-c:1: DeprecationWarning: raising a string exception is deprecated
Traceback (most recent call last):
  File "", line 1, in 
eggs

$ python2.6 -c "raise 'eggs'"
Traceback (most recent call last):
  File "", line 1, in 
TypeError: exceptions must be old-style classes or derived from BaseException, 
not str

Since 2.6 is the planned default version for the upcoming new Debian
stable release, there are chances your package may be affected by this
change.

We are not sure your package is impacted, since the exception raise
can be in a dead or very rare branch of the code, and so simply never
being executed. We would like to leverage your package maintainer
status and the relationship with upstream authors to inspect more
deeply the issue and act accordingly (that includes: making this bug
release critical, closing it as irrelevant, tagging it 'wontfix', or
whatever is appropriate).

Jakub Wilk made the discovery of the problem and kindly prepared a
list [1] of all identified packages (downloaded on 2010-06-09) along
with files & lines that triggered the pattern search.

[1] http://people.debian.org/~morph/strexp/string-exceptions.lintian

This mass-bug filing was announced at 2010-06-06 on [2] (see the
thread and the references there).

[2] http://lists.debian.org/debian-devel/2010/06/msg00097.html

We do not consider the whole situation a stopper for the Python
transition to 2.6, except (of course) for those single bugs where
severity will be increased.

Thanks in advance for your attention,
Sandro on behalf of debian-python


--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp 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/956644

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 ---

Processed: RFS: freecdb/0.76 [QA] -- creating and reading constant databases

[Debian Bug Tracking System]

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

> close 956648
Bug #956648 [sponsorship-requests] RFS: freecdb/0.76 [QA] -- creating and 
reading constant databases
Marked Bug as done
> stop
Stopping processing here.

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

Bug#937426: marked as done (pyentropy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:46:52 +
with message-id 
and subject line Bug#956603: Removed package(s) from unstable
has caused the Debian Bug report #937426,
regarding pyentropy: 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.)


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

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

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

Dear submitter,

as the package pyentropy 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/956603

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#670514: marked as done (When open a ssh session with tcsh as shell, "noise" show up in the terminal)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:15 +
with message-id 
and subject line Bug#956610: Removed package(s) from unstable
has caused the Debian Bug report #670514,
regarding When open a ssh session with tcsh as shell, "noise" show up in the 
terminal
to be marked as done.

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

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


-- 
670514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: desktop-profiles
Version: 1.4.15+nmu1
Severity: minor


Here is an example of the "noise" we have :

Last login: Thu Apr 26 11:59:24 2012 from xxx
declare -x COLUMNS="80"
declare -x GROUP="prof"
declare -x HOME="/home/xxx"
declare -x HOST="xxx"
declare -x HOSTTYPE="x86_64-linux"
declare -x LANG="fr_FR.UTF-8"
declare -x LINES="24"
declare -x LOGNAME="x"
declare -x MACHTYPE="x86_64"
declare -x MAIL="/var/mail/"
declare -x NLSPATH="/usr/share/locale/%L/LC_MESSAGES/%N.cat"
declare -x OLDPWD
declare -x OSTYPE="linux"
declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games"
declare -x PWD="/ubs/home/prof/grenault"
declare -x REMOTEHOST="x.univ-ubs.fr"
declare -x SHELL="/bin/tcsh"
declare -x SHLVL="2"
declare -x SSH_CLIENT="172.17.66.17 47913 22"
declare -x SSH_CONNECTION="172.17.66.17 47913 172.16.98.33 22"
declare -x SSH_TTY="/dev/pts/6"
declare -x TERM="xterm"
declare -x USER=""
declare -x VENDOR="unknown"
declare -x 
XDG_SESSION_COOKIE="4fefaa3cfae2dabeff2b3f7d000b-1335434404.56364-1982862778"
grenault@@kb-021-02% 

Adding "> /dev/null" at the end of line 14 make the connexion quiet.

Gilles



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

Kernel: Linux 3.0.0-1-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/dash

Versions of packages desktop-profiles depends on:
ii  debconf [debconf-2.0] 1.5.36.1   Debian configuration management sy

desktop-profiles recommends no packages.

Versions of packages desktop-profiles suggests:
ii  gconf-editor  2.30.0-2   An editor for the GConf configurat
ii  hicolor-icon-theme0.12-1 default fallback theme for FreeDes
pn  kiosktool  (no description available)
pn  kommander  (no description available)
ii  menu-xdg  0.5freedesktop.org menu compliant win
pn  pessulus   (no description available)
ii  shared-mime-info  0.71-4 FreeDesktop.org shared MIME databa

-- Configuration Files:
/etc/csh/login.d/desktop-profiles.csh changed:
set 
DESKTOP_PROFILES_SNIPPET="/usr/share/desktop-profiles/get_desktop-profiles_variables"
if (-e $DESKTOP_PROFILES_SNIPPET) then
  # initialization
  set TEMP_FILE=`tempfile`
  # use bash to write the required environment settings to a tempfile
  # this file has a VARIABLE=VALUE format
  bash $DESKTOP_PROFILES_SNIPPET  $TEMP_FILE > /dev/null
  # convert to csh format and source to set the required environment variables
  sed -i 's/^\(.*\)=\(.*\)$/setenv \1 \2/'  $TEMP_FILE
  source $TEMP_FILE
  # cleanup
endif


-- debconf information excluded


--- End Message ---
--- Begin Message ---
Version: 1.4.31+rm

Dear submitter,

as the package desktop-profiles 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/956610

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#813981: marked as done (pyentropy: FTBFS: ndexError: invalid slice)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:46:52 +
with message-id 
and subject line Bug#956603: Removed package(s) from unstable
has caused the Debian Bug report #813981,
regarding pyentropy: FTBFS: ndexError: invalid 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.)


-- 
813981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyentropy
Version: 0.4.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

pyentropy fails to build from source in unstable/amd64:

  [..]

  ==
  ERROR: pyentropy.tests.test_systems.test_1d_qe('qe', 'plugin')
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/tests/test_systems.py",
 line 61, in do_1d_check
  s.calculate_entropies(method=method, calc=allcalc, qe_method=qe_method)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 252, in calculate_entropies
  self._qe_ent(qe_method,sampling,methods)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 370, in _qe_ent
  sys = self._subsampled_instance(sl)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 595, in _subsampled_instance
  return DiscreteSystem(self.X[:,sl], self.X_dims,
  IndexError: invalid slice
  
  ==
  ERROR: pyentropy.tests.test_systems.test_1d_qe_pt('qe', 'pt')
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/tests/test_systems.py",
 line 61, in do_1d_check
  s.calculate_entropies(method=method, calc=allcalc, qe_method=qe_method)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 252, in calculate_entropies
  self._qe_ent(qe_method,sampling,methods)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 370, in _qe_ent
  sys = self._subsampled_instance(sl)
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/systems.py",
 line 595, in _subsampled_instance
  return DiscreteSystem(self.X[:,sl], self.X_dims,
  IndexError: invalid slice
  
  ==
  ERROR: pyentropy.tests.test_systems.test_1d_plugin_sorted('plugin', None)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
  return func()
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/tests/test_systems.py",
 line 98, in setup_1d_sorted
  xs[start:end] = oce
  IndexError: invalid slice
  
  ==
  ERROR: pyentropy.tests.test_systems.test_1d_pt_sorted('pt', None)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
  return func()
File 
"/home/lamby/temp/cdt.20160207102950.HNDuxkvewQ/pyentropy-0.4.1/pyentropy/tests/test_systems.py",
 line 98, in setup_1d_sorted
  xs[start:end] = oce
  IndexError: invalid slice
  
  ==
  ERROR: pyentropy.tests.test_systems.test_1d_qe_sorted('qe', 'plugin')
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, i

Bug#953452: marked as done (O: diff-match-patch -- diff/match/patch algorithms implemented in JavaScript)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:59 +
with message-id 
and subject line Bug#956618: Removed package(s) from unstable
has caused the Debian Bug report #953452,
regarding O: diff-match-patch -- diff/match/patch algorithms implemented in 
JavaScript
to be marked as done.

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

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


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

The current maintainer of diff-match-patch, Daniel Pocock ,
is not a member of the Project anymore (see https://bugs.debian.org/953378#12)

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: diff-match-patch
Binary: libjs-diff-match-patch
Version: 20121121-2
Maintainer: Daniel Pocock 
Build-Depends: debhelper (>= 9.0.0), node-uglify
Architecture: all
Standards-Version: 3.9.6
Format: 3.0 (quilt)
Files:
 39d2ff0b0a41aab2ea455dfd5e96dfbd 1980 diff-match-patch_20121121-2.dsc
 5ee1886a2f5246ad03834158c52b9f07 318282 diff-match-patch_20121121.orig.tar.bz2
 ac3777e93187cc195690ec340acb99de 1916 diff-match-patch_20121121-2.debian.tar.xz
Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/diff-match-patch.git/
Vcs-Git: git://anonscm.debian.org/collab-maint/diff-match-patch.git
Checksums-Sha256:
 fd5611847c191fbafcadde0ca834f2eea09a2eb89f9cd2d923acd9da5789c51b 1980 
diff-match-patch_20121121-2.dsc
 7ef965596e74dc4776e53e25d57c24962eab24e4640e877ff567e4af1435fe49 318282 
diff-match-patch_20121121.orig.tar.bz2
 15187e965e3cf65c4fe6eb296473ff1078f99facdc3756003f15fee4a7ea12c5 1916 
diff-match-patch_20121121-2.debian.tar.xz
Homepage: https://code.google.com/p/google-diff-match-patch/
Package-List: 
 libjs-diff-match-patch deb web optional arch=all
Directory: pool/main/d/diff-match-patch
Priority: optional
Section: misc

Package: libjs-diff-match-patch
Source: diff-match-patch
Version: 20121121-2
Installed-Size: 120
Maintainer: Daniel Pocock 
Architecture: all
Recommends: javascript-common
Description-en: diff/match/patch algorithms implemented in JavaScript
 The Diff Match and Patch libraries offer robust algorithms to perform
 the operations required for synchronizing plain text.
 .
 The libraries are implemented in various high-level languages, this is
 the JavaScript implementation.
Description-md5: 778a1e517dc1408db390baca3405cd18
Homepage: https://code.google.com/p/google-diff-match-patch/
Section: javascript
Priority: optional
Filename: pool/main/d/diff-match-patch/libjs-diff-match-patch_20121121-2_all.deb
Size: 23810
MD5sum: 7c1f95b29b6311f1d1c6d7f5726082bd
SHA256: 15fd4b4a88fa9cf87f02bfc34dc9203d294e439b4d8f3c091e25152ea1d23bd1



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 20121121-2+rm

Dear submitter,

as the package diff-match-patch 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/956618

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#956618: marked as done (RM: diff-match-patch -- RoQA; unmaintained, lacking years behind upstream, no reverse dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:54 +
with message-id 
and subject line Bug#956618: Removed package(s) from unstable
has caused the Debian Bug report #956618,
regarding RM: diff-match-patch -- RoQA; unmaintained, lacking years behind 
upstream, no reverse dependencies
to be marked as done.

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

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


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

As the title says, its probably better to RM it from Debian.

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

diff-match-patch | 20121121-2 | source
libjs-diff-match-patch | 20121121-2 | all

--- Reason ---
RoQA; unmaintained, lacking years behind upstream, no reverse dependencies
--

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/956618

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#559205: marked as done (desktop-profiles cannot apply gconf setting correctly (mandatory and default))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:15 +
with message-id 
and subject line Bug#956610: Removed package(s) from unstable
has caused the Debian Bug report #559205,
regarding desktop-profiles cannot apply gconf setting correctly (mandatory and 
default)
to be marked as done.

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

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


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

When I apply GCONF profiles via desktop-profiles the script cannot set 
$DEFAULTS_PATH.
It always only set $MANDATORY_PATH. 
I suggest the following patch to make it verify the directory name for applying 
the patch.

Thanks

=== modified file '20desktop-profiles_activateDesktopProfiles'
--- 20desktop-profiles_activateDesktopProfiles  2009-11-25 20:51:41 +
+++ 20desktop-profiles_activateDesktopProfiles  2009-12-02 19:26:20 +
@@ -301,17 +301,23 @@
 # see if there's actually anyting to add, if so create pathfiles and fill 
them
 cat $GCONF_FILE | while read LINE; do
# user gconf source should be included by system-wide path already
-   if (test "$LINE" != 'xml:readwrite:$(HOME)/.gconf'); then
- if (test $INCLUDED_HOME = false); then
-  # add configuration source
-   echo $LINE >> "$MANDATORY_PATH";
- else 
-  # add configuration source
-   echo $LINE >> "$DEFAULTS_PATH";
- fi;
-   else  
- INCLUDED_HOME=true;
-   fi  
+   if (echo "$LINE" |grep "mandatory"); then
+ echo $LINE >> "$MANDATORY_PATH";
+   elif (echo "$LINE" |grep "default"); then
+ echo $LINE >> "$DEFAULTS_PATH";
+   fi
+
+#   if (test "$LINE" != 'xml:readwrite:$(HOME)/.gconf'); then
+# if (test $INCLUDED_HOME = false); then
+# # add configuration source
+#   echo $LINE >> "$MANDATORY_PATH";
+# else 
+# # add configuration source
+#   echo $LINE >> "$DEFAULTS_PATH";
+# fi;   
+#   else  
+# INCLUDED_HOME=true;
+#   fi  
 done;
 
 # get rid of temp files and variables if we don't use them




Marc Gariépy


--- End Message ---
--- Begin Message ---
Version: 1.4.31+rm

Dear submitter,

as the package desktop-profiles 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/956610

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#956603: marked as done (RM: pyentropy -- RoQA; Depends on Python 2, RC-buggy for a long time, no rev deps)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:46:44 +
with message-id 
and subject line Bug#956603: Removed package(s) from unstable
has caused the Debian Bug report #956603,
regarding RM: pyentropy -- RoQA; Depends on Python 2, RC-buggy for a long time, 
no rev deps
to be marked as done.

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

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


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

Please remove pyentropy. It depends on Python 2, there are no reverse 
dependencies
and it FTBFSes since over four years now (813981).

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

 pyentropy |0.4.1-2 | source
python-pyentropy |0.4.1-2 | all

--- Reason ---
RoQA; Depends on Python 2, RC-buggy for a long time, no rev deps
--

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

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

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

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

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

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#344030: marked as done (Profiles are not active upon logins like ssh -X)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:15 +
with message-id 
and subject line Bug#956610: Removed package(s) from unstable
has caused the Debian Bug report #344030,
regarding Profiles are not active upon logins like ssh -X
to be marked as done.

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

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


-- 
344030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: desktop-profiles
Version: 1.4.8


Profiles are not active upon logins like ssh -X since the
desktop-profiles script is an xsession.d script.

If desktop-profiles could be activated with a PAM module the behaviour
could be the same regardless how the user entered the system.

The problem came to my attention when a user starting kmail over ssh -X
lost his settings aferwards. The loss of data is a bug in kmail, but it
hinted to the missing profiles.

--- End Message ---
--- Begin Message ---
Version: 1.4.31+rm

Dear submitter,

as the package desktop-profiles 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/956610

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#956610: marked as done (RM: desktop-profiles -- ROM; unused)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:47:07 +
with message-id 
and subject line Bug#956610: Removed package(s) from unstable
has caused the Debian Bug report #956610,
regarding RM: desktop-profiles -- ROM; unused
to be marked as done.

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

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


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

Dear ftp masters,

please remove desktop-profiles from unstable, it's unneeded today (as it has
been replaced by XDG), the last user was src:debian-edu-config which stopped
depending on it in November 2019 with it's 2.11.8 upload. 

(It probably has not been used since before buster as the thread starting
with <20191115191400.4mr27p2vrhhet...@layer-acht.org> revealed.)

Thanks for your continuous work on the archive!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Some people say that the climate crisis  is something that we all have created,
but  that is not true,  because if everyone is guilty  then no one is to blame.
And someone is to blame.  Some people, some companies,  some decision-makers in
particular, have known exactly what priceless values they have been sacrificing
to continue making unimaginable amounts of money.


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

desktop-profiles | 1.4.31 | source, all

--- Reason ---
ROM; unused
--

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/956610

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#956084: marked as done (inetutils-telnetd: CVE-2020-10188)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:34:15 +
with message-id 
and subject line Bug#956084: fixed in inetutils 2:1.9.4-12
has caused the Debian Bug report #956084,
regarding inetutils-telnetd: CVE-2020-10188
to be marked as done.

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

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


-- 
956084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inetutils-telnetd
Severity: critical
Tags: security
Justification: root security hole

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

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

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

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   www.maths.usyd.edu.au/u/psz
School of Mathematics and Statistics   University of SydneyAustralia
--- End Message ---
--- Begin Message ---
Source: inetutils
Source-Version: 2:1.9.4-12
Done: Guillem Jover 

We believe that the bug you reported is fixed in the latest version of
inetutils, 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.
Guillem Jover  (supplier of updated inetutils 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 04:08:13 +0200
Source: inetutils
Architecture: source
Version: 2:1.9.4-12
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 804766 951680 956084
Changes:
 inetutils (2:1.9.4-12) unstable; urgency=medium
 .
   * Switch to Standards-Version 4.5.0 (no changes needed).
   * Remove patches from upstream:
 - tftpd: Restore logging while chrooted. (We do not ship tftpd.)
   * Add patches from upstream:
 - Change header inclusion for ifconfig on GNU/Linux, to support musl.
 - telnetd: More work on CVE-2019-0053.
 - Various compiler warnings fixes.
 - telnet: Various off-by-one checks.
 - ftp: Fix buffer overflows.
 - ping, ping6: Fix memory leaks.
   * Add patch from Red Hat / Fedora:
 - Fix arbitrary remote code execution in telnetd via short writes or
   urgent data. Fixes CVE-2020-10188. Closes: #956084
   Thanks to Michal Ruprich .
   Note: While the PoC exploit does not work on inetutils due to the
   different codebases, the adapted patch was close enough to apply almost
   directly, even though the information leak might appear to still remain.
   * Document inetutils-inetd IPv6 support in man page, and modify the
 default template inetd.conf to use udp6 and tcp6. Closes: #804766
   * Minor wording fixes to default templated inetd.conf.
   * Remove long obsolete netkit-inetd Provides and Conflicts from
 inetutils-inetd.
   * Document that inetutils-inetd -p option without a filename disables
 writing a pidfile. Closes: #951680
   * Disable building tftp and tftpd, which we are not shipping, and are
 causing test suite failures on kfreebsd-amd64.
Checksums-Sha1:
 5652f641db425eb5c8fdbc3a3f721c09b469e75b 3084 inetutils_1.9.4-12.dsc
 c6512c1974fad1f7b03eef8baf0ecc05c6379b70 163 inetutils_1.9.4.orig.tar.xz.asc
 8c43fe43f75e913245a4a55d9895c0df47a19534 112748 
inetutils_1.9.4-12.debian.tar.xz
 1033b60e9fa4e67b99f6dc6b8c33126b35cc0304 12760 
inetutils_1.9.4-12_amd64.buildinfo
Checksums-Sha256:
 8ff53a9f45cbd0fb9065a81ba6120fe51f2291c77187fce4f54fdcc32c8da9db 3084 
inetutils_1.9.4-12.dsc
 d570ff2369cf42238bcfd63cc1faacbc440652d753f4f0b62bb770ba7a497609 163 
inetutils_1.9.4.orig.tar.xz.asc
 bad5caf9be8978f3ea7efa8e6209ee7aab8cc002ef50f81c4286396993e64da8 112748 
inetutils_1.9.4-12.debian.tar.xz
 f8787c4b00435aed181605775d616fc884ed288235a3530354ccaef356346c46 12760 
inetutils_1.9.4-12_amd64.buildinfo
Files:
 a9aa0e6a42fbb2999b40e440ee16c51c 3084 net optional inetutils_1.9.4-12.dsc
 094681dc589bc04f918febd601a38fca 163 net optional 
inetutils_1.9.4.orig.tar.xz.asc
 282b37aadf7a546670e2ad67fc

Bug#951680: marked as done (inetutils-inetd)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:34:15 +
with message-id 
and subject line Bug#951680: fixed in inetutils 2:1.9.4-12
has caused the Debian Bug report #951680,
regarding inetutils-inetd
to be marked as done.

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

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


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

Version: 2:1.9.4-7

 

Option -p do not work - pidfile is not created. Pidfile is created only,
when option -p is not present.

 

Environment:

Debian GNU/Linux 10 (buster)

Architecture: i386

libc6: 2.28-10

kernel: 4.19.98-1

 

MJS

 

--- End Message ---
--- Begin Message ---
Source: inetutils
Source-Version: 2:1.9.4-12
Done: Guillem Jover 

We believe that the bug you reported is fixed in the latest version of
inetutils, 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.
Guillem Jover  (supplier of updated inetutils 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 04:08:13 +0200
Source: inetutils
Architecture: source
Version: 2:1.9.4-12
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 804766 951680 956084
Changes:
 inetutils (2:1.9.4-12) unstable; urgency=medium
 .
   * Switch to Standards-Version 4.5.0 (no changes needed).
   * Remove patches from upstream:
 - tftpd: Restore logging while chrooted. (We do not ship tftpd.)
   * Add patches from upstream:
 - Change header inclusion for ifconfig on GNU/Linux, to support musl.
 - telnetd: More work on CVE-2019-0053.
 - Various compiler warnings fixes.
 - telnet: Various off-by-one checks.
 - ftp: Fix buffer overflows.
 - ping, ping6: Fix memory leaks.
   * Add patch from Red Hat / Fedora:
 - Fix arbitrary remote code execution in telnetd via short writes or
   urgent data. Fixes CVE-2020-10188. Closes: #956084
   Thanks to Michal Ruprich .
   Note: While the PoC exploit does not work on inetutils due to the
   different codebases, the adapted patch was close enough to apply almost
   directly, even though the information leak might appear to still remain.
   * Document inetutils-inetd IPv6 support in man page, and modify the
 default template inetd.conf to use udp6 and tcp6. Closes: #804766
   * Minor wording fixes to default templated inetd.conf.
   * Remove long obsolete netkit-inetd Provides and Conflicts from
 inetutils-inetd.
   * Document that inetutils-inetd -p option without a filename disables
 writing a pidfile. Closes: #951680
   * Disable building tftp and tftpd, which we are not shipping, and are
 causing test suite failures on kfreebsd-amd64.
Checksums-Sha1:
 5652f641db425eb5c8fdbc3a3f721c09b469e75b 3084 inetutils_1.9.4-12.dsc
 c6512c1974fad1f7b03eef8baf0ecc05c6379b70 163 inetutils_1.9.4.orig.tar.xz.asc
 8c43fe43f75e913245a4a55d9895c0df47a19534 112748 
inetutils_1.9.4-12.debian.tar.xz
 1033b60e9fa4e67b99f6dc6b8c33126b35cc0304 12760 
inetutils_1.9.4-12_amd64.buildinfo
Checksums-Sha256:
 8ff53a9f45cbd0fb9065a81ba6120fe51f2291c77187fce4f54fdcc32c8da9db 3084 
inetutils_1.9.4-12.dsc
 d570ff2369cf42238bcfd63cc1faacbc440652d753f4f0b62bb770ba7a497609 163 
inetutils_1.9.4.orig.tar.xz.asc
 bad5caf9be8978f3ea7efa8e6209ee7aab8cc002ef50f81c4286396993e64da8 112748 
inetutils_1.9.4-12.debian.tar.xz
 f8787c4b00435aed181605775d616fc884ed288235a3530354ccaef356346c46 12760 
inetutils_1.9.4-12_amd64.buildinfo
Files:
 a9aa0e6a42fbb2999b40e440ee16c51c 3084 net optional inetutils_1.9.4-12.dsc
 094681dc589bc04f918febd601a38fca 163 net optional 
inetutils_1.9.4.orig.tar.xz.asc
 282b37aadf7a546670e2ad67fc990680 112748 net optional 
inetutils_1.9.4-12.debian.tar.xz
 a9bc3cd0a2d9194a9e0464dd16cce21e 12760 net optional 
inetutils_1.9.4-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAl6VHBYACgkQuXK/PqSu
V6PCKxAA5XIVty1Yt18NIJxenNapdyUfnF1xvXr8a3V84CyK9Az/E9DbZOBwjq/J
NiHcZDA+9PRW0Z80i1MMbAXfOQQ54xdGrRj0oSAxUWaViBxQmTVplwtLID/l/Uaf
k7VlzaSakHgwLawW3

Bug#804766: marked as done (inetutils-inetd: please support ipv6)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 02:34:15 +
with message-id 
and subject line Bug#804766: fixed in inetutils 2:1.9.4-12
has caused the Debian Bug report #804766,
regarding inetutils-inetd: please support ipv6
to be marked as done.

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

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


-- 
804766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inetutils-inetd
Version: 2:1.9.2.39.3a460-3
Severity: wishlist

Dear Maintainer,

inetd does not listen on IPv6 ports, only IPv4.



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'stable'), (500, 'oldstable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages inetutils-inetd depends on:
ii  libc62.19-18+deb8u1
ii  lsb-base 4.1+Debian13+nmu1
ii  rsyslog [system-log-daemon]  8.4.2-1+deb8u1
ii  tcpd 7.6.q-25
ii  update-inetd 4.43

inetutils-inetd recommends no packages.

inetutils-inetd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: inetutils
Source-Version: 2:1.9.4-12
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated inetutils 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 04:08:13 +0200
Source: inetutils
Architecture: source
Version: 2:1.9.4-12
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 804766 951680 956084
Changes:
 inetutils (2:1.9.4-12) unstable; urgency=medium
 .
   * Switch to Standards-Version 4.5.0 (no changes needed).
   * Remove patches from upstream:
 - tftpd: Restore logging while chrooted. (We do not ship tftpd.)
   * Add patches from upstream:
 - Change header inclusion for ifconfig on GNU/Linux, to support musl.
 - telnetd: More work on CVE-2019-0053.
 - Various compiler warnings fixes.
 - telnet: Various off-by-one checks.
 - ftp: Fix buffer overflows.
 - ping, ping6: Fix memory leaks.
   * Add patch from Red Hat / Fedora:
 - Fix arbitrary remote code execution in telnetd via short writes or
   urgent data. Fixes CVE-2020-10188. Closes: #956084
   Thanks to Michal Ruprich .
   Note: While the PoC exploit does not work on inetutils due to the
   different codebases, the adapted patch was close enough to apply almost
   directly, even though the information leak might appear to still remain.
   * Document inetutils-inetd IPv6 support in man page, and modify the
 default template inetd.conf to use udp6 and tcp6. Closes: #804766
   * Minor wording fixes to default templated inetd.conf.
   * Remove long obsolete netkit-inetd Provides and Conflicts from
 inetutils-inetd.
   * Document that inetutils-inetd -p option without a filename disables
 writing a pidfile. Closes: #951680
   * Disable building tftp and tftpd, which we are not shipping, and are
 causing test suite failures on kfreebsd-amd64.
Checksums-Sha1:
 5652f641db425eb5c8fdbc3a3f721c09b469e75b 3084 inetutils_1.9.4-12.dsc
 c6512c1974fad1f7b03eef8baf0ecc05c6379b70 163 inetutils_1.9.4.orig.tar.xz.asc
 8c43fe43f75e913245a4a55d9895c0df47a19534 112748 
inetutils_1.9.4-12.debian.tar.xz
 1033b60e9fa4e67b99f6dc6b8c33126b35cc0304 12760 
inetutils_1.9.4-12_amd64.buildinfo
Checksums-Sha256:
 8ff53a9f45cbd0fb9065a81ba6120fe51f2291c77187fce4f54fdcc32c8da9db 3084 
inetutils_1.9.4-12.dsc
 d570ff2369cf42238bcfd63cc1faacbc440652d753f4f0b62bb770ba7a497609 163 
inetutils_1.9.4.orig.tar.xz.asc
 bad5caf9be8978f3ea7efa8e6209ee7aab8cc002ef50f81c4286396993e64da8 112748 
inetutils_1.9.4-12.debian.tar.xz
 f8787c4b00435aed181605775d616fc884ed288235a3530

Processed: closing 928792

[Debian Bug Tracking System]

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

> close 928792 3.35.91-1
Bug #928792 [gnome-shell] Please bump dependency on gjs to >= 1.54.0 (for 
gnome-shell >= 3.32.1)
There is no source info for the package 'gnome-shell' at version '3.35.91-1' 
with architecture ''
Unable to make a source version for version '3.35.91-1'
Marked as fixed in versions 3.35.91-1.
Bug #928792 [gnome-shell] Please bump dependency on gjs to >= 1.54.0 (for 
gnome-shell >= 3.32.1)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 765696

[Debian Bug Tracking System]

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

> close 765696 3.20.2-2
Bug #765696 [gnome-shell] gnome-shell: Dependency on gnome-icon-theme-symbolic
Marked as fixed in versions gnome-shell/3.20.2-2.
Bug #765696 [gnome-shell] gnome-shell: Dependency on gnome-icon-theme-symbolic
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#956339: marked as done (unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 23:04:37 +
with message-id 
and subject line Bug#956339: fixed in unattended-upgrades 2.3
has caused the Debian Bug report #956339,
regarding unattended-upgrades: regression: packages with conffile prompts are 
no longer skipped, leading to upgrade failures
to be marked as done.

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

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


-- 
956339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 2.1
Severity: serious

Today I noticed that packages with conffile prompts are no longer
skipped, which can lead to upgrade failures because dpkg stdin is not
connected to any terminal. I think this is a regression since the work
to enable pinning to work with unattended-upgrades.

Package installation log:
Log started: 2020-04-10  13:09:11
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
apt-listchanges: Reading changelogs...
Preparing to unpack .../sgml-base_1.30_all.deb ...
Unpacking sgml-base (1.30) over (1.29.1) ...
Setting up popularity-contest (1.70) ...

Configuration file '/etc/cron.daily/popularity-contest'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** popularity-contest (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package popularity-contest (--configure):
 end of file on stdin at conffile prompt
Errors were encountered while processing:
 popularity-contest
-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages unattended-upgrades depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  lsb-base   11.1.0
ii  lsb-release11.1.0
ii  python33.8.2-2
ii  python3-apt1.9.10
ii  python3-dbus   1.2.16-1
ii  python3-distro-info0.23
ii  ucf3.0038+nmu1
ii  xz-utils   5.2.4-1+b1

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-29
ii  cron [cron-daemon]  3.0pl1-136
ii  systemd-sysv244.3-1

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx  8.1.2-0.20180807cvs-1+b1
ii  exim4-daemon-light [mail-transport-agent]  4.93-13
ii  needrestart3.5-1
ii  powermgmt-base 1.36
ii  python3-gi 3.36.0-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: unattended-upgrades
Source-Version: 2.3
Done: Balint Reczey 

We believe that the bug you reported is fixed in the latest version of
unattended-upgrades, 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.
Balint Reczey  (supplier of updated unattended-upgrades 
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 00:37:21 +0200
Source: unattended-upgrades
Architecture: source
Version: 2.3
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Balint 

Bug#952095: marked as done (xfsdump: FTBFS: gcc: fatal error: no input files)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 08:33:25 +1000
with message-id 

and subject line Re: xfsdump: FTBFS: gcc: fatal error: no input files
has caused the Debian Bug report #952095,
regarding xfsdump: FTBFS: gcc: fatal error: no input files
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> [CC] rmtmsg.lo
> [LD] librmt.la
> ar: `u' modifier ignored since `D' is the default (see `U')
> Building common
> Building inventory
> [LTDEP]
> gcc: fatal error: no input files
> compilation terminated.
> Building invutil
> [LN] global.h
> [LN] mlog.h
> [LN] timeutil.h
> [LN] types.h
> [LN] timeutil.c
> [LN] inventory.h
> [LN] inv_priv.h
> [LN] inv_files.c
> [DEP]
> [CC] timeutil.o
> [CC] inv_files.o
> [CC] invutil.o
> In file included from invutil.c:33:
> types.h:38: warning: "UUID_STR_LEN" redefined
>38 | #define UUID_STR_LEN 36
>   | 
> In file included from /usr/include/xfs/linux.h:8,
>  from /usr/include/xfs/xfs.h:9,
>  from invutil.c:19:
> /usr/include/uuid/uuid.h:65: note: this is the location of the previous 
> definition
>65 | #define UUID_STR_LEN 37
>   | 
> [CC] cmenu.o
> In file included from cmenu.c:30:
> types.h:38: warning: "UUID_STR_LEN" redefined
>38 | #define UUID_STR_LEN 36
>   | 
> In file included from /usr/include/xfs/linux.h:8,
>  from /usr/include/xfs/xfs.h:9,
>  from cmenu.c:19:
> /usr/include/uuid/uuid.h:65: note: this is the location of the previous 
> definition
>65 | #define UUID_STR_LEN 37
>   | 
> [CC] fstab.o
> In file included from fstab.c:30:
> types.h:38: warning: "UUID_STR_LEN" redefined
>38 | #define UUID_STR_LEN 36
>   | 
> In file included from /usr/include/xfs/linux.h:8,
>  from /usr/include/xfs/xfs.h:9,
>  from fstab.c:19:
> /usr/include/uuid/uuid.h:65: note: this is the location of the previous 
> definition
>65 | #define UUID_STR_LEN 37
>   | 
> fstab.c: In function ‘fstab_highlight’:
> fstab.c:167:41: warning: ‘%s’ directive output may be truncated writing up to 
> 255 bytes into a region of size 248 [-Wformat-truncation=]
>   167 | snprintf(txt, sizeof(txt), "device: %s", fstabentry->ft_devpath);
>   | ^~
> fstab.c:167:5: note: ‘snprintf’ output between 9 and 264 bytes into a 
> destination of size 256
>   167 | snprintf(txt, sizeof(txt), "device: %s", fstabentry->ft_devpath);
>   | ^~~~
> [CC] invidx.o
> In file included from invidx.c:31:
> types.h:38: warning: "UUID_STR_LEN" redefined
>38 | #define UUID_STR_LEN 36
>   | 
> In file included from /usr/include/xfs/linux.h:8,
>  from /usr/include/xfs/xfs.h:9,
>  from invidx.c:19:
> /usr/include/uuid/uuid.h:65: note: this is the location of the previous 
> definition
>65 | #define UUID_STR_LEN 37
>   | 
> invidx.c: In function ‘invidx_highlight’:
> invidx.c:704:40: warning: ‘%s’ directive output may be truncated writing up 
> to 255 bytes into a region of size 249 [-Wformat-truncation=]
>   704 | snprintf(txt, sizeof(txt), "path:  %s", invtentry->ie_filename);
>   |^~
> invidx.c:704:5: note: ‘snprintf’ output between 8 and 263 bytes into a 
> destination of size 256
>   704 | snprintf(txt, sizeof(txt), "path:  %s", invtentry->ie_filename);
>   | ^~~
> invidx.c: In function ‘invidx_commit’:
> invidx.c:322:40: warning: ‘%s’ directive output may be truncated writing up 
> to 4095 bytes into a region of size 1020 [-Wformat-truncation=]
>   322 |  snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, dst_stobjfile);
>   |^~  ~
> invidx.c:322:6: note: ‘snprintf’ output 5 or more bytes (assuming 4100) into 
> a destination of size 1024
>   322 |  snprintf(cmd, sizeof(cmd), "cp %s %s", stobjfile, dst_stobjfile);
>   |  ^~~

Bug#757409: marked as done (freecdb: FTBFS with clang instead gcc)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:04 +
with message-id 
and subject line Bug#757409: fixed in freecdb 0.76
has caused the Debian Bug report #757409,
regarding freecdb: FTBFS with clang instead gcc
to be marked as done.

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

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


-- 
757409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecdb
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.5.0rc1&key=UNDEF_REF

Full build log is available here:
http://clang.debian.net/logs/2014-08-05/freecdb_0.75_unstable_clang.log

Thanks,
Arthur

-- System Information:
Debian Release: jessie/sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.5.0-+rc1-2 (tags/RELEASE_35/rc1) (based on 
LLVM 3.5.0)
diff -Naur freecdb.orig/freecdb-0.75/debian/changelog freecdb/freecdb-0.75/debian/changelog
--- freecdb.orig/freecdb-0.75/debian/changelog	2014-08-07 16:01:26.596557008 -0500
+++ freecdb/freecdb-0.75/debian/changelog	2014-08-07 16:04:30.076560204 -0500
@@ -1,3 +1,11 @@
+freecdb (0.76) unstable; urgency=low
+
+  * Fix FTBFS with clang
+- Fixed undefined reference error in
+  cdbmake.c
+  
+ -- Arthur Marble   Thu, 07 Aug 2014 16:04:21 -0500
+
 freecdb (0.75) unstable; urgency=low
 
   * take over upstream (closes: #272127).
diff -Naur freecdb.orig/freecdb-0.75/patches/clang-ftbfs.diff freecdb/freecdb-0.75/patches/clang-ftbfs.diff 
--- freecdb.orig/freecdb-0.75/patches/clang-ftbfs.diff	1969-12-31 18:00:00.0 -0600
+++ freecdb/freecdb-0.75/patches/clang-ftbfs.diff	2014-08-07 16:03:22.460559026 -0500
@@ -0,0 +1,11 @@
+--- a/cdbmake.c
 b/cdbmake.c
+@@ -27,7 +27,7 @@ void die_read(const char *e) {
+   strerr_die5x(111, FATAL, "unable to read input: entry ", s, ": ", e);
+ }
+ 
+-inline void getch() {
++static inline void getch() {
+   switch(buffer_GETC(buffer_0, &ch)) {
+   case 0: die_read("unexpected end if input");
+   case -1: die_read(error_str(errno));
diff -Naur freecdb.orig/freecdb-0.75/patches/series freecdb/freecdb-0.75/patches/series 
--- freecdb.orig/freecdb-0.75/patches/series	1969-12-31 18:00:00.0 -0600
+++ freecdb/freecdb-0.75/patches/series	2014-08-07 16:02:05.284557682 -0500
@@ -0,0 +1 @@
+clang-ftbfs.diff
--- End Message ---
--- Begin Message ---
Source: freecdb
Source-Version: 0.76
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated freecdb 
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, 13 Apr 2020 21:43:06 +0100
Source: freecdb
Architecture: source
Version: 0.76
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 757409
Changes:
 freecdb (0.76) unstable; urgency=medium
 .
   * QA upload.
   * Mark source format as 3.0
   * Update Standards-Version to 4.5.0
   * Orphan the package. (See: #947698)
   * Use debhelper-compat.
 - Mark compat level to 12.
 - Add dependency on ${misc:Depends}.
   * simplify debian/rules.
 - list files to install.
 - list man pages.
 - remove debian/implicit.
   * Fix FTBFS with clang. (Closes: #757409)
 - Thanks to Arthur Marble.
   * Add Vcs link to salsa.
Checksums-Sha1:
 1e7b87f1b046038f397674b02ce153c3a4eca593 1506 freecdb_0.76.dsc
 4b7297d8ce7748b5c6e4f70149d5b39dcf5f71c1 218872 freecdb_0.76.tar.xz
 da4bc89fcb134a058598414cf078560ef75719f7 5240 freecdb_0.76_source.buildinfo
Checksums-Sha256:
 1b61b9d52f62cfd9442b5a2764d1e7606c06e47d9a8fcc14d9782a667f662df7 1506 
freecdb_0.76.dsc
 96af85fc35e2a1527ca6e1de7fbebd8b29dbc11ea24f97e48201002c83c20b50 218872 
freecdb_0.76.tar.xz
 57efde

Bug#952098: marked as done (trigger-rally: FTBFS: SDL_image.h:27:10: fatal error: SDL.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:21 +
with message-id 
and subject line Bug#952098: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #952098,
regarding trigger-rally: FTBFS: SDL_image.h:27:10: fatal error: SDL.h: No such 
file or directory
to be marked as done.

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

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


-- 
952098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trigger-rally
Version: 0.6.6.1-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):
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -Wall -Wextra -pedantic  
> -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DUNIX -DPACKAGE_VERSION=\"0.6.6.1\" 
> -I'./include' -MMD -MP -c PEngine/texture.cpp -o PEngine/texture.o
> In file included from PEngine/texture.cpp:12:
> /usr/include/SDL2/SDL_image.h:27:10: fatal error: SDL.h: No such file or 
> directory
>27 | #include "SDL.h"
>   |  ^~~
> compilation terminated.
> make[1]: *** [GNUmakefile:152: PEngine/texture.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/trigger-rally_0.6.6.1-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: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Checksums-Sha256:
 e91f04119fdf20cbb28c7cdc437a97dd8910d1c0c29c6a526345acf5a5236c01 2827 
libsdl2_2.0.10+dfsg1-3.dsc
 fb6b7a079c7f50df6f205952b95d6d1897b1fee4b2ca85c0ffbc7ff683f794e6 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 059ee0b7835e649d9dc863b9dfbb6182a8ea934ee2c955f36ebab5177dce5280 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Files:
 7041cdc385289ffdafe96fe04ac82f07 2827 libs optional libsdl2_2.0.10+dfsg1-3.dsc
 61dd2b43e2c627062472cbfbe4172909 22512 libs optional 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 4e4f605226a0fafe732c8b22a6dc5236 10310 libs optional 
libsdl2_2.0.10+dfsg1-3_source.buildinfo

---

Bug#952046: marked as done (mrboom: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:21 +
with message-id 
and subject line Bug#952046: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #952046,
regarding mrboom: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such 
file or directory
to be marked as done.

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

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


-- 
952046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrboom
Version: 4.9-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):
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O3 -DMRBOOM 
> -DHAVE_IBXM -D_FORTIFY_SOURCE=0 -DPLATFORM=\"unix\" -DGIT_VERSION=\"" "\" 
> -D__LIBSDL2__ -DLOAD_FROM_FILES -Isdl2/xBRZ  -I./libretro-common/include 
> -I./libretro-common -I./ai -I. -Wall -pedantic -fPIC -std=c++11 -Wdate-time  
> -c -o ai/GridFunctions.o ai/GridFunctions.cpp
> In file included from ./mrboom.h:618,
>  from ai/MrboomHelper.hpp:3,
>  from ai/BotTree.cpp:1:
> /usr/include/SDL2/SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file 
> or directory
>25 | #include "SDL_stdinc.h"
>   |  ^~
> compilation terminated.
> In file included from ./mrboom.h:618,
>  from ai/MrboomHelper.hpp:3,
>  from ai/Bot.hpp:2,
>  from ai/Bot.cpp:1:
> /usr/include/SDL2/SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file 
> or directory
>25 | #include "SDL_stdinc.h"
>   |  ^~
> compilation terminated.
> make[2]: *** [: ai/BotTree.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/mrboom_4.9-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: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Check

Bug#952066: marked as done (jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:21 +
with message-id 
and subject line Bug#952066: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #952066,
regarding jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such 
file or directory
to be marked as done.

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

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


-- 
952066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jag
Version: 0.3.5-5
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):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_OPENGL_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB 
> -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Isrc -Isrc 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o src/gametools.o 
> src/gametools.cpp
> In file included from src/gamesound.h:33,
>  from src/gametools.cpp:33:
> /usr/include/SDL2/SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file 
> or directory
>25 | #include "SDL_stdinc.h"
>   |  ^~
> compilation terminated.
> make[1]: *** [Makefile:795: src/gametools.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/jag_0.3.5-5_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: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Checksums-Sha256:
 e91f04119fdf20cbb28c7cdc437a97dd8910d1c0c29c6a526345acf5a5236c01 2827 
libsdl2_2.0.10+dfsg1-3

Bug#952182: marked as done (awl: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:18:47 +
with message-id 
and subject line Bug#952182: fixed in awl 0.61-1
has caused the Debian Bug report #952182,
regarding awl: FTBFS: dh_auto_test: error: make -j1 test 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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # simple php syntax check
> OK (Syntax checked)
> # run phpunit tests
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:./vendor/bin/
>  phpunit tests/
> PHP Fatal error:  Declaration of vComponentTest::setUp() must be compatible 
> with PHPUnit\Framework\TestCase::setUp(): void in 
> /<>/tests/myComponentTest.php on line 32
> make[1]: *** [Makefile:52: test] Error 255
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j1 test returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/awl_0.60-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: awl
Source-Version: 0.61-1
Done: Florian Schlichting 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 21:37:06 +0200
Source: awl
Architecture: source
Version: 0.61-1
Distribution: unstable
Urgency: medium
Maintainer: Davical Development Team 
Changed-By: Florian Schlichting 
Closes: 952182 956650
Changes:
 awl (0.61-1) unstable; urgency=medium
 .
   * New upstream release (closes: #952182, #956650)
 + fix CVE-2020-11728 "Session::__construct() allows use of the current
   time as a session key"
 + fix CVE-2020-11729 "LSIDLogin() is insecure and can allow user
   impersonation"
   * Bump debhelper compat to level 12
   * Update copyright years
   * Add upstream metadata
   * Declare compliance with Debian Policy 4.5.0
Checksums-Sha1:
 cbe2fa1f7a7b314ffe687ec032dfb5cc0d8b3a3e 1949 awl_0.61-1.dsc
 86d525284036c02a5c29b108dcd7108b2adeb908 124340 awl_0.61.orig.tar.xz
 9d6412f0ca6796b0814d6df84d14ddde808f4f03 7020 awl_0.61-1.debian.tar.xz
 a0c41fc17a7a2c42a898b9ecb9078dfbec000697 7740 awl_0.61-1_amd64.buildinfo
Checksums-Sha256:
 37f1836a666d7c8858f893037d2e5201c4e034e06a3b592a45788b2ea0b00bb3 1949 
awl_0.61-1.dsc
 fc8b8bea609483feba7ac985b074c5341633d2b9a756ee894737ae5aec00dee3 124340 
awl_0.61.orig.tar.xz
 fbb635f6954dec3644fbfe0efecd20dae67b6769b554792b24b699fc9953765c 7020 
awl_0.61-1.debian.tar.xz
 334a8f542b450b3c5629e6d0b1fad786de298ac46c54886adf936cc9e459f9fb 7740 
awl_0.61-1_amd64.buildinfo
Files:
 9c7da0380668aaa8d5a56c6e4007c980 1949 php optional awl_0.61-1.dsc
 b22ee3e4a09f4b68ab1ec714319b9e41 124340 php optional awl_0.61.orig.tar.xz
 77e1ebdeffd94d82cc38913b0a7a4a05 7020 php optional awl_0.61-1.debian.tar.xz
 6e5d7d2b0fff5e3977acf01ae77cc31f 7740 php optional awl_0.61-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEMLI8i05qOwnqprZSEpc7bnLcB7UFAl6U398ACgkQEpc7bnLc
B7VWSBAAh8+e/lQguV9hEf3xHJUs9qbORJ6+bYwjsIav2EnWSPgqZMk7UUw4MrCo
dhNPp7ENlZ83Gi32IfcA0Xd4+HOHZpadeXv+NRe/Z0H97Dvid2Y0FVtdv2W54CYA
35JQwOY/dr8e8i39UEm0Xa8dXx1w/iFRhJmfV4e8jLRe/U0jTkTs+L9fEShlEQLq
9CC4Gsc/1w5BuGgdLDYlOnaDwbfRjyq2Fpia4FLgYUgsUaNyEkB/uUOIwkgo6YLW
FckCczINfoHMVY+DgE2Rid97HbcahGdGlbu

Bug#956650: marked as done (awl: CVE-2020-11728 CVE-2020-11729)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:18:47 +
with message-id 
and subject line Bug#956650: fixed in awl 0.61-1
has caused the Debian Bug report #956650,
regarding awl: CVE-2020-11728 CVE-2020-11729
to be marked as done.

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

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


-- 
956650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: awl
Version: 0.60-1
Severity: important
Tags: security upstream

Two security vulnerabilities were found in the awl package:

CVE-2020-11728
Session::__construct() allows use of the current time as a session key
https://gitlab.com/davical-project/awl/-/issues/19

CVE-2020-11729
LSIDLogin() is insecure and can allow user impersonation
https://gitlab.com/davical-project/awl/-/issues/18

All supported Debian releases are affected.
--- End Message ---
--- Begin Message ---
Source: awl
Source-Version: 0.61-1
Done: Florian Schlichting 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 21:37:06 +0200
Source: awl
Architecture: source
Version: 0.61-1
Distribution: unstable
Urgency: medium
Maintainer: Davical Development Team 
Changed-By: Florian Schlichting 
Closes: 952182 956650
Changes:
 awl (0.61-1) unstable; urgency=medium
 .
   * New upstream release (closes: #952182, #956650)
 + fix CVE-2020-11728 "Session::__construct() allows use of the current
   time as a session key"
 + fix CVE-2020-11729 "LSIDLogin() is insecure and can allow user
   impersonation"
   * Bump debhelper compat to level 12
   * Update copyright years
   * Add upstream metadata
   * Declare compliance with Debian Policy 4.5.0
Checksums-Sha1:
 cbe2fa1f7a7b314ffe687ec032dfb5cc0d8b3a3e 1949 awl_0.61-1.dsc
 86d525284036c02a5c29b108dcd7108b2adeb908 124340 awl_0.61.orig.tar.xz
 9d6412f0ca6796b0814d6df84d14ddde808f4f03 7020 awl_0.61-1.debian.tar.xz
 a0c41fc17a7a2c42a898b9ecb9078dfbec000697 7740 awl_0.61-1_amd64.buildinfo
Checksums-Sha256:
 37f1836a666d7c8858f893037d2e5201c4e034e06a3b592a45788b2ea0b00bb3 1949 
awl_0.61-1.dsc
 fc8b8bea609483feba7ac985b074c5341633d2b9a756ee894737ae5aec00dee3 124340 
awl_0.61.orig.tar.xz
 fbb635f6954dec3644fbfe0efecd20dae67b6769b554792b24b699fc9953765c 7020 
awl_0.61-1.debian.tar.xz
 334a8f542b450b3c5629e6d0b1fad786de298ac46c54886adf936cc9e459f9fb 7740 
awl_0.61-1_amd64.buildinfo
Files:
 9c7da0380668aaa8d5a56c6e4007c980 1949 php optional awl_0.61-1.dsc
 b22ee3e4a09f4b68ab1ec714319b9e41 124340 php optional awl_0.61.orig.tar.xz
 77e1ebdeffd94d82cc38913b0a7a4a05 7020 php optional awl_0.61-1.debian.tar.xz
 6e5d7d2b0fff5e3977acf01ae77cc31f 7740 php optional awl_0.61-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEMLI8i05qOwnqprZSEpc7bnLcB7UFAl6U398ACgkQEpc7bnLc
B7VWSBAAh8+e/lQguV9hEf3xHJUs9qbORJ6+bYwjsIav2EnWSPgqZMk7UUw4MrCo
dhNPp7ENlZ83Gi32IfcA0Xd4+HOHZpadeXv+NRe/Z0H97Dvid2Y0FVtdv2W54CYA
35JQwOY/dr8e8i39UEm0Xa8dXx1w/iFRhJmfV4e8jLRe/U0jTkTs+L9fEShlEQLq
9CC4Gsc/1w5BuGgdLDYlOnaDwbfRjyq2Fpia4FLgYUgsUaNyEkB/uUOIwkgo6YLW
FckCczINfoHMVY+DgE2Rid97HbcahGdGlbuhCO3F7FcvGEeD64yq5Ig7AJyXafNk
o9yA4WQ6EtBTRNUHSSnCYyUqIMsYbqt0XjebW9eTUrj+9zZ7uSrD8M24YESoPMqr
deGmlmsEHtjARuinj+o5hrVgF2dE3Yb7lUpdhkozD6AITFKUiahpJMKrn4e3xcFU
jjfN7cA2g1uNfBYY6qIPymdWqWf3+mRU3vLihXLMLuSjBlO/KsGU8kxt0Tw/pL/K
HF+Rkh+OFH70vpWYFJWF2LRRVJwaLoGQagrB3TKcYRyKKhlUk7UZ+zQ45k/ZanWm
V3SJkb88SqAR0lH0gU78nGgpFlJeYoNu24bFCYJ5QccmnSVHnhZLds1gMcCUnGBy
LMFgbPhO4aVPkNysRs70oNM5LMKHouh20T1AN+5eB38j/1NKbjk=
=7ku8
-END PGP SIGNATURE End Message ---

Bug#951962: marked as done (fife: FTBFS: Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR))

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:20 +
with message-id 
and subject line Bug#951962: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #951962,
regarding fife: FTBFS: Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR)
to be marked as done.

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

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


-- 
951962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fife
Version: 0.4.2-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):
> /usr/bin/ld: CMakeFiles/cmTC_dbfd9.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/fife_0.4.2-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: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Checksums-Sha256:
 e91f04119fdf20cbb28c7cdc437a97dd8910d1c0c29c6a526345acf5a5236c01 2827 
libsdl2_2.0.10+dfsg1-3.dsc
 fb6b7a079c7f50df6f205952b95d6d1897b1fee4b2ca85c0ffbc7ff683f794e6 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 059ee0b7835e649d9dc863b9dfbb6182a8ea934ee2c955f36ebab5177dce5280 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Files:
 7041cdc385289ffdafe96fe04ac82f07 2827 libs optional libsdl2_2.0.10+dfsg1-3.dsc
 61dd2b43e2c627062472cbfbe4172909 22512 libs optional 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 4e4f605226a0fafe732c8b22a6dc5236 10310 libs optional 
libsdl2_2.0.10+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiE

Bug#951087: marked as done (libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:20 +
with message-id 
and subject line Bug#951087: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #951087,
regarding libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2
to be marked as done.

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

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


-- 
951087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjk
Version: 0~20191030.4881be7~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

openjk FTBFS against libsdl2 2.0.10+dfsg1-2 which has moved the headers
to an arch-dependent location:

[ 53%] Building CXX object 
code/CMakeFiles/openjo_sp.x86_64.dir/client/cl_cgame.cpp.o
cd "/build/openjk-0~20191030.4881be7~dfsg/obj/code" && /usr/bin/c++  
-DARCH_STRING=\"x86_64\" -DFINAL_BUILD -DJK2_MODE -DSOURCE_DATE="\"Nov  2 
2019\"" -D_JK2EXE -I"/build/openjk-0~20191030.4881be7~dfsg/shared" -I"
/build/openjk-0~20191030.4881be7~dfsg/code" 
-I"/build/openjk-0~20191030.4881be7~dfsg/lib/gsl-lite/include" 
-I"/build/openjk-0~20191030.4881be7~dfsg/lib/minizip/include"  -g -O2 
-fdebug-prefix-map=/build/openjk-0~2
0191030.4881be7~dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wno-unused-parameter 
-Wno-missing-field-initializers -fno-strict-aliasing -Wno-strict-aliasing 
-Wno-unused-but-set-variable  
 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -msse2 -std=c++11 -Wall 
-Wno-invalid-offsetof -Wno-write-strings -Wno-comment -fsigned-char 
-mstackrealign -mfpmath=sse   -fvisibility=hidden -o CMakeFiles/openjo_sp.x86_6
4.dir/client/cl_cgame.cpp.o -c 
"/build/openjk-0~20191030.4881be7~dfsg/code/client/cl_cgame.cpp"
In file included from 
/build/openjk-0~20191030.4881be7~dfsg/code/client/cl_cgame.cpp:34:
/build/openjk-0~20191030.4881be7~dfsg/shared/sys/sys_loadlib.h:39:11: fatal 
error: SDL.h: No such file or directory
   39 | # include 
  |   ^~~
compilation terminated.


Andreas


openjk_0~20191030.4881be7~dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Checksums-Sha256:
 e91f04119fdf20cbb28c7cdc437a97dd8910d1c0c29c6a526345acf5a5236c01 2827 
libsdl2_2.0.10+dfsg1-3.dsc
 fb6b7a079c7f50df6f205952b95d6d1897b1fee4b2ca85c0ffbc7ff683f794e6 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 059ee0b7835e649d9dc863b9dfb

Bug#955416: marked as done (hedgewars: FTBFS with newer SDL)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:19:21 +
with message-id 
and subject line Bug#955416: fixed in libsdl2 2.0.10+dfsg1-3
has caused the Debian Bug report #955416,
regarding hedgewars: FTBFS with newer SDL
to be marked as done.

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

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


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

Dear Maintainer,

hedgewars is also affected by #951087, but it seems that no bug has been filed.

The quoted bugs above has some hints how to fix the issue.

-- 
tobi

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libsdl2
Source-Version: 2.0.10+dfsg1-3
Done: Simon McVittie 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 18:27:11 +0100
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 909740 951087 951943 951959 951962 951974 951976 952046 952049 952066 
952098 952105 955416
Changes:
 libsdl2 (2.0.10+dfsg1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Gianfranco Costamagna ]
   * Fix autopkgtests for cross-architecture testing, by making sure
 sdl2-config calls the correct pkg-config command
 .
   [ Simon McVittie ]
   * Revert "Add the non-multiarch include dir to pkg-config cflags for
 compatibility."
   * Revert "Install all headers in an architecture-specific location"
   * Make SDL_config.h redirect to an architecture-specific version
 (Closes: #909740, #951087, #951943, #951959, #951974, #951976, #952049,
 #951962, #952105, #955416)
   * Create a SDL_platform.h symlink in /usr/include/MULTIARCH/SDL2
 (Closes: #952046, #952066, #952098)
   * Add autopkgtests for various deprecated use patterns
Checksums-Sha1:
 fce34a37dde0bf0bafb4e0c06585b65f741c14f1 2827 libsdl2_2.0.10+dfsg1-3.dsc
 c559d011c161c6829488cae24cc51331e9935553 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 6ec44949de737cfbee4cb836abd5c478aac890e8 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Checksums-Sha256:
 e91f04119fdf20cbb28c7cdc437a97dd8910d1c0c29c6a526345acf5a5236c01 2827 
libsdl2_2.0.10+dfsg1-3.dsc
 fb6b7a079c7f50df6f205952b95d6d1897b1fee4b2ca85c0ffbc7ff683f794e6 22512 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 059ee0b7835e649d9dc863b9dfbb6182a8ea934ee2c955f36ebab5177dce5280 10310 
libsdl2_2.0.10+dfsg1-3_source.buildinfo
Files:
 7041cdc385289ffdafe96fe04ac82f07 2827 libs optional libsdl2_2.0.10+dfsg1-3.dsc
 61dd2b43e2c627062472cbfbe4172909 22512 libs optional 
libsdl2_2.0.10+dfsg1-3.debian.tar.xz
 4e4f605226a0fafe732c8b22a6dc5236 10310 libs optional 
libsdl2_2.0.10+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl6U39EACgkQ4FrhR4+B
TE9EuxAAqicTOUHgrkKo4AJCLAJXAvatgGBDwkCh2+2Ly+sYMoHZfH3T3lfeY3hB
P8hiMOfhCuyzM4AtgoUZwwhOevDiOru0jZPoSrWC/Mz2STSPNmAF6svINcdbiCJd
N7/UDSRjYaWaH82O99eynP6EtIRnuLZJV3MPdMiTarVZHvhCoOjbxVJiFg1PnIqL
J02SZW5Cvg51LMVeOmunJeSijH3nvQwm6kmL5KY99QeR8L9cWQcBOPYLjEczH4XQ
NTpLJZQmWrTdPNYzYsvNtEO3dBZWs96n9tQLgg0/LM3Tb0b2kohUwqlWtTP8FNIR
Xvnt5FLyMksodIrSKyMw31cIQknRy22feBPrqc12k1Mc4Hcf+C5eIwrgP1TkfKTV
xOeVyhuzGbsiAVaankgB1v0bazsG/ZHLUlyBE0EO9I57tYOT+vEiNz/R4Dj1haeF
fG2SvLhkxem/50s3

Bug#956613: marked as done (lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 17:47:36 -0400
with message-id <877dyjys5j@fifthhorseman.net>
and subject line Re: Bug#956613: lintian: 
inconsistent-appstream-metadata-license is confused when appstream metadata 
file is generated
has caused the Debian Bug report #956613,
regarding lintian: inconsistent-appstream-metadata-license is confused when 
appstream metadata file is generated
to be marked as done.

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

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


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

in balsa 2.6.0, balsa.appdata.xml is generated during the build from
balsa.appdata.xml.in.

While d/copyright correctly indicates that balsa.appdata.xml.in is
CC0-1.0, lintian still complains with:

W: balsa source: inconsistent-appstream-metadata-license balsa.appdata.xml 
(cc0-1.0 != gpl-2+)

It seems that to quiet this warning, i would need to add a d/copyright
entry for a file (balsa.appdata.xml) that is not shipped in the source
package, which would be weird and (i think) wrong.

Rather, i think lintian should avoid warning about license information
in a file that is not part of the source package.

Thanks for maintaining lintian in debian!

   --dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Mon 2020-04-13 09:52:32 -0700, Felix Lechner wrote:
> I do not see that tag when running lintian's development version
> against balsa from unstable:

there are separate issues with the appdata files in 2.5.9 (that have
since been fixed upstream):

   https://gitlab.gnome.org/GNOME/balsa/-/merge_requests/22

so the issue only shows up in 2.6.0 (which just landed in unstable
today)

> Lintian should not complain, for a source package, about files not
> shipped within it. Was the file perhaps included accidentally?

ah, i might have gotten confused about the file name due to it being
overwritten during the build.  i do most of my packaging work from a gbp
tree, and that tree has the generated files already pre-stripped (via an
import-orig filter in debian/gbp.conf).

Looks like upstream does in fact ship a copy of these generated files in
the tarball, though, so i probably should mark them in debian/copyright
anyway.

I'm closing this ticket because it looks like i do need to mark the
generated file in d/copyright anyway, which means there's a more obvious
fix for me to do in this packaging.

sorry for the noise!

--dkg


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

Bug#937559: marked as done (pytest-expect: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:04:23 +
with message-id 
and subject line Bug#937559: fixed in pytest-expect 1.1.0-2
has caused the Debian Bug report #937559,
regarding pytest-expect: 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.)


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

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: pytest-expect
Source-Version: 1.1.0-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
pytest-expect, 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 pytest-expect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 17:48:44 -0400
Source: pytest-expect
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937559
Changes:
 pytest-expect (1.1.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 9 to 12.
   * Set upstream metadata fields: Bug-Database, Repository, Repository-
 Browse.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937559
   * Update Homepage field
Checksums-Sha1:
 fc3549bf1f395ab4041404891f7c228e16541e96 2058 pytest-expect_

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

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:04:29 +
with message-id 
and subject line Bug#938256: fixed in python-webencodings 0.5.1-2
has caused the Debian Bug report #938256,
regarding python-webencodings: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-webencodings

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-webencodings
Source-Version: 0.5.1-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
python-webencodings, 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-webencodings package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 17:51:08 -0400
Source: python-webencodings
Architecture: source
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938256
Changes:
 python-webencodings (0.5.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Remove ancient X-Python3-Version field.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 9 to 12.
   * Set upstream metadata fields: Repository, Repository-Browse.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938256
Checksums-Sha1:
 2393bd13a18d15e7d7b416ba03843725778ad81a 2190 python-webencodings_0.5.1-2.dsc
 78333596858b157ef451137734c0b3897e659a67 3192 
python-webencodings_0.5.1-2.debian.tar.xz
 2a5c9931496209618960001f1e6b17c1b7be5483 6551 
python-webencodings_0.5.1-2_source.buildinfo
Checksums-Sha

Bug#936599: marked as done (genshi: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:04:06 +
with message-id 
and subject line Bug#936599: fixed in genshi 0.7.3-2
has caused the Debian Bug report #936599,
regarding genshi: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:genshi

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: genshi
Source-Version: 0.7.3-2
Done: Sandro Tosi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 17:46:20 -0400
Source: genshi
Architecture: source
Version: 0.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936599
Changes:
 genshi (0.7.3-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #936599
Checksums-Sha1:
 d946b5319f0d1119d5ae52131e96bdc6ea63ec03 2089 genshi_0.7.3-2.dsc
 5eafc04b28557de95fc01b412727487051ea65c3 56640 genshi_0.7.3-2.debian.tar.xz
 3d9ea4801b5b255887486c2f0018375abd64d6d5 6484 genshi_0.7.3-2_source.buildinfo
Checksums-Sha256:
 a9ebeff8fcf8fca44c19729fca11691c86fae5d092dcb3eed62366460e0a284d 2089 
genshi_0.7.3-2.dsc
 b3e9c3d79f17225bc176af6b65031b5c25208ad2a5ce10e57d605946f316e4ea 56640 
genshi_0.7.3-2.debian.tar.xz
 c98a36c1dd2b6646823ab5937f5552213887337018de17d8be0b31dadf39a830 6484 
genshi_0.7.3-2_source.buildinfo
Files:
 e7b93aa2b039c45bc7c50c2b30a19311 2089 python optional genshi_0.7.3-2.dsc
 c4bc0e19b690854ab563e51500d6b9ce 5664

Bug#932914: marked as done (gitlab: Increase version dependency of ruby-fog-google)

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 03:19:15 +0530
with message-id <239f3210-fc03-4b1c-99c6-0d8b98e1f...@onenetbeyond.org>
and subject line Closing old bug
has caused the Debian Bug report #932914,
regarding gitlab: Increase version dependency of ruby-fog-google
to be marked as done.

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

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


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

Dear Maintainer,

after upgrading the package from stretch-backports to buster-backports and
fasttrack the process failed. gitlab has ruby-fog-google > 1.8.2 as dependency
but the installation detects that is not enough.

It could be solve simple instaling manually:

apt-get install -t buster-backports ruby-fog-google.


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

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

Versions of packages gitlab depends on:
ii  asciidoctor1.5.8-1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9.1
ii  dbconfig-pgsql 2.0.11
ii  debconf [debconf-2.0]  1.5.71
ii  exim4  4.92-8
ii  exim4-daemon-light [mail-transport-agent]  4.92-8
ii  gitlab-common  11.10.8+dfsg-1+fto10+1
ii  gitlab-workhorse   8.5.2+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]  4.3.1+dfsg2-1
ii  libjs-pdf  1.5.188+dfsg-1~bpo10+1
ii  libjs-popper.js [node-popper.js]   1.14.6+ds2-1
ii  libjs-uglify   2.8.29-6
ii  lsb-base   10.2019051400
ii  nginx  1.14.2-2
ii  nginx-full [nginx] 1.14.2-2
ii  node-autosize  4.0.2~dfsg1-3
ii  node-axios 0.17.1+dfsg-2
ii  node-brace-expansion   1.1.8-1
ii  node-chart.js  2.7.3+dfsg-5
ii  node-core-js   2.4.1-2
ii  node-css-loader1.0.1-1
ii  node-d3-array  1.2.1-3
ii  node-d3-axis   1.0.8-3
ii  node-d3-brush  1.0.4-3
ii  node-d3-ease   1.0.3-3
ii  node-d3-scale  1.0.7-3~bpo10+1
ii  node-d3-selection  1.4.0-3~bpo10+1
ii  node-d3-shape  1.2.0-2
ii  node-d3-time   1.0.11-3~bpo10+1
ii  node-d3-time-format2.1.3-2~bpo10+1
ii  node-d3-transition 1.2.0-3~bpo10+1
ii  node-dateformat3.0.0-1
ii  node-fuzzaldrin-plus   0.5.0+dfsg-1
ii  node-glob  7.1.3-2
ii  node-jed   1.1.1-1
ii  node-jquery3.4.0+dfsg-1~bpo10+1
ii  node-jquery-ujs1.2.2-2
ii  node-jquery.waitforimages  2.4.0+ds-1
ii  node-js-cookie 2.2.0-2
ii  node-jszip 3.1.4+dfsg-1
ii  node-jszip-utils   0.0.2+dfsg-1
ii  node-mousetrap 1.6.1+ds-1
ii  node-pikaday   1.8.0-1
ii  node-raven-js  3.22.1+dfsg-2
ii  node-three-orbit-controls  82.1.0-2
ii  node-three-stl-loader  1.0.6-2
ii  node-timeago.js3.0.2+dfsg-3
ii  node-underscore1.9.1~dfsg-1
ii  node-vue-resource  1.5.1+dfsg-3~bpo10+1
ii  node-webpack-stats-plugin  0.2.1-1
ii  nodejs 10.15.2~dfsg-2
ii  openssh-client 1:7.9p1-10
ii  postgresql-client  11+200+deb10u1
ii  postgresql-client-11 [postgresql-client]   11.4-1
ii  postgresql-client-9.6 [postgresql-client]  9.6.13-0+

Bug#925606: marked as done (gitlab: Fail to upgrade (error with activesupport gem))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 03:16:07 +0530
with message-id 
and subject line Closing old bug
has caused the Debian Bug report #925606,
regarding gitlab: Fail to upgrade (error with activesupport gem)
to be marked as done.

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

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


-- 
925606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 11.8.3-1+fto10+1
Severity: important

Hi,

Doing an apt-get upgrade fails to install gitlab (upgrading from 11.8.2).

The error message are:

Bundle complete! 187 Gemfile dependencies, 315 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Running final rake tasks and tweaks...
gitlab_production database is not empty, skipping gitlab setup
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
rake aborted!
LoadError: cannot load such file -- sprockets/rails/context
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:81:in
 `block (2 levels) in require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in
 `block in require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler.rb:114:in 
`require'
/usr/share/gitlab/config/application.rb:5:in `'
/usr/share/gitlab/Rakefile:5:in `require'
/usr/share/gitlab/Rakefile:5:in `'
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)


Downgrading package to previous working version gives the same error.


Thanks,


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

Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor1.5.8-1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9
ii  dbconfig-pgsql 2.0.11
ii  debconf [debconf-2.0]  1.5.71
ii  exim4-daemon-light [mail-transport-agent]  4.92-2
ii  gitlab-common  11.8.3-1+fto10+1
ii  gitlab-workhorse   7.6.0+debian-1+b20
ii  libjs-

Bug#925254: marked as done (gitlab: Failed to upgrade (google-api-client not installed))

[Debian Bug Tracking System]

Your message dated Tue, 14 Apr 2020 03:13:29 +0530
with message-id 
and subject line Closing old bug
has caused the Debian Bug report #925254,
regarding gitlab: Failed to upgrade (google-api-client not installed)
to be marked as done.

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

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


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

Dear Maintainer,

I was trying to upgrade gitlab from 11.5.10 to the current version
(11.8.2-3) in unstable. Most required packages are coming from buster
with a few dependencies coming from unstable.

The output from apt is as follows:

Setting up gitlab (11.8.2-3) ...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Bundler could not find compatible versions for gem "google-api-client":
  In Gemfile:
google-api-client (~> 0.23)

fog-google (~> 1.8) was resolved to 1.8.2, which depends on
  google-api-client (~> 0.23.0)

Could not find gem 'google-api-client (~> 0.23.0)', which is required by gem
'fog-google (~> 1.8)', in any of the sources.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have no experience with ruby and how I can fix this. If you need more
information please tell me and I'll try to provide it.

One last thing, I am very grateful for providing gitlab in Debian. This
must be an huge job with all the dependencies in ruby. Thank you!

Regards, Matthijs

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

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

Versions of packages gitlab depends on:
ii  asciidoctor1.5.8-1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9
ii  dbconfig-pgsql 2.0.11
ii  debconf [debconf-2.0]  1.5.71
ii  gitlab-common  11.8.2-3
ii  gitlab-workhorse   7.6.0+debian-1+b20
ii  libjs-uglify   2.8.29-6
ii  lsb-base   10.2019031300
ii  nginx  1.14.2-2
ii  nginx-full [nginx] 1.14.2-2
ii  nodejs 10.15.2~dfsg-1
ii  openssh-client 1:7.9p1-9
ii  postfix [mail-transport-agent] 3.4.1-1
ii  postgresql-client  11+200
ii  postgresql-client-11 [postgresql-client]   11.2-2
ii  postgresql-client-9.6 [postgresql-client]  9.6.10-0+deb9u1
ii  postgresql-contrib 11+200
ii  rake   12.3.1-3
ii  redis-server   5:5.0.3-4
ii  ruby   1:2.5.1
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   6.0.0-3
ii  ruby-addressable   2.5.2-1
ii  ruby-akismet   2.0.0-1
ii  ruby-asana 0.8.1-2
ii  ruby-asciidoctor-plantuml  0.0.8-1
ii  ruby-attr-encrypted3.1.0-2
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.2-1
ii  ruby-bcrypt-pbkdf  1.0.0-2
ii  ruby-bootstrap-form2.7.0-1
ii  ruby-browser   2.5.3-1
ii  ruby-carrierwave   1.3.1-1
ii  ruby-charlock-holmes   0.7.6-1
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1
ii  ruby-connection-pool  

Bug#942937: marked as done (dawgdic: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:33:41 +
with message-id 
and subject line Bug#942937: fixed in dawgdic 0.4.5-3
has caused the Debian Bug report #942937,
regarding dawgdic: 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.)


-- 
942937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dawgdic
Version: 0.4.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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

We believe that the bug you reported is fixed in the latest version of
dawgdic, 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.
Moritz Muehlenhoff  (supplier of updated dawgdic 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, 13 Apr 2020 19:15:31 +0200
Source: dawgdic
Architecture: source
Version: 0.4.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Moritz Muehlenhoff 
Closes: 942937
Changes:
 dawgdic (0.4.5-3) unstable; urgency=medium
 .
   * Set maintainer to Debian QA Group
   * Use debhelper 10
   * Switch to python3-docutils3 (Closes: #942937)
Checksums-Sha1:
 d00c5866dbe28a0f4a6edcec71330f6df7342e8f 1900 dawgdic_0.4.5-3.dsc
 0b982fc1df2cafb20bbcc0c2ec85ae6efba78a1d 5356 dawgdic_0.4.5-3.debian.tar.xz
 e8eb44514bfbe405c98f48335f891fc6521245f3 6595 dawgdic_0.4.5-3_amd64.buildinfo
Checksums-Sha256:
 c21c4ffa015b8628b612fa4ba9209c5f4a9a61fb766623227665ce68075f6943 1900 
dawgdic_0.4.5-3.dsc
 e7aaf25833adff808e7c516fe49806c67759bca22f75aca9c444615f2df10d60 5356 
dawgdic_0.4.5-3.debian.tar.xz
 aac036559a450c454443b481d27e1e325ca1c402b61ed6929912f17235edca68 6595 
dawgdic_0.4.5-3_amd64.buildinfo
Files:
 debc46f35274ced8306ae614915e4c3e 1900 libs optional dawgdic_0.4.5-3.dsc
 e43017ddcd124842e12c610850c2eae2 5356 libs optional 
dawgdic_0.4.5-3.debian.tar.xz
 f4385c85f72e7893d8d3965af9

Bug#951739: marked as done (fontmatrix FTCBFS: runs cmake for the build architecture)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:34:19 +
with message-id 
and subject line Bug#951739: fixed in fontmatrix 0.9.99-2
has caused the Debian Bug report #951739,
regarding fontmatrix FTCBFS: runs cmake 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.)


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

fontmatrix fails to cross build from source, because it does not pass
cross compilation flags to cmake. The easiest way of doing so - using
dh_auto_configure - makes fontmatrix cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru fontmatrix-0.9.99/debian/changelog 
fontmatrix-0.9.99/debian/changelog
--- fontmatrix-0.9.99/debian/changelog  2020-02-17 12:09:08.0 +0100
+++ fontmatrix-0.9.99/debian/changelog  2020-02-20 22:53:58.0 +0100
@@ -1,3 +1,10 @@
+fontmatrix (0.9.99-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 20 Feb 2020 22:53:58 +0100
+
 fontmatrix (0.9.99-1) unstable; urgency=medium
 
   * Add debian/missing-sources. (Closes: #744698)
diff --minimal -Nru fontmatrix-0.9.99/debian/rules 
fontmatrix-0.9.99/debian/rules
--- fontmatrix-0.9.99/debian/rules  2019-07-30 09:45:03.0 +0200
+++ fontmatrix-0.9.99/debian/rules  2020-02-20 22:53:58.0 +0100
@@ -24,11 +24,10 @@
 configure-stamp:
dh_testdir
mkdir -p $(BUILD_DIR)
-   cd $(BUILD_DIR) && $(CMAKE) \
-   -DCMAKE_INSTALL_PREFIX:PATH=/usr \
+   dh_auto_configure --builddirectory=$(BUILD_DIR) -- \
-DCMAKE_SKIP_RPATH:BOOL=1 \
-DRPATH_STYLE:STRING=none \
-   -DCMAKE_C_FLAGS:STRING='$(OPT_FLAG)' ../../
+   -DCMAKE_C_FLAGS:STRING='$(OPT_FLAG)'
 #for the future   -DWANT_PODOFO:bool=1
touch configure-stamp
 #-DCMAKE_BUILD_TYPE=Debug
--- End Message ---
--- Begin Message ---
Source: fontmatrix
Source-Version: 0.9.99-2
Done: =?utf-8?q?G=C3=BCrkan_Myczko?= 

We believe that the bug you reported is fixed in the latest version of
fontmatrix, 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.
Gürkan Myczko  (supplier of updated fontmatrix 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 12:32:21 +0200
Source: fontmatrix
Architecture: source
Version: 0.9.99-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Gürkan Myczko 
Closes: 951739
Changes:
 fontmatrix (0.9.99-2) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Team upload.
   * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake.
 (Closes: #951739)
 .
   [ Gürkan Myczko ]
   * Thanks Helmut Grohne for the patch.
Checksums-Sha1:
 f06f251af1fc914066bd7884c84c3830398836a0 2100 fontmatrix_0.9.99-2.dsc
 43700fd3a74db4db75a4095a5a4c36739daa3135 10320 
fontmatrix_0.9.99-2.debian.tar.xz
 73e8664a12a9bf58b2cead2a5901be6d3c77aa9d 11289 
fontmatrix_0.9.99-2_source.buildinfo
Checksums-Sha256:
 a44bd20e7016bd0a1f2d06d3a7a427c095b69b622eb9f75ff6980268ce26b1e1 2100 
fontmatrix_0.9.99-2.dsc
 ad9f6d93a696c291d138add950508894c6a7b74c33630c54c340681ba6b6fdcc 10320 
fontmatrix_0.9.99-2.debian.tar.xz
 2db7a260f85c69883ed15285bba42fa97383cfd192f319670cf4ee5ec2e344c3 11289 
fontmatrix_0.9.99-2_source.buildinfo
Files:
 64aa94b944aa2f847b4c5dcdc0fbe77a 2100 graphics optional fontmatrix_0.9.99-2.dsc
 86c910dcd49953fb7bfa7f12b5620f4a 10320 graphics optional 
fontmatrix_0.9.99-2.debian.tar.xz
 61650cb9f4ace2e50f8434b3daf3f781 11289 graphics optional 
fontmatrix_0.9.99-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl6U1eAACgkQweDZLphv
fH46qA//XMQg2thZjdqffnblL0/a4FOVt3gJHH8QsY4wuQkQSSqUr9sxYmc6ToJo
meKLJPCiER7FL1lR0rbd+BIEibZqyWkiHJb4PyLGWCFrU9c2GTU8JjxfhcsVRJs3
b

Bug#953705: marked as done (src:rust-futures: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 22:15:20 +0100
with message-id 
and subject line re: src:rust-futures: fails to migrate to testing for too long
has caused the Debian Bug report #953705,
regarding src:rust-futures: fails to migrate to testing for too long
to be marked as done.

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

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


-- 
953705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-futures
Version: 0.1.28-2
Severity: serious
Control: fixed -1 0.1.29-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:rust-futures
in its current version in unstable has been trying to migrate for 145
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-futures




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

The old version has been removed from testing (and hopefully the new version 
will be back in soon).--- End Message ---

Bug#946328: marked as done (pd-bsaylor FTCBFS: strips with the wrong strip)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:05:06 +
with message-id 
and subject line Bug#946328: fixed in pd-bsaylor 0.1-6
has caused the Debian Bug report #946328,
regarding pd-bsaylor 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.)


-- 
946328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-bsaylor
Version: 0.1-5
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

pd-bsaylor fails to cross build from source, because it strips with the
build architecture strip. Beyond breaking cross compilation, stripping
at install time also breaks generation of -dbgsym packages as well as
DEB_BUILD_OPTIONS=nostrip. The attached patch simply disables such
stripping and fixes all of the above. Please consider applying it.

Helmut
diff --minimal -Nru pd-bsaylor-0.1/debian/changelog 
pd-bsaylor-0.1/debian/changelog
--- pd-bsaylor-0.1/debian/changelog 2018-01-29 21:30:14.0 +0100
+++ pd-bsaylor-0.1/debian/changelog 2019-12-07 09:19:46.0 +0100
@@ -1,3 +1,10 @@
+pd-bsaylor (0.1-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Defer stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 07 Dec 2019 09:19:46 +0100
+
 pd-bsaylor (0.1-5) unstable; urgency=medium
 
   * Added (CPP|C|LDFLAGS) to build
diff --minimal -Nru pd-bsaylor-0.1/debian/rules pd-bsaylor-0.1/debian/rules
--- pd-bsaylor-0.1/debian/rules 2018-01-29 21:30:14.0 +0100
+++ pd-bsaylor-0.1/debian/rules 2019-12-07 09:19:45.0 +0100
@@ -12,6 +12,6 @@
$(empty)
 
 override_dh_auto_install:
-   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir)
+   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir) STRIP=true
 # replace license file with link to the Debian license file
rm -f -- $(CURDIR)/debian/*/$(pkglibdir)/*/LICENSE.txt
--- End Message ---
--- Begin Message ---
Source: pd-bsaylor
Source-Version: 0.1-6
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-bsaylor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 21:51:37 +0200
Source: pd-bsaylor
Architecture: source
Version: 0.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 946328
Changes:
 pd-bsaylor (0.1-6) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Fix FTCBFS: Defer stripping to dh_strip.
 Thanks to Helmut Grohne  (Closes: #946328)
   * Removed Hans-Christoph Steiner from Uploaders as he requested
   * Declare that building this package does not require "root" powers
   * Add salsa-ci configuration
   * Drop obsolete file d/source/local-options
   * Bump dh-compat to 12
   * Bump standards-version to 4.5.0
Checksums-Sha1:
 905ef20ced0292360bb887090a7dea96f2284bba 2124 pd-bsaylor_0.1-6.dsc
 11137714449479dbc0eedabe423a0d5ec46215a7 4904 pd-bsaylor_0.1-6.debian.tar.xz
Checksums-Sha256:
 0c70b25116b7365bcb92a047d8488a716a8f6c5987b82cc0923f305fbf908510 2124 
pd-bsaylor_0.1-6.dsc
 1a2643709f1de6f69081c8e365b9862f7a426eab7fef671656211bf1da6749f1 4904 
pd-bsaylor_0.1-6.debian.tar.xz
Files:
 c937b0b9a8030383153b210147b0bce0 2124 sound optional pd-bsaylor_0.1-6.dsc
 b4d73b3ae849d4f738241b5fe97014fc 4904 sound optional 
pd-bsaylor_0.1-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl6UxVAWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+HprD/9tG9IbxRkjv5cYiG/mpG5LFSpY
sWUX2iPabvjcfYktf+X8W+fLTJ/G84zUpiUgRWjgDK3V2WeXA0YgvNedN6ZMs7OT
nN5bd8H5XDg6fnxkXr/NN1MFSyjobbEToC2IAHq+1/vWIVte2EfgP53I2fPEPk5h
1dLIYz2eZu8y9r6bGInDZgswHhpg1dnqYjBdCnWoXkuRRfU0Voh0uCaR0WKFq0H7
/mtGii6xUA/pIehBiMbTTg6yNg0u/J4FHpFq

Bug#956300: marked as done (facter: FTBFS if bundler is installed)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:04:11 +
with message-id 
and subject line Bug#956300: fixed in facter 3.11.0-4.1
has caused the Debian Bug report #956300,
regarding facter: FTBFS if bundler is installed
to be marked as done.

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

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


-- 
956300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: facter
Version: 3.11.0-4
Severity: important
Tags: ftbfs
Justification: fails to build from source if bundler is installed

8<8<8<-
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project /home/terceiro/src/debian/facter/obj-x86_64-linux-gnu
Start 1: libfacter tests
1/2 Test #1: libfacter tests ..   Passed2.43 sec
Start 2: libfacter specs
2/2 Test #2: libfacter specs ..***Failed0.23 sec
bundler: failed to load command: rspec (/usr/bin/rspec)
Bundler::GemNotFound: Could not find gem 'rake (~> 10.1.0)' in any of the gem 
sources listed in your Gemfile.
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/resolver.rb:290:in
 `block in verify_gemfile_dependencies_are_found!'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/resolver.rb:258:in
 `each'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/resolver.rb:258:in
 `verify_gemfile_dependencies_are_found!'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/resolver.rb:49:in
 `start'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/resolver.rb:22:in
 `resolve'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/definition.rb:258:in
 `resolve'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in definition_method'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup'
  /usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler.rb:149:in 
`setup'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in '
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence'
  
/usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `'
8<8<8<-

rspec is being run as `bundle exec rspec`, but the dependencies
specified in the Gemfile are not compatible with what we have in Debian
unstable at the moment.

Also, if bundler in installed but ruby-rspec is not, it will also fail.

On the buildds this does not look like a problem, because bundler is not
installed so the check in CMakeLists.txt never adds this test to the
final list of tests to run.

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

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

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: facter
Source-Version: 3.11.0-4.1
Done: Antonio Terceiro 

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

(This message was generated automatically at their r

Bug#956301: marked as done (facter: missing dependency on ruby)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:04:11 +
with message-id 
and subject line Bug#956301: fixed in facter 3.11.0-4.1
has caused the Debian Bug report #956301,
regarding facter: missing dependency on ruby
to be marked as done.

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

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


-- 
956301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: facter
Version: 3.11.0-4
Severity: serious
Justification: will break on every ruby interpreter transition

facter does not have any dependency on ruby, so it can't specify which
ruby it works with. In this case, in testing `ruby` is ruby 2.5, but the
facter package from ustable only provides the library for ruby 2.7.

So when trying to migrate ruby-defaults to testing removing ruby2.5 and
making ruby2.7 the default, the autopkgtest of facter fail because it
tries to run `ruby` (2.5) but the package built on unstable does not
provide the library for ruby2.5 anymore.

The failures look like this:

autopkgtest [02:13:05]: test ruby: [---
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': 
libfacter was not found. Please make sure it was installed to the expected 
location. (LoadError)
cannot load such file -- libfacter.so
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/facter.rb:30:in `'
from /usr/lib/ruby/vendor_ruby/facter.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from 
/tmp/autopkgtest-lxc.9xj2vp51/downtmp/build.d5Z/src/debian/tests/ruby:3:in 
`'
autopkgtest [02:13:05]: test ruby: ---]
autopkgtest [02:13:05]: test ruby:  - - - - - - - - - - results - - - - - - - - 
- -
ruby FAIL non-zero exit status 1


autopkgtest [02:13:43]: test puppet: [---
libfacter was not found. Please make sure it was installed to the expected 
location.
cannot load such file -- libfacter.so
autopkgtest [02:13:44]: test puppet: ---]
autopkgtest [02:13:44]: test puppet:  - - - - - - - - - - results - - - - - - - 
- - -
puppet   FAIL non-zero exit status 1


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: facter
Source-Version: 3.11.0-4.1
Done: Antonio Terceiro 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 16:45:20 -0300
Source: facter
Architecture: source
Version: 3.11.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Antonio Terceiro 
Closes: 956300 956301
Changes:
 facter (3.11.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Add patch to not fail build when bundler is installed (Closes: #956300)
   * Add a dependency on the minimal Ruby version needed (Closes: #956301)
Checksums-Sha1:
 1eb75a191d3e9078be9165f78d0f6a1557a5bfb7 2551 facter_3.11.0-4.1.dsc
 1808ba1c77be22f65371764f1c6858eb31252cd5 15996 facter_3.11.0-4.1.debian.tar.xz
 92544c4465d1150d251927de74b38caf1a86c724 9952 facter_3.11.0-4.1_amd64.buildinfo
Checksums-Sha256:
 ad9010e62bc0dbfca20e13aff50bfeb7a43bc966ab7a1c2175e8ea1297120015 2551 
facter_3.11.0-4.1.dsc
 fc82966cd7f3e98ed75565a5fa8e5b6060c472ac1c6627dee459773ab69b8206 15996 
facter_3.11.0-4.1.debian.tar.xz
 555f386b398d5622237eb16e42e521236abdcd122a9558b74051ae1a167e0ce2 9952 
facter_3.11.0-4.1_amd64.buildinfo
Files:
 2c7100b969eecc29b1e3dc9af14bd3fd 2551 admin optional facter_3.11.0-4.1.dsc
 2e1d85ff4848a9959c7c5714c0e57fe7 15996 admin optional 
facter_3.11.0-4.1.debian.tar.xz
 4ba6c2120dde9899d01ca51bd6a249cc 9952 admin optional 
facter_3.11.0-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYD

Bug#956043: marked as done (pd-wiimote FTCBFS: strips with the wrong strip)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:05:42 +
with message-id 
and subject line Bug#956043: fixed in pd-wiimote 0.3.2-4
has caused the Debian Bug report #956043,
regarding pd-wiimote 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.)


-- 
956043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-wiimote
Version: 0.3.2-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

pd-wiimote fails to cross build from source, because it strips using the
build architecture strip during make install. Beyond breaking cross
compilation, doing so also breaks DEB_BUILD_OPTIONS=nostrip as well as
generation of -dbgsym packages. It is best practice to let dh_strip
perform all stripping. Please consider applying the attached patch.

Helmut
diff --minimal -Nru pd-wiimote-0.3.2/debian/changelog 
pd-wiimote-0.3.2/debian/changelog
--- pd-wiimote-0.3.2/debian/changelog   2018-02-01 23:43:11.0 +0100
+++ pd-wiimote-0.3.2/debian/changelog   2020-04-06 16:15:42.0 +0200
@@ -1,3 +1,10 @@
+pd-wiimote (0.3.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Don't strip during make install. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 06 Apr 2020 16:15:42 +0200
+
 pd-wiimote (0.3.2-3) unstable; urgency=medium
 
   * Simplified & unified d/rules
diff --minimal -Nru pd-wiimote-0.3.2/debian/rules pd-wiimote-0.3.2/debian/rules
--- pd-wiimote-0.3.2/debian/rules   2018-02-01 23:43:11.0 +0100
+++ pd-wiimote-0.3.2/debian/rules   2020-04-06 16:15:40.0 +0200
@@ -23,7 +23,7 @@
$(empty)
 
 override_dh_auto_install:
-   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir)
+   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir) STRIP=true
 # fix permissions
find $(CURDIR)/debian/*/$(pkglibdir) -name "*.pd_linux" -exec \
chmod 0664 {} +
--- End Message ---
--- Begin Message ---
Source: pd-wiimote
Source-Version: 0.3.2-4
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= 

We believe that the bug you reported is fixed in the latest version of
pd-wiimote, 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.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-wiimote package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 22:30:54 +0200
Source: pd-wiimote
Architecture: source
Version: 0.3.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 956043
Changes:
 pd-wiimote (0.3.2-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Fix FTCBFS: Don't strip during make install.
 Thanks to Helmut Grohne  (Closes: #956043)
   * Add salsa-ci configuration
   * Declare that building this package does not require 'root' powers.
   * Bump dh-compat to 12
   * Bump standards version to 4.5.0
Checksums-Sha1:
 a87965e266feaf58496205cc559bd4e3e5ccad65 2226 pd-wiimote_0.3.2-4.dsc
 0b6e0700db3e9b7a41c10b3e94c586fd1a2cd66b 3324 pd-wiimote_0.3.2-4.debian.tar.xz
Checksums-Sha256:
 75036733f8d026c3cf351bdfdf5625f3325caff41afac0913859825ceb224e22 2226 
pd-wiimote_0.3.2-4.dsc
 ee4e9c85fabdcb9dfe2adac53421c82e5390d33e0ad1871342db289c57a6e8dc 3324 
pd-wiimote_0.3.2-4.debian.tar.xz
Files:
 35072351c7b5890cfe1b9f6616bf0b4e 2226 sound optional pd-wiimote_0.3.2-4.dsc
 d2357c27931926a409fe648191309ebb 3324 sound optional 
pd-wiimote_0.3.2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl6UzUEWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EhwD/9pHcyjRw1hTB/hZSw4qVDmovN4
YmwAg0bDz9jO39rKpQcFR2Iz/dnf7Vp3EDD2IWKGjBgoDrK54+OYpYezR3j3/eGb
Q3PJHhIFu39EIVTRjUKV1W0s60FD3SeqjZhrbPJn3dHCNqWqvkHxjcjnOYjmG08H
uHxzPSqJt69yS4FDM8G2xa/NWPNHoBXAoy7UNKrcvRP7dZmNPSB6oonI9SU1t1yg
WPK4k+XPIEGUH7Z7cDmYFpKnhKRJ87WqNr3pJOFZOmYwWn3iDzxSmLpNK472JLwK
MPv7G6zNq6JrOvy0/pVPpJIxzPAT

Bug#956408: marked as done (minetest-mod-xdecor: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:04:31 +
with message-id 
and subject line Bug#956408: fixed in minetest-mod-xdecor 1.0+dfsg1-2
has caused the Debian Bug report #956408,
regarding minetest-mod-xdecor: 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.)


-- 
956408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minetest-mod-xdecor
Version: 1.0+dfsg1-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
minetest-mod-xdecor could not be built reproducibly.

This is because .ogg streams must include unique serial numbers and,
by default oggenc includes andom serial numbers in the header, which
are seeded by the current time and the pid.

Patch attached that uses the literal value of SOURCE_DATE_EPOCH as
the seed instead.


 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2020-04-10 19:04:55.123562731 +0100
--- b/debian/rules  2020-04-10 19:06:28.432093253 +0100
@@ -4,4 +4,4 @@
dh $@
 
 override_dh_auto_build:
-   oggenc debian/wesnoth_heal.wav -o sounds/xdecor_enchanting.ogg
+   oggenc debian/wesnoth_heal.wav -o sounds/xdecor_enchanting.ogg -s 
$(SOURCE_DATE_EPOCH)
--- End Message ---
--- Begin Message ---
Source: minetest-mod-xdecor
Source-Version: 1.0+dfsg1-2
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
minetest-mod-xdecor, 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.
Julien Puydt  (supplier of updated minetest-mod-xdecor 
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, 13 Apr 2020 21:50:34 +0200
Source: minetest-mod-xdecor
Architecture: source
Version: 1.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Julien Puydt 
Closes: 956408
Changes:
 minetest-mod-xdecor (1.0+dfsg1-2) unstable; urgency=medium
 .
   * Make the build reproducible, thanks to a contribution
 of Chris Lamb (Closes: #956408).
Checksums-Sha1:
 f12cfa9f747875ebdaafec19d3fabdfec3368746 2096 
minetest-mod-xdecor_1.0+dfsg1-2.dsc
 4f21c48d9699fff5b8596c2710136cbc37a26567 63124 
minetest-mod-xdecor_1.0+dfsg1-2.debian.tar.xz
 209e84adfca8bdb3b7d31685f252b2d21c639afa 6277 
minetest-mod-xdecor_1.0+dfsg1-2_source.buildinfo
Checksums-Sha256:
 b079162b442a276647c502c50ac9473a9b1db86f6c63403dc9cb434c1096a45b 2096 
minetest-mod-xdecor_1.0+dfsg1-2.dsc
 708cea43477d89779da52e5770f6997efcadd52a01bc9461b9c175e1b0cb1361 63124 
minetest-mod-xdecor_1.0+dfsg1-2.debian.tar.xz
 0f077767e69c964adda1854348825f4e36f47245ac5a3529d944a5305a7e314f 6277 
minetest-mod-xdecor_1.0+dfsg1-2_source.buildinfo
Files:
 0675ba42fca085892ca54b7ab19b007d 2096 games optional 
minetest-mod-xdecor_1.0+dfsg1-2.dsc
 592b8bcd110db1eb462f3e3c7b63a638 63124 games optional 
minetest-mod-xdecor_1.0+dfsg1-2.debian.tar.xz
 c4062c73fb62e39093046650a9c6d5be 6277 games optional 
minetest-mod-xdecor_1.0+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl6UwrYSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRDbcP/iW/LgQMEIuK/arzWrVWaQujVRFlZDQV
xKxuOAfmRd34CtLaDPn9IiFSLNTqukH5tP4Tks5XffWJJyJ9FpDKa8+0iKQUaWb+
Kevd3pmhWkO9LGDRLAcZ8mg9MWlHNEqSaY08UkbMswJbk8v1dcMep/G8MxFbkBty
HA3OBJQ7Kfa7HveSLo01C5qghK5Lnha1F4AaF62mB2ekvxpG28xoC0RYaBEtWJ68
Nv0zgoNXVvaxADRV4X0TgTyF8iInovIpD6fDu2incsFb1LS5Eix5HdinD8F44hXY
9kg4k+RsYiqwOYVMxqldT9BZrZIx0rkJskqKE/150vb4LY9kF6jJWmWAJGjFpFun
kIHg23228AveXRiy72xFzIzbAutjxGwe3+CAJyn6k99Jts/bG4qRYzYdqdh/1i22
I+XtmoOfD0aVgVaymZb9a+DwXLIdBUjgoJlGmonXI1mFL53xE1d91xwcR0epOPuE
twkiYYt/aWGyIEa8yoFbs2489y3yHwuyv/kRB0NxggBT0Jp7J3bMm31ZgCu3KC1J
i/HbJ4lGm8RZhbIyvkyrhuj3oGegK9b0vbbSzvC6L7SE85xbyVdKQ2pFT9G9jGFA
Cq1dQiImJUBgAJ0nuMNkBfYwqu7+MbViM3nKi5NrgZy0

Processed: RFS: libcyaml/1.0.2-1 [ITP] -- library to read and write YAML documents (shared library)

[Debian Bug Tracking System]

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

> close 956601
Bug #956601 [sponsorship-requests] RFS: libcyaml/1.0.2-1 [ITP] -- library to 
read and write YAML documents (shared library)
Marked Bug as done
> stop
Stopping processing here.

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

Bug#917767: marked as done (gnome-terminal outputs debug messages when started from the command line)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:51:04 +0100
with message-id <20200413205104.ga192...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#917767: gnome-terminal outputs debug messages when 
started from the command line
has caused the Debian Bug report #917767,
regarding gnome-terminal outputs debug messages when started from the command 
line
to be marked as done.

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

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


-- 
917767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-terminal
Version: 3.30.2-2
Severity: minor
Tags: upstream
Forwarded: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42

When one starts gnome-terminal from the command line, it outputs
useless debug messages such as:

# watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
# unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
# watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

Not sure what has changed, but 2 weeks ago, I did not get such
messages.

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

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

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-2
ii  gnome-terminal-data   3.30.2-2
ii  gsettings-desktop-schemas 3.28.1-1
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-4
ii  libdconf1 0.30.1-2
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.2-3
ii  libpango-1.0-01.42.1-1
ii  libuuid1  2.33-0.2
ii  libvte-2.91-0 0.54.2-2
ii  libx11-6  2:1.6.7-1

Versions of packages gnome-terminal recommends:
ii  gvfs   1.38.1-2
ii  nautilus-extension-gnome-terminal  3.30.2-2
ii  yelp   3.30.0-2

gnome-terminal suggests no packages.

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

On Sun, 30 Dec 2018 at 00:29:22 +0100, Vincent Lefevre wrote:
> When one starts gnome-terminal from the command line, it outputs
> useless debug messages such as:
> 
> # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
> # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
> # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
> 
> Not sure what has changed, but 2 weeks ago, I did not get such
> messages.

The issue here is that newer GNOME Terminal versions override the global
GLib log handler, replacing it with one that doesn't filter out g_debug()
like the default does. The change that made you see this is either: that
change in GNOME Terminal, or dconf starting to emit g_debug() messages
(whichever of those changes happened second).

I forgot to mention the bug number in the changelog, but I followed up on
this upstream, got the fix included, and added the patch in 3.36.1.1-2,
so it should be fixed in unstable now.

smcv--- End Message ---

Bug#948175: marked as done (pd-bassemu FTCBFS: strips with the build architecture strip)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 20:04:47 +
with message-id 
and subject line Bug#948175: fixed in pd-bassemu 0.3-6
has caused the Debian Bug report #948175,
regarding pd-bassemu FTCBFS: strips with the build architecture 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.)


-- 
948175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-bassemu
Version: 0.3-5
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

pd-bassemu fails to cross build from source, because it strips with the
build architecture strip during make install. Beyond breaking cross
compilation, doing so breaks DEB_BUILD_OPTIONS=nostrip as well as
generation of -dbgsym packages. It is best to defer all stripping to
dh_strip. Please consider applying the attached patch.

Helmut
diff --minimal -Nru pd-bassemu-0.3/debian/changelog 
pd-bassemu-0.3/debian/changelog
--- pd-bassemu-0.3/debian/changelog 2018-01-29 21:01:42.0 +0100
+++ pd-bassemu-0.3/debian/changelog 2020-01-04 20:36:40.0 +0100
@@ -1,3 +1,10 @@
+pd-bassemu (0.3-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Defer stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 04 Jan 2020 20:36:40 +0100
+
 pd-bassemu (0.3-5) unstable; urgency=medium
 
   * Added C/CPP/LDFLAGS to build
diff --minimal -Nru pd-bassemu-0.3/debian/rules pd-bassemu-0.3/debian/rules
--- pd-bassemu-0.3/debian/rules 2018-01-29 21:01:42.0 +0100
+++ pd-bassemu-0.3/debian/rules 2020-01-04 20:36:37.0 +0100
@@ -12,6 +12,6 @@
$(empty)
 
 override_dh_auto_install:
-   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir)
+   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir) STRIP=true
 # replace license file with link to the Debian license file
rm -f -- $(CURDIR)/debian/*/$(pkglibdir)/*/LICENSE.txt
--- End Message ---
--- Begin Message ---
Source: pd-bassemu
Source-Version: 0.3-6
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-bassemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 21:32:55 +0200
Source: pd-bassemu
Architecture: source
Version: 0.3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 948175
Changes:
 pd-bassemu (0.3-6) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove trailing whitespaces
   * Use debhelper-compat instead of debian/compat
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Fix FTCBFS: Defer stripping to dh_strip.
 Thanks to Helmut Grohne  (Closes: #948175)
   * Removed Hans-Christoph Steiner from Uploaders as he requested
   * Declare that building this package does not require "root" powers
   * Drop obsolete file d/source/local-options
   * Add salsa-ci configuration
   * Bump dh-compat to 12
   * Bump standards version to 4.5.0
Checksums-Sha1:
 e05d4d8e6c041154baf7cd455e11bd4cbe47f101 2110 pd-bassemu_0.3-6.dsc
 6d214e21f7637a8745a955f9bcf2f306227fa59a  pd-bassemu_0.3-6.debian.tar.xz
Checksums-Sha256:
 0d863fab02d86f4505168c75ee1cf156a5242e79ff1e32aa7f2289468f262176 2110 
pd-bassemu_0.3-6.dsc
 43875531c8a546f74a56dc46b21d552a452632979f6a63c4498cf91bb325eeb6  
pd-bassemu_0.3-6.debian.tar.xz
Files:
 0aa2e54d1c5188d821560ba0728d49bf 2110 sound optional pd-bassemu_0.3-6.dsc
 8f5f3d22e23eb598fb83e175a79bdc4a  sound optional 
pd-bassemu_0.3-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl6UwEkWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+FcRD/4ylJ6gHtNLN/dzpNaZa1uDnvLU
R18H6Tf0PTsimzqKD7day9Ez9r/I8qr7h8MwkrRyQtjSVWTU5ajMvFNiJdBXlFGS
cEpsY+5qjSjqwkTB+xoJjnLyhLyCN7lWjFlu7ib4ABSrR0C0md/ZULpPXzisqXcH
tGSmGxNBceL5DQWGlKw1cJTsBpqm9rZN4cY1PgeqNPGpHendQzotvZIUXbZ259w

Bug#948174: marked as done (pd-beatpipe FTCBFS: strips with the wrong strip)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 20:04:52 +
with message-id 
and subject line Bug#948174: fixed in pd-beatpipe 0.1-6
has caused the Debian Bug report #948174,
regarding pd-beatpipe 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.)


-- 
948174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-beatpipe
Version: 0.1-5
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

pd-beatpipe fails to cross build from source, because it strips with the
build architecture strip during make install. Beyond breaking cross
compilation, this also breaks DEB_BUILD_OPTIONS=nostrip as well as
generation of -dbgsym packages. It is best to defer all stripping to
dh_strip. Please consider applying the attached patch.

Helmut
diff --minimal -Nru pd-beatpipe-0.1/debian/changelog 
pd-beatpipe-0.1/debian/changelog
--- pd-beatpipe-0.1/debian/changelog2018-01-29 21:11:57.0 +0100
+++ pd-beatpipe-0.1/debian/changelog2020-01-04 17:34:22.0 +0100
@@ -1,3 +1,10 @@
+pd-beatpipe (0.1-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Defer stripping to dh_strip. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 04 Jan 2020 17:34:22 +0100
+
 pd-beatpipe (0.1-5) unstable; urgency=medium
 
   * Updated Vcs-* stanzas to salsa.d.o
diff --minimal -Nru pd-beatpipe-0.1/debian/rules pd-beatpipe-0.1/debian/rules
--- pd-beatpipe-0.1/debian/rules2018-01-29 21:11:57.0 +0100
+++ pd-beatpipe-0.1/debian/rules2020-01-04 17:34:20.0 +0100
@@ -12,6 +12,6 @@
$(empty)
 
 override_dh_auto_install:
-   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir)
+   dh_auto_install -- prefix=/usr pkglibdir=$(pkglibdir) STRIP=true
 # replace license file with link to the Debian license file
rm -f -- $(CURDIR)/debian/*/$(pkglibdir)/*/LICENSE.txt
--- End Message ---
--- Begin Message ---
Source: pd-beatpipe
Source-Version: 0.1-6
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-beatpipe package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 21:45:48 +0200
Source: pd-beatpipe
Architecture: source
Version: 0.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 948174
Changes:
 pd-beatpipe (0.1-6) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Fix FTCBFS: Defer stripping to dh_strip.
 Thanks to Helmut Grohne  (Closes: #948174)
   * Removed Hans-Christoph Steiner from Uploaders as he requested
   * Drop obsolete file d/source/local-options
   * Add salsa-ci configuration
   * Update d/copyright
   * Declare that building this package does not require "root" powers
   * Bump dh-compat to 12
   * Bump standards-version to 4.5.0
Checksums-Sha1:
 78a90fae74a5227e8e728603c7832e92f78ce31c 2122 pd-beatpipe_0.1-6.dsc
 8cd62646414367631ce92108a4e6597b99ad2f11 6564 pd-beatpipe_0.1-6.debian.tar.xz
Checksums-Sha256:
 2ba3b6dee89a3b4b33f3a69370c8a4abd0fe52b5f4d296b66f74977935724b18 2122 
pd-beatpipe_0.1-6.dsc
 02a80327cfdabd7484def418b9777276e904cbc73889d9fd0767451183bc9c69 6564 
pd-beatpipe_0.1-6.debian.tar.xz
Files:
 c7145bfadd30b0050d9e144c88287b40 2122 sound optional pd-beatpipe_0.1-6.dsc
 fd066747db9c02e3544ca6b0794df49d 6564 sound optional 
pd-beatpipe_0.1-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl6UwdEWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+HWqD/0Q7VjxXtDFWVLpMwwHvOH7RTNf
6O4o8Djzj/D8c4Ze/vZfHgB6SzMJ6yXWhcIj4ialqkdZ1xx8bfUA3LFkEyOLkUaA
uSe7+65wbqBCDbQa3sjYoi20YrPyl0NKuYyEkt5bbGHevm1LGSECZE36geooiyq9
wZrns8LYdwql4NGt5eG6vCSuwVNlB81C01N2UW8MAMpvpNfcFWqV

Bug#939097: marked as done (conway-polynomials needs to be pickled with Python 2 as long as sagemath uses Python 2)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:56:37 +0200
with message-id <929e0e5802e37e97921d5c5d80d61ddb5b77e866.ca...@gmail.com>
and subject line 0.5-7 fixing this is in unstable and testing
has caused the Debian Bug report #939097,
regarding conway-polynomials needs to be pickled with Python 2 as long as 
sagemath uses Python 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.)


-- 
939097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath-database-conway-polynomials
Version: 0.5-6
Severity: important

Hi Julien,

I'm currently updating sagemath to version 8.8 and since version 0.5-5 
sagemath-database-conway-polynomials is pickled with Python 3 and is not 
compatible with Python 2 sagemath. Could you please revert to pickling with 
Python 2 until we update sagemath to Python 3? I want to start experimenting 
with Python 3 for sagemath soon but first I want to upload another working 
sagemath with Python 2.

Best,
Tobias
--- End Message ---
--- Begin Message ---
Hi,

since 0.5-7 fixing this is in unstable and testing, I think it's time
to close that bug.

Cheers,

JP--- End Message ---

Bug#953139: marked as done (python3-jupyter-core: Sid python3-jupyter-core 4.6.3-2 Needs python3-distutils)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 21:46:59 +0200
with message-id 
and subject line Fixed in an upload which went into testing
has caused the Debian Bug report #953139,
regarding python3-jupyter-core: Sid python3-jupyter-core 4.6.3-2 Needs 
python3-distutils
to be marked as done.

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

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


-- 
953139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-jupyter-core
Version: 4.6.3-2
Severity: important

After recent updates to the jupyter packages and for the Python
3.8 tranision in Sid, I decided to give qtconsole a spin just to
see how it's working. It's not able to load:

$ jupyter qtconsole
Traceback (most recent call last):
  File "/usr/bin/jupyter", line 11, in 
load_entry_point('jupyter-core==4.6.3', 'console_scripts', 'jupyter')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in 
load_entry_point

...

  File "/usr/lib/python3/dist-packages/jupyter_core/command.py", line 25, in 

from . import paths
  File "/usr/lib/python3/dist-packages/jupyter_core/paths.py", line 21, in 

from distutils.util import strtobool
ModuleNotFoundError: No module named 'distutils.util'

I was able to resolve this by installing python3-distutils, which
installs both Python 3.7 and 3.8 versions of distutils.util.

The latest /usr/lib/python3/dist-packages/jupyter_core/paths.py
module from Debian package python3-jupyter-core does import from
distutils.util. The python3-jupyter-core 4.4.0-2 installed on my
Buster host does not.

Should python3-jupyter-core now depend on package python3-distutils?

CAVEATS: The Python 3.8 transition is still a work-in-progress
on my Sid host, as I expect it is on other users'. Upgrades of
python3 libpython3-stdlib python3-minimal from 3.7.5-3 -> 3.8.2-1
are blocked because python3-talloc requires python3 (< 3.8), and
python3-talloc is (ultimately) required by gnome-control-center
via GVFS/Samba dependencies.

Also, I DO NOT have python3-all installed, which would bring in
python3-distutils. Should I have python3 installed?

My sincere apologies if I've jumped the gun and this issue would
have worked itself out as the 3.8 transition progresses. But this
could affect other qtconsole users, so I thought I should report it.

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

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

Versions of packages python3-jupyter-core depends on:
hi  python33.7.5-3
ii  python3-traitlets  4.3.3-2

python3-jupyter-core recommends no packages.

Versions of packages python3-jupyter-core suggests:
pn  python3-pip  

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

since the bug was fixed by 4.6.3-3, which is now in testing, I think we
can close this bug.

Cheers,

JP--- End Message ---

Bug#956505: marked as done (Relax dependency on responders gem)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:19:41 +
with message-id 
and subject line Bug#956505: fixed in open-build-service 2.9.4-3
has caused the Debian Bug report #956505,
regarding Relax dependency on responders gem
to be marked as done.

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

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


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

Package: obs-api
Version: 2.9.4-2
Severity: important
Control: tags -1 patch

Only breaking changes in responders 3.0 is dropping support for rails < 
4.2 and ruby < 2.4.


I have pushed a commit to master relaxing responders in 
src/api/Gemfile. Please upload obs-api with this fix so I can upload 
ruby-responders 3.0 to unstable.
--- End Message ---
--- Begin Message ---
Source: open-build-service
Source-Version: 2.9.4-3
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
open-build-service, 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.
Lucas Kanashiro  (supplier of updated open-build-service 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 15:30:23 -0300
Source: open-build-service
Architecture: source
Version: 2.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Kanashiro 
Closes: 926198 956504 956505
Changes:
 open-build-service (2.9.4-3) unstable; urgency=medium
 .
   [ Lucas Kanashiro ]
   * Add patch to publish Debian upstream tarball signatures to the
 repositories
   * Add patch to publish Ubuntu ddeb files to the repositories
   * Move DoD projects example configs to obs-api package, instead of obs-server
   * Add some autopkgtests test cases
   * Fix obsapidelayed.service.
 Split the obsapidelayed systemd unit file into others unit files
   * Add patch to fix the database migration.
 Limit the size of a VARCHAR to not extrapolate the number of bytes 
allocated.
 .
   [ Andrew Lee (李健秋) ]
   * Move permission adjustment from rake-tasks.sh into obs-api.postinst
 script and fix permissions for upgrade. (Closes: #926198)
 .
   [ Lucas Kanashiro ]
   * debian/NEWS: add new entry to notify users to check the default Passenger
 user when upgrading.
   * debian/rake-tasks.sh: update migration task to restart all OBS related
 services.
   * debian/README.Debian: add instructions on how to upgrade an exitent 
instance
   * debian/rake-tasks.sh: stop all running processes from the old installation
   * debian/obs-api.postrm: stop obsapi systemd services
   * debian/osb-api.prerm: stop the new obsapi systemd unit files
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Pirate Praveen ]
   * Switch dependency: ruby-parser -> ruby-ruby-parser (Closes: #956504)
   * Relax dependecy on responders in src/api/Gemfile (Closes: #956505)
Checksums-Sha1:
 3be016f133b61d44133972a776a7808a4c29 4008 open-build-service_2.9.4-3.dsc
 5e968f70f7700e7a1eab514dbfed3d777fd5a651 102964 
open-build-service_2.9.4-3.debian.tar.xz
Checksums-Sha256:
 7f1d5eb896bed8a6dd1539cbeb23b88347e79cbb2850cc01b37470365d100585 4008 
open-build-service_2.9.4-3.dsc
 f52b64e56f4d11535626b88fa3470f5fe8777b91b93cc74c0c9d34acbdf03c5c 102964 
open-build-service_2.9.4-3.debian.tar.xz
Files:
 673b03cbe092b6d1616ba8048f29 4008 devel optional 
open-build-service_2.9.4-3.dsc
 7bf1c1cbc55bf4762383a3ffa0ae2a34 102964 devel optional 
open-build-service_2.9.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl6UtcIVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8oU8QAJan1XMujc00RmKtw+/HN9KHh0qo
bzIEag80FAfnaVrqP256qCVaFZ/6AF7MFmq/pjDF3BCwwMPHGW8BtJeHQMbPHqAX
4pTFtFjB9u5Q0tRgpnLRId7WbeTs26u9R5y4tZfJb/J4CE51Q/57eVG0Me1UpppA
y9WxIcf5B/ACJq/NSBtN4ZolPPY+wnl7vrP9HfglXkM2C33dxclsIsz1ZiLTfDL8
fy9bnqRZjuafiT6kbpHJPYmN2J5h4mGseIJlYAsmPmLUChMDNaOUpuQF38PbMLk8
7TcUakJq2iHg0fuilY9/gyenlzUW9DPz6ocCMv7ZKwVPVsMTcjAjVsmR2ykJFt49
8Edb4N8P6b/w8k/DiFdacCJKIIDWjLJ95qKZ5DzJj1sISlk35FGjVhkStPOxSfkt
SJPylfdEokyv15wPEXoPETsJmGlyqcZddqPmFB0x+EwLtQ/qBbJkx

Bug#926198: marked as done (obs-api: Permissions and database setup should be done in maintainers scripts, not in a post-installation one)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:19:41 +
with message-id 
and subject line Bug#926198: fixed in open-build-service 2.9.4-3
has caused the Debian Bug report #926198,
regarding obs-api: Permissions and database setup should be done in maintainers 
scripts, not in a post-installation one
to be marked as done.

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

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


-- 
926198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obs-api
Severity: minor

Dear Maintainer,

The debian/README.Debian file instructs to run a post-installation script to
finish the obs-api setup:

$ /usr/share/obs/api/script/rake-tasks.sh setup

This script changes files permissions and finishes the database setup. These
things should be done mostly in debian/obs-api.postinst script.

Having that in mind, I expect to install the obs-api package, answer debconf,
and then have a funcional OBS API and web interface running.


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

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

Versions of packages obs-api depends on:
ii  adduser  3.118
pn  apache2  
pn  dbconfig-common  
ii  debconf [debconf-2.0]1.5.71
pn  default-mysql-client | virtual-mysql-client  
ii  gsfonts  1:8.11+urwcyr1.0.7~pre44-4.4
pn  libapache2-mod-passenger 
pn  libapache2-mod-xforward  
ii  libgd-perl [libgd-gd2-perl]  2.71-2
ii  libjs-bootstrap  3.4.1+dfsg-1
pn  libjs-html5shiv  
ii  lsb-base 10.2019031300
ii  memcached1.5.6-1
ii  ruby 1:2.5.1
pn  ruby-activemodel-serializers-xml 
pn  ruby-acts-as-list
pn  ruby-acts-as-tree
ii  ruby-addressable 2.5.2-1
pn  ruby-bcrypt  
ii  ruby-bunny   2.9.2-1
pn  ruby-capybara
pn  ruby-chunky-png  
pn  ruby-cliver  
pn  ruby-clockwork   
pn  ruby-cocoon  
pn  ruby-codemirror-rails
ii  ruby-coderay 1.1.2-2
pn  ruby-coffee-rails
ii  ruby-colorize0.8.1-1
pn  ruby-crack   
pn  ruby-crass   
pn  ruby-cssmin  
pn  ruby-daemons 
pn  ruby-dalli   
pn  ruby-data-migrate
pn  ruby-delayed-job 
pn  ruby-delayed-job-active-record   
pn  ruby-docile  
ii  ruby-erubis  2.7.0-3
pn  ruby-escape-utils
ii  ruby-execjs  2.6.0-1
pn  ruby-feature 
pn  ruby-flot-rails  
pn  ruby-font-awesome-rails  
pn  ruby-gssapi  
ii  ruby-haml5.0.4-3
pn  ruby-hike
ii  ruby-i18n1.5.3-1
pn  ruby-innertube   
pn  ruby-joiner  
pn  ruby-jquery-datatables-rails 
pn  ruby-jquery-rails
pn  ruby-jquery-ui-rails 
ii  ruby-json2.1.0+dfsg-2+b1
pn  ruby-kaminari
pn  ruby-kgio
pn  ruby-ldap
ii  ruby-metaclass   0.0.4-1
ii  ruby-method-source   0.9

Bug#956504: marked as done (Switch dependency from ruby-parser to ruby-ruby-parser)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:19:41 +
with message-id 
and subject line Bug#956504: fixed in open-build-service 2.9.4-3
has caused the Debian Bug report #956504,
regarding Switch dependency from ruby-parser to ruby-ruby-parser
to be marked as done.

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

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


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

Package: obs-api
Version: 2.9.4-2
Severity: important
Control: tags -1 patch

ruby_parser gem is now renamed to ruby-ruby-parser package to allow 
packaging parser gem as ruby-parser.


I have pushed a commit to master, a new upload of abs-api will allow us 
to upload a new ruby-parser package.
--- End Message ---
--- Begin Message ---
Source: open-build-service
Source-Version: 2.9.4-3
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
open-build-service, 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.
Lucas Kanashiro  (supplier of updated open-build-service 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 15:30:23 -0300
Source: open-build-service
Architecture: source
Version: 2.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Kanashiro 
Closes: 926198 956504 956505
Changes:
 open-build-service (2.9.4-3) unstable; urgency=medium
 .
   [ Lucas Kanashiro ]
   * Add patch to publish Debian upstream tarball signatures to the
 repositories
   * Add patch to publish Ubuntu ddeb files to the repositories
   * Move DoD projects example configs to obs-api package, instead of obs-server
   * Add some autopkgtests test cases
   * Fix obsapidelayed.service.
 Split the obsapidelayed systemd unit file into others unit files
   * Add patch to fix the database migration.
 Limit the size of a VARCHAR to not extrapolate the number of bytes 
allocated.
 .
   [ Andrew Lee (李健秋) ]
   * Move permission adjustment from rake-tasks.sh into obs-api.postinst
 script and fix permissions for upgrade. (Closes: #926198)
 .
   [ Lucas Kanashiro ]
   * debian/NEWS: add new entry to notify users to check the default Passenger
 user when upgrading.
   * debian/rake-tasks.sh: update migration task to restart all OBS related
 services.
   * debian/README.Debian: add instructions on how to upgrade an exitent 
instance
   * debian/rake-tasks.sh: stop all running processes from the old installation
   * debian/obs-api.postrm: stop obsapi systemd services
   * debian/osb-api.prerm: stop the new obsapi systemd unit files
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Pirate Praveen ]
   * Switch dependency: ruby-parser -> ruby-ruby-parser (Closes: #956504)
   * Relax dependecy on responders in src/api/Gemfile (Closes: #956505)
Checksums-Sha1:
 3be016f133b61d44133972a776a7808a4c29 4008 open-build-service_2.9.4-3.dsc
 5e968f70f7700e7a1eab514dbfed3d777fd5a651 102964 
open-build-service_2.9.4-3.debian.tar.xz
Checksums-Sha256:
 7f1d5eb896bed8a6dd1539cbeb23b88347e79cbb2850cc01b37470365d100585 4008 
open-build-service_2.9.4-3.dsc
 f52b64e56f4d11535626b88fa3470f5fe8777b91b93cc74c0c9d34acbdf03c5c 102964 
open-build-service_2.9.4-3.debian.tar.xz
Files:
 673b03cbe092b6d1616ba8048f29 4008 devel optional 
open-build-service_2.9.4-3.dsc
 7bf1c1cbc55bf4762383a3ffa0ae2a34 102964 devel optional 
open-build-service_2.9.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl6UtcIVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8oU8QAJan1XMujc00RmKtw+/HN9KHh0qo
bzIEag80FAfnaVrqP256qCVaFZ/6AF7MFmq/pjDF3BCwwMPHGW8BtJeHQMbPHqAX
4pTFtFjB9u5Q0tRgpnLRId7WbeTs26u9R5y4tZfJb/J4CE51Q/57eVG0Me1UpppA
y9WxIcf5B/ACJq/NSBtN4ZolPPY+wnl7vrP9HfglXkM2C33dxclsIsz1ZiLTfDL8
fy9bnqRZjuafiT6kbpHJPYmN2J5h4mGseIJlYAsmPmLUChMDNaOUpuQF38PbMLk8
7TcUakJq2iHg0fuilY9/gyenlzUW9DPz6ocCMv7ZKwVPVsMTcjAjVsmR2ykJFt49
8Edb4N8P6b/w8k/DiFdacCJKIIDWjLJ95qKZ5DzJj1sISlk35FGjVhkStPOxSfkt
SJPylfdEokyv15wPEXoPETsJmGlyqcZddqPmFB0x+EwLtQ/qBbJkx1CHSO1uKMnP
NsZI5

Processed: src:sleef: fails to migrate to testing for too long: FTBFS on multiple archs

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.4.1-2
Bug #956629 [src:sleef] src:sleef: fails to migrate to testing for too long: 
FTBFS on multiple archs
Marked as fixed in versions sleef/3.4.1-2.
Bug #956629 [src:sleef] src:sleef: fails to migrate to testing for too long: 
FTBFS on multiple archs
Marked Bug as done

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

Bug#956578: marked as done (libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 18:48:46 +
with message-id 
and subject line Bug#956578: fixed in casacore 3.2.1-5
has caused the Debian Bug report #956578,
regarding libcasa-python3-4: package became uninstallable with update of 
libboost-python1.67.0
to be marked as done.

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

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


-- 
956578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcasa-python3-4
Version: 3.2.1-4+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The update of libboost-python1.67.0 to 1.67.0-17+b1 on sid apparently broke
the dependencies of libcasa-python3-4, thus making it uninstallable.  I am
almost sure this is a mere packaging problem, but I am not sure whether it
should be fixed in casa or in boost packages.  At the moment I cannot check
in detail, since I pinned the version of boost on my laptop to avoid the
removal of libcasa-python3-4 and all packages that depend on it.  
If suitable, please feel free to relay this report to the maintainer of the
boost packages.

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 libcasa-python3-4 depends on:
ii  libboost-python1.67.0 [libboost-python1.67.0-py37]  1.67.0-17
ii  libc6   2.30-4
ii  libcasa-casa4   3.2.1-4+b2
ii  libgcc-s1   10-20200411-1
ii  libpython3.83.8.2-1+b1
ii  libstdc++6  10-20200411-1

libcasa-python3-4 recommends no packages.

libcasa-python3-4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: casacore
Source-Version: 3.2.1-5
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
casacore, 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.
Ole Streicher  (supplier of updated casacore 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, 13 Apr 2020 18:05:08 +0200
Source: casacore
Architecture: source
Version: 3.2.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 956578
Changes:
 casacore (3.2.1-5) unstable; urgency=medium
 .
   * Fix tObjectID failure on arm
   * Explicitly specify default Python environment (Closes: #956578)
   * Push Standards-Version to 4.5.0. No changes required
   * cme fix dpkg
Checksums-Sha1:
 37f04b617a609aff7f13b81c124f5d7078562027 3252 casacore_3.2.1-5.dsc
 6816fc282bb8d69c847c8a41fe9aaa2f7f4dc079 22820 casacore_3.2.1-5.debian.tar.xz
Checksums-Sha256:
 21884db56fdb14a1cc3e0abda50020ed3cc0a89db5188f4b0b03b26ac506a2a7 3252 
casacore_3.2.1-5.dsc
 a2cae8eb1b4ff6d5136e8671e06194e0b6b3a997e39a994c2e1198796c100b8e 22820 
casacore_3.2.1-5.debian.tar.xz
Files:
 d247491b45ae95f2ae8b22bdc705e132 3252 science optional casacore_3.2.1-5.dsc
 23c1137a2028f119b06874b94f29d01c 22820 science optional 
casacore_3.2.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl6UsO8ACgkQcRWv0HcQ
3PdTXhAA08mQSIsmMD6Em1f+Kb0hpVGZIKICbOvkBB6zi15JX0U6BYWQZmRCzFFD
MrwbqvqZAfHExOzp87fS/GYym0WyiLYouvxLZGP97xnKV2HSXclvoyOBgWnpgcOD
hkxzOd0D3/BOUPlxY+a3d+/3HS4DhHxCOmibBcB2/KCcetgXFtRG1VGlItRX0iZ6
Sot0TG2yrooxnUCOXul/TtZ4qD+VVPVLyjUIlFgpCN3DJenyBElqM5lI2sLmJGuU
dgODbpfi5OnDja9rpDJMfskp7zZgBH1Nppx+wtxBHA9ZTcIHdqwWkQbGKaKA

Bug#758566: marked as done (FTBFS with clang instead of gcc)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 18:49:25 +
with message-id 
and subject line Bug#758566: fixed in paxtest 1:0.9.15-1
has caused the Debian Bug report #758566,
regarding FTBFS with clang instead of gcc
to be marked as done.

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

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


-- 
758566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: paxtest
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang 
(instead of gcc).

We detected this kinf of error:
http://clang.debian.net/status.php?version=3.5.0rc1&key=NOT_ALLOWED_HERE

Full build log is available here:
http://clang.debian.net/logs/2014-06-16/paxtest_0.9.11-2_unstable_clang.log

Thanks,
Alexander

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- ./body.c	2010-10-22 06:01:36.0 +0400
+++ ../paxtest-0.9.11-my/./body.c	2014-08-19 00:54:19.480193990 +0400
@@ -26,6 +26,10 @@
 	return NULL;
 }
 
+
+/* Dummy nested function */
+static void dummy(void) {}
+
 int main( int argc, char *argv[] )
 {
 	int status;
@@ -36,9 +40,6 @@
 	 */
 	int paxtest_mode = 1;
 
-	/* Dummy nested function */
-	void dummy(void) {}
-
 	mode = getenv( "PAXTEST_MODE" );
 	if( mode == NULL ) {
 		paxtest_mode = 1;
--- End Message ---
--- Begin Message ---
Source: paxtest
Source-Version: 1:0.9.15-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
paxtest, 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 758...@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 paxtest 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 19:39:45 +0200
Source: paxtest
Architecture: source
Version: 1:0.9.15-1
Distribution: unstable
Urgency: low
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 758566
Changes:
 paxtest (1:0.9.15-1) unstable; urgency=low
 .
   * New upstream release
 - The new release avoids using a dummy function if compiling with
   clang instead of gcc (Closes: #758566)
   * Bumped debian/compat to 12 and update debian/control accordingly
   * debian/control:
 - Use https:// for grsecurity.net homepage
 - Add "armel arm64 armhf" to the list of supported architectures
 - Updated standards version to 4.5.0
   * Remove debian/patches/02_change_log_file_location.diff and
 debian/patches/03_paxtest_add_info.diff as they have been
 applied upstream
   * Create a new patch (debian/patches/02_remove_cc_tests) to remove
 from the Makefiles the use of 'gcc' as a test when actually it
 is not provided at all.
   * debian/copyright: Add Brad Spengler as contributor as he is the developer
 behind the 0.9.15 release
Checksums-Sha1:
 cc465fbaf84eab66e3eab40d9b94e274bf7be042 2096 paxtest_0.9.15-1.dsc
 5130f5a45a0c0c32a8bf0037b527ecf93ee247a8 37929 paxtest_0.9.15.orig.tar.gz
 5fa7076eb1a70811e2ae9fb9f751cbcfbe4531b8 801 paxtest_0.9.15.orig.tar.gz.asc
 7d6236cf2da6db83dc8fca27e875313d30db16d8 10036 paxtest_0.9.15-1.debian.tar.xz
 86f8c4119eb7c21a25d0a83558ad243a3bd90d27 6341 paxtest_0.9.15-1_source.buildinfo
Checksums-Sha256:
 2116a76bdff67ebe8040560459ba8fcb21c88a775164c175f993fd16be4deaf4 2096 
paxtest_0.9.15-1.dsc
 d553848431fd8c2ab6c8361b62e5cedfed1cc1d60088241f4a33d2af15dd667f 37929 
paxtest_0.9.15.orig.tar.gz
 2c7dabd2db46224bb68bbe690896c98e5eeb5353fe1038a441a3d0539c8ebab3 801 
paxtest_0.9.15.orig.tar.gz.asc
 10017056fa58fb54121bcf80ebe72e6ceb82c2bd14bff7e28ac06c091a933d3c 10036 
paxtest_0.9.15-1.debian.tar.xz
 06a5efc52c0a9afdaa2fe6be5d4f72c58826ae5c3ab31c0cef8ceb088c671a9f 6341 
paxtest_0.9.15-1_source.buildinfo
F

Bug#946572: marked as done (abcm2ps FTCBFS: builds for the build architecture)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 18:03:32 +
with message-id 
and subject line Bug#946572: fixed in abcm2ps 8.14.7-0.1
has caused the Debian Bug report #946572,
regarding abcm2ps FTCBFS: builds 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.)


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

abcm2ps fails to cross build from source, because it uses build
architecture build tools. The hand-written configure script ignores the
--host flag passed by dh_auto_configure. Instead, one is supposed to
pass --CC=... For pkg-config, it doesn't even provide a method for
substitution. The attached patch makes abcm2ps cross buildable. Please
consider applying it.

Helmut
diff --minimal -Nru abcm2ps-8.14.5/debian/changelog 
abcm2ps-8.14.5/debian/changelog
--- abcm2ps-8.14.5/debian/changelog 2019-09-03 12:07:16.0 +0200
+++ abcm2ps-8.14.5/debian/changelog 2019-12-11 06:09:58.0 +0100
@@ -1,3 +1,12 @@
+abcm2ps (8.14.5-0.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass cross tools CC and PKG_CONFIG to ./configure.
++ cross.patch: Make pkg-config substitutable.
+
+ -- Helmut Grohne   Wed, 11 Dec 2019 06:09:58 +0100
+
 abcm2ps (8.14.5-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru abcm2ps-8.14.5/debian/patches/cross.patch 
abcm2ps-8.14.5/debian/patches/cross.patch
--- abcm2ps-8.14.5/debian/patches/cross.patch   1970-01-01 01:00:00.0 
+0100
+++ abcm2ps-8.14.5/debian/patches/cross.patch   2019-12-11 06:09:57.0 
+0100
@@ -0,0 +1,27 @@
+--- abcm2ps-8.14.5.orig/configure
 abcm2ps-8.14.5/configure
+@@ -5,6 +5,7 @@
+ VDATE=2019-07-17
+ 
+ CC=gcc
++PKG_CONFIG=pkg-config
+ CFLAGS="-g -O2 -Wall -pipe"
+ 
+ srcdir=.
+@@ -57,11 +58,11 @@
+   DEFAULT_FDIR="$prefix/share/abcm2ps"
+ fi
+ 
+-if which pkg-config > /dev/null ; then
+-  if pkg-config --exists freetype2 ; then
+-  if pkg-config --exists pangocairo ; then
+-  CPPFLAGS="$CPPFLAGS -DHAVE_PANGO=1 `pkg-config pango 
cairo freetype2 --cflags`"
+-  LDLIBS="$LDLIBS `pkg-config pangocairo pangoft2 
freetype2 --libs`"
++if which $PKG_CONFIG > /dev/null ; then
++  if $PKG_CONFIG --exists freetype2 ; then
++  if $PKG_CONFIG --exists pangocairo ; then
++  CPPFLAGS="$CPPFLAGS -DHAVE_PANGO=1 `$PKG_CONFIG pango 
cairo freetype2 --cflags`"
++  LDLIBS="$LDLIBS `$PKG_CONFIG pangocairo pangoft2 
freetype2 --libs`"
+   else
+   echo "pangocairo not found - no pango support"
+   fi
diff --minimal -Nru abcm2ps-8.14.5/debian/patches/series 
abcm2ps-8.14.5/debian/patches/series
--- abcm2ps-8.14.5/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ abcm2ps-8.14.5/debian/patches/series2019-12-11 06:09:24.0 
+0100
@@ -0,0 +1 @@
+cross.patch
diff --minimal -Nru abcm2ps-8.14.5/debian/rules abcm2ps-8.14.5/debian/rules
--- abcm2ps-8.14.5/debian/rules 2019-09-03 12:01:08.0 +0200
+++ abcm2ps-8.14.5/debian/rules 2019-12-11 06:09:58.0 +0100
@@ -2,6 +2,7 @@
 
 DEB_BUILD_MAINT_OPTIONS := hardening=+all
 DEB_CFLAGS_MAINT_APPEND := -Wall
+include /usr/share/dpkg/buildtools.mk
 include /usr/share/dpkg/buildflags.mk
 
 %:
@@ -10,4 +11,4 @@
 .PHONY: override_dh_auto_configure
 override_dh_auto_configure:
dh_auto_configure -- \
- $(foreach v,CFLAGS CPPFLAGS LDFLAGS,'--$(v)=$($(v))')
+ $(foreach v,CC PKG_CONFIG CFLAGS CPPFLAGS LDFLAGS,'--$(v)=$($(v))')
--- End Message ---
--- Begin Message ---
Source: abcm2ps
Source-Version: 8.14.7-0.1
Done: Nicolas Boulenguez 

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated abcm2ps 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-maste

Bug#763943: marked as done (libphonenumber: FTBFS on arm64)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:36:23 +0200
with message-id <0a6168c7ae25627245fb035a41b426894a3fdf74.ca...@debian.org>
and subject line Re: libphonenumber: FTBFS on arm64
has caused the Debian Bug report #763943,
regarding libphonenumber: FTBFS on arm64
to be marked as done.

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

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


-- 
763943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libphonenumber
Version: 6.3~svn698-3
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64


This package failed to build on arm64. Build log:
http://buildd.debian-ports.org/status/fetch.php?pkg=libphonenumber&arch=arm64&ver=6.3~svn698-3&stamp=1410187296

The issue is actually a test failure:
Results :

Failed tests:   
testShortNumbersValidAndCorrectCost(com.google.i18n.phonenumbers.ExampleNumbersTest):
 expected:<0> but was:<1>

Tests run: 242, Failures: 1, Errors: 0, Skipped: 0

This is repeatable, but has not yet been investigated.
--- End Message ---
--- Begin Message ---
Control: fixed -1 6.3~svn698-4 

arm64 seems to be fine since above version…--- End Message ---

Bug#956585: marked as done (openjfx: FTBFS on all making openjfx uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 17:35:55 +
with message-id 
and subject line Bug#956585: fixed in openjfx 11.0.7+0-2
has caused the Debian Bug report #956585,
regarding openjfx: FTBFS on all making openjfx 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.)


-- 
956585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Version: 11.0.7+0-1
Severity: serious
Tags: ftbfs
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:josm

Dear Maintainer,

The recent update to 11.0.7+0-1 fails to build and several architectures,
most importantly on all making the openjfx package uninstallable, and in
turn preventing the josm build in unstable:

 The following packages have unmet dependencies:
  openjfx : Depends: libopenjfx-java which is a virtual package and is not 
provided by any available package

The openjfx build log shows:

 FAIL: Gradle version too old: 4.4.1; must be at least 4.8

https://buildd.debian.org/status/fetch.php?pkg=openjfx&arch=all&ver=11.0.7%2B0-1&stamp=1586539559&raw=0

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: openjfx
Source-Version: 11.0.7+0-2
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
openjfx, 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.
Emmanuel Bourg  (supplier of updated openjfx 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, 13 Apr 2020 19:10:07 +0200
Source: openjfx
Architecture: source
Version: 11.0.7+0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 956585
Changes:
 openjfx (11.0.7+0-2) unstable; urgency=medium
 .
   * Disable the Gradle version check when building only the arch all package
 (Closes: #956585)
   * Enable the WebKit JIT on arm64
Checksums-Sha1:
 422fdc0998b9130a8e2242ef8d20a99b1ce02505 2759 openjfx_11.0.7+0-2.dsc
 36703c1e22750ed48574918f52e8b1d735ee0993 16380 openjfx_11.0.7+0-2.debian.tar.xz
 37948b10b130fc3c5b2b7377e1e4cec99c65f3bc 23371 
openjfx_11.0.7+0-2_source.buildinfo
Checksums-Sha256:
 f4ee137b249a0a0a0313b43143d091e04ea2918c02daa1d1d3dc884336c09a98 2759 
openjfx_11.0.7+0-2.dsc
 bff7790ab83cace6512acdaad7dfe1e872e173b56ad70f6bed19a3e7fa3ac0e3 16380 
openjfx_11.0.7+0-2.debian.tar.xz
 4b58644091c14e67cf891b6989c0ebd7b3c808de65910e193614a4ab19c7a9d9 23371 
openjfx_11.0.7+0-2_source.buildinfo
Files:
 8b4b7711f343abb42c3475afc048f88a 2759 java optional openjfx_11.0.7+0-2.dsc
 0798c4be49d775eaf66353754c1ca5a5 16380 java optional 
openjfx_11.0.7+0-2.debian.tar.xz
 83575a9ffda64f27bbd9d3ababeaa504 23371 java optional 
openjfx_11.0.7+0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl6UnT4SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsdxEP/0WXzKLXx14mpZ2Fa5x+EjTm0WL5ljba
AXxY1ri0YwXZdYMxAqvpgqJPNqSOMFWHePv50aFqRsFO9YeIoOSf7nvWWac+1gze
FEp8kc0oGe+BRCpTBeR7luIqUP/zTkL0TZnR1xLJh51RoIfdm/8HxMi5LRqNZFQd
JfXMt3x4LSCritHpxj9PP/V0OU2u8YGoI5RKw/JDzWZ1dU3s8Ui/ERrdaP+EKAKN
Y5uGpNFCBJADajJyBWVoiYMG9BeY5ZH8cL/LspBLM+sXcjL+PoEMhRAb/+ZIrACP
+Xx4pAJj89HGT4Eiey4D+ERuMaSScK1X2PLuM1NRAJFapQE1P/3HDtKdGCWnUUHZ
c/CaYYQQ/mUnl9hIxM+WzQSPD0nORGPMe6j3+CfifLOJEOyUpA8KaJ7UK7O9OM+0
/aW7QUBHtHItIDKG++KAnjRQweACBYljH8v+wR9S8bZzpo+Mrrc+MuKevz8AjyEg
yB6OstaTkkisXl+yZSKnD99FEMubGJco2PgniwcUcCTHnRxLFXhgV9Nebo8Bmfi4
WBq3P7VqdvTQbqqTgSNMjj3BjQvy1pDOFcWuHebR2dqJfgOfUzj+Icy/SChN8Vet
/KsczDrWzUVSib0KqoqZh0lG4C7nZcE5pIqIkE2Cau6JwWEHL5VBTLDiPLBWdEIK
fkg/XYUSB6+E
=Hmd8
-END PGP SIGNATURE End Message ---

Processed: closing 915201

[Debian Bug Tracking System]

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

> close 915201 1.50+dfsg-1
Bug #915201 [espeak-ng] espeak-ng: Mbrola voices not working properly
There is no source info for the package 'espeak-ng' at version '1.50+dfsg-1' 
with architecture ''
Unable to make a source version for version '1.50+dfsg-1'
Marked as fixed in versions 1.50+dfsg-1.
Bug #915201 [espeak-ng] espeak-ng: Mbrola voices not working properly
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#956608: marked as done (mediathekview main GUI broken: shrinked to minimum size)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:10:21 +0200 (CEST)
with message-id <1735269417.17928.1586797821...@office.mailbox.org>
and subject line 
has caused the Debian Bug report #956608,
regarding mediathekview main GUI broken: shrinked to minimum size
to be marked as done.

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

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


-- 
956608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediathekview
Version: 13.2.1-4

I use xmonad as window manager, but that should hopefully not be a problem.
The app starts fullscreen, but the GUI elements only occupy the minimal
possible amount of space. As a result, the app can not be used.
Also menus are rendered far away from the top menu.

I tested Java 9, 13 and 15.

See attached screenshot

-- System Information:
Debian Release: rodete
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.17-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_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/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mediathekview depends on:
ii  java-wrappers   0.3
ii  libcommons-compress-java1.18-3
ii  libcommons-configuration2-java  2.2-1
ii  libcommons-dbcp2-java   2.7.0-1
ii  libcommons-lang3-java   3.8-2
ii  libcommons-pool2-java   2.6.2-1
ii  libcontrolsfx-java  9.0.0+hg20181001-1
ii  libguava-java   19.0-1+build2
ii  libh2-java  1.4.197-4
ii  libjackson2-core-java   2.10.1-1
ii  libjchart2d-java3.2.2+dfsg2-2
ii  libjiconfont-font-awesome-java  4.7.0.0-1
ii  libjiconfont-java   1.0.0-1
ii  libjiconfont-swing-java 1.0.1-1
ii  libjide-oss-java3.7.6+dfsg-1
ii  liblog4j2-java  2.11.2-1
ii  libmbassador-java   1.3.1-1
ii  libmiglayout-java   5.1-2
ii  libokhttp-java  3.13.1-1
ii  libopenjfx-java 11.0.2+1-1+build2
ii  libswingx-java  1:1.6.2-4
ii  libxz-java  1.8-2
ii  openjdk-15-jre [java9-runtime]  15~11-1

Versions of packages mediathekview recommends:
ii  flvstreamer  2.1c1-1+build1
ii  mpv  0.30.0-1
ii  vlc  3.0.8-3+build3

Versions of packages mediathekview suggests:
ii  ffmpeg  7:4.2.2-1+build3

-- no debconf information--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 16060--- End Message ---

Bug#936973: marked as done (lxml: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 17:05:12 +
with message-id 
and subject line Bug#936973: fixed in lxml 4.5.0-1.1
has caused the Debian Bug report #936973,
regarding lxml: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:lxml

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: lxml
Source-Version: 4.5.0-1.1
Done: Sandro Tosi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 12:39:33 -0400
Source: lxml
Architecture: source
Version: 4.5.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Sandro Tosi 
Closes: 936973
Changes:
 lxml (4.5.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936973
   * Install documentation under python-lxml-doc
   * python3-lxml takes over some file from python-lxml, so Breaks+Replaces it
Checksums-Sha1:
 1fc90f4c8d12fb2f0e746e9912e7a9f3d634107d 1987 lxml_4.5.0-1.1.dsc
 e6b4c3e088fa7374905743480aaa60542ae598d4 7512 lxml_4.5.0-1.1.debian.tar.xz
 8a8dfcd774e72a4cd5f448d5b1054a05cce55372 8731 lxml_4.5.0-1.1_amd64.buildinfo
Checksums-Sha256:
 2ec2b52e4945f9cf258eeb24e3de1104212cd24c5d47e25d9283dac384635009 1987 
lxml_4.5.0-1.1.dsc
 db4ec2d4d858bb78c77c62de071b1f6a73ac026b3d2d86bd399f5928a9600da0 7512 
lxml_4.5.0-1.1.debian.tar.xz
 4a39fcd4c482764d0143209b9c3bc7b9628d4748c357f8f363f51260bf9b67b6 8731 
lxml_4.5.0-1.1_amd64.

Bug#867347: marked as done (balsa: please transition to gmime 3.0)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 17:03:40 +
with message-id 
and subject line Bug#867347: fixed in balsa 2.6.0-1
has caused the Debian Bug report #867347,
regarding balsa: please transition to gmime 3.0
to be marked as done.

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

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


-- 
867347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gmime
Severity: wishlist
Control: affects -1 gmime
Control: clone -1 -2
Control: reassign -2 asterisk 1:13.14.1~dfsg-2
Control: retitle -2 asterisk: please transition to gmime 3.0
Control: clone -1 -3
Control: reassign -3 balsa 2.5.3-2
Control: retitle -3 asterisk: please transition to gmime 3.0
Control: clone -1 -4
Control: reassign -4 gambas3 3.9.2-1
Control: retitle -4 gambas3: please transition to gmime 3.0
Control: clone -1 -5
Control: reassign -5 geary v0.11.3-1
Control: retitle -5 geary: please transition to gmime 3.0
Control: clone -1 -6
Control: reassign -6 grilo-plugins 0.3.4-2
Control: retitle -6 grilo-plugins: please transition to gmime 3.0
Control: clone -1 -7
Control: reassign -7 mail-notification 5.4.dfsg.1-14
Control: retitle -7 mail-notification: please transition to gmime 3.0
Control: clone -1 -8
Control: reassign -8 maildir-utils 0.9.18-1
Control: retitle -8 maildir-utils: please transition to gmime 3.0
Control: clone -1 -9
Control: reassign -9 notmuch 0.24.2-2
Control: retitle -9 notmuch: please transition to gmime 3.0
Control: clone -1 -10
Control: reassign -10 pan 0.141-2
Control: retitle -10 pan: please transition to gmime 3.0
Control: clone -1 -11
Control: reassign -11 pinot 1.05-1.2
Control: retitle -11 pinot: please transition to gmime 3.0
Control: clone -1 -12
Control: reassign -12 totem-pl-parser 3.10.8-1
Control: retitle -12 totem-pl-parser: please transition to gmime 3.0
Control: block -1 with -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12

Hi there!

The your debian package build-depends on libgmime-2.6-dev.

gmime 3.0.1 is now in debian unstable, and it provides libgmime-3.0-dev.
Version 3 of gmime has been in debian experimental for a couple months
now.

Please try to convert your debian packages to use libgmime-3.0-dev in
unstable if possible, so that we can avoid shipping gmime 2.6 in buster.

If you run into trouble with the transition, you might want to take a
look at gmime's porting guide from 2.6 to 3.0:

 https://github.com/jstedfast/gmime/blob/master/PORTING

If this transition won't be possible for your package, please follow up
to this bug report and we can discuss options.  It would be great to not
have to keep gmime 2.6 in debian buster, but i will keep that option
open just in case something is really unportable.

You might also be interested in:

https://release.debian.org/transitions/html/auto-gmime.html

Regards,

--dkg
--- End Message ---
--- Begin Message ---
Source: balsa
Source-Version: 2.6.0-1
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated balsa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Apr 2020 12:16:56 -0400
Source: balsa
Architecture: source
Version: 2.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Daniel Kahn Gillmor 
Closes: 867347
Changes:
 balsa (2.6.0-1) unstable; urgency=medium
 .
   * New upstream release
   * drop patches already upstream
   * refresh patch that avoids git fanciness
   * build-depend on gmime 3.0 (>= 3.2.6) (Closes: #867347)
   * drop bigon from Uploaders due to ageing out from d/changelog
   * d/copyright: note appstream metadata as CC0-1.0
   * gbp.conf: strip Makefile.in during import of future revisions
   * ci: use --check-mail instead of --checkmail in screenshot test
Checksums-Sha1:
 135a9fa4ba69c396e6f6ea38282d81cfba82cc57 1908 balsa_2.6.0-1.dsc
 9cb5083f9e7156fccc76d0ea98457046cc9f756c 4518346 balsa_2.6.0.orig.tar.bz2
 501958523815b12a35ece91a9d1294cd618766dd 

Bug#956574: marked as done (josm: exception when attempting to upload "Can't find bundle for base name ch.poole.openinghoursparser.Messages")

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 16:50:17 +
with message-id 
and subject line Bug#956574: fixed in josm 0.0.svn16239+dfsg-2
has caused the Debian Bug report #956574,
regarding josm: exception when attempting to upload "Can't find bundle for base 
name ch.poole.openinghoursparser.Messages"
to be marked as done.

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

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


-- 
956574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: josm
Version: 0.0.svn16239+dfsg-1
Severity: important

Dear Maintainer,

Attempting to upload when having set opening_hours tags gave me the Java
Exception error below which preventing the upload from working. Not sure if
this is upstream issue or not.

2020-04-13 18:28:23.125 SEVERE: Handled by bug report queue:
java.lang.ExceptionInInitializerError. Cause:
java.util.MissingResourceException: Can't find bundle for base name
ch.poole.openinghoursparser.Messages, locale
java.lang.ExceptionInInitializerError
at
org.openstreetmap.josm.data.validation.tests.OpeningHourTest.checkOpeningHourSyntax(OpeningHourTest.java:89)
at
org.openstreetmap.josm.data.validation.tests.OpeningHourTest.check(OpeningHourTest.java:114)
at
org.openstreetmap.josm.data.validation.Test$TagTest.visit(Test.java:128)
at org.openstreetmap.josm.data.osm.Node.accept(Node.java:214)
at org.openstreetmap.josm.data.validation.Test.visit(Test.java:215)
at
org.openstreetmap.josm.actions.upload.ValidateUploadHook.checkUpload(ValidateUploadHook.java:66)
at
org.openstreetmap.josm.actions.UploadAction.checkPreUploadConditions(UploadAction.java:219)
at
org.openstreetmap.josm.actions.UploadAction.uploadData(UploadAction.java:238)
at
org.openstreetmap.josm.actions.UploadAction.actionPerformed(UploadAction.java:294)
at
java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
at
java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
at
java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
at
java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
at
java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
at
java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)
at
java.desktop/java.awt.Component.processMouseEvent(Component.java:6631)
at
java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
at java.desktop/java.awt.Component.processEvent(Component.java:6396)
at java.desktop/java.awt.Container.processEvent(Container.java:2263)
at
java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5007)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
at
java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
at
java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at
java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
at
java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at
java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
at
java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
at
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native
Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
at java.base/java.security.AccessController.doPrivileged(Native
Method)
at
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at
java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
at
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(E

Bug#939903: marked as done (openvpn: systemd does not start openvpn after upgrade from stretch tu buster)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 18:40:31 +0200
with message-id <91cbe842571db08b35e7b3b7b927c9e3e6a0f48e.camel@jff.email>
and subject line Re: openvpn: systemd does not start openvpn after upgrade from 
stretch tu buster
has caused the Debian Bug report #939903,
regarding openvpn: systemd does not start openvpn after upgrade from stretch tu 
buster
to be marked as done.

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

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


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

Dear Maintainer,

I am running openvpn in a Linux container. I have upgraded openvpn from stretch 
to buster version. I have tried to start openvpn with "systemctl start 
openvpn". The error in the syslog is:

Sep 10 00:31:17 vpn systemd[1]: Starting OpenVPN connection to server...
Sep 10 00:31:17 vpn systemd[3766]: openvpn@server.service: Failed to set up 
mount namespacing: Permission denied
Sep 10 00:31:17 vpn systemd[3766]: openvpn@server.service: Failed at step 
NAMESPACE spawning /usr/sbin/openvpn: Permission denied
Sep 10 00:31:17 vpn systemd[1]: openvpn@server.service: Main process exited, 
code=exited, status=226/NAMESPACE
Sep 10 00:31:17 vpn systemd[1]: openvpn@server.service: Failed with result 
'exit-code'.
Sep 10 00:31:17 vpn systemd[1]: Failed to start OpenVPN connection to server.

I would expect openvpn to start normally without errors.

I have tried to add the following lines to the systemd unit, but it has not 
helped:

PrivateTmp=false
NoNewPrivileges=yes

I have tried to manually run openvpn with these commands:

/usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 
--cd /etc/openvpn --config /etc/openvpn/server.conf --writepid 
/run/openvpn/server.pid
openvpn --config /etc/openvpn/server.conf

Both commands were successful.

Regards,
Mikolaj Menke

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

Kernel: Linux 4.15.18-16-pve (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  iproute2   4.20.0-2
ii  libc6  2.28-10
ii  liblz4-1   1.8.3-1
ii  liblzo2-2  2.10-0.1
ii  libpam0g   1.3.1-5
ii  libpkcs11-helper1  1.25.1-1
ii  libssl1.1  1.1.1c-1
ii  libsystemd0241-7~deb10u1
ii  lsb-base   10.2019051400

Versions of packages openvpn recommends:
ii  easy-rsa  3.0.6-1

Versions of packages openvpn suggests:
ii  openssl   1.1.1c-1
pn  openvpn-systemd-resolved  
pn  resolvconf

-- debconf information:
  openvpn/create_tun: false
--- End Message ---
--- Begin Message ---
Hello  Mikolaj,
thank you for spending your time helping to make Debian better with
this bug report.

Niklas Miller has described the solution. I therefore close this bug.


CU

Jörg
 
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#803909: marked as done (Assertion `bm->bus->dma->aiocb == ((void *)0)' failed)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 19:39:12 +0300
with message-id <7be09e1a-6606-b6c7-560b-ce9f6f87a...@msgid.tls.msk.ru>
and subject line Re: Assertion `bm->bus->dma->aiocb == ((void *)0)' failed
has caused the Debian Bug report #803909,
regarding Assertion `bm->bus->dma->aiocb == ((void *)0)' failed
to be marked as done.

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

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


-- 
803909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:2.1+dfsg-12+deb8u4

qemu-system-x86_64 crashes after a while when assertion fails.
Running an install of Windows 7 Enterprise.

qemu-system-x86_64 -enable-kvm -cpu host -localtime -usb -boot c \
-fda fat:floppy:rw:a \
-drive file=win7.qcow2,if=ide,index=0,media=disk,format=qcow2,\
detect-zeroes=unmap,discard=unmap \
-drive file=win7e32.iso,if=ide,index=2,media=cdrom,format=raw \
-usbdevice tablet \
-net nic,model=rtl8139 \
-net user,hostfwd=tcp:10.1.16.4:8080-:80,hostfwd=tcp:127.0.0.1:8023-:23,\
hostfwd=tcp:127.0.0.1:8139-:139,hostfwd=tcp:127.0.0.1:8445-:445,\
hostfwd=tcp:127.0.0.1:11389-:3389,hostfwd=udp:127.0.0.1:11389-:3389 \
-usbdevice disk:format=raw:usb.img \
-soundhw ac97 \
-m 2047M

qemu-system-x86_64: /build/qemu-e7wj_D/qemu-2.1+dfsg/hw/ide/pci.c:330:
bmdma_cmd_writeb: Assertion `bm->bus->dma->aiocb == ((void *)0)' failed.
--- End Message ---
--- Begin Message ---
Version: 1:4.2-1

On Tue, 3 Nov 2015 12:22:41 +0800 Andrew Buckeridge - Private 
 wrote:
> Package: qemu-system-x86
> Version: 1:2.1+dfsg-12+deb8u4
> 
> qemu-system-x86_64 crashes after a while when assertion fails.
> Running an install of Windows 7 Enterprise.
...
> qemu-system-x86_64: /build/qemu-e7wj_D/qemu-2.1+dfsg/hw/ide/pci.c:330:
> bmdma_cmd_writeb: Assertion `bm->bus->dma->aiocb == ((void *)0)' failed.

qemu 2.1 is rather old. If this problem is still present in current
version, please reopen this bugreport.

Thanks,

/mjt--- End Message ---

Bug#940956: marked as done (systemd unit description worded misleadingly)

[Debian Bug Tracking System]

Your message dated Mon, 13 Apr 2020 18:30:43 +0200
with message-id <8f9c823ea86365e6ec0fc5525d7e2e8b07082fef.camel@jff.email>
and subject line Re: systemd unit description worded misleadingly
has caused the Debian Bug report #940956,
regarding systemd unit description worded misleadingly
to be marked as done.

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

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


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

Hi,

This:

1 [4/4992]mh@torres:~ $ sudo systemctl cat openvpn@.service
/lib/systemd/system/openvpn@.service
[Unit]
Description=OpenVPN connection to %i

leads to the misleading output "OpenVPN connection to server" when an
OpenVPN instance called "server" is started which doesnt connect
anywhere but instead waits for an incoming connection.

Maybe this should be re-worded like "OpenVPN instance (%i)".

Greetings
Marc
--- End Message ---
--- Begin Message ---
Hello Marc,
thank you for spending your time helping to make Debian better with
this bug report.

Your proposed change may affect other tools that trigger it. 

Therefore I will not accept this change.

Bug closed.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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