date:20200127

Your message dated Tue, 28 Jan 2020 07:00:01 +
with message-id 
and subject line Bug#949744: Removed package(s) from unstable
has caused the Debian Bug report #937034,
regarding mgltools-sff: 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.)


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

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

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

Dear submitter,

as the package mgltools-sff 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/949744

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

Your message dated Tue, 28 Jan 2020 06:57:37 +
with message-id 
and subject line Bug#949706: Removed package(s) from unstable
has caused the Debian Bug report #936585,
regarding gbirthday: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:gbirthday

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

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

Dear submitter,

as the package gbirthday 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/949706

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#885284: marked as done (gbirthday: Depends on unmaintained pygtk)

Your message dated Tue, 28 Jan 2020 06:57:37 +
with message-id 
and subject line Bug#949706: Removed package(s) from unstable
has caused the Debian Bug report #885284,
regarding gbirthday: Depends on 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.)


-- 
885284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gbirthday
Version: 0.6.10-0.1
Severity: serious
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.

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: 0.6.10-0.1+rm

Dear submitter,

as the package gbirthday 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/949706

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#907724: marked as done (Don't ship with buster)

Your message dated Tue, 28 Jan 2020 06:58:02 +
with message-id 
and subject line Bug#949714: Removed package(s) from unstable
has caused the Debian Bug report #907724,
regarding Don't ship with buster
to be marked as done.

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

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


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

src:twitter-bootstrap is a 6.5 year old version of Bootstrap which is orphaned
since 2013. "Current" packages are in the archive as src:twitter-bootstrap3.
The vintage version should not be in buster, reverse deps should migrate to
src:twitter-bootstrap3 or get removed (if they're only compatible with such
an old version, they're apparently dead as well).

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Version: 2.0.2+dfsg-10+rm

Dear submitter,

as the package twitter-bootstrap 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/949714

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

Your message dated Tue, 28 Jan 2020 06:58:50 +
with message-id 
and subject line Bug#949741: Removed package(s) from unstable
has caused the Debian Bug report #937022,
regarding mgltools-dejavu: 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.)


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

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

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

Dear submitter,

as the package mgltools-dejavu 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/949741

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

Your message dated Tue, 28 Jan 2020 06:58:26 +
with message-id 
and subject line Bug#949740: Removed package(s) from unstable
has caused the Debian Bug report #937021,
regarding mgltools-cmolkit: 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.)


-- 
937021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mgltools-cmolkit
Version: 1.5.7~rc1+cvs.20140424-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:mgltools-cmolkit

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

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

Dear submitter,

as the package mgltools-cmolkit 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/949740

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

Your message dated Tue, 28 Jan 2020 06:59:14 +
with message-id 
and subject line Bug#949742: Removed package(s) from unstable
has caused the Debian Bug report #937031,
regarding mgltools-pybabel: 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.)


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

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

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

Dear submitter,

as the package mgltools-pybabel 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/949742

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

Your message dated Tue, 28 Jan 2020 06:57:07 +
with message-id 
and subject line Bug#949687: Removed package(s) from unstable
has caused the Debian Bug report #937479,
regarding pymetrics: 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.)


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

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.8.1-7+rm

Dear submitter,

as the package pymetrics 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/949687

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#949089: marked as done (libxmlrpc3-java: CVE-2019-17570: deserialization of server-side exception from faultCause in XMLRPC error response)

Your message dated Tue, 28 Jan 2020 06:55:27 +
with message-id 
and subject line Bug#949479: Removed package(s) from unstable
has caused the Debian Bug report #949089,
regarding libxmlrpc3-java: CVE-2019-17570: deserialization of server-side 
exception from faultCause in XMLRPC error response
to be marked as done.

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

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


-- 
949089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxmlrpc3-java
Version: 3.1.3-9
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for libxmlrpc3-java.

CVE-2019-17570[0]:
| Deserialization of server-side exception from faultCause in XMLRPC
| error response

That said, should libxmlrpc3-java rather be removed from unstable, and
not included in bullseye?

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-17570
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17570
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1775193

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 3.1.3-9+rm

Dear submitter,

as the package libxmlrpc3-java 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/949479

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#934766: marked as done (libexosip2: CVE-2014-10375)

Your message dated Tue, 28 Jan 2020 06:56:16 +
with message-id
and subject line Bug#949551: Removed package(s) from unstable
has caused the Debian Bug report #934766,
regarding libexosip2: CVE-2014-10375
to be marked as done.

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

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

--
934766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libexosip2
Version: 4.1.0-2.1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for libexosip2.

CVE-2014-10375[0]:
| handle_messages in eXtl_tls.c in eXosip before 5.0.0 mishandles a
| negative value in a content-length header.

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-2014-10375
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-10375
[1]
http://git.savannah.nongnu.org/cgit/exosip.git/commit/?id=2549e421c14aff886629b8482c14af800f411070

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 4.1.0-2.1+rm

Dear submitter,

as the package libexosip2 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/949551

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#949312: txsocksx: should this package be removed?

2020-01-27 Thread Scott Kitterman

On Sun, 19 Jan 2020 13:06:33 -0500 Sandro Tosi  wrote:
> Source: txsocksx
> Severity: serious
> 
> Hello,
> i think txsocksx should be removed from debian:
> 
> * python2-only
> * upstream is not progressing on the py3k porting: https://github.com/
habnabit/txsocksx/issues/19
> * leaf package
> 
> if i dont hear back within a week with a good reason to keep this package, 
i'll
> file for its removal.

According to DAK there is an rdepend that needs to be addressed:

Checking reverse dependencies...
# Broken Build-Depends:
foolscap: python-txsocksx

Dependency problem found.

Please remove the moreinfo tag once it is taken care of.

Scott K

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

Bug#885238: marked as done (rumor: please migrate to guile-2.2)

Your message dated Tue, 28 Jan 2020 06:55:52 +
with message-id 
and subject line Bug#949535: Removed package(s) from unstable
has caused the Debian Bug report #885238,
regarding rumor: please migrate to guile-2.2
to be marked as done.

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

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


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

I'd like to remove guile-2.0 before the buster release, so please
migrate to guile-2.2 when you can.

Thanks 
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Version: 1.0.5-2.1+rm

Dear submitter,

as the package rumor 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/949535

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

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

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

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

Processed: tagging 949312

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

> tags 949312 + moreinfo
Bug #949312 [ftp.debian.org] RM: txsocksx -- RoQA; python2-only; leaf package; 
no progress on upstream py3k port
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#938922: marked as done (zsi: Python2 removal in sid/bullseye)

Your message dated Tue, 28 Jan 2020 06:52:32 +
with message-id 
and subject line Bug#949164: Removed package(s) from unstable
has caused the Debian Bug report #938922,
regarding zsi: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:zsi

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

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

Dear submitter,

as the package zsi 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/949164

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#949164: marked as done (RM: zsi -- RoQA; python2-only; leaf package; last release 14 years ago; better alternatives exist)

Your message dated Tue, 28 Jan 2020 06:52:25 +
with message-id 
and subject line Bug#949164: Removed package(s) from unstable
has caused the Debian Bug report #949164,
regarding RM: zsi -- RoQA; python2-only; leaf package; last release 14 years 
ago; better alternatives exist
to be marked as done.

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

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


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

Hello,
i think we should remove src:zsi from Debian:

* python-2 only
* last upstream release in ~14 years (!) ago
* no trace of development
* better alternative exists
* leaf package

if I dont hear back within a week with a good reason to keep this package, i'll
file for its removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-zsi |   2.1~a1-4 | all
   zsi |   2.1~a1-4 | source

--- Reason ---
RoQA; python2-only; leaf package; last release 14 years ago; better 
alternatives exist
--

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 949...@bugs.debian.org.

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

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#948473: marked as done (RM: cain -- RoQA; python2-only; leaf package; no upstream release since 2012)

Your message dated Tue, 28 Jan 2020 06:51:52 +
with message-id 
and subject line Bug#948473: Removed package(s) from unstable
has caused the Debian Bug report #948473,
regarding RM: cain -- RoQA; python2-only; leaf package; no upstream release 
since 2012
to be marked as done.

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

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


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

Hello,
it seems to me there are several issues with this package:

* python2-only
* no upstream release since July 2012 (not even advertized on their HP)
* low popcon (but it's also probably part of a niche package)
* one of the only 2 reverse-dependency for python-scipy

It is my opinion we should remove this package from Debian; if i dont hear back
within a week with a good reason to keep this package around, i'll file for its
removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  cain | 1.10+dfsg-3 | source, all
cain-examples | 1.10+dfsg-3 | all
cain-solvers | 1.10+dfsg-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; python2-only; leaf package; no upstream release since 2012
--

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 948...@bugs.debian.org.

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

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#949991: haskell-hledger ftbfs on s390x

Package: src:haskell-hledger
Version: 1.14.2-1
Severity: serious
Tags: sid bullseye

haskell-hledger ftbfs on s390x

[...]
Dependency installability problem for haskell-hledger on s390x:
haskell-hledger build-depends on missing:
- libghc-hledger-lib-dev:s390x (>= 1.14.1)

Bug#949229: marked as done (opensc.conf config file not installed at the correct location?)

Your message dated Tue, 28 Jan 2020 05:19:27 +
with message-id 
and subject line Bug#949229: fixed in opensc 0.20.0-3
has caused the Debian Bug report #949229,
regarding opensc.conf config file not installed at the correct location?
to be marked as done.

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

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


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

Hi,

Is it possible that the opensc.conf is not installed at the correct
path?

It seems that the file is not read and looking in the opensc.conf
manpage it should be in /etc instead of /etc/opensc directory.

Shouldn't the file be moved or the OPENSC_CONF_PATH (and the manpage)
fixed?

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages opensc depends on:
ii  libc6  2.29-9
ii  libreadline8   8.0-3
ii  libssl1.1  1.1.1d-2
ii  opensc-pkcs11  0.20.0-1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages opensc recommends:
ii  pcscd  1.8.26-2

opensc suggests no packages.

-- Configuration Files:
/etc/opensc/opensc.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opensc
Source-Version: 0.20.0-3

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

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

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

Debian distribution maintenance software
pp.
Eric Dorland  (supplier of updated opensc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Jan 2020 23:41:56 -0500
Source: opensc
Architecture: source
Version: 0.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers 
Changed-By: Eric Dorland 
Closes: 949229
Changes:
 opensc (0.20.0-3) unstable; urgency=medium
 .
   * Fix patch to use /etc/opensc for opensc.conf (Closes: 949229)
Checksums-Sha1:
 95ef6e25a63ef240366e01fef357f5951e9e7015 2133 opensc_0.20.0-3.dsc
 c65fe7cf4794b643ed497c1fbf73d151d1651828 13400 opensc_0.20.0-3.debian.tar.xz
 b3bdc008417b27100168e4a39dad9f5cc46c94fe 8573 opensc_0.20.0-3_amd64.buildinfo
Checksums-Sha256:
 162bc4a27fac3caf88676ac78ae81569c385ea93e3ad6e81ae38545d67ad44d5 2133 
opensc_0.20.0-3.dsc
 ce53bc6963e0e4ff376b7cbdc0b9ec788ee36fe50b1a8d82fb00241cbc283b09 13400 
opensc_0.20.0-3.debian.tar.xz
 2679989cb2475bfb7a2a4b0694af4a2f0f25420c3a6fb07e9e79f0a65e014d17 8573 
opensc_0.20.0-3_amd64.buildinfo
Files:
 9381f0ad015c64aa4b309f6442797f57 2133 utils optional opensc_0.20.0-3.dsc
 a08ebc8c042fa50975aed44b10d51576 13400 utils optional 
opensc_0.20.0-3.debian.tar.xz
 0bfef319e1be55c8a30986c24e0a7483 8573 utils optional 
opensc_0.20.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ88SKPcm/VtHTOliwlb71QAiHpMFAl4vvwgACgkQwlb71QAi
HpNwIA/+P0fA54PVCAlIPtd5QnpVySNW3eM7CFb8WlwUKEMl+vy0RquviAbqqLT3
nToOxOQEYqlOW0TuP5i9+GQFr798YB22ADppq6m/4eaMcmRyePUXnz2dxNYC+Eae
H46s1oak2/W6le06jp7QLIkHbuH+t3Jbp2LBHYjjzHKIOz5MZ541na2/LqkFKjlU
Dg8xWjmT2ZY4f04LPakq0EduWjKAg704HjtO2E2Im3XO0R4bKU4DcVvg+Cj1KtnC
zYsoY8M0X1BycyUcoQgSN74WYrUeYJxnMW+zIM5E+mkmKlxkhYFRT8vmBsBCkz36
VooPfUeeUj5pxxYBsqn+5edUYWxX3D31/OwdEoeCDwRmKdnhE/7SSlab/h5zstqb
cgE/bKUiNbSI//RYANqFSowAKlOGVQaVd7sHJTxAj/UfUY8XOkEbGmUjmyDs8LLe
98oGXZRKZvxPO99srRuEc6/uWaBtjED5bErJ6o7xyKOA2y0OjU/cJ5QmGkdJI1NU
HOamK8aGEMw4JP3WKFt4OKHkrg5b8opX0WeuFlhnO4H9iCVoF/e3asn7y2WBb2Qg
E7p9PfLtiagsJEz2lNiWtVUZOOqEcdCTgtLPjmKAOE0SH/htLdM8FQSOp0NBIrUy
11wp6FMMIwFg3ylF/+PD9UerP3s4g4nNxvd1z6ttGh6+3+m5sEM=
=XBWX
-END PGP SIGNATURE---

Bug#947251: [Python-apps-team] Bug#947251: mypaint: Please build-depend on python-gi in addition to python-gi-dev

2020-01-27 Thread Sandro Tosi

On Mon, Jan 27, 2020 at 6:57 PM Simon McVittie  wrote:
> The long-term solution is dropping Python 2 (#937099).

there is a new beta version for 2.0.0 that should support python3;
it's in my backlog of activities for py2removal, but if someone wants
to have a go at that, that'd be great

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#936857: libfreenect: Python2 removal in sid/bullseye

2020-01-27 Thread Sandro Tosi

> I would have tried going "longer" way, given the age of 0.5.3.  Would
> you have time for it Sandro, or should I try?

if you have spare cycles, i'd prefer if you could have a look at it

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#949938: d-feet build depends on the removed pep8 transitional package

2020-01-27 Thread Sandro Tosi

yep, this is clearly my fault.

i could either reintroduce pep8, or maybe we could have pycodestyle
provide pep8 and that should satisfy the dependencies?

On Mon, Jan 27, 2020 at 6:45 PM Simon McVittie  wrote:
>
> Control: tags 949938 + pending
>
> On Mon, 27 Jan 2020 at 13:21:03 +0200, Adrian Bunk wrote:
> > pep8 is no longer built by src:pep8.
>
> Thanks for reporting this, fix in progress. The pep8 binary package seems
> to have been removed without checking for reverse-dependencies. Affected
> packages:
>
> Checking reverse dependencies...
> # Broken Build-Depends:
> backup2swift: pep8  #949942
> budgie-extras: pep8 I'll open a bug
> byobu: pep8 #949941
> cloud-init: pep8#949940
> custodia: pep8  #949939
> d-feet: pep8#949938
> dirspec: pep8   #949937
> ovirt-guest-agent: pep8 I'll open a bug
> pygobject: pep8 Fix in progress
> python-apt: pep8I'll open a bug; fixed in experimental
> python-cliapp: pep8 #949936
> python-ddt: pep8#949935
> seqdiag: pep8 (>= 1.3)  #949934
> swiftsc: pep8   #949933
> syslog-ng: pep8 #949847
>
> Regards,
> smcv



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: severity of 949910 is important

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

> severity 949910 important
Bug #949910 [src:linux] linux-image-4.19.0-6-amd64: bnx2x driver fails in DMAE, 
renders server unusable
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#949970: marked as done (b-d's on python3-dev / python3-dbg but hardcodes 3.7)

Your message dated Tue, 28 Jan 2020 03:04:35 +
with message-id 
and subject line Bug#949970: fixed in pivy 0.6.5-1
has caused the Debian Bug report #949970,
regarding b-d's on python3-dev / python3-dbg but hardcodes 3.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.)


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

b-d's on python3-dev / python3-dbg but hardcodes 3.7 in the rules file.  You
should not hard-code a specific Python3 version.
--- End Message ---
--- Begin Message ---
Source: pivy
Source-Version: 0.6.5-1

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

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

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

Debian distribution maintenance software
pp.
Kurt Kremitzki  (supplier of updated pivy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jan 2020 20:37:31 -0600
Source: pivy
Architecture: source
Version: 0.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Closes: 949970
Changes:
 pivy (0.6.5-1) unstable; urgency=medium
 .
   * [2ac31f3] Remove upstreamed patches (all)
   * [b62ef60] Update d/watch to new Github upstream
   * [da6fa49] Update homepage
   * [03ae26c] Add Rules-Requires-Root: no
   * [0d19e64] New upstream version 0.6.5
   * [5249b08] Don't hardcode Python version (Closes: #949970)
Checksums-Sha1:
 0e2d69d1cedda81d31c2f76d48dd2c1bb884ca08 2272 pivy_0.6.5-1.dsc
 5d04248fb60d3668b877dfc4ef66ccd6a202fe9f 6647652 pivy_0.6.5.orig.tar.gz
 dd6da9ae6e8d74b0337933adc732302c0b078215 4536 pivy_0.6.5-1.debian.tar.xz
 ce144a8c0930b4ffcaa978dc820bbd8191fb0892 14160 pivy_0.6.5-1_source.buildinfo
Checksums-Sha256:
 ab7bf23c2c31bc77338c9ed4cac73f00383d32c20600af90d11923552770c476 2272 
pivy_0.6.5-1.dsc
 ffc2ac04a48fc36215f7345285a9b17a3f76e39f2a48ee374f1a77b8f38a4f9f 6647652 
pivy_0.6.5.orig.tar.gz
 45712b12ae71070bb9c4adcc0347bb7f0b2d6ca43cb84d52418878351c592f24 4536 
pivy_0.6.5-1.debian.tar.xz
 581f5ac73577f5c54bf2b431e178869646410f9b8ad0e67f6c7f6dadc7d15988 14160 
pivy_0.6.5-1_source.buildinfo
Files:
 db9031fa540f947d4c50ae6a7009b92f 2272 python optional pivy_0.6.5-1.dsc
 75a8c1f029e0aa94457f6e51dd9c4830 6647652 python optional pivy_0.6.5.orig.tar.gz
 085aee070298ead793d192eedf534398 4536 python optional 
pivy_0.6.5-1.debian.tar.xz
 5909afc1d493756ec9a9c234933360bc 14160 python optional 
pivy_0.6.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl4vnsQRHGt1cnRAa3dr
LnN5c3RlbXMACgkQKUghB0bfc8ANgA/7BXjTnexw5ddgneB7v8k5mb6cQ+olP8ZI
dFIcyuM20B931Df1pC8DAdOfPj8XvwwDg4ezgqeLyDbdGV9RpbKW1sV1jbtadzzV
icOJu5SBY6N/81rkKjj523TQJ/fM+zNndKEOcMlS/tSauu1L6mhDnaQf0xf1G+3r
zPKAmavgsYjOgmKyF+7YL7I9Pb7MVHlfodh/jJJKZ4Dsh4sS1a7JYvwVHmdINaVi
ZGtlim/IhsDiCx5oih9CFdxpx3ytYRmgUh26MmzW6Goj6Y/2cjF9WyV+HZGkSHEh
PaiAmBonCQ36UJKKYtrioAAx9IRSz3jvf7C4yE469IRDwQT4iH5UshQwJ18L+NnS
1HMvr14JeNBzfNyBeCuT83i2B6eD3R2lWFd7b20fUp9te04wIhG6loeGmzjFsYvC
5OX3W/6RR+XMjYcp9YzFmbz20lSpo6sp3KdmOKUOKkjV10vucZFqLrElGx0PlkD0
BtWvRuIOtXL4p0OE9Bm3tHNmiM7IYbIOzJjSlg8MRhweCuHdkzIBJp5vhF/zmb/i
hYlGVPX/5y5BWptb5KNKFnd2Fe754Y/XpxPHnSowFdr8A4wrTQwixUsYR4qN2Yev
SqZa+WXbchMVXwjoZvQw1N9Ldel1NQAHJJzenNjJuAAruxAIsMppMEsO1MqgXDIy
apgzC16JqCY=
=sAhS
-END PGP SIGNATURE End Message ---

Bug#945260: marked as done (python-quantities ftbfs with Python 3.8)

Your message dated Tue, 28 Jan 2020 02:43:08 +
with message-id 
and subject line Bug#945260: fixed in python-quantities 0.12.4-1
has caused the Debian Bug report #945260,
regarding python-quantities ftbfs 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.)


-- 
945260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-quantities
Version: 0.12.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

==
ERROR: test_clip (quantities.tests.test_methods.TestQuantityMethods)
--
Traceback (most recent call last):
  File "/<>/.pybuild/cpython3_3.8/build/quantities/quantity.py",
line 247, in __array_prepare__
res._dimensionality = p_dict[uf](*objs)
KeyError: 

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8/build/quantities/tests/test_methods.py",
line 198, in test_clip
self.methodWithOut(
  File
"/<>/.pybuild/cpython3_3.8/build/quantities/tests/test_methods.py",
line 125, in methodWithOut
ret = getattr(q.copy(), name)(*args, out=out, **kw)
  File "/<>/.pybuild/cpython3_3.8/build/quantities/quantity.py",
line 579, in clip
clipped = self.magnitude.clip(
  File "/usr/lib/python3/dist-packages/numpy/core/_methods.py", line 131, in 
_clip
return _clip_dep_invoke_with_casting(
  File "/usr/lib/python3/dist-packages/numpy/core/_methods.py", line 85, in
_clip_dep_invoke_with_casting
return ufunc(*args, out=out, **kwargs)
  File "/<>/.pybuild/cpython3_3.8/build/quantities/quantity.py",
line 249, in __array_prepare__
raise ValueError(
ValueError: ufunc  not supported by quantities
please file a bug report at https://github.com/python-quantities


--
Ran 161 tests in 0.954s

FAILED (errors=1, expected failures=3)
--- End Message ---
--- Begin Message ---
Source: python-quantities
Source-Version: 0.12.4-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated 
python-quantities package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Jan 2020 20:34:29 -0500
Source: python-quantities
Architecture: source
Version: 0.12.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Yaroslav Halchenko 
Closes: 945260
Changes:
 python-quantities (0.12.4-1) unstable; urgency=medium
 .
   * New upstream release
 - addresses "Fix " not supported" error" (Closes: #945260)
Checksums-Sha1:
 897404296d5606ffde8de2fbe3ac005fccf35e2d 2194 python-quantities_0.12.4-1.dsc
 d4f1c4bef6c8db34217b42a6153a93839411828e 104100 
python-quantities_0.12.4.orig.tar.gz
 46a656d3b960b4751d52ef185edd998239c45083 3884 
python-quantities_0.12.4-1.debian.tar.xz
 b545b1a077c7a68a72cb0da53935765015a9 6066 
python-quantities_0.12.4-1_source.buildinfo
Checksums-Sha256:
 d707fe8ce25669abf52fccb0718d0b7dcd9b3dd0001a3abdb179f474945f2013 2194 
python-quantities_0.12.4-1.dsc
 c04c16d59ea4fa025473c4cca686288cbdf83caff1eb2acddb037483568e70d1 104100 
python-quantities_0.12.4.orig.tar.gz
 acd19cc2ec3f18739e341896ba840aad81e69c875fb77530a5aa31476708f4f2 3884 
python-quantities_0.12.4-1.debian.tar.xz
 75e3929315c1c7cecc9b5c93d05b836e67bb26552410481a0c12dd32583f9ed8 6066 
python-quantities_0.12.4-1_source.buildinfo
Files:
 b1d5bd8a0cf3dfcab40ddc517ecf4da2 2194 python optional 
python-quantities_0.12.4-1.dsc
 a41b9a73fab07388266c08fcfe8e0f8c 104100 python optional 
python-quantities_0.12.4.orig.tar.gz
 72a813dbb3caf22dd6f1077d69efd950 3884 python optional 
python-quantities_0.12.4-1.debian.tar.xz
 7ce7b015c4193407ac0cd3e29bcaf689 6066 python optional 
python-quantities_0.12.4-1_source.buil

Bug#936857: libfreenect: Python2 removal in sid/bullseye

2020-01-27 Thread Yaroslav Halchenko



On Mon, 27 Jan 2020, Sandro Tosi wrote:
> in the archive we have 0.5.3, released in 2015; the latest upstream
> release is 0.5.7 which was released in 2017; the first release to
> support python3 is 0.5.4 of 2016.

> I see 2 paths forward:

> 1. (longer) the package gets upgraded to 0.5.7 (with a relative mini
> transition i guess) and that includes adding python3-freenect and drop
> python-freenect
> 2. (shorter) we keep 0.5.3 and we simply drop python-freenect, which
> has 0 reverse dependencies in the archive.

> What do you think it's best here?

I would have tried going "longer" way, given the age of 0.5.3.  Would
you have time for it Sandro, or should I try?

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

Bug#949938: marked as done (d-feet build depends on the removed pep8 transitional package)

Your message dated Tue, 28 Jan 2020 00:04:28 +
with message-id 
and subject line Bug#949938: fixed in d-feet 0.3.15-2
has caused the Debian Bug report #949938,
regarding d-feet build depends on the removed pep8 transitional package
to be marked as done.

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

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


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

pep8 is no longer built by src:pep8.
--- End Message ---
--- Begin Message ---
Source: d-feet
Source-Version: 0.3.15-2

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated d-feet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Jan 2020 23:05:14 +
Source: d-feet
Architecture: source
Version: 0.3.15-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 949938
Changes:
 d-feet (0.3.15-2) unstable; urgency=medium
 .
   * Standards-Version: 4.5.0 (no changes required)
   * Build-depend on pycodestyle instead of the transitional pep8 package,
 which was recently removed. The upstream build system already
 prefers to use the pycodestyle name for the program. (Closes: #949938)
   * Normalize order of dependencies (wrap-and-sort -abt)
   * Eliminate trailing whitespace from d/copyright (wrap-and-sort -abt)
   * Normalize order of d/d-feet.install (wrap-and-sort -abt)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Name.
   * Set upstream metadata fields: Repository, Repository-Browse.
Checksums-Sha1:
 fd45c3448231b7de50bc1496a26a788755a3b604 2349 d-feet_0.3.15-2.dsc
 e2530f414f987b0490960dc3b25e72c54d46a49b 7416 d-feet_0.3.15-2.debian.tar.xz
 3770e57f26c89b004262eb2277183eccd956cc94 14917 d-feet_0.3.15-2_source.buildinfo
Checksums-Sha256:
 86f746f6fe46705a1843e6a5aa19610a471d942016d6af75cebb08657708b59d 2349 
d-feet_0.3.15-2.dsc
 baf0851cf6e131e10fad57fc2fa91877c3583731091b52e5bc1cbf6fa756f22c 7416 
d-feet_0.3.15-2.debian.tar.xz
 6db5a3b7579ae0172f9c960cff22519597c7114485c31fc4fb52fdfba80be67b 14917 
d-feet_0.3.15-2_source.buildinfo
Files:
 aa6bf070fc231fc697f73993600af212 2349 devel optional d-feet_0.3.15-2.dsc
 08cdad62cfb799fd8aa2f58b0735097a 7416 devel optional 
d-feet_0.3.15-2.debian.tar.xz
 dc1a4ec0e36964848826b614f8635015 14917 devel optional 
d-feet_0.3.15-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl4vdsQQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT5DWD/4y97JkC3c5npn6oMJkEShOSGqJh3tMsf5K
jpcIemKmnISFoGMxJ8JHT+X/SKL7aTHAE8lQieSIP+U8srnaRaV3KLsIq8VZh35m
sGNd5rKrujQr0MMJsI5iNxxQpHQ98xPYUjwGIuj0tsafvPkHQ6nVRXESBQJOmuth
jIk8Xc28qFRV/7ewC448ba5AlKc45mWM2EtEJ6lz/DbWcmV4IK3LSl8YxvhkFT4K
wTQgnyaiZhVt11DTxJETGmtr/695TCzGiBWsCMgbfzEaP3HPxB599/1lfXlc1kLR
HBkFUcBXo4SMHeLZHIIXOadsBHpXDitRSR4tsWn+tTZw1onPw54Pav/R4LuFIHqj
bKAvjTCM9MALbgFrfREMdUeWrORSRXd2eCzFNzfzquwhOVGkXp3pnLvBvDLYLWcj
P8ZAVsAv3tf18882oz9SdtI1xtu2DQfbBRCgX7bVYBRoKjZtIC4KVvZGlkbg2SVe
Zg/S/SPuAxUsnhaLxoLmIg5cSJ0tn9hAUjS5NKjE3rYJCc1bEq92jmfhnHGP6Ewd
PNpHxAz1xKy0kt+TxrPPgcydk0v1YwCon11BqpYUAbcff8qoW95+avcgiWxWhrd4
k0k+CFOj2nBSlhf7HjSNqmS9QWsL+uwg9CLh5zkD49zBzAAmbbFNJ7F1gUtY4pvE
kFYTC7Q6VQ==
=GuF0
-END PGP SIGNATURE End Message ---

Bug#946916: marked as done (libtritonus-java FTBFS after libfluidsynth update)

Your message dated Tue, 28 Jan 2020 00:04:46 +
with message-id 
and subject line Bug#946916: fixed in libtritonus-java 20070428-14.1
has caused the Debian Bug report #946916,
regarding libtritonus-java FTBFS after libfluidsynth update
to be marked as done.

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

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


-- 
946916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtritonus-java
Version: 20070428-14+b1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libfluidsynth2 transition, so I scheduled
binNMU's. However, your package FTBFS on all architectures.

Please fix your package.

Paul

https://buildd.debian.org/status/package.php?p=libtritonus-java

Tail of log for libtritonus-java on amd64:

org_tritonus_midi_device_fluidsynth_FluidSynthesizer.c:502:58: warning: pointer 
targets in passing argument 5 of ‘fluid_synth_get_program’ differ in signedness 
[-Wpointer-sign]
  502 |   fluid_synth_get_program(synth, channel, &sfont, &bank, &program);
  |  ^~~~
  |  |
  |  unsigned int *
In file included from /usr/include/fluidsynth.h:97,
 from org_tritonus_midi_device_fluidsynth_FluidSynthesizer.c:41:
/usr/include/fluidsynth/synth.h:79:49: note: expected ‘int *’ but argument is 
of type ‘unsigned int *’
   79 | int *bank_num, int *preset_num);
  |~^~
make[2]: *** [: 
org_tritonus_midi_device_fluidsynth_FluidSynthesizer.o] Error 1
make[2]: Leaving directory '/<>/src/lib/fluidsynth'
make[1]: *** [debian/rules:23: override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-arch] Error 2



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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl35RdIACgkQnFyZ6wW9
dQq2HwgAxaTL9mJvWiNnI65bnzGedrAsxxhA+ZXx+V45m0BiNgNpU9ePxsHlOz+6
XGwIOTFiIMVAGrEcnaqOMY90bRgiOi1rQObjHhCJjp+DFy/GX1xUjFyQBO+T9Amf
eLPlRB8UDm46/hy6wBUshXkSDGZA/2coqWrb7I5ncYvQhOndkh1JfAPHHpKX2j68
Zq6bsme6MvKuCUwa+KKgAihEzlKQmURXFvi45aNcTDRM9HiOXAb0NFZsGji/795H
6YxICMmlxTKTyMF0e/dlpVwf7ZvYeQq8CBWgUbNT8bHydo11CY8s+bz3G9N2ubnP
O23DU0AWQ4WKqeCBtQZg5P5poh8EhA==
=rwf6
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libtritonus-java
Source-Version: 20070428-14.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jan 2020 00:28:23 +0100
Source: libtritonus-java
Architecture: source
Version: 20070428-14.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 946916
Changes:
 libtritonus-java (20070428-14.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Peter Michael Green ]
   * Bump java source/binary versions to 1.6, since unstable's compiler
 no longer accepts 1.5
   * Fix build with new fluidsynth. (Closes: #946916)
   * Bump fluidsynth build-dependency.
Checksums-Sha1:
 cc5dde81c41d1383e7be2dbbb2410cd381c34852 2309 
libtritonus-java_20070428-14.1.dsc
 42335d477e59258a7112922de37fcb9ee7b807e0 9904 
libtritonus-java_200

Processed: Re: Bug#947251: mypaint: Please build-depend on python-gi in addition to python-gi-dev

Processing control commands:

> severity -1 serious
Bug #947251 [src:mypaint] mypaint: Please build-depend on python-gi in addition 
to python-gi-dev
Severity set to 'serious' from 'important'
> tags -1 + ftbfs bullseye sid
Bug #947251 [src:mypaint] mypaint: Please build-depend on python-gi in addition 
to python-gi-dev
Added tag(s) bullseye, sid, and ftbfs.

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

Bug#949938: marked as pending in d-feet

Control: tag -1 pending

Hello,

Bug #949938 in d-feet 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/utopia-team/d-feet/commit/b822ad6bd2bc24a5aca8754f93e2c1e48edd6998


Build-depend on pycodestyle instead of pep8

pep8 is a transitional package, which was recently removed. The upstream
build system already prefers to use the pycodestyle name for the program.

Closes: #949938


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/949938

Processed: Bug#949938 marked as pending in d-feet

Processing control commands:

> tag -1 pending
Bug #949938 [src:d-feet] d-feet build depends on the removed pep8 transitional 
package
Ignoring request to alter tags of bug #949938 to the same tags previously set

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

Bug#949983: python-apt: Build-Depends on pep8 which has been removed

Source: python-apt
Version: 1.8.5
Severity: serious
Tags: ftbfs sid bullseye
Control: fixed -1 1.9.1

python-apt Build-Depends on the pep8 transitional package, which has
already been removed (see #940736). This makes python-apt unbuildable
in unstable. Please build-depend on pycodestyle instead, and if necessary
update any build scripts that run the 'pep8' executable so they run
'pycodestyle' instead.

The version in experimental appears to have fixed this already.

smcv

Processed: python-apt: Build-Depends on pep8 which has been removed

Processing control commands:

> fixed -1 1.9.1
Bug #949983 [src:python-apt] python-apt: Build-Depends on pep8 which has been 
removed
Marked as fixed in versions python-apt/1.9.1.

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

Bug#949981: budgie-extras: Build-Depends on pep8 which has been removed

Source: budgie-extras
Version: 0.9.1-1
Severity: serious
Tags: ftbfs sid bullseye
Control: fixed -1 0.91.0-1

budgie-extras Build-Depends on the pep8 transitional package, which has
already been removed (see #940736). This makes budgie-extras unbuildable
in unstable. Please build-depend on pycodestyle instead, and if necessary
update any build scripts that run the 'pep8' executable so they run
'pycodestyle' instead.

The version in experimental appears to have fixed this already.

smcv

Bug#949982: ovirt-guest-agent: Build-Depends on pep8 which has been removed

Source: ovirt-guest-agent
Version: 1.0.15.dfsg-1
Severity: serious
Tags: ftbfs sid bullseye

ovirt-guest-agent Build-Depends on the pep8 transitional package, which has
already been removed (see #940736). This makes ovirt-guest-agent unbuildable
in unstable. Please build-depend on pycodestyle instead, and if necessary
update any build scripts that run the 'pep8' executable so they run
'pycodestyle' instead.

smcv

Processed: budgie-extras: Build-Depends on pep8 which has been removed

Processing control commands:

> fixed -1 0.91.0-1
Bug #949981 [src:budgie-extras] budgie-extras: Build-Depends on pep8 which has 
been removed
Marked as fixed in versions budgie-extras/0.91.0-1.

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

Bug#949938: d-feet build depends on the removed pep8 transitional package

Control: tags 949938 + pending

On Mon, 27 Jan 2020 at 13:21:03 +0200, Adrian Bunk wrote:
> pep8 is no longer built by src:pep8.

Thanks for reporting this, fix in progress. The pep8 binary package seems
to have been removed without checking for reverse-dependencies. Affected
packages:

Checking reverse dependencies...
# Broken Build-Depends:
backup2swift: pep8  #949942
budgie-extras: pep8 I'll open a bug
byobu: pep8 #949941
cloud-init: pep8#949940
custodia: pep8  #949939
d-feet: pep8#949938
dirspec: pep8   #949937
ovirt-guest-agent: pep8 I'll open a bug
pygobject: pep8 Fix in progress
python-apt: pep8I'll open a bug; fixed in experimental
python-cliapp: pep8 #949936
python-ddt: pep8#949935
seqdiag: pep8 (>= 1.3)  #949934
swiftsc: pep8   #949933
syslog-ng: pep8 #949847

Regards,
smcv

Processed: Re: Bug#949938: d-feet build depends on the removed pep8 transitional package

Processing control commands:

> tags 949938 + pending
Bug #949938 [src:d-feet] d-feet build depends on the removed pep8 transitional 
package
Ignoring request to alter tags of bug #949938 to the same tags previously set

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

Processed: Re: Bug#949938: d-feet build depends on the removed pep8 transitional package

Processing control commands:

> tags 949938 + pending
Bug #949938 [src:d-feet] d-feet build depends on the removed pep8 transitional 
package
Added tag(s) pending.

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

Processed: Merge

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

> forcemerge 947117 949960
Bug #947117 {Done: Dmitry Shachnev } [qtbase5-dev] doxygen: 
Build error: "Qt5::Gui" references the file 
"/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.
Bug #949960 [qtbase5-dev] Qt5::Gui: CMake does not find libEGL.so
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 949960 affects src:doxygen
Marked as fixed in versions qtbase-opensource-src/5.12.5+dfsg-3.
Added tag(s) ftbfs.
Merged 947117 949960
> thanks
Stopping processing here.

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

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration"

2020-01-27 Thread scott092707

Further attempts to install, with images through the current 01/27/2020 .iso,
continue to fail in exactly the same way.

Bug#948965: calamares: Debian 11 live testing amd64 LXQt + non-free fails with: "Bad unsquash configuration"

2020-01-27 Thread scott092707

Further attempts to install, with images through the current 01/27/2020 .iso,
continue to fail in exactly the same way.

Bug#949967: marked as done (fix build dependencies)

Your message dated Mon, 27 Jan 2020 21:34:57 +
with message-id 
and subject line Bug#949967: fixed in python-py2bit 0.3.0-3
has caused the Debian Bug report #949967,
regarding fix build dependencies
to be marked as done.

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

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


-- 
949967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-py2bit
Version: 0.3.0-2
Severity: serious
Tags: sid bullseye patch

fix build dependencies, python3-all-dev is the only correct b-d.

patch at
http://launchpadlibrarian.net/462373681/python-py2bit_0.3.0-2build1_0.3.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-py2bit
Source-Version: 0.3.0-3

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-py2bit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jan 2020 22:05:50 +0100
Source: python-py2bit
Architecture: source
Version: 0.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 949967
Changes:
 python-py2bit (0.3.0-3) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Team upload.
   * Fix build dependencies.
 Closes: #949967
 .
   [ Andreas Tille ]
   * Standards-Version: 4.5.0 (routine-update)
   * debhelper-compat 12 (routine-update)
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
Checksums-Sha1:
 57c0f272b5b5b09bbdd12f27cc85fcc27fbc20c6 2044 python-py2bit_0.3.0-3.dsc
 e466dd455e6a6d6f9bdea37fa24774b4daf32de5 2428 
python-py2bit_0.3.0-3.debian.tar.xz
 1c8e0a194bcf923fd2696cdf3822120c66a8cd71 7120 
python-py2bit_0.3.0-3_amd64.buildinfo
Checksums-Sha256:
 15dbaaccec18c06d1eb678203b3a45139565d58ca0dfeceda3193cfc47c48e78 2044 
python-py2bit_0.3.0-3.dsc
 06e2873d9978dae3ded9f33448f29e815d858f1f4af84a67cbc22001cc1e2bbb 2428 
python-py2bit_0.3.0-3.debian.tar.xz
 9fc4b52c297548434c33419c974ee60b92cfa798c0999c7df012f8ac70081b9b 7120 
python-py2bit_0.3.0-3_amd64.buildinfo
Files:
 fd44ca0198c0cdc0fc8c6b74da90bbe7 2044 science optional 
python-py2bit_0.3.0-3.dsc
 4f36966187e89d4ad5896a2efa5ffacc 2428 science optional 
python-py2bit_0.3.0-3.debian.tar.xz
 eaf7e22cfd1d27f3a9c3cb700bba0d64 7120 science optional 
python-py2bit_0.3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4vUiQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHhcQ//TefWlLDGxiuEwdCFpRQ+3lTCn+GfksC3
o8slDQl5DN4X6aco5XhruCNNjE0v68XxH14ot4NtpKBq51wkdc2BxzaNN+oEDGx6
6xIG43PgukBpmWJ93GY8UK7FcQwZo4FQrL8oB5QwUy9Jid0oY8J+Sy1/Z+94n+ZX
b519SuRM9tragFIbwt+7vKk8nXDGaVepDZopi96aDyWTM/yhXimlWzy2d75aVU3M
jlMBwHvIdLlt0alQm2zv0VPfGwUrzscLZkLUlpdjBUwOB9wOb0NEr04UyrYBw2O8
KMPk4b0Wee3a9XjqjDIRE4SJaS0uEhxd4lHmch3GEVYlAOWjyutB2jW7Ac3nAkJM
uwenmA3tf4GsROPw5SOuSOVwk8X3Fq15jeXXCPxLP9KALDREfxBf0IB2s22JO+Di
owdAraSLAeX43C0K+GN9ZUDkDDzQaoisFp7SfIz+qqUDwDIfgXgR2oCnrTDzYkmj
KfH1WXVnJB3DQEnX0OhCzGxNoRUtfabks0xwVQ3I+KO/cme0diW/ztlGuUClzyU7
8FUQETT4Cu5A0CdHeYtkAAdr2ycDk6XRaTbqb7oW37u72+SpdLQ3YUyRCFHdf5Y6
t7B6K6lOUxGiGBdnzJro1A8HLT5mXLceTPSMRqx5qkjXXuww/CsQoEhkql2AiKNm
3Lq4AoF93aM=
=5RBO
-END PGP SIGNATURE End Message ---

Bug#949975: coq,coqide: both ship /usr/bin/coqidetop{,.opt}

2020-01-27 Thread Andreas Beckmann

Package: coq,coqide
Version: 8.9.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../120-coqide_8.9.1-4_amd64.deb ...
  Unpacking coqide (8.9.1-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-XoXXFb/120-coqide_8.9.1-4_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/coqidetop', which is also in package coq 
8.9.1-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-XoXXFb/120-coqide_8.9.1-4_amd64.deb


cheers,

Andreas


coqide=8.9.1-4_coq=8.9.1-4.log.gz
Description: application/gzip

Bug#948774: Bug#948477: transition: openbabel

2020-01-27 Thread Paul Gevers

Hi Andrius,

On 16-01-2020 11:48, mer...@debian.org wrote:
> Thanks a lot, I will wait a week before working on the transition.

I see you went ahead *and* you added an autopkgtest to openbabel.
Obviously I love autopkgtests, however, the test fails and times out on
arm64.

In case you don't know how to fix the test for arm64, I suggest you mark
the test with the skippable restriction and exit 77 at the start of the
test if it detects it runs on arm64. Obviously, fixing the test is better.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: your mail

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

> tags 949968 + pending
Bug #949968 [src:python-noise] fix build dependencies
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: clblas: *gemm wrong answers in out-of-order queues

Processing control commands:

> retitle -1 clblas: *gemm wrong answers in out-of-order queues
Bug #949767 [src:libgpuarray,src:pocl] wrong results in gemm(batch) in 
out-of-order queues
Changed Bug title to 'clblas: *gemm wrong answers in out-of-order queues' from 
'wrong results in gemm(batch) in out-of-order queues'.
> reassign -1 src:clblas
Bug #949767 [src:libgpuarray,src:pocl] clblas: *gemm wrong answers in 
out-of-order queues
Bug reassigned from package 'src:libgpuarray,src:pocl' to 'src:clblas'.
Ignoring request to alter found versions of bug #949767 to the same values 
previously set
Ignoring request to alter fixed versions of bug #949767 to the same values 
previously set
> found -1 2.12-1
Bug #949767 [src:clblas] clblas: *gemm wrong answers in out-of-order queues
Marked as found in versions clblas/2.12-1.

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

Bug#949767: clblas: *gemm wrong answers in out-of-order queues

2020-01-27 Thread Rebecca N. Palmer


Control: retitle -1 clblas: *gemm wrong answers in out-of-order queues
Control: reassign -1 src:clblas
Control: found -1 2.12-1

I think I've found the actual bug, in clblas src/library/blas/xgemm.cc: 
clblasGemm (with a single command queue) enqueues up to 4 kernels and 
returns an event that depends on only the last of them, so if the queue 
is out-of-order, waiting on this event doesn't necessarily wait for all 
of them to finish.


This was previously noticed in 
https://github.com/clMathLibraries/clBLAS/issues/269#issuecomment-225453543 
, but not actually reported as a bug.


clblas includes a client/performance tester that creates an out-of-order 
queue (at src/client/clfunc_common.hpp:306), implying that it intends to 
allow such queues.  (We don't run clblas' own tests, possibly because of 
https://github.com/clMathLibraries/clBLAS/issues/338.)


The real fix would be to return an event that depends on all the 
kernels' events (e.g. created with clEnqueueMarkerWithWaitList).


As a workaround for now, I intend to disable out-of-order queues in 
libgpuarray.  (It appears to be the only reverse dependency of clblas 
that also uses out-of-order queues.)

Bug#949972: ftbfs, fix build dependencies

Package: src:python-alignlib
Version: 0.1.1+dfsg-1
Severity: serious
Tags: sid bullseye patch

fix build dependencies, python3-all-dev is the only correct b-d.

patch at
http://launchpadlibrarian.net/462376359/python-alignlib_0.1.1+dfsg-1build1_0.1.1+dfsg-1ubuntu1.diff.gz

Bug#949971: ftbfs, missing b-d on dh-python

Package: src:pycangjie
Version: 1.3-1
Severity: serious
Tags: sid bullseye patch

missing b-d on dh-python,

patch at
http://launchpadlibrarian.net/462375088/pycangjie_1.3-1build1_1.3-1ubuntu1.diff.gz

Bug#949970: b-d's on python3-dev / python3-dbg but hardcodes 3.7

Package: src:pivy
Version: 0.6.4-2
Severity: serious
Tags: sid bullseye

b-d's on python3-dev / python3-dbg but hardcodes 3.7 in the rules file.  You
should not hard-code a specific Python3 version.

Bug#949968: fix build dependencies

Package: src:python-noise
Version: 0.3.0-2
Severity: serious
Tags: sid bullseye patch

fix build dependencies, python3-all-dev is the only correct b-d.

patch at
http://launchpadlibrarian.net/462373949/python-noise_1.2.3-2build1_1.2.3-2ubuntu1.diff.gz

Bug#949967: fix build dependencies

Package: src:python-py2bit
Version: 0.3.0-2
Severity: serious
Tags: sid bullseye patch

fix build dependencies, python3-all-dev is the only correct b-d.

patch at
http://launchpadlibrarian.net/462373681/python-py2bit_0.3.0-2build1_0.3.0-2ubuntu1.diff.gz

Processed: [bts-link] source package aiozmq

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

> #
> # bts-link upstream status pull for source package aiozmq
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #904358 (http://bugs.debian.org/904358)
> # Bug title: python3-aiozmq: fails to install with python 3.7
> #  * https://github.com/aio-libs/aiozmq/issues/132
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 904358 + fixed-upstream
Bug #904358 [python3-aiozmq] python3-aiozmq: fails to install with python 3.7
Added tag(s) fixed-upstream.
> usertags 904358 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 904358 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#947573: marked as done (FTBFS with scons 3.1.2-1)

Your message dated Mon, 27 Jan 2020 17:19:51 +
with message-id 
and subject line Bug#947573: fixed in nuitka 0.6.7+ds-1
has caused the Debian Bug report #947573,
regarding FTBFS with scons 3.1.2-1
to be marked as done.

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

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


-- 
947573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.6.3.1+ds-1
Severity: important
Usertags: scons_ftbfs


Hello, 

in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far. 

However, an error occurred while building your package. The build log
is attached.

Please check it and fix the error.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

dpkg-checkbuilddeps: error: Unmet build dependencies: python-all-dbg (>= 
2.6.6-2) rst2pdf (>= 0.14-2) python-pil | python-imaging python3-all-dev (>= 
3.2) python3-all-dbg (>= 3.2) python-appdirs | base-files (<< 7.2) 
python3-appdirs | base-files (<< 7.2)
[1;33mW: Unmet build-dependency in source[0m
dh clean --with python2,python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
pybuild --clean
I: pybuild base:217: python3.7 setup.py clean 
running clean
removing 
'/data/entwicklung/linux/debian/trans_scons/nuitka-0.6.3.1+ds/.pybuild/cpython3_3.7_nuitka/build'
 (and everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python2.7 setup.py clean 
running clean
removing 
'/data/entwicklung/linux/debian/trans_scons/nuitka-0.6.3.1+ds/.pybuild/cpython2_2.7_nuitka/build'
 (and everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
rm -rf .pybuild/
find . -name \*.pyc -exec rm {} \;
   dh_clean -O--buildsystem=pybuild
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/nuitka.substvars debian/files
rm -fr -- debian/nuitka/ debian/tmp/
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
-type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building nuitka using existing 
./nuitka_0.6.3.1+ds.orig.tar.gz
dpkg-source: info: building nuitka in nuitka_0.6.3.1+ds-1.debian.tar.xz
dpkg-source: info: building nuitka in nuitka_0.6.3.1+ds-1.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: including full source code in upload
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Fri Dec 27 14:36:10 CET 2019[0m
[0mI: pbuilder-time-stamp: 1577453770[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz][0m
[0mI: copying local configuration[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: Mounting /var/cache/debs[0m
[0mI: policy-rc.d already exists[0m
[1;33mW: Could not create compatibility symlink because /tmp/buildd exists and 
it is not a directory[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../nuitka_0.6.3.1+ds-1.dsc][0m
[0mI: copying [../nuitka_0.6.3.1+ds.orig.tar.gz][0m
[0mI: copying [../nuitka_0.6.3.1+ds-1.debian.tar.xz][0m
[0mI: Extracting source

Bug#937166: marked as done (nuitka: Python2 removal in sid/bullseye)

Your message dated Mon, 27 Jan 2020 17:19:51 +
with message-id 
and subject line Bug#937166: fixed in nuitka 0.6.7+ds-1
has caused the Debian Bug report #937166,
regarding nuitka: 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.)


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

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: nuitka
Source-Version: 0.6.7+ds-1

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

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

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

Debian distribution maintenance software
pp.
Kay Hayen  (supplier of updated nuitka 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: Thu, 23 Jan 2020 12:34:10 +0100
Source: nuitka
Binary: nuitka
Architecture: source all
Version: 0.6.7+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen 
Changed-By: Kay Hayen 
Description:
 nuitka - Python compiler with full language support and CPython compatibil
Closes: 937166 943645 947573
Changes:
 nuitka (0.6.7+ds-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   * The rst2pdf dependency is finally fixed
 (Closes: #943645) (Closes: #947573).
 .
   * Enabled package build without Python2 (Closes: #937166)
Checksums-Sha1:
 762fe25a7400aecab6d42dd564e657632a746695 2307 nuitka_0.6.7+ds-1.dsc
 6722db67ca191b8ba3e31a2df62e8b249b24c73a 1013741 nuitka_0.6.7+ds.orig.tar.gz
 280f8d317ed3d7eca49438483598e61063fb3148 11356 nuitka_0.6.7+ds-1.debian.tar.xz
 36b3e3cc111be461e45f49ffa1bdf0f084b3ca7d 871500 nuitka_0.6.7+ds-1_all.deb
 9238949c1af36d6e31ff8e3b78f8f9784d28455e 8851 nuitka_0.6.7+ds-1_amd64.buildinfo
Checksums-Sha256:
 0f4481bfd8ce01

Bug#943645: marked as done (nuitka: FTBFS: Traceback while running rst2pdf: NameError: name 'reportlab' is not defined)

Your message dated Mon, 27 Jan 2020 17:19:51 +
with message-id 
and subject line Bug#943645: fixed in nuitka 0.6.7+ds-1
has caused the Debian Bug report #943645,
regarding nuitka: FTBFS: Traceback while running rst2pdf: NameError: name 
'reportlab' is not defined
to be marked as done.

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

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


-- 
943645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.6.3.1+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

nuitka/experimental in a curent sid/experimental pbuilder environment:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/nuitka-0.6.3.1+ds'
rst2pdf README.rst
Traceback (most recent call last):
  File "/usr/bin/rst2pdf", line 11, in 
load_entry_point('rst2pdf==0.93.dev0', 'console_scripts', 'rst2pdf')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 489, 
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2852, 
in load_entry_point
return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2443, 
in load
return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2449, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/rst2pdf/createpdf.py", line 85, in 

from rst2pdf import flowables
  File "/usr/lib/python2.7/dist-packages/rst2pdf/flowables.py", line 875, in 

if reportlab.Version == '2.1':
NameError: name 'reportlab' is not defined
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/nuitka-0.6.3.1+ds'


Andreas


nuitka_0.6.3.1+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: nuitka
Source-Version: 0.6.7+ds-1

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

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

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

Debian distribution maintenance software
pp.
Kay Hayen  (supplier of updated nuitka 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: Thu, 23 Jan 2020 12:34:10 +0100
Source: nuitka
Binary: nuitka
Architecture: source all
Version: 0.6.7+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen 
Changed-By: Kay Hayen 
Description:
 nuitka - Python compiler with full language support and CPython compatibil
Closes: 937166 943645 947573
Changes:
 nuitka (0.6.7+ds-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   * The rst2pdf dependency is finally fixed
 (Closes: #943645) (Closes: #947573).
 .
   * Enabled package build without Python2 (Closes: #937166)
Checksums-Sha1:
 762fe25a7400aecab6d42dd564e657632a746695 2307 nuitka_0.6.7+ds-1.dsc
 6722db67ca191b8ba3e31a2df62e8b249b24c73a 1013741 nuitka_0.6.7+ds.orig.tar.gz
 280f8d317ed3d7eca49438483598e61063fb3148 11356 nuitka_0.6.7+ds-1.debian.tar.xz
 36b3e3cc111be461e45f49ffa1bdf0f084b3ca7d 871500 nuitka_0.6.7+ds-1_all.deb
 9238949c1af36d6e31ff8e3b78f8f9784d28455e 8851 nuitka_0.6.7+ds-1_amd64.buildinfo
Checksums-Sha256:
 0f4481bfd8ce01e0820834451dfb4304f061d210f3346d0ef62791efec2396de 2307 
nuitka_0.6.7+ds-1.dsc
 719008f609000a677c5eadfd386ae93f0f26161bf9f22544eb78be67dcbbd338 1013741 
nuitka_0.6.7+ds.orig.tar.gz
 750129e29503735293c964a8bee59c6de4968c08d2c99a3ef0054a489af75df9 11356 
nuitka_0.6.7+ds-1.debian.tar.xz
 82e6728e300a9b7693d28844cb9b562e4902b04b9381a02b7065e3766c153f03 871500 
nuitka_0.6.7+ds-1_all.deb
 bdeaf6e46d77fc48c6f3bce7678a26af0f3bc39a7d0f8cbf05ffed719144c717 8851 
nuitka_0.6.7+ds-1_amd64.buildinfo
Files:
 9883fc912aa369a391a2a3efa5383403 2307 python optional nuitka_0.6.7+ds-1.dsc
 f8c438d5441f47bf4c24d6e166ca74b4 1013741 python optional 
nuitka_0.6.7+ds.orig.tar.gz
 0937d0717403323ccc4b65b3be6e21f4 11356 python optional 
nuitka_0.6.7+ds-1.debian.tar.xz
 37d09e1ac8e5d06922fb5085a9246de5 871500 python optional 
nuitka_0.6.7+ds-

Processed: [bts-link] source package src:exiv2

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

> #
> # bts-link upstream status pull for source package src:exiv2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #923473 (http://bugs.debian.org/923473)
> # Bug title: exiv2: CVE-2019-9144
> #  * https://github.com/Exiv2/exiv2/issues/712
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 923473 + fixed-upstream
Bug #923473 [src:exiv2] exiv2: CVE-2019-9144
Added tag(s) fixed-upstream.
> usertags 923473 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 923473 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: debcargo.toml should make it possible to declare additional dependencies for generated autopkgtests

Processing control commands:

> block 947709 with -1
Bug #947709 [src:rust-clang-sys] rust-clang-sys: autopkgtest failure: all tests 
fail
947709 was not blocked by any bugs.
947709 was not blocking any bugs.
Added blocking bug(s) of 947709: 949959
> affects -1 + src:rust-clang-sys
Bug #949959 [debcargo] debcargo.toml should make it possible to declare 
additional dependencies for generated autopkgtests
Added indication that 949959 affects src:rust-clang-sys

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

Processed: found 949229 in 0.20.0-2, severity of 949229 is serious

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

> found 949229 0.20.0-2
Bug #949229 {Done: Eric Dorland } [opensc] opensc.conf config 
file not installed at the correct location?
Marked as found in versions opensc/0.20.0-2; no longer marked as fixed in 
versions opensc/0.20.0-2 and reopened.
> severity 949229 serious
Bug #949229 [opensc] opensc.conf config file not installed at the correct 
location?
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: virglrenderer: CVE-2020-8002 CVE-2020-8003

Processing control commands:

> found -1 0.7.0-2
Bug #949954 [src:virglrenderer] virglrenderer: CVE-2020-8002 CVE-2020-8003
Marked as found in versions virglrenderer/0.7.0-2.

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

Bug#949711: Build-depends on sgmltools-lite, which is being removed

2020-01-27 Thread Moritz Mühlenhoff

On Fri, Jan 24, 2020 at 10:24:59AM -0800, Steve Langasek wrote:
> On Thu, Jan 23, 2020 at 11:34:12PM +0100, Moritz Muehlenhoff wrote:
> > Source: aboot
> > Severity: serious
> 
> > sgmltools-lite is scheduled for removal and aboot is the last package
> > build depending on it.
> 
> > There hasn't been any aboot upload since 2013 and it's RC-buggy for a
> > long time, should we simply remove it?
> 
> Yes, the arch: all binaries can only be built on an alpha toolchain, for
> which we have no official builders in Debian.  I think it should probably
> just be removed.

Thanks, I've just filed a removal bug.

Cheers,
Moritz

Bug#947709: (no subject)

2020-01-27 Thread Wolfgang Silbermayr

A quick investigation reveals:

* We have the "@" test (currently called command1 in the quoted log)
  which enables all crate features. The clang-sys crate does not permit
  enabling both the "runtime" and the "static" features at the same
  time, so the build script intentionally aborts with a compiler error.
  We will mark this test as FLAKY with the test_is_broken debcargo
  config flag for the next rust-clang-sys release.
* The other tests fail because they attempt to run the `llvm-config`
  tool which isn't installed. I tested with the llvm and clang moved
  from the Recommends to the Depends field. This could be fixed by using
  the Depends field in the autopkgtests control. I don't know if
  debcargo is already able to output that field, maybe we have to
  implement it there first.

Bug#949954: virglrenderer: CVE-2020-8002 CVE-2020-8003

2020-01-27 Thread Salvatore Bonaccorso

Source: virglrenderer
Version: 0.8.1-6
Severity: grave
Tags: security upstream
Control: found -1 0.7.0-2

Hi,

The following vulnerabilities were published for virglrenderer.

CVE-2020-8002[0]:
| A NULL pointer dereference in vrend_renderer.c in virglrenderer
| through 0.8.1 allows attackers to cause a denial of service via
| commands that attempt to launch a grid without previously providing a
| Compute Shader (CS).


CVE-2020-8003[1]:
| A double-free vulnerability in vrend_renderer.c in virglrenderer
| through 0.8.1 allows attackers to cause a denial of service by
| triggering texture allocation failure, because
| vrend_renderer_resource_allocated_texture is not an appropriate place
| for a free.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-8002
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8002

https://gitlab.freedesktop.org/virgl/virglrenderer/commit/63bcca251f093d83da7e290ab4bbd38ae69089b5
[1] https://security-tracker.debian.org/tracker/CVE-2020-8003
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8003

https://gitlab.freedesktop.org/virgl/virglrenderer/commit/522b610a826f6de58c560cbb38fa8dfc65ae3c42
[2] https://gitlab.freedesktop.org/virgl/virglrenderer/merge_requests/340

Regards,
Salvatore

Processed: fix severity and affects after using forcemerge the wrong way around

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

> severity 946267 serious
Bug #946267 [cpio] cpio -i --no-absolute-filenames breaks symlinks starting 
with / or /..
Bug #946469 [cpio] initramfs-tools-core: unmkinitrams creates broken binaries
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> affects 946267 live-build
Bug #946267 [cpio] cpio -i --no-absolute-filenames breaks symlinks starting 
with / or /..
Bug #946469 [cpio] initramfs-tools-core: unmkinitrams creates broken binaries
Added indication that 946267 affects live-build
Added indication that 946469 affects live-build
>
End of message, stopping processing here.

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

Processed: Re: Bug#945814: audacity: various segfaults of audacity on startup

Processing control commands:

> reassign -1 zynaddsubfx-dssi 3.0.3-1
Bug #945814 [audacity] audacity: various segfaults of audacity on startup
Bug reassigned from package 'audacity' to 'zynaddsubfx-dssi'.
No longer marked as found in versions audacity/2.2.2-1.
Ignoring request to alter fixed versions of bug #945814 to the same values 
previously set
Bug #945814 [zynaddsubfx-dssi] audacity: various segfaults of audacity on 
startup
Marked as found in versions zynaddsubfx/3.0.3-1.
> affects -1 + audacity
Bug #945814 [zynaddsubfx-dssi] audacity: various segfaults of audacity on 
startup
Added indication that 945814 affects audacity

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

Bug#945814: audacity: various segfaults of audacity on startup

2020-01-27 Thread Bernhard Übelacker

Control: reassign -1 zynaddsubfx-dssi 3.0.3-1
Control: affects -1 + audacity


Hello Tjeerd,

> Thanks for coming back, I'm not in a hurry...
> 
> The problem is that I can not trigger specific bugs (they seem to happen
> somewhat random). So a made some more valgrinds: valgrind.dat 

Because the error des not manifest each run in the same location
this might be thread related e.g. two threads are working on the
same memory.


> I had zynaddsubfx installed to try it out and see if I like it, but did
> not uninstall after the tries (sufficient diskspace luxury). I could
> uninstall zynadd, zynsaddsubfx and zynaddsubfx-dssi, the data package is
> depended on by the lmms-common package.

I tried to install some more lv2 plugins and bridges and after enabling
all in audacity I got the shared library loaded libzynaddsubfx_dssi.so
by just starting audacity - but still cannot reproduce a crash.
(Details attached.)


> And audacity runs without crashing (thanks for the hint) but still gives
> a lot of debug output: audacity_debug.dat

Most of the remaining output seems gui related - seems to be harmless.


> So at least the the source of all evil is now clear... and the bug
> "resolved". Do you have contact with the zynaddsubfx devs and file a bug
> there? Devs amongst each other might talk clearer? Otherwise I'm happy
> to do it.

It might not be that clear - depending on e.g. libzynaddsubfx_dssi.so
is intended to work multi threaded ...

When I did run audacity in my test environment I get some
"Possible data race" with valgrind's helgrind tool.

At least it might be related to some plugins, either direct or
via some bridges, therefore I hope it is ok to reassign.

Bringing the issue upstream might also not be a bad idea.

Kind regards,
Bernhard

# Buster/stable amd64 qemu VM 2020-01-27

apt update
apt dist-upgrade


apt install systemd-coredump xserver-xorg sddm openbox xterm mc strace valgrind 
gdb audacity jackd2 lmms zynadd zynaddsubfx-dssi liblv2dynparamhost1-1 
naspro-bridges audacity-dbgsym libstdc++6-8-dbg zynaddsubfx-dssi-dbgsym 
naspro-bridges-dbgsym libjack-jackd2-0-dbgsym libwxbase3.0-0v5-dbgsym 
libportaudio2-dbgsym libnabrit-dbg liblilv-0-0-dbgsym


reboot


# dpkg -l | grep -i -E "audacity|jack|zynaddsubfx|lmms"
ii  audacity   2.2.2-1+b1   amd64
fast, cross-platform audio editor
ii  audacity-data  2.2.2-1  all  
fast, cross-platform audio editor (data)
ii  audacity-dbgsym2.2.2-1+b1   amd64
debug symbols for audacity
ii  jackd  5+nmu1   all  
JACK Audio Connection Kit (default server package)
ii  jackd2 1.9.12~dfsg-2amd64
JACK Audio Connection Kit (server and example clients)
ii  jackd2-firewire1.9.12~dfsg-2amd64
JACK Audio Connection Kit (FFADO and FreeBoB backends)
ii  libjack-jackd2-0:amd64 1.9.12~dfsg-2amd64
JACK Audio Connection Kit (libraries)
ii  libjack-jackd2-0-dbgsym:amd64  1.9.12~dfsg-2amd64
debug symbols for libjack-jackd2-0
ii  lmms   1.1.3-8.1amd64
Linux Multimedia Studio
ii  lmms-common1.1.3-8.1all  
Linux Multimedia Studio - common files
ii  qjackctl   0.5.0-1  amd64
User interface for controlling the JACK sound server
ii  zynadd 1+git.20100609+dfsg0-4   amd64
ZynAddSubFX engines converted to LV2 plugin format
ii  zynaddsubfx3.0.3-1  amd64
Realtime software synthesizer for Linux
ii  zynaddsubfx-data   3.0.3-1  all  
Realtime software synthesizer for Linux (data)
ii  zynaddsubfx-dssi   3.0.3-1  amd64
dssi plugin of zynaddsubfx
ii  zynaddsubfx-dssi-dbgsym3.0.3-1  amd64
debug symbols for zynaddsubfx-dssi





export LANG=C
export DISPLAY=:0

qjackctl
# Start



audacity

# Select all new plugins and enable
# Close




gdb -q

set width 0
set pagination off
set breakpoint pending on
file /usr/bin/audacity
break _ZN3zyn10MiddleWare4tickEv
run
break 
_ZN3zyn4Bank9addtobankEiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_
cont
break free
cont
generate /home/benutzer/core



(gdb) bt
#0  __GI___libc_free (mem=0x5652b0c0) at malloc.c:3083
#1  0x7fffe9511f3d in zyn::Bank::addtobank(int, 
std::__cxx11::basic_string, std::allocator 
>, std::__cxx11::basic_string, 
std::allocator >) () from /usr/lib/dssi/libzynaddsubfx_dssi.so
#2  0x7fffe95138a1 in zyn::Bank::loadbank(std::__cxx11::basic_string, std::allocator >) () from 
/usr/lib/dssi/libzynaddsubfx_dssi.so
#3  0x7fffe955b29c in ?? () from /usr/lib/dssi/libzynad

Processed: Re: #946469: cpio-2.13 relative symlink handling with --no-absolute-filenames

Processing control commands:

> forcemerge -1 946267
Bug #946469 [cpio] initramfs-tools-core: unmkinitrams creates broken binaries
Bug #946267 [cpio] cpio -i --no-absolute-filenames breaks symlinks starting 
with / or /..
Unset Bug forwarded-to-address
Severity set to 'important' from 'serious'
Removed indication that 946267 affects live-build
Merged 946267 946469

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

Bug#949942: backup2swift build depends on the removed pep8 transitional package

Source: backup2swift
Version: 0.8-1.1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949940: cloud-init build depends on the removed pep8 transitional package

Source: cloud-init
Version: 19.3-1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949941: byobu build depends on the removed pep8 transitional package

Source: byobu
Version: 5.130-1.1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949939: custodia build depends on the removed pep8 transitional package

Source: custodia
Version: 0.6.0-4
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949938: d-feet build depends on the removed pep8 transitional package

Source: d-feet
Version: 0.3.15-1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949936: python-cliapp build depends on the removed pep8 transitional package

Source: python-cliapp
Version: 1.20180812.1-3
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949937: dirspec build depends on the removed pep8 transitional package

Source: dirspec
Version: 13.10-1.1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949934: seqdiag build depends on the removed pep8 transitional package

Source: seqdiag
Version: 0.9.5+dfsg-1.2
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949935: python-ddt build depends on the removed pep8 transitional package

Source: python-ddt
Version: 1.2.1-2
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Bug#949933: swiftsc build depends on the removed pep8 transitional package

Source: swiftsc
Version: 0.5-1.1
Severity: serious
Tags: ftbfs

pep8 is no longer built by src:pep8.

Processed: closing 949213

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

> close 949213
Bug #949213 [src:naev] naev: FTBFS: undefined reference to 
`bfd_get_section_flags'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#949859: google-apputils-python: should this package be removed?

2020-01-27 Thread Thomas Goirand

On 1/26/20 7:02 AM, Sandro Tosi wrote:
> Source: google-apputils-python
> Severity: serious
> 
> Hello,
> i think we should remove google-apputils-python from debian:
> 
> * last upstream release in 2014
> * upstream marked[1] it as "Obsolete. Please migrate to absl-py instead."
> * no reverse dependencies for both py2 and py3 packages
> * RC-buggy since a year and a half with no action on a (simple?) bug
> 
> [1] https://pypi.org/project/google-apputils/
> 
> If i dont hear back within a week with a good reason to keep this package, 
> i'll
> file for its removal.
> 
> Regards,
> Sandro

I agree with this.

Thomas

Bug#948907: ktp-call-ui is marked for autoremoval from testing

2020-01-27 Thread Alexander Akulich

Hello, dear Debian developers!

It seems that you updated TelepathyQt to v0.9.8, but you didn't update
KDE Applications at least to v19.12.0. The mentioned bug fixed by this
patch from an Arch developer: https://phabricator.kde.org/D25372
(released as v19.12.0).

Processed: tagging 949767, found 949887 in 2.0.51-1, found 949887 in 2.96-2.1

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

> tags 949767 + sid bullseye
Bug #949767 [src:libgpuarray,src:pocl] wrong results in gemm(batch) in 
out-of-order queues
Added tag(s) bullseye and sid.
> found 949887 2.0.51-1
Bug #949887 [munin,sysvinit-core] munin autopkgtest failure for sysvinit based 
tests
There is no source info for the package 'sysvinit-core' at version '2.0.51-1' 
with architecture ''
Marked as found in versions munin/2.0.51-1.
> found 949887 2.96-2.1
Bug #949887 [munin,sysvinit-core] munin autopkgtest failure for sysvinit based 
tests
There is no source info for the package 'munin' at version '2.96-2.1' with 
architecture ''
Marked as found in versions sysvinit/2.96-2.1.
> thanks
Stopping processing here.

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

Bug#937487: marked as done (pynag: Python2 removal in sid/bullseye)

Your message dated Mon, 27 Jan 2020 09:19:40 +
with message-id 
and subject line Bug#937487: fixed in pynag 1.1.2+dfsg-2
has caused the Debian Bug report #937487,
regarding pynag: 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.)


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

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: pynag
Source-Version: 1.1.2+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pynag package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jan 2020 10:51:59 +0200
Source: pynag
Architecture: source
Version: 1.1.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Stefano Rivera 
Closes: 937487
Changes:
 pynag (1.1.2+dfsg-2) unstable; urgency=medium
 .
   * Team upload (to unstable).
   * Drop Python 2 package (Closes: #937487)
   * Bump Standards-Version to 4.5.0, no changes needed.
Checksums-Sha1:
 12850ee950826851d9b6caa40751896175ff971e 1480 pynag_1.1.2+dfsg-2.dsc
 d220d311a6dacc652deebe01efc1839e8c55b718 2628 pynag_1.1.2+dfsg-2.debian.tar.xz
 2e7961979262698d1d1f3d07f382739ec685d9d9 5465 
pynag_1.1.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 e6648d2da6ebd869ea22142e3090410a9a13b5b4564b32162f5d5ff13ec29fef 1480 
pynag_1.1.2+dfsg-2.dsc
 cbd48f776eae210975a94a882c0edd55f45cbf74cb26bbf0a00b4f8d5a35df4e 2628 
pynag_1.1.2+dfsg-2.debian.tar.xz
 89569d97755e5c18ca8b94192f4861c1662b6b2d5c92cb49ff378947d0bb0c30 5465 
pynag_1.1.2+dfsg-2_source.buildinfo
Fi

Processed: bug 949926 is forwarded to https://github.com/backtracking/mlpost/issues/10

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

> forwarded 949926 https://github.com/backtracking/mlpost/issues/10
Bug #949926 [src:mlpost] FTBFS with bitstring 3.1.1
Set Bug forwarded-to-address to 
'https://github.com/backtracking/mlpost/issues/10'.
> thanks
Stopping processing here.

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

Bug#949926: FTBFS with bitstring 3.1.1

2020-01-27 Thread Stéphane Glondu

Package: src:mlpost
Version: 0.8.2-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

mlpost FTBFS with latest ocaml-bitstring (3.1.1):

  https://buildd.debian.org/status/package.php?p=mlpost&suite=unstable


Cheers,

-- 
Stéphane

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

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

Bug#937487: marked as pending in pynag

2020-01-27 Thread Stefano Rivera

Control: tag -1 pending

Hello,

Bug #937487 in pynag 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/python-team/modules/pynag/commit/680767f52a05163ac0472cded08d910f124a27ba


Drop Python 2 package (Closes: #937487)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937487

Bug#949727: firmware-misc-nonfree: Missing dependency initramfs-tools-core

2020-01-27 Thread Vincent Lefevre

On 2020-01-26 04:42:13 +, Ben Hutchings wrote:
> On Fri, 2020-01-24 at 08:53 +0100, mando wrote:
> > I tried to install firmware-misc-nonfree and I got this error:
> > 
> > modprobe: ERROR: ../libkmod/libkmod.c:508 
> > kmod_lookup_alias_from_builtin_file() 
> > could not open builtin file '/lib/modules/xxx/modules.builtin.bin'
> >
> > ... where xxx is the result of $(uname -r)
> 
> Looks like bug #948257.

No, it isn't. The user's logs show that he installed

2020-01-24 08:43:15 status installed initramfs-tools-core:all 0.136

but version 0.136 is claimed as fixed.

The path in the error message starts with "/lib/modules" rather than
"/var/tmp/mkinitramfs_". So I would say that it's rather bug 949444.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Bug#937487 marked as pending in pynag

Processing control commands:

> tag -1 pending
Bug #937487 [src:pynag] pynag: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#949044: marked as done (dbus-cpp: FTBFS: -Werror=deprecated-copy)