Bug#943042: gitso: Python2 removal in sid/bullseye

[Florian Schlichting]

Hi Scott,

> > > The package doesn't look all that complicated.  I can take a stab at 
> > > trying
> > > to port it to Python 3.  If I get it working, perhaps I can ask you to 
> > > test
> > > it?
> > 
> > that would be awesome! I can definitely do the testing.
> 
> I submitted a merge request on salsa:
> https://salsa.debian.org/debian/gitso/merge_requests/2
> 
> Let me know if you run into any problems or have any comments.

that was fast! In my testing, the package behaves just like the old
version, so I'll prepare an upload in a minute. Thanks a TON!

Florian

Bug#930858: marked as done (gif2png: "not expected to be able to deal with arbitrarily broken input")

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:31:00 +
with message-id 
and subject line Bug#945793: Removed package(s) from unstable
has caused the Debian Bug report #930858,
regarding gif2png: "not expected to be able to deal with arbitrarily broken 
input"
to be marked as done.

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

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


-- 
930858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gif2png
Version: 2.5.8-1+b2
Severity: grave
Tags: security
Justification: user security hole

I happened to notice the entry for 2.5.14 (which I realise is newer than
the one in Debian) on http://www.catb.org/~esr/gif2png/NEWS:

  "Redirect segfault to a graceful exit. Tired of meaningless fuzzer
  bugs."

This is from https://gitlab.com/esr/gif2png/issues/5, where the upstream
maintainer says:

  "Crash confirmed. Buthis program is not expected to be able to deal
  with arbitrarily broken input. All I'm going to do about it is add a
  SIGSEGV handler."

I understand that security vulnerabilities happen and that normally they
are patched and life goes on.  But this is a different case: here we
have an upstream maintainer explicitly saying that an image-processing
program is not suitable for use on arbitrary input, and explicitly
adding code to defeat fuzzers that might otherwise help to find bugs in
it.  I'm honestly flabbergasted by this approach to what must surely be
undefined behaviour in C code.

I suppose that one might still safely use gif2png to convert one's own
website if all it had to deal with was trusted images.  However, this is
an undocumented limitation, and it's quite easy to believe that
unsuspecting people might try to use gif2png as part of a larger system
where the input files cannot be trusted, such as an image-upload widget
on a website.

At the very least, the limitation that this program cannot safely be
used with untrusted input needs to be prominently documented (I'd
suggest the package description and the manual page).  web2png would be
harder to replace this way, but at least people wanting to make
straightforward use of gif2png should perhaps be advised to use some
other image processing system instead whose maintainers have a more
reasonable approach to reports of undefined behaviour in their programs.

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

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

Versions of packages gif2png depends on:
ii  libc62.28-10
ii  libpng16-16  1.6.36-6

Versions of packages gif2png recommends:
ii  python  2.7.16-1

gif2png suggests no packages.

-- no debconf information

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]
--- End Message ---
--- Begin Message ---
Version: 2.5.8-1+rm

Dear submitter,

as the package gif2png 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/945793

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:32:02 +
with message-id 
and subject line Bug#946182: Removed package(s) from unstable
has caused the Debian Bug report #943039,
regarding disper: 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.)


-- 
943039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: disper
Version: 0.3.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 (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: 0.3.1-2+rm

Dear submitter,

as the package disper 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/946182

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:31:00 +
with message-id 
and subject line Bug#945793: Removed package(s) from unstable
has caused the Debian Bug report #945644,
regarding gif2png: 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.)


-- 
945644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gif2png
Version: 2.5.8-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_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package gif2png 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/945793

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#844505: marked as done (disper -S → Segmentation fault)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:32:02 +
with message-id 
and subject line Bug#946182: Removed package(s) from unstable
has caused the Debian Bug report #844505,
regarding disper -S → Segmentation fault
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Running "disper -S" simply emits "Segmentation fault".

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

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

Versions of packages disper depends on:
ii  libx11-62:1.6.3-1
ii  libxrandr2  2:1.5.0-1
pn  python:any  

Versions of packages disper recommends:
ii  libnotify-bin  0.7.7-1

disper suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYLEAZAAoJECx8MUbBoAEhe1AP/iQpX0HSGU2xgunrpMuatWM3
n2Ar4uH/Achq9OfBM47YIjKGuL7Wwx2cfkmZ7nwY6rd+cTDSoMbqG7VgRmKj3CCQ
sugIgjWZ/4TCcawk0p/jYx13O+iH5Acz6XKDQYgcjTK6c6kvKu6HE7aEQwyQggfN
qn7JH2WhYmMStkMftGlzGNlh5NHtrOoeZ3a2C7nx+rkQJKE4i/1RHH9TZSClg4lw
KgekWPC/nyjuDqdqSOcaDroEI9D8geYgixtjGF62ipy9kRsDCiCzNryUJy1voLA/
P4USozA0D4P8rbpN1R2bFYaFFDU+QG7FuDm+vWd71oiWW8cW76i89V7Qvj7zkqUC
/113MfbHu13WJWQ+32M7tWWhU3QhcKmu7gvqv4jlgQsnKn1Q9XzBVYbDJbneyfMw
tMqVpig7f2RdXJz/tOoQM7N4+HZ4W+r1Ix7SlWKsq/JzGRqyZmKrlprk87D9wNU+
LGApiPmvEthTAZ7DTZBS5dz8SqKglUV0GlPIEaU08ntnlhB6NS/wuGFpJfGceFF6
S1AlKcHsLHL+yIwlwvuzE24bdXNJ6rfGrtd85ob/sDBFYfRsofaIsbbYLyBptlOF
HoTcO82Tvk7S3030EmPUKF3ZswwfBrfIVezeflMxA9KbaAcqQ7mFBNOHMCLwkjqS
5Ut6FovLTwp30hoJ/YN+
=vBl4
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.3.1-2+rm

Dear submitter,

as the package disper 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/946182

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:30:11 +
with message-id 
and subject line Bug#945775: Removed package(s) from unstable
has caused the Debian Bug report #938188,
regarding python-sponge: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-sponge

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.3.1-1.1+rm

Dear submitter,

as the package python-sponge 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/945775

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#922116: marked as done (tulip - FTBFS - error: there are no arguments to 'memcpy' that depend on a template parameter)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id 
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #922116,
regarding tulip - FTBFS - error: there are no arguments to 'memcpy' that depend 
on a template parameter
to be marked as done.

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

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


-- 
922116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tulip
Version: *4.8**.0+dfsg-7*10
Severity: important
Tags: patch

Hello,
There is a regression on all platforms for tulip version from
4.8.0dfsg-2+b7  to current (4.8.0dfsg-2+b10 ) The error message is

  *  error: there are no arguments to 'memcpy' that depend on a template
parameter, so a declaration of 'memcpy' must be available [-fpermissive]

A simple patch could be to add #include  which includes
definition of memcpy() in some header files like
   . /thirdparty/OGDF/include/ogdf/basic/DisjointSets.h

Thanks
 
--- End Message ---
--- Begin Message ---
Version: 4.8.0dfsg-2+rm

Dear submitter,

as the package tulip 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/940232

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#925689: marked as done (gamera: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:29:47 +
with message-id 
and subject line Bug#945179: Removed package(s) from unstable
has caused the Debian Bug report #925689,
regarding gamera: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/gamera_3.4.3-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
test_plugins.TestPlugins.test_plugin_sauvola_threshold ... ok
test_plugins.TestPlugins.test_plugin_save_PNG ... ok
test_plugins.TestPlugins.test_plugin_save_image ... ok
test_plugins.TestPlugins.test_plugin_save_tiff ... ok
test_plugins.TestPlugins.test_plugin_scale ... ok
test_plugins.TestPlugins.test_plugin_segmentation_error ... ok
test_plugins.TestPlugins.test_plugin_shading_subtraction ... ok
test_plugins.TestPlugins.test_plugin_shaped_grouping_function ... ok
test_plugins.TestPlugins.test_plugin_shear_column ... ok
test_plugins.TestPlugins.test_plugin_shear_row ... ok
test_plugins.TestPlugins.test_plugin_simple_sharpen ... ok
test_plugins.TestPlugins.test_plugin_skeleton_features ... ok
test_plugins.TestPlugins.test_plugin_sobel_edge_detection ... ok
test_plugins.TestPlugins.test_plugin_soft_threshold ... ok
test_plugins.TestPlugins.test_plugin_soft_threshold_find_sigma ... ok
test_plugins.TestPlugins.test_plugin_splitx ... ok
test_plugins.TestPlugins.test_plugin_splitx_left ... ok
test_plugins.TestPlugins.test_plugin_splitx_max ... ok
test_plugins.TestPlugins.test_plugin_splitx_right ... ok
test_plugins.TestPlugins.test_plugin_splity ... ok
test_plugins.TestPlugins.test_plugin_splity_bottom ... ok
test_plugins.TestPlugins.test_plugin_splity_top ... ok
test_plugins.TestPlugins.test_plugin_sub_cc_analysis ... ok
test_plugins.TestPlugins.test_plugin_subimage ... ok
test_plugins.TestPlugins.test_plugin_subtract_images ... ok
test_plugins.TestPlugins.test_plugin_textline_reading_order ... ok
test_plugins.TestPlugins.test_plugin_thin_hs ... ok
test_plugins.TestPlugins.test_plugin_thin_hs_large_image ... ok
test_plugins.TestPlugins.test_plugin_thin_lc ... ok
test_plugins.TestPlugins.test_plugin_thin_zs ... ok
test_plugins.TestPlugins.test_plugin_threshold ... ok
test_plugins.TestPlugins.test_plugin_tiff_info ... ok
test_plugins.TestPlugins.test_plugin_to_buffer ... ok
test_plugins.TestPlugins.test_plugin_to_complex ... ok
test_plugins.TestPlugins.test_plugin_to_cv ... ok
test_plugins.TestPlugins.test_plugin_to_float ... ok
test_plugins.TestPlugins.test_plugin_to_grey16 ... ok
test_plugins.TestPlugins.test_plugin_to_greyscale ... ok
test_plugins.TestPlugins.test_plugin_to_nested_list ... ok
test_plugins.TestPlugins.test_plugin_to_onebit ... ok
test_plugins.TestPlugins.test_plugin_to_pil ... ok
test_plugins.TestPlugins.test_plugin_to_rgb ... ok
test_plugins.TestPlugins.test_plugin_to_rle ... ok
test_plugins.TestPlugins.test_plugin_to_xml ... ok
test_plugins.TestPlugins.test_plugin_to_xml_filename ... ok
test_plugins.TestPlugins.test_plugin_top_bottom ... ok
test_plugins.TestPlugins.test_plugin_trim_image ... ok
test_plugins.TestPlugins.test_plugin_tsai_moment_preserving_

Bug#866470: marked as done (python-sponge: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:30:11 +
with message-id 
and subject line Bug#945775: Removed package(s) from unstable
has caused the Debian Bug report #866470,
regarding python-sponge: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
to be marked as done.

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

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


-- 
866470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-sponge
Version: 0.3.1-1.1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Version: 0.3.1-1.1+rm

Dear submitter,

as the package python-sponge 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/945775

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#853688: marked as done (tulip: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id 
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #853688,
regarding tulip: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tulip
Version: 4.8.0dfsg-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/tulip_4.8.0dfsg-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
[ 22%] Building CXX object 
library/tulip-core/src/CMakeFiles/tulip-core-4.8.dir/YajlFacade.cpp.o
cd /<>/obj-x86_64-linux-gnu/library/tulip-core/src && /usr/bin/c++ 
  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_OPENGL_LIB 
-DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XMLPATTERNS_LIB 
-DQT_XML_LIB -D_LINUX -Dtulip_core_4_8_EXPORTS 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKit 
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets 
-I/<>/library/tulip-core/src/../include 
-I/<>/obj-x86_64-linux-gnu/library/tulip-core/include 
-I/<> -I/<>/thirdparty/yajl/src 
-I/<>/thirdparty/yajl/src/api -I/<>/obj-x86_64-linux-gnu/thirdparty/yajl/yajl-2.1.0/include 
-I/<>/thirdparty -I/<>/thirdparty/gzstream  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DI64 -Wall -Wextra 
-Wunused -Wno-long-long -pedantic -D_TULIP_LIB_DIR="\"/usr/lib/\"" -fPIC   -o 
CMakeFiles/tulip-core-4.8.dir/YajlFacade.cpp.o -c 
/<>/library/tulip-core/src/YajlFacade.cpp
[ 22%] Building CXX object 
library/tulip-core/src/CMakeFiles/tulip-core-4.8.dir/PluginLister.cpp.o
cd /<>/obj-x86_64-linux-gnu/library/tulip-core/src && /usr/bin/c++ 
  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_OPENGL_LIB 
-DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XMLPATTERNS_LIB 
-DQT_XML_LIB -D_LINUX -Dtulip_core_4_8_EXPORTS 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKit 
-I/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets 
-I/<>/library/tulip-core/src/../include 
-I/<>/obj-x86_64-linux-gnu/library/tulip-core/include 
-I/<> -I/<>/thirdparty/yajl/src 
-I/<>/thirdparty/yajl/src/api -I/<>/obj-x86_64-linux-gnu/thirdparty/yajl/yajl-2.1.0/include 
-I/<>/thirdparty -I/<>/thirdparty/gzstream  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DI64 -Wall -Wextra 
-Wunused -Wno-long-long -pedantic -D_TULIP_LIB_DIR="\"/usr/lib/\"" -fPIC   -o 
CMakeFiles/tulip-core-4.8.dir/PluginLister.cpp.o -c 
/<>/library/tulip-core/src/PluginLister.cpp
[ 22%

Bug#938723: marked as done (tulip: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id 
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #938723,
regarding tulip: 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.)


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

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: 4.8.0dfsg-2+rm

Dear submitter,

as the package tulip 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/940232

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#937476: marked as done (RM: pymappergui -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:28:03 +
with message-id 
and subject line Bug#937476: Removed package(s) from unstable
has caused the Debian Bug report #937476,
regarding RM: pymappergui -- RoQA; dead upstream; unmaintained; low popcon; 
blocking py2 removal
to be marked as done.

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

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


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

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 ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pymappergui |  0.1-2 | source, all

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal
--

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

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

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

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

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

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 ftpm

Bug#945691: marked as done (linuxbrew-wrapper: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:26:17 +
with message-id 
and subject line Bug#919039: Removed package(s) from unstable
has caused the Debian Bug report #945691,
regarding linuxbrew-wrapper: 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.)


-- 
945691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linuxbrew-wrapper
Version: 20180923-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_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package linuxbrew-wrapper 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/919039

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#937420: marked as done (RM: pydhcplib -- removal triggered by the Python2 removal)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:27:34 +
with message-id 
and subject line Bug#937420: Removed package(s) from unstable
has caused the Debian Bug report #937420,
regarding RM: pydhcplib -- removal triggered by the Python2 removal
to be marked as done.

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

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


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

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 ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 pydhcplib |0.6.2-3 | source
python-pydhcplib |0.6.2-3 | all

--- Reason ---
removal triggered by the Python2 removal
--

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

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

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

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

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

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

Bug#938650: marked as done (tessa: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:27:14 +
with message-id 
and subject line Bug#930143: Removed package(s) from unstable
has caused the Debian Bug report #938650,
regarding tessa: 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.)


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

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.3.1-6.2+rm

Dear submitter,

as the package tessa 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/930143

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:23:48 +
with message-id 
and subject line Bug#834337: Removed package(s) from unstable
has caused the Debian Bug report #938853,
regarding xnbd: 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.)


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

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.3.0-3+rm

Dear submitter,

as the package xnbd 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/834337

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:21:16 +
with message-id 
and subject line Bug#574013: Removed package(s) from unstable
has caused the Debian Bug report #945650,
regarding ccontrol: 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.)


-- 
945650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ccontrol
Version: 1.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package ccontrol 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/574013

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:24:20 +
with message-id 
and subject line Bug#836421: Removed package(s) from unstable
has caused the Debian Bug report #945671,
regarding fofix-dfsg: 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.)


-- 
945671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fofix-dfsg
Version: 3.121-7
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package fofix-dfsg 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/836421

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:22:14 +
with message-id 
and subject line Bug#814894: Removed package(s) from unstable
has caused the Debian Bug report #937044,
regarding mididings: 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.)


-- 
937044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mididings
Version: 0~20120419~ds0-6
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mididings

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~20120419~ds0-6+rm

Dear submitter,

as the package mididings 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/814894

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#885519: marked as done (ccontrol: Recommends unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:21:16 +
with message-id 
and subject line Bug#574013: Removed package(s) from unstable
has caused the Debian Bug report #885519,
regarding ccontrol: Recommends unmaintained pygtk
to be marked as done.

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

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


-- 
885519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ccontrol
Version: 1.0-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.0-2+rm

Dear submitter,

as the package ccontrol 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/574013

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

[Debian Bug Tracking System]

Your message dated Thu, 05 Dec 2019 06:21:46 +
with message-id 
and subject line Bug#681042: Removed package(s) from unstable
has caused the Debian Bug report #945658,
regarding ladr: 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.)


-- 
945658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ladr
Version: 0.0.200911a-2.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_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package ladr 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/681042

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#942914: caja-mediainfo: Python2 removal in sid/bullseye

[Vlad Orlov]

Hi,

This extension seems to work with Python 3 after one import change:

-from MediaInfoDLL import *
+from MediaInfoDLL3 import *

After that, it also needs a dependency change from python-mediainfodll
to python3-mediainfodll.

Bug#875250: Intend to port to Qt 5

[Benda Xu]

Hi Moritz,

I started to work on qt5 port of SCIM.  There is some remaining blocks.
I will work on it for another 10 days.

I want to postpone to deadline to Dec 15, if that does not drag the QT5
migration too much.

Thank you for your understanding!

Yours,
Benda

Processed: ledger: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936834 [src:ledger] ledger: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#938859: marked as done (yade: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 22:19:51 +
with message-id 
and subject line Bug#938859: fixed in yade 2019.12~git~0~e74819ea-1~exp1
has caused the Debian Bug report #938859,
regarding yade: 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.)


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

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: yade
Source-Version: 2019.12~git~0~e74819ea-1~exp1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 23:08:05 +0100
Source: yade
Architecture: source
Version: 2019.12~git~0~e74819ea-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 938859
Changes:
 yade (2019.12~git~0~e74819ea-1~exp1) experimental; urgency=medium
 .
   * [ee07f9d] Switch to python3. (Closes: #938859)
   * [e4c0fff] Refresh patch
   * [9db90d4] Set Stndards-Version to 4.4.1
   * [648e6a3] Trim trailing whitespace.
   * [f961d72] Set upstream metadata fields: Repository.
   * [21d9f4b] Use canonical URL in Vcs-Browser.
   * [b71d6cb] Remove obsolete fields Name from debian/upstream/metadata.
   * [dee59f9] Update upstream/metadata
   * [2c51dcb] Temporarly use python-yade for python3-bindings
   * [b196fd3] Some tweaks in the d/rules to make package buildable
   * [62fdca3] Use libsqlite3-dev instead of libsqlite-dev
   * [f434690] Set upstream metadata fields: Repository-Browse.
   * [6b86

Bug#921220: xchat stops autoconnecting, complaining about "%U" and "host unknown", broken .desktop entry ?

[ydirson]

The control email got bounced before unarchiving, here are the details of new 
findings. 

- Mail original -

> unarchive 921220
> reopen 921220
> retitle 921220 xchat.desktop makes invalid use of %U, breaks at least
> lxqt and flwm
> affects 921220 + lxqt flwm
> severity 921220 grave
> thanks

> I've switched away from lxqt and forgot to follow up on this issue,
> but now I'm stumbling on a configure error of flwm,
> which qualifies as grave under the "breaks other package" rule.

> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Setting up flwm (1.02+git2015.10.03+7dbb30-6) ...
> Exec key for 'XChat IRC' contains '%F', '%U' or '%D' at the wrong
> place
> dpkg: error processing package flwm (--configure):
> installed flwm package post-installation script subprocess returned
> error exit status 255
> Errors were encountered while processing:
> flwm

> Note that the freedesktop standard [1] says "Field codes must not be
> used inside a quoted argument, the result of field code expansion
> inside a
> quoted argument is undefined", this could possibly be the reason for
> any complaint.

> If I replace the faulty line by just "Exec=xchat --existing --url %U"
> the flwm configure step does succeed, which seems to confirm this
> diagnostic.

> Probably the better solution would be to use a wrapper script, which
> could have saner behaviour (the current behaviour lauches "exec
> xchat"
> on any error of the first try, where it looks like what we really
> want is to launch it if %U is empty.

> https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s07.html

> - Mail original -

> > De: "Gianfranco Costamagna" 
> 
> > À: ydir...@free.fr, 921220-d...@bugs.debian.org
> 
> > Envoyé: Mardi 5 Février 2019 11:13:35
> 
> > Objet: Re: Bug#921220: xchat stops autoconnecting, complaining
> > about
> > "%U" and "host unknown", broken .desktop entry ?
> 

> > Hello,
> 

> > >OTOH when launched from cmdline the problem does not appear.
> 

> > >
> 

> > >And indeed the provided .desktop file shows:
> 

> > >
> 

> > >Exec=sh -c "xchat --existing --url %U || exec xchat"
> 

> > >
> 

> > >Could it be that there was a fix in a recently-dropped patch ?
> 

> > I didn't drop any patch (you didn't even tell me which was your
> > previous version, so its difficult to say)
> 
> > but looks like a network error to me
> 
> I guess at that time I made assumptions on not-so-recent "Drop old
> and useless patch" changelog entry, my bad.

Processed: tagging 936886

[Debian Bug Tracking System]

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

> tags 936886 + help
Bug #936886 [src:libktoblzcheck] libktoblzcheck: Python2 removal in sid/bullseye
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#936886: Bug#946174: libktoblzcheck: Python2 removal in sid/bullseye

[Micha Lenk]

Status update:

I started working on removing the python 2 package, which turned out to 
be more complicated than necessary. I had to rip out a broken chunk from 
CMakeLists.txt that caused the build to fail when no Python interpreter 
is installed. This made at least the build succeed again, but for some 
reason now the very basic autopkgtest is failing.


The work in progress code to fix this bug is currently tracked in branch 
python_removal on Salsa:

https://salsa.debian.org/aqbanking-team/pkg-ktoblzcheck/tree/python_removal

Check the autopkgtest log from Salsa CI for details about how bad it fails:
https://salsa.debian.org/aqbanking-team/pkg-ktoblzcheck/-/jobs/440456

The way how bad the autopkgtest fails...

Could not read directory "": No such file or directory
Oops, no bank data file was found in directory ""! The ktoblzcheck 
library will not work.


... reminds how the package broke in my first attempts of using CMake 
for building libktoblzcheck 1.50. At that time I added 
-DINSTALL_RAW_BANKDATA_FILE=1 to dh_auto_configure in debian/rules. Now 
it looks as if this flag no longer causes the correct bank data path to 
be hard-coded. We will need to look into the code to see what's 
different this time.

Processed: Re: Bug#921220: xchat stops autoconnecting, complaining about "%U" and "host unknown", broken .desktop entry ?

[Debian Bug Tracking System]

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

> unarchive 921220
Bug #921220 {Done: Gianfranco Costamagna } [xchat] 
xchat stops autoconnecting, complaining about "%U" and "host unknown", broken 
.desktop entry ?
Unarchived Bug 921220
> reopen 921220
Bug #921220 {Done: Gianfranco Costamagna } [xchat] 
xchat stops autoconnecting, complaining about "%U" and "host unknown", broken 
.desktop entry ?
Bug reopened
Ignoring request to alter fixed versions of bug #921220 to the same values 
previously set
> retitle 921220 xchat.desktop makes invalid use of %U, breaks at least lxqt 
> and flwm
Bug #921220 [xchat] xchat stops autoconnecting, complaining about "%U" and 
"host unknown", broken .desktop entry ?
Changed Bug title to 'xchat.desktop makes invalid use of %U, breaks at least 
lxqt and flwm' from 'xchat stops autoconnecting, complaining about "%U" and 
"host unknown", broken .desktop entry ?'.
> affects 921220 + lxqt flwm
Bug #921220 [xchat] xchat.desktop makes invalid use of %U, breaks at least lxqt 
and flwm
Added indication that 921220 affects lxqt and flwm
> severity 921220 grave
Bug #921220 [xchat] xchat.desktop makes invalid use of %U, breaks at least lxqt 
and flwm
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#945595: New mpv in sid breaks smplayer

[Diederik de Haas]

On Wed, 27 Nov 2019 17:17:32 +0100 Alf Gaida  wrote:
> new mpv 0.30* don't play well with smplayer in sid - new 19.10.* will solve
> that problem.
> 
> No action needed right now, will work on it.

Salsa shows as latest commit "prepare to upload" (of version 19.10.2).
Why hasn't it been uploaded already?

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

Bug#946183: Should fusionforge be removed?

[Moritz Muehlenhoff]

Source: fusionforge
Severity: serious

There hasn't been an upload since two years and fusionforge missed the last two
stable releases and has gathered five RC bugs at this point. Should it be 
removed?

Cheers,
Moritz

Bug#945328: marked as done (pyzmq ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 21:20:01 +
with message-id 
and subject line Bug#945328: fixed in pyzmq 17.1.2-4
has caused the Debian Bug report #945328,
regarding pyzmq ftbfs in unstable
to be marked as done.

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

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


-- 
945328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyzmq
Version: 17.1.2-3
Severity: serious
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

pyzmq ftbfs in unstable, needing a patch from 18.1.  Please could you also relax
some timing conditions for tests seen on non-amd64 architectures?

patches at
https://patches.ubuntu.com/p/pyzmq/pyzmq_17.1.2-3ubuntu5.patch

[..]
=== FAILURES ===
__ TestAsyncIOSocket.test_recv_json_cancelled __

self = 

def test_recv_json_cancelled(self):
@asyncio.coroutine
def test():
a, b = self.create_bound_pair(zmq.PUSH, zmq.PULL)
f = b.recv_json()
assert not f.done()
f.cancel()
# cycle eventloop to allow cancel events to fire
yield from asyncio.sleep(0)
obj = dict(a=5)
yield from a.send_json(obj)
with pytest.raises(CancelledError):
recvd = yield from f
assert f.done()
# give it a chance to incorrectly consume the event
events = yield from b.poll(timeout=5)
assert events
yield from asyncio.sleep(0)
# make sure cancelled recv didn't eat up event
f = b.recv_json()
recvd = yield from asyncio.wait_for(f, timeout=5)
assert recvd == obj
>   self.loop.run_until_complete(test())

zmq/tests/asyncio/_test_asyncio.py:152:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <_UnixSelectorEventLoop running=False closed=True debug=False>
future = .test() done, defined
at
/<>/.pybuild/cpython3_3.8/build/zmq/tests/asyncio/_test_asyncio.py:131>>

def run_until_complete(self, future):
"""Run until the Future is done.

If the argument is a coroutine, it is wrapped in a Task.

WARNING: It would be disastrous to call run_until_complete()
with the same coroutine twice -- it would wrap it in two
different Tasks and that can't be good.

Return the Future's result, or raise its exception.
"""
self._check_closed()

new_task = not futures.isfuture(future)
future = tasks.ensure_future(future, loop=self)
if new_task:
# An exception is raised if the future didn't complete, so there
# is no need to log the "destroy pending task" message
future._log_destroy_pending = False

future.add_done_callback(_run_until_complete_cb)
try:
self.run_forever()
except:
if new_task and future.done() and not future.cancelled():
# The coroutine raised a BaseException. Consume the exception
# to not log a warning, the caller doesn't have access to the
# local task.
future.exception()
raise
finally:
future.remove_done_callback(_run_until_complete_cb)
if not future.done():
raise RuntimeError('Event loop stopped before Future completed.')

>   return future.result()
E   asyncio.exceptions.CancelledError
[..]
 1 failed, 232 passed, 11 skipped, 88 warnings in 33.62 seconds 
Task was destroyed but it is pending!
task: >/.pybuild/cpython3_3.8/build/zmq/auth/asyncio/__init__.py:25>
wait_for=>
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8/build; python3.8 -m pytest -v
--ignore=zmq/tests/test_auth.py --ignore=zmq/tests/test_security.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.8 3.7"
--test-pytest returned exit code 13
make[1]: *** [debian/rules:42: override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: pyzmq
Source-Version: 17.1.2-4

We believe that the bug you reported is fixed in the latest version of
pyzmq, 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 945...@bugs.debian.

Bug#927137: src:tumgreyspf: Please port to python3 or remove

[Moritz Mühlenhoff]

On Sat, Aug 24, 2019 at 02:07:26AM -0400, Scott Kitterman wrote:
> On Mon, 15 Apr 2019 09:01:29 -0400 Scott Kitterman  
> wrote:
> > Package: src:tumgreyspf
> > Version: 1.36-4.1
> > Severity: important
> > 
> > Python2.7 will go out of upstream security support during the Bullseye
> > development cycle.  It is not safe to assume it will be included in the
> > next release, so if you want to be sure tumgreyspf can stay in Debian, 
> please
> > port it to python3.
> > 
> > Alternately, it's close to 8 years without a new release and there are
> > certainly alternatives for SPF checking and greylisting.  Removal might be 
> in
> > order.
> > 
> > Personally, I want to remove some packages I maintain, particularly python-
> > ipaddr, which tumgreyspf depends on (indirectly via python-spf - which I 
> will
> > change to python3 only) during the Bullseye cycle, regardless of what
> > happens to python2.7, so please update (python3 includes the ipaddress 
> module,
> > which was developed from ipaddr, in the standard library).
> 
> Bumping to serious since python2 removals are going on in earnest and this 
> will need to be ported or removed soon.

Thomas,
tumgreyspf seems dead upstream, the last commit on Github is from April 2015,
should we remove it from the archive?

Cheers,
Moritz

Bug#946181: knot-resolver: CVE-2019-19331

[Salvatore Bonaccorso]

Source: knot-resolver
Version: 3.2.1-3
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for knot-resolver.

CVE-2019-19331[0], but see [1] for more details.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19331
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19331
[1] https://www.openwall.com/lists/oss-security/2019/12/04/4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc

[Synthea]

Package: lxcfs
Version: 2.0.7-1+deb9u1
Severity: grave

Here's lxc log:

  lxc-start 20191204112931.787 INFO lxc_cgroup - 
cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for debian-test
  lxc-start 20191204112931.790 ERRORlxc_cgfs - 
cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable mount point 
for cgroup hierarchy 11 while trying to create cgroup.
  lxc-start 20191204112931.802 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user/root/0
  lxc-start 20191204112931.807 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user/root
  lxc-start 20191204112931.808 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user
  lxc-start 20191204112931.808 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete 
/sys/fs/cgroup/systemd//user.slice/user-135.slice/session-1.scope
  lxc-start 20191204112931.808 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user.slice/user-135.slice
  lxc-start 20191204112931.808 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete 
/sys/fs/cgroup/systemd//user.slice/user-0.slice/session-c1.scope
  lxc-start 20191204112931.809 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user.slice/user-0.slice
  lxc-start 20191204112931.817 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete 
/sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-2.scope
  lxc-start 20191204112931.817 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user.slice/user-1000.slice
  lxc-start 20191204112931.817 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd//user.slice
  lxc-start 20191204112931.817 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Device or resource busy - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/systemd/
  lxc-start 20191204112931.817 ERRORlxc_start - start.c:lxc_spawn:1108 
- Failed creating cgroups.
  lxc-start 20191204112931.857 INFO lxc_conf - 
conf.c:lxc_delete_network:3015 - Removed interface "(null)" with index 18.
  lxc-start 20191204112931.883 WARN lxc_conf - 
conf.c:lxc_delete_network:3038 - Failed to remove "vethXD8GPK" from host: 
Invalid argument.
  lxc-start 20191204112931.883 WARN lxc_monitor - 
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No 
such file or directory.
  lxc-start 20191204112931.883 ERRORlxc_start - 
start.c:__lxc_start:1346 - Failed to spawn container "debian-test".
  lxc-start 20191204112931.884 WARN lxc_monitor - 
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No 
such file or directory.
  lxc-start 20191204112931.884 WARN lxc_monitor - 
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No 
such file or directory.
  lxc-start 20191204112931.884 INFO lxc_conf - 
conf.c:run_script_argv:424 - Executing script 
"/usr/share/lxcfs/lxc.reboot.hook" for container "debian-test", config section 
"lxc".
  lxc-start 20191204112932.401 ERRORlxc_start_ui - 
tools/lxc_start.c:main:366 - The container failed to start.
  lxc-start 20191204112932.401 ERRORlxc_start_ui - 
tools/lxc_start.c:main:370 - Additional information can be obtained by setting

--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-5-amd64

Debian Release: 9.11
  500 oldstable-updates deb.debian.org 
  500 oldstable   security.debian.org
  500 oldstable   deb.debian.org 
  100 stretch-backports deb.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libc6(>= 2.17) | 
libfuse2  (>= 2.6) | 
init-system-helpers (>= 1.18~) | 
lsb-base(>= 3.0-6) | 


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#946021: marked as done (qtpass: Invoking results in SegFault)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 20:50:59 +
with message-id 
and subject line Bug#946021: fixed in qtpass 1.3.2-1
has caused the Debian Bug report #946021,
regarding qtpass: Invoking results in SegFault
to be marked as done.

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

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


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

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: qtpass: Invoking results in SegFault
Bcc: Scott Jacobs 
Message-ID: 
<157533667450.3876.7878626174146484422.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 02 Dec 2019 20:31:14 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

Invoking qtpass from the menu results in nothing happening.

Invoking from the terminal results in:
~$ qtpass
Segmentation fault

Invoking with gdb does not result in SegFault, but also exits without bringing
up the program.
bt yields nothing except "No stack"

=
~$ gdb qtpass
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from qtpass...
Reading symbols from /usr/lib/debug/.build-
id/3c/f1d9ba416482bc8a78d951a09d69c5bf14778e.debug...
(gdb) run
Starting program: /usr/bin/qtpass
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x724c6700 (LWP 2904)]
[New Thread 0x715cb700 (LWP 2905)]
[Thread 0x724c6700 (LWP 2904) exited]
[Thread 0x715cb700 (LWP 2905) exited]
[Inferior 1 (process 2900) exited normally]
(gdb) bt
No stack.
(gdb) quit
=



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

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

Versions of packages qtpass depends on:
ii  libc6   2.29-2
ii  libgcc1 1:8.3.0-6
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-4
ii  libqt5network5  5.11.3+dfsg1-4
ii  libqt5svg5  5.11.3-3
ii  libqt5widgets5  5.11.3+dfsg1-4
ii  libstdc++6  9.2.1-8
ii  pass1.7.3-2

Versions of packages qtpass recommends:
ii  pass-extension-otp  1.2.0-1
ii  pwgen   2.08-2

Versions of packages qtpass suggests:
ii  git  1:2.24.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtpass
Source-Version: 1.3.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 21:19:39 +0100
Source: qtpass
Architecture: source
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Philip Rinn 
Changed-By: Philip Rinn 
Closes: 946021
Changes:
 qtpass (1.3.2-1) unstable; urg

Bug#943042: gitso: Python2 removal in sid/bullseye

[Scott Talbert]

On Wed, 4 Dec 2019, Florian Schlichting wrote:


The package doesn't look all that complicated.  I can take a stab at trying
to port it to Python 3.  If I get it working, perhaps I can ask you to test
it?


that would be awesome! I can definitely do the testing.


I submitted a merge request on salsa:
https://salsa.debian.org/debian/gitso/merge_requests/2

Let me know if you run into any problems or have any comments.

Scott

Bug#944821: marked as done (Unhandled (and undocumented) directory to symlink (and vice versa) change breaks on upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 18:53:51 +
with message-id 
and subject line Bug#944821: fixed in popper.js 1.14.6+ds2-3
has caused the Debian Bug report #944821,
regarding Unhandled (and undocumented) directory to symlink (and vice versa) 
change breaks on upgrade
to be marked as done.

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

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


-- 
944821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: popper.js
Version: 1.14.6+ds2-2
Severity: serious

The /usr/share/javascript/popper.js proper directory became a symlink in
the latest version, but dpkg does not support it, and it wasn’t handled
in maintainer scripts (nor documented in d/changelog).

Upgrading from 1.14.6+ds2-2 to 1.14.6+ds2-1 ends up with an empty
directory.

dpkg-maintscript-helper(1) should be helpful.

Regards

David

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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: popper.js
Source-Version: 1.14.6+ds2-3

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated popper.js package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 19:19:38 +0100
Source: popper.js
Architecture: source
Version: 1.14.6+ds2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 944821
Changes:
 popper.js (1.14.6+ds2-3) unstable; urgency=medium
 .
   * Add libjs-popper.js.maintscript to manage dir change to link
 (Closes: #944821)
Checksums-Sha1: 
 6c43d84778214766a77f95f2851c8e1040ecbcfd 2040 popper.js_1.14.6+ds2-3.dsc
 d9f0966386d57eb54b564864b4716dbe18bbfe7a 4328 
popper.js_1.14.6+ds2-3.debian.tar.xz
Checksums-Sha256: 
 4f605f115315994f98adeaf9b6086fe1a997d68dd074f9d328b2e87abf986108 2040 
popper.js_1.14.6+ds2-3.dsc
 310fac2e7a6a148e9d2482f00973a7b56bbe4f8b0350c1cbdc31903c6c5b1382 4328 
popper.js_1.14.6+ds2-3.debian.tar.xz
Files: 
 27a2d8cd5d8370051b554e4976ca681c 2040 javascript optional 
popper.js_1.14.6+ds2-3.dsc
 7809c5a57dd0a5afe6b9762e5cf4fbd0 4328 javascript optional 
popper.js_1.14.6+ds2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl3n+UEACgkQ9tdMp8mZ
7ulwhg//YHp/CtDRsEBrPTCLHZEhX1k3XZr6kibfS16rhTkDC12Z41H1DqzVRkF1
hzbWwteslLkzNjXwpBD6bhWV57Pk72dZ8CKtrMKaVUKfD3I9gyAz3XNaI2ccTiSE
z1twY2AE6cY8ScLmcNWJvKjxWiTlwcHwqg5Uu1X1U8taiP1dBzy6hqUMEzIwRnev
eChWmQoij8vYKlqJ+7rjO7L7F5YMfTOB5UgkSVxzrcZhzMWiZ+2sMUfpF9pmKIY8
Xdq8wMJ/mj0OkeDtD+KtNpE6URW+zfpUcvHvH2Ogk2HWMrtBNai2h6UwhqN58qYa
+HjlzSbowBVFlT4MAYHNZ6sDPBvanT4oiUjSNE1i/V62DmBcjBq9WMyyK2ld8bf9
PYHhIp/vHUHA3Qhu8gfFTZ3kkAP9umNRO1uqCJ5CeVkN4TkarDMkFy1xpPQb2Hbl
Cgyaqk0RU1iBrjBhD55pvS3BhkAOrXBcYX29tbIRS0TywADrzaZTFaOfbiZWXguW
qGKbiAOu98XyETiN8CHaX4y0jRuDnc3C72jfBgE27hRbggZv2XdwQMyTxRKgXxEx
oZexjSB6CyejvIQ0a2/3DKDCc1o8JNGwqAF8N+QG+NQPhSKIr2gZB+GxCQ/RoLdG
kPOXGh8RATLj31+eCqCNWB/bYry/yUua/nr827g3Q4OcdrS9zow=
=PV7T
-END PGP SIGNATURE End Message ---

Processed: severity of 918163 is serious

[Debian Bug Tracking System]

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

> severity 918163 serious
Bug #918163 [xul-ext-sieve] Broken in Stretch
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#918163: Broken in Stretch

[Carsten Schoenert]

Control: tags -1 stretch
Control: tags -1 buster
Control: tags -1 sid
Control: severity - 1 serious

Hi, and once again this package isn't working anymore due the API change
for AddOns that are introduced by Thunderbird 68.x

Thunderbird now requires AddOns that are build as webextension.

So far I've seen this package needs to get updated to version 0.3.1 to
get it working in Thunderbird 68.x.
This will requiring changes to the Debian packaging.

Examples how the packaging needs to be done to fit the requirements to
get system wide installed Thunderbird AddOns recognized by Thunderbird
can be found on these packages e.g.

https://salsa.debian.org/webext-team/compactheader/tree/debian/sid/debian
https://salsa.debian.org/webext-team/tbsync/tree/debian/experimental/debian

Please also move over the binary package name to webext-sieve-extension
as this was discussed and wantied naming schema within the Mozilla
Packaging Team.

This will require to make the old binary name a transitional package.

If you want or need help please say so. Thanks!

Regards
Carsten

Processed (with 1 error): Re: Bug#918163: Broken in Stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 stretch
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) stretch.
> tags -1 buster
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) buster.
> tags -1 sid
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) sid.
> severity - 1 serious
Unknown command or malformed arguments to command.


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

Processed: Bug#944821 marked as pending in popper.js

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944821 [src:popper.js] Unhandled (and undocumented) directory to symlink 
(and vice versa) change breaks on upgrade
Added tag(s) pending.

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

Bug#944821: marked as pending in popper.js

[Xavier Guimard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/popper.js/commit/5289f4d9c1def2d2ac1dfef1704c7cd8c944544a


Add libjs-popper.js.maintscript to manage dir change to link

Closes: #944821


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944821

Bug#944242: marked as done (fix build & test issues with Python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 17:35:41 +
with message-id 
and subject line Bug#944242: fixed in python-biopython 1.75+dfsg-1
has caused the Debian Bug report #944242,
regarding fix build & test issues with Python 3.8
to be marked as done.

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

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


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

Package: src:python-biopython
Version: 1.73+dfsg-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

please find patches to build and run the tests with Python 3.8. All patches 
taken from upstream except for

https://github.com/biopython/biopython/issues/2325


diff -Nru python-biopython-1.73+dfsg/debian/changelog python-biopython-1.73+dfsg/debian/changelog
--- python-biopython-1.73+dfsg/debian/changelog	2019-01-11 22:23:52.0 +
+++ python-biopython-1.73+dfsg/debian/changelog	2019-11-06 13:31:00.0 +
@@ -1,3 +1,23 @@
+python-biopython (1.73+dfsg-1ubuntu4) focal; urgency=medium
+
+  * Pull some Python 3.8 fixes from upstream.
+
+ -- Matthias Klose   Wed, 06 Nov 2019 14:31:00 +0100
+
+python-biopython (1.73+dfsg-1ubuntu2) focal; urgency=medium
+
+  * No-change rebuild to build with python3.8.
+
+ -- Matthias Klose   Fri, 18 Oct 2019 18:42:37 +
+
+python-biopython (1.73+dfsg-1ubuntu1) disco; urgency=medium
+
+  * debian/patches/test_phenotype_fit-ppc64el.patch:
+- reduce precision on one test, per upstream recommendation at:
+  https://github.com/biopython/biopython/issues/1945
+
+ -- Adam Conrad   Mon, 04 Mar 2019 12:21:32 -0700
+
 python-biopython (1.73+dfsg-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru python-biopython-1.73+dfsg/debian/control python-biopython-1.73+dfsg/debian/control
--- python-biopython-1.73+dfsg/debian/control	2019-01-11 22:23:52.0 +
+++ python-biopython-1.73+dfsg/debian/control	2019-03-04 19:21:32.0 +
@@ -1,5 +1,6 @@
 Source: python-biopython
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Charles Plessy ,
Andreas Tille 
 Section: python
diff -Nru python-biopython-1.73+dfsg/debian/patches/2146.diff python-biopython-1.73+dfsg/debian/patches/2146.diff
--- python-biopython-1.73+dfsg/debian/patches/2146.diff	1970-01-01 00:00:00.0 +
+++ python-biopython-1.73+dfsg/debian/patches/2146.diff	2019-11-06 13:31:00.0 +
@@ -0,0 +1,34 @@
+--- a/Bio/SeqFeature.py
 b/Bio/SeqFeature.py
+@@ -1533,6 +1533,11 @@ class ExactPosition(int, AbstractPositio
+ """Return a representation of the ExactPosition object (with python counting)."""
+ return str(int(self))
+ 
++# Must define this on Python 3.8 onwards because we redefine __repr__
++def __str__(self):
++"""Return a representation of the ExactPosition object (with python counting)."""
++return str(int(self))
++
+ def __repr__(self):
+ """Represent the ExactPosition object as a string for debugging."""
+ return "%s(%i)" % (self.__class__.__name__, int(self))
+@@ -2067,8 +2072,7 @@ class OneOfPosition(int, AbstractPositio
+ for position in self.position_choices:
+ out += "%s," % position
+ # replace the last comma with the closing parenthesis
+-out = out[:-1] + ")"
+-return out
++return out[:-1] + ")"
+ 
+ def _shift(self, offset):
+ """Return a copy of the position object with its location shifted (PRIVATE)."""
+@@ -2094,8 +2098,7 @@ class PositionGap(object):
+ 
+ def __str__(self):
+ """Return a representation of the PositionGap object (with python counting)."""
+-out = "gap(%s)" % self.gap_size
+-return out
++return "gap(%s)" % self.gap_size
+ 
+ 
+ if __name__ == "__main__":
diff -Nru python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff
--- python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff	1970-01-01 00:00:00.0 +
+++ python-biopython-1.73+dfsg/debian/patches/dict-iterate.diff	2019-11-06 13:31:00.0 +
@@ -0,0 +1,11 @@
+--- a/Bio/SubsMat/__init__.py
 b/Bio/SubsMat/__init__.py
+@@ -207,7 +207,7 @@ class SeqMat(dict):
+ 
+ def _correct_matrix(self):
+ """Sort key tuples (PRIVATE)."""
+-for key in self:
++for key in dict(self):
+ if key[0] > key[1]:
+ self[(key[1], key[0])] = self[key]

Bug#944242: Test issues with BioPython 1.75

[Peter Cock]

Yes, ignore that one please.

That test has since been disabled (and replaced with a more robust one).
We eventually traced test_chapter_align_line_02819 failing on 32 bit
systems with a different overflow error:

https://github.com/biopython/biopython/pull/2297

Thanks,

Peter

On Wed, Dec 4, 2019 at 4:22 PM Andreas Tille  wrote:
>
> On Wed, Dec 04, 2019 at 01:55:26PM +, Peter Cock wrote:
> > Good. If you are still missing Tests/Fasta/flowers.pro.gz that's odd,
> > since it was in the official tar ball:
> >
> > https://files.pythonhosted.org/packages/33/55/becf2b99556588d22b542f3412990bfc79b674e198d9bc58f7bbc333439e/biopython-1.75.tar.gz
>
> Arghh again.  The test script is unzipping all files before running the
> test since in the Debian doc dir most files are gzipped.  After gzipping
> it again this test is fine.
>
> So the only remaining issue is:
>
> ==
> ERROR: test_doctests (test_Tutorial.TutorialTestCase)
> Run tutorial doctests.
> --
> Traceback (most recent call last):
>   File "/tmp/autopkgtest.hiPio2/autopkgtest_tmp/Tests/test_Tutorial.py", line 
> 260, in test_doctests
> (len(failures), ", ".join(failures)))
> ValueError: 1 Tutorial doctests failed: test_chapter_align_line_02819
>
> --
> Ran 194 tests in 204.479 seconds
>
>
> and I think we agreed that I'll ignore this test.
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de

Bug#945411: pyfai fails tests with Python 3.8

[Drew Parsons]

Package: pyfai
Version: 0.18.0+dfsg1-3
Followup-For: Bug #945411

"pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close 
resident module'"

That suggests pocl is not yet built against python3.8

Bug#945411: pyfai: 1

[Drew Parsons]

Package: pyfai
Followup-For: Bug #945411

On the other hand, python3-pyopencl is indeed built against python3.8.
So need to dig deeper.

Bug#946146: marked as done (Tests are failing)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 16:49:53 +
with message-id 
and subject line Bug#946146: fixed in astlib 0.11.3-1
has caused the Debian Bug report #946146,
regarding Tests are failing
to be marked as done.

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

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


-- 
946146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ginga
Version: 3.0.0-1

The tests started failing in unstable
https://ci.debian.net/packages/g/ginga/unstable/amd64/

E   ginga.util.wcsmod.common.WCSError: WCS projection has 3 dimensions, 
so expected 2 (an Nx3 array and the origin argument) or 4 arguments (the 
position in each dimension, and the origin argument). Instead, 3 arguments were 
given.

/usr/lib/python3/dist-packages/ginga/util/wcsmod/wcs_astlib.py:76: WCSError


--- End Message ---
--- Begin Message ---
Source: astlib
Source-Version: 0.11.3-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 17:09:52 +0100
Source: astlib
Architecture: source
Version: 0.11.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 946146
Changes:
 astlib (0.11.3-1) unstable; urgency=medium
 .
   * New upstream version 0.11.3. Closes: #946146
Checksums-Sha1:
 f2086d0d33edd6d5ef79ad5771f9f644ecf5e20f 2032 astlib_0.11.3-1.dsc
 abaf2f27a9d1da5e1e7084ddb0bae92248870b41 742413 astlib_0.11.3.orig.tar.gz
 24f682d271a1a19a34db6d213ca7c2c1be27710e 3708 astlib_0.11.3-1.debian.tar.xz
Checksums-Sha256:
 48277de92b591d5f466c0b7f9cfd4e7899068fce227fa6acbf5192b9f1cde568 2032 
astlib_0.11.3-1.dsc
 003447812e19966f0e7e3dc9ccaedfaff76fe4a452e311bde5d05f6d4fa3e3af 742413 
astlib_0.11.3.orig.tar.gz
 8853294b29645358e2e9c949bc81410b1b022db22cb6324be52fef8cc711dcd3 3708 
astlib_0.11.3-1.debian.tar.xz
Files:
 9c954190d8fe7c31b888a1e3a7ce7de5 2032 python optional astlib_0.11.3-1.dsc
 56b3d11ffed2cab4f63ffcc13bbf1f45 742413 python optional 
astlib_0.11.3.orig.tar.gz
 47d2f3ab701c44dc0bdcd344794ae9f1 3708 python optional 
astlib_0.11.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl3n2xUACgkQmk9WvbkO
GL27ww/+MPN0H0W9T49bsW+HDz6fBiVooxEt957D2R+0BDy67khnxVvfzuJRTkKE
OOaxcLgu/Nze/Nslv5t8Rctwh2ycInFyy7g/iYejPTiVsnb0ksmTNmQYo0nDZny/
8OjFJfzK4S5q3Tz5JDa7hDRoTrJnN0hkZ4lUhdnDC/iBGA2CjGgwKBJYzGVJJ509
m7gHV2OfWX9foVaK/HoA6vBTfnIcfPcHrtV9qAPMyagLb6ANy+VJGqXH+mt2MZ/I
jDfyHpTQxOu2bnTS6bslheh2KlBo5JQp00CVeh5T8JdDwOnPpE6SJ0VfoiCmnPZq
pjAVoyoTUU4tsnlSElgNHpjTOlQ+km3Gz8UCT5IXsj436+vdxH0UXY/4zHEWLeu2
TEmU+LY/igtNH7zkIy3/oo/pJjcNA/gcVThoPPQHXbWKmgM/3jLj29k0uAy9vbUM
vTm+aKYNT/WFVNC/e9cljqXSfmc6j9JgShtL00Ph+gx0A5TKhPfQLoV2kIXy0qql
TLL502iPekLJETwFxSH1s6ZNpCv6JVrU/wtsc1WcixnmPgKIAtpfXyq48EDEJCZQ
DG0kDItYnyjVbrsOZCVC6tYJA7582nZ0LBzrqhJnh/HNweKPtmVIFRcGQ/MmID4d
dpCebP1azLH8MYhXWGVtIfDf4HLnjgI66+BqqUxbc57Hp77Pp+8=
=Y/+x
-END PGP SIGNATURE End Message ---

Bug#943042: gitso: Python2 removal in sid/bullseye

[Florian Schlichting]

Hi Scott,

> The package doesn't look all that complicated.  I can take a stab at trying
> to port it to Python 3.  If I get it working, perhaps I can ask you to test
> it?

that would be awesome! I can definitely do the testing.

Florian

Bug#944242: Test issues with BioPython 1.75

[Andreas Tille]

On Wed, Dec 04, 2019 at 01:55:26PM +, Peter Cock wrote:
> Good. If you are still missing Tests/Fasta/flowers.pro.gz that's odd,
> since it was in the official tar ball:
> 
> https://files.pythonhosted.org/packages/33/55/becf2b99556588d22b542f3412990bfc79b674e198d9bc58f7bbc333439e/biopython-1.75.tar.gz

Arghh again.  The test script is unzipping all files before running the
test since in the Debian doc dir most files are gzipped.  After gzipping
it again this test is fine.

So the only remaining issue is:

==
ERROR: test_doctests (test_Tutorial.TutorialTestCase)
Run tutorial doctests.
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.hiPio2/autopkgtest_tmp/Tests/test_Tutorial.py", line 
260, in test_doctests
(len(failures), ", ".join(failures)))
ValueError: 1 Tutorial doctests failed: test_chapter_align_line_02819

--
Ran 194 tests in 204.479 seconds


and I think we agreed that I'll ignore this test.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#943042: gitso: Python2 removal in sid/bullseye

[Scott Talbert]

On Wed, 4 Dec 2019, Florian Schlichting wrote:


Do you have any plans to port gitso to Python 3?

If not, I will probably just convert this to an RM request as it seems gitso
is unmaintained upstream for many years.


I have in fact started to look into porting gitso to Python 3, but
haven't spent enough time on it to be able to say how long it will take
or if it will be doable with my (very limited) python skills. However I
still use gitso occasionally and would love to keep it around.

Do you have a time frame until such a project would have to be
completed? I was of the impression that I had until the bullseye
release, but the Python 2 removal seems to be progressing with a lot of
energy lately...


Hey Florian,

Yes, the target for Python 2 removal is bullseye release, but since the 
removal is going to take a long time, work is progressing steadily.  Since 
gitso is a 'leaf' Python 2 package, that's why I poked this bug report.


The package doesn't look all that complicated.  I can take a stab at 
trying to port it to Python 3.  If I get it working, perhaps I can ask you 
to test it?


Scott

Bug#943042: gitso: Python2 removal in sid/bullseye

[Florian Schlichting]

Hi Scott,

> Do you have any plans to port gitso to Python 3?
> 
> If not, I will probably just convert this to an RM request as it seems gitso
> is unmaintained upstream for many years.

I have in fact started to look into porting gitso to Python 3, but
haven't spent enough time on it to be able to say how long it will take
or if it will be doable with my (very limited) python skills. However I
still use gitso occasionally and would love to keep it around.

Do you have a time frame until such a project would have to be
completed? I was of the impression that I had until the bullseye
release, but the Python 2 removal seems to be progressing with a lot of
energy lately...

Florian

Processed: reassign 946161 to src:dia, forcibly merging 945876 946161

[Debian Bug Tracking System]

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

> reassign 946161 src:dia
Bug #946161 [dia] dia: CVE-2019-19451: Endless loop on filenames with invalid 
encoding can be used for denial-of-service
Bug reassigned from package 'dia' to 'src:dia'.
No longer marked as found in versions dia/0.97.3+git20160930-8.1.
Ignoring request to alter fixed versions of bug #946161 to the same values 
previously set
> forcemerge 945876 946161
Bug #945876 [src:dia] dia: CVE-2019-19451
Bug #946161 [src:dia] dia: CVE-2019-19451: Endless loop on filenames with 
invalid encoding can be used for denial-of-service
Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/dia/issues/428'.
Severity set to 'important' from 'critical'
Marked as found in versions dia/0.97.3+git20160930-8.2, 
dia/0.97.3+git20160930-8.1, and dia/0.97.3+git20160930-6.
Merged 945876 946161
> thanks
Stopping processing here.

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

Bug#946061: landslide: FTBFS; Package should be removed instead of being made into compat pkg

[Andrej Shadura]

Hi,

On Wed, 4 Dec 2019 at 16:03, Boyuan Yang  wrote:
> I have no idea why the package would have to go through NEW. Removing package
> does not need to go throught NEW and it's much faster (usually needs only 1 or
> 2 days).

No, I’m talking about a compat package in darkslide. I still want it
to be a separate binary package, which means I’d have to add it to
darkslide, which I don’t (yet) want to do.

-- 
Cheers,
  Andrej

Bug#946061: landslide: FTBFS; Package should be removed instead of being made into compat pkg

[Boyuan Yang]

在 2019-12-04三的 15:00 +0100，Andrej Shadura写道：
> Hi,
> 
> On Tue, 3 Dec 2019 at 15:54, Boyuan Yang  wrote:
> > Currently package landslide FTBFS in Sid. I noticed that it was just made
> > into
> > a compatibility package with nothing inside. This is unnecessary, plus
> > that
> > current setup actually fails to build from source.
> > 
> > Since python-landslide has no reverse dependency and no reverse build-
> > dependency, please consider removing it from the Debian archive instead of
> > making a compatibility package. Please let me know if that works for you.
> 
> I’d like to avoid going through NEW needlessly. I will convert it at
> some point in future, but now just now yet.

Hi Andrej,

I have no idea why the package would have to go through NEW. Removing package
does not need to go throught NEW and it's much faster (usually needs only 1 or
2 days).

Or are you talking about uploading python3-landslide? In this case it should
be pushed into the NEW queue sooner rather than later since the NEW queue is
always being processed slowly. We can make uploads onto Experimental with the
new package and let it stay in the NEW queue. This is harmless since the Sid
uploads are not affected by experimental/NEW at all.

-- 
Thanks,
Boyuan Yang

Bug#946061: marked as done (landslide: FTBFS; Package should be removed instead of being made into compat pkg)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 14:55:43 +
with message-id 
and subject line Bug#946061: fixed in landslide 1.1.3+0
has caused the Debian Bug report #946061,
regarding landslide: FTBFS; Package should be removed instead of being made 
into compat pkg
to be marked as done.

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

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


-- 
946061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: landslide
Version: 1.1.3-1
Severity: grave

Currently package landslide FTBFS in Sid. I noticed that it was just made into
a compatibility package with nothing inside. This is unnecessary, plus that
current setup actually fails to build from source.

Since python-landslide has no reverse dependency and no reverse build-
dependency, please consider removing it from the Debian archive instead of
making a compatibility package. Please let me know if that works for you.

-- 
Best Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: landslide
Source-Version: 1.1.3+0

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 04 Dec 2019 14:01:08 +
Source: landslide
Architecture: source
Version: 1.1.3+0
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 946061
Changes:
 landslide (1.1.3+0) unstable; urgency=medium
 .
   * Convert to a dummy native package (Closes: #946061).
Checksums-Sha1:
 0eb99276c2344847a260c8f759462f572ea0c775 1357 landslide_1.1.3+0.dsc
 93977e2b1fba8b7c184177dea2d5c0d2cb2143f7 2504 landslide_1.1.3+0.tar.xz
Checksums-Sha256:
 33d9e49ef96d9735d3bc33c4eeba6c09f5a9d356e8084f21c7cd17416bfadc1e 1357 
landslide_1.1.3+0.dsc
 cff5eb4dd84f4fb067f74389cf89c4191f07a818fffad336685f6bcabea4ca44 2504 
landslide_1.1.3+0.tar.xz
Files:
 bfa5cee85ae7b85c0f5762e982d9c384 1357 oldlibs optional landslide_1.1.3+0.dsc
 6bd8163d00110d44841a47232d74592f 2504 oldlibs optional landslide_1.1.3+0.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl3nvOUACgkQXkCM2RzY
OdJO0wf+OllssleY0in7BFat80A7HjrEstcf2E29jm2XmIFoADvMyUwy1PveQINJ
X7sOFDSnESliSL3uEaNbaUmppwMwHjfjgw+LVfph8mJjnUZHEOtB0zOlPk/8qXOp
pH2iZNxSrKCFUDAUCeyVocTt61f6tBlrUQjt3+CAOW4wZ3mlSaidL8no1NA//VlA
dU4nBpkbuFPY5Dc6NVIolHTGsZikdA9oIshqmB4OnzaqIzP8mu1fLq2hWvnY56oE
LEDHz3uQxUuueBOOg4uasn1k5MgLdVpIXO6uo9oKxEymQEwJ1FYDQjjolmhdlGgN
PJp6xrLeMa0+s3NpRovpRUXPfzv2Ww==
=GyEH
-END PGP SIGNATURE End Message ---

Bug#946161: dia: CVE-2019-19451: Endless loop on filenames with invalid encoding can be used for denial-of-service

[Nils Steinger]

Package: dia
Version: 0.97.3+git20160930-8.1
Severity: critical
Tags: security upstream
Justification: breaks the whole system

Dear Maintainer,

when GNOME Dia before 2019-11-27 is launched with a filename argument
that is not a valid codepoint in the current encoding, it enters an
endless loop, thus endlessly writing text to stdout.
(The filename can be for a nonexistent file.)

If this launch is from a thumbnailer service, this output will usually
be written to disk via the system's logging facility (potentially with
elevated privileges), thus filling up the disk and eventually rendering
the system unusable.

Further details are available in the upstream bugreport [1] and the CVE
description [2].

Upstream (the GNOME Dia developers) has not tagged any official release
versions since 2011 (0.97.2), so Debian currently ships a more recent
state as 0.97.3+git20160930-8.2.
The vulnerability was introduced after the release of 0.97.2, and is
contained in all 0.97.3+* versions in Debian.

Could you please package the current development version of Dia, or
apply the (one-line) patch [3], to fix this vulnerability?

Kind regards,
Nils Steinger

[1]: https://gitlab.gnome.org/GNOME/dia/issues/428
[2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19451
[3]: 
https://gitlab.gnome.org/GNOME/dia/commit/baa2df853f9fb770eedcf3d94c7f5becebc90bb9?merge_request_iid=50

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.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 dia depends on:
ii  dia-common   0.97.3+git20160930-8.1
ii  libart-2.0-2 2.3.21-4
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk2.0-0  2.24.32-3
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  libpangoft2-1.0-01.42.4-7~deb10u1
ii  libpng16-16  1.6.36-6
ii  libpython2.7 2.7.16-2+deb10u1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxslt1.1   1.1.32-2.2~deb10u1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages dia recommends:
ii  dia-shapes   0.6.0-3
ii  gsfonts-x11  0.26

dia suggests no packages.

-- no debconf information

Bug#946155: marked as done (libpam-fscrypt: PAM module config broken)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 14:50:07 +
with message-id 
and subject line Bug#946155: fixed in fscrypt 0.2.5-2
has caused the Debian Bug report #946155,
regarding libpam-fscrypt: PAM module config broken
to be marked as done.

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

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


-- 
946155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-fscrypt
Version: 0.2.4-2
Severity: grave
Justification: renders package unusable

Hi!

Apparently in the latest version (0.2.5-1) the path substitution was broken,
resulting in "PAM_INSTALL_PATH" being used instead of the library name
"pam_fscrypt.so".

This killed decryption triggered by PAM.



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

Kernel: Linux 5.2.0-2-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-fscrypt depends on:
ii  fscrypt   0.2.4-2
ii  libc6 2.29-3
ii  libpam0g  1.3.1-5

libpam-fscrypt recommends no packages.

libpam-fscrypt suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fscrypt
Source-Version: 0.2.5-2

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

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

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

Debian distribution maintenance software
pp.
Paride Legovini  (supplier of updated fscrypt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 13:57:04 +
Source: fscrypt
Architecture: source
Version: 0.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Paride Legovini 
Closes: 946155
Changes:
 fscrypt (0.2.5-2) unstable; urgency=medium
 .
   * The upstream libpam config file is now a template; compile it.
 (Closes: #946155)
   * Build-Depend on m4.
Checksums-Sha1:
 6b7d2837c61719866b6f2599adcfa34cda18f539 1967 fscrypt_0.2.5-2.dsc
 a9c63e21efe4b8af3bc72bf14a540373e95a293b 5260 fscrypt_0.2.5-2.debian.tar.xz
 a6478a70727066162685a312770a2a7f3f84594b 6457 fscrypt_0.2.5-2_amd64.buildinfo
Checksums-Sha256:
 924b5a7c87d82e9348d7c1c8ee777ca85de15b12534346dc5d7f07066e77f5d7 1967 
fscrypt_0.2.5-2.dsc
 833374927671a3c26d2bb8caba82a3a00691693280f36ac1d70180b0ddbf804e 5260 
fscrypt_0.2.5-2.debian.tar.xz
 895c16076ef2771a9845eabebab78565e8d8e854c5c224ef97794d9f13ea29c6 6457 
fscrypt_0.2.5-2_amd64.buildinfo
Files:
 b615f956fdf364bda92ef2a20cc902df 1967 admin optional fscrypt_0.2.5-2.dsc
 576495cd534cc673d9e990d44ea38515 5260 admin optional 
fscrypt_0.2.5-2.debian.tar.xz
 d983efba2b508451e25a5abf1c605052 6457 admin optional 
fscrypt_0.2.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEVhrVhe7XZpIbqN2W1lhhiD4BTbkFAl3nvPQSHHBsQG5pbnRo
Zmxvb3Iub3JnAAoJENZYYYg+AU255akH/3iH0xRsE+e6k1V4jrySmSSWtKgWzHWa
ID8q1EJ3+hCrImUwFlSqL4t9p7K8PNHzV2kc/OMuUczrA7jBxn727XQ+QcEOGcW7
iBTnZBNZbCK/IwSLNTAnY5ZxSCk3qe23f81n+HmfEv4dBS2d/rBL6m/JO5ZP5Y7d
dke7UF53xb6wdw+T6JR0fJcHHfSk5GjIqvFob3cbZp7KizIdfn9qZQyuDJz04Dcn
nZqTeGT7+RpZXChYhe8cyMMqGUJEhOrVnMCrfv7/3/Xibfbtm5SigNqWF2o225Zl
pi6TVIUyCPhx009AFx1SkHMI88qM7I3/1UU6awlnIDG93fbhMaLUUHA=
=wTg9
-END PGP SIGNATURE End Message ---

Bug#946155: marked as pending in fscrypt

[Paride Legovini]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/packages/fscrypt/commit/c5bf1c329d49ea8fdcaccb9f5907a67bb5452beb


The upstream libpam config file is now a template; compile it

Closes: #946155.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946155

Processed: Bug#946155 marked as pending in fscrypt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946155 [libpam-fscrypt] libpam-fscrypt: PAM module config broken
Added tag(s) pending.

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

Bug#946061: landslide: FTBFS; Package should be removed instead of being made into compat pkg

[Andrej Shadura]

Hi,

On Tue, 3 Dec 2019 at 15:54, Boyuan Yang  wrote:
> Currently package landslide FTBFS in Sid. I noticed that it was just made into
> a compatibility package with nothing inside. This is unnecessary, plus that
> current setup actually fails to build from source.
>
> Since python-landslide has no reverse dependency and no reverse build-
> dependency, please consider removing it from the Debian archive instead of
> making a compatibility package. Please let me know if that works for you.

I’d like to avoid going through NEW needlessly. I will convert it at
some point in future, but now just now yet.

-- 
Cheers,
  Andrej

Bug#944242: Test issues with BioPython 1.75

[Peter Cock]

Good. If you are still missing Tests/Fasta/flowers.pro.gz that's odd,
since it was in the official tar ball:

https://files.pythonhosted.org/packages/33/55/becf2b99556588d22b542f3412990bfc79b674e198d9bc58f7bbc333439e/biopython-1.75.tar.gz

Peter

On Tue, Dec 3, 2019 at 9:13 PM Andreas Tille  wrote:
>
> Hi Peter,
>
> On Mon, Dec 02, 2019 at 03:42:21PM +, Peter Cock wrote:
> > This was included in Biopython 1.74 and 1.75, yet your copy of 
> > Tests/test_psw.py
> > would seem to date from Biopython 1.73 or older.
> >
> > I suspect an old cached copy of the test folder is largely to blame?
>
> Arghhh, sorry for wasting your time.  The test examples are in
> python-biopython-doc package which I forgot to update on my local
> machine.  I just get:
>
> ==
> ERROR: test_gzip_fasta (test_SeqIO.TestZipped)
> Testing FASTA with gzip.
> --
> Traceback (most recent call last):
>   File "/tmp/autopkgtest.vFO6HI/autopkgtest_tmp/Tests/test_SeqIO.py", line 
> 156, in test_gzip_fasta
> with gzip.open("Fasta/flowers.pro.gz", mode) as handle:
>   File "/usr/lib/python2.7/gzip.py", line 34, in open
> return GzipFile(filename, mode, compresslevel)
>   File "/usr/lib/python2.7/gzip.py", line 94, in __init__
> fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
> IOError: [Errno 2] No such file or directory: 'Fasta/flowers.pro.gz'
>
> ==
>
>
> (now with the real data).
>
> Kind regards
>
>  Andreas.
>
> --
> http://fam-tille.de

Processed: notfound 944776 in prepair/0.7.1-3+b2, found 944776 in 0.7.1-3, tagging 944775, tagging 946114 ...

[Debian Bug Tracking System]

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

> notfound 944776 prepair/0.7.1-3+b2
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
The source prepair and version 0.7.1-3+b2 do not appear to match any binary 
packages
No longer marked as found in versions prepair/0.7.1-3+b2.
> found 944776 0.7.1-3
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
Marked as found in versions prepair/0.7.1-3.
> tags 944775 + sid bullseye
Bug #944775 [src:pprepair] FTBFS with CGAL 5.0
Added tag(s) sid and bullseye.
> tags 946114 + sid bullseye
Bug #946114 [src:crrcsim] FTFBS with CGAL 5.0 (NMU)
Added tag(s) sid and bullseye.
> notfound 946155 0.2.4-2
Bug #946155 [libpam-fscrypt] libpam-fscrypt: PAM module config broken
No longer marked as found in versions fscrypt/0.2.4-2.
> found 946155 0.2.5-1
Bug #946155 [libpam-fscrypt] libpam-fscrypt: PAM module config broken
Marked as found in versions fscrypt/0.2.5-1.
> tags 946039 + sid bullseye experimental
Bug #946039 [picprog] picport: Will crash with Linux 5.5 due to cli
Added tag(s) sid, experimental, and bullseye.
> tags 946068 + sid bullseye
Bug #946068 [src:lv2dynparam1] lv2dynparam1 FTCBFS: lv2core.pc not found
Added tag(s) bullseye and sid.
> tags 945931 + sid bullseye
Bug #945931 [src:haskell-crypto] haskell-crypto: Removal notice: broken and 
unmaintained
Added tag(s) bullseye and sid.
> fixed 945340 1.9.19
Bug #945340 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world: depends on no longer available firefox-esr-l10n-{as, en-za, 
mai, ml, or}
Marked as fixed in versions debian-parl/1.9.19.
> notfixed 945340 10.8.6
Bug #945340 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world: depends on no longer available firefox-esr-l10n-{as, en-za, 
mai, ml, or}
There is no source info for the package 'parl-desktop-world' at version 
'10.8.6' with architecture ''
Unable to make a source version for version '10.8.6'
No longer marked as fixed in versions 10.8.6.
> fixed 945340 boxer-data/10.8.6
Bug #945340 {Done: Jonas Smedegaard } [parl-desktop-world] 
parl-desktop-world: depends on no longer available firefox-esr-l10n-{as, en-za, 
mai, ml, or}
Marked as fixed in versions boxer-data/10.8.6.
> tags 945961 + sid bullseye
Bug #945961 [src:xz-utils] xz-utils: FTBFS: cannot stat 
'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'
Added tag(s) sid and bullseye.
> tags 946046 + sid bullseye
Bug #946046 [unison-all] unison-all should also depend on the old unison 
version, compatible with Debian 10
Added tag(s) bullseye and sid.
> tags 945989 - a11y
Bug #945989 [apngdis] apngdis producing blank images
Removed tag(s) a11y.
> tags 946061 + sid bullseye
Bug #946061 [src:landslide] landslide: FTBFS; Package should be removed instead 
of being made into compat pkg
Added tag(s) sid and bullseye.
> tags 945989 + buster bullseye sid
Bug #945989 [apngdis] apngdis producing blank images
Added tag(s) sid, buster, and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
944775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944775
944776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944776
945340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945340
945931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945931
945961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945961
945989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945989
946039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946039
946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046
946061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946061
946068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946068
946114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946114
946155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#946011: python-django: CVE-2019-19118

[Salvatore Bonaccorso]

Hi Chris,

On Tue, Dec 03, 2019 at 09:25:42PM +0100, Chris Lamb wrote:
> Dear Salvatore,
> 
> > > Security team, would you like an upload for stable?
> > 
> > As far I can see this issue has been introduced around 2.1 where the
> > search support for view permissions and a read-only admin support was
> > added.  […]
> 
> Upon further inspection that is my reading too. I was being overly-
> cautious in assuming that it was vulnerable without doing any checking
> first, thus leading to this noise (for which I apologise).
> 
> I have updated data/dla-needed.txt and data/CVE/list to match.

Thanks for double-checking and confirming!

Regards,
Salvatore

Bug#946155: libpam-fscrypt: PAM module config broken

[Paride Legovini]

Alex Hofbauer wrote on 04/12/2019:
> Package: libpam-fscrypt
> Version: 0.2.4-2
> Severity: grave
> Justification: renders package unusable
> 
> Hi!
> 
> Apparently in the latest version (0.2.5-1) the path substitution was broken,
> resulting in "PAM_INSTALL_PATH" being used instead of the library name
> "pam_fscrypt.so".
> 
> This killed decryption triggered by PAM.

Thanks Alex, I'll look into it today.

Paride

Bug#942235: marked as done (dask: autopkgtest needs update for new version of pytest)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 12:34:39 +
with message-id 
and subject line Bug#942235: fixed in dask 2.8.1+dfsg-0.1
has caused the Debian Bug report #942235,
regarding dask: autopkgtest needs update for new version of pytest
to be marked as done.

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

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


-- 
942235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dask
Version: 1.0.0+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pyt...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pytest

Dear maintainers,

With a not so recent upload of pytest the autopkgtest of dask fails in
testing when that autopkgtest is run with the binary packages of pytest
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
pytest from testing4.6.5-2
dask   from testing1.0.0+dfsg-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of pytest to testing
[1]. Of course, pytest shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in pytest was
intended and your package needs to update to the new situation. The
package had two months to adapt before this bug was even filed.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pytest should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask/3146640/log.gz

autopkgtest [19:13:10]: test command1: [---
Testing with python3.7:
= test session starts
==
platform linux -- Python 3.7.5rc1, pytest-4.6.5, py-1.8.0, pluggy-0.12.0
-- /usr/bin/python3.7
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.n16ld1px/downtmp/autopkgtest_tmp
collecting ... collected 5850 items / 2 errors / 7 skipped / 5841 selected

 ERRORS

_ ERROR collecting dataframe/io/tests/test_parquet.py
__
/usr/lib/python3/dist-packages/pluggy/hooks.py:289: in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:87: in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:81: in 
firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
/usr/lib/python3/dist-packages/_pytest/python.py:234: in
pytest_pycollect_makeitem
res = list(collector._genfunctions(name, obj))
/usr/lib/python3/dist-packages/_pytest/python.py:410: in _genfunctions
self.ihook.pytest_generate_tests(metafunc=metafunc)
/usr/lib/python3/dist-packages/pluggy/hooks.py:289: in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:87: in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:81: in 
firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
/usr/lib/python3/dist-packages/_pytest/python.py:137: in
pytest_generate_tests
metafunc.parametrize(*marker.args, **marker.kwargs)
/usr/lib/python3/dist-packages/_pytest/python.py:1004: in parametrize
function_definition=self.definition,
/usr/lib/python3/dist-packages/_pytest/mark/structures.py:130: in
_for_parametrize
if len(param.values) != len(argnames):
E   TypeError: object of type 'MarkDecorator' has no len()
__ ERROR collecting tests/test_dot.py

Bug#946155: libpam-fscrypt: PAM module config broken

[Alex Hofbauer]

Package: libpam-fscrypt
Version: 0.2.4-2
Severity: grave
Justification: renders package unusable

Hi!

Apparently in the latest version (0.2.5-1) the path substitution was broken,
resulting in "PAM_INSTALL_PATH" being used instead of the library name
"pam_fscrypt.so".

This killed decryption triggered by PAM.



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

Kernel: Linux 5.2.0-2-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-fscrypt depends on:
ii  fscrypt   0.2.4-2
ii  libc6 2.29-3
ii  libpam0g  1.3.1-5

libpam-fscrypt recommends no packages.

libpam-fscrypt suggests no packages.

-- no debconf information

Bug#938720: marked as done (trimage: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 11:37:03 +
with message-id 
and subject line Bug#938720: fixed in trimage 1.0.6-1
has caused the Debian Bug report #938720,
regarding trimage: 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.)


-- 
938720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trimage
Version: 1.0.5+git20130126.e47888e-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:trimage

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: trimage
Source-Version: 1.0.6-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 04 Dec 2019 12:19:41 +0100
Source: trimage
Binary: trimage
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Andreas Tille 
Description:
 trimage- GUI and command-line interface to optimize image files
Closes: 930279 935352 938720
Changes:
 trimage (1.0.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #930279
   * Point watch file to upstream release tags
   * Build using python3-pyqt5
 Closes: #935352, #938720
   * debhelper-compat 12
   * Standards-Version: 4.4.1
   * Trim trailing whitespace.
   * Use secure URI in Homepage field.
   * Set upstream metadata fields: Repository, Repository-Browse.
Checksums-Sha1:
 9a8e66a3c1da97c3b9541bebea9bbf9973f3d05a 1984 trimage_1.0.6-1.dsc
 73433417a40f93d1843b98844e93f765afea7faa 69246 trimage_1.0.6.orig.tar.gz
 ed9574e6155f8140a6cd6351052a8244b46e0098 5688 trimage_1.0.6-1.de

Bug#935352: marked as done (trimage: Qt4 removal from Bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 11:37:03 +
with message-id 
and subject line Bug#935352: fixed in trimage 1.0.6-1
has caused the Debian Bug report #935352,
regarding trimage: Qt4 removal from 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.)


-- 
935352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trimage
Version: 1.0.5+git20130126.e47888e-1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Hi!

As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
cycle, as announced in [1].

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get removed
from the Debian repositories.

Your package still uses Qt 4, via the Python bindings (PyQt4).

Therefore, please take the time and:

- contact your upstream (if existing) and ask about the state of a Qt 5 /
  PyQt5 port of your application;
- if there are no activities regarding porting, investigate whether there are
  suitable alternatives for your users;
- if there is a Qt 5 port that is not yet packaged, consider packaging it;
- if both the Qt 4 and the Qt 5 versions already coexist in the Debian
  archives, consider removing the Qt 4 version.

Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4.
Please see [2] for the general porting instructions, and [3] for some
Python-specific differences.

The removal is being tracked in [4]. My intention is to bump the severity
of this bug to RC soon, like it is already the case with other Qt 4 removal
bugs.

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
[2]: https://doc.qt.io/qt-5/sourcebreaks.html
[3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html
[4]: https://wiki.debian.org/Qt4Removal

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: trimage
Source-Version: 1.0.6-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated trimage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 04 Dec 2019 12:19:41 +0100
Source: trimage
Binary: trimage
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Andreas Tille 
Description:
 trimage- GUI and command-line interface to optimize image files
Closes: 930279 935352 938720
Changes:
 trimage (1.0.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #930279
   * Point watch file to upstream release tags
   * Build using python3-pyqt5
 Closes: #935352, #938720
   * debhelper-compat 12
   * Standards-Version: 4.4.1
   * Trim trailing whitespace.
   * Use secure URI in Homepage field.
   * Set upstream metadata fields: Repository, Repository-Browse.
Checksums-Sha1:
 9a8e66a3c1da97c3b9541bebea9bbf9973f3d05a 1984 trimage_1.0.6-1.dsc
 73433417a40f93d1843b98844e93f765afea7faa 69246 trimage_1.0.6.orig.tar.gz
 ed9574e6155f8140a6cd6351052a8244b46e0098 5688 trimage_1.0.6-1.debian.tar.xz
Checksums-Sha256:
 9b9d7a788e935d3db50f91c08dab764882592f48b6b10252a6a98e3e2f167589 1984 
trimage_1.0.6-1.dsc
 60448b5a827691087a1bd016a68f84d8c457fc29179271f310fe5f9fa21415cf 69246 
trimage_1.0.6.orig.tar.gz
 fb713c122c7aa9c8ab27dd8523269738e751d0a62737e074ace99d7d27d8ce74 5688 
trimage_1.0.6-1.debian.tar.xz
Files:
 d98a2bd8e125e637a349cc0476c9e480 1984 graphics optional trimage_1.0.6-1.dsc
 0e69c56323692594b66ec5b2f6d0a206 69246 graphics optional 
trimage_1.0.6.orig.tar.gz
 258462e094d63e875a3d603e5ffef0b1 5688 graphics optional 
trimage_1.0.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3nly8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF1Pg/+JN0BFOuntiu7x9QTQFUwMlka56G2ltjK
Em8XsRMF0tqc2r2kQKsJiHiXWFFpszTOOd5vtgajggPw2ij

Bug#935352: python-qt4 removal from sid

[Andreas Tille]

On Wed, Dec 04, 2019 at 09:55:00AM +0100, Kilian Valkhof wrote:
> Someone did it for me back in 2010 when it was first added as I didn't have
> the know-how. I think most of the configuration from then still works and I
> would be very grateful if someone could pick this up after we did the work
> to migrate it to QT5 :)

Done.  However, you are mentioned in the package metadata as the only
Uploader which is confusing if someone did it for you and you are just
hoping that somebody else will take over.

I'm not really sure why I did this for two times but I hope it helped
so far.

Kind regards

Andreas. 

PS: Since I need to assume that you are also not watching Debian BTS
please have a look here:
  https://bugs.debian.org/640318

 
> On 03-12-2019 22:52, Moritz Mühlenhoff wrote:
> > On Fri, Nov 22, 2019 at 11:04:18AM +0300, Dmitry Shachnev wrote:
> > > Dear maintainers,
> > > 
> > > I am going to remove the Python 2 part of python-qt4 from sid soon, but 
> > > not
> > > before 10 days from now, 2019-12-02.
> > > 
> > > If your package does not migrate away from it, it will become 
> > > uninstallable.
> > > 
> > > You will still be able to use python3-pyqt4 or python-pyqt5 for some time,
> > > so porting to Python 3 *or* to Qt 5 is enough. Of course, in the middle 
> > > term
> > > it is better to port to Python 3 *and* Qt 5.
> > Does anyone intend to upgrade trimage to 1.0.6? Otherwise I'll ask for it's
> > removal in the next weeks, we're closing in on the Qt4 removal.
> > 
> > Cheers,
> >  Moritz
> 

-- 
http://fam-tille.de

Bug#936678: marked as done (gumbo-parser: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 4 Dec 2019 14:21:46 +0300
with message-id 

and subject line Closing the bug
has caused the Debian Bug report #936678,
regarding gumbo-parser: 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.)


-- 
936678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gumbo-parser
Version: 0.10.1+dfsg-2.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:gumbo-parser

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.10.1+dfsg-2.4

Hi!

The bug is fixed in 0.10.1+dfsg-2.4 (the closing line in the changelog
mentions an incorrect bug number though, sorry.)

-- 
Sergei Golovan--- End Message ---

Processed: Re: Bug#946146: Tests are failing

[Debian Bug Tracking System]

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

> reassign 946146 python3-astlib 0.11.2-1
Bug #946146 [ginga] Tests are failing
Bug reassigned from package 'ginga' to 'python3-astlib'.
No longer marked as found in versions ginga/3.0.0-1.
Ignoring request to alter fixed versions of bug #946146 to the same values 
previously set
Bug #946146 [python3-astlib] Tests are failing
Marked as found in versions astlib/0.11.2-1.
> severity 946146 serious
Bug #946146 [python3-astlib] Tests are failing
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 915504 is serious

[Debian Bug Tracking System]

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

> severity 915504 serious
Bug #915504 [sbt] sbt: Fails to detect version of java
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#873341: marked as done (SBT is uninstallable; depends on nonexistent packages)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 18:30:18 +0800
with message-id <9d11a0458dc1234990ce84d94ae92c3927bc85f8.ca...@debian.org>
and subject line Re: SBT is uninstallable; depends on nonexistent packages
has caused the Debian Bug report #873341,
regarding SBT is uninstallable; depends on nonexistent packages
to be marked as done.

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

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


-- 
873341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbt
Version: 0.13.13-2
Severity: serious

sbt is not installable; it depends on various packages like
sbt-test-interface that only exist in experimental.
--- End Message ---
--- Begin Message ---
On Sat, 26 Aug 2017 18:52:24 + David Starner wrote:

> sbt is not installable; it depends on various packages like
> sbt-test-interface that only exist in experimental.

This appears to have been fixed now, I can install it from unstable.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: tagging 915504 ...

[Debian Bug Tracking System]

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

> tags 915504 + fixed-upstream
Bug #915504 [sbt] sbt: Fails to detect version of java
Added tag(s) fixed-upstream.
> forwarded 915504 
> https://github.com/sbt/sbt-launcher-package/commit/5a0bde442dec7d9a1bdc35655541902fb873172a#diff-edd0ab5838b2fa424d30f94df800e1f9
>  
> https://github.com/sbt/sbt-launcher-package/commit/a638ad49ac484ba87e512f6dfebf8aa83e4b3ad7#diff-edd0ab5838b2fa424d30f94df800e1f9
>  
> https://github.com/sbt/sbt-launcher-package/commit/21cf71e384b8d3dba4c56d167837a9236d294c9d#diff-edd0ab5838b2fa424d30f94df800e1f9
Bug #915504 [sbt] sbt: Fails to detect version of java
Set Bug forwarded-to-address to 
'https://github.com/sbt/sbt-launcher-package/commit/5a0bde442dec7d9a1bdc35655541902fb873172a#diff-edd0ab5838b2fa424d30f94df800e1f9
 
https://github.com/sbt/sbt-launcher-package/commit/a638ad49ac484ba87e512f6dfebf8aa83e4b3ad7#diff-edd0ab5838b2fa424d30f94df800e1f9
 
https://github.com/sbt/sbt-launcher-package/commit/21cf71e384b8d3dba4c56d167837a9236d294c9d#diff-edd0ab5838b2fa424d30f94df800e1f9'.
> thanks
Stopping processing here.

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

Bug#944582: paraview - vtk depenency removed

[nkr]

Hi,

Made a mistake by sending this mail to 944353. This is where it belongs.

The issue described in this bug is fixed. However, after the update to
5.7.0-2, the new python3-paraview has no vtk dependencies (python3-
vtk7). Previously, paraview-python had dependencies on python-vtk6 and
python3-vtk7. Yet, `python -c "import vtk"` runs successfully even when
`dpkg -l | grep vtk`, shows no vtk packages. So I'm assuming, paraview
has parts of vtk packaged with it. Parts, because although `import vtk`
is successful, a script like the one in the link below fails.

https://vtk.org/Wiki/VTK/Examples/Python/Cylinder

It runs only after installing python3-vtk7. Perhaps this is
intentional. But I just wanted to make sure.

Thanks

Bug#945389: Tried to upgrade skimage to see whether #945389 is fixed but failed

[Andreas Tille]

Hi Stefan,

thanks a lot for your feedback.

On Tue, Dec 03, 2019 at 12:38:24PM -0800, Stefan van der Walt wrote:
> The problem here stems from an old version of Cython.  My recommended 
> approach would be to build from the git tag instead of the source tarball 
> (i.e., the version without pre-generated Cython files).

Hmmm, I think the Cython files are generated in the build I did.  The
build log says:

...
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py config.
Compiling /build/skimage-0.16.2/skimage/_shared/geometry.pyx because it changed.
Compiling /build/skimage-0.16.2/skimage/_shared/transform.pyx because it 
changed.
Compiling /build/skimage-0.16.2/skimage/_shared/interpolation.pyx because it 
changed.
Partial import of skimage during the build process.
[1/3] Cythonizing /build/skimage-0.16.2/skimage/_shared/geometry.pyx
[3/3] Cythonizing /build/skimage-0.16.2/skimage/_shared/transform.pyx
[2/3] Cythonizing /build/skimage-0.16.2/skimage/_shared/interpolation.pyx
Compiling /build/skimage-0.16.2/skimage/draw/_draw.pyx because it changed.
[1/1] Cythonizing /build/skimage-0.16.2/skimage/draw/_draw.pyx
Compiling /build/skimage-0.16.2/skimage/feature/corner_cy.pyx because it 
changed.
Compiling /build/skimage-0.16.2/skimage/feature/censure_cy.pyx because it 
changed.
Compiling /build/skimage-0.16.2/skimage/feature/orb_cy.pyx because it changed.
Compiling /build/skimage-0.16.2/skimage/feature/brief_cy.pyx because it changed.
Compiling /build/skimage-0.16.2/skimage/feature/_texture.pyx because it changed.
Compiling /build/skimage-0.16.2/skimage/feature/_hessian_det_appx.pyx because 
it changed.
Compiling /build/skimage-0.16.2/skimage/feature/_hoghistogram.pyx because it 
changed.
[4/7] Cythonizing /build/skimage-0.16.2/skimage/feature/brief_cy.pyx
[5/7] Cythonizing /build/skimage-0.16.2/skimage/feature/censure_cy.pyx
[1/7] Cythonizing /build/skimage-0.16.2/skimage/feature/_hessian_det_appx.pyx
[6/7] Cythonizing /build/skimage-0.16.2/skimage/feature/corner_cy.pyx
[3/7] Cythonizing /build/skimage-0.16.2/skimage/feature/_texture.pyx
[2/7] Cythonizing /build/skimage-0.16.2/skimage/feature/_hoghistogram.pyx
[7/7] Cythonizing /build/skimage-0.16.2/skimage/feature/orb_cy.pyx
...

> I don't think the Cython-related patches that were applied since would then 
> be necessary.

The packaging does not contain any Cython-related patches as far as I
can see.  For the Debian packaging we usually prefer tagged releases.
While I could be convinced to derive from this principle it is not
really clear to me in how far your explanation matches the issue.  May
be its just me since I'm not so comfortable with Cython so I'd rather
ask back to make sure I understand you correctly.
 
> I will no longer be doing packaging work for scikit-image, so feel free to 
> remove me from the maintainer list (I thought it had already been transferred 
> to the science team a while ago).

Its correct that the _Maintainer_ is set to Debian Science team.  But
the actual members of the team (in Debian terminology the _Uploaders_)
are you and Yaroslav.  I just pushed the following commit:

$ git diff HEAD^
diff --git a/debian/changelog b/debian/changelog
index 4baf3e7e..e294c4bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,8 @@ skimage (0.16.2-1) UNRELEASED; urgency=medium
   * New upstream version
   * Standards-Version: 4.4.1
   * More default d/rules
+  * Drop Stefan van der Walt from Uploaders since he confirmed not to
+do packaging work any more (thanks for your previous work Stefan)
 
  -- Andreas Tille   Mon, 02 Dec 2019 10:07:39 +0100
 
diff --git a/debian/control b/debian/control
index deee0d75..bd692cc2 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,6 @@
 Source: skimage
 Maintainer: Debian Science Maintainers 

-Uploaders: Stefan van der Walt ,
-   Yaroslav Halchenko 
+Uploaders: Yaroslav Halchenko 
 Section: python
 Priority: optional
 Build-Depends: cython3 (>= 0.23),


Kind regards,

 Andreas. 

-- 
http://fam-tille.de

Bug#935352: python-qt4 removal from sid

[Kilian Valkhof]

Someone did it for me back in 2010 when it was first added as I didn't 
have the know-how. I think most of the configuration from then still 
works and I would be very grateful if someone could pick this up after 
we did the work to migrate it to QT5 :)


Best,

Kilian

On 03-12-2019 22:52, Moritz Mühlenhoff wrote:

On Fri, Nov 22, 2019 at 11:04:18AM +0300, Dmitry Shachnev wrote:

Dear maintainers,

I am going to remove the Python 2 part of python-qt4 from sid soon, but not
before 10 days from now, 2019-12-02.

If your package does not migrate away from it, it will become uninstallable.

You will still be able to use python3-pyqt4 or python-pyqt5 for some time,
so porting to Python 3 *or* to Qt 5 is enough. Of course, in the middle term
it is better to port to Python 3 *and* Qt 5.

Does anyone intend to upgrade trimage to 1.0.6? Otherwise I'll ask for it's
removal in the next weeks, we're closing in on the Qt4 removal.

Cheers,
 Moritz

Bug#946004: marked as done (satpy: autopkgtest failures)

[Debian Bug Tracking System]

Your message dated Wed, 04 Dec 2019 08:47:40 +
with message-id 
and subject line Bug#946004: fixed in satpy 0.16.1-5
has caused the Debian Bug report #946004,
regarding satpy: autopkgtest 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.)


-- 
946004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: satpy
Version: 0.16.1-4
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for your package are failing which block testing migration of 
its dependencies.

The log shows:

 ==
 FAIL: test_reflectance_corrector_abi 
(satpy.tests.compositor_tests.test_viirs.TestVIIRSComposites)
 --
 Traceback (most recent call last):
   File 
"/usr/lib/python3/dist-packages/satpy/tests/compositor_tests/test_viirs.py", 
line 309, in test_reflectance_corrector_abi
 self.assertLess(abs(np.mean(data) - 29.907390988422513), 1e-10)
 AssertionError: nan not less than 1e-10
 
 --

See: https://ci.debian.net/data/autopkgtest/testing/amd64/s/satpy/3561116/log.gz

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: satpy
Source-Version: 0.16.1-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Dec 2019 07:29:08 +
Source: satpy
Architecture: source
Version: 0.16.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Closes: 946004
Changes:
 satpy (0.16.1-5) unstable; urgency=medium
 .
   * debian/patches:
 - rename dask-2.8.patch into 0007-dask-2.8.patch
 - new 0008-Fix-TestVIIRSComposites.patch, backport form upstream
   (closes: #946004)
   * debian/control:
 - explicitly specify Rules-Requires-Root: no
Checksums-Sha1:
 9b2d1125eb9ac97cb6735a9b1b60e7cb232ce337 2708 satpy_0.16.1-5.dsc
 cf5e96bb547989c4449706b782c5789a0601a063 10508 satpy_0.16.1-5.debian.tar.xz
 af331a5bd9a0f0dd432e883d1f0bd5389f671f37 14222 satpy_0.16.1-5_amd64.buildinfo
Checksums-Sha256:
 a2e5fbd2d5aa5d06b3a6c626b029f8e87ffbe05121fafa59b047d39fdda9a65e 2708 
satpy_0.16.1-5.dsc
 9b75b70880d27417fb9f622dc8fc7bd8b62dd88d1dbef7dd843569c287e5bbd3 10508 
satpy_0.16.1-5.debian.tar.xz
 b6c8acb4cd6a7ce1437d13bcbd18ce13b2029796845bf8278f5b2ba93c77d4a4 14222 
satpy_0.16.1-5_amd64.buildinfo
Files:
 6a96e0113c43a196cb82021e63b6c318 2708 python optional satpy_0.16.1-5.dsc
 2cedf4f4d84a05a99191ee43c3f31dca 10508 python optional 
satpy_0.16.1-5.debian.tar.xz
 3bb5b1be1c6453f2c9bcf657c43b97ee 14222 python optional 
satpy_0.16.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl3nZ/wACgkQZ1DxCuiN
SvHJaA/+MV9YnD/cYwA37GbDacimGB2F4x3Fj3yIZc41t+JwxejcmIQhkDpUPjRW
bUf4+F2Su0rJ2oAtq2fUM2W3+ou41RtTpmt+wKsBnJKKgFGy/VbEE4kBHCDtVXNc
PHcD04+CR71dkqXD81Tn1Y2pkYx07Hkca5ER5WdOLeBosHHzIiTn+mfTYhi/kOTk
o6JROuJHwIwbS12jlTMCMf/Jy2ATTsj8V/vk3+qAtvL3hnCJi/V264n/NlSNB7KI
vcty2cm6/gWR8cAGlq8JNJjKs5wPkcd1VHOcQxQ//uifKv8PrpYMu6wJFpquldQ0
c9h7hT32UAKFlQUdwIo/zCnZvibL/vbUhsioDPXOVYhq2wjSRJhH/tVvSasM7RF0
oXV2XdBjLD8XR74FzPfriwbI522/ZtksEhMGKSzZPZkdrjwTiiK9jj/w2aZx696t
tnqQOj+eDiRxULtRp9cc7iAlRSu2vagVWwmY0x5/D8hhYAUf5yMpxwTBukcw0YRK
2kmDqEp89s8y6/CpeUPXtLdrGHgMwx7bn0DqEhpfDXPLAfZbZ5fGccUsFHLoQLar
uqqG88DAUcIOEpgRL8IuO1ZOtUIB5t3PH8HG8HYCFnuRT8pjZ0kLMWxrEGTVv1N+
UQH0a0tMjJcbFQgm0/uk1OvKMAXVI19Xvzc02haxCu0/6r/8KpE=
=7/eH
-END PGP SIGNATURE End Message ---